Related
*** DISCLAIMER ***
I work on projects that may brick your device. Don't sue me, hate me or try and kill my dog if that happens. I will feel bad the community will feel bad and hopefully we'll find a way to get you going again. But, the very nature of my projects involves a certain amount of risk taken by YOU. And by using the projects that I work on, you've accepted that fact.
WARNING #1: CURRENTLY THERE IS AN UNKNOWN ISSUE WHERE IF YOU HAVE ENCRYPTION ENABLED AND INSTALL SS IT BOOTLOOPS. IF YOU FIT THIS DESCRIPTION PLEASE STAY AWAY FROM SAFESTRAP FOR NOW.
WARNING #2: BECAUSE THERE ARE NO ODIN FILES FOR MF3, DO NOT FLASH THE STOCK ROM AT ALL. PLAY IT SAFE AND USE ROM-SLOTS.
CURRENT PROJECT STATUS:
v3.72 (TW4.4): Beta testing, no rom-slots
v3.65 (TW4.2): Stable
WHAT IS SAFESTRAP?
Safestrap is a Bootstrap / Recovery for locked bootloader phones. The goal is to avoid touching your primary system (I'll call this "stock" system) and only flash or make large changes to another place on your phone that Safestrap treats as a "2nd system" (in this case, it's a series of virtual ROM slots located on the internal emmc area: "/sdcard"). Once installed, you will see a "Splashscreen" giving you the option to hit "menu" to enter recovery. The recovery portion of Safestrap is now based on TWRP 2.6.1.0 (a touch based recovery) and you can perform .zip installs, backups and restores here. The additional features I've added to TWRP are mostly located under the "Boot Options" menu:
Here you can create virtual ROM-slots (2 on the S4 due to partition size and internal space) for flashing ROMs. These ROM-slots allow for different sizes of /data partitions. NOTE: The bigger you make the /data partition the less room you will have to make other ROM-slots.
You can activate a new ROM-slot by choosing the slot you wish to make active and then selecting the "Activate" button. Once active, you will see the "rom-slot#" up in the top of the screen shown in green. If you make the "stock" ROM active, then you can see it in the top shown in red.
Once a ROM-slot is active, all actions you would normally perform using TWRP are directed to that ROM-slot. For example, "Install" to flash a .zip, backup and restore.
For more information you can read up here:
http://blog.hash-of-codes.com/how-to-safestrap/
HOW DO I INSTALL SAFESTRAP?
Requirement: Root
[NEW FOR KK/v3.73] Install Busybox via the Play Store (Busybox Free Installer)
[NEW FOR KK/v3.73] Remove XPOSED framework for the Safestrap install. It causes conflicts sometimes. Can re-install afterward.
Requirement: Allow APK install from Unknown Sources
Download the Safestrap APK
Find the APK using a Filemanager tool and open it on your device, then click "Install".
(If updating from an existing Safestrap you might be warned that this will over-write the existing installation. Click the "Yes" equivalent to this message.)
Once installed, open up the Safestrap application as you would any other app.
Agree to the disclaimer that you won't try to sue me and hunt me down with a rifle if you manage to break your phone..
Then use the "Install Recovery" button. You should see the current version down in the lower left corner of the window. And the "Status:" should say "Installed" when you're done.
From there you can reboot and you *should* see a new splash screen during the boot up. While this is showing you can enter Safestrap Recovery using the [ menu ] button.
That's it for the installation! Read below for a brief overview of Safestrap Recovery v3.x
HOW DO I ENTER RECOVERY?
During each reboot a splashscreen will be displayed showing whether the device is running a rom-slot or on the "Stock ROM".
Press under the button shown on the screen to either enter "RECOVERY" or "CONTINUE" booting.
By "under", I mean on the touch key portion of the front display on either side of the center button.
KNOWN ISSUES:
[v3.73] ROM-SLOTs aren't supported yet
[v3.73] "Reboot Recovery" doesn't work in the APK (? -- need verified)
NEW TO v3.73:
TWRP 2.7.0.x update for the base recovery. This includes vibration support, backup time/date fixes and more.
ROM-SLOTs now have a 16gb size limit (vs 4gb previously) [THEY DON'T WORK YET IN KK THO SO BE PATIENT]
DOWNLOADS:
CONFIRM THAT YOU ARE USING AN AT&T SAMSUNG GALAXY S4 ACTIVE
MAKE SURE IF YOU ARE UPGRADING TO v3.7x FROM v3.65 THAT YOU USE THE "UNINSTALL RECOVERY" BUTTON IN THE v3.65 APK BEFORE INSTALLING v3.7x.
NOTE: USE ONLY ROMS THAT MATCH UP WITH YOUR TOUCHWIZ VERSION. IF YOU'RE ON TW4.2 USE SS3.65 AND ONLY USE TW4.2 ROMS. IF ON TW4.4 USE SS3.73 AND ONLY USE TW4.4 ROMS
FIND YOUR STOCK OPERATING SYSTEM VERSION BELOW AND USE THAT FILENAME:
FOR USERS OF KK/TW4.4:
USE 3.73+:BETA Safestrap-JFLTEATT-ACTIVE-3.73.apk (updated 2014-06-02)
FOR USERS OF MF3 (TW4.2):
LATEST FILE: Safestrap-JFLTEATT-ACTIVE-3.65.apk (updated 2013-11-15)
Main XDA Downloads Page
Mirror 1 (Goo.im): http://goo.im/devs/Hashcode/jflteatt-active/safestrap
Mirror 2 (Crackflasher): http://downloads.crackflasher.com/?dir=Devs/Hashcode0f/jflteatt-active/safestrap
HOW TO MANUALLY REMOVE SAFESTRAP:
Enter adb shell from your pc:
Code:
su
mount -o remount,rw /system
mv /system/etc/init.qcom.modem_links.sh.bin /system/etc/init.qcom.modem_links.sh
rm -rf /system/etc/safestrap
rm /system/etc/firmware/q6.mdt
ln -s /firmware/image/q6.mdt /system/etc/firmware/q6.mdt
mount -o remount,ro /system
As of version 3.7x, Safestrap Recovery is now based on TWRP 2.7.x.x. For more on TWRP you can visit their website: http://www.teamw.in/
WARNING: Safestrap is heavily modified to be "Safe" for your device. Do not download TWRP from their website and expect it to work the same way. Also TWRP does not support Safestrap, tho some issues that may come up will be TWRP dependant, please try and contact myself or look on the forums for your device for answers before hunting down TWRP people. They won't be able to help w/ Safestrap specific questions.
This thread is a development ONLY thread.
For discussion go here:
http://forum.xda-developers.com/showthread.php?t=2447764
XDA:DevDB Information
Safestrap Recovery v3.65 (JB) / v3.73 (KK), Tool/Utility for the Samsung Galaxy S 4 Active
Contributors
Hashcode, DeesTroy & TeamWin
Version Information
Status: Beta
Current Stable Version: 3.65
Stable Release Date: 2013-11-15
Current Beta Version: 3.73
Beta Release Date: 2014-06-02
Created 2013-09-18
Last Updated 2014-06-02
Reserved
MAIN MENU:
Boot Options: This area is for managing your virtual ROM-slots. You create a new ROM-slot by clicking on one and if it doesn't exist you will be prompted to create it. Follow the on-screen guides. Once a ROM-slot is created you select that slot to activate or delete it. Under each ROM slot (once created) you can:
Activate: Makes the chosen ROM-slot the "current" one, where almost all of the features of TWRP affect that slot. This will also be the ROM that is booted.
Set Nickname: For convenience you can set a small name for each ROM-slot. This is limited to 10 characters as it will eventually be added to the beginning of backup names. This name is shown on the ROM-slot button once it is set.
Check FS: This performs a file system checks on the ROM-slot and fixes any errors found.
Delete: Delete the ROM-slot files (disabled if the ROM is active — please choose another ROM-slot to activate and then come back) USE WITH CAUTION, THERE'S NO GETTING THESE BACK UNLESS YOU HAVE BACKUPS.
Install: This is for flashing a .zip file to the currently active system. Currently, this is disabled for the stock system. In a future release I will enable flashing to the stock system.
Backup / Restore: This should be self-explanitory, but you use these options for making backups of the currently selected system. Or restoring a previously made backup to the currently selected system (regardless of where you backed it up from). DON'T RESTORE A CUSTOM ROM-SLOT BACKUP TO THE STOCK ROM. THIS WILL MOST LIKELY BRICK YOUR PHONE.
Mount: You can manually manage mounts here. NOTE: the "system", "data" and "cache" mounts will use the currently selected ROM-slot.
Wipe: Manually erase portions of the device. NOTE: You only have 1 internal and 1 external SD card. These are not "virtual" if you erase them. They are gone. Use with caution. Wiping the "system" when "stock" ROM is selected will try and keep the Safestrap hijack in place.
Advanced:
Copy Log to SD: Experienced something odd and want to report it? DO THIS and include the log when you send me the report. Otherwise, the recovery.log will disappear when you reboot.
Fix Permissions: This can fix up ROMs which are displaying odd force close issues, etc. You will probably never need to do this.
Partition SD Card: You can add ext3 partitions to the external SD card if you want. I'm not sure we have much of a need for this on our devices.
File Manager: This works like any other file manager inside Android. You can thank the TWRP people for this, because it is quite possibly one of the best features I've ever seen in a recovery.
Terminal Command: Also very handy for those once in a while moments when you have to do something via terminal but don't have adb handy. USE WITH CAUTION
Settings:
Here you can turn on and off signature verification of .zip files
Force MD5 sum checks on .zip files prior to flashing
"Use rm -rf instead of formatting" this may or may not be checked in Safestrap, but the key partitions which are signed and cannot be truely formatted will automatically use this feature
There are a few other checkbox options in here. Please know what you are doing.
Simulate most actions for theme testing. If you have this checked, Safestrap/TWRP will not perform most actions but show the dialog boxes so you can review theme elements. If you turn this on, it STAYS ON till you turn it off. And will show "SIMULATING ACTIONS" up top.
Set the Time Zone (use "Set Time Zone" button after choosing which time zone you want)
Restore Defaults. Use this to reset all options back to default as it came when you installed for the first time. Does not erase backups or ROM-slots, tho it might change the active slot.
Reboot: Choose from 2 options for rebooting "System" which performs a reset/reboot of the device and "Power Off" which turns the device off.
Reserved
KNOWN ISSUES:
Bluetooth remote control isn't working on rom-slots.
CHANGELOG:
[2013/11/13] TWRP updates
[2013/11/13] "toolbox" binary / symlinks in recovery fixed
[2013/11/11] Uninstall from the APK fixed
[2013/09/17] /sdcard mounting bugfix
[2013/09/17] Hijack improments to support default rootfs files
[2013/09/17] ROM-slot image creation bugfix for size > 2gb
[2013/09/12] Much improved block device handling
[2013/09/11] Bugfix in script translation
[2013/09/11] hijack / init.rc tweaks
[2013/09/11] Bugfix for display lag / buffering issue (WIP)
[2013/09/10] Adjust "ROM-slot" display in UI
[2013/09/10] /data/media handling changes
[2013/09/06] custom twrp.fstab files
[2013/09/06] /data/media handling changes
It's like Christmas... Testing now!
Edit: No camera or wifi (didn't test much else), but I successfully booted this: http://forum.xda-developers.com/showthread.php?t=2406177
Sent from my SAMSUNG-SGH-I537 using Tapatalk 4
Bleh, just realized this isn't a discussion thread, my mistake. Mods, delete this is necessary, sorry, sorry, was just excited to see some progress.
Go Hashcode go!
Thanks you soon much OP. Testing now.
Sent from my SAMSUNG-SGH-I537 using Xparent BlueTapatalk 2
Added the ATT ACTIVE MF3 stock kernel modules to the downloads section.
http://forum.xda-developers.com/devdb/project/?id=681#downloads
If you're on the locked MF3 build: Keep these on the device and flash them after any ROMs that are installed. They will sync up the kernel modules and restore wifi, bt, etc.
Do we need those modules for MF1?
Hashcode said:
Added the ATT ACTIVE MF3 stock kernel modules to the downloads section.
http://forum.xda-developers.com/devdb/project/?id=681#downloads
If you're on the locked MF3 build: Keep these on the device and flash them after any ROMs that are installed. They will sync up the kernel modules and restore wifi, bt, etc.
Click to expand...
Click to collapse
@Hashcode I modified your zip with the modules for MF1. You can add it to the d/l page if you want. Confirmed wifi fix for AOSP port.
http://db.tt/4uMS68Xy
Sent from my SAMSUNG-SGH-I537 using Tapatalk 4
Anyone have a mirror to the MF3 kernel modules? I cant download it for some reason.
Edit N/M finally got it. Here is a mirror if someone has issues like I did. https://www.dropbox.com/s/5xdeag03qu90r92/jflteatt-active-MF3-modules.zip
And here's another mirror just in case meaning the kernel modules for build MF3 in a flashable zip as provided by Hashcode; these are necessary for people wishing to install other ROMs using Safestrap to ensure the hardware works, for the most part (Wi-Fi, Bluetooth, etc - but the camera will probably always have issues with other ROMs till someone figures it out):
https://dl.dropboxusercontent.com/u/19019338/jflteatt-active-MF3-modules.zip
br0adband said:
And here's another mirror just in case meaning the kernel modules for build MF3 in a flashable zip as provided by Hashcode; these are necessary for people wishing to install other ROMs using Safestrap to ensure the hardware works, for the most part (Wi-Fi, Bluetooth, etc - but the camera will probably always have issues with other ROMs till someone figures it out):
https://dl.dropboxusercontent.com/u/19019338/jflteatt-active-MF3-modules.zip
Click to expand...
Click to collapse
Has anybody tried contacting @LeJay about the camera issue? He was able to get the camera working on Cyanogenmod so he might be able to work his magic again.
Devo7v said:
Has anybody tried contacting @LeJay about the camera issue? He was able to get the camera working on Cyanogenmod so he might be able to work his magic again.
Click to expand...
Click to collapse
Not sure how safestrap works and I haven't tested it myself, but something along the lines of this patch + maybe a 3rd party camera app should work.
Posted specific instructions by @TreyLWalker for flashing Safestrap + Google Play Edition ROM and the camera patch in #3 post:
http://forum.xda-developers.com/showpost.php?p=45694084&postcount=3
Procedure for my Samsung S4 Active i537 MF3 - I537UCUAMF3 - US, AT&T:
Installed Safestrap Recovery v3.5x Safestrap-JFLTEATT-ACTIVE-3.5x-B08.apk
Installed Recovery, Rebooted into Recovery, Pressed Settings Key on Splash Screen Load
Created ROM Slot-1, Set it to active, Installed with the following:
AOSP Port GT-I9295 - Official 4.2.2 - I9295-PORT-GoogleEdition-V1.zip (worked for i537 despite saying otherwise, I still wouldn't flash stock ROM....)
MF3/MF1 Kernal Modules - jflteatt-active-MF3-modules.zip / jflteatt-active-MF1-modules.zip (in same downloads area)
LeJay's S4 Active Camera Patch - SGS4A_CamPatch.zip
Working Phone, Bluetooth, Wifi, Stock Camera App /w Flash (video-recording preview is low-res, but records normal)
If this was made to work on the i9295 would we then be able to flash roms without needing to use Odin to get Wi-Fi working?
Sent from my GT-I9295 using XDA Premium HD app
Hashcode said:
Posted specific instructions by @TreyLWalker for flashing Safestrap + Google Play Edition ROM and the camera patch in #3 post:
http://forum.xda-developers.com/showpost.php?p=45694084&postcount=3
Procedure for my Samsung S4 Active i537 MF3 - I537UCUAMF3 - US, AT&T:
Installed Safestrap Recovery v3.5x Safestrap-JFLTEATT-ACTIVE-3.5x-B08.apk
Installed Recovery, Rebooted into Recovery, Pressed Settings Key on Splash Screen Load
Created ROM Slot-1, Set it to active, Installed with the following:
AOSP Port GT-I9295 - Official 4.2.2 - I9295-PORT-GoogleEdition-V1.zip (worked for i537 despite saying otherwise, I still wouldn't flash stock ROM....)
MF3/MF1 Kernal Modules - jflteatt-active-MF3-modules.zip / jflteatt-active-MF1-modules.zip (in same downloads area)
LeJay's S4 Active Camera Patch - SGS4A_CamPatch.zip
Working Phone, Bluetooth, Wifi, Stock Camera App /w Flash (video-recording preview is low-res, but records normal)
Click to expand...
Click to collapse
Already had the MF3 AOSP up and running but the camera was the sticking point, just flashed that zip provided by LeJay and it's working - it's not the same as the stock GS4A camera (which I was getting pretty used to) but it does allow for photos and video presently so that's better than not having that ability in any respects.
Thanks, LeJay...
Yeah thanks for the camera fix. I'm wondering if I can grab the camera apk from stock and bring it over. Would love to have that aqua mode. Its one of those look what I can do kinda features. Oh and the reason we all got the active over the regular s4
Sent from my GT-I9295(AOSP GS4A) using xda app-developers app
Diablo2424 said:
Yeah thanks for the camera fix. I'm wondering if I can grab the camera apk from stock and bring it over. Would love to have that aqua mode. Its one of those look what I can do kinda features. Oh and the reason we all got the active over the regular s4
Sent from my GT-I9295(AOSP GS4A) using xda app-developers app
Click to expand...
Click to collapse
I doubt it since the camera app is built on Samsung's TouchWiz framework (much like you can't use their widgets on Nova Launcher and such).
Unless someone were to replicate what "aqua mode" does, you may just have to live without it, or find an app on the play store that allows button assignment.
Wow I've been busy with work and to see this on XDA WOW
Once again Hashcode has saved me from a locked boot loader. I used safestrap with my RAZR and now I'm running the Google edition it put my active into Beast Mode.
If you want to use the camera underwater just reboot into your stock system.
Sent from my GT-I9295 using XDA Premium 4 mobile app
mrmartin86 said:
I doubt it since the camera app is built on Samsung's TouchWiz framework (much like you can't use their widgets on Nova Launcher and such).
Unless someone were to replicate what "aqua mode" does, you may just have to live without it, or find an app on the play store that allows button assignment.
Click to expand...
Click to collapse
True.. Its not that big of a deal i was just curious. Thanks for the info!
dave5777 said:
Wow I've been busy with work and to see this on XDA WOW
Once again Hashcode has saved me from a locked boot loader. I used safestrap with my RAZR and now I'm running the Google edition it put my active into Beast Mode.
If you want to use the camera underwater just reboot into your stock system.
Sent from my GT-I9295 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Duh I can't believe I didn't think of that, haha. Problem solved. Although I will say I may not bother at this point. This AOSP ROM running on SS is so fast and smooth, I don't think I'll be going back to stock anytime soon heh
Sent from my ATT SGS 4 Active running AOSP
Only fresh flashed bootloader locked XT1058 AT&T - ROM LPAS23.12-21.7-1, and XT1060 VZW - ROM LPAS23.12-39.7-1 are supported!
See archive content for instructions. Time to install ~20 min. If you experience problems after Android boot, like not working buttons or quick settings, wipe cache + data partitions. Don't update SuperSU (disable auto updates), it won't work. Later I'll post complete debloated ROMs with fresh SuperSU version, and simplify instructions. Be informed also, that this method doesn't give you read-write rights like unlocked bootloader. You may read and write having root-rights, but only till a restart or shutdown occurs, and every change will be undo by the Qualcomm protection (like HTC' s=on).
At the moment patch includes:
SuperSU 2.65 Free
Xposed Framework v86 (installer, modules)
Busybox 1.25.0.YDS, path /system/xbin/busybox
Download
P.S. Install only on indicated above ROM versions, and it's obvious that you must have enough theory knowledge and practical experience to make use of 9008 patch, so I'm not responsible for any consequences, etc. Greets go to: CrashXXL (method inventor), Sabissimo (our former OP), and serg_gangubas (ROM guru).
==============================================================================================
31.07.2017 - Full ROM Patch for Bootloader Locked Moto X ATT/VZW/etc
Based on the same principle, and not depend on system partition content, so it suits any bootloader locked Moto X Gen1 ATT/VZW (possibly any model, besides 1049 RepW / 1055 US Cell), but takes about 4 hours to be done - prepare for that, 100% battery level only!
This full ROM patch includes:
SuperSU 2.82 Free
Xposed Framework v87 (installer, modules)
Busybox 1.26.2, path /system/xbin/busybox
ViperFX 2.5.0.5 - sorry needs polishing, removed now (
Gallery and Camera not depend on Moto services
Gboard instead AOSP Keyboard. If it eats too much RAM, see Simple Keyboard
GAPPSes updated. Use command like adb shell pm uninstall --user 0 com.blahblah.blah to block any unwanted app or service
ES File Explorer Free Edition (a clone, you can disable and install yours )
"Jedy" gesture
AdBlock support (effect lasts till the 1st reboot yet, I'll think about make it constant). Please, choose /data/hosts instead of /system/etc/hosts
ROM debloated, but not deodexed.
Download
Instruction
Be careful, phone will be WIPED then flashed in 9008 "brick" mode (CrashXXL idea). Before you start install Moto drivers, latest RSD Lite, and fully charge the battery.
1) Download and unpack zip on С: (or any), open Python27, launch RUN_path.bat (needs to be launched only single time), install driver QHSUSB_driver.exe, and launch file _Moto.X.BootLocked.*.exe (where * - is desired ROM).
2) Go into fastboot mode, execute RUN_blbroke.bat. Screen gets black, Device Manager in Windows finds "QHSUSB_DLOAD", and installs it as "Qualcomm HS-USB QDLoader 9008 (COM*)". If it doesn't install, google for Windows driver digital signature disable.
3) Now launch RUN_root.bat, and see that patching process took start.
4) A small patch *SPEAKERS.BOOST.exe (if exists) boosts both speakers' volume.
P.S. Please, don't flash anything extra into the phone. In case of trouble, all you need is inside this folder. Just make it work.
To make "Battery OK" in fastboot use fastboot_cyclecharge.bat
Completely drained out battery causing "USB input device" needs disassembly of the phone to charge externally.
In case Titanium Backup shows error "Batch backup interrupted: insufficient free storage space", delete default backup folder, and make a new:
Titanium Backup > Menu > Preferences > Backup folder location > Storage Provider > DocumentProvider storage > Show Internal Storage > Internal Storage > Select Internal Storage > Create the folder > Use the current folder. Done!
Notes for myself: Viper, force wipe, readme.txt, volume patch, Adblock, advanced debloat
Debloated, rooted, lightweight ROM - soon! )
PUBLISHED. Sorry, took long time.
As soon as I can actually get 5.1 flashed I'll try this.
Though I'm afraid I'll have to try to go to stock and use sunshine first, still have a locked BL.
But this is great, I didn't expect root so soon.
DownTheCross said:
As soon as I can actually get 5.1 flashed I'll try this.
Though I'm afraid I'll have to try to go to stock and use sunshine first, still have a locked BL.
But this is great, I didn't expect root so soon.
Click to expand...
Click to collapse
This method is working on locked BL.
DownTheCross said:
As soon as I can actually get 5.1 flashed I'll try this.
Though I'm afraid I'll have to try to go to stock and use sunshine first, still have a locked BL.
But this is great, I didn't expect root so soon.
Click to expand...
Click to collapse
Wait wait... If you can have now possibility to unlock bootloader - go for it immediately! You will have normal FULL root-rights (SuperSU 2.49). Don't install 5.1, if you plan to unlock, because Sunshine app (25$) works only on 4.4.2 Android.
This topic is to help those AT&T users that are boot locked forever (who missed out possibility to unlock on 4.4.2 by proceed to 5.1) to give them READ-ONLY root. Yes, it's limited, but anything at least.
s5610 said:
If you can have now possibility to unlock bootloader...
Click to expand...
Click to collapse
I guess anyone on 4.4.4 today. There is no possibility to use Sunshine anymore.
Anyway spasibo za method
Ahh, if I don't have to be BL unlocked that's great lol.
I haven't read too much into the 5.1 updates or sunshine for that matter.
I've been on krypton 1.4.1 since it was released, and I haven't been able to successfully upgrade to any 5.1 roms yet.
Works great!
Works great for me on Windows 10 RTM 64-bit! Thanks a ton, I was waiting for a post like this.
I only had 3 minor hiccups:
1. RSD Lite gave me an error about "getvar", so I had to go into flashfile.xml in the ROM zip and remove the line that said getvar
2. I had to reboot to disable driver signature enforcement twice for some reason because Windows Update
3. The run-root.bat got stuck on "Executing..." because I installed the wrong driver (the correct file is qcusb.inf when installed from device manager -> browse my computer for driver software -> let me pick from a list -> all devices -> have disk)
Otherwise, everything runs just as well as KitKat, including Xposed.
Hehe got to love step 9
System Write
How can we help in getting the system write to zero using the same method,because I have xt1058 model bootloader unlocked and I provide any file needed to disable the pesky system write...
How can we help in getting the system write to zero using the same method,because I have xt1058 model bootloader unlocked and I provide any file needed to disable the pesky system write...
Click to expand...
Click to collapse
First, never quote op. It takes way to much space and is redundant.
Second, to get write off we would need to some how either start a custom kernel some magical way or disable it via a kernel mod like htc guys did. Another way, which was done before was to burn the efuse but kernel has been patched since then.
Need some help, I did all steps until step 9. I installed the QHSUSB_DLOAD driver manually, and I can see 'Qualcomm HS-USB QDLoader 9008 (COM4)' showed in my Device Manager, but when I run 'RUN_Root.bat', I got this
c:\Python27>python qdloadRoot.py MPRG8960.bin -ptf root/partitions.txt
QDLoad utility version 1.2 (c) VBlack 2014
Found TTY port: com4
Sending MAGIC ...
QCOM fast download protocol targ:
Version: 7
Compatible version 2
Maximum block size 1024 (0x00000400)
Base address of Flash 0x00000000
Flash: eMMC
Window size: 30
Number of sectors: 128
First sector size: 2097152 (0x00200000)
Feature bits: 09
Sending SBL Reset...
Done
c:\Python27>pause
Press any key to continue . . .
Then I tried to run 'RUN_Root.bat' again, then I got
c:\Python27>python qdloadRoot.py MPRG8960.bin -ptf root/partitions.txt
QDLoad utility version 1.2 (c) VBlack 2014
Found TTY port: com4
Requesting Params...
Params:
Version: 8
Min version: 1
Max write size: 1536 (0x00000600)
Model: 144
Device size: Invalid or unrecognized Flash device, or Flash device progr
amming not supported by this implementation
Device type: Intel 28F400BX-TL or Intel 28F400BV-TL
Requesting SoftwareVersion...
Version: PBL_DloadVER2.0
Requesting SerialNumber...
Serial number: 00,00,48,03
Requesting HW Id...
HW Id: 00,00,48,03,e1,10,7e,00
Requesting PublicKey...
PublicKey: 39,c4,ee,3e,b5,be,eb,87,8e,2f,e3,b8,53,4d,14,6f,91,ca,fd,bb,94,2a,0d
,aa,d0,1e,b0,87,62,d4,b9,b8
Uploading file 'MPRG8960.bin' to addr 0x2a000000...
Executing...
Could not find Qualcomm device in Emergency download mode
Done, with errors!!!
c:\Python27>pause
Press any key to continue . . .
any suggestions? Thanks
jahrule said:
First, never quote op. It takes way to much space and is redundant.
Second, to get write off we would need to some how either start a custom kernel some magical way or disable it via a kernel mod like htc guys did. Another way, which was done before was to burn the efuse but kernel has been patched since then.
Click to expand...
Click to collapse
Ill put the files here
Fantastic!!! I was looking this. All the last week I was sleeping about 3 hours per day trying to root my phone.
----
I scream "Victory" before the process finish.
Damn! My phone reboot and stay in the android doll fallen screen.
DejanPet said:
Ill put the files here
Click to expand...
Click to collapse
What to do with these files?
Those files are needed by Jahrule
Sabissimo
Hello.
I did everything as instructed, but eventually got the screen "no command".
The only thing I did not flash rom - a month ago updated by an OTA to 5.1, thought it was not necessary.
Factory reset does not help.
Advise something.
In the end, everything worked, thank you))
It works
It works great! Thank you very much! ATT xt1058.
eze_cba17 said:
Damn! My phone reboot and stay in the android doll fallen screen.
Click to expand...
Click to collapse
Follow the OP instruction EXACTLY, no exceptions!
If you got your current 5.1 through AT&T OTA, it's not enough for root patching procedure. A full RSD 5.1 official SBF flash over is required.
Could someone please do a video on this. I'm having a little trouble.
Has anyone installed the Nougat update for the Asus Zenpad 10 Z300M?
Yes I do, what do you need to know?
I didn't know there was an update to Android 7 - I'm still hoping (probably in vain) for this tablet to be rooted.
fabfor said:
Yes I do, what do you need to know?
Click to expand...
Click to collapse
I was just wondering if there were any noticeable changes or any issues with it as of yet.
Thanks for the reply.
Is the update OTA or from a website?
odyseus said:
Is the update OTA or from a website?
Click to expand...
Click to collapse
OTA
---------- Post added at 14:19 ---------- Previous post was at 14:13 ----------
PeteSeiler2010 said:
I was just wondering if there were any noticeable changes or any issues with it as of yet.
Thanks for the reply.
Click to expand...
Click to collapse
Changes are those in the changelog. I haven't noticed any issues so far but multi user support isnt't there and I was hoping yes.
ASUS ZenPad 10 Android Nougat Changelog:
Update Google security patch
Remove redundant app shortcuts “Audio Wizard” “Splendid” “System update” and “Flashlight” from all apps menu
Remove ”PC Suite” (CD ROM)
Remove “Tap and hold to show menu” form Settings > ASUS customized settings > Touch key setting. Add “Tap and hold to activate Multi-window ” in Touch key setting
Quick Settings supports multiple pages , user can swipe left to right to see more quick settings if using more than 12. User can enter edit screen by tap the edit button on top right corner to determine which settings enabling or disabling
Default Tap and hold Recent apps key to activate Multi-window
Add “Game Genie”
ZenUI Keyboard added New Unicode code 9.0 emoji and skin tone.
The preloaded Holo Spiral, Bubbles, Black Hole, and Phase Beam live wallpapers are not compatible with Android N and will be removed after system update
Add bundled notifications switch. (Settings > Notification > Configure notifications.) When multiple notifications for a single app are received, they can be bundled together into a single group. This group can be expanded to see the individual messages
Add Lock screen wallpaper slideshow
Change wallpaper every time you wake up your device. And users can go to “Settings” -> “Lock screen” -> “Wallpaper slideshow settings” for setting
Update SMMI tool to SMMI_TEST_V5.1.74_CSC_L1L2
Support Unlock tool
Click to expand...
Click to collapse
Must be US update then as still running Android 6.x here in the UK
Odd .. haven't gotten it .. and I check every couple of days ..
It could be me, but it seems like my battery dies faster after having the update for a few days.
odyseus said:
Must be US update then as still running Android 6.x here in the UK
Click to expand...
Click to collapse
No, it's worldwide.
The official website have the link of the update, and you can apply it manually.
http://dlcdnet.asus.com/pub/ASUS/Ee...62.438207375.1494693050-1331990512.1494693046
Hello, pls can anybody help? I bough z300m from second hand, turn on it (not try log in to google) and on startup screen (language select) system ask me for update to nougat, i click OK, system updated, tablet restarted and i cant log into tablet (FRP).
I search for bypass z300m on nougat, but cant find it.
This procedure dont work for me (android 7.0)
So i need flash from fastboot, but i cant find flashtool for z300m (p00c), firmware i downloaded from official page.
Any solutions?
Thanks.
Edit. I cant turn on usb debugging in developer settings (system want log in for view all options in developer settings...)
Nougat
PeteSeiler2010 said:
Has anyone installed the Nougat update for the Asus Zenpad 10 Z300M?
Click to expand...
Click to collapse
I did the nougat OTA update yesterday,it took a few minutes to download,but it is working great !
macikcz said:
Hello, pls can anybody help? I bough z300m from second hand, turn on it (not try log in to google) and on startup screen (language select) system ask me for update to nougat, i click OK, system updated, tablet restarted and i cant log into tablet (FRP).
I search for bypass z300m on nougat, but cant find it.
This procedure dont work for me (android 7.0)
So i need flash from fastboot, but i cant find flashtool for z300m (p00c), firmware i downloaded from official page.
Any solutions?
Thanks.
Edit. I cant turn on usb debugging in developer settings (system want log in for view all options in developer settings...)
Click to expand...
Click to collapse
Bad news I'm afraid. You need the original login details used to setup the device when it was originally purchased other than that it's a long winded battle with ASUS to prove you didn't steal the device.
Good luck
After update the system reboots all the time when WiFi is ON.
If I turn OFF wifi - it works fine. No other solution...
root / multi-user
fabfor said:
OTA
---------- Post added at 14:19 ---------- Previous post was at 14:13 ----------
Changes are those in the changelog. I haven't noticed any issues so far but multi user support isnt't there and I was hoping yes.
Click to expand...
Click to collapse
There is a thread right after this listing when search for Z300M on XDA that claims TWRP and asus bootloader unlock tool (not necessary 2 get twrp) and was the reason I purchased this tablet. So far errors in everything in the OP with no responses and I hate to be paranoid but once I know, if not twice I have actuall run into "FAKE" threads on XDA in the 2-3 years being on here claiming root/twrp for a device with a small amount of chit chat, responses.... that was pure BS!
Anyhow, if you ever get root here is the fix for your multi-user issue, with es file explorer, or root explorer and editing the boot. file:
Enable Multi Window and Multi User Modes
If you have a rooted Marshmallow ROM (or Nougat), you can enable the 2 features above by editing the build.prop file found in /system/
For multi-window mode, change this entry in build.prop
ro.build.type=user
to -
ro.build.type=userdebug
To enable multi-user mode, add these 2 lines to the build.prop (anywhere, it doesn't matter)
fw.max_users=3
fw.show_multiuserui=1
Once you've made these changes, reboot the tablet.
To use multi-window mode, go to Settings, Developer options, and there will be a new menu item to switch this on or off.
To use multi-user, there will be a new option under Settings called Users.
If anyone seeing this has accomplished root on the Z300M 16GB wi-fi tablet, please let me know.....
thanks,
zach
ps of course, make sure you make a copy of the boot file to ext sd card or somewhere b4 just in case.... in the 15 times I have used this on 6.0, 7.0 lenovo & LG devices & 1 HTC... never had an issue BUT...
---------- Post added at 05:26 PM ---------- Previous post was at 05:19 PM ----------
odyseus said:
Must be US update then as still running Android 6.x here in the UK
Click to expand...
Click to collapse
Actually all of the updates for the Z300M taking it to 7.0 are for the WW SKU (world wide) tablets, as well one for Japan and 1 other.........
any sign of root?
Asking around since purchasing this tablet due to thread on here claiming twrp but its falling on its face and no response as of yet.....
zach
?????
coolbeans2016 said:
Anyhow, if you ever get root here is the fix for your multi-user issue, with es file explorer, or root explorer and editing the boot. file:
Click to expand...
Click to collapse
Thank you coolbeans2016, that's right the reason I am too desperately looking for a way to root: to apply that fix.
Btw, I really do not see the reason for Asus to disable a native function (multi-user) that is - to me - obvious for a tablet. (Maybe it eats resources? i.e. storage space)
problem is
fabfor said:
Thank you coolbeans2016, that's right the reason I am too desperately looking for a way to root: to apply that fix.
Btw, I really do not see the reason for Asus to disable a native function (multi-user) that is - to me - obvious for a tablet. (Maybe it eats resources? i.e. storage space)
Click to expand...
Click to collapse
Problem is the instructions for getting TWRP flashed or even just booted up on TWRP threaded for installation of SuperSU or Magisk is failing. I've been told I'm wrong and am just not reading or following the instructions correctly but on a VERY popular device there is NO ONE claiming $$PROFIT$$ on the thread! Even the ones claiming understanding of the thread are having complications but only have an average of 6 posts as jr users with no thanks feedback.... yet they have no questions regarding using the SP Flash Tool?!!!!! Strange to me!
I'm contacting the dev on the thread AGAIN to see if I can get a detailed set of instructions in JUST getting TWRP onto this tablet, or its useless to me......
He really thought I was calling his thread a false listing but straightened it out with him about the fact he references another such thread along the same lines for the Verizon Asus A380M, which EVERYONE knows has never been, probably never will be able to get a custome recovery, let alone root of any kind!!!!!!!!
Any info you come across, or if you have tried the thread I'm mentioning please let me know your errors encountered, any ideas how WE may be not taking the instructions correctly.
zach
Hi,
I couldn'tt find any update for Z300CL.
Does anyone know if such an update is available?
Could you post the link here?
Thanks a lot
I used usb ethernet dongle on android 6 and it worked , it showed ethernet icon instead wifi. But when on android 7 the dongle does not work, seems usb host function is disabled, I dont want to root my tabled is there any way to enable usb host support ?
Introduction
Few weeks ago, I got a Pixel 1 as my backup phone, when I try to connect it to the Microsoft Wireless Display Adapter, it couldn't find the Adapter.
I haven't used Android phones for a long time. In my mind, Android natively supports Miracast. After some searching, I was frightened to find that Google has removed Miracast from Android.
I was really disappointed because I often cast my Windows devices easily by using Miracast. My Projector has only two HDMI ports, one for HDMI cable, and one for Wireless Display Adapter. I can't add a Chromecast unless a HDMI switch is used.
One possible solution is to add a line "persist.debug.wfd.enable=1" in "build.prop" to enable WiFi-Display, but many people say that it doesn't work since Android N, the phone can discover WiFi-Displays but unable to cast.
Since Android framework is open source, I did some searching and found that some WiFi-Display related code still exists. Android 9 still keeps the WifiDisplayAdapter in DisplayManagerService, but removed WifiDisplay from MediaPlayerService, that's why we can discover WiFi-Displays but can't cast.
I recovered some code from AOSP history commits, fixed the build errors, and debugged on my Pixel, finally the Miracast can work on my Pixel.
If you also want Miracast to work on your Google phones, you can follow my steps, but first make sure your ROM is open source so that you can change and rebuild it.
If you have a Pixel 1 running the same version of system, you can simply replace some files in your system with the files I built.
If you have other Google phones or running different versions, you can apply my patch to AOSP, and build it by yourself. I have built the latest version for all Google Pixel phones, but I haven't tested except Pixel 1.
If your ROM is not open source, I will no longer be able to help, since MediaPlayerService may have been changed by your ROM, you may can't replace it with the AOSP version.
Prerequisites
Pixel running Android 9.0.0 build number PQ1A.181205.002.A1 or PQ1A.190105.004.
Bootloader unlocked.
adb and fastboot tools and drivers are working for your device.
Note & Disclaimer
These steps will change files in your system, your Pixel should run the exact same version of system. Pushing files to different versions of system may cause unknown problems.
Please check carefully before running each command, a mistaken operation may result in unable to boot up, or destroy your data, or even damage your phone.
If you are not sure about what these steps are doing, but still want to go ahead, please backup your phone firstly, you may not be able to recover your phone to its original state.
I have only tested on Pixel 1 with build number PQ1A.181205.002.A1 and PQ1A.190105.004, for other phones or versions, you should build and test on your own.
Basic Steps
Flash the same version of factory image for your phone.
Download the prebuilt files from https://github.com/sbjbs/android-wfd-patch
Add this line into "build.prop", without it, we will not be able to enable WiFi-Display:
Code:
persist.debug.wfd.enable=1
Replace some files in system:
Code:
system/lib/libaudioflinger.so
system/lib64/libaudioflinger.so
system/lib/libserviceutility.so
system/lib64/libserviceutility.so
system/lib/libmedia.so
system/lib64/libmedia.so
system/lib/libwilhelm.so
system/lib64/libwilhelm.so
system/lib/libandroid_runtime.so
system/lib64/libandroid_runtime.so
system/lib/libstagefright.so
system/lib64/libstagefright.so
system/lib/libstagefright_wfd.so
system/lib64/libstagefright_wfd.so
system/lib/libmediaplayerservice.so
If you have magisk installed, you can refer to Phoenix Wright's post:
Phoenix Wright said:
using "setprop" to set that property once is enough, no need to touch build.prop; given it's a "persist" property it'll be permanent.
using magisk to overlay them on /system
Click to expand...
Click to collapse
Some extra steps that you may need
Remove dm-verity metadata of system.img
The dm-verity can prevent us from changing the system, and what's more it has a forward-error-correction(FEC) feature, which can detect and correct some corrupted data.
I spend a lot of time on attempting to change the build.prop but fail again and again, it just always correct the file, and I can't enable wifi-display.
I don't know how to disable it. Since the error-correcting info should be stored in the dm-verity metadata, I just removed the dm-verity metadata from the stock system.img, and flash the system.img.
I will list the steps to remove dm-verity metadata, but if you can disable dm-verity entirely, that should work too.
For phones that have a vbmeta partition (like Pixel 2), seems you can flash an special vbmeta.img to disable AVB. You can build the empty vbmeta image by this command, but I don't have a device to test if it works:
Code:
avbtool make_vbmeta_image --flag 2 --padding_size 4096 --output vbmeta.img
For Pixel 1, we need to remove dm-verity metadata that attached to system.img, first convert the sparse system.img to an ext4 image:
Code:
simg2img system.img system.ext4.img
read the block count to calculate the system size:
Code:
od -j 1028 -An -N4 -tu system.ext4.img
for Pixel 1, it should be 516099. You also can read it by a Hex Editor, e.g., WinHEX in Windows, read 4 bytes starting from 1028 bytes, as a little-endian hex value.
so the real system partition size is 516099 * 4096 = 2113941504 bytes.
we need to set the data to zero after that position. It's important to do this, since we need to overwrite the metadata in that area, rather than just truncate the size of system.img.
next get the ext4 image size, for Pixel PQ1A.181205.002.A1, it should be 2147483648.
so we need to write 2147483648 - 2113941504 = 33542144 bytes：
Code:
dd if=/dev/zero of=system.ext4.img seek=2113941504 count=33542144 oflag=seek_bytes iflag=count_bytes
we also can use some other tools to do this, e.g., WinHEX in Windows. Open the file in in-place mode, and jump to 2113941504, and select it as the begin, and jump to the end, and select as the end, and fill the selection with all zero.
after that, flash the changed system.ext4.img to Pixel:
Code:
fastboot flash system system.ext4.img
Test that you can boot up normally. If not, check what's wrong and fix it.
Temporary boot up by TWRP image
We don't have to install TWRP, but just use it to temporary boot up, so that we can mount the system partition for writing. If you have TWRP installed, you can just boot to TWRP.
Download TWRP image for pixel, just need the twrp.img, we won't install the zip file.
boot your device to bootloader:
Code:
adb reboot bootloader
and boot by the twrp.img
Code:
fastboot boot twrp.img
after TWRP booted up, just leave it there, no need to unlock or input password, we will change the system by adb.
Mount system partition for writing.
In the current version of TWRP for Pixel (twrp-3.2.3-1-sailfish.img), its fstab has an entry for system partition, we can directly mount it.
Code:
adb shell mount /system
run mount to check if successfully mounted:
Code:
adb shell mount
you should see an entry like this:
Code:
/dev/block/sda34 on /system type ext4 (rw,seclabel,relatime)
If not, you should stop now, and check the above steps.
after mount, we can use adb to push files into system.
Hey guy,
You helped me a lot to understand why it was not working with Pie. I tried several custom ROMs + the official Pie and it was not working.
There is Wireless display option in quick settings but it' doesn't find my Microsoft Wireless Display Adaptor also.
I so downgrade to Oreo. With Oreo it works without any issue. (there is an option "allow Wireless display" to tick and then your miracast dongle will appear).
You did a great job to make it working on Pie. Congratulations. I will anyway stay on Oreo. I think google will change that (many people already complained i guess).
Jean Michel
jean_michmich said:
Hey guy,
You helped me a lot to understand why it was not working with Pie. I tried several custom ROMs + the official Pie and it was not working.
There is Wireless display option in quick settings but it' doesn't find my Microsoft Wireless Display Adaptor also.
I so downgrade to Oreo. With Oreo it works without any issue. (there is an option "allow Wireless display" to tick and then your miracast dongle will appear).
You did a great job to make it working on Pie. Congratulations. I will anyway stay on Oreo. I think google will change that (many people already complained i guess).
Jean Michel
Click to expand...
Click to collapse
Thanks for your reply!
I have tested on Pie on my Pixel, I often play online games while cast is on, and didn't meet any problems last week.
I also hope that Google will support Miracast again in the future, but it seems unlikely in the near future.
Google has abandoned it since Android 6 (source: Wikipedia), and now they're deleting unused source code related to wifi-display.
I'm more worried about that there will be more build errors and potential issues when we try to enable it for future Android versions.
sbjbs said:
Thanks for your reply!
I have tested on Pie on my Pixel, I often play online games while cast is on, and didn't meet any problems last week.
I also hope that Google will support Miracast again in the future, but it seems unlikely in the near future.
Google has abandoned it since Android 6 (source: Wikipedia), and now they're deleting unused source code related to wifi-display.
I'm more worried about that there will be more build errors and potential issues when we try to enable it for future Android versions.
Click to expand...
Click to collapse
OK it's getting more clear. You are right. Wikipedia says : "but support was dropped with Android 6.0 Marshmallow in 2015 in favor of Google's own proprietary Google Cast protocol.[15] Some manufacturers of Android devices step in and support Miracast through their software"
I'm not an "official android ROM" user.
I always use Pixel Dust custom ROM. For this custom ROM, Miracast was supported for Oreo but not for Pie (not yet).
jean_michmich said:
OK it's getting more clear. You are right. Wikipedia says : "but support was dropped with Android 6.0 Marshmallow in 2015 in favor of Google's own proprietary Google Cast protocol.[15] Some manufacturers of Android devices step in and support Miracast through their software"
I'm not an "official android ROM" user.
I always use Pixel Dust custom ROM. For this custom ROM, Miracast was supported for Oreo but not for Pie (not yet).
Click to expand...
Click to collapse
I used to be a ‘latest official ROM’ user
For custom ROMs, since they may have changed the framework, we can't replace files with AOSP version, but as long as they're open source, we can try to contribute to it.
Adding Miracast support in Android is not difficult, and many manufactures have their own support.
I hope your custom ROM will support Miracast for Pie in the near future.
Tested on Pixel 2 XL and working (for what it's worth, using "setprop" to set that property once is enough, no need to touch build.prop; given it's a "persist" property it'll be permanent). I built the .so files on my local aosp tree and I'm using magisk to overlay them on /system.
Hi @sbjbs
If I understand you right then you have patched the AOSP codebase. Would you mind sharing the repositories/commits on your GitHub? That would be highly appreciated. :good:
Regards
spezi
Sent from my Pixel 3 using XDA Labs
spezi77 said:
Hi @sbjbs
If I understand you right then you have patched the AOSP codebase. Would you mind sharing the repositories/commits on your GitHub? That would be highly appreciated. :good:
Regards
spezi
Sent from my Pixel 3 using XDA Labs
Click to expand...
Click to collapse
There's a link in the OP: https://github.com/sbjbs/android-wfd-patch/tree/master/patches/android-9.0.0
Phoenix Wright said:
Tested on Pixel 2 XL and working (for what it's worth, using "setprop" to set that property once is enough, no need to touch build.prop; given it's a "persist" property it'll be permanent). I built the .so files on my local aosp tree and I'm using magisk to overlay them on /system.
Click to expand...
Click to collapse
Great to hear that!
You method is simpler and more elegant, that's awesome!
Phoenix Wright said:
Tested on Pixel 2 XL and working (for what it's worth, using "setprop" to set that property once is enough, no need to touch build.prop; given it's a "persist" property it'll be permanent). I built the .so files on my local aosp tree and I'm using magisk to overlay them on /system.
Click to expand...
Click to collapse
Can you elaborate how you did use "magisk to overlay them on /system"?
I pushed them using adb as mentioned on github but it is stuck at Google splash screen. I've taimen BTW and am on Pixeldust ROM. It booted while writing this post but the screen was not responding to touch.
Nitin
nitin.chobhe said:
Can you elaborate how you did use "magisk to overlay them on /system"?
I pushed them using adb as mentioned on github but it is stuck at Google splash screen. I've taimen BTW and am on Pixeldust ROM. It booted while writing this post but the screen was not responding to touch.
Nitin
Click to expand...
Click to collapse
I made a module with the .so files I compiled: https://workupload.com/file/pd4EUBdw
Note that I can't vouch for this to work on your ROM, it works on taimen on stock 9.0 with January security patches though.
nitin.chobhe said:
Can you elaborate how you did use "magisk to overlay them on /system"?
I pushed them using adb as mentioned on github but it is stuck at Google splash screen. I've taimen BTW and am on Pixeldust ROM. It booted while writing this post but the screen was not responding to touch.
Nitin
Click to expand...
Click to collapse
Did you build the so files for your ROM from source? the patch has changed the interface of IMediaPlayerService, if anything else in your ROM is using IMediaPlayerService.h, you'd better rebuild and replace them.
that's why I uploaded the libwilhelm.so and libandroid_runtime.so, even though I didn't change the source code of them.
Phoenix Wright said:
I made a module with the .so files I compiled: https://workupload.com/file/pd4EUBdw
Note that I can't vouch for this to work on your ROM, it works on taimen on stock 9.0 with January security patches though.
Click to expand...
Click to collapse
Thanks!
sbjbs said:
Did you build the so files for your ROM from source? the patch has changed the interface of IMediaPlayerService, if anything else in your ROM is using IMediaPlayerService.h, you'd better rebuild and replace them.
that's why I uploaded the libwilhelm.so and libandroid_runtime.so, even though I didn't change the source code of them.
Click to expand...
Click to collapse
I tried building with my ROM but I got build errors related to OMX.h, I need to find a solution for them. Thanks anyways!
Nitin
Someone tries on Pixel 3? Thanks
It works perfectly ! I used the prebuilt files on the march build.
Do you know if we can force the 16/9 ratio ?
Thanks
edit : I will try with second screens !
this works a treat on my Pixel 3 XL (Stock Pie) just overlayed the files from Phoenix Wright using magisk and it works now....sweet thanks, now just need to figure out how to fool sky sports app into letting me cast.....
marshyrob said:
this works a treat on my Pixel 3 XL (Stock Pie) just overlayed the files from Phoenix Wright using magisk and it works now....sweet thanks, now just need to figure out how to fool sky sports app into letting me cast.....
Click to expand...
Click to collapse
Can you explain more how did you do?
Did you just flash the zip from Phoenix Wright in Magisk?
EMJI79 said:
Can you explain more how did you do?
Did you just flash the zip from Phoenix Wright in Magisk?
Click to expand...
Click to collapse
Yes just copied the .zip file from Phoenix Wright's post to my device then used the module install option in Magisk like if you are installing a module found in Magisk (use the plus sign to add your own .zip file instead and browse to the file you just saved) then reboot. Then i went to the cast option in settings - connected devices - connection preferences, there i could tick in the top right corner under the 3 dots "enable wireless display" and it showed my Panasonic TV, chose connected and boom it connected. Needed to enable the mirroring option on my Panasonic but this is a TV setting nothing to do with the phone, you might need to do a similar step based on your TV as they need to be able to see each other.
marshyrob said:
Yes just copied the .zip file from Phoenix Wright's post to my device then used the module install option in Magisk like if you are installing a module found in Magisk (use the plus sign to add your own .zip file instead and browse to the file you just saved) then reboot. Then i went to the cast option in settings - connected devices - connection preferences, there i could tick in the top right corner under the 3 dots "enable wireless display" and it showed my Panasonic TV, chose connected and boom it connected. Needed to enable the mirroring option on my Panasonic but this is a TV setting nothing to do with the phone, you might need to do a similar step based on your TV as they need to be able to see each other.
Click to expand...
Click to collapse
It did work today with my Sony television.
Thanks!
OMG!!! You made my week. Few hiccups tho....
Can anyone else confirm that Hulu and HBO go and Amazon prime . YouTube works.
Hulu and amazon I can log on but when it plays all you get is audio. Haven't tried Netflix I don't sub them.
HBO go as soon as I try to play a video it says this video cannot be played. If I disable the mirror it plays perfectly. Same thing with Hulu and prime. Disable the mirror an it works perfectly on my phone.
********** ANNOUNCEMENT - Beta Enrollment without Banner (OPEN NOW - Nov 16,17) - Read More Here
INTRODUCTION - Hello all. Now Samsung wants us to go to Members app and keep looking for banner to sign up for Android 11, One UI 3 Beta . It went live October 27th, 10:20 PM EST, As fate would have it, i went to sleep early, i missed it and the banner refused to show up for me in the morning. Download was only showing up for people with unlocked variants on ATID firmware.
DISCLAIMER / NOTICE - Flashing is always risky. I am not responsible for anything that may happen to your device including but not limited to it turning against you, making you its slave and sucking you into the Matrix.
This post is a collection of wisdom, research and hard work of many people over many years across many forums and not just XDA. I will try to credit and link to their original posts.
TIP -Keep in Notice -This SHALL NOT Factory Reset Your Device or Format Data, it is still a good idea to Take Back Up - Just a Suggestion - Always have a latest Back Up
******** UPDATE - It seems ATT devices are getting wiped now if its CSC or the Sim remains to be tested.
i don't have ATT hence cant verify but in case you have an Unlocked device (N986U1) with ATT sim, then, removing sim and Changing the CSC to XAA/XAA/XAA before sideloading Beta is advisable.
PROBLEM STATEMENT - Missed the One UI 3.0, Android 11, Beta Sign up Banner in Members app or got the banner but didn't get the download and I really want it NOW.
Not sure if you want it now? - Find the BETA CHANGELOG HERE
GRAB YOURSELF A COFFEE / DRINK, because depending on where you at and how fast you/your internet speeds/your Machine is this may take anywhere between 7 to 45 MinsSOLUTION -
1. Pre-Requisites - Make sure Following Conditions are met before you start
You need a PC/Laptop along with your phone and USB Cable.
You need ADB installed, you can use ADB on Linux too - NOTE If your ADB Tools are not working, download my ADB Folder called platform-tools. Then extract it somewhere easy to remember/ find, like desktop
Remember the Location of the folder where you have ADB installed / Location of platform-tools- This is the location containing adb.exe file.
You may or may not need ADB/USB Drivers if any errors in ADB please Download Drivers from here and Install on your PC.
This following one step is relevant Only for flashing Beta 1
Use Odin to Flash Unlocked (SM-N986U1) ATID Firmware if you are not on that. Refer this thread to get your Firmware.
For changing Firmware from N986U to N986U1 and / or GUIDE TO FLASHING USING ODIN Refer This thread
______________________________________________________________________________________________________________________________________________________________
2. Now Download the relevant Beta File that you intend to flash - note that to Sideload Beta 2 you need to be on Beta 1 first. Mandotory Sequence = Beta 1>>Beta 2>>Beta 3 There is no skipping versions possible here.
BETA 1 (ZTGJ) Get the Beta1.zip file from here Thanks to @thatotherguy.. for the original zip.
BETA 2 (ZTK1) Get the Beta2.zip file from here
BETA 3 (ZTK9) Get the Beta3.zip file from here
______________________________________________________________________________________________________________________________________________________________
*************** Apply Update from SD card failed for me (Feel free to try that ) but here we will be using ADB Sideload Feature in Stock Recovery*************
HOW TO - Using ADB Sideload - Windows -The Process is Similar for Linux too
1. Copy the downloaded zip file to the ADB Folder (From Pre-Requisite step). ADB Folder is the folder containing ADB.exe it might be named differently for you (The one i have posted is called platform-tools)
2. Open Command Prompt Window as Admin.
3. Type in
Code:
cd Copy-paste the location of your ADB folder here
4. Connect the phone to the PC using USB Cable and Unlock it. Go to Developer Options and Switch on USB Debugging.
To turn on developer options go to Settings>>About Phone>>Software Information>> Then tap the build number 7 times - Developer options will appear at the bottom of Settings Menu
5. On your PC Type in Command Prompt
Code:
adb devices
6. Give Permission that appears on your phone and PC - I check the box Always Allow, you should do the same.
7. Now type the following and the phone will reboot to recovery.
Code:
adb reboot recovery
8. Once you see recovery on your phone Use Volume Keys to scroll down to Apply Update from ADB and press Power Button.
9. Now on your PC, Type the following in Command Prompt; this is just to be sure, it should show the device name with Sideload next to it.
Code:
adb devices
10. Type
Code:
adb sideload Beta1.zip
For Beta 2 use adb sideload beta2.zip Similarly For Beta 3 use adb sideload beta3.zip. Use whatever you have named the zip file. Most people use update.zip. The commands here are for the attached files in this post and their naming convention.
11. Wait for it to finish and Done
2nd (Second) BETA Is Out- How To Do this if you are not able to Enroll for Beta and or don't see update to download even after Enrolling
Second Beta should be flashed After Beta 1. Second Beta (ZTK1) can not be flashed unless you have Beta 1 (ZTJG).
To flash follow the same instructions as above only this time the prerequisite is you have to be on the 1st Beta. Download the 2nd Beta (ZTK1) Zip File to flash Here Thanks to @hayabusa1300cc for the FOTA Link.
3rd (Third) BETA Is Out- Nov 16, 2020 Do this if you are not able to Enroll for Beta and or don't see update to download even after Enrolling
Third Beta should be flashed After Beta 1>>Beta 2. Third Beta (ZTK9) can not be flashed unless you have Second Beta (ZTK1). Second Beta (ZTK1) can not be flashed unless you have Beta 1 (ZTJG).
To flash follow the same instructions as above only this time the prerequisite is you have to be on the 2nd Beta. Download the 3rd Beta (ZTK9) Zip File to flash Here
OPTIONAL THINGS TO DO POST UPDATE
If you want to enable RCS (In the Native SMS app) and Native Video calling (This feature is on Tmobile) have a look at this thread.
Check out this Guide Service Mode and CSC Guide/Enable LTE/5G Bands and Services/5G Low Band on U1 by @mellojosh
TROUBLESHOOTINGSome people might run into "cant read update.zip" error for that we need to make ADB Large address aware. Follow the Steps Here I use the Advanced mode as it shows the true false flags. - This wont happen if you use the ADB Tools provided by me above under the Pre-requisites section.
************** FOR FUTURE BETA OTA Questions / Bugs - Observations and some more info - Go Here ********Please dont ask questions without reading.
QUESTIONS, HELP & SUPPORT ?? - See if I am Online here on this Live Chat
If it helped HIT THAT THANKS BUTTON, what are you waiting for ? Cheers !!
Suggest you rename the title for which device it's for as it's not for every snapdragon (right?)
I get "adb: failed to read command: No error"
ekerbuddyeker said:
Suggest you rename the title for which device it's for as it's not for every snapdragon (right?)
Click to expand...
Click to collapse
I flashed on an Unlocked one so there is no way for me to tell if this can be flashed on N986U since so many people have flashed Unlocked firmware on the U devices using Odin (One confirmed guy flashed unlocked firmware on Verizon locked device and got the Beta banner) hence i think this will work for all Snapdragon devices. Give it a try and see. Just that before you try this make sure you are on ATID firmware.
d_ganggreen said:
I get "adb: failed to read command: No error"
Click to expand...
Click to collapse
Use a different USB Cable. A good quality one preferably. Also try changing USB port.
Can i install this on sm n 9860 version and does google pay and samsung pay beta work?
warriorvibhu said:
Use a different USB Cable. A good quality one preferably. Also try changing USB port.
Click to expand...
Click to collapse
Hmm, still getting same. Tried 3 cables including the one that came with the phone and both usb ports on my computer.
d_ganggreen said:
Hmm, still getting same. Tried 3 cables including the one that came with the phone and both usb ports on my computer.
Click to expand...
Click to collapse
Are you on ATID Firmware?
warriorvibhu said:
Are you on ATID Firmware?
Click to expand...
Click to collapse
I am, I odin flashed it a few weeks ago.
1gorelo said:
Can i install this on sm n 9860 version and does google pay and samsung pay beta work?
Click to expand...
Click to collapse
Too early in the morning to go out and test that. This is Beta and i have already encountered some bugs. So you have to be up for that.
Good Lock wont work, gesture navigation is buggy, you can not even apply wallpapers from the Galaxy Themes app.
Wallpaper Service on the other hand is greatly improved. Fingerprint sensor is much faster.
d_ganggreen said:
I am, I odin flashed it a few weeks ago.
Click to expand...
Click to collapse
My friend there are so many reasons why that error can happen. Sometimes you might have to change the ADB version. I am attaching the platform-tools i used. Extract this zip inside folder on desktop and try. If that doesnt work you might need to update ADb/Samsung drivers. Let us know if this works.
warriorvibhu said:
My friend there are so many reasons why that error can happen. Sometimes you might have to change the ADB version. I am attaching the platform-tools i used. Extract this zip inside folder on desktop and try. If that doesnt work you might need to update ADb/Samsung drivers. Let us know if this works.
Click to expand...
Click to collapse
Thank you! Whatever it was, that worked. I am able to get it running with your tools. I am running it now.
CHANGELOG - Android 11_OneUI 3 Beta
************ Notice: This changelog is compiled from various different resources online, verification of these features rests with the users **********
Code:
[COLOR="SeaGreen"][CENTER]BETA CHANGELOG[/CENTER][/COLOR]
[B]Home screen[/B]
– Touch and hold an app to add an associated widget
– Turn the screen off by double-tapping on an empty are of the Home screen. You can turn this on in Settings > Advanced features > Motion and gestures.
Lock screen
– Dynamic Lock screen now has more categories, and you can select more than one.
– Lock screen widgets are improved.
[B]Contacts, Phone and Call Background[/B]
– Added the ability to edit multiple linked contacts at one time.
– Added an option to help you quickly delete duplicate contacts.
– Enhanced the search experience.
– Extended the storage period of the Trash bin from 15 to 30 days.
– Added the ability to customize the call screen with your own pictures and videos.
[B]Messages[/B]
– Created a Trash bin to store recently deleted messages.
– Call & Text on other devices
– Added the ability to turn Call & text on other devices on or off with Bixby Routines.
[B]Calendar[/B]
– Events with the same start time are now shown together in month and agenda view.
– Reorganized options for adding and editing events.
– Improved layout for full screen alerts.
[B]Reminder[/B]
– Improved layout for full screen alerts
[B]Camera[/B]
– Improved auto-focus and auto exposure functionality and usability.
– Improved stabilization when taking pictures of the moon at high zoom levels.
[B]Photo editor[/B]
– Added the ability to revert edited pictures back to their original versions.
[B]Bixby Routine[/B]
– Grouped preset routines help you get started quickly and learn how to build your own routines easily.
– You can now see what actions are reversed when a routine ends.
– New conditions have been added, such as a specific start time, the disconnection of a Bluetooth device or Wi-Fi network, a call from a specific number, and more.
– New actions have been added, including talking to Bixby and accessibility actions.
– You can add a customized icon for each routine and add routines to the Lock screen for quick access.
[B]Digital wellbeing and Parental controls[/B]
– Added trends to your weekly report. You can see how your usage has changed since the previous week and check your usage time for each feature.
– Added phone usage time while driving to the weekly report.
– Added a lock screen widget so you can check your screen time without unlocking your phone.
– Added separate profiles for personal and work modes so you can track your screen time separately.
[B]Internet[/B]
– Added ability to block websites from redirecting you when you tap the Back button.
– Added warnings and blocking options for websites that shot too many pop-ups or notifications.
– Rearranged menus to make things easier to find.
– Added several new add-ons, including one that translates websites.
– Added option hide the status bar for a more immersive browsing experience.
– Increased maximum number of open tabs to 99.
– Added ability to lock and reorder tabs.
– Improved design for tab bar which is now supported on all devices.
– Ended support for Samsung Internet edge panel.
[B]Quick panel[/B]
– See your conversations and media more conveniently in their own sections when you swipe down from the top of the screen.
[B]AOD[/B]
– Always On Display widgets are improved.
[B]Accessibility[/B]
– Get quick access to the most important accessibility settings during device setup.
– Get recommended accessibility features based on what you use.
– Set the Accessibility shortcut more easily in settings.
– Sound detectors now work with your SmartThings devices such as TVs and lights to give you more visible alerts when the doorbell rings or a baby is crying.
[B]Samsung Keyboard[/B]
– You can find the keyboard in settings more easily under General management in Settings, and the settings have been reorganized to put the most important ones first.
Samsung DeX
– You can now connect to supported TVs wirelessly.
– New touchpad multi-gestures let you change screen zoom and font size more easily.
Feel free to add anything else that you observe.
warriorvibhu said:
Wohooo Fingers Crossed. Did it finish ?
Click to expand...
Click to collapse
Yes it did, running 3.0 beta now!
warriorvibhu said:
I flashed on an Unlocked one so there is no way for me to tell if this can be flashed on N986U since so many people have flashed Unlocked firmware on the U devices using Odin (One confirmed guy flashed unlocked firmware on Verizon locked device and got the Beta banner) hence i think this will work for all Snapdragon devices. Give it a try and see. Just that before you try this make sure you are on ATID firmware.
Click to expand...
Click to collapse
I'm on n9860 which is a snapdragon. I'm not sure if it's the same. Anyone want to try?
My US unlocked stuck at 16% when sideloading? Is it normal?
jianansong said:
My US unlocked stuck at 16% when sideloading? Is it normal?
Click to expand...
Click to collapse
Since how long ?
Which step are you at?
warriorvibhu said:
Since how long ?
Which step are you at? (See Pics)
Click to expand...
Click to collapse
On my phone, it shows "Verifying updte package..."
On the adb, it shows serving update.zip 16%.
It has been there for at least 20 minutes... Do I need to cancel and restart?
I used the uploaded adb and the first link for update.zip.
jianansong said:
On my phone, it shows "Verifying updte package..."
On the adb, it shows serving update.zip 16%.
It has been there for at least 20 minutes... Do I need to cancel and restart?
I used the uploaded adb and the first link for update.zip.
Click to expand...
Click to collapse
Yes thats too long Cancel and restart, It took me 97.5 seconds to verify the package.
Your ADB is fine dont change that. For firmware you can try using the second link from google drive. do you meet the criteria Unlocked and on ATID ?
warriorvibhu said:
Yes thats too long. do you meet the criteria Unlocked and on ATID ?
Click to expand...
Click to collapse
Yes, mine is us unlocked and it's on ATID. Do you know how I could cancel it?
---------- Post added at 03:45 PM ---------- Previous post was at 03:43 PM ----------
jianansong said:
Yes, mine is us unlocked and it's on ATID. Do you know how I could cancel it?
Click to expand...
Click to collapse
At the command line, I clicked "control + C" and surprisingly the progress number starts moving again, and now I am at 53% and it's still going...