Hello,
maybe someone would be able to help or explain. Running on 9.1.0.215 (but tried with 9.1.0.210 as well), after I try to root with Magisk (=flash patched recovery_ramdisk), my SMS stop working. I've tried more applications (default 'Messaging', Google 'Messages', also Facebook 'Messenger') but no chance, phone is not able to receive or create any SMS messages. However, everything else is working fine.
I'm pretty sure that it's caused by this activity, because when I flash back original RECOVERY_RAMDIS.img, SMS are back again.
Any ideas what could be wrong? I really like to use Magisk, but unfortunately, it's no go without SMS.
Thanks!
1. Flash stock recovery_ramdisk. (If you already flash magisk patched ramdisk). Stock recovery is needed to factory reset.
2. back up your data.
3. reboot to recovery. Perform factory reset
4. Power off device. Hold volume down, plug usb to boot to bootloader.
5. flash magisk patched recovery ramdisk
6. Reboot by holding power + volume up button.
7. Done
buchman said:
1. Flash stock recovery_ramdisk. (If you already flash magisk patched ramdisk). Stock recovery is needed to factory reset.
2. back up your data.
3. reboot to recovery. Perform factory reset
4. Power off device. Hold volume down, plug usb to boot to bootloader.
5. flash magisk patched recovery ramdisk
6. Reboot by holding power + volume up button.
7. Done
Click to expand...
Click to collapse
Thanks for hint!
Doing factory reset isn't exactly one's wish, but if there is no other choice I will definitely give it a try. Speaking of backup/restore of apps - can you please give me a hint, what could be the most comfortable way of doing that? I do not care about data - that is easy to backup/restore - but is there any simple way how to avoid manual re-installation of all apps after restore?
Thanks again!
burton_mb said:
I'm pretty sure that it's caused by this activity, because when I flash back original RECOVERY_RAMDIS.img, SMS are back again.
Click to expand...
Click to collapse
Hi, just to confirm that I had exactly the same problem. To solve it, I had to reinstall the original recovery ramdisk.
burton_mb said:
Thanks for hint!
Doing factory reset isn't exactly one's wish, but if there is no other choice I will definitely give it a try. Speaking of backup/restore of apps - can you please give me a hint, what could be the most comfortable way of doing that? I do not care about data - that is easy to backup/restore - but is there any simple way how to avoid manual re-installation of all apps after restore?
Thanks again!
Click to expand...
Click to collapse
When you go through the setup it should suggest it if you've backed up to drive. Otherwise use titanium backup. It saves the apks and works with root
pierangelof said:
Hi, just to confirm that I had exactly the same problem. To solve it, I had to reinstall the original recovery ramdisk.
Click to expand...
Click to collapse
But reinstall original recovery ramdisk means no root, right?
Did you succeed with rooting afterwards, e. g. with factory reset like suggested above?
burton_mb said:
But reinstall original recovery ramdisk means no root, right?
Click to expand...
Click to collapse
Yes, this was the price to pay to get the SMS working again
burton_mb said:
Did you succeed with rooting afterwards, e. g. with factory reset like suggested above?
Click to expand...
Click to collapse
I haven't tried it, sorry.
I ran into this problem on my honor 9 and in addition to a not working sms-app,the dialer app was broken aswell.
I did find this thread https://forum.xda-developers.com/mate-10/how-to/fix-messages-dialer-9-1-root-required-t3955964 and this fixed both issues.
adb shell
su
rm /data/user/0/com.android.providers.telephony/databases/*
rm /data/user/0/com.android.providers.contacts/databases/*
Go back to phone and wipe data of Phone and Messages
Go back to command prompt and:
reboot recovery
Sheepy777 said:
I ran into this problem on my honor 9 and in addition to a not working sms-app,the dialer app was broken aswell.
I did find this thread https://forum.xda-developers.com/mate-10/how-to/fix-messages-dialer-9-1-root-required-t3955964 and this fixed both issues.
adb shell
su
rm /data/user/0/com.android.providers.telephony/databases/*
rm /data/user/0/com.android.providers.contacts/databases/*
Go back to phone and wipe data of Phone and Messages
Go back to command prompt and:
reboot recovery
Click to expand...
Click to collapse
Thank you very much! This helped even without factory reset! :good::good::good:
burton_mb said:
Thank you very much! This helped even without factory reset! :good::good::good:
Click to expand...
Click to collapse
Glad I could help I tried a factory reset and rooted afterwards, but as soon as magisk was flashed, sms stopped working and tons of "access denied" or so errors started to show up in the log.
Hello, is it still possible to root the phone? I want to get rid of all the huawei apps and I need adaway.
timenewroman said:
Hello, is it still possible to root the phone? I want to get rid of all the huawei apps and I need adaway.
Click to expand...
Click to collapse
If your bootloader is unlocked, yes it's still possible
Sheepy777 said:
If your bootloader is unlocked, yes it's still possible
Click to expand...
Click to collapse
And any chances of unlocking the bootloader with Android 9?
Enviado desde mi STF-L09 mediante Tapatalk
xaametz said:
And any chances of unlocking the bootloader with Android 9?
Enviado desde mi STF-L09 mediante Tapatalk
Click to expand...
Click to collapse
I unlocked my bootloader last year, when you could get the unlock code from their website. Unlocking your bootloader on Pie with one of those codes should still work.
I don't know, if other unlocking method like dc-unlocker or funkyhuawei will work. Sry
Sheepy777 said:
I ran into this problem on my honor 9 and in addition to a not working sms-app,the dialer app was broken aswell.
I did find this thread https://forum.xda-developers.com/mate-10/how-to/fix-messages-dialer-9-1-root-required-t3955964 and this fixed both issues.
adb shellsurm /data/user/0/com.android.providers.telephony/databases/*rm /data/user/0/com.android.providers.contacts/databases/*Go back to phone and wipe data of Phone and MessagesGo back to command prompt and:reboot recovery
Click to expand...
Click to collapse
Thank youuuuuu this worked perfectly for me. I had to change the directory name from user to user_de, but once I did that, it was perfect And I didn't even lose my text messages
Oh no This solution worked, but after doing it, I no longer have access to 4G/LTE on my phone. Did this happen to anyone else? Is there a fix for this?
Related
Hey all used this guide to upgrade stock jellybean,
http://forum.xda-developers.com/showthread.php?t=1909819
Worked brilliantly and then got above my skill level when removing some bloatware, normally i copy the apks i remove however this time i pressed delete by mistake, now have huge issues with play store and other apps. I have deleted too many apks
Have tried installing google apks again but still no joy. Does any one know of a way i can install JB again to start afresh i did try downgrading as per the guide but that didnt actually remove the JB firmware. I feel although even with huge amounts of help from flumpster (many thanks) we arnt cracking it so a fresh install is prob best, i just hope someone knows how to.
Thanks in advance.
wesley.neary said:
Hey all used this guide to upgrade stock jellybean,
http://forum.xda-developers.com/showthread.php?t=1909819
Worked brilliantly and then got above my skill level when removing some bloatware, normally i copy the apks i remove however this time i pressed delete by mistake, now have huge issues with play store and other apps. I have deleted too many apks
Have tried installing google apks again but still no joy. Does any one know of a way i can install JB again to start afresh i did try downgrading as per the guide but that didnt actually remove the JB firmware. I feel although even with huge amounts of help from flumpster (many thanks) we arnt cracking it so a fresh install is prob best, i just hope someone knows how to.
Thanks in advance.
Click to expand...
Click to collapse
I would assume you can do a factory reset. With the until off, press and hold vol dwn, then press and hold the pwr button for a few seconds, release the pwr button but continue to hold vol dwn, then release when the bootloader is displayed, from there you should have an option to Wipe Data (Factory Reset).
imadork8317 said:
I would assume you can do a factory reset. With the until off, press and hold vol dwn, then press and hold the pwr button for a few seconds, release the pwr button but continue to hold vol dwn, then release when the bootloader is displayed, from there you should have an option to Wipe Data (Factory Reset).
Click to expand...
Click to collapse
I did try try that however it didnt replace the missing apps.
wesley.neary said:
I did try try that however it didnt replace the missing apps.
Click to expand...
Click to collapse
enter the bootloader, select Fastboot (USB icon)
Go to this forum and download the jb-twrp-recovery
http://forum.xda-developers.com/showthread.php?t=1911024
>> Download tf201-jb-twrp-recovery.blob and flash it via fastboot (fastboot -i 0x0b05 flash recovery tf201-jb-twrp-recovery.blob) and reboot.
Click to expand...
Click to collapse
Go back and follow the steps again
INSTRUCTIONS:
1. Download the ROM update zip (us-tf201-jro03c-10.4.2.15-stock-deodexed.zip)
2. Download the Superuser update zip (Superuser-3.2-arm-signed.zip)
3. Copy the files to your device and reboot into recovery
4. Wipe data/factory reset [VERY IMPORTANT STEP!! Just use the recovery wipe/factory reset, do not use any full wipe update zips or scripts]
5. Flash the ROM update zip and immediately after that, flash the Superuser update zip.
6. Reboot your device and wait for the new bootloader, kernel & recovery to flash (the blue progress bar) and then let the device boot up.
7. Enjoy JB on your device!!
Click to expand...
Click to collapse
imadork8317 said:
enter the bootloader, select Fastboot (USB icon)
Go to this forum and download the jb-twrp-recovery
http://forum.xda-developers.com/showthread.php?t=1911024
Go back and follow the steps again
Click to expand...
Click to collapse
The poster is not unlocked and cannot do this.
wesley, you know I told you to force close them apps and wipe data and cache for them, did you restart before trying play again?
flumpster said:
The poster is not unlocked and cannot do this.
wesley, you know I told you to force close them apps and wipe data and cache for them, did you restart before trying play again?
Click to expand...
Click to collapse
Yes force stopped wiped data and rebooted but still as soon as device reboots i get the error google play store has stopped.
Thanks for all your help guys it is appreciated, and is probably all that has stopped me throwing the thing at the wall.
wesley.neary said:
Yes force stopped wiped data and rebooted but still as soon as device reboots i get the error google play store has stopped.
Thanks for all your help guys it is appreciated, and is probably all that has stopped me throwing the thing at the wall.
Click to expand...
Click to collapse
because you are not unlocked we are purely guessing on fixes for this at the moment but I know you now have google services framework back. When you was asked above to do the volume down and power and then select wipe was this done after we got google services back or before?
flumpster said:
because you are not unlocked we are purely guessing on fixes for this at the moment but I know you now have google services framework back. When you was asked above to do the volume down and power and then select wipe was this done after we got google services back or before?
Click to expand...
Click to collapse
The plot thickens as now i tried the wipe as described and its force closing on the new setup wizard im guessing im running out of options as i now cant get past the setup wizard.
wesley.neary said:
The plot thickens as now i tried the wipe as described and its force closing on the new setup wizard im guessing im running out of options as i now cant get past the setup wizard.
Click to expand...
Click to collapse
Well there are still options. If you had USB debugging enabled in developer options you can still adb stuff to the device. If you don't as a last resort you could unlock the bootloader and install it as a custom rom. Also as you are not unlocked at all asus would probably accept it as an rma under warranty.
flumpster said:
Well there are still options. If you had USB debugging enabled in developer options you can still adb stuff to the device. If you don't as a last resort you could unlock the bootloader and install it as a custom rom. Also as you are not unlocked at all asus would probably accept it as an rma under warranty.
Click to expand...
Click to collapse
Ok how can i tell if i still have adb and if so whats the best file to try and push.
wesley.neary said:
Ok how can i tell if i still have adb and if so whats the best file to try and push.
Click to expand...
Click to collapse
You need to have the adb files on your computer. Open a command prompt where adb files are by holding down shift and right clicking on the folder adb is in and selecting open command prompt here. Then type adb devices into command window.
if you get waiting check in your device manager to see if you have any devices with explanation marks on it. If there are then install naked drivers from the top of developer section.
Hello,
I've looked around, but I haven't found anyone with this peculiar error message. So, I'm trying to flash the 5.0.2 OTA on my N9, but I get this message:
package expects build fingerprint of google/volantis/flounder:5.0.1/LRX22C/1602158:user/release-keys or google/volantis/flounder:5.0.2/LRX22L/1816899:user/release-keys; this device has google/omni_flounder/flounder:5.0.2/LRX22G/dees_troy03251233:eng/test-keys
I thought it was because I had a modifier my kernel boot.img (to unencrypt my N9), so I restored the stock IMG. It encrypted my tablet after a reboot. I came back in recovery, but I still get the message. I'm rooted/unlocked, stock Android and xposed is also installed. Before returning my N9 to it's stock state, I wanted to know if there was something I could try? What does the message means?
Thanks a lot!
I'm on the same boat,kinda...Stock ROM,only rooted...Is there an easy way to unroot without wiping the device?
It has already been reported that you can't simply install the OTA .zip as it comes, since Google is doing a checksum to the whole partitions (i guess boot and system) and as long as this isn't the original, it won't allow for the installation of the update.
I am not sure how can you override this check and make the .zip to install without reverting to a perfect stock (kernel+rom) system.
Flash the factory image (there is a line on the instal file that you need to edit so it doesn't wipe) or you can download the image , extract the zip inside and manually flash the system partition. Then try to run the update
Sent from my Nexus 9 using Tapatalk
Hello,
I've figured it out. I've used "WugFresh Nexus Rootkit 2.0.5" to flash LRX22C without Wiping the userdata and I was then able to apply the OTA 5.0.2.
Thanks for the help guys!
Majesty00 said:
Hello,
I've figured it out. I've used "WugFresh Nexus Rootkit 2.0.5" to flash LRX22C without Wiping the userdata and I was then able to apply the OTA 5.0.2.
Thanks for the help guys!
Click to expand...
Click to collapse
I must really be stupid not finding exactly what to choose,can you please tell me which option did you use on Wug's Toolkit?Thanks in advance!
tagari said:
I must really be stupid not finding exactly what to choose,can you please tell me which option did you use on Wug's Toolkit?Thanks in advance!
Click to expand...
Click to collapse
Sure, no problem. I did Option #1 from this FAQ:
http://www.wugfresh.com/faqs/how-to-update-ota-not-working/
Good luck!
Majesty00 said:
Sure, no problem. I did Option #1 from this FAQ:
http://www.wugfresh.com/faqs/how-to-update-ota-not-working/
Good luck!
Click to expand...
Click to collapse
Cheers mate!! I was looking in the advanced utilities!!THanks for your time !!
Hm... I tried the Wug method, and it was erroring out on the "flash LRX22C without Wiping the userdata" step, so it told me to check "Force Flash". I did, and it seemed to work, but I had to manually reboot (it didn't reboot for me at the end like it was supposed to). Now I'm stuck in an eternal bootloop. I can't get past the colored balls, and I can't turn the dang thing off; holding down the power button just performs endless force restarts.
Only thing I can think of is to run the battery down, plug it in, then go to the bootloader and do the Flash Stock + Unroot option again. Any other suggestions?
Thanks
generosity21 said:
Hm... I tried the Wug method, and it was erroring out on the "flash LRX22C without Wiping the userdata" step, so it told me to check "Force Flash". I did, and it seemed to work, but I had to manually reboot (it didn't reboot for me at the end like it was supposed to). Now I'm stuck in an eternal bootloop. I can't get past the colored balls, and I can't turn the dang thing off; holding down the power button just performs endless force restarts.
Only thing I can think of is to run the battery down, plug it in, then go to the bootloader and do the Flash Stock + Unroot option again. Any other suggestions?
Thanks
Click to expand...
Click to collapse
Did you try a factory reset in Hboot in the bootloader menu? Just hold the volume down button when it reboots, select Hboot, then Factory Reset. Or do the same to boot into the bootloader and try Wug's toolkit again with force flash AND the wipe settings I think it is. I checked, it's with the 'No Wipe Mode' unchecked.
KedarWolf said:
Did you try a factory reset in Hboot in the bootloader menu? Just hold the volume down button when it reboots, select Hboot, then Factory Reset.
Click to expand...
Click to collapse
You're a genius. I keep reading that I need to hold power+vol down+vol up. Holding power+vol down got my right out of the boot loop, and so I'm back in Bootloader and can hopefully get it figured out from there. Thanks!
generosity21 said:
so I'm back in Bootloader and can hopefully get it figured out from there. Thanks!
Click to expand...
Click to collapse
You can't flash the OTA if you are rooted. If you want to go the OTA route you will need to flash the stock 5.0.1 system.img, boot.img(if you have a modified kernel) and vendor.img first.
F.Y.I.
even if you mount vendor and or system
as rw and still change nothing
that will not let the ota flash
I'm trying to dump some files so i can try and make a custom ROM how ever i was told that i should restore so that there are not any junk files in my system folder. how ever when i try to restore using the settings app i get stuck in a infinite boot screen. im unrooted and am using the stock recovery i have been able to get my device working again by flashing twrp and restoring an nandroid how ever i want a fresh EMUI install that i can use to dump the ROM. Thanks in advance.
0v3r cl0ck3d said:
I'm trying to dump some files so i can try and make a custom ROM how ever i was told that i should restore so that there are not any junk files in my system folder. how ever when i try to restore using the settings app i get stuck in a infinite boot screen. im unrooted and am using the stock recovery i have been able to get my device working again by flashing twrp and restoring an nandroid how ever i want a fresh EMUI install that i can use to dump the ROM. Thanks in advance.
Click to expand...
Click to collapse
Your queries are not clear. What exactly do you need?
rspn69 said:
Your queries are not clear. What exactly do you need?
Click to expand...
Click to collapse
Otherwise follow these steps if your factory reset fails through app
Caution - You will loose all your data and user installed apps
Switch off the phone
Wait for 10 seconds
Press volume up and power button and hold until it vibrates
select factory reset
confirm factory reset and wait until process completes
restart your phone
and thank me if it worked for you
rspn69 said:
Your queries are not clear. What exactly do you need?
Click to expand...
Click to collapse
NVM i managed to do it thanks anyway though
rspn69 said:
Otherwise follow these steps if your factory reset fails through app
Caution - You will loose all your data and user installed apps
Switch off the phone
Wait for 10 seconds
Press volume up and power button and hold until it vibrates
select factory reset
confirm factory reset and wait until process completes
restart your phone
and thank me if it worked for you
Click to expand...
Click to collapse
I managed to do it a different way but thanks for taking the time to help
0v3r cl0ck3d said:
I managed to do it a different way but thanks for taking the time to help
Click to expand...
Click to collapse
Its my pleasure dude....after all sharing is caring:good::good:
Hey guys.
The below is my full experience of how I flashed TWRP, the Xiaomi.eu rom and rooted with Magisk. Whilst it essentially is a step-by-step, it also contains not only how I succeeded but also how I encountered issues and so...
*UPDATE!*
Here is a slightly condensed verison with thanks to @airwebber
Get the latest xiaomi.eu rom from here or here, just scroll down and find the "xiaomi.eu_multi_MI9..." version.
https://sourceforge.net/p/xiaomi-eu...ty/?page=0&limit=100#5cb9f96ee8ba7c44716e87ff
Get the latest magisk (magisk v19 works at the time of writing this post):
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Some versions of twrp may not work on older builds other than the latest (9.4.25) and so use this one with:
https://mega.nz/#!CH5jgYTB!yNqOiVoo3cf0_15jIwZ-btO52cvpOG7iZrRCe19V2Nc
Once the waiting time elapses (usually 360 hours) use the MiFlash tool to unlock the bootloader. Warning: this wipes your phone entirely, so be sure to backup anything of importance.
Unlocking takes a few minutes and once 100% complete your Mi 9 will reboot. Your phone will say “unlocked” on the first splash screen while booting up.
Your Mi 9 will boot, and you will need to either perform/skip the initial setup stuff. Once ready, power off your device in order to flash TWRP.
Press both the volume down key and power key to boot into Fastboot Mode.
Once in Fastboot Mode, use the following command to install TWRP: “fastboot flash recovery XXXX” (XXXX = the pathway to your TWRP.img file). However, I find it best using Minimal ADB and copying the TWRP file and renaming it to “twrp.img” for ease) in the Minimal ADB folder location e.g. “C:\Program Files (x86)\Minimal ADB and Fastboot”.
Once flashed, disconnect the USB cable and boot to TWRP recovery by holding down both the volume up and the power buttons. This sometimes will bring you to the stock recovery and NOT TWRP! If it does, boot back to Fastboot and reflash TWRP.
Once you can boot to TWRP, push both the rom and magisk via CMD line:
adb push rom.zip /tmp/
adb push magisk.zip /tmp/
For ease, I suggest copying both files to the Minimal ADB folder location e.g. “C:\Program Files (x86)\Minimal ADB and Fastboot”. And renaming them to: “rom.zip” and “magisk.zip”.
This step is very important!! You must go to the Wipe menu and select: Format Data, then type “yes” to continue and then: do a Factory reset, which also wipes: Data, Caches and Format Data. If you skip this step you won’t be able to install a lot of important apps and will have to start over.
Now that you have pushed both the rom & magisk and wiped everything you needed to. Install the ROM immediately after install magisk.zip (in that order) both located in /tmp/.
The installation will take a couple of minutes (if your screen dims, don’t worry that’s just TWRP screen dimming, touch the screen to keep it awake!) once finished with no errors, then reboot and chose Do Not Install the TWRP app when prompted.
The phone will take a few seconds to reboot and show the first MI splash screen, but it should start booting. After a couple of minutes, you should see the initial boot screen! Perform the setup (connecting to Wi-Fi, adding my Google account etc.).
Once finished setting up, you may notice that magisk was not installed, if that happens, you can install the APK version and follow the prompts and reboot.
Once rebooted, confirm that magisk is now installed. If it is, I suggest installing SafetyNet and confirming your phone passes!
If it passes, you have successfully installed and rooted the Xiaomi.eu rom!
Also, when updating with each weekly I recommend the below as an alternative to using the built in Updater app. The reason being is I believe the updater app automatically reboots after it installs, which if you're rooted means you'll lose it. That then means you have to reboot back to twrp, reflash magisk, reboot, reinstall modules, reboot again etc.
Therefore to update a weekly:
Download the rom manually
Reboot to twrp
Wipe system and caches
Flash the rom and magisk
Reboot
Optional: I also disable my substratum theme too before updating and reapply afterwards. Whether it's needed or not I'm not too sure, so give it a try either way
Awesome, all files at the ready! BTW get the latest MIUI from HERE or HERE.
Make sure you download the xiaomi.eu_multi_MI9_xxx.zip.
The Dutchman said:
Awesome, all files at the ready! BTW get the latest MIUI from HERE or HERE.
Make sure you download the xiaomi.eu_multi_MI9_xxx.zip.
Click to expand...
Click to collapse
Thanks, first post updated!
cd993 said:
Thanks, first post updated!
Click to expand...
Click to collapse
You have used the Magisk Canary build I presume?
And great job for writing it down.... Now I remember the same culprits I had of flashing TWRP. [emoji23]
*justintime* said:
You have used the Magisk Canary build I presume?
And great job for writing it down.... Now I remember the same culprits I had of flashing TWRP. [emoji23]
Click to expand...
Click to collapse
That's right:
Magisk-v18.2-51110866(18116).zip
If I can find the link (of if someone can link me to it) I'll update the posy
cd993 said:
That's right:
Magisk-v18.2-51110866(18116).zip
If I can find the link (of if someone can link me to it) I'll update the posy
Click to expand...
Click to collapse
Here ya go.
https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
*justintime* said:
Here ya go.
https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
Click to expand...
Click to collapse
Thanks, updated!
Rommco05 said:
Good stuff for early roots without not tested stuff like twrp and magisk but I would hide that middle part coz some people can get be confused. Or make a short version which working in order and another with your all step's but separately
edit: still 46h left
Click to expand...
Click to collapse
Yeah I agree it's kinda overkill, being a a full run down - when I get time I'll make a shorter condensed version
Thanks for the detailed write up. The EU roms are google approved correct? Does the side Ai button work with google assist? Do you need to install twrp to flash or can I just flash global/EU rom if I don't want to root yet?
I just got the bootloader unlocked (1h before than I tought ahahah). I had some issue that the unlocker was telling to me thaat I didn't use enought the phone and that so I had to try in few days I overtook the problem using an old version of the unlocker (2.3.803.10).
Reading your procedure it all logical and fine, thanks! Except one thing that I'm not sure... Is xiaomi.eu a 'full rom' (on all Xiaomi that I had I always jumped straight to something different than MIUI and so I never tried it ahahah )?
If so, I think it would be better to wipe the system too before installing the rom. That's because doing so it will do 100% 'clean' installation and not a an update on the normal global miui
perryano said:
Thanks for the detailed write up. The EU roms are google approved correct? Does the side Ai button work with google assist? Do you need to install twrp to flash or can I just flash global/EU rom if I don't want to root yet?
Click to expand...
Click to collapse
Hmm unsure about them being approved or not... The side button does work. As far as I understand, you'll need to install twrp in order to flash the new rom, but could always go back to stock recovery and of course no need to root if you don't want to
mr-mauro said:
I just got the bootloader unlocked (1h before than I tought ahahah). I had some issue that the unlocker was telling to me thaat I didn't use enought the phone and that so I had to try in few days I overtook the problem using an old version of the unlocker (2.3.803.10).
Reading your procedure it is more or less everything fine except one thing that I'm not sure. is xiaomi.eu a full rom? If so, I think it would be better to wipe the system too before installing the rom because instead it will try to to an update on the normal global miui rather than a 100% 'clean' installarion
Click to expand...
Click to collapse
That's a fair point - if you have some this successfully then perhaps I'll amend my post. Sometime soon I'll make a small set of instructions, rather than my essay
cd993 said:
That's a fair point - if you have some this successfully then perhaps I'll amend my post. Sometime soon I'll make a small set of instructions, rather than my essay
Click to expand...
Click to collapse
aahahha, yes, it looks like an essay. I'm trying it now... If it fail I'll scream ahahaha
mr-mauro said:
aahahha, yes, it looks like an essay. I'm trying it now... If it fail I'll scream ahahaha
Click to expand...
Click to collapse
Let us know
cd993 said:
Let us know
Click to expand...
Click to collapse
It just boot So, it is fine I just noticed TickTock as a default app installed by Xiaomi.eu
P.S. FYI I noticed that the devices is seen by Google as a Mi Mix 2S
mr-mauro said:
It just boot So, it is fine I just noticed TickTock as a default app installed by Xiaomi.eu
Click to expand...
Click to collapse
Great!
Ahh I did see 1 random app. But then I debloated a went away
cd993 said:
Great!
Ahh I did see 1 random app. But then I debloated a went away
Click to expand...
Click to collapse
Luckily in those two waiting-weeks I had time to test all the debloat that I wanted to come with a stable configuration today It's just a pity that we can't get rid completely of the Security app It is integrated too much in the system!
One quick question for who has installed Xiaomi EU with Magisk: does it pass SafetyNet to you? (to me no )
cd993 said:
Hmm unsure about them being approved or not... The side button does work. As far as I understand, you'll need to install twrp in order to flash the new rom, but could always go back to stock recovery and of course no need to root if you don't want to
Click to expand...
Click to collapse
So once bootloader is unlocked I can install TWRP and flash the EU rom without rooting?
mr-mauro said:
It just boot So, it is fine I just noticed TickTock as a default app installed by Xiaomi.eu
P.S. FYI I noticed that the devices is seen by Google as a Mi Mix 2S
Click to expand...
Click to collapse
Yeah, to change the device name back to mi 9, just install "Find my device" app from Google play store, sign in with google account, there's an option in the setting to rename the device (this device).
That's the only place you can change the name back, I did try all, but only this one worked.
Hey guys, I would like to ask for advice.
My phone suddenly stuck at this screen:
Android Recovery
Xiaomi/laurel_sprout_eea/laurel_sprout
10/QKQ1.190910.002/V11.0.2.0.QFQEUXM
user/release-keys
Use volume up/down and power.
Can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data store on this device.
- Try again
- Factory data reset
Its very similar to an issue already discussed on this site: https://forum.xda-developers.com/mi-a2/help/xiao-mi-a2-load-android-t3993067?nocache=1
However, in my case, i'm unable to access the Recovery menu. It results in Error screen: https://imgur.com/a/2rPDGQa
I would really appreciate some help as i have data inside my phone which i need. So if possible i would like to retain the data.
Thanks for your help!
If you have already unlocked bootloader, flash TWRP, make backup of all partitions and copy it to the PC. If you're still with locked bootloader, then I'm afraid you're out of luck. There is probably no way how to restore user data.
Also happened to me not long ago, interesting, did you do some system changes before that?
alexandarpb said:
Also happened to me not long ago, interesting, did you do some system changes before that?
Click to expand...
Click to collapse
No, I don't think so. Although there might had been some kind of a system update few hours before.
_mysiak_ said:
If you have already unlocked bootloader, flash TWRP, make backup of all partitions and copy it to the PC. If you're still with locked bootloader, then I'm afraid you're out of luck. There is probably no way how to restore user data.
Click to expand...
Click to collapse
Hi @_mysiak_ I'm in a similar situation (Mi A3 too) but instead of eMkoC4, I can access to Recovery menu. Is there anything I can do to recover some data?
Thanks in advance, Simone
simogere said:
Hi @_mysiak_ I'm in a similar situation (Mi A3 too) but instead of eMkoC4, I can access to Recovery menu. Is there anything I can do to recover some data?
Thanks in advance, Simone
Click to expand...
Click to collapse
I would try pulling the data via ADB (if you have it enabled) in stock recovery. I am not sure how it will behave with encryption, but it's worth a try. Boot into recovery on the phone, connect it to the PC and use this command on the PC:
"adb pull /storage/emulated/0"
_mysiak_ said:
I would try pulling the data via ADB (if you have it enabled) in stock recovery. I am not sure how it will behave with encryption, but it's worth a try. Boot into recovery on the phone, connect it to the PC and use this command on the PC:
"adb pull /storage/emulated/0"
Click to expand...
Click to collapse
Hi @_mysiak_ thanks for the reply. I'm quite sure I've never enabled USB debugging
simogere said:
Hi @_mysiak_ thanks for the reply. I'm quite sure I've never enabled USB debugging
Click to expand...
Click to collapse
In such case I'm afraid that you're out of luck as well (it probably wouldn't work anyway due to encryption).