Database Develop

Xiaomi Mi 3 Ask Away- help thread.

[SIZE=+2]Welcome to
Questions Answers & Troubleshooting
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This thread has been created to assist owners of:[/SIZE]
[SIZE=+2]The Xiaomi Mi3[/SIZE]
There are no questions that are deemed insignificant
Helpful information for your device:
Full device specifications
ᴥAsk Awayᴥ​
Please feel free to ask anything related to your device.​

Hi, I am unable to find the required files to root my MI3. All the links that i find after googling don't have the correct files. My MIUI version is MIUI 6.6.3.0(KXDCNCF). Any help would be appreciated.

Whiskeyjack4855 said:
Hi, I am unable to find the required files to root my MI3. All the links that i find after googling don't have the correct files. My MIUI version is MIUI 6.6.3.0(KXDCNCF). Any help would be appreciated.
Click to expand...
Click to collapse
I used MIUI for about 30 minutes before moving to AOSP, but I thought it came already rooted...
All the same, you can install SuperSU, which is the best root manager. It's on the play store, or you can go to Recovery and flash the zip file in the first post here http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133

I'm trying to install CWM on MIUI 7. But I'm unable to flash it using Updater. I've tried revision 8, revision 11 and revision 11 u1 by furniel... It just keeps saying something went wrong

Annoying sound from the ear piece
There will be an annoying sound from the ear piece of the device while booting up and while on a call. We all know that,but I would like to ask, is there any workaround for that? The sound really is a head ache causing thing with its low frequency noise

@sarathchandraj
I had the same issue, but the Rashr app helped me. Try it. Just download the recovery image, open Rashr, select "Recovery from storage" andthen select your recovery image. But if CWM is not necessary to you, use TWRP. CWM is buggy on Mi3.

Hi guys, I replaced my broken LCD with the new one recently. I am facing an issue. when replacing the LCD display, my lower charge port assembly was not coming out of the main body. I tried hard and in that process I slightly lifted the metallic part underneath the charging port. I thought that metallic thing is a part of main body. The metal is still with ribbon assembly firmly. not detached. But my loud (external, which is in the back)speaker is not working and also home and back button backlit are not glowing. menu button light works ok. speaker gives very faint sound though. What can be the reason. Speaker is ok I guess, as it was working well before replacement.
I know it's a software related issue forum but as you guys are having the same mobile, I think you all might have an idea about it.

please give QCN file

Hi
---------- Post added at 06:27 PM ---------- Previous post was at 06:21 PM ----------
Hi guys, I am in big problem. .. im using mi3 xiaomi and i just up to mokee 5.1 and its runing. The problem is i forget my gapps. So now im runing without a gapps. I cant flash either roots or even upgrade also. Can anyone help me.....please!!?

Hiii...i am unable to go back to miui 7 from cm 12.1. I have downloaded latest miui 7 build and renamed it "update.zip" and tried it to flash via stock recovery. Installation went fine but after restarting it's getting stuck on MI logo.... Please help.. Missing Miui...

Hello, after many years of running with Ivan's 4.4.4 AOSP I feel like it's time to move to something newer so I wanted to try and flash the 6.0.1 new one seeing as he released the final version. It has been few years since I last flashed a rom so I mostly forgot the procedure. Chcked few threads but overall I still have some confusion. If someone can clear up the doubts I'd be grateful.
Currently: MI3W with Ivan AOSP 4.4.4 and CWM
Here's what I was currently planning to do:
ttp://en.miui.com/thread-209941-1-1.html
Following this guide to merge the partitions and install TWRP.
Now for the questions:
1. Will the flash.bat merge the partions AND install TWRP too all at once? Will it overwrite my current CWM without any problem or do I need to install it separately?
2. Once the flashing there is done, how should I proceed to install the 6.0.1 ROM? Usual procedure? (load zip on SDCard,wipe all, and flash zip).
3. Will Ivan's ROM be Rooted/Have Gapps on default?
Thanks to whoever can solve these doubts for me.

unable to flash gapps
please help me friends, i am unable to flash gapps on cm13, mokee. i am able to flash the rom zip but after that when i flash gapps it gives me error insufficient space..

Hi my friend is having a problem with her Mi3. No custom ROM installed, it's updated to the latest version. After trying to update Hearthstone, and downloading 99%, the download failed with error 903. Looked around for a fix, saw a solution that required clearing data+cache and uninstalling updates of the Play Store app. Did that and now when trying to download the app the error that is returned is
java.lang.SecurityException: No permission to write to /storage/emulated/0/Android/obb/com.blizzard.wtcg.hearthstone/temp.main.1355705.com.blizzard.wtcg.hearthstone.obb:
Neither user 10050 nor current process has android.permission.WRITE_EXTERNAL_STORAGE.
at android.os.Parcel.readException(Parcel.java:1620)
at
android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:183)
at
android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:135)
at
android.content.ContentProviderProxy.insert(ContentProviderNative.java:476)
at
android.content.ContentResolver.insert(ContentResolver.java:1234)
at com.google.android.finsky.download.l.run(SourceFile:182)
at android.os Handler.handleCallback(handler.java:739)
at android.os.Handler.dispatchMessage(Handler.java:95)
at android.os.Looper.loop(Looper.java:148)
at android.os.HandlerThread.run(HandlerThread.java:61)
Click to expand...
Click to collapse
Other apps (Zalora, pinterest) are installing fine. The phone has more than enough storage space to run the game, upwards of 3 GB
Any advice or assistance is appreciated.

hi, i'm not new to android, but it's been a few years after using windows phone, but i'm back to android for a while. why does everybody say you'll need a rooted phone to install a custom rom? i never had to root my phone to flash a custom rom.

Hi. I am returning to XDA after a long time. I am looking for a stable Custom Rom for my Mi3. What is the popular rom as of now for Mi3 ?

HELP NEEDED!!! Not able enter fastboot or recovery mode
I was trying to flash miui 8 developer ROM onto my mi3 device which didn't have any os installed.
After flashing the ROM, I selected "Bootloader" Option in "Reboot" menu in TWRP.
Now, phone neither switching on nor entering into either of fastboot or recovery modes.
Even if I connect my phone to charger no response like doesn't vibrate and screen never turns on.
If I connect the phone to my linux machine around 6 disks are mount.
Please help me find out what's wrong here, how do I get the phone back online.

vjsrinath said:
I was trying to flash miui 8 developer ROM onto my mi3 device which didn't have any os installed.
After flashing the ROM, I selected "Bootloader" Option in "Reboot" menu in TWRP.
Now, phone neither switching on nor entering into either of fastboot or recovery modes.
Even if I connect my phone to charger no response like doesn't vibrate and screen never turns on.
If I connect the phone to my linux machine around 6 disks are mount.
Please help me find out what's wrong here, how do I get the phone back online.
Click to expand...
Click to collapse
It happened to me like this when I was testing out my own kernel. Have you tried to flash a custom kernel? Try entering recovery mode by holding down the volume up and power button at the same time.
Sent from my Mi 4 using XDA Labs

@kaiz16, thanks for the reply.
After bit of googling i found that i hard bricked my phone.
Using some Qualcomm drivers and Mi Flash tool I was successfully able to recover my phone by installing stock recovery ROM.

Hello, i flashed twrp in my mi3 but i didn't unlock my bootloader so when i tried to flash lineage rom on my device it started showing error and because i wiped my data before that its not booting up its stuck on the mi logo so please help me what should i do in order to get it boot again
and is this firmware related issue is yes then where can i find the correct firmware for it ?

Sudhanshu7 said:
Hello, i flashed twrp in my mi3 but i didn't unlock my bootloader so when i tried to flash lineage rom on my device it started showing error and because i wiped my data before that its not booting up its stuck on the mi logo so please help me what should i do in order to get it boot again
and is this firmware related issue is yes then where can i find the correct firmware for it ?
Click to expand...
Click to collapse
Afaik cancro doesn't have it's boot loader locked. Try flashing twrp with adb and then you can install lineage os OR you could try fastbooting miui.

I believe I have bricked my HTC One Mini 2?

Was at work using both my company phone (iPhone 5) and my personal phone (HTC One Mini 2) just fine. Put my personal phone away to get on with actual work and came home at around 5:30'ish. Played a bit ("a bit") until about 9/10pm (I think?) whereby I looked for my phone to just check things like WhatsApp and Snapchat and the phone wasn't turning on when I was holding the power button. I just thought to myself "huh, the battery must be dead" and put it to charge and the charging LED (as well as the charging screen with the "do not distribute outside htc blabla" dev screen) displayed so I just assume it's charging as per usual. Fast forward to about 1am, I have finished using my computer and decide to hop into bed. I go to turn on my phone by first powering down with power, vol up and vol down (as usual) and then try to boot the phone up. It boots as normal up until the O/S loading screen with a pac-man boot animation (I have PAC ROM installed) whereby it will freeze on the "game over" image of the boot animation and then proceed to go to a black screen. I thought to myself "hm, must be a mistake or something" and try it again to no avail. So I then go into recovery to do a fresh install and I try to wipe the phone and I do a factory reset in twrp, but upon trying to format data, the progress bar doesn't move (and so I left it overnight as I couldn't be bothered to wait). Upon leaving it overnight (1am to 7am) to format the data, I wake up to see that the progress bar hadn't moved at all from 0%. I then just thought "maybe the phone has actually formatted it but hasn't updated the image on screen so me being the dumbo I am, decided to force shut down the phone (with power, volup and voldown) and upon trying to boot the phone up again, it displays the HTC logo with the red writing, tries to boot into the O/S, fails, and then tries to boot into recovery and gets stuck in a boot loop (it will show the twrp logo and then a black screen, twrp logo and then black screen etc.). I have tried to flash twrp again (without first removing the twrp currently on it) but I was wondering what I could do in this situation. I am able to access the bootmenu (for hboot and fastboot) but nothing else.
TL;DR: I think I bricked my HTC One Mini 2. Came home, charged phone and phone got stuck at boot animation. Wiped phone in recovery, it got stuck on formatting data and now It can't boot into the O/S since it's wiped and it can't boot into Recovery for whatever reason.

DistincTHD said:
blah blah
Click to expand...
Click to collapse
This is not Facebook, go straight to the point.
Did you install a different kernel?

kativiti said:
This is not Facebook, go straight to the point.
Did you install a different kernel?
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sorry for the confusion, I wasn't doing that because I couldn't/didn't want to explain, it's just a common message people get after dev unlocking their HTC phones. And no, It was working up until when I tried to use it last night randomly. I flashed PAC-ROM ages ago (like maybe 2-3 weeks ago or maybe even a month) with the HTC One M9 Camera Kernel and that's it. I then tried to use it last night and what I explained in the original post occurred.

DistincTHD said:
[IMG="HTC Dev Message"]
Sorry for the confusion, I wasn't doing that because I couldn't/didn't want to explain, it's just a common message people get after dev unlocking their HTC phones. And no, It was working up until when I tried to use it last night randomly. I flashed PAC-ROM ages ago (like maybe 2-3 weeks ago or maybe even a month) with the HTC One M9 Camera Kernel and that's it. I then tried to use it last night and what I explained in the original post occurred.
Click to expand...
Click to collapse
Oops, Just realised you meant the whole post, not just the blah blah bit within the post. But yeah what I did, I explained above and in the original post. I basically just told a story to give a better idea of what generally happened before the phone just pooped out on me.

DistincTHD said:
Sorry for the confusion, I wasn't doing that because I couldn't/didn't want to explain, it's just a common message people get after dev unlocking their HTC phones. And no, It was working up until when I tried to use it last night randomly. I flashed PAC-ROM ages ago (like maybe 2-3 weeks ago or maybe even a month) with the HTC One M9 Camera Kernel and that's it. I then tried to use it last night and what I explained in the original post occurred.
Click to expand...
Click to collapse
Something its corrupted so try to reinstall everything using the files from this post plus your choosen ROM.
When rebooting phone unplug USB cable.

kativiti said:
Something its corrupted so try to reinstall everything using the files from this post plus your choosen ROM.
When rebooting phone unplug USB cable.
Click to expand...
Click to collapse
I can't access twrp recovery but I do have fastboot enabled and working and I can access the boot menu so how would I go about wiping everything before re-flashing the recovery and then re-installing the o/s and everything else?

Just tried to first erase everything before installing and it's locking me out of the phone? It's telling me that an administrator console is unable to erase the system or its data so I'm quite stumped at the moment

DistincTHD said:
Just tried to first erase everything before installing and it's locking me out of the phone? It's telling me that an administrator console is unable to erase the system or its data so I'm quite stumped at the moment
Click to expand...
Click to collapse
you don't need to do all that.
try to flash twrp. (if OK use it to wipe everything)
If NOT ok flash stock recovery and unlock bootloader( yes again, this will wipe your phone and fix permissions)
Then you can do all you want.
Good luck.
let me know...

kativiti said:
you don't need to do all that.
try to flash twrp. (if OK use it to wipe everything)
If NOT ok flash stock recovery and unlock bootloader( yes again, this will wipe your phone and fix permissions)
Then you can do all you want.
Good luck.
let me know...
Click to expand...
Click to collapse
Right, so before I read that message, I flashed stock recovery and tried to reformat data and now It won't let be get into the boot menu and the HTC dev writing is gone (so I think it's locked again). On top of this, it just keeps booting into the reformatting data screen and just ends up hanging so I think I will let the battery drain or something (no idea how long it would take, probably days) and then try again from there. Pretty sure it is bricked now though lol welp. Is there any way to cancel a format?

Getting "Your device is corrupt" message and I want to start completely fresh.

Getting "Your device is corrupt" message and I want to start completely fresh.
I had setup a Nexus 6 a couple years back for someone who was mostly blind and I used tasker to let them do most things they needed by voice only.
It was working fine until a couple days ago when somehow the device upgraded from Lollipop to Android 7.0. The way I initially unlocked the phone and obtained root, I didn't think it would ever be able to upgrade unless I intervened but it finally happened seemingly on its own.
Anyway, it lost root and many of the tasker commands stopped working because of it so I tried to get it back by:
1) Using fastboot to flashe twrp-3.1.1-0-shamu.img to recovery
2) Booting into recovery and installing SuperSU with TWRP after I made a backup
After that, the phone booted back up normally but still didn't have root access so I restarted again but when I tried to get into recovery I got a "no command" message. I was finally able to get passed that by pressing volume down (I think) and it gave me the standard android factory reset, wipe cache, etc. options. I tried wiping the cache and then after reboot I got this message:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And then it just disappears after a few seconds and the phone will not boot up.
Now though I can still get back into the bootloader menu with Power and Volume Down and even get back to the TWRP recovery where I tried restoring the backup I made before installing SuperSU but the same problem occurs.
I don't know what I've done wrong but I just want to start over. What do I need to do to wipe the phone completely and start over like it was brand new out of the box?

LaTropa64 said:
I had setup a Nexus 6 a couple years back for someone who was mostly blind and I used tasker to let them do most things they needed by voice only.
It was working fine until a couple days ago when somehow the device upgraded from Lollipop to Android 7.0. The way I initially unlocked the phone and obtained root, I didn't think it would ever be able to upgrade unless I intervened but it finally happened seemingly on its own.
Anyway, it lost root and many of the tasker commands stopped working because of it so I tried to get it back by:
1) Using fastboot to flashe twrp-3.1.1-0-shamu.img to recovery
2) Booting into recovery and installing SuperSU with TWRP after I made a backup
After that, the phone booted back up normally but still didn't have root access so I restarted again but when I tried to get into recovery I got a "no command" message. I was finally able to get passed that by pressing volume down (I think) and it gave me the standard android factory reset, wipe cache, etc. options. I tried wiping the cache and then after reboot I got this message:
And then it just disappears after a few seconds and the phone will not boot up.
Now though I can still get back into the bootloader menu with Power and Volume Down and even get back to the TWRP recovery where I tried restoring the backup I made before installing SuperSU but the same problem occurs.
I don't know what I've done wrong but I just want to start over. What do I need to do to wipe the phone completely and start over like it was brand new out of the box?
Click to expand...
Click to collapse
I'm not sure what to tell you, there's a lot of complication between these things but mostly seems like it'd include Re-flashing stock os 7.0 and obtaining root thru Android 7 without flashing any rom
Sent from my Z988 using Tapatalk
---------- Post added at 08:09 AM ---------- Previous post was at 08:08 AM ----------
And by complication I mean the whole concept of just starting over fresh
Sent from my Z988 using Tapatalk
---------- Post added at 08:09 AM ---------- Previous post was at 08:09 AM ----------
Good luck tho
Sent from my Z988 using Tapatalk

LaTropa64 said:
I don't know what I've done wrong but I just want to start over. What do I need to do to wipe the phone completely and start over like it was brand new out of the box?
Click to expand...
Click to collapse
Download a factory image from Google developer site. That site gives instructions to set-up your PC for fastboot (if you need it) and there is a flash all script in the download to handle the flash through fastboot. This thread will give you an overview. Using the flash all script will wipe the entire phone!
You can also fastboot flash each partition manually. If you use the -w flag, it will wipe all user data from the phone.
Be warned, the probability is you'll wipe the internal (user data) and if you want to try to back up first, you should be able to boot into TWRP and use ADB to do an a back up of user data to your PC using:
adb pull /path/to/files /home/[your username]/
E.G.
Windows:
adb pull /sdcard C:\Users\[your username]\Desktop
Linux:
adb pull /sdcard /home/[your username]/
You'll need administrator privileges on the PC to specify the output path.
---Edit---
You might look into the tasker beta to work with the newer nougat releases. I will say, all of my tasker profiles continued to work regardless of OS version with the exception of those relying on secure settings. Those I updated to use auto tools. There are other work around as well.

Follow what @ktmom says to get the device all straightened out firmware wise. As the device totally skipped Android 6 in doing its upgrade there could be undesired leftovers from the original install. Once you've installed the latest stock firmware from Google you can start over with your customizations, but be aware that installing TWRP, rooting the device, or both will cause the "device is corrupt" message you're seeing. That message will remain on every boot until a custom kernel which ignores dm-verity is installed.

In a few months, Galaxy S8 will get Bixby Voice so you could get one of them.
Sent from my Z988 using Tapatalk

Who in the hell would want to use Bixby?

Root SM-M405F (Galaxy M40)

Read all the Instructions very carefully, as missing even a single steps cause bootloop.
1. Unlocking Bootloader
Allow bootloader unlocking in Developer options → OEM unlocking
Power off your device. Press Volume Up + Volume Down and plug in your device to a PC to boot into download mode
Long press volume up to unlock the bootloader. This will wipe your data and automatically reboot.
Just when you think the bootloader is unlocked, surprise surprise, it is actually not! Samsung introduced VaultKeeper in the system, meaning the bootloader will reject any unofficial partitions before VaultKeeper explicitly allows it.
Go through the initial setup. Skip through all the steps since data will be wiped again later when we are installing Magisk. Connect the device to internet in the setup!
Enable developer options, and confirm that the OEM unlocking option exists and grayed out!
2. Before Installing Magisk
Installing Magisk WILL trip KNOX
Installing Magisk for the first time REQUIRES a full data wipe, backup before continue
You have to have your bootloader unlocked before following the instructions
After installing Magisk, you can directly upgrade Magisk within Magisk Manager without an issue.
3. Flashing Magisk:
Download the firmware for SM-M405F
Unzip the firmware and copy the AP tar file to your device. It is normally named as AP_[device_model_sw_ver].tar.md5
Install the latest Magisk Manager
In Magisk Manager: Install → Install → Select and Patch a File and select the AP tar file.
Magisk Manager will patch the whole firmware file and store the output to [Internal Storage]/Download/magisk_patched.tar
Copy the tar file to your PC and boot your device to download mode.
Flash magisk_patched.tar as AP in ODIN, together with the BL, CP and HOME_CSC files. Never flash only an AP file, as Odin can shrink your /data file-system if you do.
Important: Uncheck “Auto Reboot” in Options!
Magisk is now successfully flashed! But there are still several steps before you can properly use the device.
We now want to boot into the stock recovery to factory reset our device.
Full data wipe is mandatory! Do not skip this step.
Press Power + Volume Down to exit download mode. As soon as the screen turns off, immediately press Power + Volume Up to boot to recovery partition. Just as mentioned in the previous section, since we want to boot into stock recovery, continue pressing the volume up button until you see the stock recovery screen.
In the stock recovery menu, use volume buttons to navigate through menus, and the power button to select the option. Select Wipe data/factory reset to wipe the data of the device.
This time, we can finally boot to the system with Magisk. Select Reboot system now, and immediately press Power + Volume Up. After seeing the bootloader warning screen, release all buttons so it can boot to the system.
The device will automatically reboot for the first time it boots. This is completely normal and done by design.
After the device is booted up, do the usual initial setup. The following steps will need internet connection.
You shall see Magisk Manager in your app drawer; if not, manually install the APK you downloaded and continue to the next step. The app would be a stub and it shall automatically upgrade to the full Magisk Manager when you open it.
Magisk Manager will ask to do additional setups. Let it do its job and the app will automatically reboot your device.
Enjoy Root

Successfully rooted Galaxy M40
Thanks for the post. I have successfully rooted Galaxy M40 using magisk. Just one thing to add to the above post-- while copying patched ap from phone to pc use adb otherwise the flashing patched AP fails.

Ayan Chakraborty said:
Thanks for the post. I have successfully rooted Galaxy M40 using magisk. Just one thing to add to the above post-- while copying patched ap from phone to pc use adb otherwise the flashing patched AP fails.
Click to expand...
Click to collapse
I did not use Adb, it went smoothly for me. :good:

Enable 3CA for Rooted M40
Galaxy M40 uses LTE 2CA but the chipset supports 3CA. Can we enable it for Rooted M40?

Be careful doing this, since the latest Samsung firmware update in August it doesn't work anymore. You can root at first, but then every time you reboot the phone unroots... If you persist and do it again Samsung lock the phone for "security reasons" and you can't even reach the bootloader or recovery screens using the up / down buttons... Meaning you can't go back to stock firmware without taking your phone back to the store or sending for service, but of course you now no longer have warranty.

awsmanks said:
I did not use Adb, it went smoothly for me. :good:
Click to expand...
Click to collapse
This method will work for samsung a60 with his own firmware? Its the china better version of m40, i think i'll try this method

Rooted Successfully.
I had to flash twice since it did not boot into the stock recovery first time and messed with root I presume. second time it went perfectly and manually installed magisk manager. later magisk manager did some setups and rebooted my system.
Thanks Dev.
waiting for TWRP

rajeshca911 said:
Rooted Successfully.
I had to flash twice since it did not boot into the stock recovery first time and messed with root I presume. second time it went perfectly and manually installed magisk manager. later magisk manager did some setups and rebooted my system.
Thanks Dev.
waiting for TWRP
Click to expand...
Click to collapse
So this the new update it works?

Scorpio02 said:
This method will work for samsung a60 with his own firmware? Its the china better version of m40, i think i'll try this method
Click to expand...
Click to collapse
The A60 and the M40 are identical, it's not the "china better version" lol, it's just 90 USD more expensive because Chinese people have more money. It's literally identical down to the microchips inside.

Scorpio02 said:
So this the new update it works?
Click to expand...
Click to collapse
I think that I flashed on latest firmware AP_M405FDDU1ASF2_CL16060793_QB24248847_REV00_user_low_ship_MULTI_CERT_meta_RKEY_OS9.tar
Android Pie
Magisk 19.3
Magisk Manager 7.3.2
everything works perfectly except that annoying message on the boot screen
Here are my screenshots
View attachment 4807915
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
View attachment 4807917

I've uploaded the latest firmware file to Mega for anyone who doesn't want to wait 10 years for it to download from the snail-speed Samsung Firmware website:
https://mega.nz/#!T1sBka7B!iP8Ub8xbmO4ppa1CJg5vh4dWk_Vh-KjnPM6M6VjiqCc
Feel free to check the MD5 hashes, zero changes.

Theseusperse said:
Be careful doing this, since the latest Samsung firmware update in August it doesn't work anymore. You can root at first, but then every time you reboot the phone unroots... If you persist and do it again Samsung lock the phone for "security reasons" and you can't even reach the bootloader or recovery screens using the up / down buttons... Meaning you can't go back to stock firmware without taking your phone back to the store or sending for service, but of course you now no longer have warranty.
Click to expand...
Click to collapse
I rooted my phone yesterday, today I rebooted my phone. and pfff it is gone.
this rooting procedure is not persistent
Waiting for a stable root method
now I am neither on ofw nor on rooted firmware

rajeshca911 said:
I rooted my phone yesterday, today I rebooted my phone. and pfff it is gone.
this rooting procedure is not persistent
Waiting for a stable root method
now I am neither on ofw nor on rooted firmware
Click to expand...
Click to collapse
Yeah that was the same issue I was having, I'm using the Indian version of the firmware so I wonder if it just affects Indian models.
I did a lot of research and there's actually not just 5 international models but 7, some with a /DS on the end which appear to use different firmwares, and I wonder if that is the cause of the issue.
Anyway I found a temporary fix. Reset everything back to stock firmware, do the rooting as the guide shows on page 1, then ALWAYS reboot using root, either by installing or upgrading a new Magisk module, or updating your AdAway blacklist, or by using ADB Shell #Su... For some reason when you reboot like this it doesn't unroot the phone and everything stays fine. Also make sure you never ever press the "Okay continue" button that appears when the phone first starts and tells you the bootloader is unlocked, just wait a while and allow it to continue automatically.

Theseusperse said:
Yeah that was the same issue I was having, I'm using the Indian version of the firmware so I wonder if it just affects Indian models.
I did a lot of research and there's actually not just 5 international models but 7, some with a /DS on the end which appear to use different firmwares, and I wonder if that is the cause of the issue.
Anyway I found a temporary fix. Reset everything back to stock firmware, do the rooting as the guide shows on page 1, then ALWAYS reboot using root, either by installing or upgrading a new Magisk module, or updating your AdAway blacklist, or by using ADB Shell #Su... For some reason when you reboot like this it doesn't unroot the phone and everything stays fine. Also make sure you never ever press the "Okay continue" button that appears when the phone first starts and tells you the bootloader is unlocked, just wait a while and allow it to continue automatically.
Click to expand...
Click to collapse
Thanks Theseusperse, I will follow that. and can u suggest me easy way to port twrp? I tried carlive image kitchen however when i flashed it not only reboots into stock rom but also shrinked my internal space to 16 GB. To Revert this effect I had to flash stock rom again using Odin ( only odin other tools failed) . Please let me know if there is any safe porting Recovery

rajeshca911 said:
Thanks Theseusperse, I will follow that. and can u suggest me easy way to port twrp? I tried carlive image kitchen however when i flashed it not only reboots into stock rom but also shrinked my internal space to 16 GB. To Revert this effect I had to flash stock rom again using Odin ( only odin other tools failed) . Please let me know if there is any safe porting Recovery
Click to expand...
Click to collapse
There won't be any port of TWRP for a long time, Samsung has to release the source code for the phone first. Based on the Galaxy A series that was released in May this year, they just got their source code last week and the TWRP porting community literally kicked off in the past few days, so we'll probably have to wait some months. I'd estimate November sometime.
I'm excited for when it finally does happen though, I absolutely hate the stock Samsung software and want pure Google, even if it means a GSI rom.
Our phone is actually 100% identical to the Samsung Galaxy A60, so it's possible any TWRP ports made for that device would work, but so far the ones I've tried have all failed and resulted in the same effects you experienced.

SIZE=1]---------- Post added at 04:02 AM ---------- Previous post was at 03:59 AM ----------[/SIZE]
[/COLOR]
Theseusperse said:
There won't be any port of TWRP for a long time, Samsung has to release the source code for the phone first. Based on the Galaxy A series that was released in May this year, they just got their source code last week and the TWRP porting community literally kicked off in the past few days, so we'll probably have to wait some months. I'd estimate November sometime.
I'm excited for when it finally does happen though, I absolutely hate the stock Samsung software and want pure Google, even if it means a GSI rom.
Our phone is actually 100% identical to the Samsung Galaxy A60, so it's possible any TWRP ports made for that device would work, but so far the ones I've tried have all failed and resulted in the same effects you experienced.
Click to expand...
Click to collapse
Im excited to hear that A60 recovery might work on M40 any ways me either hate to be on stock rom. I got habituated to the root and custom roms. Hope A60 source works for M40 . Please do update me if anything that kind of miracle happens. Thanks in advance Brother

rajeshca911 said:
I rooted my phone yesterday, today I rebooted my phone. and pfff it is gone.
this rooting procedure is not persistent
Waiting for a stable root method
now I am neither on ofw nor on rooted firmware
Click to expand...
Click to collapse
To prevent loosing magisk root after reboot. NEVER REBOOT NORMALLY but Reboot it via Magisk or Fully Power Off then Turn Power On.

redymedan said:
To prevent loosing magisk root after reboot. NEVER REBOOT NORMALLY but Reboot it via Magisk or Fully Power Off then Turn Power On.
Click to expand...
Click to collapse
Can i reflash again 0n same rom without loosing data ??
Sent from my SM-M405F using Tapatalk

rajeshca911 said:
Can i reflash again 0n same rom without loosing data ??
Sent from my SM-M405F using Tapatalk
Click to expand...
Click to collapse
No, never ever do this, it will shrink your data partition and there's no way to ever fix it, even with a total system restore or using manufacturer tools.

Theseusperse said:
No, never ever do this, it will shrink your data partition and there's no way to ever fix it, even with a total system restore or using manufacturer tools.
Click to expand...
Click to collapse
Too late, I already did that and it shrieked my devices storage to 16Gb first time and 32 gb on second flash. But It got fixed with Odin repartition. Dont worry It is fixable
Sent from my SM-M405F using Tapatalk

[ROM][sGSI] OxygenOS v9.5.7 OP7 build for Realme 3 Pro

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
​Device side changes:
1. Fingerprint scanner is fixed, Huge thanks to @karthick111
2. About screen is modded for our device
3. Updated Power Profile & Battery mAH is now correctly reported
4. Fixed VOOC detection
5. Enabled Doze (only when new notications arrive)
6. Enabled DT2W by default, all off screen gestures are working
7. Pickup/Raise to wake phone is enabled
8. Fixed USB error when connected to pc/laptop as File Transfer
9. Fixed Google FaceUnlock (Native OP FaceUnlock shouldn't be enabled)
10. Dark mode is enabled by default
11. Many changes done to system under the hood for smoother performance
Prerequisites:
1. sGSI System Image
2. Flashable Patched Recovery & Boot ZIPhttps://sourceforge.net/projects/rmx1851/files/OxygenOS_sGSI_RMX1851/rec_boot.zip/downloadhttps://sourceforge.net/projects/rmx1851/files/OxygenOS_sGSI_RMX1851/rec_boot.zip/download
Process of flashing:
1. First take backup of Internal Storage then format Data in twrp if you're flashing oos for the first time otherwise only wipe data
2. Extract the downloaded OxygenOS_OP7_sGSI_RMX1851.7z, flash it to System_Image.
3. Flash rec_boot.zip
4. REBOOT TO RECOVERY (this boots into system)
Known Issues:
1. Reboot issue. Device won't reboot or power off through system. You need to do it manually, how? Hold all the three buttons, when device vibrates leave all buttons except volume down. This takes you to fastboot.
2. SDCard can't be accessed by few apps.
3. Off Screen FP
Credits:
@karthick111 for fixing fingerprint
@Erfan Abdi for his GSI tool

Reserved

Stuck at the boot animation
After flashing the device is stuck at the oneplus bootanimation.What am i supposed to do now?
Update:
Thanks for the support ajith it works like a charm now

@4j17h
Its pleasant to see another Rom from your Garden. Would love to try this Rom but preferably I will wait for the bugs to be fixed.
In case, I installed... will come up with brief review.
Thanks a lot for your development work.

Hey OP,
Since you mentioned almost every issue is fixed in this room, is it good for daily driver and also does camera works perfectly?
I assume oxygen os features like fnatic mode won't work right?
And can I also unlock my bootloader if I'm on a19

Intex12345 said:
@4j17h
Its pleasant to see another Rom from your Garden. Would love to try this Rom but preferably I will wait for the bugs to be fixed.
In case, I installed... will come up with brief review.
Thanks a lot for your development work.
Click to expand...
Click to collapse
Did you install it? Is is stable for daily driver and good?
---------- Post added at 01:17 AM ---------- Previous post was at 01:17 AM ----------
pranavdas said:
After flashing the device is stuck at the oneplus bootanimation.What am i supposed to do now?
Update:
Thanks for the support ajith it works like a charm now
Click to expand...
Click to collapse
Please share in brief review bro, if it's worth it I will unlock bootloader

Realme X
Will there be one for Realme X.I really want to try Oxygen os.

Akshai Raj said:
Will there be one for Realme X.I really want to try Oxygen os.
Click to expand...
Click to collapse
This is a Realme 3 Pro thread. You can ask such questions in the respective forums for Realme X.

-- deleted---

ahmedmoselhi said:
reboot fix posted by @4j17h in telegram group in attachments
Click to expand...
Click to collapse
can you pls delete it, this is not confirmed working yet. Flashing it causes issues.

The homescreen is not showing up. It keeps on showing "Phone is Starting" but the status bar is accessible. Please help. Also twrp asks password for decrypt.

vinacchio said:
The homescreen is not showing up. It keeps on showing "Phone is Starting" but the status bar is accessible. Please help. Also twrp asks password for decrypt.
Click to expand...
Click to collapse
yes that's how decryption works in device, when it asks for password enter your lockscreen password to enter into twrp. Then format data (not wipe) & reboo to recovery (which boots into system)

When I go to fastboot and select recovery mode it's start the phone instead to twrp, and there is a message saying something wrong with my internal when I startup the phone, can you help me with this ?

lsweb said:
When I go to fastboot and select recovery mode it's start the phone instead to twrp, and there is a message saying something wrong with my internal when I startup the phone, can you help me with this ?
Click to expand...
Click to collapse
Ignore the error msg when you reboot the device. To boot into twrp you need to keep hold of volume up button while device is rebooting.

When tried to reboot, phone switched off and after that not turning on. I have tried to go to fastboot mode recovery mode but nothing happening even charging is also not showing

[email protected] said:
When tried to reboot, phone switched off and after that not turning on. I have tried to go to fastboot mode recovery mode but nothing happening even charging is also not showing
Click to expand...
Click to collapse
Yeah looks like device went to EDL mode, hold all the buttons for few seconds. Device gets to normal state again.

So I accidentally deleted the stock OnePlus Launcher and now my gestures aren't working for recent apps. Is there a way to fix it by installing the launcher's apk? If so, which version should I install?

I can't update magisk because it is not booting into recovery. Any ways to do that ....

madaniitk said:
I can't update magisk because it is not booting into recovery. Any ways to do that ....
Click to expand...
Click to collapse
After pressing reboot to recovery keep holding the power up button so it'll reboot to recovery and not the system.

Please provide always on display feature and there is no camera in ROM.