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.
A while ago I installed lineage 14 on my p9 because my son who uses the phone did want to have an experience a little closer to aosp.
Today he wanted to go back to stock emui. I thought I use the dload method. But I couldn't enter the recovery. Every time I ended up back at twrp.
Then I installed magic rainbow 4. The installation went OK but not all apps where available. Camera etc not installed.
Again I tried to use de dload method but still the same issue.
The I tried to reinstall lineage 14. Because in magic rainbow I couldn't enter the the developers option to activate oem unlock or USB debugging.
I thought that the problem for dload was an frp lock. In bootloader there is everything unlocked. But I wanted to check it.
After reinstall of lineage I wanted to reboot but I always ended up in TWRP....
I seems that there wasn't a system installed?
Then I found a tutorial that said to wipe all partitions and manually flash boot.img and system.img
But the flashing failed of both img.
So now I have a phone with all wiped....
Anyone an idea about this?
curtricias said:
Hi.
A while ago I installed lineage 14 on my p9 because my son who uses the phone did want to have an experience a little closer to aosp.
Today he wanted to go back to stock emui. I thought I use the dload method. But I couldn't enter the recovery. Every time I ended up back at twrp.
Then I installed magic rainbow 4. The installation went OK but not all apps where available. Camera etc not installed.
Again I tried to use de dload method but still the same issue.
The I tried to reinstall lineage 14. Because in magic rainbow I couldn't enter the the developers option to activate oem unlock or USB debugging.
I thought that the problem for dload was an frp lock. In bootloader there is everything unlocked. But I wanted to check it.
After reinstall of lineage I wanted to reboot but I always ended up in TWRP....
I seems that there wasn't a system installed?
Then I found a tutorial that said to wipe all partitions and manually flash boot.img and system.img
But the flashing failed of both img.
So now I have a phone with all wiped....
Anyone an idea about this?
Click to expand...
Click to collapse
If you were installing MR v4, didn't you read also the OP post #3 about HWOTA method for going back to stock from custom Nougat ROMs
https://forum.xda-developers.com/showpost.php?p=75787156&postcount=3
zgfg said:
If you were installing MR v4, didn't you read also the OP post #3 with HWOTA method for going back to stock from custom Nougat ROMs
https://forum.xda-developers.com/showpost.php?p=75787156&postcount=3
Click to expand...
Click to collapse
Forgot to mention. Yes. I tried that but software install failed.
curtricias said:
Forgot to mention. Yes. I tried that but software install failed.
Click to expand...
Click to collapse
You had to use the proper TWRP (from MR v4 thread) and flash by HWOTA the same stock you were before going to custom.
You can try HWOTA7
https://forum.xda-developers.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849
or even HuRUpdater
https://forum.xda-developers.com/ho...lash-official-firmware-recovery-t3769279/amp/
zgfg said:
You had to use the proper TWRP (from MR v4 thread) and flash by HWOTA the same stock you were before going to custom.
You can try HWOTA7
https://forum.xda-developers.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849
Already tried this to. Script ended with more than one device emulator.
or even HuRUpdater
https://forum.xda-developers.com/ho...lash-official-firmware-recovery-t3769279/amp/
Click to expand...
Click to collapse
And tried this also. Software installation failed.
I tried to install magic rainbow 4 again and it worked!
First I flashed TWRP from the MR4 topic.
But...
still various apps are missing. When I want to enter developer settings I automatically go back to home screen.
What can I do from there.
@Tecalote I'm gonna quote you here. Maybe you have an idea?
FYI
I managed to solve the problem!
Started over again.
In TWRP full wiped.
Tried HuRUpdater again. Flashed successfully the latest stock EMUi (C432-B505).
Factory reset in stock recovery.
Complete setup.
Rooted with latest Magisk (patched boot.img)
3T
Root, with last twrp, with a pie custom rom, Havoc Pie.
Everything normal, then, my wifi option was not switching on.
I tried do flash another rom's, many, same issue. Then I tried to flash stock and don't boot.
Tried the metod of unbrick and a android marshmallow version of stock boot. Tried install a new stock, and bootloop. Tried flash with ADS sideload and bootloop,
nor the white ball is spinning, only a red dot of the logo.
I can flash other rom's, my mac address was 02: 00: 00: 00: 00: 00. Maybe that's why the wi-fi does not activate anymore. And install the stock to see if it returns to normal, does not start, happening what I described
Michael R said:
3T
Root, with last twrp, with a pie custom rom, Havoc Pie.
Everything normal, then, my wifi option was not switching on.
I tried do flash another rom's, many, same issue. Then I tried to flash stock and don't boot.
Tried the metod of unbrick and a android marshmallow version of stock boot. Tried install a new stock, and bootloop. Tried flash with ADS sideload and bootloop,
nor the white ball is spinning, only a red dot of the logo.
I can flash other rom's, my mac address was 02: 00: 00: 00: 00: 00. Maybe that's why the wi-fi does not activate anymore. And install the stock to see if it returns to normal, does not start, happening what I described
Click to expand...
Click to collapse
Hello, when you have twrp installed, everything is ok. don´t panic.
You have Havoc Pie on the phone, right? Good, when you want to install sstock Rom, you "downgrade" the phone now.
Here we go: go to twrp, make a factory reset, wipe everything, then install the stock rom and make a clean install - done.
Good luck, reinipic:fingers-crossed:
reinipic said:
Hello, when you have twrp installed, everything is ok. don´t panic.
You have Havoc Pie on the phone, right? Good, when you want to install sstock Rom, you "downgrade" the phone now.
Here we go: go to twrp, make a factory reset, wipe everything, then install the stock rom and make a clean install - done.
Good luck, reinipic:fingers-crossed:
Click to expand...
Click to collapse
I can install any rom except the stock. And this problem is occurring since wi-fi no longer activates, and I realized that the MAC address was also modified (not by me)
I already tried to install the Stock, the Beta, already tried with TWRP and the ADB. After the flash, recovery hangs, goes pro boot and it does not start. Get bugged on OnePlus's red ball.
With other rom's the boot is normal. Using the unbrick process, the Marshmallow stock who comes in the package installs, until it starts normal. But when you try to install the most current stock, it will not start. And I'm using the most current blu_spark twrp.
Another strange thing is that even installing, even partially, passing the latest firmware, Wi-Fi does not activate at all.
Michael R said:
I can install any rom except the stock. And this problem is occurring since wi-fi no longer activates, and I realized that the MAC address was also modified (not by me)
I already tried to install the Stock, the Beta, already tried with TWRP and the ADB. After the flash, recovery hangs, goes pro boot and it does not start. Get bugged on OnePlus's red ball.
With other rom's the boot is normal. Using the unbrick process, the Marshmallow stock who comes in the package installs, until it starts normal. But when you try to install the most current stock, it will not start. And I'm using the most current blu_spark twrp.
Another strange thing is that even installing, even partially, passing the latest firmware, Wi-Fi does not activate at all.
Click to expand...
Click to collapse
Try using newest official twrp for our device from here: https://eu.dl.twrp.me/oneplus3/
It could help perhaps. I just did today unbrick process and after flashing MM stock you need to start it, and allow OEM unlock from developer settings, and then unlock bootloader (this is a must because the process of unbricking lock the BL), flash twrp from link, and finally flash stock rom (I flashed this one: https://forum.xda-developers.com/oneplus-3t/development/rom-theone3tos-v1-0-t3730932 and it works fine).
Try it and report
-CRO-Maher said:
Try using newest official twrp for our device from here: https://eu.dl.twrp.me/oneplus3/
It could help perhaps. I just did today unbrick process and after flashing MM stock you need to start it, and allow OEM unlock from developer settings, and then unlock bootloader (this is a must because the process of unbricking lock the BL), flash twrp from link, and finally flash stock rom (I flashed this one: https://forum.xda-developers.com/oneplus-3t/development/rom-theone3tos-v1-0-t3730932 and it works fine).
Try it and report
Click to expand...
Click to collapse
I'll try follow this steps. Thank you for the link. Soon I'll report.
Michael R said:
3T
Root, with last twrp, with a pie custom rom, Havoc Pie.
Everything normal, then, my wifi option was not switching on.
I tried do flash another rom's, many, same issue. Then I tried to flash stock and don't boot.
Tried the metod of unbrick and a android marshmallow version of stock boot. Tried install a new stock, and bootloop. Tried flash with ADS sideload and bootloop,
nor the white ball is spinning, only a red dot of the logo.
I can flash other rom's, my mac address was 02: 00: 00: 00: 00: 00. Maybe that's why the wi-fi does not activate anymore. And install the stock to see if it returns to normal, does not start, happening what I described
Click to expand...
Click to collapse
wen u switch wifi toggle you will get sometime that mac id i.e 02: 00: 00: 00: 00: 00. , after toggle wifi switch u get desired mac address.
uttam.ace said:
wen u switch wifi toggle you will get sometime that mac id i.e 02: 00: 00: 00: 00: 00. , after toggle wifi switch u get desired mac address.
Click to expand...
Click to collapse
The wifi does not even activate. Automatically, the switch pulls off
-CRO-Maher said:
Try using newest official twrp for our device from here: https://eu.dl.twrp.me/oneplus3/
It could help perhaps. I just did today unbrick process and after flashing MM stock you need to start it, and allow OEM unlock from developer settings, and then unlock bootloader (this is a must because the process of unbricking lock the BL), flash twrp from link, and finally flash stock rom (I flashed this one: https://forum.xda-developers.com/oneplus-3t/development/rom-theone3tos-v1-0-t3730932 and it works fine).
Try it and report
Click to expand...
Click to collapse
I tried, I followed step by step. When I installed the rom in the twrp, the phone vibrated for almost 5 seconds without stopping and nothing else after that.
Michael R said:
I tried, I followed step by step. When I installed the rom in the twrp, the phone vibrated for almost 5 seconds without stopping and nothing else after that.
Click to expand...
Click to collapse
Did you update your OxygenOS to the latest version? I updated my firmware cause I got error 7 from TWRP. If you're TWRP is the latest version: https://dl.twrp.me/oneplus3/ then I would look at your firmware: https://www.oneplus.com/support/softwareupgrade/details?code=6
Once you download that, connect your phone to your PC with USB debugging enabled on your phone. Make sure you have ADB installed: https://www.xda-developers.com/install-adb-windows-macos-linux/
Then open a command prompt (type CMD in "Search Programs and Files") and type without quotes "adb sideload filename.whatever" where "filename.whatever" is the name and extension of the OxygenOS file. Then do the same command again with the ROM file. That's how I got my ROM on my phone after I had some problems with decryption.
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 2 weeks ago. While backing up and restoring Dem keys, I broke something I don't kno. Now every custom rom I install boots and gets stuck at Phone is starting and then reboots. Tried LOS 16, 17.1 and Pixel experience rom. But result is the same. Sony firmware boots perfectly, Twrp works, but custom roms don't.
Is it possible to wipe everything , all partitions and repair them using TWRP? I kno that option exists in Twrp and I have drm keys backed up. But woud that solve the problem I face with custom roms?
GOrMHATRe said:
But result is the same. Sony firmware boots perfectly, Twrp works, but custom roms don't.
Click to expand...
Click to collapse
Are you missing a step in the instructions, like flashing the boot.img for the roms you're trying to install?
GOrMHATRe said:
Is it possible to wipe everything , all partitions and repair them using TWRP? I kno that option exists in Twrp and I have drm keys backed up. But woud that solve the problem I face with custom roms?
Click to expand...
Click to collapse
To start over use the Flashtool, Newflasher, or even PC Companion. There is even Sony EMMA when something really messes up.
SXUsr said:
Are you missing a step in the instructions, like flashing the boot.img for the roms you're trying to install?
To start over use the Flashtool, Newflasher, or even PC Companion. There is even Sony EMMA when something really messes up.
Click to expand...
Click to collapse
Boot.img is part of rom zip file. With all 3 roms I tried, there was no instruction to flash boot separately. It's always flash recovery and then flash rom using recovery.
I have already use flashtool and newflasher. That's how I rooted my phone. Both of them are successful in flashing stock sony firmware. But the custom roms are in zip file. Don't kno of its possible to flash those using flashtool.
GOrMHATRe said:
Boot.img is part of rom zip file. With all 3 roms I tried, there was no instruction to flash boot separately. It's always flash recovery and then flash rom using recovery.
Click to expand...
Click to collapse
Steps :
Remove your screen lock (set it to swipe up or none) and remove all your fingerprints registered.
Download the zip above and extract the boot, system and vendor images
Make sure you have Android 10 TWRP as mentioned above with link
Go to recovery > wipe and wipe system, cache and data nothing else.
Then go to install and flash boot.img as boot image, system.img as system image and vendor.img as vendor image.
Click to expand...
Click to collapse
- [ROM] Pixel Experience 10.0 Plus
Always extract the boot.img and flash it with fastboot. If there is no instructions then still do it.
SXUsr said:
- [ROM] Pixel Experience 10.0 Plus
Always extract the boot.img and flash it with fastboot. If there is no instructions then still do it.
Click to expand...
Click to collapse
Latest file of PE rom is in zip format. Boot.img is in zip . But vendor and system are not img files.
GOrMHATRe said:
Latest file of PE rom is in zip format. Boot.img is in zip . But vendor and system are not img files.
Click to expand...
Click to collapse
Then extract the boot.img and flash it using fastboot, along with TWRP, then flash the rom. That should work flashing any custom rom.
SXUsr said:
Then extract the boot.img and flash it using fastboot, along with TWRP, then flash the rom. That should work flashing any custom rom.
Click to expand...
Click to collapse
I tried this but the result was same. Rom boots upto the lock screen. Then when I swipe it shows: phone is starting and goes into bootloop. I even tried an older version of PE Rom whic contain s only img files but again same result.
You kno initially, after I unlocked the bootloader I just installed stock rom and installed LOS on top of it as per guide. It worked well. I coud go into menu and see apps.
But I panicked that I had forgotten to restore drm keys. Instead of first checking camera, I went back and restored the Ta partition and repeated the steps after it upto installation of rom and since then I have faced problems . Restoring ta partition and flashing stock rom after it is where I have made a mistake and broken something. Can this be fixed with twrp. I kno there are options in twrp to format & repair partitions. Coud that help to repair what ever that was broken?
GOrMHATRe said:
Coud that help to repair what ever that was broken?
Click to expand...
Click to collapse
No more than the Flashtool, Newflasher or PC Companion, so I wouldn't even consider using TWRP. Check your service menu for the status of your DRM keys, flashing them is a one time process so if they have been successfully restored there is no need to flash them again.
Use Sonys Flashtool to repair, and start over. If you're still having issues, then user error is at play here. What command in fastboot did you use to flash the kernel?
SXUsr said:
No more than the Flashtool, Newflasher or PC Companion, so I wouldn't even consider using TWRP. Check your service menu for the status of your DRM keys, flashing them is a one time process so if they have been successfully restored there is no need to flash them again.
Use Sonys Flashtool to repair, and start over. If you're still having issues, then user error is at play here. What command in fastboot did you use to flash the kernel?
Click to expand...
Click to collapse
Which kernel are you speaking about? I had backed up Ta image using renoroot exploit and restored it using:
adb pull /data/local//tmp/TA-unlocked.img
adb push TA-locked.img /data/local/tmp
Then in window with temp root prompt:
cd /data/local/tmp
de if=TA-locked.img of=/dev/block/bootdevice/by-name/TA
sync
sync
Reboot phone
But actually, when I checked my phone just now and that tmp directory seems empty. So, does that mean TA didn't get restored properly? Is that why I am facing problems? Stock roms seem to be working fine.
As for sony's own flashtool, I have it installed. But thought it doesn't offer any different functionality than newflasher or old flashtool? Woud sony flashtool help me go back to square 1 and make my phone as it was before rooting so that I can do everything again properly?
GOrMHATRe said:
Which kernel are you speaking about?
Click to expand...
Click to collapse
The kernel of the rom. Check your service menu for drm status.
SXUsr said:
The kernel of the rom. Check your service menu for drm status.
Click to expand...
Click to collapse
The keys are there. The rooting status is shown not done because I have used that hide root unlock patch after going back to stock rom.
GOrMHATRe said:
The keys are there. The rooting status is shown not done because I have used that hide root unlock patch after going back to stock rom.
Click to expand...
Click to collapse
So, now forget your drm keys for a minute, and do the following.
1. Use Sonys flashtool to reset your phone. Make sure you've backed up what you need to.
2. Using fastboot, flash both the kernel of whatever rom you wish to use, and TWRP.
3. Following the instructions of the rom you want to flash, install the rom using twrp. You may want to read them first to ensure you're using the required stock firmware that you will be flashing over.
Have you tried NOT restoring TA partition? It isn't needed with custom ROMs (as far as I know).
SXUsr said:
So, now forget your drm keys for a minute, and do the following.
1. Use Sonys flashtool to reset your phone. Make sure you've backed up what you need to.
2. Using fastboot, flash both the kernel of whatever rom you wish to use, and TWRP.
3. Following the instructions of the rom you want to flash, install the rom using twrp. You may want to read them first to ensure you're using the required stock firmware that you will be flashing over.
Click to expand...
Click to collapse
I will try this but after some time. I have experimented on my phone a lot in recently. Need it to be stable for work for some time now. My secondary phone is not setup to work with gmail etc. Thanks for all the advice you have provided though.
On another note, now that Android 11 is out, do you think we will get a rom based on it for Xz1 compact? I even had a thought of skipping 10 and going for 11 based rom.
thefelineofaveb said:
Have you tried NOT restoring TA partition? It isn't needed with custom ROMs (as far as I know).
Click to expand...
Click to collapse
I have not touched drm keys after I backed up and restored them for the 1st time.