Related
Hi All,
Was finally able to get a hold of the Android 7 version for Zuk Z2pro, at this point it's in the development phase, looks pretty stable as of now, it's just been an hour since I installed it, Got it from the Chinese site ( Landlord ) a little tough to figure out the content on the site, but the ROM is in English.
I tried flashing it with the Stock Recovery but didn't work , went back to 2.3.044 and then flashed the TWRP ( Chinese Version ) Did a dirty flash, and all the sensors {Heart Rate, UV Sensor, Pedometer, Proximity, etc } seem to be working fine. The file is available in a Baidu link, and it takes a lot of time to download.
The ROM now supports themes but as of now i see only 4 inbuilt themes and no black themes. But inbuilt themes uses nice icons to make it look simple and neat. I shall post pics of the screens. Settings now show the lab features directly to play around with fake location( never got it working though ). As of now calls and Volte working fine. Haven't been successful in making video calls over LTE with Zui Roms.
Need some help in getting a cloud storage to upload the file.
If someone could help me, would be happy to upload it for the benefit of the community. Again ***** Please do install it at your own risk, make sure you backup in TWRP before you flash this ROM , the size is 1.6 GB. ***** All thanks to the Chinese forums BBS.lenovomobiles.
Screenshots
These are the screenshots
And you can download the file from :
https://drive.google.com/file/d/0B6GiX9_gwfCqVXVhRHcyVEdfbkU/view?usp=sharing
Make sure you backup in TWRP, Please use the Chinese version of the TWRP to flash this file,
More screenshots please ??
Some bugs ? Any way to go back to Android 6? After flashing this ROM TWRP still working?
Отправлено с моего Z2 Pro через Tapatalk
Bugs
raber111 said:
Some bugs ? Any way to go back to Android 6? After flashing this ROM TWRP still working?
Отправлено с моего Z2 Pro через Tapatalk
Click to expand...
Click to collapse
Following are the bugs I have noticed
1. Vibration stops working, a reboot will be needed
2. Manual mode in the Camera gives a red tint in faster shutter speeds
3. No Root, haven't been able to root it, maybe I am doing it wrong. Flashing the Superuser in TWRP makes the sim card go an undetected state.
4. No options to set a live wallpaper ( Google Pixel wallpaper with animation ). Figured out a way to fix it by using the app shortcut maker to set a shortcut for the live wallpaper picker.
5. Battery seems to be draining faster.
Will keep adding can't complain as it is a dev version.
anupsnair said:
Following are the bugs I have noticed
1. Vibration stops working, a reboot will be needed
2. Manual mode in the Camera gives a red tint in faster shutter speeds
3. No Root, haven't been able to root it, maybe I am doing it wrong. Flashing the Superuser in TWRP makes the sim card go an undetected state.
4. No options to set a live wallpaper ( Google Pixel wallpaper with animation ). Figured out a way to fix it by using the app shortcut maker to set a shortcut for the live wallpaper picker.
5. Battery seems to be draining faster.
Will keep adding can't complain as it is a dev version.
Click to expand...
Click to collapse
So TWRP still working after flashing?
Gapps working?
Отправлено Ñ Ð¼Ð¾ÐµÐ³Ð¾ Z2 Pro через Tapatalk
I'm not able to flash it via chinese TWRP. I've also tried TWRP from Emmaus. If someone can share a working recovery with this ROM I'll tell you my opinion about it. (Error 7 is the problem).
raber111 said:
So TWRP still working after flashing?
Gapps working?
Þтÿрðòûõýþ Ѡüþõóþ Z2 Pro чõрõ÷ Tapatalk
Click to expand...
Click to collapse
TWRP works fine, just that I wasn't able to root it, Gapps not required, as I installed the Google sync app and the Google contacts previously on the 2.3.044 build since I did a dirty update, got the play store and the Google contacts in tact
cyBeRdUdE-9 said:
More screenshots please ??
Click to expand...
Click to collapse
Hi Cyberdude,
Is there any specific screen that u are looking for?
anupsnair said:
Hi Cyberdude,
Is there any specific screen that u are looking for?
Click to expand...
Click to collapse
Screens of any major UI changes ??
Hey I was on CM13 By Emmaus, did a TWRP backup.
Flashed the Chinese TWRP.
Wipe -> Flashed the Android 7 ZUI -> Used it for a day and wanted to go back to CM13.
I flashed the TWRP By Emmaus-> Restore-> Now the phone doesnt go past the ZUK logo with the blue LED light.
What do you think needs to be done to restore the TWRP backup and go back to CM13?
Edit: Solution: I had QFIL to 1.9 then flash Emmaus Recovery and restore.
Root Zuk Z2pro Android 7
Hi All,
For those who need to root this ROM, you can flash the following file from twrp it's a modified version of SU,
anupsnair said:
Hi All,
For those who need to root this ROM, you can flash the following file from twrp it's a modified version of SU,
Click to expand...
Click to collapse
I've flashed just the last version of SuperSu beta, no modify version needed in my option because is working like a charm!
Sent from my Z2 Pro using Tapatalk
lucaam said:
I've flashed just the last version of SuperSu beta, no modify version needed in my option because is working like a charm!
Sent from my Z2 Pro using Tapatalk
Click to expand...
Click to collapse
Thank you Lucaam, for the benefit of the forum can you please post a link, when I flashed SU, the sim in my phone stopped working.
Here's to you the link https://download.chainfire.eu/750/SuperSU/BETA-SuperSU-v2.64-20151220185127.zip?retrieve_file=1 of to the file that I've downloaded. I flashed it after the first full boot.
Sent from my Z2 Pro using Tapatalk
syedtahir16 said:
Hey I was on CM13 By Emmaus, did a TWRP backup.
Flashed the Chinese TWRP.
Wipe -> Flashed the Android 7 ZUI -> Used it for a day and wanted to go back to CM13.
I flashed the TWRP By Emmaus-> Restore-> Now the phone doesnt go past the ZUK logo with the blue LED light.
What do you think needs to be done to restore the TWRP backup and go back to CM13?
Edit: Solution: I had QFIL to 1.9 then flash Emmaus Recovery and restore.
Click to expand...
Click to collapse
hey dude, i had same problem, i couldn flash any rom through twrp, nor could i recover any backup.. then i saw your post, i could hardly flash 1.9 firmware, but even then, and even with locked or unlocked bootloader, i could neither update through official firmware update process (OTA) nor could i flash anything through any recovery, it stucks on updating/flashing system image unconditionaly.. so something strange happens when flashing 7.0, so you cannot go back anyway. May you could help. Its just so anoying that i cant restore my backups, cant install any custom rom, official rom, only qfil works but dont solves any problem.
thanks in advance
Ikram
ikram.senguen said:
hey dude, i had same problem, i couldn flash any rom through twrp, nor could i recover any backup.. then i saw your post, i could hardly flash 1.9 firmware, but even then, and even with locked or unlocked bootloader, i could neither update through official firmware update process (OTA) nor could i flash anything through any recovery, it stucks on updating/flashing system image unconditionaly.. so something strange happens when flashing 7.0, so you cannot go back anyway. May you could help. Its just so anoying that i cant restore my backups, cant install any custom rom, official rom, only qfil works but dont solves any problem.
thanks in advance
Ikram
Click to expand...
Click to collapse
I"m not certain about other backups. But I had a CM13 TWRP backup.
What I did was:
QFIL to 1.9. This should work irrespective of what recovery you have. This is like an absolute reset. Once this is done, let your phone reboot and load once.
Then adb reboot bootloader
In the bootloader mode -> Flash the recovery ( You will need to flash Emmaus recovery if you are going back to CM13).
Once flashed. You can wipe the data,system and cache. Install CM13 and you should be all set.
You could also wipe and restore any old CM13 Backup too. Hope this helps.
SOLVED
SOLVED: HOW? STRANGE!
i did everything exact same as at home, but somehow ..just somehow ..it didnt ****ed itself and didnt stuck on everywhere and indeed succeeded flashing every f****** rom!
so here a step-by-step (if some ever expirience same) thanks to you all which i can confirm:
1. flash 1.9.104 rom through qfil (let it boot..)
2. enable usb debuging through enabled developer settings
3. boot in fastboot (adb reboot bootloader) unlock bootloader with your unlock_bootloader.img (fastboot -i 0x2b4c flash unlock unlock_bootloader.img) right after that unlock it (fastboot -i 0x2b4c oem unlock-go) forreal
4. reboot, then enable usb debuging again and boot in fastboot again (adb reboot bootloader)
5. flash emmaus TWRP (fastboot flash recovery recovery.img) DO !NOT! USE ---> [fastboot -i 0x2b4c boot recovery.img] <--- CODE!
6. boot to TWRP, wipe data/cache/dalvik-cache (system not needed, better dont wipe system to be sure)
7. flash AICP, RR or CM13 .zip, NOT ANY OTHER (https://emmaus.pro/?dir=Zuk Z2 Pro & http://forum.xda-developers.com/zuk-z2-pro/development/rom-aicp-11-0-mm-6-0-1-unofficials-t3499283) those work for sure on emmaus TWRP
8. reboot, DONE
to every single zuk z2 pro user out there, please make sure your PC, USB PORT, USB-CABLE is working right, because even if everything seems right, under the hook its sometimes not. In my case, i knew it, but could not believe it since qfil showed me SUCCSESS in every section, the connection betweet cable and usb port was faulty, thats the only possibility. THANK YOU ALL VERY MUCH, this was one of the most HARD-BRIKS ive ever experienced, and ive been through S2, S3, S4, S5, S6, HTC ONE M7 hard-bricks.. so.. yeah!!! THANK YOU VERY MUCH :')
i try this zip on my twrp , but my phone are dead don't run anybody else
what i can do ?
Many thanks to you ! the flash worked very well. i had same issues here . best description ever many many thanks !!
Hi guys
Sorry for my bad English
My device was running Android 10
miui 11
After I accidentally used an application to raise the screen frequency to 84Hz
The devics did a reboot and then stopped on the fastboot logo
I tried to enter recovery mode but was back to fastboot mode
I tried to flash twrp via adb and fastboot but the method did not work and the device returned to fastboot mode
Finally I downloaded the ROM file global Version Android 9
miui 11 and when i flashed the system via "xiaomi flash tool " the operation was successful until it reached the end of the process it showed me an error and the flash failed
I restarted the process and noticed that the flashing process gives me the error when the download arrives at "flashing boot"
I searched a lot for the version of Android 10 miui 11 but I did not find
What is the problem!
Can anyone explain what the problem is?
Thank you very much
Edit : solved With the help of my friend and brother @tsongming thanks bro
You likely damaged the phone, myself and others have posted numerous warning about flashing mods to increase the refresh rate.
I would recommend trying the Flashall.bat method.
Follow my instructions here : https://forum.xda-developers.com/showpost.php?p=80825243&postcount=2
tsongming said:
You likely damaged the phone, myself and others have posted numerous warning about flashing mods to increase the refresh rate.
I would recommend trying the Flashall.bat method.
Follow my instructions here : https://forum.xda-developers.com/showpost.php?p=80825243&postcount=2
Click to expand...
Click to collapse
When i flash device with edl mod in xiaomi mi tool i got these error
What i can due
ahmadbasher said:
When i flash device with edl mod in xiaomi mi tool i got these error
What i can due
Click to expand...
Click to collapse
See this thread : https://c.mi.com/thread-2121755-1-0.html
Also, I read about some people getting past these recent issues by using a USB hub extender. These decrease the amount of power to the port which may be causing a conflict. Try other ports and only use a usb 2 port. Further, I would recommend temporarily disabling firewall and antivirus if all else fails. Worst case use another computer.
If this helps come back and let us know what finally resolved it.
tsongming said:
See this thread : https://c.mi.com/thread-2121755-1-0.html
Also, I read about some people getting past these recent issues by using a USB hub extender. These decrease the amount of power to the port which may be causing a conflict. Try other ports and only use a usb 2 port. Further, I would recommend temporarily disabling firewall and antivirus if all else fails. Worst case use another computer.
If this helps come back and let us know what finally resolved it.
Click to expand...
Click to collapse
I solved and my device life agin
I flash these rom http://bigota.d.miui.com/V9.5.11.0....EACNFA_20180703.0000.00_8.1_cn_64c55c8438.tgz
With mi flash tool older version (2016)
In fastboot mode
But now i need back to global rom and after i flash latest global rom in fastboot the device bricking again
And stay in fastboot
What is the problem
ahmadbasher said:
I solved and my device life agin
I flash these rom http://bigota.d.miui.com/V9.5.11.0....EACNFA_20180703.0000.00_8.1_cn_64c55c8438.tgz
With mi flash tool older version (2016)
In fastboot mode
But now i need back to global rom and after i flash latest global rom in fastboot the device bricking again
And stay in fastboot
What is the problem
Click to expand...
Click to collapse
You still have encryption on your device, use the tool all in one and install TWRP ( You may need to use a different/maybe older computer, I think possibly windows 10 is part of the issue. ( Because I have had this exact issue that you are having)
Install the tool, and update ADB but not the tool itself, there will be a popup, asking to update. ignore it or the update will be flagged a sbeinga virus ( Actually a Windows issue) However, yes the program is unsigned.
Use all in One tool to remove encryption from device and flash TWRP
Boot to recovery, immediately flash root, Flash Su if you must.
Reboot to recovery, then flash a recovery rom. the boot to system , may take up to 10 minutes.
use ports from the back of the PC and you may need to use a usb hub.
tsongming said:
You still have encryption on your device, use the tool all in one and install TWRP ( You may need to use a different/maybe older computer, I think possibly windows 10 is part of the issue. ( Because I have had this exact issue that you are having)
Install the tool, and update ADB but not the tool itself, there will be a popup, asking to update. ignore it or the update will be flagged a sbeinga virus ( Actually a Windows issue) However, yes the program is unsigned.
Use all in One tool to remove encryption from device and flash TWRP
Boot to recovery, immediately flash root, Flash Su if you must.
Reboot to recovery, then flash a recovery rom. the boot to system , may take up to 10 minutes.
use ports from the back of the PC and you may need to use a usb hub.
Click to expand...
Click to collapse
thanks for replay bro i will tri it
tsongming said:
You still have encryption on your device, use the tool all in one and install TWRP ( You may need to use a different/maybe older computer, I think possibly windows 10 is part of the issue. ( Because I have had this exact issue that you are having)
Install the tool, and update ADB but not the tool itself, there will be a popup, asking to update. ignore it or the update will be flagged a sbeinga virus ( Actually a Windows issue) However, yes the program is unsigned.
Use all in One tool to remove encryption from device and flash TWRP
Boot to recovery, immediately flash root, Flash Su if you must.
Reboot to recovery, then flash a recovery rom. the boot to system , may take up to 10 minutes.
use ports from the back of the PC and you may need to use a usb hub.
Click to expand...
Click to collapse
I tri it and no change
Again reboot to fastboot
ahmadbasher said:
I tri it and no change
Again reboot to fastboot
Click to expand...
Click to collapse
While its possible that you have a hardware issue. Unless the phone has been exposed to moisture, or exposed to a great deal of force I doubt that you have a hardware problem. Again, I too have had a similar issue, it's just took a while to finally get it working, in my case my computer was part of the problem, since you have fastboot the number one goal at the moment should be with getting TWRP recovery installed, and then root.
Did you happen to make any TWRP backups?
Hopefully so, specifically if you have a TWRP backup that includes the persist image files, you need to try flashing those to the persist partition. If you can successfully restore the persist image then try the flashall.bat method again.
Another option is to use QPST, but try the above first.
Edit
Finally, After re-reading you initial post. I had forgotten that you attempted to improve the refresh rate of the display. If all you can get is fastboot after following all of the steps that I have mentioned than I am certain that you have a burned chip. Ignore the people who claim that you can't fry the chip they have no idea what they are talking about. The chip can absolutely be fried. It's still worth trying a few more times, you could have just simply corrupted partition images. When you flash the stock rom, or even when using the flashall.bat method not every partition is over written.
@ahmadbasher
When you flashed the file to increase the refresh rate you likely overwrote a partition called DTBO, See if you can flash a Mi8 DTBO image to the DTBO partition. If you have the full recovery backup, you can extract the file from there. i need to research exactly how that file works and I will try to help you will getting the image if you don't have it in a backup.
tsongming said:
While its possible that you have a hardware issue. Unless the phone has been exposed to moisture, or exposed to a great deal of force I doubt that you have a hardware problem. Again, I too have had a similar issue, it's just took a while to finally get it working, in my case my computer was part of the problem, since you have fastboot the number one goal at the moment should be with getting TWRP recovery installed, and then root.
Did you happen to make any TWRP backups?
Hopefully so, specifically if you have a TWRP backup that includes the persist image files, you need to try flashing those to the persist partition. If you can successfully restore the persist image then try the flashall.bat method again.
Another option is to use QPST, but try the above first.
Edit
Finally, After re-reading you initial post. I had forgotten that you attempted to improve the refresh rate of the display. If all you can get is fastboot after following all of the steps that I have mentioned than I am certain that you have a burned chip. Ignore the people who claim that you can't fry the chip they have no idea what they are talking about. The chip can absolutely be fried. It's still worth trying a few more times, you could have just simply corrupted partition images. When you flash the stock rom, or even when using the flashall.bat method not every partition is over written.
@ahmadbasher
When you flashed the file to increase the refresh rate you likely overwrote a partition called DTBO, See if you can flash a Mi8 DTBO image to the DTBO partition. If you have the full recovery backup, you can extract the file from there. i need to research exactly how that file works and I will try to help you will getting the image if you don't have it in a backup.
Click to expand...
Click to collapse
All thanks to you my friend, I do not know how I can give all thanks and gratitude to you for helping me ? But my friend unfortunately I do not have a backup of it Will wait for you
Thanks again
Is it possible that this is part of the problem..!
I can't check it
@tsongming
ahmadbasher said:
All thanks to you my friend, I do not know how I can give all thanks and gratitude to you for helping me But my friend unfortunately I do not have a backup of it Will wait for you
Thanks again
Click to expand...
Click to collapse
No problem, after reading some various post on GitHub, CNX, and source android.com, I found out that the Mi8 DTBO is in the boot. Image.
So you should be able to flash a boot image, root, and then recovery and hopefully boot to TWRP.
If that doesn't work then send me a pm and I will share my personal dtbo with you privately. But again you shouldn't need mine since dtbo is nothing more than the device tree and the boot image should suffice, because it has the exact same file.
ADB command : fastboot flash boot c:\boot.img
ahmadbasher said:
Is it possible that this is part of the problem..!
I can't check it
@tsongming
Click to expand...
Click to collapse
No that is just encryption, if the issue was related to encryption the flashall.bat method would have resolved it.
If you had a persist issue, you would see specific messages about not being able to mount the persist partition.
tsongming said:
No problem, after reading some various post on GitHub, CNX, and source android.com, I found out that the Mi8 DTBO is in the boot. Image.
So you should be able to flash a boot image, root, and then recovery and hopefully boot to TWRP.
If that doesn't work then send me a pm and I will share my personal dtbo with you privately. But again you shouldn't need mine since dtbo is nothing more than the device tree and the boot image should suffice, because it has the exact same file.
ADB command : fastboot flash boot c:\boot.img
Click to expand...
Click to collapse
Thank you I will now try to do this
Yesterday I flashed the pixle rom on the device and I took off the device without problems but every period of time the device was doing a reboot, I do not know if it is the problem of the ROM or there is something wrong with the device
I tell you so that you know only that
Now I will flash the latest version of miui 11 android 9 global version, and flash the boot.img and then Root and finally Recovery True ?
ahmadbasher said:
Thank you I will now try to do this
Yesterday I flashed the pixle rom on the device and I took off the device without problems but every period of time the device was doing a reboot, I do not know if it is the problem of the ROM or there is something wrong with the device
I tell you so that you know only that
Now I will flash the latest version of miui 11 android 9 global version, and flash the boot.img and then Root and finally Recovery True ?
Click to expand...
Click to collapse
Hey sorry for the delay in getting back to you, I sent you the link for the file via PM.
Also, I would strongly suggest using the stock miui initially. Just until you know it's resolved. Also while Miui is installed make a full TWRP backup and save it to your desktop. This way you always have a full backup to resolve any serious issues.
Then once you know everything is working as it should then go back to what you prefer..
For the record this issue was solved. Anyone reading this, make sure that you have a full working TWRP backup of your working device, it will save you a lot of headaches. The solution for the refresh rate is issue is restoring stock DTBO, and then flashing Miui Stock.
Hello Guys,
I am facing this weird issue. Whenever i am trying to switch to my front camera the camera keeps switching between both the rear ones. I tried flashing stock, tried different roms, nothing is helping.
Please suggest a solutions. Thanks
gamerboy_010 said:
Hello Guys,
I am facing this weird issue. Whenever i am trying to switch to my front camera the camera keeps switching between both the rear ones. I tried flashing stock, tried different roms, nothing is helping.
Please suggest a solutions. Thanks
Click to expand...
Click to collapse
very unusual sounding problem ...sounds like you tried to play around with vendor props and to make aux camera working
flash stock using miflash ...do it in edl mode using fastboot
fastboot oem.edl
when finished ...BOOT not flash orange fox revovery
fastboot boot recovery.img
*"might be different command depending on pc amd name and location of downloaded recovery
then use a persist restorer flashable zip you can.find in jasmine/wayne official telegram.group and flash that ..
them reboot and use as normal
Thanks, i will try and rever
I tried the process you suggested and followed every step. Even after that the camera is still switching between rear ones. Can't switch to front camera.
gamerboy_010 said:
I tried the process you suggested and followed every step. Even after that the camera is still switching between rear ones. Can't switch to front camera.
Click to expand...
Click to collapse
yeah no bro that is impossible even if nothing is impossible that is 99% impossible and you didn't do everything that i suggested
make a video of the problem and a video of applying my fix
if not i can't help you further ..
Here's what i did.
Rebooted the phone to fastboot - used fastboot oem edl
Phone was detected as COM 10 in Mi FlashTool.
Flashed whole Pie Stock Rom.
Without booting, went to fastboot and unlocked bootloader although it was showing its already unlocked.
Used fastboot boot recovery.img and went into recovery.
Flashed persistrestorer6X.zip, found in Mi A2 telegram group, there is only zip.
Booted the phone. Tell me a few things.
Which stock version to flash?
What's wrong in above steps that i did?
gamerboy_010 said:
Here's what i did.
Rebooted the phone to fastboot - used fastboot oem edl
Phone was detected as COM 10 in Mi FlashTool.
Flashed whole Pie Stock Rom.
Without booting, went to fastboot and unlocked bootloader although it was showing its already unlocked.
Used fastboot boot recovery.img and went into recovery.
Flashed persistrestorer6X.zip, found in Mi A2 telegram group, there is only zip.
Booted the phone. Tell me a few things.
Which stock version to flash?
What's wrong in above steps that i did?
Click to expand...
Click to collapse
what device are you using ?
jasmine or wayne
which recovery did you use ?
_what i can tell you is not all twrp recovery works or can flash persist
_ try to use orange fox but use another recovery that can backup and flash persist ..
press
mount button ...if you don't see persist partition option here the recovery can not flash it even if .zip seems to flash well
look for pie persist.img for your device according to if it is jasmine or wayne ...look for recovery that can mount, backup and flash .img files to persist
---------- Post added at 09:01 PM ---------- Previous post was at 08:42 PM ----------
use these files bro
https://www.dropbox.com/s/w2d2z92yn6115ot/persist.img?dl=0
https://www.dropbox.com/s/zy8prxeum9qbkx5/TWRP-3.2.3-0810-XIAOMI6X-RU-wzsx150-hypeartist.zip?dl=0
https://www.dropbox.com/s/or0n7b6hxagr2ee/4_6050642049911227980.zip?dl=0
if you have jasmine flash persist in both slots
Thanks, i have jasmine. Let me use your files and revert.
Hello,
Sorry took a little longer.
I tried again with the process you suggested.
I used two different recoveries after flashing stock.
1. TWRP 3.2.3 unofficial
2. Orange Fox Recovery
I was successfully able to flash Persist using Orange Fox Recovery but it didn't helped. I was still not able to switch to front camera.
I tried to download and flash another Pie Stock Rom, same thing was happening on that as well.
Now i don't understand how else i can fix this. I have tried different versions of stock, i tried different recovery to flash persist, still the same issue.
gamerboy_010 said:
Hello,
Sorry took a little longer.
I tried again with the process you suggested.
I used two different recoveries after flashing stock.
1. TWRP 3.2.3 unofficial
2. Orange Fox Recovery
I was successfully able to flash Persist using Orange Fox Recovery but it didn't helped. I was still not able to switch to front camera.
I tried to download and flash another Pie Stock Rom, same thing was happening on that as well.
Now i don't understand how else i can fix this. I have tried different versions of stock, i tried different recovery to flash persist, still the same issue.
Click to expand...
Click to collapse
flash stock rom but in edl mode , using Miflash. Use the cmd :
fastboot oem edl
_dont use custom rom
_dont flash in normal fastboot
the only way this problem could be happening is if you were trying modifications in vendor and when you flash a new rom it doesn't overwrite the changes because it is modifying only vendor ...flashing custom roms in recovery won't help , neither will stock in fastboot mode . Only edl mode .... furthermore directly after flashing stock ...flash persist ...that way you start 100% fresh ..if it still doesn't work it is hardware failure
but i can do nothing more for you unless you send videos or photos of you following the steps and the problem with the camera .
**if you know how try removing back and enter edl with testpoint ...flash ... disconnect cameras and reconnect them ... then start phone
***if you remember what you changed just change it back ( did you try modifications? , what did you do ?)
****copy vendor files for camera from friend
Thanks for your help. I managed to get out of this in a weird way.
Flashed Stock in EDL. Tried different different Pie version this time.
Unlocked BL and Critical. Flashed Persist, didn't helped though.
Flashed Derpfest Rom with Mystic kernal and suddenly it started working.
Thanks for the help.
gamerboy_010 said:
Thanks for your help. I managed to get out of this in a weird way.
Flashed Stock in EDL. Tried different different Pie version this time.
Unlocked BL and Critical. Flashed Persist, didn't helped though.
Flashed Derpfest Rom with Mystic kernal and suddenly it started working.
Thanks for the help.
Click to expand...
Click to collapse
no problem man glad you succeeded ... probably it worked but after flashing persist everything usually starts working Normally after a few reboots ..so probably by then it was when you flashed derp
gamerboy_010 said:
Thanks for your help. I managed to get out of this in a weird way.
Flashed Stock in EDL. Tried different different Pie version this time.
Unlocked BL and Critical. Flashed Persist, didn't helped though.
Flashed Derpfest Rom with Mystic kernal and suddenly it started working.
Thanks for the help.
Click to expand...
Click to collapse
today i experienced a funny situation ...i took the new stock update for wayne and then i had the same camera problem ..
after thinking a little i realised it was after uodate so i had to just reapply the api2 for camera and then it started working normally so in future before going the long way make sure to enable api2 again after you update or flash a new thing . if camera works great if not take the long way...
I rooted my phone but didn't really like it while having my banking apps on it. So I tried to get back to normal but ended up wiping everything, even the OS, off of my phone. I am trying to get it back to normal. I followed one guide on here which gave me an android 10 ROM but I was unable to update it to the latest version. The link for that guide is: https://forum.xda-developers.com/mi-a2/how-to/guide-official-stock-android-10-t4033835. I didn't install the force encrypt or the magisk because I don't wanna root it. I just want it back to how it was before the root. So I am wondering if there is a way that I can get back to normal now. Thanks in advance for any advice.
Tyche303 said:
I rooted my phone but didn't really like it while having my banking apps on it. So I tried to get back to normal but ended up wiping everything, even the OS, off of my phone. I am trying to get it back to normal. I followed one guide on here which gave me an android 10 ROM but I was unable to update it to the latest version. The link for that guide is: https://forum.xda-developers.com/mi-a2/how-to/guide-official-stock-android-10-t4033835. I didn't install the force encrypt or the magisk because I don't wanna root it. I just want it back to how it was before the root. So I am wondering if there is a way that I can get back to normal now. Thanks in advance for any advice.
Click to expand...
Click to collapse
well what is the problem ? if it booted and you didn't flash magisk you are on stock. ...what exactly do you want ? to lock the bootloader or remove twrp custom recovery too ?
KevMetal said:
well what is the problem ? if it booted and you didn't flash magisk you are on stock. ...what exactly do you want ? to lock the bootloader or remove twrp custom recovery too ?
Click to expand...
Click to collapse
The ROM was an earlier version of android 10. But I am unable to install the latest updates for android 10 OTA. It's working but I would like to be able to receive updates again. If there is another ROM that would give me those results I would be fine with flashing that too.
Tyche303 said:
The ROM was an earlier version of android 10. But I am unable to install the latest updates for android 10 OTA. It's working but I would like to be able to receive updates again. If there is another ROM that would give me those results I would be fine with flashing that too.
Click to expand...
Click to collapse
the most likely issue is your recovery ... take the stock recovery from a fastboot stock rom and flash that with fastboot
also make sure to flash stock rom in both slot A & B then updates will work
go to this website
https://www.getdroidtips.com/xiaomi-mi-a2-stock-firmware/
download a PIE stock rom that is a FASTBOOT version ... download miflash ...follow instructions to flash it using miflash in fastboot mode
then boot & set it up ...it will start offering updates by itself
your problem right now is that you flashed stock rom in only one slot and you have a custom recovery so that is why it can't update
KevMetal said:
the most likely issue is your recovery ... take the stock recovery from a fastboot stock rom and flash that with fastboot
also make sure to flash stock rom in both slot A & B then updates will work
go to this website
https://www.getdroidtips.com/xiaomi-mi-a2-stock-firmware/
download a PIE stock rom that is a FASTBOOT version ... download miflash ...follow instructions to flash it using miflash in fastboot mode
then boot & set it up ...it will start offering updates by itself
your problem right now is that you flashed stock rom in only one slot and you have a custom recovery so that is why it can't update
Click to expand...
Click to collapse
Awesome, thanks! I will try that later tonight or tomorrow.
KevMetal said:
the most likely issue is your recovery ... take the stock recovery from a fastboot stock rom and flash that with fastboot
also make sure to flash stock rom in both slot A & B then updates will work
go to this website
https://www.getdroidtips.com/xiaomi-mi-a2-stock-firmware/
download a PIE stock rom that is a FASTBOOT version ... download miflash ...follow instructions to flash it using miflash in fastboot mode
then boot & set it up ...it will start offering updates by itself
your problem right now is that you flashed stock rom in only one slot and you have a custom recovery so that is why it can't update
Click to expand...
Click to collapse
So I downloaded a fastboot file from here :https://forum.xda-developers.com/mi-a2/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824849
The miui flash program wouldn't work for me. On the website you linked me there was a method that used twrp to flash it. But when use twrp I can't see any of the zip files in twrp. I've tried three different ones from the link I just shared here. Not sure what the problem is.
KevMetal said:
the most likely issue is your recovery ... take the stock recovery from a fastboot stock rom and flash that with fastboot
also make sure to flash stock rom in both slot A & B then updates will work
go to this website
https://www.getdroidtips.com/xiaomi-mi-a2-stock-firmware/
download a PIE stock rom that is a FASTBOOT version ... download miflash ...follow instructions to flash it using miflash in fastboot mode
then boot & set it up ...it will start offering updates by itself
your problem right now is that you flashed stock rom in only one slot and you have a custom recovery so that is why it can't update
Click to expand...
Click to collapse
nevermind, I have gotten it to work. Thank you for your help
Tyche303 said:
nevermind, I have gotten it to work. Thank you for your help
Click to expand...
Click to collapse
okay glad you came right
half the fun is figuring this stuff out
Not sure what I did but I am now stuck in a bootloop where it reboots every 10 seconds or so but I can't get into recovery or get to fastboot no matter how I press and hold the Power and up or down volume buttons? Is there any way out of this? I left the phone overnight and the battery wasted but as soon as I plugged it into the USB on my laptop again it went back to the bootloop.
So, just wondering is there a special sequence of buttons to press on the device, that I don't know of, when this happens?
Thanks
Did you flash anything?
Yes, I had switched from MIUI to PixelExperience (and I had unlocked the bootloader etc to do this) but I believe I did something wrong in the process and both my IMEI (which were still reported correctly) were not working - I thought this might be some firmware issue so I had flashed an update firmware but that did not help. So I went and flashed the Engineering ROM to see would that help resetting the device.
But that didn't help and I had lost TWRP so I refreshed TWRP and at that point it went into the bootloop. What I don't understand is why I can't get back to fastboot - I can understand maybe something went wrong with the version of TWRP I flashed (though I am pretty sure it was the same one I flashed originally when playing around with the PixelExperience ROM.
Anyway, just wondering if there was some other mechanism to trigger either the fast boot or some recovery as its like the boot loader fail to find anything appropriate to boot up from.
jeromeof said:
Yes, I had switched from MIUI to PixelExperience (and I had unlocked the bootloader etc to do this) but I believe I did something wrong in the process and both my IMEI (which were still reported correctly) were not working - I thought this might be some firmware issue so I had flashed an update firmware but that did not help. So I went and flashed the Engineering ROM to see would that help resetting the device.
But that didn't help and I had lost TWRP so I refreshed TWRP and at that point it went into the bootloop. What I don't understand is why I can't get back to fastboot - I can understand maybe something went wrong with the version of TWRP I flashed (though I am pretty sure it was the same one I flashed originally when playing around with the PixelExperience ROM.
Anyway, just wondering if there was some other mechanism to trigger either the fast boot or some recovery as its like the boot loader fail to find anything appropriate to boot up from.
Click to expand...
Click to collapse
Because you compromissed the boot process.
When your device try to boot, it make some checks first.
You need to flash the stock MIUI rom again.
VD171 said:
Because you compromissed the boot process.
When your device try to boot, it make some checks first.
You need to flash the stock MIUI rom again.
Click to expand...
Click to collapse
Yes, thanks, I imagine that is what happened but how can I flash when I can't get into recovery or get to into fastboot?
jeromeof said:
Yes, thanks, I imagine that is what happened but how can I flash when I can't get into recovery or get to into fastboot?
Click to expand...
Click to collapse
You need to flash the stock MIUI rom again using SPFLASHTOOL.
[GUIDE] How to properly solve the errors of the SP FLASH TOOL for MERLIN ? (Redmi Note 9 / Redmi 10X 4G)
WARNINGS: Keep your backup files safe and secure ! If you can, encrypt them. If you try to flash in "firmware upgrade" mode, bootloader will be LOCKED again ! Never try to flash in "format all" mode ! Otherwise, you will LOSE all secure and...
forum.xda-developers.com
jeromeof said:
Not sure what I did but I am now stuck in a bootloop where it reboots every 10 seconds or so but I can't get into recovery or get to fastboot no matter how I press and hold the Power and up or down volume buttons? Is there any way out of this? I left the phone overnight and the battery wasted but as soon as I plugged it into the USB on my laptop again it went back to the bootloop.
So, just wondering is there a special sequence of buttons to press on the device, that I don't know of, when this happens?
Thanks
Click to expand...
Click to collapse
If you have have adb drivers installed in your pc, try connecting your phone and open power shell. Then try this command.
Code:
adb devices
If it shows the device, then simply command
Code:
adb reboot fastboot
and flash the fastboot rom.
If not works, then follow VD171.
Also you should read threads carefully before flashing anything. Like there a tread about pixelplus UI. And they recommend to force reboot when you see the boot logo. To avoid boot loop.
Good luck
jeromeof said:
Yes, I had switched from MIUI to PixelExperience (and I had unlocked the bootloader etc to do this) but I believe I did something wrong in the process and both my IMEI (which were still reported correctly) were not working - I thought this might be some firmware issue so I had flashed an update firmware but that did not help. So I went and flashed the Engineering ROM to see would that help resetting the device.
But that didn't help and I had lost TWRP so I refreshed TWRP and at that point it went into the bootloop. What I don't understand is why I can't get back to fastboot - I can understand maybe something went wrong with the version of TWRP I flashed (though I am pretty sure it was the same one I flashed originally when playing around with the PixelExperience ROM.
Anyway, just wondering if there was some other mechanism to trigger either the fast boot or some recovery as its like the boot loader fail to find anything appropriate to boot up from.
Click to expand...
Click to collapse
Don't flash pixel experience. It's unofficial and it's and old version. I recommend you to flash pixel extended after solving and flashing latest fastboot rom. It's official and provide update every month. This rom is also a pure aosp based Stock rom.
Always read new treads before deciding
Redmi Note 9 ROMs, Kernels, Recoveries, & Other De
Improve your Redmi Note 9's battery life, performance, and look by rooting it and installing a custom ROM, kernel, and more.
forum.xda-developers.com
jeromeof said:
Yes, I had switched from MIUI to PixelExperience (and I had unlocked the bootloader etc to do this) but I believe I did something wrong in the process and both my IMEI (which were still reported correctly) were not working - I thought this might be some firmware issue so I had flashed an update firmware but that did not help. So I went and flashed the Engineering ROM to see would that help resetting the device.
But that didn't help and I had lost TWRP so I refreshed TWRP and at that point it went into the bootloop. What I don't understand is why I can't get back to fastboot - I can understand maybe something went wrong with the version of TWRP I flashed (though I am pretty sure it was the same one I flashed originally when playing around with the PixelExperience ROM.
Anyway, just wondering if there was some other mechanism to trigger either the fast boot or some recovery as its like the boot loader fail to find anything appropriate to boot up from.
Click to expand...
Click to collapse
Also, before doing any customization, you have to flash the Indonesian fastboot rom. Because almost every development is based on Indonesian rom.
Mobarok_ said:
Also, before doing any customization, you have to flash the Indonesian fastboot rom. Because almost every development is based on Indonesian rom.
Click to expand...
Click to collapse
Indonesia V12.0.1.0 precisely (V12.0.1.0.QJOIDXM).
Here, you can find and download the rom: https://xiaomifirmwareupdater.com/miui/merlin/stable/V12.0.1.0.QJOIDXM/