Related
I am trying to fix the WiFi on my Captivate. This thread here tells how to do it. Unfortunately when I run DDMS I get the error "Failed to get the adb version: Cannot run program "adb": CreateProcess error=2, The system cannot find the file specified." I have tried installing the SDK on both a Windows 7 64-bit and XP 32-bit machine. I get the same error on both machines. I have tried both the generic Galaxy S drivers and the Captivate drivers. Any suggestions? Here are the instructions I've followed in case you don't want to read the other thread:
1. Install the SDK -> Android SDK | Android Developers
(make sure the <SDK>/tools path is added to the windows path variable. My Computer -> Properties -> Advanced -> Environment Variables -> System variable -> add the SDK path at the end of Path variable )
2. On your phone, please enable (tick mark) "USB debugging" under "Settings" -> "Applications" -> "Development"
3. Connect your phone using USB to PC/Laptop. Close phone manager application if it comes up on the PC.
4. Run "ddms.bat" from <SDK>/tools directory. The DDMS application will come up and it should readily connect to your phone. (in the main screen, under Name, you should find the phone ID and SW ver. no.)
5. Go to menu Device -> File Explorer. New window will come up.
6. Here go to data -> wifi directory. You will see a file bcm_supp.conf.
7. Though it is not possible to read this file, you should be able to delete it. (at least I could delete it). You can delete the file by selecting it and then pressing red "-" on top left of the window.
Thanks!
Post in q and a.
sent from my craaazy fast cappy running di11igaf v2.5 at 1280mhz!!!
silverslotcar said:
Post in q and a.
sent from my craaazy fast cappy running di11igaf v2.5 at 1280mhz!!!
Click to expand...
Click to collapse
Yes, Q&A would be the proper location for this thread.
Sent from my GT-I9000 using XDA App
Ok, sorry, although I just figured out the problem. The Path should have the platform-tools directory instead of the tools directory because that's where adb is located. I corrected that and it loaded right up. Unfortunately, when I click on the + sign for the Data folder it doesn't show me anything Guess I'm going to have to do a factory reset after all.
automagrt said:
I am trying to fix the WiFi on my Captivate. This thread here tells how to do it. Unfortunately when I run DDMS I get the error "Failed to get the adb version: Cannot run program "adb": CreateProcess error=2, The system cannot find the file specified." I have tried installing the SDK on both a Windows 7 64-bit and XP 32-bit machine. I get the same error on both machines. I have tried both the generic Galaxy S drivers and the Captivate drivers. Any suggestions? Here are the instructions I've followed in case you don't want to read the other thread:
1. Install the SDK -> Android SDK | Android Developers
(make sure the <SDK>/tools path is added to the windows path variable. My Computer -> Properties -> Advanced -> Environment Variables -> System variable -> add the SDK path at the end of Path variable )
2. On your phone, please enable (tick mark) "USB debugging" under "Settings" -> "Applications" -> "Development"
3. Connect your phone using USB to PC/Laptop. Close phone manager application if it comes up on the PC.
4. Run "ddms.bat" from <SDK>/tools directory. The DDMS application will come up and it should readily connect to your phone. (in the main screen, under Name, you should find the phone ID and SW ver. no.)
5. Go to menu Device -> File Explorer. New window will come up.
6. Here go to data -> wifi directory. You will see a file bcm_supp.conf.
7. Though it is not possible to read this file, you should be able to delete it. (at least I could delete it). You can delete the file by selecting it and then pressing red "-" on top left of the window.
Thanks!
Click to expand...
Click to collapse
Hi,
I am going crazy with this crap, I am not impressed how google put this **** together.
I can see you managed to fix the issue of ddms not finding adb but I didnt. Can you please explain in more details? I searched everywhere over the internet but everybody just says "add the path". Fine. Then what....?
I added a new path in the environmental system variables called "SDK" and points to:"C:\program files\Android\android-sdk-windows\platform tools\. Still no joy. What am I doing wrong?
thanks
Did you reboot after adding the path?
And I didn't realize that Google had changed the SDK path to "platform-tools" with their latest release. Just plain dumb imo as folks have been so used to it being in just the "tools" location.
Inspired by this post, i've set on a quest to get USB tethering working on my HTC one (M8) Windows Phone.
The steps are very simmilar, so I will modify the original post, with specifics to the HTC One Device:
1) First, you need the Diagnosis app for HTC phones. This is included, but hidden, on each phone. To access it, type ##634# (##MFG#) into the phone dialer.
There, in "EmbeddedTool" select Diag function, and enable "Diag mode"
Your phone will imidiatly reboot, that is normal
2) When the phone boots up again you should plug it into your PC, if you haven't done so already.
It will not appear in Windows Explorer or the Windows Phone app. You'll get a "Found new hardware" notification, but the odds are that the drivers will fail to install automatically. We'll need to install them manually.
3) To do that, first download the attached ZIP file included with this post. Extract its contents somewhere handy.
Next, open Device Manager. This can be done from the Start menu/screen, or by opening Computer Management. into It will require Administrator permissions.
4) You should see four new"USB device" entries that don't have drivers. We only need one of them (typically first one). with the hardware id "VID_0BB4&PID_0BFF&MI_00"
5) Double-click one of those entries, or right-click on it, and select Update Driver.
6) in the driver dialog select "Browse my computer for driver software" and then select the folder where you have extracted the attahced driver
7) Once driver is installed one of the devices will be identified as "HTC USB Modem"
8) Open it's properties and in the Advanced tab, set the "Extra initialization command:
+cgdcont=1,"ip","APN"
Where APN is the APN from your carrier.
For me it was "vzwinternet", so the command that I used was:
+cgdcont=1,"ip","vzwinternet"
9) after this is done you will able to create a Dial-up connection
via "Internet options-> Connections-> Add
in the next dialog: Select Dial-up
for the "Dial-up phone number" use *99# and leave the password and username blank.
10) once connection is setup, disable the IP-V6 from its properties. and you should be able to connect.
11) Don't forget to disable the "Data Connection" on your phone
Enjoy
PS
Although drivers did work on my machine, I suggest being extra cautious before using them, so create restore point, and run an anti-virus scan, as I found that driver by Googling the hardware ID of the 4 unrecognized devices.
References:
Everything about HTC one 8
USB Tethering
HTC HD7 device tethering
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??
Hi
(Sorry for my little english, feel free to speak french if you can)
I have try to root my 4X HD for using a better recovery app (recover pictures deleted in sd card, now you know my skill). I have use this page: (as newbie i cant post outside links)
n fact, I never had an Android device where this was that easy to achive! Our friends at XDA-Developers offer a guide and the necessary tools in this thread. Having a "Microsoft free zone" and "only" running Linux machines (yeah, even the Android ones run a Linux kernel), I was able to follow up those steps with a little adaption here and there -- and so I will sum up the results for Windows and Linux users as well:
Preparation
First you need to download the required tools, all of them available at the linked XDA-Developers thread:
o4xr.zip is the rooting toolkit
IS11LG_SystemBackupTest.signed.apk to prepare your device
Windows users only: LGUnitedMobileDriver_Ver_3.7.2_LG-P880_LGO4XHD.zip -- the Windows drivers for the device
Having everything downloaded, some additional steps are necessary at your computer:
Windows users only: Unzip and install the drivers
Linux users: Make sure adb is able to detect the device (check with adb devices). If it's not, see at the end of this answer for some hints.
Everybody: Copy IS11LG_SystemBackupTest.signed.apk to your Optimus (e.g. after connecting it via USB in MTP mode, copy the file to the internal SDCard)
Everybody: Create a new directory, unzip o4xr.zip there, and change into this directory.
The rooting process
On your Optimus, go to Settings→Security and make sure "Unknown Sources" is TICKED (i.e. contains a checkmark)
Go to Settings→Developer Options and enable "USB Debugging"
Now install IS11LG_SystemBackupTest.signed.apk (e.g. use a file explorer to find and "launch" it)
Open the "SystemBackupTest" app you just installed. Nothing spectacular will happen, so don't be disappointed here.
Hold the power button and choose "Power off and restart".
When you can see the lock screen, you may notice that the phone is running very slowly, this is normal.
Once the device is fully started up again, connect it to your computer with an USB cable. Make sure the phone is in "Charging Only" mode.
On your PC, open a terminal (Linux) resp. command (cmd.exe, Windows) window and change into the directory you've extractedo4xr.zip` into.
(on Windows, you may need admin privileges: right click, run as administrator. On Linux it did fine for me without superuser/root permissions)
Now run the rooting script:
Windows users: type root followed by the enter key
Linux users: type ./root-linux.sh, also followed by the enter key
Any Mac users? Type ./root-mac.sh, also followed by the enter key. Don't worry, it won't root your Mac/Linux machine (Windows users: it is unlikely to root your box, either
DO NOT DISCONNECT YOUR PHONE WHILE THE SCRIPT RUNS! Wait while it does its job. During that process, the phone will reboot automatically a couple of times. The script will inform you about this in your command/terminal window. Once the command/shell prompt returns, the misdeed is accomplished
Now uninstall SystemBackupTest from your Optimus. Do not launch it again at this state, or you might have to start over from step 5
On your phone, open up Google Play Store and search for "SuperSU". Update the app when prompted, then open it. Press OK to update the SU binary.
You now have root and can safely restore the "Unknown Sources" and "USB debugging" settings back to how you had them! Congratulations! Next steps are to install Titanium Backup, LBE Privacy Guard, and all the other things you might need and which require root!
At step 8. i got "command not found" in Terminal (Linux Mint), assuming script don't work i have reboot my device.
Since my phone boot but is very very slow and screen is friezed, even if i can unlock my SIM card by memory pattern (without sim card and always by memory i can see Settings of android but not down the list).
In recovery boot (Sound up + Power), my device show me a picture that would say "dont unplug charge and usb".
I guess my phone is not rooted, adb can list it but not fastbood. LG software (on windows 7) cant communicate with it because usb driver not work. I guess i've try and read more since 8 hours but my brain is off right now. Any help will be very welcome.
Cheers
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.