Hi guys,
I have a problem. The screen in my mi 9 is broken. I would like to recovery data at least photos. Bootloader is unlocked, adb is enabled but pc is unathorized for adb, I need to accepted on phone. I'm also able to launch phone in fastboot mode and recovery mode.
Could you suggest me any method how to download data from my phone?
I tried adb pull but error:
pull: /sdcard/3fmB6592A7enJTGXC2M30D/yoeozhBuX,Q2poPiA9N0bB -> /3fmB6592A7enJTGXC2M30D/yoeozhBuX,Q2poPiA9N0bB
failed to copy '/sdcard/3fmB6592A7enJTGXC2M30D/yoeozhBuX,Q2poPiA9N0bB' to '/3fmB6592A7enJTGXC2M30D/yoeozhBuX,Q2poPiA9N0bB': open failed: Required key not available
pull: /sdcard/3fmB6592A7enJTGXC2M30D/_wjgHoHRw3ssLu907QHw4CcVKsXdrQtw0 -> /3fmB6592A7enJTGXC2M30D/_wjgHoHRw3ssLu907QHw4CcVKsXdrQtw0
i went through this before, this may not help you now but in in the future make sure adb is fully working at all times, also install team viewer so in this case you can use another phone or computer to browse broken phone.
the best thing i can tell you is that what i did once is IF your touch on the phone is broken using a otg cable you can plug in a computer mouse and blindly try to press the adb authorization button or enable usb mode popup, i got lucky with that before but it requires you to REALLY know your phones layout.
xdarkmario said:
i went through this before, this may not help you now but in in the future make sure adb is fully working at all times, also install team viewer so in this case you can use another phone or computer to browse broken phone.
the best thing i can tell you is that what i did once is IF your touch on the phone is broken using a otg cable you can plug in a computer mouse and blindly try to press the adb authorization button or enable usb mode popup, i got lucky with that before but it requires you to REALLY know your phones layout.
Click to expand...
Click to collapse
Thanks for advise. I was searching about method and seems hard to do something. first I need to encrypt storage but to do it I need to draw patter to unlock. Same in TWRP I need to check what exactly part is broken then order and replace.
This guide will be about deleting a magisk module that caused your phone to bootloop. Definetly works with Xiaomi Redmi Note 10 5G, let me know if it works on Poco M3 Pro as well.
Prerequisites:
- rooted phone with magisk installed
- usb data cable
First you have to boot into safe mode which will disable the loading of all magisk modules:
- Turn off the smartphone completely.
- Turn it on normally and when the MIUI logo appears, press and hold the volume down button until the system boots completely, and you see the lock screen, it should also display "safe mode" in the bottom left corner.
Next enable USB debugging on your phone and connect it to a pc, then run
adb devices
If your devices is recognized and authenticated it will output:
List of devices attached
**************** device
where ************* is your device ID. If it writes 'unauthorized' then accept the prompt for authorization on your phone.
Now open an ADB shell from your pc:
adb shell
su
cd /data/adb/modules
ls
This will list all your installed magisk modules. Remove the problematic one with:
rm -r problematic_module
Done, reboot normally!
------------------------- If su command freezes the command line------------------------------
If somehow this does not work, for example you have not granted shell superuser rights before, then you have the following backup options:
run:
adb wait-for-device shell magisk --remove-modules
This should remove all installed modules, and reboot the phone. If it does not work from safe mode, you can try it during the boot animation. (After MIUI logo comes up adb gets enabled (check with 'adb devices' command, if adb is running))
If so far nothing worked you still have a third option to recover you phone/data:
--------------------- Nothing working ---------------------------
You can flash the stock boot.img from your currently installed stock ROM and it should boot your phone without magisk (but also no root). This will enable you to back up your phone/data, but if you want magisk again, you probably have reflash your ROM from fastboot again. This is because with no root access, and magisk not present in your boot image there is no way to remove the module that is causing the bootloop.
Feel free to comment, share your suggestions, and correct me on anything if I am wrong.
Gorg2331 said:
This guide will be about deleting a magisk module that caused your phone to bootloop. Definetly works with Xiaomi Redmi Note 10 5G, let me know if it works on Poco M3 Pro as well.
Prerequisites:
- usb debugging already enabled and authenticated (preferrably)
- rooted phone with magisk installed
- usb data cable
all you have to do is connect your phone to your PC and when it shows the MIUI logo during normal boot run
adb devices
If your devices is recognized and authenticated it will output:
List of devices attached
**************** device
where ************* is your device ID. If it writes unauthorized then skip to the "Other Method" section below. If you get back nothing try to run it a couple times during boot. I am not sure when adb gets enabled during the boot but should be around the MIUI logo appearing.
next write:
adb wait-for-device shell magisk --remove-modules
This will delete all magisk modules from your phone, and it reboot it automatically. It should boot up just fine, and all your magisk modules will be deleted.
---------------- Other method --------------------------
If you really need access to the phone, but do not have adb enabled:
You can flash the stock boot.img from your currently installed stock ROM and it should boot your phone without magisk (but also no root). This will enable you to back up your phone/data, but if you want magisk again, you probably have reflash your ROM from fastboot again. This is because with no root access, and magisk not present in your boot image there is no way to remove the module that is causing the bootloop.
Feel free to comment, share your suggestions, and correct me on anything if I am wrong.
Click to expand...
Click to collapse
just a thought on the above;
i haven't followed this topic anymore since the built-in functionality where modules are disabled if phone is in safe mode so i just thought to post it as a way to remind people that ( i think) most phones have a safe mode and with that , it might get you out of the bootloop.
I guess the above option is a great way too, but i think the use of safe mode makes it a lot easier.
pjottrr said:
just a thought on the above;
i haven't followed this topic anymore since the built-in functionality where modules are disabled if phone is in safe mode so i just thought to post it as a way to remind people that ( i think) most phones have a safe mode and with that , it might get you out of the bootloop.
I guess the above option is a great way too, but i think the use of safe mode makes it a lot easier.
Click to expand...
Click to collapse
That is a great suggestion, tho you cannot use any root applications since they will not be loaded. (Even if you install them during safe mode) But it should help sidestep the adb not authorized issue possibly! I incorporated safe mode in the post.
I used safemode purely to get rid of the troublesome modules( since you still have root access) . Then reboot the phone normal, and all should be fine/ you should be out of the bootloop
And i know the safemode is a bit off topic compared to what you are writing about, but it might help getting back into the phone
pjottrr said:
I used safemode purely to get rid of the troublesome modules( since you still have root access) . Then reboot the phone normal, and all should be fine/ you should be out of the bootloop
And i know the safemode is a bit off topic compared to what you are writing about, but it might help getting back into the phone
Click to expand...
Click to collapse
Oh you are totally right! You can use safe mode to remove the problematic modules with rm -r. But I think this only works if you have previously granted shell superuser rights. (Since in safe mode you will not get prompts to give SU rights)
I confirm, your guide Is correct. Now i have installed a modules called magisk bootloop saver. Works fine. Do the same thing without digit the adb command.
i'd also suggest in case of BOOTLOOP (cause of bad magisk module)
you can still fastboot
Code:
fastboot flash boot boot.img
the ORIGINAL boot.img of your actual ROM ( so everytime you root keep a copy of the original BOOT.IMG)
in that case you'll be able to reboot your phone ( without root ) and without losing any data !
yes, all these suggestions are good and 100% work! great thread
Booting into Safemode, adb shell and deleting the bad module worked great, thank you!
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.
Good evening.
I have the following equipment and an unsolvable problem:
- Oneplus Nord CE 5G
- Twrp-3.5.2_11-ebba
- Bootloader unlocked
- ADB platform tools 30.0.5, 33.0.1 and 33.0.3
For the last five months I have been trying to root the phone but nothing works. The only thing I can start is twrp in recovery mode.
System boot generates: dm-verify device corrupted Force Dump kernel_restart.
Initially, internal and OTG USB showed 0MB but I could change the file internal file system and now it is showing the correct capacity. The laptop also detects it now as internal folder but no contents.
OTG USB never shows anything and I have tried different SUB sticks and formats.
There is no way to transfer anything from the PC to the phone or vice versa.
When in twrp recovery mode, the phone accepts ADB commands but whenever I try bootloader mode or fastboot mode from the twrp menu, I cannot issue fastboot commands from my laptop (which worked before when I unlocked the bootloader).
I believe the only way is to flash the phone completely and I have extracted the files using Payloader Dump.
However, without fastboot commands there is no way to transfer anything to the phone and install.
I have not tried an SD card yet and it would be a nano type.
Does anyone have any idea? I am seriously frustrated and have seen any error message imaginable.
Thanks a lot in advance.
Audoghast
Audoghast said:
Good evening.
I have the following equipment and an unsolvable problem:
- Oneplus Nord CE 5G
- Twrp-3.5.2_11-ebba
- Bootloader unlocked
- ADB platform tools 30.0.5, 33.0.1 and 33.0.3
For the last five months I have been trying to root the phone but nothing works. The only thing I can start is twrp in recovery mode.
System boot generates: dm-verify device corrupted Force Dump kernel_restart.
Initially, internal and OTG USB showed 0MB but I could change the file internal file system and now it is showing the correct capacity. The laptop also detects it now as internal folder but no contents.
OTG USB never shows anything and I have tried different SUB sticks and formats.
There is no way to transfer anything from the PC to the phone or vice versa.
When in twrp recovery mode, the phone accepts ADB commands but whenever I try bootloader mode or fastboot mode from the twrp menu, I cannot issue fastboot commands from my laptop (which worked before when I unlocked the bootloader).
I believe the only way is to flash the phone completely and I have extracted the files using Payloader Dump.
However, without fastboot commands there is no way to transfer anything to the phone and install.
I have not tried an SD card yet and it would be a nano type.
Does anyone have any idea? I am seriously frustrated and have seen any error message imaginable.
Thanks a lot in advance.
Audoghast
Click to expand...
Click to collapse
While your phone is in fastboot and connected to your laptop; How is it shown in device manager?
Good evening.
I found the solution to unbrick my Oneplus Nord CE 5G and here it is.
Status: - normal start leading to Qualcomm Crash Dump screen
- Recovery mode into TWRP possible but no transfer of files to/from phone
- No Fastboot possible
Procedure:
Install Qualcomm USB Drivers from
https://www.getdroidtips.com/download-qualcomm-qdloader-hs-usb-driver/
You may have to launch the command prompt as admin and type:
bcdedit /set testsigning on
I did not have to do it because the Qualcomm Driver installation did it for me.
After restart you will see the following message in the lower right side of your PC:
Testmode Windows 10 Pro + build number
To get rid of end at the very end type:
bcdedit -set testsigning off
Download the following package:
Europe: https://onepluscommunityserver.com/...BA/R/OnePlus_Nord_CE_EU_OxygenOS_11.0.9.9.zip
India:
https://onepluscommunityserver.com/...R/OnePlus_Nord_CE_India_OxygenOS_11.0.4.4.zip
These packages contain the MSM Download Tool and the respective files. Beware that you have to get the correct bundle for your phone. Other bundles contain MSM Download Tool too but will not be compatible and the tool generates a failure message.
Launch MSM and type OTHER at login.
Target was EU in my case.
Then click on start.
Now your phone needs to boot into EDL mode. It worked for me from the TWRP Reboot screen but supposedly starting the phone by holding the volume up and down buttons for 45 seconds does the same.
The screen will be totally black, no beep, no vibration, no feedback.
Then connect the USB cable and MSM will start working. After about 5 minutes the phone should be back to normal.
ADB commands worked again too (phone was being recognized as USB device under device manager). However, fastboot did not work. The device was listed as other device in the manager.
After updating the driver using the following files everything worked:
https://drive.google.com/drive/folders/1D96njoYn-n3alu3ggaK3Kw8hMGLKhJVg
Now I am back to rooting and will report about that too.
Good luck
So, i've been tinkering a bit for days over my Wiko UFeel Prime (i had even heard this one is the "clone" of the YU Yureka Black and/or viceversa around) and found a ton of problems at first due to the manufacturer (Tinno) putting a ton of "walls" to make modding impossible, like:
Removing various Fastboot commands (oem unlock, oem unlock-tinno, reboot edl, general bootloader info, refuses reboots to recovery, bootloader and system, etc.);
Making updates/downgrades impossible, just in case last time you've touched the device and upgraded to the latest firmware from Wiko (fun fact: the update app pings a site called https://frogs.wiko-ota.com, but sadly it has never been archived before and nowadays shows chinese text saying how the content doesn't exist) and you're completely stuck with the shady apps and trackers Tinno put on their P7 board;
You couldn't use stuff like adb push or upgrade from recovery because they force you to use their proprietary tool on Windows to do such (they bundle all of their firmware updates into an huge .exe file, despite being inside a .zip file);
And more...
Despite everything, i found one crack into the phone to take advantage of: you can reboot on EDL mode via adb
And that's where my guide begins!
Requirements:In order to convert your Wiko to a Yureka Black, you must need...
Your Wiko UFeel Prime (whatever firmware, either it is M or N);
Another Android phone (must have: Magisk root, OTG Cable support);
An OTG adapter;
A charging cable (must be able to transfer data);
Preparing your rooted Android device:Moving on, your device must have the following apps installed
ADB & Fastboot Tools;
Fox's Magisk Module Manager;
Terminal Emulator;
After got the latter, do the following steps afterwards
Open the Fox MMM app;
Tap the search button (placed on the bottom right corner of the screen);
Type "QDL" or "Qualcomm" into the bar;
You should find a tool called QDL For Android NDK;
Tap on "Install";
Tap on "Install Module";
Wait for the module to install;
Reboot your device;
After reboot, open the ADB & Fastboot tools app;
Allow root perms;
As a last step (for now), you must hop over the YU Yureka Black QFIL files page and download the zip file under the Stock M File hyperlink- after doing that, extract the .zip file wherever you want (with your fav file explorer of choice) (for simplicity's sake: extract the zip out of the Download folder. After extraction, rename the "YU5040" etc. etc. folder as simply "yu"- the purpose of it will come in handy further on the guide).
As of now, leave your secondary phone as is and move to the Wiko phone.
Preparing your Wiko UFeel Prime:If you had setup your secondary phone successfully: preparing your Wiko phone will be 10 times easier than the latter.
Just follow thru the following steps:
Go to Settings;
Tap on the "About" section of your device;
Tap a ton of times on the Build number, until the following will tell you you had unlocked Developer Settings;
Go back;
Tap on Developer Settings;
Scroll until you find USB Debug and enable it;
As a last thing, if you prefer, jump straight to the home menu (on your Wiko), then lay the phone together with the other device on a safe spot where nobody could interfere on the work.
The next title will introduce you to the "delicate" part of the guide: but also the moment where your Wiko will finally get converted as a YU Yureka Black and allow modding!
Converting your Wiko:Now, follow carefully the steps i'm about to give
On your secondary device
Open the ADB & Fastboot tools app;
Connect on the device's slot the OTG cable;
On your Wiko
Connect the charging cable to it's slot;
Connect the cable's end (the USB part) to the OTG slot attached to the other device;
Tap on "Allow" if it asks you about USB debug (or generally allowing a pc to get access to the device);
On your secondary device
Tap on the "Refresh" button (placed on the top right part of the app's UI);
Scroll on the bottom of the screen;
Type reboot edl on the writing camp;
Tap "Execute" (which is next to the zone where you wrote the command);
If you came this far and your Wiko effectively turned off plus the notification LED started blinking RED: this means your Wiko successfully booted into EDL mode!
Now, let's move on the focus to your secondary device.
On your secondary device
Quit the ADB & Fastboot tools app;
Open the Terminal Emulator app;
Write the following commands:
Code:
cd /sdcard
cd yu
su
After typed these commands on the terminal, copy and paste this string of code on your terminal:
Code:
qdl --debug --storage emmc --include /sdcard/yu /sdcard/yu/prog_emmc_firehose_8937_ddr.mbn /sdcard/yu/rawprogram_unsparse_upgrade.xml /sdcard/yu/rawprogram_unsparse.xml /sdcard/yu/patch0.xml
Once done, tap send on your keyboard and let the program do it's magic.
The wait should vary depending on your secondary device's specs (approximates 1h at max) and the speed on writing the .mbn, .img, and .tz files inside the folder over the Wiko's board- also, pro-tip, be sure to check often on your secondary device (by tapping it's screen often).
The reason?
it will avoid the device to go into sleep mode (especially if you set the backlight to a short period of time) and once unlocked it restarts the whole flashing all over again, extending the flashing wait the double.
If an accident happens (like it happened in my case) you must resort on disassembling your device's back and short the pins with some tweezers to enter back EDL mode manually, and also repeating the flashing process by pasting again the code string on the terminal.
If you don't know how to disassemble your Wiko: check here.
Also, if you don't know which pins you should press to enter EDL mode: check here aswell.
After the long wait, you should see the following behaviors:
Your secondary device will flag a disconnection on the QDL program (via terminal);
Your Wiko phone will vibrate and start booting up, showing the YUREKA BLACK text as the splash screen;
Now you can finally unlock your bootloader (note: you must type unlock-go to do the latter) and flash your device however you like!Thanks for following my guide!---------------------
Credits:
- The Yu Yureka Black modding community;
- Sosavo;
- You, for following my guide!