Related
ah please help. I have rc29 or whatever because when i type in reboot it restarts my phone. I ahve a SIM card in but I cannot get adb shell started. :/
when i plug in my phone nothing happens.
I d/l the sdk but it doesnt ask for the usb thing.
PLEASE HELP
i have tried everything. adb isnt seenig my device
you have to make sure USB debugging is on inside Settings | Applications | Development
Edit: hehehe ^^^ what he said.
Go to Settings > Applications > Development > USB Debugging (check)
well you cant do that when you cant even activate your phone. im doing the activate without data plan. help?
samrozzi said:
well you cant do that when you cant even activate your phone. im doing the activate without data plan. help?
Click to expand...
Click to collapse
did you try typing
<enter>setprop persist.service.adb.enable 1<enter>
?
yes hundreds of times. when i enter it and i plug into computer nothing happens. nothing pops up on vista. is there a way to maybe delete a driver for android I maybe installed already?
its that my pc isnt detecting my g1. it says no device detected. PLEASE HELP.
idk maybe I need a way to usb debug without activating?
i think its something with my driver. i might have installed it long ago? idk. any way to uninstall and reinstall?
samrozzi said:
i think its something with my driver. i might have installed it long ago? idk. any way to uninstall and reinstall?
Click to expand...
Click to collapse
If you have Windows Vista or 7 you can right click my comptuer > Manage > Device Manager (or just call up device manager in xp) and look for ADB Interface.
Right Click HTC Dream Composite ADB Interface and click Uninstall.
Unplug and replug the USB and it should re-detect.
nevermind me =)
Same problems
I am having the same problems as "samrozzi".
Phone is OK with Reboot command.
Will not recognize "Setprop Persist etc".
My device manager shows (HTC Android Phone USB Device) in "Disk Drives" but nothing about ADB interface.
Also you guys are saying
"Go to Settings > Applications > Development > USB Debugging (check)
Settings where? On the phone? not possible without getting past the registration screen.
In SDK ?
In ADB ?
On Computer somewhere ?
I have un-installed the driver for the phone. I reconnect and turn the phone on. The computer says HTC Google phone--hardware is installed and ready to use. Then it goes away and doesn't seem to be of any further use.
Please help, my brain is starting to sizzle from info-overload.
unkabuzz said:
I am having the same problems as "samrozzi".
Phone is OK with Reboot command.
Will not recognize "Setprop Persist etc".
My device manager shows (HTC Android Phone USB Device) in "Disk Drives" but nothing about ADB interface.
Also you guys are saying
"Go to Settings > Applications > Development > USB Debugging (check)
Settings where? On the phone? not possible without getting past the registration screen.
In SDK ?
In ADB ?
On Computer somewhere ?
I have un-installed the driver for the phone. I reconnect and turn the phone on. The computer says HTC Google phone--hardware is installed and ready to use. Then it goes away and doesn't seem to be of any further use.
Please help, my brain is starting to sizzle from info-overload.
Click to expand...
Click to collapse
did you install the driver
USBDeview
Try this:
- get USBDeview : http://www.nirsoft.net/utils/usb_devices_view.html
- unplug phone from PC
- in USBDeview delete all drivers that have anything to do with HTC
- plug phone in PC; drivers should now install correctly IF you have downloaded and installed them before
If the above procedure does not work reinstall drivers (from SDK) and start all over.
check out this thread on "How to solve "G1/HTC Magic not recognized by ADB under Windows"
http://groups.google.com/group/android-beginners/browse_thread/thread/ff713181959c48ee
pascanu said:
If the above procedure does not work reinstall drivers (from SDK) and start all over.
Click to expand...
Click to collapse
I don't see any "drivers" in SDK. I assume they are in "tools"??
unkabuzz said:
I don't see any "drivers" in SDK. I assume they are in "tools"??
Click to expand...
Click to collapse
it should be in the main folder of the sdk "usb driver"
Vulgrim said:
it should be in the main folder of the sdk "usb driver"
Click to expand...
Click to collapse
When I open "android-sdk-windows" I see;
add ons (empty)
platforms (empty)
SDK Readme
SDK Setup (green droid) running/opening this gives me a black rectangle that is gone in an instant. (I assume that this is a command screen)
and tools
Inside tools are 24 folders.
I have opened all that I can inside tools "all" of them open the same black rectangle and then disappear.
Closest thing I can see is AdbWinUsbApi.dll Don't see any way to open it successfully............
Found another thread
http://href.to/eNE
http://www.anddev.org/download.php?id=449
(Android USB Drivers)
that gave me drivers that seem OK.... HOWEVER...
You guys are also saying
"Go to Settings > Applications > Development > USB Debugging (check)
Settings where? On the phone? not possible without getting past the registration screen.
In SDK ?
In ADB ?
On Computer somewhere ?
unkabuzz said:
You guys are also saying
"Go to Settings > Applications > Development > USB Debugging (check)
Settings where? On the phone? not possible without getting past the registration screen.
In SDK ?
In ADB ?
On Computer somewhere ?
Click to expand...
Click to collapse
Can anybody help ?? Please ??
unkabuzz said:
Can anybody help ?? Please ??
Click to expand...
Click to collapse
settings on the phone
unkabuzz said:
When I open "android-sdk-windows" I see;
add ons (empty)
platforms (empty)
SDK Readme
SDK Setup (green droid) running/opening this gives me a black rectangle that is gone in an instant. (I assume that this is a command screen)
and tools
Inside tools are 24 folders.
I have opened all that I can inside tools "all" of them open the same black rectangle and then disappear.
Closest thing I can see is AdbWinUsbApi.dll Don't see any way to open it successfully............
Found another thread
http://href.to/eNE
http://www.anddev.org/download.php?id=449
(Android USB Drivers)
that gave me drivers that seem OK.... HOWEVER...
You guys are also saying
"Go to Settings > Applications > Development > USB Debugging (check)
Settings where? On the phone? not possible without getting past the registration screen.
In SDK ?
In ADB ?
On Computer somewhere ?
Click to expand...
Click to collapse
Run the setupsdk.exe and it should be under "available" for download, it will be called something like Usb Drivers r2 or something
Hi all,
So I've tried lots of forums on here about how to root my LG Optimus 2x but keep running into the same problem. Here are the steps I've been following:
Remove the battery.
Plug in your USB cable to your PC.
Hold Volume Up and Volume Down at the same time keeping them held down.
Plug in the USB cable to your phone. (Keep the buttons held until Windows detects a new APX device.)
Open Device Manager in Windows and you should see "APX Device" listed with an error icon.
Right click on the APX device.
Select 'Update driver software'.
Select 'Browse my computer...'.
Select 'Let me pick...'.
Select 'Have disk'.
Browse to directory you extracted the *driver* software to: One-Click-G2x-recovery-flasher-09-23\APX.
Accept any warnings, including the big red alert (you may need to disable UAC).
Now in Device Manager under 'USB Controllers' you should have an 'NVIDIA USB Boot-recovery driver for mobile devices'.
If not, uninstall the driver, reboot, rinse and repeat.
I'm on a Windows 7 32 bit PC. When I check for an APX device in the Device manager I don't see one?
I do see an unknown device but when I try to click have disk etc for this, it does not recognise the drivers I'm pointing at and does not install. Can anyone help me with this?
Many thanks,
Derek
What version are you on? Froyo or Gingerbread? It seems you are flashing CWM but that's a longer way to root. You could always try Super one click, which works on froyo.
Yes, I am on 2.2. So Superoneclick is safe to use?
Absolutely. I used it when I was on froyo. Do you have any sensitive data however on your phone? Just in case you mess up, it's always good to have a backup of it. Probably hook up your USB cable to your pc/laptop and copy/paste the files to be safe.
Ok, thanks. So I have rooted the phone using SuperOneClick. Can you send me a link where I can find information about how to put on Gingerbread 2.3 now? Or maybe there is a better ROM I can use that that? Any advice would be appreicated.
Thanks,
Derek
You can try Cyanogen Mod, but that is experimental, even the RC one (Release Candidate).
You can try other leaked versions of ROMs, or you can download the latest v10L Gingerbread release. Before installing any ROM, I recommend doing a CWM or Nandroid backup.
The link to download gingerbread (it's only out in a few countries in Europe) is located in the development sub section of the LG 2x forums. However, try using the update tool and see if it tells you that you have an update.
I seem to have a bit of a problem. I took your advice and found a forum that helped me to do a Nandroid Backup. As part of the steps it asked me to install ROM manager from the Market. I started this and chose my phone model. I started the Flash ClockworkMod Recovery’ in the ROM manager but it stopped and said a permissions error occured. Then I tried to open other programs but they wouldn't open. I tried to reboot the phone but now it just flashes on the LG logo and won't boot up. Please help me with this.
Hello people on this great forum i am new here so i salud you all.
i installed Cyanogenmod 2.3.4 android on lg optimus 2x butt here is the thing how do you update to a newer version or do you have to unstall everything and start from scratch.any tips are welcome and is there a new version of cyanogenmod
derbeast said:
Hi all,
So I've tried lots of forums on here about how to root my LG Optimus 2x but keep running into the same problem. Here are the steps I've been following:
Remove the battery.
Plug in your USB cable to your PC.
Hold Volume Up and Volume Down at the same time keeping them held down.
Plug in the USB cable to your phone. (Keep the buttons held until Windows detects a new APX device.)
Open Device Manager in Windows and you should see "APX Device" listed with an error icon.
Right click on the APX device.
Select 'Update driver software'.
Select 'Browse my computer...'.
Select 'Let me pick...'.
Select 'Have disk'.
Browse to directory you extracted the *driver* software to: One-Click-G2x-recovery-flasher-09-23\APX.
Accept any warnings, including the big red alert (you may need to disable UAC).
Now in Device Manager under 'USB Controllers' you should have an 'NVIDIA USB Boot-recovery driver for mobile devices'.
If not, uninstall the driver, reboot, rinse and repeat.
I'm on a Windows 7 32 bit PC. When I check for an APX device in the Device manager I don't see one?
I do see an unknown device but when I try to click have disk etc for this, it does not recognise the drivers I'm pointing at and does not install. Can anyone help me with this?
Many thanks,
Derek
Click to expand...
Click to collapse
Only select the DEBUG USB, and its ok!
Settings > Applications.
I hope this help, because you can only do the root with the DEBUG USB activate
I have been trying for don't know how long but am just unable to flash the new bootloader. I have tried the AIO tool kit but with the latest drivers installed, usb debugging enabled but it keeps saying no connection found. I have also tried nvflash method but still not able to work my way around it. currently i am on pa rom but really want to get the ICS rom. I really need some help....
Thank you in advance
Yeah I had the same problem fe(w days ago . i have bricked my device totally then i will suggest you flash it through NV flash mathod and yeah ,make sure you have all drivers (device ) the most imp driver is 'APX DRIVER " Download it and install it ..on your system or laptop , remove battery of your device .. press + and - together and plug in usb . a popup and sound will be appear on our computer . thats it now you can flash your device through NV flash ..Happy flashing .. HIT THANKS IF I M HELPFUL and for more queries message me here :laugh:[/B][/B][/I]
APX drivers are included in AIO tool
maddyrokieasta said:
Yeah I had the same problem fe(w days ago . i have bricked my device totally then i will suggest you flash it through NV flash mathod and yeah ,make sure you have all drivers (device ) the most imp driver is 'APX DRIVER " Download it and install it ..on your system or laptop , remove battery of your device .. press + and - together and plug in usb . a popup and sound will be appear on our computer . thats it now you can flash your device through NV flash ..Happy flashing .. HIT THANKS IF I M HELPFUL and for more queries message me here :laugh:[/B][/B][/I]
Click to expand...
Click to collapse
agree (see below)
I - Install APX (NVFlash Recovery) Drivers if not already installed. It starts a device driver wizard to help you install the drivers needed for NVFlash. It detects your system OS and gives on-screen instructions if running Windows 8. FYI the drivers are located under ToolKitFiles\nvflash\driver folder.
Click to expand...
Click to collapse
- via http://forum.xda-developers.com/showpost.php?p=34809475&postcount=1
Prepare Phone
-Power down phone
-Remove battery
-Hold VOL_DWN+VOL_UP & plug in USB connection from computer (note, your phone will not visibly respond but it will boot to APX mode quickly)
-Open Device Manager in Windows and you should see "APX Device" listed with an error, or not if you have used NVFlash before
-Right click on the APX device
-Select 'Update driver software'
-Select 'Browse my computer...'
-Select 'Let me pick...'
-Select 'Have disk'
-Browse to directory you extracted the *driver* software to above (It's included in Stefan's zip)
-Select 'NVIDIA USB Boot-recovery driver for mobile devices'
-Accept any warnings, including the big red alert (you may need to disable UAC)
-Now in Device Manager under 'USB Controllers' you should have an 'NVIDIA USB Boot-recovery driver for mobile devices'
If not, uninstall the driver, reboot, rinse and repeat
Install the rom:
- Go to the folder where you unpacked Stefans rom
- Run Windows installer and follow instructions on screen, should be peace of cake for everyone!
- DONE
I think you should try either updating your drivers for the phone and if that doesn't work, try an older version then.
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.