Related
Hi there,
I think we should make a simple thread to sum up everything we know about root, since the main talking thread is long, here are the main informations:
Xperia Z5:
- No locked bootloader root yet
- AndroPlusKernel: http://forum.xda-developers.com/xperia-z5/development/kernel-andropluskernel-v1-t3246100
- TWRP here http://forum.xda-developers.com/xperia-z5/development/twrp-2-8-7-0-z5-rootable-kernel-t3240032
- CWM booting but not usable: http://forum.xda-developers.com/xperia-z5/development/recovery-clockworkmod-recovery-sony-t3249782
- Unlocked BL dirty rooting available and working as intended: http://forum.xda-developers.com/xperia-z5/development/dirty-root-solution-unlocked-bl-t3233274
- Dumped original firmware: http://forum.xda-developers.com/xperia-z5/general/ftf-files-sony-xperia-z5z5-dual-t3214397
- Xposed works but you need to let it bootloop a few times
Xperia Z5 Compact:
- No locked bootloader root yet
- Zombie Kernel testing release here: http://forum.xda-developers.com/z5-compact/orig-development/kernel-zombie-t3224735
- Unlock bootloader root available (http://forum.xda-developers.com/z5-compact/development/dirty-root-solution-unlocked-bl-t3230524)
- Prerooted firmware available for unlocked BL: http://forum.xda-developers.com/z5-...-rooted-32-0-5-32-firmware-one-click-t3231520
- Xposed doesn't work with prerooted firmware
Currently we need to:
- Compile Zombie Kernel for Z5
- Improve TWRP support
- Create prerooted-firmware
- Most obviously and most hardly, find exploit for Locked BL root
Ok I'm not an Xperia pro, just got my first one few days ago, but still a android and linux geek, so if there is mistakes in my post, or update I haven't seen, notify me
Knux14 said:
- Maybe dump the original firmware ?
Click to expand...
Click to collapse
If I'm not mistaken, I think it already has: http://forum.xda-developers.com/xperia-z5/general/ftf-files-sony-xperia-z5z5-dual-t3214397
Need root for Z5, thx for efforts.
Uclydde said:
If I'm not mistaken, I think it already has: http://forum.xda-developers.com/xperia-z5/general/ftf-files-sony-xperia-z5z5-dual-t3214397
Click to expand...
Click to collapse
Updated
Test kernel for Z5:
https://mega.nz/#!15oSGLiA!N-lOlfn8RS9_gN_GcVJrFzXg21nzL1xDdt1xKujl9is
This is stock Z5 kernel modified to disable Sony RIC, dm verity, etc.
It should work together with the Z5C rooting solution:
http://forum.xda-developers.com/z5-compact/development/dirty-root-solution-unlocked-bl-t3230524
Please report back.
nilezon said:
Test kernel for Z5:
https://mega.nz/#!15oSGLiA!N-lOlfn8RS9_gN_GcVJrFzXg21nzL1xDdt1xKujl9is
This is stock Z5 kernel modified to disable Sony RIC, dm verity, etc.
It should work together with the Z5C rooting solution:
http://forum.xda-developers.com/z5-compact/development/dirty-root-solution-unlocked-bl-t3230524
Please report back.
Click to expand...
Click to collapse
You are the man, you saved me
my phone works now with root access
nilezon said:
Test kernel for Z5:
https://mega.nz/#!15oSGLiA!N-lOlfn8RS9_gN_GcVJrFzXg21nzL1xDdt1xKujl9is
This is stock Z5 kernel modified to disable Sony RIC, dm verity, etc.
It should work together with the Z5C rooting solution:
http://forum.xda-developers.com/z5-compact/development/dirty-root-solution-unlocked-bl-t3230524
Please report back.
Click to expand...
Click to collapse
Huge thanks, But I can't get it working...
I open BL, I fastboot flashed the kernel, then I fastboot booted on the recovery (Which doesn't show a black screen as expected but a real non-fully-working twrp for me) and I tried to install Supersu but I write an error then...
EDIT: Kinda glitchy to do, but works.
If anyone has Xposed working, please make a tutorial
Okay so this is my first Xperia device and my second android device (used to have a Nexus 5 so rooting was simple). Can anyone ELI5 the root situation?
I understand that the TA partition contains DRM keys to make X-Reality etc work and that unlocking the bootloader will wipe this TA partition and the features will stop working. My main confusion comes from - if other lollipop devices have rooting methods for locked bootloaders, why don't these methods work on the Z5? Sorry if this is extremely obvious and I'm an idiot.
Most android devices have either already unlocked BL or you have to. For example, Nexus 5 needed to unlock the BL, as well as the OnePlus One, but those devices don't contain DRM so you don't loose anything when unlocking
nilezon said:
Test kernel for Z5:
https://mega.nz/#!15oSGLiA!N-lOlfn8RS9_gN_GcVJrFzXg21nzL1xDdt1xKujl9is
This is stock Z5 kernel modified to disable Sony RIC, dm verity, etc.
It should work together with the Z5C rooting solution:
http://forum.xda-developers.com/z5-compact/development/dirty-root-solution-unlocked-bl-t3230524
Please report back.
Click to expand...
Click to collapse
Worked in second attempt. First time reboot into recovery. New fastboot boot booted into black screen.
In following sequence it was necessary to add destination file name,
D:\DOWNLOADS\Sony\Xperia\Z5\Fastboot>adb push SuperSU-v2.51.zip /data/media/0/
failed to copy 'SuperSU-v2.51.zip' to '/data/media/0/': Is a directory
D:\DOWNLOADS\Sony\Xperia\Z5\Fastboot>adb push SuperSU-v2.51.zip /data/media/0/SuperSU-v2.51.zip
9055 KB/s (3989636 bytes in 0.430s)
harfot said:
Worked in second attempt. First time reboot into recovery. New fastboot boot booted into black screen.
In following sequence it was necessary to add destination file name,
D:\DOWNLOADS\Sony\Xperia\Z5\Fastboot>adb push SuperSU-v2.51.zip /data/media/0/
failed to copy 'SuperSU-v2.51.zip' to '/data/media/0/': Is a directory
D:\DOWNLOADS\Sony\Xperia\Z5\Fastboot>adb push SuperSU-v2.51.zip /data/media/0/SuperSU-v2.51.zip
9055 KB/s (3989636 bytes in 0.430s)
Click to expand...
Click to collapse
I did not had to :/
You guys work fast!
Unsure whether to root myself yet,
Kind of wouldn't mind being able to connect a ps3 pad instead of
Ps4 using the sixaxis app
I'm still confused here. I don't see clear instructions for root process, probably because this is my first Xperia device. Neither do I know if using this modded stock kernel and doing this adb thing few posts back will break the DRM thingy and camera features or not.
Falenone said:
I'm still confused here. I don't see clear instructions for root process, probably because this is my first Xperia device. Neither do I know if using this modded stock kernel and doing this adb thing few posts back will break the DRM thingy and camera features or not.
Click to expand...
Click to collapse
There is nothing clear enough for beginner yet. Sooner or later there will be a TWRP fully working and it will be easy.
Try the dirty method, but don't do things that you are not sure that will work. Ask us if needed
I don't want to lose features because of unlocked bootloader. I guess I'm going to survive without root til there's TWRP and pretty much flash n go root
You will maybe never be able to root without loosing feature. Xperia devices work like this for ages..
The only way you could would be that we find a flaw in Android, which could either arrive soon, or never...
Knux14 said:
You will maybe never be able to root without loosing feature. Xperia devices work like this for ages..
The only way you could would be that we find a flaw in Android, which could either arrive soon, or never...
Click to expand...
Click to collapse
Ages means..? I know that the Z1 is not so fresh anymore but we were able to root 4.2/4.4.4/5.1 without losing anything with locked BL. (I know nothing except following tutorials)
Sent from my E6653
Yes because there were security holes in android. For now we havent found anything yet in this version
harfot said:
Worked in second attempt. First time reboot into recovery. New fastboot boot booted into black screen.
In following sequence it was necessary to add destination file name,
D:\DOWNLOADS\Sony\Xperia\Z5\Fastboot>adb push SuperSU-v2.51.zip /data/media/0/
failed to copy 'SuperSU-v2.51.zip' to '/data/media/0/': Is a directory
D:\DOWNLOADS\Sony\Xperia\Z5\Fastboot>adb push SuperSU-v2.51.zip /data/media/0/SuperSU-v2.51.zip
9055 KB/s (3989636 bytes in 0.430s)
Click to expand...
Click to collapse
I did boot into TWRP (it was like tablet mode) mounted all partitions to be sure, flashed SuperSU from external sd. It is working. Thank you all
ChrissehB said:
Okay so this is my first Xperia device and my second android device (used to have a Nexus 5 so rooting was simple). Can anyone ELI5 the root situation?
I understand that the TA partition contains DRM keys to make X-Reality etc work and that unlocking the bootloader will wipe this TA partition and the features will stop working. My main confusion comes from - if other lollipop devices have rooting methods for locked bootloaders, why don't these methods work on the Z5? Sorry if this is extremely obvious and I'm an idiot.
Click to expand...
Click to collapse
Google "Verified Boot Android" .. there is almost 100% probability that locked bootloader root will never be achieved, because of this security feature. Verified Boot was introduced in KitKat, but almost nobody used it in so strict mode implementation... Until now, no single firmware using Verified Boot was ever rooted without either custom kernel (must unlock bootloader) or leaked engineering bootloader (try ask Sony engineers for it).
Hello, I own Xiaomi Mi5 Prime, is it possible to make it capture images in .RAW format, if yes, whats the way? Thanks!
pi4a7a said:
Hello, I own Xiaomi Mi5 Prime, is it possible to make it capture images in .RAW format, if yes, whats the way? Thanks!
Click to expand...
Click to collapse
Try some 3rd part app like Footej Camera (should be free to check if RAW is available) or other camera apps like (manual camera, proshot etc.) to see if it has RAW support.
RAW option is available in Footej Camera in My Mi5 prime with RR rom. The last MIUI version (Xiaomi.eu version) that I checked also passed the manual camera compatibility test which should mean that rom will support RAW too and have camera2 api enabled. Newer Global rom probably have camera2 api enabled too.
LineageOS also have camera2 api and RAW support (most probably).
JRC1995 said:
Try some 3rd part app like Footej Camera (should be free to check if RAW is available) or other camera apps like (manual camera, proshot etc.) to see if it has RAW support.
RAW option is available in Footej Camera in My Mi5 prime with RR rom. The last MIUI version (Xiaomi.eu version) that I checked also passed the manual camera compatibility test which should mean that rom will support RAW too and have camera2 api enabled. Newer Global rom probably have camera2 api enabled too.
LineageOS also have camera2 api and RAW support (most probably).
Click to expand...
Click to collapse
Im using MIUI Global 7.2.8.0.0(MAACNBD) | Stable ROM
My Mi5P doesn't pass the Manual camera compatibility test... aaannnd there is no option in Footej Camera for raw just the quality of the JPEG.
Which MIUI rom should I flash for RAW support?
Also I want to ask about the updater app, looks like it can't connect with network its version 3.0.0 is there update or something ?
Thanks.
pi4a7a said:
Im using MIUI Global 7.2.8.0.0(MAACNBD) | Stable ROM
My Mi5P doesn't pass the Manual camera compatibility test... aaannnd there is no option in Footej Camera for raw just the quality of the JPEG.
Which MIUI rom should I flash for RAW support?
Also I want to ask about the updater app, looks like it can't connect with network its version 3.0.0 is there update or something ?
Thanks.
Click to expand...
Click to collapse
Firstly you seem to be having a very old global rom. So you may need to update it.
If you click the the dots in footej camera you will get options like grid, white balance, single photo etc in the viewfinder.
If you click the single photo option you will get options for HDR, RAW, Burst mode.....
But I doubt you will get RAW support without the camera 2 api enabled (if it is enabled footej camera should also 'show' shutter speed and ISO in viewfinder by default.
But other than the camera thing, I have another major concern for your rom.
I am not sure, but I suspect that you have a 'fake ROM' or 'vendor ROM'.
"h t t p: //xiaomit ips.com/guide/how-to-spot-fake-miui-rom-on-your-phone/" (can't post links yet. Remove quotes and spaces to use the link)
You have more than 4 digits for the version apparently.
It is advisable to get rid of the fake rom as soon as possible....generally they are full of bugs..and may even have adwares and malwares with worse performace. And yes having a fake rom is probably the reason why you have no OTA yet....(not a network problem but a rom problem). Do your research and if you can confirm you are having a fake rom getting rid of it should be your first priority.
I was lucky to have a official global rom from the start, so I can't advise you on how to get rid of it from my own experience.
However I had this link bookmarked as I was expecting I will recieve a fake rom:
"h t t p : //en. miui .com/thread-309122-1-1.html" (can't post links yet. Remove quotes and spaces to use the link)
It seems to list some possible ways to remove the fake rom from least risky to most risky method. Most risky method should still be fine if you are flashing the proper rom, I guess.
EDL is often the recommended method for totally getting rid of it...but after a certain version Xiaomi blocked EDL or something.
Assuming your bootloader is locked, you can request for Mi unlock by explaining your situation and then fastboot flash your rom with the latest global beta (or stable) or you may be able to put twrp and flash Xiaomi.eu version of the rom (which is a bloatfree translated chinese version of miui....which is quite stable..)
JRC1995 said:
Firstly you seem to be having a very old global rom. So you may need to update it.
If you click the the dots in footej camera you will get options like grid, white balance, single photo etc in the viewfinder.
If you click the single photo option you will get options for HDR, RAW, Burst mode.....
But I doubt you will get RAW support without the camera 2 api enabled (if it is enabled footej camera should also 'show' shutter speed and ISO in viewfinder by default.
But other than the camera thing, I have another major concern for your rom.
I am not sure, but I suspect that you have a 'fake ROM' or 'vendor ROM'.
"h t t p: //xiaomit ips.com/guide/how-to-spot-fake-miui-rom-on-your-phone/" (can't post links yet. Remove quotes and spaces to use the link)
You have more than 4 digits for the version apparently.
It is advisable to get rid of the fake rom as soon as possible....generally they are full of bugs..and may even have adwares and malwares with worse performace. And yes having a fake rom is probably the reason why you have no OTA yet....(not a network problem but a rom problem). Do your research and if you can confirm you are having a fake rom getting rid of it should be your first priority.
I was lucky to have a official global rom from the start, so I can't advise you on how to get rid of it from my own experience.
However I had this link bookmarked as I was expecting I will recieve a fake rom:
"h t t p : //en. miui .com/thread-309122-1-1.html" (can't post links yet. Remove quotes and spaces to use the link)
It seems to list some possible ways to remove the fake rom from least risky to most risky method. Most risky method should still be fine if you are flashing the proper rom, I guess.
EDL is often the recommended method for totally getting rid of it...but after a certain version Xiaomi blocked EDL or something.
Assuming your bootloader is locked, you can request for Mi unlock by explaining your situation and then fastboot flash your rom with the latest global beta (or stable) or you may be able to put twrp and flash Xiaomi.eu version of the rom (which is a bloatfree translated chinese version of miui....which is quite stable..)
Click to expand...
Click to collapse
Whoa.. I didn't know that.. looks like mine is fake....
They say "Please note that the new MIUI versions (7.3.X.X and above) today already blocking this method (EDL), but if you have the old version you can use it."
Mine is 7.2 so I guess it's not locked right ?
Can you provide me the best step by step tutorial how to completely remove that fake stuff and install a brand new global stable MIUI rom ?
EDL
Thanks
pi4a7a said:
Whoa.. I didn't know that.. looks like mine is fake....
Can you provide me a step by step tutorial how to completely remove that fake stuff and install a brand new global stable MIUI rom ?
Thanks
Click to expand...
Click to collapse
Follow the 2nd link : "http://en.miui.com/thread-309122-1-1.html"
They have done a good job arranging the possible options along with links to other threads and tutorials necessary for this process.
Sorry, I am not too experienced myself regarding removal of a fake rom. I can help you with specific things like how to unlock bootloader or stuffs but totally getting rid of fake rom can be a complex process and many options and method may be needed to be tried.
First just try to do the simplest possible thing:
0) Backup all data if you need to. Pics, contacts stuffs....
1) Go to miui forum and download the latest China Dev Recovery rom. (It should have english language as an option but no
gapps). ("http://en.miui.com/download-299.html#435") (you may also try the Global beta\stable roms)
2) Rename the downloaded rom to "update.zip" and put it in your phone.
3) Open updater app. Go to menu (three dots or something...) ->choose update package -> then choose the update.zip.
4) The app should try to verify the package and update to it.
5) If update is successfully done check about and see if the version number looks real.
If you happen to have successful then you have removed the fake rom. At this stage you may already have RAW support and more. But if you used the China Dev Rom, you may want to use the Global rom or custom roms for which you have to unlock bootloader. If you have somehow successfully updated to the official global beta\stable rom and don't want to root or try custom rom then no need to do anything.
Note you may first try the above steps using the latest global dev\stable rom and then if it fails, next try to us china dev\stable rom. I think there is a higher chance for china dev\stable rom to work successfully because fake roms are usually based on the china rom.
To unlock bootloader.
1) Make sure you have an MI account at miui forum...and also you must sign in with the same account in your phone. Your account and device should be connected. ALso make sure your MI\MIUI account has proper details like Name, Phone Number etc.
(Also it's better if you keep your name free of spaces).
2) Unlock developer mode. Search google on how to unlock developer settings in miui if you need to.
3) Go to developer settings (probably it will appear inside additional settings)> enable usb debugging and other usb related settings)
4) Enable "allow OEM bootloader unlock" (may not be exactly written like that, currently not in miui so I can't mention the option in exact terms) if the option is there.
5) I think in developer settings there was an option to check lock status of phone....and inside the option there is a button to associate the phone with mi account..do it. (may not be necessary, but just to be safe).
6) Then apply for unlock permission here: http://en.miui.com/unlock/
Note: Your name should be without spaces while filling up.
If you encounter warnings in chinese , use google translate or something. I was warned in chinese about my image verfiication
captcha error.
There you have to explain why you need to unlock bootloader. Clearly explain your need regarding why (it may be because you are still stuck in fake rom and you want to remove it or if you are already in official china rom you can explain that you want to shift to global rom).
7) Wait for the msg. They (Xiaomi) should message to your phone (the no. which is registered to your mi account) regarding if they have accepted your request and granted you unlock permission. After that they will provide the link to download the unlock tool and a code.
8) Connect your phone to computer after entering fastboot mode (power off your phone then hold volumn down+power button until you see the fastboot screen). Then just use the mi unlock tool that you will recieve and follow the instructions to unlock the phone. (for more details you may google on how to use mi unlock tool to unlock bootloader or something).
Once you have unlocked bootloader:
You can have several options. You may shift to global dev rom (download the fastboot rom for your device and use the mi flashing tool. "http://en.miui.com/a-234.html". Google for more details)
NOTE: Be careful following this steps. I won't be responsible if your device is bricked. I may have overlooked certain things so consider my instructions merely as a summary. Do check the links for details. Also even if the miui thread about unlocking bootloader suggest one to use china dev rom for unlocking, I have unlocked my bootloader from global beta rom and global stable rom may work too.
You may install twrp and then flash Xiaomi.eu (China versions of MIUI made bloatfree with more languages and necessary gapps like google play store and services) or you can try custom roms like Resurrection Remix, Lineage OS etc. All of them should have camera 2 api support, at least.
---------- Post added at 06:08 PM ---------- Previous post was at 06:05 PM ----------
pi4a7a said:
Whoa.. I didn't know that.. looks like mine is fake....
They say "Please note that the new MIUI versions (7.3.X.X and above) today already blocking this method (EDL), but if you have the old version you can use it."
Mine is 7.2 so I guess it's not locked right ?
Can you provide me the best step by step tutorial how to completely remove that fake stuff and install a brand new global stable MIUI rom ?
EDL
Thanks
Click to expand...
Click to collapse
Apparently yes, you might be able to attempt EDL. However, I have no experience in that regards. You have to google it.
JRC1995 said:
Follow the 2nd link : "http://en.miui.com/thread-309122-1-1.html"
They have done a good job arranging the possible options along with links to other threads and tutorials necessary for this process.
Sorry, I am not too experienced myself regarding removal of a fake rom. I can help you with specific things like how to unlock bootloader or stuffs but totally getting rid of fake rom can be a complex process and many options and method may be needed to be tried.
First just try to do the simplest possible thing:
0) Backup all data if you need to. Pics, contacts stuffs....
1) Go to miui forum and download the latest China Dev Recovery rom. (It should have english language as an option but no
gapps). ("http://en.miui.com/download-299.html#435") (you may also try the Global beta\stable roms)
2) Rename the downloaded rom to "update.zip" and put it in your phone.
3) Open updater app. Go to menu (three dots or something...) ->choose update package -> then choose the update.zip.
4) The app should try to verify the package and update to it.
5) If update is successfully done check about and see if the version number looks real.
If you happen to have successful then you have removed the fake rom. At this stage you may already have RAW support and more. But if you used the China Dev Rom, you may want to use the Global rom or custom roms for which you have to unlock bootloader. If you have somehow successfully updated to the official global beta\stable rom and don't want to root or try custom rom then no need to do anything.
Note you may first try the above steps using the latest global dev\stable rom and then if it fails, next try to us china dev\stable rom. I think there is a higher chance for china dev\stable rom to work successfully because fake roms are usually based on the china rom.
To unlock bootloader.
1) Make sure you have an MI account at miui forum...and also you must sign in with the same account in your phone. Your account and device should be connected. ALso make sure your MI\MIUI account has proper details like Name, Phone Number etc.
(Also it's better if you keep your name free of spaces).
2) Unlock developer mode. Search google on how to unlock developer settings in miui if you need to.
3) Go to developer settings (probably it will appear inside additional settings)> enable usb debugging and other usb related settings)
4) Enable "allow OEM bootloader unlock" (may not be exactly written like that, currently not in miui so I can't mention the option in exact terms) if the option is there.
5) I think in developer settings there was an option to check lock status of phone....and inside the option there is a button to associate the phone with mi account..do it. (may not be necessary, but just to be safe).
6) Then apply for unlock permission here: http://en.miui.com/unlock/
Note: Your name should be without spaces while filling up.
If you encounter warnings in chinese , use google translate or something. I was warned in chinese about my image verfiication
captcha error.
There you have to explain why you need to unlock bootloader. Clearly explain your need regarding why (it may be because you are still stuck in fake rom and you want to remove it or if you are already in official china rom you can explain that you want to shift to global rom).
7) Wait for the msg. They (Xiaomi) should message to your phone (the no. which is registered to your mi account) regarding if they have accepted your request and granted you unlock permission. After that they will provide the link to download the unlock tool and a code.
8) Connect your phone to computer after entering fastboot mode (power off your phone then hold volumn down+power button until you see the fastboot screen). Then just use the mi unlock tool that you will recieve and follow the instructions to unlock the phone. (for more details you may google on how to use mi unlock tool to unlock bootloader or something).
Once you have unlocked bootloader:
You can have several options. You may shift to global dev rom (download the fastboot rom for your device and use the mi flashing tool. "http://en.miui.com/a-234.html". Google for more details)
NOTE: Be careful following this steps. I won't be responsible if your device is bricked. I may have overlooked certain things so consider my instructions merely as a summary. Do check the links for details. Also even if the miui thread about unlocking bootloader suggest one to use china dev rom for unlocking, I have unlocked my bootloader from global beta rom and global stable rom may work too.
You may install twrp and then flash Xiaomi.eu (China versions of MIUI made bloatfree with more languages and necessary gapps like google play store and services) or you can try custom roms like Resurrection Remix, Lineage OS etc. All of them should have camera 2 api support, at least.
---------- Post added at 06:08 PM ---------- Previous post was at 06:05 PM ----------
Apparently yes, you might be able to attempt EDL. However, I have no experience in that regards. You have to google it.
Click to expand...
Click to collapse
I downloaded Version: V8.1.4.0.MAAMIDI (MIUI8) Global Stable ROM from their site
Did as you said with the Updater app, now all I see is black screen with white circle spinning from about 5 minutes.
In case this method bricks my device what should I do?
Edit: It's booting now..
Edit2: Nothing really happened, just drained my battery with 4%. Everything is still the same...
What exactly did happen?
IIRC the updater app first verify the package and then tries to update.
Was the verification successful?
Did it directly went to the black screen in one go?
Also you may wait for at least 10-20 minutes.
I am not really experienced in this method...I only suggested as it was written in the link.
I don't think it's exactly bricked, the white circle means something is going on......if the updater successfully updated first boot should take some time.
In case of brick., I am not sure what to do with a locked bootloader. You will probably be able to still go to fastboot (holding volume down + power button)....but not exactly sure what after that. May be you will need an engineering cable. May be make a thread here or search google regard what to do when mi 5 bricked with locked bootloader.
Here's a thread where an user bricked his phone while bootloader is locked: http://en.miui.com/thread-474717-1-1.html
Hopefully the solution given in the reply should work: http://en.miui.com/thread-298885-1-1.html
JRC1995 said:
What exactly did happen?
IIRC the updater app first verify the package and then tries to update.
Was the verification successful?
Did it directly went to the black screen in one go?
Also you may wait for at least 10-20 minutes.
I am not really experienced in this method...I only suggested as it was written in the link.
I don't think it's exactly bricked, the white circle means something is going on......if the updater successfully updated first boot should take some time.
Click to expand...
Click to collapse
The Updater verificated the package and then it ask me am I sure, etc. and I agreed then the circle for 10 min. then restarted, and nothing changed...
pi4a7a said:
Edit: It's booting now..
Edit2: Nothing really happened, just drained my battery with 4%. Everything is still the same...
Click to expand...
Click to collapse
So still the vendor rom?
I guess you can try china dev recovery rom next.
Or other methods. May be start by unlocking bootloader (may have to wait 3-10 days to get permission and in the end they may even deny permission for some reason) or you may take the risk and try EDL searching google for guide.
JRC1995 said:
So still the vendor rom?
I guess you can try china dev recovery rom next.
Or other methods. May be start by unlocking bootloader (may have to wait 3-10 days to get permission and in the end they may even deny permission for some reason) or you may take the risk and try EDL searching google for guide.
Click to expand...
Click to collapse
Yup...
I will try the China rom but wasn't this rom without Google Play store and Google Services, how can I get them without unlocking bootloader?
If this fails I will try Option Two... Or I will try it directly
pi4a7a said:
Yup...
I will try the China rom but wasn't this rom without Google Play store and Google Services, how can I get them without unlocking bootloader?
If this fails I will try Option Two... Or I will try it directly
Click to expand...
Click to collapse
Here's a relevant thread (check the whole discussion, and decide how you wanna do it): https://forum.xda-developers.com/mi-5/themes/play-store-mi5-chinese-dev-miui-8-rom-t3578236
Apparently this is usually the suggested way to install gapps in china rom: http://en.miui.com/thread-299317-1-1.html
JRC1995 said:
Here's a relevant thread (check the whole discussion, and decide how you wanna do it): https://forum.xda-developers.com/mi-5/themes/play-store-mi5-chinese-dev-miui-8-rom-t3578236
Apparently this is usually the suggested way to install gapps in china rom: http://en.miui.com/thread-299317-1-1.html
Click to expand...
Click to collapse
Tried China ROM but it couldnt be verified by the Updater...
The Mi tool for PC shows the picture from the first post from this thread http://en.miui.com/thread-309629-1-1.html
I really don't want to unlock the bootloader what should I do..
pi4a7a said:
Tried China ROM but it couldnt be verified by the Updater...
The Mi tool for PC shows the picture from the first post from this thread http://en.miui.com/thread-309629-1-1.html
I really don't want to unlock the bootloader what should I do..
Click to expand...
Click to collapse
For chinese characters you can try google translate phone app to get the gist of what is going on.
Also the thread is quite old, I wonder if the same thing can be done using the English version of MI PC Suite or not. You can try that if the language barrier poses a problem. But I am not sure if there are any reason for which english version shouldn't be used or not.
Even if you unlock bootloader it can be relocked again while flashing the global fastboot rom using mi flash tool if you choose the clean all and lock (or something like that) option.
JRC1995 said:
For chinese characters you can try google translate phone app to get the gist of what is going on.
Also the thread is quite old, I wonder if the same thing can be done using the English version of MI PC Suite or not. You can try that if the language barrier poses a problem. But I am not sure if there are any reason for which english version shouldn't be used or not.
Even if you unlock bootloader it can be relocked again while flashing the global fastboot rom using mi flash tool if you choose the clean all and lock (or something like that) option.
Click to expand...
Click to collapse
I just don't want to go through the unlocking process and requesting and stuff...
I give up...
UPDATE!
I just coudn't sleep all night because of that...
So I followed so many guides and nothing worked, then I discovered this one - http://en.miui.com/thread-293457-1-1.html
Everything went fine, now my phone is going through first boot up so im waiting, Ill update is with more details when I got results.
EDIT: The device got bricked... I went through the procces again and this time the PC Suite (English version) found a newer ROM and installed it, it said procces failed or something like that, the device turned on and it was with the new 8.2 china rom, all information was on the phone, everything is good now, Thanks for all the help
Suggesting all to you guys with Fake Mi rom, remove it!
pi4a7a said:
UPDATE!
I just coudn't sleep all night because of that...
So I followed so many guides and nothing worked, then I discovered this one - http://en.miui.com/thread-293457-1-1.html
Everything went fine, now my phone is going through first boot up so im waiting, Ill update is with more details when I got results.
EDIT: The device got bricked... I went through the procces again and this time the PC Suite (English version) found a newer ROM and installed it, it said procces failed or something like that, the device turned on and it was with the new 8.2 china rom, all information was on the phone, everything is good now, Thanks for all the help
Suggesting all to you guys with Fake Mi rom, remove it!
Click to expand...
Click to collapse
I don't know what happened, but it's all's well when the end is well, I guess.
It sounds like you went through a messy processes, some bugs may appear as a result....if you experience strange graphical bugs or something you might consider full wipe flashing but if there is no major bugs (though there are some bugs that are part of the rom which won't be gone no matter how clean the flash is), things should be alright now if you are on the official version.
I am not sure if camera2 api is enabled by default in 8.2 stable china rom (which is what I am guessing you have now?) but hopefully it is enabled. In miui 8 camera 2 can still be enabled by editing build props even if it is not enabled by default but that will need root which will need bootloader unlocking beforehand......but hopefully latest stable version is enabled by default.
So it seems you are stuck on the china rom...but if you can make gapps work with it, it might not be so bad. I also hear that china roms are more supported and has less bug (3rd party widgets didin't work well in latest global dev but work for me in latest xiaomi.eu based on china rom) and many users said that china rom has better audio output (in headphone or something)...but that may be fixed in latest global rom....well my point is that there can be some pros in staying in china rom too.
JRC1995 said:
I don't know what happened, but it's all's well when the end is well, I guess.
It sounds like you went through a messy processes, some bugs may appear as a result....if you experience strange graphical bugs or something you might consider full wipe flashing but if there is no major bugs (though there are some bugs that are part of the rom which won't be gone no matter how clean the flash is), things should be alright now if you are on the official version.
I am not sure if camera2 api is enabled by default in 8.2 stable china rom (which is what I am guessing you have now?) but hopefully it is enabled. In miui 8 camera 2 can still be enabled by editing build props even if it is not enabled by default but that will need root which will need bootloader unlocking beforehand......but hopefully latest stable version is enabled by default.
So it seems you are stuck on the china rom...but if you can make gapps work with it, it might not be so bad. I also hear that china roms are more supported and has less bug (3rd party widgets didin't work well in latest global dev but work for me in latest xiaomi.eu based on china rom) and many users said that china rom has better audio output (in headphone or something)...but that may be fixed in latest global rom....well my point is that there can be some pros in staying in china rom too.
Click to expand...
Click to collapse
There are no bugs at all. Raw is not supported...
Now I want to swap to Global stable rom, is that posssible ? This is top priority now.
If not, How can I get google play working on this china 8.2 stable?
pi4a7a said:
There are no bugs at all. Raw is not supported...
Now I want to swap to Global stable rom, is that posssible ? This is top priority now.
If not, How can I get google play working on this china 8.2 stable?
Click to expand...
Click to collapse
So it didn't pass the manual camera compatibility test? (Note, RAW is not available in stock camera, it can only be used in some 3rd party camera if camera 2 api is enabled which can be checked using manual camera compatibility test)
I guess, then they implemented this feature in the dev versions. You can probably update to china dev by downloading the latest china dev ota rom and updating it with the updater app after renaming it to update.zip. Or they will probably implement it in the later stable versions which they will release.
Switching to global rom without unlocking bootloader? Now that process is not as straightforward.
Here's a thread about it: http://en.miui.com/thread-299790-1-1.html
But it talks about making\buying an engineering cable.....unlocking bootloader is much less hassle imo and in future all these rom switicng things will be lot easier.......
For installing google apps in china rom, you need google installer or something, I guess. Installing gapps should be the simplest thing that you can try at the moment, I guess. You have to use google installer or something.
http://www.technobuzz.net/install-google-apps-xiaomi-miui-china-rom/
https://xiaomininja.com/2016/09/16/the-complete-guide-to-installing-google-apps-gaaps-on-miui-8/
I gave some links earlier too...I really haven't tried any of these things, google can be your friends in this regards.
JRC1995 said:
So it didn't pass the manual camera compatibility test? (Note, RAW is not available in stock camera, it can only be used in some 3rd party camera if camera 2 api is enabled which can be checked using manual camera compatibility test)
I guess, then they implemented this feature in the dev versions. You can probably update to china dev by downloading the latest china dev ota rom and updating it with the updater app after renaming it to update.zip. Or they will probably implement it in the later stable versions which they will release.
Switching to global rom without unlocking bootloader? Now that process is not as straightforward.
Here's a thread about it: http://en.miui.com/thread-299790-1-1.html
But it talks about making\buying an engineering cable.....unlocking bootloader is much less hassle imo and in future all these rom switicng things will be lot easier.......
For installing google apps in china rom, you need google installer or something, I guess. Installing gapps should be the simplest thing that you can try at the moment, I guess. You have to use google installer or something.
http://www.technobuzz.net/install-google-apps-xiaomi-miui-china-rom/
https://xiaomininja.com/2016/09/16/the-complete-guide-to-installing-google-apps-gaaps-on-miui-8/
I gave some links earlier too...I really haven't tried any of these things, google can be your friends in this regards.
Click to expand...
Click to collapse
So if I unlock my bootloader it will be easy to change to Global Stable right?
I will reques unlock code.
Can you share the process for UB please?
And how to lock it later if its not ok to stay with unlocked..
When I try to use screen mirroring to connect to my Samsung smart TV(nu7100) I get an error "Your output device does not support HDCP. Cannot mirror. You still can mirror some apps and unprotected content to the device."
When I mirror from the settings or music app, it works, but nothing else. I have an Ulefone power 5, and a Samsung a8+, and they both work flawlessly with the same tv.
I tried on a miracast dongle on another tv, with the same error (the other phones do work on the dongle as well)
I followed the instructions from https://www.youtube.com/watch?v=1wIM67kVVL8 but no difference.
How can I get this working? Pretty basic feature...
Do you root your phone? My phone rooted and can't connect to my sony tv
Yeah, I assume you unlocked the bootloader.
It needs a hack to ignore the missing DRM keys.
Damn, yes I am rooted so bl unlocked..
Are there any hacks the community knows about that work? I had run xperifix on oero to fix the camera, which didn't work, and flashed stock pie, which fixed the camera but didn't fix the drm keys..
Kobro said:
Damn, yes I am rooted so bl unlocked..
Are there any hacks the community knows about that work? I had run xperifix on oero to fix the camera, which didn't work, and flashed stock pie, which fixed the camera but didn't fix the drm keys..
Click to expand...
Click to collapse
Did you switched to SeLinux Permissive after you installed XperiFix on Oreo?
MartinX3 said:
Did you switched to SeLinux Permissive after you installed XperiFix on Oreo?
Click to expand...
Click to collapse
I did but that did not help the camera. I don't know if it helped the drm. Should I try setting that now to see of it solves the hdcp issue?
It IS a fix if so, but I don't really think having selinux always be permissive on a rooted device seems very safe..
Kobro said:
I did but that did not help the camera. I don't know if it helped the drm. Should I try setting that now to see of it solves the hdcp issue?
It IS a fix if so, but I don't really think having selinux always be permissive on a rooted device seems very safe..
Click to expand...
Click to collapse
Did you unlock the bootloader on PIE or on OREO?
If the camera preview in OREO with permissive doesn't work, the xperifix is not active.
Did you do a custom installation with A/B, VENDOR and by choosing the magisk.zip?
MartinX3 said:
Did you unlock the bootloader on PIE or on OREO?
If the camera preview in OREO with permissive doesn't work, the xperifix is not active.
Did you do a custom installation with A/B, VENDOR and by choosing the magisk.zip?
Click to expand...
Click to collapse
Unlocked in pie, downgraded to oreo, ran xperifix exactly as you described, but it still didnt work. Then upgraded to pie again and camera was fixed but I don't know how or what did it
Kobro said:
Unlocked in pie, downgraded to oreo, ran xperifix exactly as you described, but it still didnt work. Then upgraded to pie again and camera was fixed but I don't know how or what did it
Click to expand...
Click to collapse
If you have a camerapreview in PIE then you don't need the camerafix in PIE.
And probably the xperifix won't work.
They changed the way how the DRM keys are getting removed from the TA partition.
Now less features are lost after unlocking.
MartinX3 said:
If you have a camerapreview in PIE then you don't need the camerafix in PIE.
And probably the xperifix won't work.
They changed the way how the DRM keys are getting removed from the TA partition.
Now less features are lost after unlocking.
Click to expand...
Click to collapse
Camera preview worls and no green images eother. In the settings I see rhe xreality things, and I assumed the other drm things worked too. Question is, what do I do about the HDCP issue now in pie?
Kobro said:
Camera preview worls and no green images eother. In the settings I see rhe xreality things, and I assumed the other drm things worked too. Question is, what do I do about the HDCP issue now in pie?
Click to expand...
Click to collapse
Maybe switching to a custom ROM after OEMv8 got released with some TAMA camera fixes and test it there?
If it doesn't work there, you can write a bug report and it may get fixed.
But stock. umhhhh DRM.
I kind of found a workaround. For me the reason I need to screen mirror at all is to watch videosvstores on my phone, on the big screen. So I found apps in the play store that can stream without hdcp. (Allcast etc) So, it's not full mirroring, but at least I can cast my videos, that'll have to do for now.
Greetings Folks
For starters I just got Mi8 and am planning to go for Havoc or Pixel Experience there is a Pixel Port too I'll have to try which is best close to stock but with gestures features and full fledged Gcam support
Back to Questions
I have seen many threads where newer folks are victim of their devices getting bricked and paying for fix?
Why isnt there a proper guide thread to avoid these obstacles and spread awareness out ?
I know there are certain partitions you need to backup too e.g efs in case of lost IMEI there was a thread Its hell I have been through it with a Samsung Device,There was a guy who messed up his phone sensor files?
But most of all EDL and Devices getting brick so lets address the elephant in the room
Now My Phone is on
MIUI 10.3 Global 10.3.2.0(PEAMIXM)
Android Version : 9 PKQ1.180729.001
Android Security Patch : 2019-04-01
Rom threads say 9.3
take havoc for example
Help Appreciated thanks
@techyrock
Here is a guide : https://forum.xda-developers.com/mi-8/how-to/how-to-install-roms-resolve-issues-t3911611
Part 1 ( The OP is general info ) Below the first couple of comments have detailed steps for AOSP.
Be extremely careful, unfortunately this community doesn't have a lot of highly active professionals.
So definitely double check any advice that you are given, or that you find. With that being said there are definitely several members that are mature, knowledgeable, friendly and overall fantastic.
If you need help, feel free to ask me anytime, I haven't had a lot of time to use XDA recently. But if I am around, I am always willing to help. At the moment I am going to sleep, but go ahead and read my thread, and I have made some lengthy post that may be helpful as well. You can find those posts by reading my post history. Enjoy.
As long as your account is bound to your device, unbricking is pretty easy with these phones. If you want to avoid a brick, avoid brand new builds, test software etc. Some of the recent issues actually stemmed from the 7.11 china developer rom which had a major issue.
if you want to use Miui with zero ads, and every single feature, then Mi-Globe is pretty great, and solid on a week to week basis.
As far as AOSP, I feel that in my experience that Syberia is practically always highly stable, but it's a little plain compared to some other roms. I also liked Pixel 3, Bootleggers ( Newer version) and Havoc. ( I used Havoc in the beginning of July and loved it, that build is fantastic)
I haven't tried a lot of AOSP roms on this phone yet. So that is all I have
Addition to that, the main issue is people are using Miflash to flash a ROM from bootloader. DO NOT USE IT.
Just use the flash_all.bat in the fastboot rom zip, it's easy. Miflash chooses to lock bootloader by default, and if you don't change it, you'll need to use EDL to fix your device. People usually forget about it, and will whine here to be able to unbrick. Don't be one of them
Don't relock the damn bootloader. It's unnecessary, and dangerous on a Chinese machine.
The War Profiteer said:
Addition to that, the main issue is people are using Miflash to flash a ROM from bootloader. DO NOT USE IT.
Just use the flash_all.bat in the fastboot rom zip, it's easy. Miflash chooses to lock bootloader by default, and if you don't change it, you'll need to use EDL to fix your device. People usually forget about it, and will whine here to be able to unbrick. Don't be one of them
Don't relock the damn bootloader. It's unnecessary, and dangerous on a Chinese machine.
Click to expand...
Click to collapse
We ok that to unlock bootloader on mi8 we have to use mi "flash" unlock tool. Right?
Cheers
Erpe7 said:
We ok that to unlock bootloader on mi8 we have to use mi "flash" unlock tool. Right?
Cheers
Click to expand...
Click to collapse
Yes, that is the only way to unlock. he was talking about using Mi Flash to flash roms, which may seem to be user friendly which it is but is also extremely dangerous because the the option to lock the bootloader is checked by default. If using it make sure that its unchecked and you should not have any issues.
Personally, I prefer ADB if flashing via fastboot or TWRP with a OTG flash drive.
Also there is a tool that is excellent that I have also used many times, its called Tool all in One ( TAIO) After your bootloader is unlocked, you can use TAIO for many functions, including keep your PC's ADB platform tools, up to date, and providing system wide access. You can use it to remove encryption, flash recovery, root, roms or to restore to stock. It definitely worth installing if if you only use it to keep your drivers, and platform tools up to date.
First of all thanks guys for replies wasn't expecting this response
My device is Global Mi8 bootloader is locked for now I still have some hours left I'll be able to unlock it by 26th
miflash_unlock prompted to bind my account from developer option for unlocking,I did so it will be bound to my account and ill be unlocking it for first time I believe i bought it used but previous owner seemed to have know info about ROMs though
I have been using Pixel 2XL twice followed by Nokia 8 so I am much more inclined towards AOSP stock experience the two feature I would love to have from MIUI are the
1)MIUI gestures
2)MIUI Dual Apps (I am aware of Play store alternatives but clash of clans doesnt work as good on them as on dual apps )
I know gestures are on Havoc
guess you guys have been playing around with your mi8 kindly guide me to right directrion what ROMs you guys prefer and why ?
how would you prefer to flash a ROM do I need to back up any partitions ? if so which app should use for it ,Ill surely back up everything via TWRP for sure
also the encryption thingy should I sign out my google account before bootloader unlock and other stuff?
and since I am on
MIUI 10.3 Global 10.3.2.0(PEAMIXM)
Android Version : 9 PKQ1.180729.001
Android Security Patch : 2019-04-01
is it safe to flash havoc ?
tsongming said:
Yes, that is the only way to unlock. he was talking about using Mi Flash to flash roms, which may seem to be user friendly which it is but is also extremely dangerous because the the option to lock the bootloader is checked by default. If using it make sure that its unchecked and you should not have any issues.
Personally, I prefer ADB if flashing via fastboot or TWRP with a OTG flash drive.
Also there is a tool that is excellent that I have also used many times, its called Tool all in One ( TAIO) After your bootloader is unlocked, you can use TAIO for many functions, including keep your PC's ADB platform tools, up to date, and providing system wide access. You can use it to remove encryption, flash recovery, root, roms or to restore to stock. It definitely worth installing if if you only use it to keep your drivers, and platform tools up to date.
Click to expand...
Click to collapse
Thank you for this precious advices ;(
I'll note that!
Sent from my Redmi Note 5 Pro using XDA Labs
Thank you folks.
Could someone explain what EDL is meaning?
Gesendet von meinem BTV-DL09 mit Tapatalk
ktrokar said:
Thank you folks.
Could someone explain what EDL is meaning?
Gesendet von meinem BTV-DL09 mit Tapatalk
Click to expand...
Click to collapse
There's a primary bootloader that we consumer know of and there's Qualcomm's Emergency Download Mode bootloader (EDL) , since Mi8 has ARB(Anti Rollback) downgrading the phone gets it bricked to EDL mode requiring EDL authentication to my understanding thats why edl is a thing(since its just emergency bootloader for oems to work with) I have not experienced it personally so I don't know whether it bricks that way or not but ARB and EDL authentication are a thing with Mi8 from what I have read in different threads
Sent from my MI 8 using Tapatalk
ktrokar said:
Thank you folks.
Could someone explain what EDL is meaning?
Gesendet von meinem BTV-DL09 mit Tapatalk
Click to expand...
Click to collapse
EDL is Qualcomm recovery mode, it's the mode that you must be in to restore a hard bricked phone.
As long as you are careful you should never need to worry about EDL. Basically, you place the phone into a mode that the computer is able to recognise port 9008, once that is down you can use 1 of 4 techniques to restore your phone. Unbricking Xiaomi's is actually very easy to do, as long as the device is bound to your account.
The big issue is that unscrupulous Chinese vendors, used their own account to unlock bootloaders of Mi8's and other Xiaomi devices, then installed the Global Miui ROM and then sold the phone as new to unsuspecting western customers and at a lower price than western outlets such as Amazon. These vendors marketed the phones as Ïnternational versions" when they were actually Chinese devices and not the Global version that the customer thought they bought.
When these customer's used programs such as MiFlash to upgrade their phone's their bootloaders were locked and the are unable to log into their Mi Account to restore the phone. Remember the vendors unlocked the phone, so these Mi8's were bound to the vendor and not the final customer. This is the Primary reason why Xiaomi makes us wait to unlock the bootloader. Finally, ARB is potential issue, but it hasn't been implemented yet on Global devices.
So do your research before flashing anything and you should be safe.
As the title states, my auto brightness, compass and proximity sensors are all broken, I believe this is a failure of a partition similar to persist.img where the fingerprint used to be stored.
Had this issue a while back but I hadn't noticed the compass being broken
I've ran through the tests in engineer mode *#*#4636#*#* and the results are all null for the above sensors.
Factory wipe did nothing, moving between bases 12-13 did nothing, installing a GSI only affected only system.
I'd rather not RMA if I don't have to..
Any ideas anyone??
Have you tried installing lineage and then reverting back?
https://www.droidwin.com/how-to-install-lineageos-rom-on-oneplus-10-pro
g96818 said:
Have you tried installing lineage and then reverting back?
https://www.droidwin.com/how-to-install-lineageos-rom-on-oneplus-10-pro
Click to expand...
Click to collapse
That's a GSI buddy, yes I've installed them all.. but they only affect system so the issues will remain as the partitions that house the sensors aren't affected...
Similar thing happened on the 8 pro with the fingerprint, the perist partition was the culprit.
Have mentioned all this in the OP.
dladz said:
That's a GSI buddy, yes I've installed them all.. but they only affect system so the issues will remain as the partitions that house the sensors aren't affected...
Similar thing happened on the 8 pro with the fingerprint, the perist partition was the culprit.
Have mentioned all this in the OP.
Click to expand...
Click to collapse
i see. i'm not paying attention to any roms for this phone since there's no msm available to use without paying.
I haven't been followed this thread, but you could try flashing this fastboot rom. I'm not sure if anyone tested it, but the 9RT version worked great to convert COS to OOS without side effects.
OnePlus 10 Pro Fastboot ROMs (and how to make for any device)
First of all and most importantly, I want to say that this is not my work. This is a port of the work done by @abhinavgupta371 and @HELLBOY017 for the OP9RT. I merely made sure there weren't extra or missing files and edited the .bat and .sh...
forum.xda-developers.com
Here's the original post it was built from
[FASTBOOT][ROM][UNOFFICIAL][OP9RT] OxygenOS A.04-A.08 for MT2110 devices
Greetings, I've appreciated @abhinavgupta371, @HELLBOY017 for initial version of this firmware and @penguinus for continuous support and testing. PLEASE NOTE THAT FASTBOOT ROMS CAN ONLY BE USED IN DEVICES WITH AN UNLOCKED BOOTLOADER!!! AND BE...
forum.xda-developers.com
g96818 said:
i see. i'm not paying attention to any roms for this phone since there's no msm available to use without paying.
I haven't been followed this thread, but you could try flashing this fastboot rom. I'm not sure if anyone tested it, but the 9RT version worked great to convert COS to OOS without side effects.
OnePlus 10 Pro Fastboot ROMs (and how to make for any device)
First of all and most importantly, I want to say that this is not my work. This is a port of the work done by @abhinavgupta371 and @HELLBOY017 for the OP9RT. I merely made sure there weren't extra or missing files and edited the .bat and .sh...
forum.xda-developers.com
Here's the original post it was built from
[FASTBOOT][ROM][UNOFFICIAL][OP9RT] OxygenOS A.04-A.08 for MT2110 devices
Greetings, I've appreciated @abhinavgupta371, @HELLBOY017 for initial version of this firmware and @penguinus for continuous support and testing. PLEASE NOTE THAT FASTBOOT ROMS CAN ONLY BE USED IN DEVICES WITH AN UNLOCKED BOOTLOADER!!! AND BE...
forum.xda-developers.com
Click to expand...
Click to collapse
Have you used fastboot enhance to flash a rom?
AFAIK it's just a case of deleting the cows then extracting the payload then flashing it in fastbootd
I think the partition needs nuking then rebuilding.
On the 8 pro they used MSM, different ROMs and and fastboot, nothing worked.
Have you any idea where these sensors information is stored? What partition?
Anyone else have any idea?
Finding out where the proximity, compass and auto brightness sensor data is kept would help me
Answered my own question.
It is indeed within the persist partition.
How to Fix Android 10’s Sensors Bug Caused by Corrupted Persist Partition
A step-by-step guide on how to fix the Android 10 Sensors bug caused by corrupted Persist partition, on devices like Google Pixel, Xiaomi Mi A3, and others.
www.thecustomdroid.com
To fix this is need someone elses persist.img
Could someone extract theirs so i can use it please?
Theres nothing i can use in there i'm just using it as the files in mine are corrupt.
To pull it it's quite simple.
Connect your phone to your computer and open an ADB terminal then type the following
adb shell
Press enter and allow the prompt on your phone if you get one.
su
Press enter and allow the root prompt on your phone
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
Press enter, this will put a file called persist.img on the root of your phone, it contains functional calibrated files for auto brightness, fp reader, proximity sensor and compass.
I'm not able to see your fingerprints or anything like that, its just going to be used to restore my device to a functional state.
Hope someone can help with this, anyone who's rooted can do this and it won't affect them.
Cheers
PS: if this works, then we'll have a fix for broken sensors if anyone should run into it, i'm happy to share mine once it's working
dladz said:
To fix this is need someone elses persist.img
Could someone extract theirs so i can use it please?
Theres nothing i can use in there i'm just using it as the files in mine are corrupt.
To pull it it's quite simple.
Connect your phone to your computer and open an ADB terminal then type the following
adb shell
Press enter and allow the prompt on your phone if you get one.
su
Press enter and allow the root prompt on your phone
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
Press enter, this will put a file called persist.img on the root of your phone, it contains functional calibrated files for auto brightness, fp reader, proximity sensor and compass.
I'm not able to see your fingerprints or anything like that, its just going to be used to restore my device to a functional state.
Hope someone can help with this, anyone who's rooted can do this and it won't affect them.
Cheers
PS: if this works, then we'll have a fix for broken sensors if anyone should run into it, i'm happy to share mine once it's working
Click to expand...
Click to collapse
it doesn't seem like a file that gets updated during updates since it's not in the payload file. I can send you my vanilla persist.img from the moment i first rooted, but idk if 2215 and 2213 images are the same. AFH is giving me errors again with uploading. I'll PM you a google link instead.
g96818 said:
it doesn't seem like a file that gets updated during updates since it's not in the payload file. I can send you my vanilla persist.img from the moment i first rooted, but idk if 2215 and 2213 images are the same. AFH is giving me errors again with uploading. I'll PM you a google link instead.
Click to expand...
Click to collapse
I appreciate that mate, thank you.
I'm just updating to A_17
But you're right, it doesn't update it, i've just used fastboot enhance and flashed a payload from A_13, same issue.
It's so horrible man, missing these things isn't breaking the phone but it's really inconvenient.
dladz said:
I appreciate that mate, thank you.
I'm just updating to A_17
But you're right, it doesn't update it, i've just used fastboot enhance and flashed a payload from A_13, same issue.
It's so horrible man, missing these things isn't breaking the phone but it's really inconvenient.
Click to expand...
Click to collapse
yea it sucks, especially since oppo isn't releasing the msm tools.
hope the file works for you. it came out of my A.10 rom. hopefully A.10 shared more files than just the boot image.
It flashed and did affect the fingerprint but unfortunately didn't fix the other sensors.
Restored mine and my FP is working again but all other sensors are broken.
I think RMA is the only way at this point.
Just found this.
[Guide] About repairing/fixing the persist partition
Disclaimer: I am not responsible for the results of any of these operations. Everyone knows that the persist partition is responsible for sonsors and carrier network etc. Once this partition is failed or lost, your phone will go wrong. I just...
forum.xda-developers.com
Going to give this a whirl.. I reckon it could work.
dladz said:
Just found this.
[Guide] About repairing/fixing the persist partition
Disclaimer: I am not responsible for the results of any of these operations. Everyone knows that the persist partition is responsible for sonsors and carrier network etc. Once this partition is failed or lost, your phone will go wrong. I just...
forum.xda-developers.com
Going to give this a whirl.. I reckon it could work.
Click to expand...
Click to collapse
It didn't..
dladz said:
It didn't..
Click to expand...
Click to collapse
were you able to solve the problem?
crhistiandavidbonilla47 said:
were you able to solve the problem?
Click to expand...
Click to collapse
Nope...still can't use proximity, nor auto brightness, I'll send it back prior to the end of my contract, then sell it..but not until then.
I don't believe there is a fix for it.
dladz said:
Nope...still can't use proximity, nor auto brightness, I'll send it back prior to the end of my contract, then sell it..but not until then.
I don't believe there is a fix for it.
Click to expand...
Click to collapse
without a doubt my worst purchase was this device
crhistiandavidbonilla47 said:
without a doubt my worst purchase was this device
Click to expand...
Click to collapse
Haha, try to see the good, you live and you learn..
I've bought some stinkers, Nokia Lumia 800, note 4, Sony Z1, Huawei p20 pro, HTC Evo 3D.
You take the good with the bad.
You'll learn to avoid this problem in future, I'm sure you'll have another problem with a future phone and you'll learn from that too.
Just try to see the good.
Performance is unreal
Battery life is superb
Speakers are great.
Cameras are top notch.
We have root.
We have some mods
We have TWRP
Sure no ROMs but that could change (maybe)
Lot of updates.
RMA is solid.
For most people that above list is way more than enough.
dladz said:
Haha, try to see the good, you live and you learn..
I've bought some stinkers, Nokia Lumia 800, note 4, Sony Z1, Huawei p20 pro, HTC Evo 3D.
You take the good with the bad.
You'll learn to avoid this problem in future, I'm sure you'll have another problem with a future phone and you'll learn from that too.
Just try to see the good.
Performance is unreal
Battery life is superb
Speakers are great.
Cameras are top notch.
We have root.
We have some mods
We have TWRP
Sure no ROMs but that could change (maybe)
Lot of updates.
RMA is solid.
For most people that above list is way more than enough.
Click to expand...
Click to collapse
Yeah, you are right