Database Develop

[Guide] Downgrade/Root/DualRecovery C6916 Guide

This is my NOOB friendly version for rooting and installing Dual Recovery on a Sony Xperia Z1S (C6916).
First things first, I have written this entire this myself and have only used links from other posts here on XDA.
The thank you's will be at the end of this post.
Ok, Now onto the real reason your here...
Follow these steps to pre-pair your Z1S for the road ahead...​
1) Go to "Settings-About Phone".
Be sure your "Model Number" is "C6916".
Your "Build Number" is "14.4.B.0.37".
If your "Build Number" is different then see 2nd post for "How to Downgrade/Upgrade Build Number"
2) Click "Build Number" about 7 times (I think) to unlock "Developer Mode".
3) Go back to "Settings" screen.
Second option from the bottom should now be "Developer Options".
5) Enter this new screen and enable "USB Debugging".
6) Go back to "Settings" and enter "Security".
Enable "Unknown Sources" and disable "Verify Apps".
7) Go to "support.sonymobile.com/us/tools/pc-companion/"
Download, Install, plug device in, and it should detect and install drivers for your Z1S.
8) Download & Extract "forum.xda-developers.com/showthread.php?t=2784900" to a folder on the desktop (Name folder something easy like Z1S).
9) Download & Extract "Z1-lockeddualrecovery2.8.3-RELEASE.installer.zip" from "nut.xperia-files.com/" by clicking the "XZDualRecovery" to the same folder from step #8 (keeping separate folders inside to avoid confusion).
Well that seemed like allot now didn't it? Well the worst is over (hopefully).
Follow the below steps to root your phone...​
1) On computer go to the folder where you extracted "Easy Root Tool v12.4"
Run file called "install.bat"
Wait for it to load and follow the on-screen instructions to gain root.
Notes!!!
a) If at any time it seems like the tool has frozen, it probably has.
Wait for at least 1 minute and then click the red X in the top right of the window to close.
Press "Ctrl+Alt+Delete" and select "Start Task Manager" (depending upon windows version).
Choose the "Processes" tab and look for "abd.exe".
Choose it and then click "End Process" and confirm in the new window.
If you do not find "adb.exe" or you have killed it already then repeat step 1.
2) Once Easy Root Tool v12.4 has completed and shows a successes message you will be rooted! But we cant just use it as it is now, its "SuperSU Binary" is outdated.
3) Unplug usb and reboot your phone.
4) Once rebooted, go to the "Play Store" and search for and download "supersu" by "Chainfire" (support him if you can )
5) Once installed run supersu and a window should come up saying to update binaries...well...update them
6) When finished you will now have root, super user control, but outdated "BusyBox".
******* NOTE!!!​I have found out that some users were having problems after updating "BusyBox".
Update at your own risk!!!
BTW it worked for me with and without updating so I'm just giving feedback from other users.
7) Use "Play Store" again to download, install, and run "BusyBox" by "Stephen (Stericson)".
a) Let it run until "Smart Install" is finished.
b) Choose "Replace All (Symlinks all)" (not supposed to be able to but it worked for me )
b1) if it doesn't check then don't worry about it. its an extra step
8) Choose "Install" and wait for process to finish.
9) Congratulations! You now have Root, SuperSU, and BusyBox needed to use your phone to its (almost) full potential.
Now onto the Custom Recovery...​1) Go to the folder we created (in a land far far away...lol...couldn't help it ) and go into the dual recovery folder.
a) Run "install.bat" and (if we installed SuperSU) choose option #1 (if we installed SuperUser) choose option #2.
b) Follow instructions until you get success message. (see above for freeze or errors fixes at 1-a)
2) Congrats again! this time you now have a dual recovery!
a) I recommend installing "NDRUtils [root]" by "CamberCreek", it makes things much easier with your new found recoveries.
Here is my who's who and thank you's for this post. (this is in order of use in guide not relevance or importance)​1) XDA for such a great site!
2) Sony Mobile for a great phone and PC Companion.
3) zxz0O0 for his Easy Root Tool v12.4 without which I would have been lost.
4) [NUT]'s Z1-lockeddualrecovery2.8.3-RELEASE.installer.zip recoveries woot!
5) Chainfire for SuperSU the force in this rooted world.
6) Stephen (Stericson) for BusyBox the gears that keep us going.
7) CamberCreek for NDRUtils [root] making Xperia recoveries easier since....
8) Bin4ry & Androxyde for Flashtool making time travel possible?
9) And anyone else i might have missed.
Hope this helps those that were stuck like myself trying to get my phones true power unlocked!
***** NOTE!!!​I'm not sure if its just me/my phone/everyone's phone but i have noticed while working to get adb to recognize my device my usb debugging would seem to not be working (adb devices). If anyone has some feed back about this problem i would love to hear. BTW my device is less then 2 months old.

Ok, so you updated and now want to root? Well great news! We can get you downgraded to "14.4.B.0.37" so you can rock like the rest of them!​
1) Download, install "flashtool.net/downloads.php".
2) Download "storagecow.eu/Xda/Sony/Xperia%20Z1s/C6916_14.4.B.0.37_T-Mobile.ftf".
3) Move "C6916_14.4.B.0.37_T-Mobile.ftf" to folder "C:\Users\(your name)\.flashTool\firmwares".
4) Run "Flashtool" and wait for loading to finish.
a) Connect your device and Flashtool should recognize it and show that it is connected and has debugging turned on.
1a) If debugging is off then go to "Developer Settings" again and turn off then back on the "USB Debugging" option.
b) Click the lightning bolt in the top left area.
c) Choose "Flashmode" and click "Ok".
d) On the left should be the files you moved, choose "", uncheck the "DATA" box on the right side, and lastly choose "Flash".
e) When it says to turn "Off" your device and enter "Flash mode", turn off and wait for the charging screen (if connected still) or it to fully turn off.
f) Disconnect device and hold down "Vol. Down" and plug device back in. When you see your charging lights show/flash a few times you should have a blank screen and no lights.
g) Flashtool should have automatically started flashing now.
h) When finished exit flashmode by removing usb and holding the power button down to turn on. If it dont vibrate after a few seconds just release power and try again.
5) Felicitations! You should not be running "14.4.B.0.37" and are now able to follow above guide!

Forgot to mention that once finished rooting with above method you can upgrade to latest (as of this post) and still keep root. happy rooting

theshadower10 said:
This is my NOOB friendly version for rooting and installing Dual Recovery on a Sony Xperia Z1S (C6916).
First things first, I have written this entire this myself and have only used links from other posts here on XDA.
The thank you's will be at the end of this post.
Ok, Now onto the real reason your here...
Follow these steps to pre-pair your Z1S for the road ahead...​
1) Go to "Settings-About Phone".
Be sure your "Model Number" is "C6916".
Your "Build Number" is "14.4.B.0.37".
If your "Build Number" is different then see 2nd post for "How to Downgrade/Upgrade Build Number"
2) Click "Build Number" about 7 times (I think) to unlock "Developer Mode".
3) Go back to "Settings" screen.
Second option from the bottom should now be "Developer Options".
5) Enter this new screen and enable "USB Debugging".
6) Go back to "Settings" and enter "Security".
Enable "Unknown Sources" and disable "Verify Apps".
7) Go to "support.sonymobile.com/us/tools/pc-companion/"
Download, Install, plug device in, and it should detect and install drivers for your Z1S.
8) Download & Extract "forum.xda-developers.com/showthread.php?t=2784900" to a folder on the desktop (Name folder something easy like Z1S).
9) Download & Extract "Z1-lockeddualrecovery2.8.3-RELEASE.installer.zip" from "nut.xperia-files.com/" by clicking the "XZDualRecovery" to the same folder from step #8 (keeping separate folders inside to avoid confusion).
Well that seemed like allot now didn't it? Well the worst is over (hopefully).
Follow the below steps to root your phone...​
1) On computer go to the folder where you extracted "Easy Root Tool v12.4"
Run file called "install.bat"
Wait for it to load and follow the on-screen instructions to gain root.
Notes!!!
a) If at any time it seems like the tool has frozen, it probably has.
Wait for at least 1 minute and then click the red X in the top right of the window to close.
Press "Ctrl+Alt+Delete" and select "Start Task Manager" (depending upon windows version).
Choose the "Processes" tab and look for "abd.exe".
Choose it and then click "End Process" and confirm in the new window.
If you do not find "adb.exe" or you have killed it already then repeat step 1.
2) Once Easy Root Tool v12.4 has completed and shows a successes message you will be rooted! But we cant just use it as it is now, its "SuperSU Binary" is outdated.
3) Unplug usb and reboot your phone.
4) Once rebooted, go to the "Play Store" and search for and download "supersu" by "Chainfire" (support him if you can )
5) Once installed run supersu and a window should come up saying to update binaries...well...update them
6) When finished you will now have root, super user control, but outdated "BusyBox".
******* NOTE!!!​I have found out that some users were having problems after updating "BusyBox".
Update at your own risk!!!
BTW it worked for me with and without updating so I'm just giving feedback from other users.
7) Use "Play Store" again to download, install, and run "BusyBox" by "Stephen (Stericson)".
a) Let it run until "Smart Install" is finished.
b) Choose "Replace All (Symlinks all)" (not supposed to be able to but it worked for me )
b1) if it doesn't check then don't worry about it. its an extra step
8) Choose "Install" and wait for process to finish.
9) Congratulations! You now have Root, SuperSU, and BusyBox needed to use your phone to its (almost) full potential.
Now onto the Custom Recovery...​1) Go to the folder we created (in a land far far away...lol...couldn't help it ) and go into the dual recovery folder.
a) Run "install.bat" and (if we installed SuperSU) choose option #1 (if we installed SuperUser) choose option #2.
b) Follow instructions until you get success message. (see above for freeze or errors fixes at 1-a)
2) Congrats again! this time you now have a dual recovery!
a) I recommend installing "NDRUtils [root]" by "CamberCreek", it makes things much easier with your new found recoveries.
Here is my who's who and thank you's for this post. (this is in order of use in guide not relevance or importance)​1) XDA for such a great site!
2) Sony Mobile for a great phone and PC Companion.
3) zxz0O0 for his Easy Root Tool v12.4 without which I would have been lost.
4) [NUT]'s Z1-lockeddualrecovery2.8.3-RELEASE.installer.zip recoveries woot!
5) Chainfire for SuperSU the force in this rooted world.
6) Stephen (Stericson) for BusyBox the gears that keep us going.
7) CamberCreek for NDRUtils [root] making Xperia recoveries easier since....
8) Bin4ry & Androxyde for Flashtool making time travel possible?
9) And anyone else i might have missed.
Hope this helps those that were stuck like myself trying to get my phones true power unlocked!
***** NOTE!!!​I'm not sure if its just me/my phone/everyone's phone but i have noticed while working to get adb to recognize my device my usb debugging would seem to not be working (adb devices). If anyone has some feed back about this problem i would love to hear. BTW my device is less then 2 months old.
Click to expand...
Click to collapse
Ugh, where were you when I was stuck on 4.4? :laugh: I ended up downgrading my c6916 to 4.3 when I rooted it, it was the only way I could seem to achieve root. Hopefully this article will help someone out!
I myself haven't experienced any issues with adb/debugging, but maybe it's because I'm on a different os build.
So grateful for the EasyRoot tool!

Glad this could help you and thanks for the feedback

Thank you for this! I just got the lollipop update notification but wanted to double check to see if I could root before updating. Glad I did!
Two questions...
This file.... Z1-lockeddualrecovery2.8.3-RELEASE.installer.zip I cannot find. I can only find the 2.8.15 version. Will that do?
Also... Since I just got the lollipop update. Can I OTA to that and keep root?

silentsnow31802 said:
Thank you for this! I just got the lollipop update notification but wanted to double check to see if I could root before updating. Glad I did!
Two questions...
This file.... Z1-lockeddualrecovery2.8.3-RELEASE.installer.zip I cannot find. I can only find the 2.8.15 version. Will that do?
Also... Since I just got the lollipop update. Can I OTA to that and keep root?
Click to expand...
Click to collapse
Yes, that version is fine and will work. Also, I will update this soon. Just been busy with work so haven't had time as of yet. Also if you update you will loose root and have to start over again. Hope this helped.

So I am stuck..
Hey. So I was on 4.5 Lolipop and decided to follow the guide, the 2nd one first of course. And now I am in a Boot loop. and stuck.
Any suggestions or help ?
BTW i really do not want to wipe everything using the companion software. ...Did not fully back it up :/

me too
dweller02 said:
Hey. So I was on 4.5 Lolipop and decided to follow the guide, the 2nd one first of course. And now I am in a Boot loop. and stuck.
Any suggestions or help ?
BTW i really do not want to wipe everything using the companion software. ...Did not fully back it up :/
Click to expand...
Click to collapse
did you get any solution to stop dat ?
---------- Post added at 01:16 PM ---------- Previous post was at 01:11 PM ----------
theshadower10 said:
Ok, so you updated and now want to root? Well great news! We can get you downgraded to "14.4.B.0.37" so you can rock like the rest of them!​
1) Download, install "flashtool.net/downloads.php".
2) Download "storagecow.eu/Xda/Sony/Xperia%20Z1s/C6916_14.4.B.0.37_T-Mobile.ftf".
3) Move "C6916_14.4.B.0.37_T-Mobile.ftf" to folder "C:\Users\(your name)\.flashTool\firmwares".
4) Run "Flashtool" and wait for loading to finish.
a) Connect your device and Flashtool should recognize it and show that it is connected and has debugging turned on.
1a) If debugging is off then go to "Developer Settings" again and turn off then back on the "USB Debugging" option.
b) Click the lightning bolt in the top left area.
c) Choose "Flashmode" and click "Ok".
d) On the left should be the files you moved, choose "", uncheck the "DATA" box on the right side, and lastly choose "Flash".
e) When it says to turn "Off" your device and enter "Flash mode", turn off and wait for the charging screen (if connected still) or it to fully turn off.
f) Disconnect device and hold down "Vol. Down" and plug device back in. When you see your charging lights show/flash a few times you should have a blank screen and no lights.
g) Flashtool should have automatically started flashing now.
h) When finished exit flashmode by removing usb and holding the power button down to turn on. If it dont vibrate after a few seconds just release power and try again.
5) Felicitations! You should not be running "14.4.B.0.37" and are now able to follow above guide!
Click to expand...
Click to collapse
Hey i was running at lollipop 5.0.2.while i was using the second method first my mobile is looping after flashing...kindly tell me a solution

sorry for not a faster response...haven't had internet for awhile
anyways, for above 2 posts...i had updated to 5.0.2 and had to downgrade myself.
i had followed the same thing as above just updated the programs and apps from their respective owners.
i had no issues and have even upgraded back up to 5.0.2 using a different guide found on xda.
cant remember for the life of me what post it was though...
since i still have no internet and am typing this on friends laptop, i would suggest searching for other guides here to find one.

My apologies beforehand: I have Xperia Z1S (C6916, Android 5.0.2, Build #: 14.5.B.0.247), unlocked bootloader, Android Lollipop & would like to root my phone after first downgrading it. Viewing this post, I would like to know where I can get access to the files mentioned in this post. Or am I a year too late?

he has mentioned the links to the files
1)"forum.xda-developers.com/showthread.php?t=2784900" for Easy root tool
(you can even try kingroot "https://kingroot.net/" if you want,i used kingroot to root my Z1)
2) "nut.xperia-files.com/" for XZdualrecovery
3)use playstore for downloading Superuser by chainfire
4)"support.sonymobile.com/us/tools/pc-companion/" for pc companion

How I installed Marshmallow to Nexus 4...

I did this 4 days ago and only published this now as I wanted to make sure it was stable and be as close to stock (aka pure Google experience). Only problem I have now is "Now on Tap" doesn't seem to work. Advise from those in the know if appreciated. Credits to those in their respective links I've included here.
-------
How I installed Android 6.0 (Marshmallow) on my Nexus 4...
I used Windows 7 as the base platform as all the tools needed are easily found on this platform.
WARNING: You will lose all data in phone, backup as necessary. I will not be responsible for this HOWTO, do so at your own risk. Yes, it worked for me. Your mileage may vary...
A. Prior to building/installing the Marshmallow build, you will need the following.
A.1. Install ADB and FASTBOOT tools.
These are the tools used to install Marshmallow on your phone. You can either install the full Android SDK or get them from this XDA thread at URL http://forum.xda-developers.com/showthread.php?t=2317790
A.2. Install WinRAR.
You will need to use a tool called WinRAR to extract or replace certain files in an archive. You can download a copy from URL http://www.win-rar.com/
A.3. Download a Mako Google factory image of Lollipop at URL https://developers.google.com/android/nexus/images?hl=en#occam
We are going to modify the factory image of a Lollipop build. To upgrade my Mako, I used the LMY48M build.
A.4. Download the WORKING IMAGE of Android M on Nexus 4
Get the image file from URL http://dmitry.gr/index.php?r=06.+Thoughts&proj=02.+Android+M+on+Nexus4
You will get an archive called "MakoM_bin_v2.zip" file. If there is a newer version, use that instead but I used this version when I installed on my Mako.
A.5. Download TWRP for Mako
Get the TeamWin Recovery Project (TWRP) v2.8.7.0 from URL https://dl.twrp.me/mako/twrp-2.8.7.0-mako.img
A.6. Download the Google Apps (not provided in the AOSP builds).
Get the file "gapps-mm-fix.zip" from URL https://www.androidfilehost.com/?fid=24052804347833783
A.7. Download a patched kernel image that allows you to install SuperSU root.
Get the file "Fixed_Data_root.img" from URL https://www.androidfilehost.com/?fid=24052804347833767
A.8. Download a fix for Location services (GPS) not working.
Get the file "framework-res.apk" from URL http://forum.xda-developers.com/showpost.php?p=63229334&postcount=434
A.9. Download the root manager utility.
Get the file "BETA-SuperSU-v2.52.zip" from URL http://download.chainfire.eu/743/SuperSU/BETA-SuperSU-v2.52.zip
B. Checklist
B.1. If you have downloaded everything, you should have a list of the following:
- minimal_adb_fastboot_v1.3.1_setup.exe
- wrar521.exe
- occam-lmy48m-factory-03ae06e5.tgz
- MakoM_bin_v2.zip
- twrp-2.8.7.0-mako.img
- gapps-mm-fix.zip
- Fixed_Data_root.img
- framework-res.apk
- BETA-SuperSU-v2.52.zip
C. Installation and building the installer
C.1. Install the "minimal_adb_fastboot_v1.3.1_setup.exe" and "wrar521.exe" installers, leave settings as default.
C.2. Extract the content of file "occam-lmy48m-factory-03ae06e5.tgz" using WinRAR, it'll create a folder called "occam-lmy48m". Rename "occam-lmy48m" to "mako-marshmallow".
C.3. Extract the content of file "MakoM_bin_v2.zip" and you should get the following files:
- system.img
- Choose either "n4_lte_modem.img" or "normal_modem.img" depending if you want LTE support or just 3G (UMTS) support and rename that file to "radio-mako-m9615a-cefwmazm-2.0.1701.07.img"
C.4. Rename the file "twrp-2.8.7.0-mako.img" to "recovery.img", and "Fixed_Data_root.img" to "boot.img"
C.5. Replace the "radio-mako-m9615a-cefwmazm-2.0.1701.07.img" file inside the "mako-marshmallow" folder with our "radio-mako-m9615a-cefwmazm-2.0.1701.07.img" which we extracted from file "MakoM_bin_v2.zip"
C.6. Open the "image-occam-lmy48m.zip" file and replace the following files which we downloaded from the twrp.me or dimitry.gr site. They are:
- boot.img
- system.img
- recovery.img
C.7. Open a command shell:
Start -> Run -> cmd
From the command shell, go to the folder called "mako-marshmallow"
C.8. Make sure the Nexus 4 has at least 80% battery and restart the phone into bootloader mode (by switching off the phone, the pressing the on button and at the same time pressing the volume down button). To confirm you are in bootloader mode, type in the command:
fastboot devices
You should now see the output "xxxxxxxxxxxxxxxx fastboot" appear, where "xxxxxxxxxxxxxxxx" is the serial number that appears on your Nexus 4 screen. They should be the same and you should only have one line appearing, disconnect any other device if they appear on the list.
C.9. Install the image you just build by running the script "flash-all.bat". A Series of statuses will appear on the screen. Do not disconnect the phone from the cable and let the script install everything. If done correctly, you will find the Nexus 4 rebooting. WARNING: This will erase all user data on your Nexus 4!
C.10. Once you see the Home screen of Marshmallow on your Nexus 4, go to Settings -> About Phone and tap the BUILD number seven (7) times. When you go back to the Settings screen, just above the "About Phone" is a new menu item called "Developer Options".
C.11. Go to Settings -> Developer Options and enable "USB debugging". To ensure debugging is on, go to the command shell and type:
adb devices
It sure display the list of devices with the same serial number and should have the word "device" next to the serial number. You will be prompted on the phone if you want to allow this connection.
C.12. Make sure the USB is connected in MTP mode (Transfer files mode). In windows file maanger (Press the Win-E keys), you will see a device called "Nexus 4". Open it and in the "Internal storage", go to the "Download" folder and copy the following files:
- gapps-mm-fix.zip
- framework-res.apk
- BETA-SuperSU-v2.52.zip
Then, in a command shell, issues the command:
adb reboot bootloader
C.13. From the bootloader screen, press the volume down button until the option "Recovery" appears, then press the Power button once to boot into TWRP/Recovery.
C.14. In TWRP, select to install the file "gapps-mm-fix.zip" and "BETA-SuperSU-v2.52.zip" from the "Download" folder. Once completed, press the "Reboot" button that appears in TWRP.
C.15. When the phone restarts. Go to Settings -> Backup & reset and reset the whole phone. If you get a error message from the "Setup Wizard", press the Open-apps (ie. the square softkey on the screen) and you should see the "Settings" pane.
C.16. Once the phone restart from the master reset exercise. You will be prompted as if you just switched on a new phone. Fill in as necessary until you get to the Home screen.
C.17. We will need to replace a file to get Location Services (GPS) working. From you command shell:
adb root
adb remount
adb shell
cp /sdcard/Download/framework-res.apk /system/framework/
exit
adb reboot
C.18. I disabled the following apps (drag the app to the "App Info" button, and press the "Disable" button) for the following and replaced the with similar app from Google Play (name in brackets). This was done as the built in apps kept crashing every few minutes or didn't work as expected. The apps are:
- Browser (Chrome Browser)
- Clock (Clock)
- Camera (Google Camera)
- Calendar (Google Calendar)
- Contacts (Google Contacts)
- Music (Google Play Music)
- Gallery (Google Photos)
- Search (Google)
- EMail (GMail)
C.19. Restart phone and you're ready to experience a stable (close to Google stock) build of Marshmallow on your Mako (Nexus 4).
C.20. Fixing the "Google Now on Tap" not working problem (thanks to gamekid94).
Go to Settings -> Apps
- Tap on the "Gear" (icon on the top right) -> Default Apps -> Assist & voice input -> Assist app
- Select "None", then select "Google App".
Go to Settings -> Google -> Search & Now -> Voice
- Enable "Now on Tap"
C.21. Install and customize as you see fit.

While this can probably be useful to new users I don't think it belongs in the development subforum. A better place for it would probably be the general subforum.

OR... Or.. Or- You could just install a custom M ROM via flashing in TWRP. Much more easier lol.
Use Nexus Root Toolkit to backup everything, unlock bootloader, flash TWRP, and Root. Download Custom M ROM and Gapps, reboot to recovery, make a backup, wipe everything except internal storage, flash ROM. Done.
No need for extracting everything, ridiculous ADB commands, etc.

thanks, this is usefull to new users and detailed to avoid any doubt. will try

ajack2001my said:
I did this 4 days ago and only published this now as I wanted to make sure it was stable and be as close to stock (aka pure Google experience). Only problem I have now is "Now on Tap" doesn't seem to work.
Click to expand...
Click to collapse
Here's how i managed to get Now on Tap to work :
1. Go to settings .
2. Open "Apps" from the settings menu.
3. Tap on the "Gear" icon on the top right.
4. Select "Default Apps" and open "Assist and voice input".
5. Here, tap on Assist app, set it to None and then Back to google app.
Also, make sure that Now on Tap is switched on in the settings menu of the Google App.

It now works thanks...

Thank you so much for the nice post.
I got stuck up at C12. I do see the Nexus 4 in the as one of the devices connected. However when I click on it, I don't see any folders under it called as "internal storage", also when I try to copy these files (as in C12) I get an error "Cannot copy item - The device has stopped responding or has been disconnected". I am stuck here, any direction here is well appreciated.

mahavirvemuri said:
Thank you so much for the nice post.
I got stuck up at C12. I do see the Nexus 4 in the as one of the devices connected. However when I click on it, I don't see any folders under it called as "internal storage", also when I try to copy these files (as in C12) I get an error "Cannot copy item - The device has stopped responding or has been disconnected". I am stuck here, any direction here is well appreciated.
Click to expand...
Click to collapse
Connect using MTP mode...

ajack2001my said:
Connect using MTP mode...
Click to expand...
Click to collapse
Thanks a ton, that resolved it

Milion Thanks..!!
Thanks a lot..

Title should be "how i installed marshmallow the most difficult way possible"
Sent from my Nexus 4 using Tapatalk

I thought I'd post this in hope that people will appreciate how much effort needs to be put into it, yet simple enough to allow newbies to try building something. It's also a very light build without all the unnecessary apps which people end up uninstalling or disabling.
People here can always choose a ready build and ignore my post. I rather those with more experience help with problems in this build instead of condemning it.
If the senior members here feel this is unnecessary, I will delete this thread.

Yes, thank you for this tutorial, very much appreciated

question N4 with Marshmallow
Hi ajack2001my,
How is working N4 with the android M ? What is your experience about battery., stabilty .... afther two months ?
thanks
Pedro

ajack2001my said:
I did this 4 days ago and only published this now as I wanted to make sure it was stable and be as close to stock (aka pure Google experience). Only problem I have now is "Now on Tap" doesn't seem to work. Advise from those in the know if appreciated. Credits to those in their respective links I've included here.
-------
How I installed Android 6.0 (Marshmallow) on my Nexus 4...
I used Windows 7 as the base platform as all the tools needed are easily found on this platform.
WARNING: You will lose all data in phone, backup as necessary. I will not be responsible for this HOWTO, do so at your own risk. Yes, it worked for me. Your mileage may vary...
A. Prior to building/installing the Marshmallow build, you will need the following.
A.1. Install ADB and FASTBOOT tools.
These are the tools used to install Marshmallow on your phone. You can either install the full Android SDK or get them from this XDA thread at URL http://forum.xda-developers.com/showthread.php?t=2317790
A.2. Install WinRAR.
You will need to use a tool called WinRAR to extract or replace certain files in an archive. You can download a copy from URL http://www.win-rar.com/
A.3. Download a Mako Google factory image of Lollipop at URL https://developers.google.com/android/nexus/images?hl=en#occam
We are going to modify the factory image of a Lollipop build. To upgrade my Mako, I used the LMY48M build.
A.4. Download the WORKING IMAGE of Android M on Nexus 4
Get the image file from URL http://dmitry.gr/index.php?r=06.+Thoughts&proj=02.+Android+M+on+Nexus4
You will get an archive called "MakoM_bin_v2.zip" file. If there is a newer version, use that instead but I used this version when I installed on my Mako.
A.5. Download TWRP for Mako
Get the TeamWin Recovery Project (TWRP) v2.8.7.0 from URL https://dl.twrp.me/mako/twrp-2.8.7.0-mako.img
A.6. Download the Google Apps (not provided in the AOSP builds).
Get the file "gapps-mm-fix.zip" from URL https://www.androidfilehost.com/?fid=24052804347833783
A.7. Download a patched kernel image that allows you to install SuperSU root.
Get the file "Fixed_Data_root.img" from URL https://www.androidfilehost.com/?fid=24052804347833767
A.8. Download a fix for Location services (GPS) not working.
Get the file "framework-res.apk" from URL http://forum.xda-developers.com/showpost.php?p=63229334&postcount=434
A.9. Download the root manager utility.
Get the file "BETA-SuperSU-v2.52.zip" from URL http://download.chainfire.eu/743/SuperSU/BETA-SuperSU-v2.52.zip
B. Checklist
B.1. If you have downloaded everything, you should have a list of the following:
- minimal_adb_fastboot_v1.3.1_setup.exe
- wrar521.exe
- occam-lmy48m-factory-03ae06e5.tgz
- MakoM_bin_v2.zip
- twrp-2.8.7.0-mako.img
- gapps-mm-fix.zip
- Fixed_Data_root.img
- framework-res.apk
- BETA-SuperSU-v2.52.zip
C. Installation and building the installer
C.1. Install the "minimal_adb_fastboot_v1.3.1_setup.exe" and "wrar521.exe" installers, leave settings as default.
C.2. Extract the content of file "occam-lmy48m-factory-03ae06e5.tgz" using WinRAR, it'll create a folder called "occam-lmy48m". Rename "occam-lmy48m" to "mako-marshmallow".
C.3. Extract the content of file "MakoM_bin_v2.zip" and you should get the following files:
- system.img
- Choose either "n4_lte_modem.img" or "normal_modem.img" depending if you want LTE support or just 3G (UMTS) support and rename that file to "radio-mako-m9615a-cefwmazm-2.0.1701.07.img"
C.4. Rename the file "twrp-2.8.7.0-mako.img" to "recovery.img", and "Fixed_Data_root.img" to "boot.img"
C.5. Replace the "radio-mako-m9615a-cefwmazm-2.0.1701.07.img" file inside the "mako-marshmallow" folder with our "radio-mako-m9615a-cefwmazm-2.0.1701.07.img" which we extracted from file "MakoM_bin_v2.zip"
C.6. Open the "image-occam-lmy48m.zip" file and replace the following files which we downloaded from the twrp.me or dimitry.gr site. They are:
- boot.img
- system.img
- recovery.img
C.7. Open a command shell:
Start -> Run -> cmd
From the command shell, go to the folder called "mako-marshmallow"
C.8. Make sure the Nexus 4 has at least 80% battery and restart the phone into bootloader mode (by switching off the phone, the pressing the on button and at the same time pressing the volume down button). To confirm you are in bootloader mode, type in the command:
fastboot devices
You should now see the output "xxxxxxxxxxxxxxxx fastboot" appear, where "xxxxxxxxxxxxxxxx" is the serial number that appears on your Nexus 4 screen. They should be the same and you should only have one line appearing, disconnect any other device if they appear on the list.
C.9. Install the image you just build by running the script "flash-all.bat". A Series of statuses will appear on the screen. Do not disconnect the phone from the cable and let the script install everything. If done correctly, you will find the Nexus 4 rebooting. WARNING: This will erase all user data on your Nexus 4!
C.10. Once you see the Home screen of Marshmallow on your Nexus 4, go to Settings -> About Phone and tap the BUILD number seven (7) times. When you go back to the Settings screen, just above the "About Phone" is a new menu item called "Developer Options".
C.11. Go to Settings -> Developer Options and enable "USB debugging". To ensure debugging is on, go to the command shell and type:
adb devices
It sure display the list of devices with the same serial number and should have the word "device" next to the serial number. You will be prompted on the phone if you want to allow this connection.
C.12. Make sure the USB is connected in MTP mode (Transfer files mode). In windows file maanger (Press the Win-E keys), you will see a device called "Nexus 4". Open it and in the "Internal storage", go to the "Download" folder and copy the following files:
- gapps-mm-fix.zip
- framework-res.apk
- BETA-SuperSU-v2.52.zip
Then, in a command shell, issues the command:
adb reboot bootloader
C.13. From the bootloader screen, press the volume down button until the option "Recovery" appears, then press the Power button once to boot into TWRP/Recovery.
C.14. In TWRP, select to install the file "gapps-mm-fix.zip" and "BETA-SuperSU-v2.52.zip" from the "Download" folder. Once completed, press the "Reboot" button that appears in TWRP.
C.15. When the phone restarts. Go to Settings -> Backup & reset and reset the whole phone. If you get a error message from the "Setup Wizard", press the Open-apps (ie. the square softkey on the screen) and you should see the "Settings" pane.
C.16. Once the phone restart from the master reset exercise. You will be prompted as if you just switched on a new phone. Fill in as necessary until you get to the Home screen.
C.17. We will need to replace a file to get Location Services (GPS) working. From you command shell:
adb root
adb remount
adb shell
cp /sdcard/Download/framework-res.apk /system/framework/
exit
adb reboot
C.18. I disabled the following apps (drag the app to the "App Info" button, and press the "Disable" button) for the following and replaced the with similar app from Google Play (name in brackets). This was done as the built in apps kept crashing every few minutes or didn't work as expected. The apps are:
- Browser (Chrome Browser)
- Clock (Clock)
- Camera (Google Camera)
- Calendar (Google Calendar)
- Contacts (Google Contacts)
- Music (Google Play Music)
- Gallery (Google Photos)
- Search (Google)
- EMail (GMail)
C.19. Restart phone and you're ready to experience a stable (close to Google stock) build of Marshmallow on your Mako (Nexus 4).
C.20. Fixing the "Google Now on Tap" not working problem (thanks to gamekid94).
Go to Settings -> Apps
- Tap on the "Gear" (icon on the top right) -> Default Apps -> Assist & voice input -> Assist app
- Select "None", then select "Google App".
Go to Settings -> Google -> Search & Now -> Voice
- Enable "Now on Tap"
C.21. Install and customize as you see fit.
Click to expand...
Click to collapse
thanks man

ladysuin said:
thanks man
Click to expand...
Click to collapse
Really?? You quoted the original post for this??

MM Update

was just wondering : has anyone got the MM update already ?
cheers

OTA update link: https://android.googleapis.com/pack...5e909bdec.signed-signed-sprat-ota-2576000.zip
This next part is assuming you have ADB installed on your computer. If you don't, google how to install ADB first.
To sideload the update:
1. Enable Developer Options: Settings>About>Tab Build Number 7x
2. Go back to the Settings Menu
3. Go into Developer Options (All the way at the bottom, below About)
4. Enable USB Debugging
5. Go to wherever ADB is installed on your PC (For me, it is C:\Program Files (x86)\Android\android-sdk\platform-tools\)
6. Shift+Right Click inside the folder, but not on a file in the folder, then click "Open command window here"
7. Type "adb devices"
8. At this point, on your watch, it should pop up a dialog asking if you would like to authorize the connection. Hit Always.
9. Type “adb reboot recovery”
10. On your watch, tap the screen once, then swipe down until you're hovering on “apply update from ADB.” then swipe to the right.
11. In the command prompt on your PC type “adb sideload” followed by a single space then drag and drop the zip to the command prompt window then hit Enter.
12. It will now begin installing the update on your device. Whatever you do, do not disconnect your watch from the computer or close the command prompt window.
13. Depending on the situation, your watch may or may not reboot automatically. If it doesnt, after it is done installing the update and goes back to the main Recovery menu, swipe to the right on "Reboot system now."
Click to expand...
Click to collapse

BTW I highly recommend forgetting your watch from the Android Wear app on your phone/tablet and factory resetting your watch after updating.
After I installed it, settings on the watch were funky, like it offering phone options which we shouldn't have without a speaker, and it wouldn't install the new Wear Messenger app that is included in the newest version of Google Messenger.

Dudash said:
OTA update link: https://android.googleapis.com/pack...5e909bdec.signed-signed-sprat-ota-2576000.zip
Click to expand...
Click to collapse
cool, thanks, have just installed it !
cheers

Dudash said:
OTA update link: https://android.googleapis.com/pack...5e909bdec.signed-signed-sprat-ota-2576000.zip
This next part is assuming you have ADB installed on your computer. If you don't, google how to install ADB first and since the zip file doesn't say which "version-from-version" it is for like they normally do, for example LCA43-from-LDZ22J, I'd recommend being on LCA43 before sideloading the update.
Click to expand...
Click to collapse
Someone correct me if I am wrong, but that OTA update is a full image unlike all previous updates. So, it should work as long as you have partition in place. Also, it looks like they added "new" features to the stock recovery. It has more options now.

aligatro2010 said:
Someone correct me if I am wrong, but that OTA update is a full image unlike all previous updates. So, it should work as long as you have partition in place. Also, it looks like they added "new" features to the stock recovery. It has more options now.
Click to expand...
Click to collapse
It is possible that you could flash it from an earlier build and end up with the same system. If you want to be a guinea pig for other people, be my guest
I was merely stating the safest way to not end up with a watch that won't go past the boot logo.
Also, since MM updates for other watches include the "version-from-version" text in the name of the update.zip, I assumed they just forgot to put it in the Gear Live .zip.

Dudash said:
It is possible that you could flash it from an earlier build and end up with the same system. If you want to be a guinea pig for other people, be my guest
I was merely stating the safest way to not end up with a watch that won't go past the boot logo.
Also, since MM updates for other watches include the "version-from-version" text in the name of the update.zip, I assumed they just forgot to put it in the Gear Live .zip.
Click to expand...
Click to collapse
Nope, they didn't forget, but its just a full image. I was able to sideload it to my watch after formatting the partitions(so no prev firmware at all).

Does anyone know if root is available already ?
Cheers !
Enviado desde mi Galaxy Nexus mediante Tapatalk

thagringo said:
Does anyone know if root is available already ?
Cheers !
Enviado desde mi Galaxy Nexus mediante Tapatalk
Click to expand...
Click to collapse
Haven't tried it on the latest version, but I think you can root it by installing latest supersu. Just need to remove the apk that comes with it, as it will crash on launch.

One thing I don't like about the new update is how they changed the "Simple" and "Incremental" watchfaces.
They used to have a daytime color (light blue), an evening color (yellowish-orange), and a nighttime color (dark blue/purple).
Now the colors/images are updated (more clouds) but there isn't an evening color anymore and it doesn't change to the nighttime one until like 10pm.
Kind of a strain on the eyes to see a light blue background after the sun goes down.
I'm curious why they removed the evening color.

thagringo said:
was just wondering : has anyone got the MM update already ?
cheers
Click to expand...
Click to collapse
Mine updated automatically. I left it charging and when I came back, there it was, waiting to be installed.
One thing though: it won't show starred contacts (favorites) anymore, which it did before the update, and I can't figure out how to fix it.
Anyone else notice this?

I got it. So far so good
Sent from my SM-G935P using XDA-Developers mobile app

[GUIDE] How to flash 1.5 update on LG Urbane (non-LTE version)

For some Urbane users, for whatever the reason may have been, they were unable to install the 1.5 OTA, the "dead" android continued to come up. This guide assumes that you have Minimal ADB and Fastboot installed on your computer, a guide that includes how to set your computer up for this is found HERE. This guide also assumes your watch is already on ADB debugging, etc, etc, else follow the previously mentioned guide.
READ ENTIRE GUIDE BEFORE YOU START. NEEDLESS TO SAY YOU'RE TRYING THIS AT YOUR OWN RISK..
Files needed:
- System
- Boot
- Recovery
(these are for 6.01 version, and can be found HERE with the 5.01 version).
- 1.5 update zip found HERE
1 - Connect your watch's charger to your PC and set your watch on the charger.
2- Open Minimal ADB and Fastboot, and type:
Code:
adb devices
and hit enter
3- If properly connected you should see something similar to "504KPJP00XXXX8 device".
4- Now type in:
Code:
adb reboot bootloader
and hit enter. The watch should reboot into the bootloader.
5- While in bootloader type:
Code:
fastboot flash system
and drag the System file you downloaded earlier to the Minimal ADB and Fastboot window, and hit enter.
6- When it's done installing type in:
Code:
fastboot reboot
and hit enter.
7 - Repeat steps 1-6 for EACH of the other two files: Boot and Recovery files you downloaded. Keep in mind that EACH TIME when you get to step 5 you must type in:
Code:
fastboot flash boot
for the Boot file, and
Code:
fastboot flash recovery
for the Recovery file respectively and drag their respective files to the window. So, to recap, do steps 1-6 for Boot, and 1-6 for Recovery. Got it? Good.
8- Get into bootloader mode again (see steps 2-4). Using the left and right (< >) arrows in bootloader screen on your watch look for "Recovery Mode" and hit the (o) option.
9- Now you will see the good ol' "dead" android. Fear not, touch the screen and you should get some options. Sliding your finger up or down scroll to "Mount /system", and swipe left or right.
10- Now slide down to "Apply update from ADB" and slide left or right to get into ADB sideload mode.
11- Once in sideload mode go to Minimal ADB and Fastboot window and type in:
Code:
adb sideload
AND drag the 1.5 update zip file you downloaded onto the screen, THEN hit enter.
12- If done properly the Minimal ADB and Fastboot window will start showing you some progress and so will the watch. wait until it's done. When it's done reboot your watch. Be advised it will take a little bit to power on, be patient!
You're all done!
Now you can go back and install TWRP, root, etc..
I want to point out that 1 or many of the above steps may not be necessary but this is exactly what I did to successfully flash the update. No wiping, no factory reset was necessary.

Can you please share how to disable auto update after installing 1.5 on urbane? I successfully downgraded but in couple of hours my watch updated back to AW2.

caughtmountain said:
Can you please share how to disable auto update after installing 1.5 on urbane? I successfully downgraded but in couple of hours my watch updated back to AW2.
Click to expand...
Click to collapse
Here. By the way what's so bad about 2.0?

How do I update to M1D65H (the last aw 1.5 update) ?
Thanks for the detail tutorial. BTW the aw 1.5 version given in your link (MM) was MWD48B.
How to find and upgrade to the last aw 1.5 just before the aw 2.0 was released. i.e M1D65H
Update : Somehow I managed to upgrade to M1D63G (OTA package - using adb sideload), after which I could not able to find further updates.
Updating to M1D65H (OTA package using "adb sideload") directly fails.
---------- Post added at 03:04 AM ---------- Previous post was at 02:58 AM ----------
cubandanger05 said:
Here. By the way what's so bad about 2.0?
Click to expand...
Click to collapse
I keep getting the notifications even after running this APP in my watch.
After running this APP, the message says disabled update and please restart.
But after some time I get back the "Notification for the Update"
Does the watch requires to be rooted ?

razebond said:
Thanks for the detail tutorial. BTW the aw 1.5 version given in your link (MM) was MWD48B.
How to find and upgrade to the last aw 1.5 just before the aw 2.0 was released. i.e M1D65H
Update : Somehow I managed to upgrade to M1D63G (OTA package - using adb sideload), after which I could not able to find further updates.
Updating to M1D65H (OTA package using "adb sideload") directly fails.
---------- Post added at 03:04 AM ---------- Previous post was at 02:58 AM ----------
I keep getting the notifications even after running this APP in my watch.
After running this APP, the message says disabled update and please restart.
But after some time I get back the "Notification for the Update"
Does the watch requires to be rooted ?
Click to expand...
Click to collapse
I believe so, yes.

Have installed updatedisabler.apk on both phone and watch (watch is rooted) both come up with "Check your watch to find the application". Still get nags about updating?
Has anyone got this to work?

updatedisabler is not working, somebody knows how to uninstall it?

First, it's slow and buggy. Google Assistant takes several seconds to load before you can speak to it, sometimes so long the screen times out before you can speak your command. I always get a notification vibration, but rarely get the notification card, destroying the most useful smart feature of the watch, and instead of cards peaking, I always have a full screen card of whatever song or podcast I'm listening to, that is persistent and blocks my watch face, destroying the most useful feature of not smart watches (since I can't see the time). But, those apps run on the watch natively by default, so if I try to start playing music or podcasts it can only playback locally from the watch, not start the playback on the phone. Do disturb on the watch is also now separate from dnd on the phone, which means when going into meetings I have to silence both independently. In short, what's wrong with aw2? Everything! Oh, and my battery just says 50% all the time since the update. Totally garbage.

Hello. I'm getting an error that it's locked and so I can't flash the file to downgrade. Does the bootloader need to be unlocked ????? I'm currently on AW 2 and I would like to flash back down. Thanks.

Im confused, I know how to flash .img files but what do I do with this 1.5 update file? I currently downgraded to 1.3 but thats a little too old for my liking.

mexiken said:
Hello. I'm getting an error that it's locked and so I can't flash the file to downgrade. Does the bootloader need to be unlocked ????? I'm currently on AW 2 and I would like to flash back down. Thanks.
Click to expand...
Click to collapse
Yes, your bootloader needs to be unlocked

RunNgun42 said:
Im confused, I know how to flash .img files but what do I do with this 1.5 update file? I currently downgraded to 1.3 but thats a little too old for my liking.
Click to expand...
Click to collapse
If you're on stock 1.3 you should be able to flash the update following the adb sideload steps

Hi guys. I tried to follow the steps, but the "adb sideload" part is not working. The watch presents an error: "can't mount /system". Any tips? Is there any 1.5 full rom out there?

[fixed]

How To Guide Realme GT Neo 2T (RMX3357) Guide for BL Unlock/Root/Debloat/Android Auto/Hey Google

NOTE - THIS GUIDE IS ONLY FOR THE REALME GT NEO 2T (RMX3357)
For the X7 Max or GT Neo/GT Neo Flash Edition, please refer to the excellent guide by @mahotlov found here.
(The X7 Max subforum seemed the best place for this guide, but please let me know if there's a better place!)
------------------------------------------------------------------------------------------------------------------​Preamble: I recently purchased a Realme GT Neo 2T under the assumption it could take Realme X7 Max ROMs. The specs and design were an exact match, and since Realme has a history of releasing existing phones with new model numbers and sparklier plastic, I felt pretty good about compatibility. I quickly learned I was mistaken - both stock and custom ROMs for the X7 Max cause the display on the Neo 2T to stop working. Flashing back the stock bootloader fixed the display, but the phone would only boot into recovery, which had no touch support. Flashing the stock recovery brought back touch support, but nothing I tried could get the ROM to boot. Clearly there are changes under the hood.
Unfortunately, that left precious few options for turning the Neo 2T into a usable phone. The hardware is amazing for the price, and ColorOS is pretty decent, but the amount of non-removable bloatware and lack of Android Auto and Hey Google to activate Google Assistant was a dealbreaker for me. In the end, I decided to take matters into my own hands.
------------------------------------------------------------------------------------------------------------------​
This guide will show you how to:
- Unlock your bootloader.
- Root your phone. (Magisk)
- Bypass SafetyNet. (Universal SafetyNet Fix Magisk module)
- Install Android Auto and Google apps as system apps. (BusyBox-NDK and Terminal Systemizer Magisk modules)
- Remove Realme bloatware. (ADB)
- Flash device with SP Tools and stock ROM to recover from a softbrick or restore to factory state. (SP Tools)
(Some sections are still being written and will be available soon.)
------------------------------------------------------------------------------------------------------------------
THE GUIDE ASSUMES YOU ARE USING WINDOWS 10. SOME STEPS MAY BE DIFFERENT FOR OTHER OPERATING SYSTEMS
PLEASE READ THROUGH ALL INSTRUCTIONS FIRST BEFORE PROCEEDING. ALL REQUIRED FILES CAN BE FOUND ATTACHED TO THIS POST.
UNLOCKING YOUR BOOTLOADER WILL VOID YOUR WARRANTY. THIS PROCESS WILL WIPE ALL DATA FROM YOUR PHONE. I AM NOT RESPONSIBLE FOR LOST DATA. I AM ALSO NOT RESPONSIBLE IF YOU DAMAGE OR KILL YOUR DEVICE, YOUR PROPERTY, YOUR LOVED ONES OR YOURSELF BY FOLLOWING THESE INSTRUCTIONS. YOU HAVE BEEN WARNED!
------------------------------------------------------------------------------------------------------------------​
STEP 1: Unlock your bootloader.
Spoiler: Click here for instructions.
First, we need to enable developer mode. On the Neo 2T:
- Open Settings.
- Choose "About Phone".
- Choose "Version - Baseband & Kernel"
- Tap "Build Number" until developer mode is enabled.
Next, we need to turn on USB Debugging and allow OEM Unlock. On the Neo 2T:
- Go back to Settings.
- Choose "Additional Settings".
- Choose "Developer Options".
- Turn on "OEM Unlock" and "USB Debugging".
We need to get the Deep Testing app to unlock the bootloader. On your PC:
- Download "DeepTesting_GT_NEO_2T.apk" attached to this post.
- Plug the Neo 2T into your PC.
Now, we need to allow file transfers. On the Neo 2T:
- Select "Transfer Files" on the "Use USB to" popup.
Time to send the .apk to the Neo 2T. On your PC:
- Copy the "DeepTesting_GT_NEO_2T.apk" file you downloaded to the "Download" folder on the internal storage of the Neo 2T.
We're ready to request unlocking of the bootloader. On the Neo 2T:
- Open the "File Manager" app.
- Choose the "APK" option.
- Find "DeepTesting_GT_NEO_2T.apk" and open it.
- Follow the instruction to install the app. You may need to allow installing from the "File Manager" app.
- Once install is finished, launch the app.
- Click "Start Applying".
- Tick the checkbox to agree to the disclaimer. Due to a bug, the disclaimer text itself may or may not appear.
- When you see "Application Submitted", click "Back."
- Go grab a coffee. It can sometimes take up to an hour for the bootloader unlock request to be approved.
- You can close the app and use your phone as normal in the meantime. Periodically open the app and click "Query Verification Status" to check your request. Once you see "Application Approved" we are done with this step.
- Unplug the Neo 2T from your PC.
- Click "Start Deep Testing".
- The Neo 2T will reboot into "Fastboot" mode. You should see a black screen with small white text.
- Plug the Neo 2T into your PC.
Now we need to install the ADB drivers. On your PC:
- Download "ADB_DRIVERS.zip" attached to this post.
- Unzip the files somewhere. Remember the location.
- Right-click on your start menu button and choose "Device Manager".
- Find the device called "Android".
- Right-click the device and choose "Update Driver".
- Choose "Browse My Computer for Drivers".
- Choose "Let Me Pick From a List of Available Drivers On My Computer".
- Click "Have Disk".
- Click "Browse".
- Navigate to the folder where you extracted the files.
- Choose "android_winusb.inf".
- Choose "Android Bootloader Interface".
- Click "Finish" to close the driver wizard once it has finished.
We need to use Fastboot to unlock the bootloader. On your PC:
- Download "ADB_FASTBOOT.zip" attached to this post.
- Unzip the files somewhere. Remember the location.
- Open a command prompt pointing to the extracted files. (The fastest way to do this is to open the folder, then replace the file path with "cmd" end hit enter.)
- Enter this command to check that your phone is detected: fastboot.exe devices
- You should see your device represented by a long string of numbers and letters followed by "fastboot".
- If you don't see this, or it doesn't say "fastboot", double-check your USB cable or port, and make sure you installed the drivers as instructed previously.
- Enter this command: fastboot.exe flashing unlock
Your phone will now ask you to confirm unlocking of the bootloader. On the Neo 2T:
- REMINDER: THIS WILL WIPE ALL YOUR DATA!
- Read the text on the screen and follow the instructions to confirm the bootloader unlock.
Next we reboot the phone. On your PC:
- Enter this command: fastboot.exe reboot
- Your phone will now warn you during boot that the bootloader is unlocked.
- Unplug the Neo 2T from your PC.
Now we need to enter Fastboot again. On the Neo 2T:
- Allow the phone to fully boot to the initial setup wizard.
- Turn off the phone by holding down the power button until the power actions slider appears.
- Slide down to turn off the phone.
- While holding down Vol-, press and hold the power button.
- Release the power button when you feel the phone vibrate.
- Release the Vol- button when you have entered Fastboot mode. You should see a black screen with small white text.
- Plug the Neo 2T into your PC.
We will use Fastboot to get into recovery mode. On your PC:
- Open the folder where you extracted the "ADB_FASTBOOT.zip" (Done previously during Step 1: Unlock your bootloader.)
- Open a command prompt pointing to the extracted files. (The fastest way to do this is to open the folder, then replace the file path with "cmd" end hit enter.)
- Enter this command to check that your phone is detected: fastboot.exe devices
- You should see your device represented by a long string of numbers and letters followed by "fastboot".
- If you don't see this, or it doesn't say "fastboot", double-check your USB cable or port, and make sure you installed the drivers as instructed previously.
- Enter this command: fastboot.exe reboot recovery
- Wait for phone to reboot into recovery
Finally, we will wipe the data partition to ensure a clean state for future steps. On the Neo 2T:
- Select your language.
- Select "Wipe data".
- Select "Format data".
- Enter the code displayed on the screen.
- Select "Format".
- Data will be wiped. Select "OK" when finished. Phone will reboot.
- Once the phone has booted, proceed through the first time setup until you reach the home screen.
- Setup WiFi or verify/configure a data connection which will be needed for the next steps.
- If still plugged into your PC, or upon the next connection, the phone will show a popup to allow USB debugging. Check "always allow from this computer" and select OK.
- We can now move on to rooting!
STEP 2: Root your phone.
Spoiler: Click here for instructions.
First we need to reboot the phone into fastboot. On the Neo 2T:
- Unplug the Neo 2T from your PC.
- Turn off the phone by holding down the power button until the power actions slider appears.
- Slide down to turn off the phone.
- While holding down Vol-, press and hold the power button.
- Release the power button when you feel the phone vibrate.
- Release the Vol- button when you have entered Fastboot mode. You should see a black screen with small white text.
- Plug the Neo 2T into your PC.
We need to use Fastboot to root the phone. On your PC:
- Open the folder where you extracted the "ADB_FASTBOOT.zip" (Done previously during Step 1: Unlock your bootloader.)
- Open a command prompt pointing to the extracted files. (The fastest way to do this is to open the folder, then replace the file path with "cmd" end hit enter.)
- Enter this command to check that your phone is detected: fastboot.exe devices
- You should see your device represented by a long string of numbers and letters followed by "fastboot".
- If you don't see this, or it doesn't say "fastboot", double-check your USB cable or port, and make sure you installed the drivers as instructed previously.
- Enter this command: fastboot.exe flash boot magisk.img
- Enter this command: fastboot.exe flash vbmeta --disable-verity --disable-verification vbmeta.img
- Enter this command: fastboot.exe reboot
- Wait for phone to reboot.
Complete Magisk setup. On the Neo 2T:
- Open Magisk from your app drawer.
- Accept the request to install the full version of Magisk.
- Allow Magisk to install apps in the resulting popup.
- Open Magisk from your app drawer.
- Accept the request to reboot to complete installation.
- Once the phone has rebooted, the process is complete and we can move on to bypassing SafetyNet!
STEP 3: Bypass SafetyNet.
Spoiler: Click here for instructions.
First we grab the SafetyNet module for Magisk. On your PC:
- Download "safetynet-fix-v2.2.1.zip" attached to this post.
- Plug the Neo 2T into your PC.
Now, we need to allow file transfers. On the Neo 2T:
- Select "Transfer Files" on the "Use USB to" popup.
Time to send the .apk to the Neo 2T. On your PC:
- Copy the "safetynet-fix-v2.2.1.zip" file you downloaded to the "Download" folder on the internal storage of the Neo 2T.
We're ready to install the module. On the Neo 2T:
- Open the "Magisk" app.
- Open Settings.
- Turn on "Zygist (Beta)" and "Enforce DenyList".
- Exit settings.
- Go to the "Modules" tab.
- Select "Install From Storage".
- Find "safetynet-fix-v2.2.1.zip" and open it.
- Wait until installation of the module is complete.
- Click the "Reboot" button that appears to reboot the phone.
- Once the phone has rebooted, the process is complete and we can move on to installing Android Auto and Google apps as system apps!
STEP 4: Install Android Auto and and Google apps as system apps.
Spoiler: Click here for instructions.
First we grab the BusyBox-NDK and Terminal Systemizer modules for Magisk. On your PC:
- Download "busybox-v1.34.1.zip" attached to this post.
- Download "terminal_systemizer_v17.4.1.zip" attached to this post.
- Plug the Neo 2T into your PC.
Now, we need to allow file transfers. On the Neo 2T:
- Select "Transfer Files" on the "Use USB to" popup.
Time to send the .apks to the Neo 2T. On your PC:
- Copy the "busybox-v1.34.1.zip" file you downloaded to the "Download" folder on the internal storage of the Neo 2T.
- Copy the "terminal_systemizer_v17.4.1.zip" file you downloaded to the "Download" folder on the internal storage of the Neo 2T.
We're ready to install the BusyBox-NDK module. On the Neo 2T:
- Open the "Magisk" app.
- Go to the "Modules" tab.
- Select "Install From Storage".
- Find "busybox-v1.34.1.zip" and open it.
- Wait until installation of the module is complete.
- Click the back button.
We're ready to install the Terminal Systemizer module. On the Neo 2T:
- Go to the "Modules" tab.
- Select "Install From Storage".
- Find "terminal_systemizer_v17.4.1.zip" and open it.
- Wait until installation of the module is complete.
- Click the "Reboot" button to reboot the phone.
Time to get the Google Play Store app. On your PC:
- Download "Google_Play_Store_29.9.16-21.apk" attached to this post.
- Plug the Neo 2T into your PC.
Now, we need to allow file transfers. On the Neo 2T:
- Select "Transfer Files" on the "Use USB to" popup.
Time to send the .apk to the Neo 2T. On your PC:
- Copy the "Google_Play_Store_29.9.16-21.apk" file you downloaded to the "Download" folder on the internal storage of the Neo 2T.
We're ready to install the Google Play Store. On the Neo 2T:
- Open the "Files" app.
- Choose the "APK" option.
- Find "Google_Play_Store_29.9.16-21.apk" and open it.
- Follow the instruction to install the app. You may need to allow installing from the "File Manager" app.
- Once install is finished, launch the app.
We need to install our apps before we can systemize them. On the Neo 2T:
- Open the Google Play Store and sign in.
- Update any apps that have updates available.
- Use the Google Play Store to install Android Auto, Google Assistant, and the Google app.
We need to use ADB to systemize Android Auto and Google Assistant. On your PC:
- Open the folder where you extracted the "ADB_FASTBOOT.zip" (Done previously during Step 1: Unlock your bootloader.)
- Open a command prompt pointing to the extracted files. (The fastest way to do this is to open the folder, then replace the file path with "cmd" end hit enter.)
- Enter this command to check that your phone is detected: adb.exe devices
- You should see your device represented by a long string of numbers and letters followed by "device".
- If you don't see this, or it doesn't say "device", double-check your USB cable or port, and make sure you installed the drivers as instructed previously.
- Enter this command: adb shell
- Have your phone unlocked and at the ready, then enter this command: su
Allow root for ADB Shell. On the Neo 2T:
- Select "Forever" on the superuser request popup for Shell. Click "Grant".
Now we can systemize Android Auto and Google. On your PC:
- Enter this command: systemize
- Type 1 and hit enter to choose "Systemize Installed Apps (Listed)".
- You should see a numbered list of apps after a few seconds of loading. Find the numbers for "Android Auto" and "Google" and type them with a space in between. For example, if you see "1 - Android Auto" and "2 - Google", type 1 2 followed by enter.
- Type 2 and hit enter to choose "/system/priv-app" for the first app.
- Type 2 and hit enter to choose "/system/priv-app" for the second app.
Reboot the phone. On the Neo 2T:
- Hold down the power button until the power actions slider appears.
- Slide up to reboot the phone.
- Once rebooted, Android Auto will soon disappear from your app launcher now that is a system app. This is by design.
- Use the Google Play Store to install "Android Auto for Phone Screens".
- Open the "Android Auto for Phone Screens" app. Complete all setup steps.
- Open the "Android Assistant" app. Complete all setup steps.
- Open the "Google" app. Go to More > Settings > Google Assistant > Hey Google & Voice Match.
- Turn on "Hey Google". Complete all setup steps.
- In the Google Assistant settings in the Google app, you should now be able to turn on "Hey Google" voice activation.
- Hold down the power button until the power actions slider appears.
- Slide up to reboot the phone.
- Upon reboot, Android Auto should now work both on the phone and with Android Auto compatible vehicles head units.
- Hey Google should now work as long as the screen is on.
- Time for debloating!
STEP 5: Remove Realme bloatware.
Spoiler: Click here for instructions.
First we need to install an alternative input method, since we will be removing the stock keyboard. On the Neo 2T:
- Use the Google Play Store to install an input method of your choice, such as GBoard.
Now we can run the debloat script. On your PC:
- Plug the Neo 2T into your PC if it is not already.
- Open the folder where you extracted the "ADB_FASTBOOT.zip" (Done previously during Step 1: Unlock your bootloader.)
- Double-click the RMX3357_A14_DEBLOAT_NO_ROOT.bat file to run the non-root debloat script.
- Press Enter to run the script.
- Close the window or press Enter to exit once finished.
We need to use ADB to remove a few system apps. On your PC:
- Open the folder where you extracted the "ADB_FASTBOOT.zip" (Done previously during Step 1: Unlock your bootloader.)
- Open a command prompt pointing to the extracted files. (The fastest way to do this is to open the folder, then replace the file path with "cmd" end hit enter.)
- Enter this command to check that your phone is detected: adb.exe devices
- You should see your device represented by a long string of numbers and letters followed by "device".
- If you don't see this, or it doesn't say "device", double-check your USB cable or port, and make sure you installed the drivers as instructed previously.
- Enter this command: adb shell
- Enter this command: su
- Enter this command: pm uninstall --user 0 com.android.email
- Enter this command: pm uninstall --user 0 com.coloros.safecenter
- Enter this command: pm uninstall --user 0 com.heytap.book
- Enter this command: pm uninstall --user 0 com.heytap.market
- Enter this command: pm uninstall --user 0 com.heytap.themestore
- Enter this command: pm uninstall --user 0 com.nearme.gamecenter
Reboot the phone. On the Neo 2T:
- Hold down the power button until the power actions slider appears.
- Slide up to reboot the phone.
- You're done! Enjoy your debloated phone!
UH OH: Unbricking and Factory Restore.
Spoiler: Click here for instructions.
Click here for the ROM, use SP tools to flash. Guide coming soon, for now use the guide here.
------------------------------------------------------------------------------------------------------------------​Realme GT Neo 2T Tips:
​- If you find yourself needing to force your phone to power off for any reason, on the Neo 2T you must hold Vol+, Vol- and Power at the same time for around 10 seconds.
- The stock messaging app is com.android.mms, otherwise known as Mms.apk. It seemingly cannot be removed without breaking SMS/MMS.
- Removing Breeno will replace it with Google Feed when swiping left on the stock launcher fi the Google app is installed.
- There's a good chance the APN settings the phone chose are incorrect or nonexistent. Double-check them to make sure you have working data and MMS for your SIMs.
- Android Auto forces the phone to 60Hz and locks the settings, even once disconnected. Seems to be a common issue across a bunch of phones. Reboot to fix.
- If an app isn't showing notifications or is otherwise misbehaving:
>>> Make sure the app has been opened at least once since the phone was last powered on or rebooted.
>>> Check that notifications are enabled in Settings > Notifications & Status Bar > Manage Notifications > [Your App].
>>> If that doesn't help, try allowing background activity in Settings > Battery > App Battery Management > [Your App].
>>> Lastly, you can disable battery optimization for an app in Settings > Battery > More Battery Settings > Optimize Battery Use > [Your App].
------------------------------------------------------------------------------------------------------------------​
Spoiler: SOURCES
Guide by @mahotlov I shamelessly stole bits from: https://forum.xda-developers.com/t/x7-max-and-gt-neo-flash-ubrick-instructions.4337339/
Magisk: https://github.com/topjohnwu/Magisk
SafetyNet-Fix: https://github.com/kdrag0n/safetynet-fix
BusyBox NDK: https://github.com/Magisk-Modules-Repo/busybox-ndk
Terminal Systemizer: https://github.com/Magisk-Modules-Repo/terminal_systemizer
​

Reserved #1.

Hi, thanks for topic!
Have any room stock global? Need with language Portuguese of Brazil, i'm using the app MoreLocale to change, but this is not automatic

J_Eudes said:
Hi, thanks for topic!
Have any room stock global? Need with language Portuguese of Brazil, i'm using the app MoreLocale to change, but this is not automatic
Click to expand...
Click to collapse
Unfortunately there is no global ROM for the GT Neo 2T, I specifically asked Realme and they said they have no plans to release one.

Hi @MatinatorX, can you help to extract framework-res.apk and settings.apk? I would like to explore the possibility of decompiling those apk and adding languages. thank you!

dewidoj461 said:
Hi @MatinatorX, can you help to extract framework-res.apk and settings.apk? I would like to explore the possibility of decompiling those apk and adding languages. thank you!
Click to expand...
Click to collapse
Sure, here you go.

Hey, Is there a notification solution? to come from everyone?

AngelXTR91 said:
Hey, Is there a notification solution? to come from everyone?
Click to expand...
Click to collapse
Haven't had any issues with notifications myself. I'd check these:
- Make sure the app has been opened at least once since the phone was last powered on or rebooted.
- Check that notifications are enabled in Settings > Notifications & Status Bar > Manage Notifications > [Your App].
- If that doesn't help, try allowing background activity in Settings > Battery > App Battery Management > [Your App].
- Lastly, you can disable battery optimization for an app in Settings > Battery > More Battery Settings > Optimize Battery Use > [Your App].

Who faced such a (another) problem, let's say I have a working chat in a telegram, and today I read it through a smart watch while I was busy, but noticed that if there are more than 5+ unread notifications in the chat, then it stops even making a sound that something new has come, is there a way to treat this? and a similar story with viber as well. (translate.google)

AngelXTR91 said:
Who faced such a (another) problem, let's say I have a working chat in a telegram, and today I read it through a smart watch while I was busy, but noticed that if there are more than 5+ unread notifications in the chat, then it stops even making a sound that something new has come, is there a way to treat this? and a similar story with viber as well. (translate.google)
Click to expand...
Click to collapse
Unfortunately I'm not sure why that might be happening. I don't have a smartwatch and I don't use Telegram or Viber. I can tell you that Slack and Wyze both keep giving me notifications well after 5 of them. Maybe someone else might know.

My Neo 2T just arrived and upon further inspection, seemed to be preinstalled with Indian firmware by the seller which has Google Play Services and the languages I needed. Posted a screenshot of build number in case it helps anyone.
If anyone knows how to backup my ROM file, I'm willing to try and share it for everyone.
Edit: Out of ideas. MTK Droid Tool reports "Unknown ROM structure, backup NOT possible!"

dewidoj461 said:
My Neo 2T just arrived and upon further inspection, seemed to be preinstalled with Indian firmware by the seller which has Google Play Services and the languages I needed. Posted a screenshot of build number in case it helps anyone.
If anyone knows how to backup my ROM file, I'm willing to try and share it for everyone.
Edit: Out of ideas. MTK Droid Tool reports "Unknown ROM structure, backup NOT possible!"
Click to expand...
Click to collapse
As much as I'd love to find some sort of global ROM for this phone, that looks identical to my build number etc. when I first got the phone and probably the China ROM. Latest now is A14. When I asked, Realme was pretty adamant that this phone will never see a global ROM. They had also installed Google Play and a long list of languages for me before shipping, but these just bolt on to the stock China ROM.
I'm not sure how to tell 100% if it's actually the China ROM or not, but I'd give "Hey Google" a try, or Android Auto if you have an AA compatible vehicle. Would also be curious to know if your phone came with a bunch of bloatware apps and Breeno.
As for backing up, SP Tools is what worked for me. I recommend taking a proper backup ASAP just in case something goes wrong later. That said, I'm not sure how to anonymize the files it spits out (empty data partition, remove your IMEI etc) so it's safe to share.

I can confirm that "Hey Google" works, no chinese apps and breeno too. FYI, the bootloader was already unlocked when I got the phone. I noticed the Region defaulted to India so it's probably a custom firmware tailored to this phone. The box and manuals were chinese though.
As for the SP Flash Tool, how do I load the DA? This error appears after selecting the scatter file and clicking readback.

dewidoj461 said:
I can confirm that "Hey Google" works, no chinese apps and breeno too. FYI, the bootloader was already unlocked when I got the phone. I noticed the Region defaulted to India so it's probably a custom firmware tailored to this phone. The box and manuals were chinese though.
Click to expand...
Click to collapse
Oh wow. A proper global ROM for this phone would be amazing. I'll see if I can figure out how to turn a backup into something flashable. In the meantime I think I'm going to email Realme again and see if their tune has changed.
Would it be possible to share where you bought the phone? I got mine from "realme Direct Store" on AliExpress.

I bought it from a reseller in shopee malaysia. I've asked the seller for the source to no avail, they just said it was the supplier who installed the rom.

I sent Realme an email directly, hopefully I get a more favorable answer this time. Will update if I hear anything. My AndroidFileHost account finally got upload perms so if I manage to get the ROM out of them it'll be easy to share.

Managed to take a proper backup after reading the guide by mahotlov linked in your thread. Just let me know which files you'd need anytime and I'd be willing to share.
Edit: Wifi and bluetooth no longer works after flashing your magisk.img & vbmeta.img. Restored my backup and it works again, interesting

I have a DM from someone else who also has an India A13 ROM shipped with their Neo 2T, so this is definitely a thing, but Realme responded to me yesterday and is still claiming it doesn't exist. They are having similar issues with the China ROM I uploaded breaking things. I seriously hope there aren't multiple hardware versions under the RMX3357 model number messing everything up.
As for your backup, I think it should be possible to just pick some of the files from your backup and use them to replace the matching .img file in the China ROM upload. This is assuming the partition structure and other things are the same and only the contents of the partitions are different (which it should be, but you never know). Only thing I'm not 100% sure on is which partitions would be safe to share and which ones might have personal info like IMEI or bits of your data partition.

dewidoj461 said:
Just let me know which files you'd need anytime and I'd be willing to share.
Click to expand...
Click to collapse
Please check here scatter to backup phone on sp flash tool and give me link download ROM_0-55 except ROM_14,15,18,19,24(ram, nvdata, nvcfg, protect1, protect2) in folder SP Flash tool.

Andy_men2 said:
Please check here scatter to backup phone on sp flash tool and give me link download all ROM_0-55
Click to expand...
Click to collapse
I would advise against this @dewidoj461. One of those ROMs has your IMEI info in it, and if you had been using the phone before your backup there is likely personal info somewhere too, especially if SIMs were installed. Maybe the intent here is not malicious but that user account is brand new and you would absolutely be giving sensitive information by supplying your full backup.
EDIT: I'm also suspicious about that RAR. The scatter file is only 54kb while that RAR is 2.1MB.