Hello people. After successful root and installing xposed module n-ify you still don't get a multi window feature. Though many of you must be familiar with it but those who ain't. This is just the right place.
Here's something new .... U can do it without root too.
Enable Multiwindow WITHOUT ROOT
Requirements:
1. Working adb and fastboot on PC
2. Notepad++ or anything to edit the build.prop
3. TWRP on your device
4. Cool Attitude
Let's begin.
(Note: The commands in command prompt are to be give without the Quotes)
1. Boot your Android device into TWRP recovery.
2. Select Mount and then select System from the list of partitions to mount the system partition and then go back.
3. Connect your device to the PC.
4. Open minimal adb and fastboot or just open command prompt if u have adb shell installed separately
5. Type command, "adb devices" and if adb is properly installed, your device will be listed.
Then type command,
"adb pull /system/build.prop"
The above command will download the build.prop file to your PC in the same directory where your command prompt is running from. (Tip: Make a copy of your build.prop)
6. Open the build.prop file on your PC using the Notepad++ program.
7. Find the line "ro.build.type=user" and change it to "ro.build.type=userdebug" and save the changes
8. Now again in command prompt, type the command
"adb push build.prop /system/"
9. Now set the correct permissions for the build.prop file with following commands (issue them one-by-one):
"adb shell"
"cd system"
"chmod 644 build.prop"
10. Now reboot your device.
11. Go to Developer options in settings and you'll see a "Multi-window mode" just toggle it on and voila.
Enable Multiwindow on Rooted device...!
Requirements:
1. Root access
2. Any root explorer (es explorer is very good and I'm using it in this tutorial)
Let's begin.
1. After rooting your Moto G4 plus, download and install any root explorer and grant it superuser access. (I'm using es explorer)
2. In the explorer, go to Device\ System\ Build.prop.
3. Copy the build.prop to any other location (incase you wish to revert this, this is kinda backup step)
4. Now again go to original build.prop (Device\ System\ Build.prop)
5. Open it with the es note editor (I'm using es explorer here)
6. Find the line "ro.build.type=user" and click on the 3-dot menu on top right side (es explorer) and click edit.
7. Now edit the line and change "user" to "userdebug" (without quotes)
8. Save it and Reboot your device.
9. Go to Developer options in settings and you'll see a "Multi-window mode" just toggle it on and voila.
You have the Working multi window. Screenshots attached.
[To get other Android Nougat features, just get working xposed on your device and install n-ify module. Activate it and there you are!]
Screenshots here,
https://drive.google.com/folderview?id=0Bya7b1JXXZycS2pHT3d4alhxaWc
A thanks would be really appreciated
Tested and it works
Added screenshot
{
"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"
}
It's an old trick. I know but it's really cool
Would this work on the regular G4? Noob question but I don't wanna mess up my phone.
NexusFan9219 said:
Would this work on the regular G4? Noob question but I don't wanna mess up my phone.
Click to expand...
Click to collapse
Yeah sure it would. Go ahead. Just make a copy of Build.prop. Incase u desire to revert it or Incase u edit something else in build.prop
If u are not rooted and still want to have multiwindow...... Then u can pull the build.prop via adb and edit it and then push it again into the system via adb.......
If u do not get it or want a detailed explanation then comment below..... I'll update the OP
cool_sid said:
If u are not rooted and still want to have multiwindow...... Then u can pull the build.prop via adb and edit it and then push it again into the system via adb.......
If u do not get it or want a detailed explanation then comment below..... I'll update the OP
Click to expand...
Click to collapse
Pl update process for non-root, dont think its a noob question..
sirtbhopal said:
Pl update process for non-root, dont think its a noob question..
Click to expand...
Click to collapse
OP has been updated with the Non Root method.
N buddy..... It's just question...... Never a noob or a silly question.....
U don't know guys..... Some simple questions teach lot to us.....
Just like I learned that I can edit system without root too just by mounting the system in twrp....
So guys now u can do this without even having root access on your device....
Multiwindow on Moto G4 Plus and that too without root.....
Rush it guys....
So I hear you can't do OTA updates with TWRP installed? Is there a way to do the non root method without TWRP? If not, is there a quick way to install TWRP, make the fix and then return to normal recovery? I can't see much in the way of guides?
Thanks
damonsmith666 said:
So I hear you can't do OTA updates with TWRP installed? Is there a way to do the non root method without TWRP? If not, is there a quick way to install TWRP, make the fix and then return to normal recovery? I can't see much in the way of guides?
Thanks
Click to expand...
Click to collapse
Use recovery switcher app from XDA..... It also is great to quickly switch recoveries....... Then u can easily switch between stock recovery n twrp
To apply ota..... Flash fire can also be used.... (Never used it though)
And u can modify system without root or a custom recovery at least...... Hope u can understand that......
Rest I'll see if there is any other possible way
cool_sid said:
Use recovery switcher app from XDA..... It also is great to quickly switch recoveries....... Then u can easily switch between stock recovery n twrp
To apply ota..... Flash fire can also be used.... (Never used it though)
And u can modify system without root or a custom recovery at least...... Hope u can understand that......
Rest I'll see if there is any other possible way
Click to expand...
Click to collapse
What he said, plus you can just boot TWRP instead of flashing it if you want to use features of TWRP without flashing it.
Tel864 said:
What he said, plus you can just boot TWRP instead of flashing it if you want to use features of TWRP without flashing it.
Click to expand...
Click to collapse
Yeah instead of giving command.
fastboot flash recovery twrp.img
U can use
fastboot boot twrp.img
I guess......
On my N5, with TWRP I can flash Google OTA files just fine. Maybe with TWRP for Moto G4 that can be possible...
Recently picked up this phone up, sucks there isn't much for the G4's compared to the Nexus/Pixel devices, even tho they basically run stock AOSP. But I have an Nexus 5 still too
Anyway, I tried out your little tip and it worked like a charm ?
Thanks for this!
My device = Moto G4 XT1625_retail_non-amazon_garbage lol
Thanx
Related
Hi Folks,
Today TheF3nix requested me how to root and speed up the LG P500 Optimus One.
The best way to make the phone faster is to delete system apps or equal to flash a new system. In this guide i want to show you how to root delete system apps and flash new systems.
Step1: Rooting
Windows/Linux
First download SuperOneClick. Unzip the file and open the setup(.exe)
Before continuing make sure USB-Debugging(Settings > Applications > Development > USB-Debugging) is activated/ticked.
Connect your Device via USB to the PC.
Go to the SuperOneClick window and press the "Root"-Button
Wait till the process is finished. Close all Dialogs(Test, Donate) on PC.
After all finished Reboot your Device. If you don't do that Root will not work.
If the reboot finished the Phone is rooted
aravindsagar said:
Anyway, Super One Click will not work if the phone is running on stock 2.3.3. To root that, goto adb shell (see the next paragraph), type "echo 1 > /data/local/lge_adb.conf" (without the quotes) and then go to Super One Click, select psneuter exploit, and then click root.
To setup adb in your computer, see this link: http://forum.xda-developers.com/showthread.php?t=1387527 After setting up adb succesfully, type adb shell in the command prompt to get into the asb shell
Click to expand...
Click to collapse
Mac/No PC
Download z4root to your phone/device and install it. Make sure Unknown Sources(Settings > Applications > Unknown Sources) is activated/ticked before install.
Before continuing make sure USB-Debugging(Settings > Applications > Development > USB-Debugging) is activated/ticked.
Open z4root and click "permanent-root"
Do not care if the screen becomes white. After one to two minutes you phone will reboot.
If the reboot finished the Phone is rooted
_________________________________________________________________________
Take a Eyebreak here
_________________________________________________________________________
Step: Removing System Apps
For this step we need Root Explorer or any other root filemanager.
If we have installed Root Explorer and launch it a popup will appear. In this popup rott explorer asks for root rights. Simple click allow, and root explorer is ready to work.
To delete system apps we go to system/app/ and there are the system apps.
To show how root explorer works we'll delete facebook for lg.
Now search for the apk. Long click on it and press delete. Press Ok and the file is deleted.
Or
Step: Installing Custom Rom
Search here at XDA for Roms. If you found a good download it to your SD-Card.
Install Clockworkmod Rom Manager from Google Playstore.
IOpen the App and allow Root Rights.
Press "Install Recovery" and choose "p500"
After the install is finished shut down
Now press Volume Down+Home+On to access recovery.
You can move between items with volume keys
Make a nandroid backup(Recovery > Backup/Restore > Backup) before you do anything with the recovery
If you've made a backup go to "Install zip from sd card" press home and choose "choose zip". Now go to your zip choose it with pressing "home". Follow the steps in the recovery.
Follow all other steps like clear data as its written in your roms thread.
Press "back" until you are at start.
If you're really sure you followed all relevant steps press reboot system now.
First Reboot take up to 5 minutes.
Here is another way to install recovery:
aravindsagar said:
Firstly, you need to download two files:
1. http://www.mediafire.com/?g6cgvutkqw4t4j6
2. http://www.mediafire.com/?7pkcte8gcyn9pet
Now, copy these two files and paste in the root of your SD card. Disable USB-MS, but keep the phone connected via the USB Cable, and make sure that USB debugging is enabled.
Then, go to adb shell, type su. Click allow in the phone if superuser request is coming (it didn't come for me, that's ok).
Now, type each of the following commands exactly as it is:
1. mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system
2. cat /sdcard/flash_image > /system/bin/flash_image
3. chmod 755 /system/bin/flash_image
4. mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak (if it gives error message here, simply proceed to the next step)
5. mount -o remount,ro -t yaffs2 /dev/block/mtdblock1 /system
6. flash_image recovery /sdcard/recovery-RA-GNM-thunderg-1.1.0.img
7. reboot recovery
The phone will reboot now.
To access the Custom Recovery, turn off the phone and then press Home+Vol Down+Power button to boot into the Custom Recovery.
If on booting into the recovery you get the following message at the bottom of the screen -
E: "Bad Boot Message"
Don't panic, its perfectly normal and you can proceed with what you want to do from the recovery.
I've been using this recovery till now, and has got absolutely no problems till now. It wipes and flashes everything well.
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"
}
Feel free to correct me if i did anything wrong.
If you want to know more about kernels go to this thread.
This took some time for writing so press thanks if this helped you.
Thanks:
- aravindsagar to correct me about 2.3.3 roms
Disclaimer:
I am not responsive if this bricks your device.
Reserved
Don't you think the post is kinda redundant? It's all explained in the stickies. But if this becomes useful, then by all means, carry on.
Anyway, Super One Click will not work if the phone is running on stock 2.3.3. To root that, goto adb shell (see the next paragraph), type "echo 1 > /data/local/lge_adb.conf" (without the quotes) and then go to Super One Click, select psneuter exploit, and then click root.
To setup adb in your computer, see this link: http://forum.xda-developers.com/showthread.php?t=1387527 After setting up adb succesfully, type adb shell in the command prompt to get into the asb shell.
---------- Post added at 08:17 PM ---------- Previous post was at 08:03 PM ----------
After trying to install CWM through ROM Manager, my phone did not boot. Finally I had to reflash stock firmware using KDZ. Then installed a recovery through ADB. If anyone needs detailed steps, just post a message, and I'll give the links.
deutron said:
Hi Folks,
Today TheF3nix requested me how to root and speed up the LG P500 Optimus One.
The best way to make the phone faster is to delete system apps or equal to flash a new system. In this guide i want to show you how to root delete system apps and flash new systems.
Step1: Rooting
Windows/Linux
First download SuperOneClick. Unzip the file and open the setup(.exe)
Before continuing make sure USB-Debugging(Settings > Applications > Development > USB-Debugging) is activated/ticked.
Connect your Device via USB to the PC.
Go to the SuperOneClick window and press the "Root"-Button
Wait till the process is finished. Close all Dialogs(Test, Donate) on PC.
After all finished Reboot your Device. If you don't do that Root will not work.
If the reboot finished the Phone is rooted
Mac/No PC
Download z4root to your phone/device and install it. Make sure Unknown Sources(Settings > Applications > Unknown Sources) is activated/ticked before install.
Before continuing make sure USB-Debugging(Settings > Applications > Development > USB-Debugging) is activated/ticked.
Open z4root and click "permanent-root"
Do not care if the screen becomes white. After one to two minutes you phone will reboot.
If the reboot finished the Phone is rooted
_________________________________________________________________________
Take a Eyebreak here
_________________________________________________________________________
Step: Removing System Apps
For this step we need Root Explorer or any other root filemanager.
If we have installed Root Explorer and launch it a popup will appear. In this popup rott explorer asks for root rights. Simple click allow, and root explorer is ready to work.
To delete system apps we go to system/app/ and there are the system apps.
To show how root explorer works we'll delete facebook for lg.
Now search for the apk. Long click on it and press delete. Press Ok and the file is deleted.
Or
Step: Installing Custom Rom
Search here at XDA for Roms. If you found a good download it to your SD-Card.
Install Clockworkmod Rom Manager from Google Playstore.
IOpen the App and allow Root Rights.
Press "Install Recovery" and choose "p500"
After the install is finished shut down
Now press Volume Down+Home+On to access recovery.
You can move between items with volume keys
Make a nandroid backup(Recovery > Backup/Restore > Backup) before you do anything with the recovery
If you've made a backup go to "Install zip from sd card" press home and choose "choose zip". Now go to your zip choose it with pressing "home". Follow the steps in the recovery.
Follow all other steps like clear data as its written in your roms thread.
Press "back" until you are at start.
If you're really sure you followed all relevant steps press reboot system now.
First Reboot take up to 5 minutes.
Fell free to correct me if i did anything wrong.
This took some time for writing so press thanks if this helped you.
Disclaimer:
I am not responsive if this bricks your device.
Click to expand...
Click to collapse
Hi! you can link my guide also for newbies flashning kernels and basically knowledge about it. http://forum.xda-developers.com/showthread.php?t=1721781
aravindsagar said:
[/COLOR]After trying to install CWM through ROM Manager, my phone did not boot. Finally I had to reflash stock firmware using KDZ. Then installed a recovery through ADB. If anyone needs detailed steps, just post a message, and I'll give the links.
Click to expand...
Click to collapse
I did all the steps with my friend and it worked.
good
Thanks,It works great.
Thanks,It works great. :victory::victory:
I`ve updated the complete guide by changing the way you have to do these things and making a Video out of it. Thanks [NUT] .
Files:
http://forum.xda-developers.com/showthread.php?t=1538053...
http://nut.xperia-files.com/
Steps:
Enable DEV. Options and USB-Debugging, PC Companion must be installed AND CLOSED.
Download SuperSU and place it into your internal storage
Download ZU-lockeddualrecovery2.7.154 INSTALLER here, extract it and run Installer.bat.
Use option 3 and follow the instructions
Device will reboot, make shure your device goes into Recovery by pressing vol. up.
In recovery flash SuperSU.zip
Reboot and you're done
Enjoy root
IMPORTANT INFORMATION:
Busybox is already preinstalled, don`t override it! The APK from the Play Store is useable but don''t tap on install or uninstall, this can result in trouble.
Point 1. You write about downloading TabZ-lockdualrec - why? You have been tested on C6833, it is ZU. Why not to download ZU-lockdualrec and use it? Recovery for ZU is broken or som? Version for TabZ and ZU are the same, have the same build number… confused
FRM300 said:
Point 1. You write about downloading TabZ-lockdualrec - why? You have been tested on C6833, it is ZU. Why not to download ZU-lockdualrec and use it? Recovery for ZU is broken or som? Version for TabZ and ZU are the same, have the same build number… confused
Click to expand...
Click to collapse
this should also work on non C6833 Z Ultras. The. point is i only have the C6833 to test it and the tabz one doesnt need root to work while phils recovery also works for the Z Ultra.
so the TabZ Recovery Installer gives you only a temporary root on 4.4.4 and installs the recovery, which means after reboot the Root is gone (enugh for installing Recovery). so you need to Root it again permamently via the easy Root tool after rebooting and install SuperSU directly after it via Recovery, so that not every app can have root Acess whithout asking you.
using this order all works perfectly.
update to 4.4.4
enable usb debugging
run easyroot bat
reboot
install supersu from play (and update binary when prompted)
run ZU Dual recovery installer bat (from same @[NUT] dl page)
done.. easyroot and supersu (via play) before recovery is a neater option and then no supersu flash is required (plus you have supersu so can grant adb shell access when asked during the recovery flash). You then choose method 1 instead of 3 when flashing recovery ("already rooted with supersu" option instead of the "about to root with towelroot" option).
cheers..
iBuzman said:
using this order all works perfectly.
update to 4.4.4
enable usb debugging
run easyroot bat
reboot
install supersu from play (and update binary when prompted)
run ZU Dual recovery installer bat (from same @[NUT] dl page)
done.. easyroot and supersu (via play) before recovery is a neater option and then no supersu flash is required (plus you have supersu so can grant adb shell access when asked during the recovery flash). You then choose method 1 instead of 3 when flashing recovery ("already rooted with supersu" option instead of the "about to root with towelroot" option).
cheers..
Click to expand...
Click to collapse
Or you install XZDR with option 3 in the installer menu and have @Chainfire's latest SuperSU flashable ready on your sdcard/internal storage before you do. Then you can flash it the instant you enter recovery for the first time and be done with it
[NUT] said:
Or you install XZDR with option 3 in the installer menu and have @Chainfire's latest SuperSU flashable ready on your sdcard/internal storage before you do. Then you can flash it the instant you enter recovery for the first time and be done with it
Click to expand...
Click to collapse
agreed, tested it right now. i`ll change my post, ty.
changes done:
-removed old guide
-completly changed the steps for rooting (old one was working, but this one includes recoverys that are made for ZU)
-new steps are now described in a Video
Supersu 2.01 from market don't update su binary, after dual recovery I prefer flash the supersu update zip from recovery
@Lightbird I see there is a ZU-lockeddualrecovery2.7.141-BETA.installer.zip. Is this newer and should I use it instead of 2.7.128 ?
adfurgerson said:
@Lightbird I see there is a ZU-lockeddualrecovery2.7.141-BETA.installer.zip. Is this newer and should I use it instead of 2.7.128 ?
Click to expand...
Click to collapse
you can try it, the .132 stucked in Towelroot, thats why you should use .128 instead. However if this one stucks in Towelroot, too and you want to have the newest Version you simply can flash the flashable.zip version after rooting whith the .128.
Lightbird said:
you can try it, the .132 stucked in Towelroot, thats why you should use .128 instead. However if this one stucks in Towelroot, too and you want to have the newest Version you simply can flash the flashable.zip version
Click to expand...
Click to collapse
@Lightbird just an update, I have a c6806 and on .128 it said unsupported when selecting make it rain. It worked fine with .141 though.
adfurgerson said:
@Lightbird just an update, I have a c6806 and on .128 it said unsupported when selecting make it rain. It worked fine with .141 though.
Click to expand...
Click to collapse
thanks for the reply
@[NUT] is working on a new dual recovery version, 141 is missing philz. 132 is currently my preferred version https://docs.google.com/file/d/0B0uD0ZLDjONjZ0dKck00OUdBdWM/edit?usp=docslist_api
Please help me
Hello, I tryed to root my xperia z ultra with the tutorial maked by lightbird and towelroot tells me : your device is not already supported.
Please help me really want to root my ZU!:crying:
Salutations
dual recovery updated to 142 http://forum.xda-developers.com/showthread.php?p=53935287
Lightbird said:
I`ve updated the complete guide by changing the way you have to do these things and making a Video out of it. Thanks [NUT] .
Files:
http://forum.xda-developers.com/showthread.php?t=1538053...
http://nut.xperia-files.com/
Steps:
Enable DEV. Options and USB-Debugging
Download SuperSU and place it into your internal storage
Download ZU-lockeddualrecovery2.7.128 INSTALLER, extract it and run Installer.bat
Use option 3 and follow the instructions
Device will reboot, make shure your device goes into Recovery by pressing vol. up.
In recovery flash SuperSU.zip
Reboot and you're done
Enjoy root
Click to expand...
Click to collapse
spent 10days to root and flash recovey ,your illustration helped ,cheers
I cant run install bat file. Please see below error message. Did i.missed something?
{
"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"
}
Thanks in advance!
zaxharu said:
I cant run install bat file. Please see below error message. Did i.missed something?
Thanks in advance!
Click to expand...
Click to collapse
This message appears if you didn`t extract the files bevore using the .bat file ^^. Try again after extracting the Files in a seperate folder :good:.
If this doesn`t work try to run this as an Administrator (rightklick - run as Admin) (maybe your permission settings block the script loading other files). If you cant run it directly run cmd as admin and navigate to it:
Cd.. = directory up
Cd (folder) = navigate into (folder)
Dir = shows the folders and files
ZU-lockeddualrecovery2.7.145-BETA.installer.zip
successed
Confirmed that .145 is working, no bugs detected.
Changes to Guide done:
Upgraded Version to .145
Hi guys, I'm here to learn something about Android Security System.
I have this Sapphire TV BOX
model: DWI259S / UIW4020ETI / UIW4020ETI2 (Sapphire)
SoC: Broadcom BCM7271
The goal of this post is to understand how I can gain root access on this device
I know how to turn it in recovery mode .
if you are interested you can read this Reddit post from ams_sharif
"You can boot to recovery by switching the unit off ( the black button in the back), then while holding the power button (the one on the side, next to the pair button) turn the set top box on until the recovery shows up."
This is what I see.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I tried to flash an update.zip in order to see if I can execute command through any script, but the verification of the signature fails.
I tried to click on "Apply update from USB" (that is adb sideload) , but connecting the tv box on the pc nothing happen, no device found neither with "adb devices"
I tried also to click on "Reboot to bootloader" but "fastboot devices" command return nod devices connected.
My idea was to read the recovery image from fastboot extract it and try to compile my own TWRP
Do you have any suggestions to guide me in the right way?
@element14
When you enter
Code:
adb devices
and don't see an entry listed under the “List of devices” section, then your device isn't connected to PC.
Same is case when you enter
Code:
fastboot devices
Recovery option "Apply update from USB" isn't equal to "adb sideload". This option assumes the Update.Zip you want to flash is located on USB-device connected with your TV box.
With regards to rooting your TV box you can try to flash Chainfire's SuperSu Pro.
BTW: TWRP isn't a recovery image you compile in order to flash, it's merely a touch-enabled replacement for device's Stock Recovery menu as shown by you
Example screenshot:
jwoegerbauer said:
@element14
When you enter
Code:
adb devices
and don't see an entry listed under the “List of devices” section, then your device isn't connected to PC.
Same is case when you enter
Code:
fastboot devices
Recovery option "Apply update from USB" isn't equal to "adb sideload". This option assumes the Update.Zip you want to flash is located on USB-device connected with your TV box.
Click to expand...
Click to collapse
I tried to flash a custom script that use the
Code:
u_print()
function , but the signature verification fails i get an
Code:
errorr:21
jwoegerbauer said:
With regards to rooting your TV box you can try to flash Chainfire's SuperSu Pro[/url].
Click to expand...
Click to collapse
Are you sure that I can flash an unsigned zip like superSu , with a stock recovery and locked bootloader ?
jwoegerbauer said:
BTW: TWRP isn't a recovery image you compile in order to flash, it's merely a touch-enabled replacement for device's Stock Recovery menu as shown by you
Click to expand...
Click to collapse
The TWRP is an open source project , all the source code is avaiable. But to have it works , you need the original kernel .
I tought , If I can unlock the bootloader I can read the image of the recvoery.img and from it extarct the kernel
Thanks for your answer.
@ element14
did you manage to make the device usebale?
Hello, i am also interested to reset\flash this device but I couldn't find any useful guide, did you manage to root it or flash it, I want to use it as android STB.
As long as you can establish an USB-connection ( read: ADB connection ) then you can root any device's Android OS, otherwise NOT.
Any updates on this topic? It would be great to know if someone was able to root it.
If this is the etisalat version of this box I have gotten APKs to work on it.
xilogofficial said:
If this is the etisalat version of this box I have gotten APKs to work on it.
Click to expand...
Click to collapse
What apk exactly?what you can do with this apk? And how you installed?
element14 said:
What apk exactly?what you can do with this apk? And how you installed?
Click to expand...
Click to collapse
I think it lets you install any APK on the device. Check https://emiratestel.github.io/website
There is only one port. Is there any other way? And how can i play videos from usb
xilogofficial said:
I think it lets you install any APK on the device. My method:
Going to apps list:
- insert usb
- click browse
- go up to internal storage, press ok, click Apps
part 1
- go to apps list, keep usb inserted
- scroll to Files, click it, click open
- if it opens skip to part 2
- else it will crash and show the first time boot
- go to apps list again while keeping usb inserted
- open files again
part 2
- connect a mouse to other USB port, navigate into the USB and into where you placed your APKs
- double click the apk to install it
- on first time install, it will show an error about unknown sources
- click settings on the prompt
- enable all sources shown
- continue installing the app
Click to expand...
Click to collapse
There is only one usb port. Is there any other way? And how can i play videos from usb
there's another on the bottom, or use a USB hub.
you can't play videos from USB without installing third party apps.
xilogofficial said:
If this is the etisalat version of this box I have gotten APKs to work on it.
Click to expand...
Click to collapse
Good Day! Appreciate your support . Dear Exactly Etisalat TV box model: DWI259S, but it is locked on Etisalat home page with their logo as I don't have Etisalat subscription any more, in that situation how possible to browse an APK file as you said in below steps? 2nd thing there is no standard Firmware available by Manufacturer (Technicolor), Please make a video or at least solve with help of photos and help us close this topic. Till date solution is not yet provided, Please help, Thanks and appreciate your support
.
element14 said:
Hi guys, I'm here to learn something about Android Security System.
I have this Sapphire TV BOX
model: DWI259S / UIW4020ETI / UIW4020ETI2 (Sapphire)
SoC: Broadcom BCM7271
The goal of this post is to understand how I can gain root access on this device
I know how to turn it in recovery mode .
if you are interested you can read this Reddit post from ams_sharif
"You can boot to recovery by switching the unit off ( the black button in the back), then while holding the power button (the one on the side, next to the pair button) turn the set top box on until the recovery shows up."
This is what I see.
I tried to flash an update.zip in order to see if I can execute command through any script, but the verification of the signature fails.
I tried to click on "Apply update from USB" (that is adb sideload) , but connecting the tv box on the pc nothing happen, no device found neither with "adb devices"
I tried also to click on "Reboot to bootloader" but "fastboot devices" command return nod devices connected.
My idea was to read the recovery image from fastboot extract it and try to compile my own TWRP
Do you have any suggestions to guide me in the right way?
Click to expand...
Click to collapse
Any Luck dear, Please advise as I want the same solution and receive same error 21.
engr.sys said:
Any Luck dear, Please advise as I want the same solution and receive same error 21.
Click to expand...
Click to collapse
Kindly Join our Discord Server Link :https://discord.gg/sbFnauNTWy
I can help u there
Hi
Can you please share the APK please ?
any update on this? did anyone managed to finally root this device or least sideload and apk?
b1acktiger said:
Hi
Can you please share the APK please ?
Click to expand...
Click to collapse
PM Me
Can you please share the APK please ?
{
"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"
}
吨wrp root
Hi, it seems like this version of Magisk doesn't let you enable Magiskhide, am I right ?
(I'm on Realme UI 2.0 - Android 11) , is there a way to use my banking apps, Google Pay, etc.?
Thanks
This worked well.
Didn't work first time, but then I updated magisk to the latest version and it worked perfectly, whereas it was stopping before that.
Hey guys! Last root I did was on android 4.1 and I don't really know how to do it. I have Realme with C.05 soft. Will someone guide me?
Hi guys
This root is worked on europe version? Im from Slovakia. Rmx2202gdpr 11.a.17 .Thank you
qiurigao said:
View attachment 5486671
Click to expand...
Click to collapse
Hello. Is it possible to install this driver on Linux?
I could root a European RMX2202_11_a.17 this way.
First I checked OEM unlock in developer options.
The most difficult part is getting into bootloader. I used a program DeepTesting_realme-release_20210426_newID_signed.apk for this, which I had from https://forum.xda-developers.com/t/...-twrp-2022-02-21.4381727/page-3#post-86279181, I believe.
Hereafter I did under Linux the same as the batch files:
Code:
fastboot flashing unlock
Hereafter an automatic reinstall
Reenabling development options and USB debugging.
Code:
adb reboot bootloader
In bootloader:
Code:
fastboot boot twrp/twrp11.img
Change the language.
Uploaded a recent version of magisk renamed to zip to tmp
Code:
adb push Magisk-v24.3.zip /tmp
Pressed install in twrp and selected this file.
Hereafter reboot to system.
EDIT:
After the update to Android12 RMX2202_11_C.05, I could root it the same way using twrp/twrp12.img.
You can just press Cancel when asked for a password.
EDIT2:
After the last update RMX2202_11.C.16_1160_202204192320.44.7636e18c (for which I didn't remove root), the above method didn't work anymore.
fastboot boot twrp/twrp12.img
resulted in a black screen. I could adb in to recovery, but
/bin/twrp install /sbin/Magisk.zip
gave the following message:
TWRP does not appear to be running. Waiting for TWRP to start . . .
Press CTRL + C to quit.
EDIT3:
Booting the same way from the recovery I found here https://droidfilehost.com/download/download-realme-gt-5g-rmx2202-twrp-recovery-file/ worked. The only problem is that it is Chinese so you have to guess what to do.
EDIT4:
After the update to RMX2202_11.C.20_1200_202207201946.44.84bc864c, this method still works (when the bootloader is unlocked):
adb reboot bootloader
#WAIT
fastboot boot recovery.img
#WAIT
adb push Magisk-v25.2.zip /tmp
adb shell /bin/twrp install /tmp/Magisk-v25.2.zip
adb reboot
EDIT5:
Also works with RMX2202_11.C.27.
Rooted my device successfully but the banking apps not working. Is there any way to make it work magisk hide??
If you are using Magisk 24.3, you have to add the banking app to the DenyList. Go to Magisk settings. Turn on Zygisk and Enforce DenyList and add banking app to Configure DenyList.
Can someone fix systeam read only
Kabid0033 said:
Can someone fix systeam read only
Click to expand...
Click to collapse
there are somethings here and here but i didnt try yet
Kabid0033 said:
Can someone fix systeam read only
Click to expand...
Click to collapse
Magisk is made so that it leaves /system intact and can be better hidden, but you can create files that replace existing ones. If in Magisk setting you check 'Systemless hosts', such a replacement file is created (which takes effect after reboot). How this is done you can see in /data/adb/modules
If you want to change more files, you can imitate this.
To change /etc/mkshrc I have created:
/data/adb/modules/mkshrc/system/etc/mkshrc
/data/adb/modules/mkshrc/module.prop
mkshrc is the replacement file
In module.prop I put:
id=mkshrc
name=mkshrc
version=1.0
versionCode=1
author=I
description=mkshrc edit
jkaltes said:
Magisk is made so that it leaves /system intact and can be better hidden, but you can create files that replace existing ones. If in Magisk setting you check 'Systemless hosts', such a replacement file is created (which takes effect after reboot). How this is done you can see in /data/adb/modules
If you want to change more files, you can imitate this.
To change /etc/mkshrc I have created:
/data/adb/modules/mkshrc/system/etc/mkshrc
/data/adb/modules/mkshrc/module.prop
mkshrc is the replacement file
In module.prop I put:
id=mkshrc
name=mkshrc
version=1.0
versionCode=1
author=I
description=mkshrc edit
Click to expand...
Click to collapse
Thanxx I will try this
grown_man said:
there are somethings here and here but i didnt try yet
Click to expand...
Click to collapse
thnx for your concern buddy
jkaltes said:
Magisk is made so that it leaves /system intact and can be better hidden, but you can create files that replace existing ones. If in Magisk setting you check 'Systemless hosts', such a replacement file is created (which takes effect after reboot). How this is done you can see in /data/adb/modules
If you want to change more files, you can imitate this.
To change /etc/mkshrc I have created:
/data/adb/modules/mkshrc/system/etc/mkshrc
/data/adb/modules/mkshrc/module.prop
mkshrc is the replacement file
In module.prop I put:
id=mkshrc
name=mkshrc
version=1.0
versionCode=1
author=I
description=mkshrc edit
Click to expand...
Click to collapse
Hey if I want to edit in build.prop so I have to write all the values or only the values which I have to add??
Kabid0033 said:
Hey if I want to edit in build.prop so I have to write all the values or only the values which I have to add??
Click to expand...
Click to collapse
The files in /data/adb/modules are taken in place of the original files. So if you open /system/etc/mkshrc, /data/adb/modules/mkshrc/system/etc/mkshrc is opened instead.
So if you want to edit /etc/mkshrc you copy /etc/mkshrc to /data/adb/modules/mkshrc/system/etc/mkshrc and then you edit it. If you have rebooted after it's creation, you can edit /etc/mkshrc. In reality, you will be editing /data/adb/modules/mkshrc/system/etc/mkshrc because if you open /etc/mkshrc, in reality /data/adb/modules/mkshrc/system/etc/mkshrc will be opened. Without much consequences you can try it out with /etc/mkshrc.
I have never modified /system/build.prop, but you should probably do the same.
Copy the original /system/build.prop to /data/adb/modules/amodulename/system/build.prop
After reboot, you can edit /system/build.prop because /data/adb/modules/amodulename/system/build.prop is opened instead of the original file.
jkaltes said:
The files in /data/adb/modules are taken in place of the original files. So if you open /system/etc/mkshrc, /data/adb/modules/mkshrc/system/etc/mkshrc is opened instead.
So if you want to edit /etc/mkshrc you copy /etc/mkshrc to /data/adb/modules/mkshrc/system/etc/mkshrc and then you edit it. If you have rebooted after it's creation, you can edit /etc/mkshrc. In reality, you will be editing /data/adb/modules/mkshrc/system/etc/mkshrc because if you open /etc/mkshrc, in reality /data/adb/modules/mkshrc/system/etc/mkshrc will be opened. Without much consequences you can try it out with /etc/mkshrc.
I have never modified /system/build.prop, but you should probably do the same.
Copy the original /system/build.prop to /data/adb/modules/amodulename/system/build.prop
After reboot, you can edit /system/build.prop because /data/adb/modules/amodulename/system/build.prop is opened instead of the original file.
Click to expand...
Click to collapse
Hey I tried to send one app to system but it didn’t work so I remove that module but after that my most of the system apps not working
Like: camera, gmail, clock, calculator etc
Can you help me fix this
Kabid0033 said:
Hey I tried to send one app to system but it didn’t work so I remove that module but after that my most of the system apps not working
Like: camera, gmail, clock, calculator etc
Can you help me fix this
Click to expand...
Click to collapse
You can't add files to /system, only replace files with your own. Something like: open is intercepted, but the directory structure is left intact. So, if you add something you have to use the name of something that already existed.
I don't understand you problem after removing the module. Did you reboot afterwards?
You can always reinstall Magisk.
jkaltes said:
You can't add files to /system, only replace files with your own. Something like: open is intercepted, but the directory structure is left intact. So, if you add something you have to use the name of something that already existed.
I don't understand you problem after removing the module. Did you reboot afterwards?
You can always reinstall Magisk.
Click to expand...
Click to collapse
You said that we have to put files in /data/adb/modules so that it can reflect in system
So I like to make one app to place in system /app
(eg: Like in older version of android we mangae to do that directly cause their system is rw)
(From this my apps stop working)
So I manually remove the folder from the modules then reboot
But it didn’t fix how it used to be
So I have a Infinix Note 12 pro 4g x676b. The manufacturer of this model has another model with the same name which is more popular. Now let me get to the point. I wanted to root this phone with magisk. its android 12. I tried a few tutorials for it but i realised i need twrp, but this phone model dosent have a twrp img. So i tried the method of fastboot and adb. i patched my boot.img using magisk and then try to patch it to my mobile using my pc. The adb device gets detected and i get it into fastboot. But in fastboot the device does not get recognized. I tried installing all the drivers but the manufacturer does not provide any. I got every unnofical driver installed but still it dosent detect. And also my phone does not get detected in device manager either in other devices or portable devices. What do i do now?
May be this guide is useful:
How to get into fastboot and How to exit fastboot INFINIX Note 12 (2023)? - HardReset.info
The Fastboot Tutorial will show you the easiest way to access the hidden model called fastboot. Check out the secret combination of keys that will boot your device into fastboot.
www.hardreset.info
xXx yYy said:
May be this guide is useful:
How to get into fastboot and How to exit fastboot INFINIX Note 12 (2023)? - HardReset.info
The Fastboot Tutorial will show you the easiest way to access the hidden model called fastboot. Check out the secret combination of keys that will boot your device into fastboot.
www.hardreset.info
Click to expand...
Click to collapse
that is not my question tho. My phone does not get recognised on my windows pc
potatosil said:
that is not my question tho. My phone does not get recognised on my windows pc
Click to expand...
Click to collapse
It is getting recognised as Unknown device?
A PC-connection isn't required at all, you can run ADB and/or Fastboot commands from phone, too. Note: Android must got rooted.
{
"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"
}
Take note that a phone's Android is rooted if SU is present in Android's filesystem.
xXx yYy said:
A PC-connection isn't required at all, you can run ADB and/or Fastboot commands from phone, too. Note: Android must got rooted.
Click to expand...
Click to collapse
i am asking my question to get my phone rooted. If it was already rooted i wouldnt have made a thread
potatosil said:
that is not my question tho. My phone does not get recognised on my windows pc
Click to expand...
Click to collapse
It is a driver related problem.
You may be able to get your work done using wireless adb, although flashing stuff wirelessly is very risky (if the connection breaks whilst the flashing is still going on).
mvikrant97 said:
It is getting recognised as Unknown device?
Click to expand...
Click to collapse
not even an unknown device just nothing is there
potatosil said:
i am asking my question to get my phone rooted. If it was already rooted i wouldnt have made a thread
Click to expand...
Click to collapse
To root a phone's Android Fastboot isn't needed as you suppose : ADB is the correct tool.
Most people instead of adb.exe what comes with Android SDK use adbLink2 app what provides a link between your Android device and your computer.
adbLink2 features:
Install Programs without Android SDK
ADB/Fastboot enabled command-line
Busybox for root and non-root
Built-in WIFI/USB remote
Manage devices via USB or IP address
Root-aware File Manager for Android devices
Install/Uninstall Apps
Connect to devices ad hoc
Manage multiple devices from one PC
Edit XML and other files on your devices
Log file viewer for adbLink2
Hyperlinked HTML Help
adbLink2 is available for Windows, macOS and Linux/ChromeOS
BTW to clarify things, you obviously don't know of:
1.
Before I define root, it's important to understand why it exists and how it works. It's because Android uses permissions ( Linux-based permissions, to be exact ) in the file structure. Every file, every folder and every partition has a set of permissions. These permissions decide who can read a file ( look at or access the contents without changing them ), write to a file ( be able to change the contents of that file, or create a new file inside a folder or partition ) and execute a file ( run the file if it's a type that can run, like an app ). This is done based on users and permissions - certain users have access, while users who don't have the right permissions are blocked from having access.
When you first set up your phone and turn it on for the first time, you are assigned a user ID. If another user logs in via Google, they are assigned a different user ID. When an app is installed on your phone, it's also assigned a user ID of its own. The system itself is a user and other processes that need to run on your phone may have their own user ID. Everything that can do anything to any files on your Android is a user.
2.
To get elevated permissions ( root access ) you place the SU binary ( SubstituteUser ) in a spot that it can run when it's called to run - that's called a PATH - e.g /data/local/tmp. If any app is in user ID's PATH it will run without telling the system exactly where it is. You also need to make sure the SU binary is in a spot that your user ID has permission to execute ( run ) files. Any other app ( Google Play has plenty of apps that need root permissions ) will also need the same access. When you use a method to root your phone, all this is sorted out by the folks who built the root method.
3.
This is where root comes in. The SU binary uses flags when it's run to tell the system what user ID you want to switch to. For example, if I run the SU binary on my Google Pixel phone like this "su Jim -c 'mount - o rw,remount -t auto /system'" I will run the mount command as the user Jim ( after supplying Jim's password ). If I run the SU binary with no flags or arguments, it switches me to the root user. Normally you would need to supply a password, but since "root" is an unused user on Android it has no password. Running the command "su" will switch you to the user root, and assign you the user ID of 0, and put you in the root group. You are now the Super User.
4.
As the Super User you can do anything to any file, folder or partition on your Android. By anything, I mean literally anything. You can remove bloatware apps and you can also remove essential system files that break your phone. You can also do things to the hardware like change the CPU frequency and ruin your phone forever.