How to enable MultiWindow on COS13 - ONE General

A lot of users complaining about missing multiwindow mode on recently released COS13. Here's the methos to activate it:
Pre-requisites:
1. Root
2. Root Browser https://play.google.com/store/apps/details?id=com.jrummy.root.browserfree
3. Developer options enabled on your device (tap build number 7 times to enable)
Open root browser, provide supersu permission
Go to / system / directory and open build. prop file
find ro.build.type=user
change it ro.build.type=userdebug
save..reboot
go to developer option..find multiwindow and enable it
Profit !!!

If you mean
ro.build.type=userdebug
then yes

y2kkingboy said:
If you mean
ro.build.type=userdebug
then yes
Click to expand...
Click to collapse
corrected..thanks

guys i updated the COS 13 using stock recovery everything went fine but after optimizing the apps the phone is still in start screen.. what should i do ?? I dint do any backup...

nobert010 said:
guys i updated the COS 13 using stock recovery everything went fine but after optimizing the apps the phone is still in start screen.. what should i do ?? I dint do any backup...
Click to expand...
Click to collapse
go to stock recovery..wipe data/dalvik/cache and reboot

I've Installed the new build of COS, flashed super su, so the device it's rooted but I can't edit the build.prop file with root explorer(Yes, I gave to it supersu permissions)! I can't understand the reason! some help please?
I don't know why but I've solved. After the erase of build.prop via recovery and the re-flash of COS 13. I've followed the guide again and it worked. so thank you.

Nice

piece of cake. thanks op.

Related

[UPDATED ROOT][Lollipop 5.0.1][XT1069][XT1068]

HEADS UP!
I am not responsible for a bad installation that will damage your device. So, follow the tutorial carefully and install successfully!
P.S¹: Need not be specifically with some firmware.
P.S²: This tutorial was translated with Google Translate!
SPECIFICATIONS
Official version Soak Test
Compatible with XT1068
Not Rooted
Size: 576MB
REQUIREMENTS
Bootloader Unlocked
Lollipop Backup 5.0.1 --> MEGA or Google Drive
TWRP v2.8.0.1 V2 --> Download
ADB+Fastboot.zip --> Download
BETA SuperSU v2.44.zip --> Download
CUSTOM RECOVERY INSTALLATION
Download the TWRP Recovery and ADB+Fastboot.zip
Unzip the ADB+Fastboot.zip
Place the TWRP file inside the unzipped folder ADB+Fastboot
Open a command window in the folder. To do this, hold the Shift key and click the right mouse button in a free field within the folder, select "Open command window here".
When the command window opens, type the seguinto command and press Enter:
Code:
fastboot flash recovery TWRP_2.8.0.1_Titan_v2.img
Ready, TWRP Recovery installed !
RESTORE LOLLIPOP 5.0.1
Download Backup Lollipop.
Extract the zipped file.
Go to the TWRP/BACKUPS/YOUR SERIAL NUMBER folder, and change the name of the folder for your device Serial Number, for this go to Settings - > About phone -> Status then look at your "Serial Number".
Then copy the TWRP folder and paste in the device memory.
Now, turn off the device.
Enter Bootloader mode, then go down with the volume button least until "Recovery" and confirm with the most volume button.
Within the TWRP Recovery, go to the "RESTORE", press on the "Lollipop 5.0.1" folder
Then confirm the restoration of the backup.
Wait until the restoration is complete.
ROOT - [UPDATED]
NOTE: THIS VERSION IS RUNNING SUPERSU 100% WITHOUT BOOTLOOPS.
Download the BETA SuperSU v2.44.zip
Put in the internal memory.
Install the SuperSU with TWRP Recovery.
When finished, wipe cache/dalvik.
Restart the device and wait a few seconds, then it will start normally without Bootloops.
STOCK RECOVERY LXB22.46-25 --> Download
AUTO INSTALLER OF THIS STOCK RECOVERY LXB22.46.25 --> Download
Thanks to Lucas Alves, for having made ​​available this backup.
Thanks to Chainfire by execelente SuperSU!
Downloading to see if it can be...
Share some SS for the same, also specify the Firmware required to restore this? I.e. should be on 4.4.4 Braz Firmware or what? Pls put proper details to avoid any mistake from any user...
deeplyyoung said:
Share some SS for the same
sent From My XT1033{LP} using TapatalK
Click to expand...
Click to collapse
Seconded! Screenshots plzz... Specially the about page with Kernal Description and the Build date
Downloaded and installing.
Didn't wipe anything (I want to try upgrading). After the initial logo, the screen went black for about 2 mins and then started optimizing installed apps.
I' ll let you know as soon as I' ll be able to do some testing.
Thanks for sharing
PS. I own a XT-1068
gvala said:
Downloaded and installing.
Didn't wipe anything (I want to try upgrading). After the initial logo, the screen went black for about 2 mins and then started optimizing installed apps.
I' ll let you know as soon as I' ll be able to do some testing.
Thanks for sharing
PS. I own a XT-1068
Click to expand...
Click to collapse
Gr8, await for your reviews, but you should format system & clear cache for clean install, well now just tell us what you got, me to having XT1068 Dual Sim...:good:
Kernel version 3.4.42, Date Thu Dec 18 04:15:21 CST 2014
System version: 22.21.25.titan_retbr_dstv.retbr.en.BR reteu
Build number: LXB22.46-25
noemi.abril said:
Kernel version 3.4.42, Date Thu Dec 18 04:15:21 CST 2014
System version: 22.21.25.titan_retbr_dstv.retbr.en.BR reteu
Build number: LXB22.46-25
Click to expand...
Click to collapse
That we saw under SS, could you pls specify your Device Version & Dual Sim is Working or not??
deeplyyoung said:
Share some SS for the same, also specify the Firmware required to restore this? I.e. should be on 4.4.4 Braz Firmware or what? Pls put proper details to avoid any mistake from any user...
Edit: as per SS it's Braz Soak update for XT1069, @EduardoBoese update OP accordingly that one must be on Braz KK 4.4.4 XT1069 before restoring the same.
Click to expand...
Click to collapse
P.S¹: Need not be specifically with some firmware, just Wipe Dalvik Cache, Data, Cache and System, then you can restore.
Click to expand...
Click to collapse
Sorry, now explained
gvala said:
Downloaded and installing.
Didn't wipe anything (I want to try upgrading). After the initial logo, the screen went black for about 2 mins and then started optimizing installed apps.
I' ll let you know as soon as I' ll be able to do some testing.
Thanks for sharing
PS. I own a XT-1068
Click to expand...
Click to collapse
Wipe Dalvik Cache, Data, Cache and System, then you can restore
deeplyyoung said:
That we saw under SS, could you pls specify your Device Version & Dual Sim is Working or not??
Click to expand...
Click to collapse
Work OK on XT1068 reteu
noemi.abril said:
Kernel version 3.4.42, Date Thu Dec 18 04:15:21 CST 2014
System version: 22.21.25.titan_retbr_dstv.retbr.en.BR reteu
Build number: LXB22.46-25
Click to expand...
Click to collapse
just a quickie as still setting up XT1068 Dual sim UK
1)flashed with a full wipe and had to force a reboot as had been stuck in bootloop for 10mins +
2) it then booted with the upgrading android 1 to 50 screen , installed and booted to setup screen
3) 1st check was dialler and it works! (sort of!) you can dial AND you have dual sim selection , no FC's as had before,
but i dialled home phone, it rang and i hung up- great I thought - until i was checking phone settings and my home phone rang again, It was my xt1068 again BUT i wasnt showing any thing on phone to say I was dialling out. WTf?!!!
Maybe It a one off as not able to repeat this - but just a little warning - you could be connected to a number with NO indication.
4) plan to set up , root , remove brazil apps , edit build.prop to xt1068 friendly and make a new TWRP backup
@noemi.abril & @reefuge pls specify which version of TWRP you used to restored?? i.e. 2.8.0.1 or ______??
/sigh
How many times do OTA capturing how-to's have to be posted before people use them?
Installing someone else's installation backup is clearly Not a Clever Thing to Do®.
deeplyyoung said:
@noemi.abril & @reefuge pls specify which version of TWRP you used to restored?? i.e. 2.8.0.1 or ______??
Click to expand...
Click to collapse
TWRP 2.8.3.0
rufflove said:
/sigh
How many times do OTA capturing how-to's have to be posted before people use them?
Installing someone else's installation backup is clearly Not a Clever Thing to Do®.
Click to expand...
Click to collapse
yes it's clever thing to do cuz this is the only safest way to enjoy LP & we can easily revert to KK 4.4.4 anytime when official OTA release...:fingers-crossed:
deeplyyoung said:
@noemi.abril & @reefuge pls specify which version of TWRP you used to restored?? i.e. 2.8.0.1 or ______??
Click to expand...
Click to collapse
http://forum.xda-developers.com/moto-g-2014/development/recovery-images-install-recovery-images-t2987246
I used the No install TWRP
its 2.8.3.0. Fixed
Everything is OK
Everything works just fine
But upgrade path has problems with wifi.
Dual sim selector works fine, and data counters work fine.
what surprised me is that the old messages app, still exists and the new one Google Messenger is missing
Again, thanks for uploading
PS. It seems that it is a Brazilian rom. After factory reset, it starts with portuguese language and there is also a preintalled app "BR Apps" that says something for Brasil
gvala said:
Everything works just fine
But upgrade path has problems with wifi.
Dual sim selector works fine, and data counters work fine.
what surprised me is that the old messages app, still exists and the new one Google Messenger is missing
Again, thanks for uploading
PS. It seems that it is a Brazilian rom. After factory reset, it starts with portuguese language and there is also a preintalled app "BR Apps" that says something for Brasil
Click to expand...
Click to collapse
That's Rite, it's Braz Soak update for XT1069[emoji14]
Successfully upgraded...
Successfully Rooted too..
Request for new download links.
Sir I am from India. Here the mega.co.nz website is not opening i tried several different ways but due to large size of the file I was unable to download. Please provide us with googledrive download link.

[ROOT] Xiaomi Redmi Note 3 Pro (Snapdragon 650)

Edited: Credit to Informatyk,
Hi everyone. Today I want to share you. How to root new device Redmi Note 3 pro. Unlock bootloader not needed.
1. Enable Developer Functions: Go to Settings, About phone, 7 click on Miui version to enable Developer options.
2. Enable USB debugging: Go to Settings, Additional settings, Developer options, then turn on USB debugging.
3. Download and install this application from here.
static1(dot)romzj(dot)com/file/shuame/root/RootGenius_chrome_3.1.3_setup.exe
(see pictures 1,2,3 what you have to do when install application on PC and follow in reverse order: 3-2-1)
refer to pics here: en(dot)miui(dot)com/thread-234857-1-1.html
replace the "(dot)" with the punctuation
4. Turn on Wifi or Mobile data.
5. Connect your phone to computer via USB.
(a notif bubble should appear, allow USB debugging on phone)
6. Run the installed application (Root¾«Áé.exe) as admin from your PC, then click on button (picture 4). And wait.
7. Your phone will reboot automatically while process rooting is 65%.
(a notif bubble should appear again, allow USB debugging on phone again after reboot)
8. After this your phone will be rooted.
(If not. Plz go to home screen. Run application again, then click on root icon in menu.)
Good luck all!!!
Thanks to msmobile.vn
Does not work properly, breaks installs and security center, cannot install any apks after using this method.
Resets after reboot
Verdict: AVOID
Yes, i can't install any app from play store after "root"... and when you reboot it will be reset completely.
I successfully used this method from 7.1.1.16 Stable (bootloader still locked), and achieved temporary root only. So you can run Titanium Backup etc. and some individual apps which require root.
But no way to replace KingRoot with SuperSU.
Also, root does not survive reboot, and phone resets (takes a long time to reboot) - so cannot install e.g. Xposed (which requires reboot).
The method is safe - no data or apps are lost in the process.
Note I have since updated to 7.1.1.18 Stable, and this method no longer works at all (not even temporary root).
But I guess there is hope?
Now with the latest update rom, this process does not work at all.. The application simply does not do anything
Install the China DEV Rom 6.3.17 Then go to Security, Permissions, Root Access. Done.
How? http://en.miui.com/download-301.html#439
ROM: http://bigota.d.miui.com/6.3.17/miui_HMNote3Pro_6.3.17_6a6a3b709a_5.1.zip
Don't know how you did it w/o unlocking the bootloader.
unable to flash this via updater app, do i need to flash it via miflash tool???
Is this the Note 3 Pro Prime version?
How to flash at locked bootloader, this way does't worked or I'm doing something wrong.
exonerare said:
Is this the Note 3 Pro Prime version?
Click to expand...
Click to collapse
del, sry wrong
Super-Sume Pro can replace KingoRoot with SuperSu
Super-Sume Pro can replace KingoRoot with SuperSu !
Super-Sume Pro :
https://play.google.com/store/apps/details?id=darkslide.com.supersumepro
:laugh::laugh::laugh:
iustinteo said:
Super-Sume Pro can replace KingoRoot with SuperSu !
Super-Sume Pro :
https://play.google.com/store/apps/details?id=darkslide.com.supersumepro
:laugh::laugh::laugh:
Click to expand...
Click to collapse
I tried this method a while ago and SuperSume did NOT work on the RN3Pro.
Things might have changed but why would you even bother with KingoRoot?
Just root directly from developer ROM then install SuperSu from Play Store, or install TWRP and SuperSU from the start.
redmi note 3 7.2.8 root
can anyone plzz teelll me that how can i unlock my bootloader and then root it plzzz
iamvips said:
can anyone plzz teelll me that how can i unlock my bootloader and then root it plzzz
Click to expand...
Click to collapse
Unlock : http://en.miui.com/unlock/
Root: Flash TWRP and SuperSU
ive already hace unlock code for my miui. when i wan unlock via unlocker tool, they stuck at 50%. just google then got ppl say need flash dev rom 1st. i try downlod dev rom, try update my phone the dev rom but failed. its looks like so hard to just get root this phone. i only need root. wan unlock bootloader still stuck with bugs. can anyone help me?
_ossie_ said:
Install the China DEV Rom 6.3.17 Then go to Security, Permissions, Root Access. Done.
Click to expand...
Click to collapse
So after unlocking BL of stable ROM, and going through all the TWRP/other ways to gain root access - we can just flash to China Dev ROM (+unlocked BL), gain root access via Security>Permissions>Allow root access?
PWRX said:
So after unlocking BL of stable ROM, and going through all the TWRP/other ways to gain root access - we can just flash to China Dev ROM (+unlocked BL), gain root access via Security>Permissions>Allow root access?
Click to expand...
Click to collapse
That's what I did, way back on 6.3.17. Once rooted I moved on to flashing TWRP and SuperSU. But if you just want root, then yes.
_ossie_ said:
That's what I did, way back on 6.3.17. Once rooted I moved on to flashing TWRP and SuperSU. But if you just want root, then yes.
Click to expand...
Click to collapse
Thanks. Will the data be wiped when updating to Chinese Dev ROM from Stable Global ROM?
PWRX said:
Thanks. Will the data be wiped when updating to Chinese Dev ROM from Stable Global ROM?
Click to expand...
Click to collapse
No, - You can try without wiping data but I wouldn't recommend as there are different app sets.
To preserve your data use the intrinsic MIUI backup to backup everything (This will back up all your user apps and settings). Then Wipe data / cache , flash new ROM, and run restore using the same tool. It works perfectly, except you will have to manually reinstate all your Google Accounts. For some reason the MIUI Backup tool doesn't play nicely with Google.

[TUTORIAL][Tethering]+[Android Pay] How to have your Nougat, and eat it too!

Obviously I'm not responsible for your mom exploding or your phone disowning you, but.....
I got tethering and Android Pay working on stock Nougat - that's Android N, folks - on a Nexus.
(confirmed will work on Marshmallow and up on 5, 5x, 6, 6p...etc.)
Thanks to @Chainfire, @ManHands and @interloper, and you!
click thanks if this helps, or buy me a beer or something.
prerequisites:
working adb and fastboot (from platform-tools in the Android SDK if you don't know where to find it)
twrp .img for your device
latest stable systemless supersu
1. be on Marshmallow or Nougat obviously
2. flash twrp
(volume down + power on nexus gets you into bootloader, then after flashing recovery, use volume buttons to scroll and power button to select recovery mode)
3. flash systemless root while booted into twrp (unsure if .supersu SYSTEMLESS=true in /data is still needed, but can't hurt - mine is still there from earlier.)
4. while still in twrp, go to mount and check system. Make sure you allow changes.
5. from your computer, do this
Code:
adb shell
echo "net.tethering.noprovisioning=true" >> /system/build.prop
6. reboot into Android.
7. Install Terminal Emulator from the Play Store.
8. Launch it, and in Terminal Emulator, do this
Code:
su
settings put global tether_dun_required 0
exit
9. go into Supersu, expert, scroll to the bottom and hit full unroot. No, you don't want it to patch you back to the stock boot image or recovery*. If it hangs, just reboot and try doing it again.
10. ????
11. Profit! You should have tethering unlocked, be unrooted, and have full Android Pay goodness working.
To take an OTA, do this, because Flashfire gets confused after you've done build.prop edits -
1. go to About Phone, scroll down. Find your build number.
2. download that Nexus Factory Image.
3. Unzip it all. ALL OF IT.
4. Make sure you have Android SDK & platform-tools (or just a working Fastboot and ADB)
5. just flash boot, system, and recovery - you can now OTA with no problems. Then repeat the above guide on your new OTA. Confirmed working 10 minutes ago, OTA'ing from Marshmallow to Nougat and then getting tethering working again
ALTERNATE IF YOU PREFER FLASHFIRE:
All the above steps, but you only have to flash the System image to fix the build.prop hash fail then flashfire should work for you. Wouldn't necessarily recommend upgrading version numbers (6.0.1 to 7.0.0) with Flashfire, but who knows, it might work great! Chainfire is a wizard.
*you can do this if you want, but when I let it patch my boot image I got the dreaded "device corrupt!!!!1" message at boot. Did not try letting it flash stock recovery image.
You're mentioning to do a systemless root but enable read/write on the system partition. Isnt't that counter-intuitive?
codycook said:
You're mentioning to do a systemless root but enable read/write on the system partition. Isnt't that counter-intuitive?
Click to expand...
Click to collapse
Nope! rw system is only for the build.prop echo, other than that you don't touch /system
Have you been able to get this to work with the latest factory Nougat images from Google's website?
I successfully did your process above when I was on an older version of Nougat for Nexus 6 (beta release), but when I try now with NBD90Z Google Pay won't work after rooting after a full unroot.
Yes i'm seeing this also and other not root methods for tethering don't not seem to work either with NBD90Z .
cal028 said:
Yes i'm seeing this also and other not root methods for tethering don't not seem to work either with NBD90Z .
Click to expand...
Click to collapse
Hmm. Bummer. For a split second, I felt like I finally had a fully functioning Android
Almost regret upgrading to NBD90Z, but figured it would be less buggy. If anyone has figured out how to get AP and NBD90Z to work with a slightly modified build.prop file (to allow tethering), please update this thread!
cal028 said:
Yes i'm seeing this also and other not root methods for tethering don't not seem to work either with NBD90Z .
Click to expand...
Click to collapse
same for me too. Pulled build.prop and verified net.tethering.noprovisioning=true and settings put global tether_dun_required 0
still no luck on NBD90Z
w8291 said:
same for me too. Pulled build.prop and verified net.tethering.noprovisioning=true and settings put global tether_dun_required 0
still no luck on NBD90Z
Click to expand...
Click to collapse
Flashed back down to NRD90S and the method works again.
Where did you download that version?
The stock Nexus 6 images on the official Google site do not list that version as valid for the Nexus 6.
Are you using the Nexus 6P image?
May be a dumb question but I have a Moto X Pure running Ressurection Remix nougat ROM and I don't have WiFi tethering in my settings. Would this method work on it?
worked, thanks
n8onXDA said:
Have you been able to get this to work with the latest factory Nougat images from Google's website?
I successfully did your process above when I was on an older version of Nougat for Nexus 6 (beta release), but when I try now with NBD90Z Google Pay won't work after rooting after a full unroot.
Click to expand...
Click to collapse
With the current build, no methods work. SafetyNet check fails with the last 2 builds
Safety net now requires OEM lock, even fully stock with open bootloader never rooted fails
Sent from my Nexus 6 using Tapatalk
Ok great! Well at least I know I'm not missing some clever workaround. Isn't there a way to bypass SafetyNet and/or OEM lock? I thought someone was trying or working on something like this...
wrecklesswun said:
With the current build, no methods work. SafetyNet check fails with the last 2 builds
Click to expand...
Click to collapse
So I read that the March 2017 7.1.1 Update for Nexus 6 broke Android Pay even on non-rooted devices so Google released images with SafetyNet disabled. Would that version allow us to root AND use Android Pay since SafetyNet is disabled to make it work for regular users?
Had to do this but gaining root was going to be tricky (encrypted partition), and I didn't need root for any other reason. I unlocked the bootloaded, flashed twrp, and used adb to pull build.prop, added the line in (net.tethering.noprovisioning=true), pushed it back using adb (with twrp still running), and rebooted. Tethering is working fine now.
By the way -- this is so infuriating. When tethering does not work it asks your provider's permission even in airplane mode (which fails, it's airplane mode), so you can't use the phone to provide wifi to other devices. Such an amateurish disrespect for my rights as an owner of an unlocked device.
I flashed Vanilla rom 7.1.2, then flash stock recovery and locked bootloader and Android pay, Netflix and Snapchat etc all work. After I flashed Vanilla rom Android pay wasn't working stating I had a root, so I locked bootloader but was bootlooping into twrp. After flashing stock recovery it worked just fine
I discovered that you can you can have TWRP recovery and still use android pay so long as you have your bootloader locked. I am pretty sure you can still flash roms w/ locked bootloader in recovery but I am not positive

Custom Rom For Samsung J2 (J200H) S7 Experience Custom Build

Hey There ...........
Introducing My New Rom : S7 Experience Custom Build
Built V1
Based On Stock 5.1.1 Lollipop Rom
Warnings :
1. You are now Void your Warrenty …….
2. Backup all your personal apps and important data to avoid loosing them …
3. Do all steps perfectly And carefully ……
4. I am not responsible for any mistake and Brick your phone ….[/SIZE]
Features :
1. Only For J2 2015 3G Variants
2. Android 5.1.1 Lollipop
3. Based on latest J200HDDU0APE1/APJ3 firmware
4. Deodexed
5. Medium Deboalted
6. Zipaligned
7. Signed
8. PreRooted
9. Added Busybox,SU.d and Init.d Support
10. S7 Style Statusbar
11. S7 Music Player
12. S7 Themed Apps
13. Xposed Enabled Zip Added
14. All Apps Are Updated
15. Fx Root Explorer
16. Sony Movies Added
17. S7 Wallpaper
18. S7 Icons
19. S7 Sound And Bootanimation
20. And More ...
How To Install :
1. Download Zip file Of the Rom From Link Given Below
2. You Mast Have TWRP Recovery on your device.(Letest TWRP is Given In attachments)
4. Copy the S7 Experience Custom Build.zip toYour SD card
5. Turn off Your Phone And press home button+power+Volume up button at a same time
6. Aftar apearing TWRP recovery go to install and install S7 Experience Custom Build.zip file from sd card you downloaded before
7. Now reboot system and wait for approximately 5 minutes.
9. Now you are good to use this rom ......
[For Xposed Install xposed-v78.0-sdk22-arm-custom-build-by-wanam-20151116.zip after installing rom given in the attachments]
Downloads :
https://drive.google.com/open?id=0B0rTXdhaTd2MV2szTEYtQWVIeVU
Credits :
@ASSAYYED –for his best ever kitchen.
@ashyx - for his Twrp
@me - For building Rom
Contact Me :
On Facebook Only Send Massages
www.facebook.com/almamun512
Thanks
Nice rom the rom like realy galaxy s7 I very like this
Great work . I will soon test it By the way is there theme support and if not are you planning to do it????
ad. said:
Great work . I will soon test it By the way is there theme support and if not are you planning to do it????
Click to expand...
Click to collapse
Actually Theme Option Is Enabled But Its Not Change Everything, I Dont Know Why, But thing Is Our Framework Doesn't Suppot That.
almamun512 said:
Actually Theme Option Is Enabled But Its Not Change Everything, I Dont Know Why, But thing Is Our Framework Doesn't Suppot That.
Click to expand...
Click to collapse
ok but my phone stick in bootlogo when i tried to install xposed it said unable to mount system ?????? what to do
ad. said:
ok but my phone stick in bootlogo when i tried to install xposed it said unable to mount system ?????? what to do
Click to expand...
Click to collapse
Did You clean Insall It ?
Do Wipe/Advance Wipe/system,data,delvik,catch
Then Install
Make Sure Your Device Is J200H 3g
almamun512 said:
Did You clean Insall It ?
Do Wipe/Advance Wipe/system,data,delvik,catch
Then Install
Make Sure Your Device Is J200H 3g
Click to expand...
Click to collapse
I tried both clean and dirty flash but no sucess ...
I got where the problem is...
system is not being fully extracted . There lacks many folders like priv-app in system partition .
I installed another zip file and noted that every thing is working well the system got fully extracted.
Maybe the problem is in updater-script Hope you can fix it soon
Will it wrk on j200g?
ad. said:
I tried both clean and dirty flash but no sucess ...
I got where the problem is...
system is not being fully extracted . There lacks many folders like priv-app in system partition .
I installed another zip file and noted that every thing is working well the system got fully extracted.
Maybe the problem is in updater-script Hope you can fix it soon
Click to expand...
Click to collapse
Can you send me a picture of the error or something.
There Should be no problem in updater-script
Also send me your about devices screenshot
almamun512 said:
Can you send me a picture of the error or something.
There Should be no problem in updater-script
Also send me your about devices screenshot
Click to expand...
Click to collapse
http://imgur.com/GYMLjJL
here's the ss about phone and i cant send picture of error but I'm sure the problem was caused due to the problem in system
The flashing had went smoothly but when i tried to boot to system i got atuck at samsung galaxy j2 screen and on checking system via twrp file manager i gound ther lacked different things.
I don't know if its the problem of my twrp or else I'm thinking of giving one try to flashify
ad. said:
http://imgur.com/GYMLjJL
here's the ss about phone and i cant send picture of error but I'm sure the problem was caused due to the problem in system
The flashing had went smoothly but when i tried to boot to system i got atuck at samsung galaxy j2 screen and on checking system via twrp file manager i gound ther lacked different things.
I don't know if its the problem of my twrp or else I'm thinking of giving one try to flashify
Click to expand...
Click to collapse
What Rom Are U Using Stock ?
I Dont think so.
Anyway Its strongly Recommended to be on letest Stock Rom Before Flashing My Custom Rom.
Nobody Having this Problem Like You.
And Use the TWRP I gave in attachment.
Not working....
Sent from my SM-J200H using XDA Free mobile app
wow this rom is better than i expected
in twrk recovery i got msg regarding it succeeded. but after that my mobile is still booting showing samsung j2 android. pl help me.
finally got it
Best rom out till date.
thanks @almamun512
No superuser access
I flashed this custom rom today and i like the new UI. But there is no superuser preinstalled although it said installing superuser when flashing the rom. I also installed supersu later using twrp but it says " Your device is unrooted."
How can i install superuser and gain root access ?
Nikeshsml said:
I flashed this custom rom today and i like the new UI. But there is no superuser preinstalled although it said installing superuser when flashing the rom. I also installed supersu later using twrp but it says " Your device is unrooted."
How can i install superuser and gain root access ?
Click to expand...
Click to collapse
I didn't experienced that problem. The phone was rooted only SuperSU app was missing which I installed.
Good day sir. I appreciate your hardwork creating the rom. :good: Will it work on a j200bt rom?
GREAT ROM
Beautiful Rom and fast but the problem i faced was the wifi reconnecting every 2 minutes and cant customize the rom by apps like gravity box ....
battery is friendly and i hope to make update for this vertion of S7 because the S8 Randomly restart without any reason
thanks a lot from my heart .
Rom can be flash in samsung J200GDDUZAQF6
PLEASE REPLY ME

[GUIDE] Enable Camera2 API Without Root [mido] [Unlocked Bootloader] [MIUI 9]

DISCLAIMER
I am not responsible for anything that happens to your device on following these steps. These are untested steps that worked for me and might work for you.
PREREQUISITES
1. PC with adb
2. Unlocked Bootloader
3. TWRP
4. MIUI 9 [Might work with other ROMs, not tested]
5. Lazyflasher zip
NOTES
1. If you are on a custom ROM, chances are that camera2 api is already enabled. Use Manual Camera Compatibility to verify.
2. If you are on MIUI, updating using ota might reset build.prop file. This might help, not tested. Update: I successfully updated to MIUI 9 Global 7.10.19 | Beta, see below for steps,
3. I am using Google Camera v4.4.020.163412804 on MIUI 9 Global 7.9.7 | Beta, and it is a HUGE improvement over the stock camera.
STEPS
1. Boot into TWRP. (Guide if you don't have TWRP)
2. Mount System.
3. Take NANDroid backup. (Optional but HIGHLY RECOMMENDED)
4. Connect to PC and execute the following command in terminal:
Code:
[SIZE="3"]adb pull /system/build.prop[/SIZE]
5. This copies build.prop to the current directory. (C:\Users\[USERNAME] by default on windows)
6. Copy it to another directory for backup.
7. Open in editor and add the following line at end:
Code:
[SIZE="3"]persist.camera.HAL3.enabled=1[/SIZE]
8. Save and exit.
9. Execute following commands:
Code:
[SIZE="3"]adb push build.prop /system/
adb shell
cd system
chmod 644 build.prop
[/SIZE]
10. Copy lazyflasher to internal storage.
11. Flash using TWRP.
12. Reboot to system.
13. Use Manual Camera Compatibility Checker to verify.
14. PROFIT!
15. Install the latest Google Camera HDR+ Port. (Optional but HIGHLY RECOMMENDED ;P)
UPDATING MIUI
1. Download the official recovery zip from here.
2. Download latest TWRP from here
2. Reboot into TWRP.
3. Take NANDroid. (Optional, just in case . . .)
4. Transfer ROM zip, TWRP img and Lazyflasher zip to internal storage.
5. Flash ROM zip. (Took about 10 minutes)
6. Flash TWRP img. (Go to flash -> select flash image -> select twrp-[v].img)
7. Flash Lazyflasher zip.
8. Follow steps 4 through 9 of above instructions. (Yes, build.prop also gets replaced on update)
9. Reboot to system.
10. Wait patiently.
11. VOILA !!
LINKS
1. Manual Camera Compatibility Checker
2. Lazyflasher Zip
3. Google Camera HDR+ Port
4. Latest MIUI Recovery Image
5. Official TWRP for mido
6. Sources: (1) (2) (3)
Hope this helps. Try and comment if this works for you in other ROMs. Also let me know if anything is unclear.
TWRP Tweaks (MIUI 9 Beta)
The method in this thread basically allows you to edit build.prop without rooting, which opens up a lot of possibilities. Here are some other useful tweaks to build.prop that I use.
(Note: If a line is already present in the file, edit the line otherwise add at end.)
1. Enable MIUI's full screen gestures
Code:
[SIZE="3"]
qemu.hw.mainkeys=0
[/SIZE]
2. Add EIS and disable noise cancellation
Code:
[SIZE="3"]
persist.camera.eis.enable=1
persist.camera.HAL3.enabled=1
ro.qc.sdk.audio.fluencetype=fluencepro
[/SIZE]
3. Turn off noise cancellation for audio recordings
Code:
[SIZE="3"]
persist.audio.fluence.voicerec=false
[/SIZE]
4. Fix Google Assistant talkback
Code:
[SIZE="3"]
mm.enable.qcom_parser=245389
[/SIZE]
Sources: (1)
Do reply if you are using some build.prop tweak and I'll add it here!
is it possible to make the flash-able zip work with stock recovery?
What does the lazyflasher zip actually do? A quick search on google shows a custom kernel installer.
joefso said:
is it possible to make the flash-able zip work with stock recovery?
Click to expand...
Click to collapse
I am not sure if it is safe to flash zips from stock recovery. Even if you could, you would not be able to take NANDroid, so you are doomed if things go south. Still, if you want, you could try and then we'll know
mato_d007 said:
What does the lazyflasher zip actually do? A quick search on google shows a custom kernel installer.
Click to expand...
Click to collapse
The source of the lazyflasher zip (2 in sources) says:
This device uses dm-verity
This means that swiping to allow system modifications will prevent you from being able to boot if you are using the stock kernel. In order to bypass dm-verity's boot prevention, you will have to install a kernel that has dm-verity disabled in the fstab.
Click to expand...
Click to collapse
When I was trying the adb method, I was getting a bootloop, because (I think) the system partition had been modified (new build.prop replaced old one). Flashing this zip solved this, so I guess it essentially allows modifications to the system partition.
A_K_S_H_ said:
I am not sure if it is safe to flash zips from stock recovery. Even if you could, you would not be able to take NANDroid, so you are doomed if things go south. Still, if you want, you could try and then we'll know
Click to expand...
Click to collapse
I am willing to try because it would be great if this could work withouth using twrp, root or a unlocked bootloader.
Are the scripts compatible?
joefso said:
I am willing to try because it would be great if this could work withouth using twrp, root or a unlocked bootloader.
Are the scripts compatible?
Click to expand...
Click to collapse
They should be, as I used them with stock MIUI, stock kernel. However, are you going to flash a zip on locked bootloader? Is that even possible? Why would modifications to the system partition be allowed with locked bootloader? What would be the point of locking if that is the case?
A_K_S_H_ said:
They should be, as I used them with stock MIUI, stock kernel. However, are you going to flash a zip on locked bootloader? Is that even possible? Why would modifications to the system partition be allowed with locked bootloader? What would be the point of locking if that is the case?
Click to expand...
Click to collapse
I assumed that if OTA updates can be flashed through bootloader then by that logic /system could be modified too, right? hmmm
In Android devices, Recovery is an Android-based, lightweight runtime environment separate from and parallel to the main Android operating system. Recovery's original purpose was:
to apply software updates to the device, e.g. OTA updates, and
to erase user data and cache, e.g. for troubleshooting or preparing the device for resale (factory reset) and
to run (another) external tool from microSD flash memory
https://forum.xda-developers.com/wiki/Recovery
Click to expand...
Click to collapse
Thanks... BTW..
You can simply add that line using any file manager with root permissions and after rebooting device it works..
amit.tiger12 said:
Thanks... BTW..
You can simply add that line using any file manager with root permissions and after rebooting device it works..
Click to expand...
Click to collapse
Read the title : WITHOUT ROOT
A_K_S_H_ said:
Read the title : WITHOUT ROOT
Click to expand...
Click to collapse
yep I found..
do you have any solution for locked bootloader or everything stock??
amit.tiger12 said:
yep I found..
do you have any solution for locked bootloader or everything stock??
Click to expand...
Click to collapse
Unfortunately I don't have access to a stock mido right now, and I don't want to lock my bootloader.
If you're willing to risk it, you could try these steps:
1. Go to developer settings and enable adb.
2. Follow steps 4 to 9 of main post (with device switched on)
3. Reboot.
You might get a bootloop on rebooting, in which case you'd have to get into stock recovery and factory reset, because afaik, stock recovery doesn't give you adb.
Do tell what happens if you try this, good luck!
When I replace the build.prop the phone goes bootloop. It does not matter I use adb or root explorer or something... Why is that? BTW only this method worked: I used an app called build prop editor and worked like a charm! Thank you. If you did not tell that it was possible to enable camera 2 api on miui 9, all my hopes would be lost. So I suggest everyone to use another methods in case this does not work.
Does this work for MIUI 8? I dont want to root my phone but would like camera2
qun said:
Does this work for MIUI 8? I dont want to root my phone but would like camera2
Click to expand...
Click to collapse
It should, provided you have unlocked bootloader, but I haven't tested yet. Take a backup and try! Also, don't forget to reply what happens if you do try.
Can someone tell me what is this?it was set to no hdr+ on default.im on miui 9 global beta 7.12.8
In the end of the TWRP guide it says to flash lazyflasher.zip . In the end of this guide it also says you have to install lazyflasher.zip .
Do you have to install it both times or is once enough ? What would happen if you follow both guides to the letter and install it twice ?
Ghavio1516 said:
Can someone tell me what is this?it was set to no hdr+ on default.im on miui 9 global beta 7.12.8
Click to expand...
Click to collapse
These are configs, check and see which one works best for you.
foxhunt said:
In the end of the TWRP guide it says to flash lazyflasher.zip . In the end of this guide it also says you have to install lazyflasher.zip .
Do you have to install it both times or is once enough ? What would happen if you follow both guides to the letter and install it twice ?
Click to expand...
Click to collapse
No, once should be enough, but flashing twice won't cause any trouble either.

Categories

Resources