Develop Bugs

[Q] Sony Xperia ZL / root

I tried many times to root the phone, unfortunately i couldn't.
Special thanks to user destroyedbeauty, he adviced my ( in PM ) step by step how to do it, but still no success.I followed the steps very careful.
When i tried to root, i didn't check USB Debugging & Unknown Sources.
Should i ?
Is there a way to install apps which require root, on the phone with no root ?
Below are the steps i tried to root the phone, adviced by the mentioned user.
I rather recommend that you install an kernel with pre-configed root access (Doomkernel / Advanced Stock kernel / XzK-kernel) by using built-in Fastboot in Flashtool. By doing this method, do this!!!:
1) Download kernel ZIP from specific kernel thread in "Xperia Z (Original) Android Development" thread section. Take anyone of these below, I also link Advanced Stock Kernel if you want complete stock Sony kernel with added init.d / root / recovery add-on / built-in!;
a) Xz-Gaming v1.0
b) XzK-Kernel v11.0
c) Doomkernel v19
d) AdvancedStockkernel
OBS!! Choice latest kernel from list in each thread for getting latest kernel that is optimized and made for your installed FW. Otherwise, problems can occur..
2) Extract boot.img from downloaded ZIP and put boot-file in Flashtool > Firmwares. After this, copy the same zip to your phone external / internal-SD card. Leave it there and continue read..
3) Turn off your phone and hold volume up, then connect phone to USB-cable. Keep an eye on LED notify lamp, see if it blinking blue - then you're connected in fastboot mode between phone and PC!
4) Open up Flashtool and push on the "Bolt-Button". Select fastboot, then go to firmware subfolder in your Flashtool folder on HDD and select extracted boot.img. Read log in flashtool, read it carefully. If everything seems to be normal, disconnect your phone and boot it up.
5) Go into recovery mode by either hammering volume up / volume down button and then choice "Install ZIP" option. Search after your ZIP file in recovery that contains boot.img and wifi-specific modules (critical for getting working WIF / Bluetooth!!).
6) After completed flashing, wipe cache and Dalvik cache (Dalvik can be found under Advanced section in recovery).
7) Reboot and voilá! Enjoy your custom kernel!
I only tried with "AdvancedStockkernel"
After step 4, the display stays black, nothing happent, no boot, no Sony logo, nothing.
I want to mention one more think : when i unlocked the bootloader 2 days ago, i followed this link :
http://unlockbootloader.sonymobile.com/
It was successful.On the next step I was asked to write my email / imei / etc !!! Everything went ok.
After that, i tried to root and something went wrong, so i flashed whole .67 FTF in flashmode, again. Now is stock
Is the bootloader still unlocked, after i flashed .67 ftf in flashmode ? Could that be the reason i can't root the phone ?
Should i try again to unlock the bootloader, before i start again to root ?
Please help me guys.
Thank you

nex_t said:
I tried many times to root the phone, unfortunately i couldn't.
Special thanks to user destroyedbeauty, he adviced my ( in PM ) step by step how to do it, but still no success.I followed the steps very careful.
When i tried to root, i didn't check USB Debugging & Unknown Sources.
Should i ?
Is there a way to install apps which require root, on the phone with no root ?
Below are the steps i tried to root the phone, adviced by the mentioned user.
I rather recommend that you install an kernel with pre-configed root access (Doomkernel / Advanced Stock kernel / XzK-kernel) by using built-in Fastboot in Flashtool. By doing this method, do this!!!:
1) Download kernel ZIP from specific kernel thread in "Xperia Z (Original) Android Development" thread section. Take anyone of these below, I also link Advanced Stock Kernel if you want complete stock Sony kernel with added init.d / root / recovery add-on / built-in!;
a) Xz-Gaming v1.0
b) XzK-Kernel v11.0
c) Doomkernel v19
d) AdvancedStockkernel
OBS!! Choice latest kernel from list in each thread for getting latest kernel that is optimized and made for your installed FW. Otherwise, problems can occur..
2) Extract boot.img from downloaded ZIP and put boot-file in Flashtool > Firmwares. After this, copy the same zip to your phone external / internal-SD card. Leave it there and continue read..
3) Turn off your phone and hold volume up, then connect phone to USB-cable. Keep an eye on LED notify lamp, see if it blinking blue - then you're connected in fastboot mode between phone and PC!
4) Open up Flashtool and push on the "Bolt-Button". Select fastboot, then go to firmware subfolder in your Flashtool folder on HDD and select extracted boot.img. Read log in flashtool, read it carefully. If everything seems to be normal, disconnect your phone and boot it up.
5) Go into recovery mode by either hammering volume up / volume down button and then choice "Install ZIP" option. Search after your ZIP file in recovery that contains boot.img and wifi-specific modules (critical for getting working WIF / Bluetooth!!).
6) After completed flashing, wipe cache and Dalvik cache (Dalvik can be found under Advanced section in recovery).
7) Reboot and voilá! Enjoy your custom kernel!
I only tried with "AdvancedStockkernel"
After step 4, the display stays black, nothing happent, no boot, no Sony logo, nothing.
I want to mention one more think : when i unlocked the bootloader 2 days ago, i followed this link :
http://unlockbootloader.sonymobile.com/
It was successful.On the next step I was asked to write my email / imei / etc !!! Everything went ok.
After that, i tried to root and something went wrong, so i flashed whole .67 FTF in flashmode, again. Now is stock
Is the bootloader still unlocked, after i flashed .67 ftf in flashmode ? Could that be the reason i can't root the phone ?
Should i try again to unlock the bootloader, before i start again to root ?
Please help me guys.
Thank you
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=45974001 try this. For rooting you just need to check uknown sources and usb debugging mode
Sent from my C6502 using xda app-developers app

coolrevi said:
http://forum.xda-developers.com/showthread.php?p=45974001 try this. For rooting you just need to check uknown sources and usb debugging mode
Sent from my C6502 using xda app-developers app
Click to expand...
Click to collapse
Thanks a million, it was working. Now my phone is rooted, bootloader unlocked, and i want to install a CWM / TWRP custom recovery.
Would you please explain it to me how i have to proceed ?
Thank you.

nex_t said:
Thanks a million, it was working. Now my phone is rooted, bootloader unlocked, and i want to install a CWM / TWRP custom recovery.
Would you please explain it to me how i have to proceed ?
Thank you.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=40977606
Everything you need is in development section dude.. It's better to search instead of typing so much. Remember. just follow the procedure exactly..
Sent from my C6502 using xda app-developers app

Progress?

I saw this in facebook group "xperia t3 - india".. it seems we just need the camera to work

and 4G, and sdcard1...

vmlc said:
I saw this in facebook group "xperia t3 - india".. it seems we just need the camera to work
Click to expand...
Click to collapse
Hi i'm the guy how have cyanogen on my T3 , I just wanted to warn you for the rom, select the FXP-cm12-20150412...
And not the FXP-cm12.1 ...
otherwise your phone will bootloop, and when you make the first start of the phone , don't worry if after the bootanimation there's a black screen just wait 2-3 minutes for the update
So enjoy Cyanogen Xperia Users

fastbooking said:
Hi i'm the guy how have cyanogen on my T3 , I just wanted to warn you for the rom, select the FXP-cm12-20150412...
And not the FXP-cm12.1 ...
otherwise your phone will bootloop, and when you make the first start of the phone , don't worry if after the bootanimation there's a black screen just wait 2-3 minutes for the update
So enjoy Cyanogen Xperia Users
Click to expand...
Click to collapse
so, you confirm no 4g and camera working?

vmlc said:
so, you confirm no 4g and camera working?
Click to expand...
Click to collapse
yes no camera and 3G/4G

fastbooking said:
yes no camera and 3G/4G
Click to expand...
Click to collapse
also, you should do a detailed tutorial how to try the seagull build, i tried it the other day, but I couldnt do it....

vmlc said:
also, you should do a detailed tutorial how to try the seagull build, i tried it the other day, but I couldnt do it....
Click to expand...
Click to collapse
I will try tomorow there's a french tutorial about that here's the link for the one's who speak french
phonandroid.com/forum/post1800321.html (www . before its just because i can't now)

Cyanogen ROM are distributed in zip format, so you have to :
- push the zip file to your sdcard
- you need a kernel with recovery (for the time being, the Philz one)
- you enter in recovery mode
- you select "install zip" and the zip file.
once it's finished, install the right kernel
for that, on your PC, extract the boot.img file from the ROM zip file and flash it with flashtool or fastboot
reboot and enjoy

dan15 said:
Cyanogen ROM are distributed in zip format, so you have to :
- push the zip file to your sdcard
- you need a kernel with recovery (for the time being, the Philz one)
- you enter in recovery mode
- you select "install zip" and the zip file.
once it's finished, install the right kernel
for that, on your PC, extract the boot.img file from the ROM zip file and flash it with flashtool or fastboot
reboot and enjoy
Click to expand...
Click to collapse
ok, the part I dont get is: "once it's finished, install the right kernel
for that, on your PC, extract the boot.img file from the ROM zip file and flash it with flashtool or fastboot"
how do you do this?

dan15 said:
Cyanogen ROM are distributed in zip format, so you have to :
- push the zip file to your sdcard
- you need a kernel with recovery (for the time being, the Philz one)
- you enter in recovery mode
- you select "install zip" and the zip file.
once it's finished, install the right kernel
for that, on your PC, extract the boot.img file from the ROM zip file and flash it with flashtool or fastboot
reboot and enjoy
Click to expand...
Click to collapse
I don't install cyanogen like that,
First I update my phone with EMMA with the Open devices TA
-After I open the zip of the rom and i extract it somewhere you can find it
-take the zip AND THE GAPPS and connect your phone on usb for sending the zip on THE ROOT of your sdcard
-Enter in fastboot, and open flashtool (not emma the other)
-Flash the kernel called : boot.img
-Once Flashed reboot your phone in recovery (up button when the led is purple or violet)
-The led became gold color
- You now are (normaly) in cyanogen recovery
-Wipe data/Factory reset
-Wipe Cache for avoid bugs
-Now the fun part
-Apply update select the ROM and after the GAPPS
-Reboot and enjoy !
If the screen is black for a while after boot it's normal it's the system update
I also recommand you to take the
FXP-cm-12-20150412-UNOFFICIAL-seagull.zip
file because the other in cm12.1 are bootlooping
Now you can enjoy properly without camera and 3G/4G cyanogen
Sorry for my english I'm just a 14 french kid

btw, is this for 5102 or 5103? also, what do I have to be installed on my computer so I can flash boot for fastboot?

vmlc said:
btw, is this for 5102 or 5103? also, what do I have to be installed on my computer so I can flash boot for fastboot?
Click to expand...
Click to collapse
This is for D5103 the D5102 isn't the seagull this name is ONLY for the D5103
For the manipulation you will need emma (called flashtool by sony,for updating the bootloader)
And flashtool by Androxyde (this only is for flash kernel)
:highfive: now you're ready
Enjoy cyanogen on our t3 :laugh:

fastbooking said:
This is for D5103 the D5102 isn't the seagull this name is ONLY for the D5103
For the manipulation you will need emma (called flashtool by sony,for updating the bootloader)
And flashtool by Androxyde (this only is for flash kernel)
:highfive: now you're ready
Enjoy cyanogen on our t3 :laugh:
Click to expand...
Click to collapse
Im having problems flashing the kernel. I cant find my device in fastboot, and when I use flashtool to go ADB mode it says I dont have usb debugging on because I installed zip from recovery, the seagull file...

vmlc said:
Im having problems flashing the kernel. I cant find my device in fastboot, and when I use flashtool to go ADB mode it says I dont have usb debugging on because I installed zip from recovery, the seagull file...
Click to expand...
Click to collapse
Ok let's start off zero
you installed the zip via the philz recovery and after you wanted to flash the kernel ?

dan15 said:
Cyanogen ROM are distributed in zip format, so you have to :
- push the zip file to your sdcard
- you need a kernel with recovery (for the time being, the Philz one)
- you enter in recovery mode
- you select "install zip" and the zip file.
once it's finished, install the right kernel
for that, on your PC, extract the boot.img file from the ROM zip file and flash it with flashtool or fastboot
reboot and enjoy
Click to expand...
Click to collapse
thats what it says...

vmlc said:
thats what it says...
Click to expand...
Click to collapse
follow my tutorial it's the steps i followed and it works for me :good:

fastbooking said:
follow my tutorial it's the steps i followed and it works for me :good:
Click to expand...
Click to collapse
I got bricked meanwhile. Battery problem I think, not the first time...

ok, i think there is a missunderstanding.
in order to flash the kernel, you need to be in fastboot mode (with the blue light). so, once you have installed the zip file, shut down the phone (in recovery mode, select "power options/power off" , disconnect the phone and reconnect it in fastboot (maintain the vol up before and during the USB connection ).
you can now use "flashtool" (the Androxyde's one. to avoid confusion, the Sony's one is called EMMA or if it is more easy for you fastboot.exe
to use fastboot, you open a command line (Windows+R + type "cmd") , you go to the folder where the boot.img is and you enter the comand "fastboot flash boot boot.img". after ~2s the kernel is flashed, you can disconnect the phone and restart.
the first time, the boot time is about 5 min with a black screen after the animated screen, so wait a moment.
it's for that it's very important to have a well charged phone (min 40%) because the first start use a lot of battery, and you can't see anything.

I want to restore, I just installed the zip. Why cant I enter recovery?
edit: ok, I entered cyanogen recovery. will try to boot now. but I dont have backup/restore option....
edit2: ok, It booted but I still want to know how to back to previous version...

vmlc said:
I want to restore, I just installed the zip. Why cant I enter recovery?
edit: ok, I entered cyanogen recovery. will try to boot now. but I dont have backup/restore option....
edit2: ok, It booted but I still want to know how to back to previous version...
Click to expand...
Click to collapse
go on emma and select the android 4.4.4 update KK in the services line under open devices TA
It will restore the like the 1 st day but you will loose your data, but after you can install the philz recovery and restore the backup

install lineageOS -- failure on verification

Hey, I think I read all the threads that could be helpful (development, Q&A, lineageos & cm-installguides, twrp-install and so on), but I don't get my phone to work.
I have a Xperia M2 Dual c2005 and want to get LineageOS working. I have no data left that I would need, so I try to start from new...
Steps already taken:
- unlocked bootloader for both IMEIs https://zifnab.net/~zifnab/wiki_dump/Install_CM_for_nicki.html#What_does_.22unlocking.22_mean.3F --> worked
- flashed boot.img (extracted from lineage-14.1-20170131-nightly-nicki-signed.zip) in fastboot-mode and went to recovery
- wanted to copy zip to device, but adb (also with sudo!) says: unauthorized (Please check the confirmation dialog on your device. ... but there is none)
- in CM-recovery i tried to flash via sideload, but it stops transferring data at around 50% and saying: E: signature verification failed ... and E: error 21
- had the md5sum created and put it in folder, still the same
- also tried, what shouldn't be done fastboot flash boot twrp-3.0.2-0-nicki.img --> doesn't work b/c of FOTA, so how to install twrp?
Any ideas how to install clean lineageOS? Thanks in advance.

...usually this problem cause bad kernel or image .. so wipe format,data,cache,dalvik cache, make factory reset in cwm... boot again to recovery and flash TWRP 2.8.6.0 zip. file via recovery and reboot again to recovery .. now flash latest lineage os , without any extract
.. here is link for twrp..: https://forum.xda-developers.com/xp...very-cwm-twrp-recoveries-custom-roms-t3016507
..dont forget!! flash this 2.8.6.0 version ... if doesnt work this little guide, try to format sdcard via recovery in advanced option "this is partition where is everithyng set on 0 " ... and try again

Thanks a lot! For me it worked the following way, since I didn't have CWM present:
- downloaded TWRP 2.8.7.0 from the link you provided
- extracted FOTAKernel.img
- in fastboot mode: sudo fastboot flash boot FOTAKernel.img
- reboot in recovery (worked well!)
- adb push lineageos14.1.xxx.zip /sdcard/
- install and choose image
Thanks a lot, after a couple of days of trying I do now understand Sony a little more (for my own, I only use Nexus, which works quite simple ).

jeensg said:
Thanks a lot! For me it worked the following way, since I didn't have CWM present:
- downloaded TWRP 2.8.7.0 from the link you provided
- extracted FOTAKernel.img
- in fastboot mode: sudo fastboot flash boot FOTAKernel.img
- reboot in recovery (worked well!)
- adb push lineageos14.1.xxx.zip /sdcard/
- install and choose image
Thanks a lot, after a couple of days of trying I do now understand Sony a little more (for my own, I only use Nexus, which works quite simple ).
Click to expand...
Click to collapse
no problem, iam glad i could help

[D5503] Lollipop 5.1.1 goes AICP 13.1 Oreo 8.1 /// Beginners Link Collection

Hello hello,
this will be my "live" thread of bringing AICP 13.1 to my xperia z1c, I found some Guide's that I will follow and I will share with you all the links and knowledge I gained as a newbie that I used to understand and fix my problems on the way.
Maybe this will help you, too.
Main Tutorial: LINK
Target of all this: LINK
My Device:
Sony XPERIA Z1C, 14.6.A.1.236 , Lollipop 5.1.1
My best hint: read carefully, take your time to understand what you're trying to do and do your own research!
Hopefully you will get a aicp custom rom out of it.
_____________________________________________
_____________________________________________
General information: Android 5.1.1 cannot be rooted due to its high security standards, therefore we will downgrade to a lower security stock rom and create root access there. Root access will be needed as well as an unlocked bootloader to install real recovery (TWRP) which is the tool to flash custom roms like aicp. But the aicp custom rom will not have a good working camera, don't ask me why, but the camera seems to be a really difficult thing from the point of developer's view, let's accept this. Aside of that disadvantage, this custom rom is a very nice software and it makes my z1c kind of new. I don't use my camera anyway often at all.
During all this flashing thing I had a very big ??? while implementing real recovery. I was able to flash the .236.ftf but not the openbootloader.ftf as described in section 5 in the main tutorial. The result was twrp boot failed.
Error description:
flash .236.ftf works
flash openbootloader fails
flash twrp works
boot twrp fails
boot stock rom works
My solution:
I restarted from scratch and finally with the kind of messed up secquenceI got it:
flash .236.ftf works
flash openbootloader fails
flash twrp works
boot twrp fails
flash openbootloader works
flash twrp works
boot twrp works
UPDATE 06.12.2018 as a solution for REAL RECOVERY with working camera <<< RECOMMENDED
0. boot into rom works
1. flash openbootloader works
2. boot into rom works
3. flash .236.ftf works
4. boot into rom & check camera works
3. flash twrp ( business as usal ) works
4. boot twrp ( First boot is damn important, don't miss it! Press Vol- & Power, wait for vibration, release Power & keep Vol- until twrp boots up ) works
5. full wipe, flash aicp-rom, flash gapps, flash magisk-root, boot system works
6. enjoy Oreo 8.1 & camera check !!! works !!!
This routine worked straight forward for me where I started from scratch with my second device.
Flashing aicp was pretty easy, good to know for flashing the rom was full wipe = advanced wipe and select everything except of micro sd
To complete my aicp 13.1 Oreo 8.1 device the camera problem has to be fixed ( Saving the taken picture fails, display goes into freeze, no chance to solve this with camera mods, camera apps )
But @lm089 gave me the right hint, and finally this was my solution! Thanks again @lm089!!
Have fun with your new >> SONY XPERIA Z1 COMPACT <<
How to update TWRP
1. Turn Off your device
2. Start device in fastboot mode by connecting via usb cable to your pc and press Vol- until blue led tuns on
3. use fastboot flash recovery twrp.img to flash it
4. boot twrp ( This first boot is damn important, don't miss it! Press Vol- & Power, wait for vibration, release Power & keep Vol- until twrp boots up ) works
How to update to aicp 14.0 pie 9.0
starting with the running and latest aicp 13.1 oreo 8.1 rom above I just followed the Instructions here. As a specialty I had to install the Magisk Manager App manually into the rom to get root. Downloading supersu.apk from www.supersuroot.org works fine as well.
Your fastboot connection doesnt work for some reason though u had this workin fine in the past? maybe u had a windows update. install your drivers again.
>> LETS KEEP THIS DEVICE ALIVE <<
_____________________________________________
_____________________________________________
More helpful links that I used:
Debug apps by creating logs
what is adb? an xda tutorial
ADB working Download Link and ADB Article on xda
xda flashtool error during setup: click
[NOOBIE] Basic adb commands and device partition overview
Latest TWRP 3.2.3-0 for z1c
root solution using flash tool
Restore DRM functionality after UB
If TA Backup dry restoration restoration fails: Solution and Download *.dll
Boot into recovery or fastboot mode
How to install TWRP
Magisk beats superSU
How to Install Custom ROM using TWRP for Android!
change boot animations
[TUTORIAL] Design Your Own Bootanimation
Backup & Restore Your ROM With TWRP
Terminology: odex and deodex
If the camera goes into freeze or saving the picture fails: This was my solution! /// But you better go straight with the steps of my update 06.12.2018, field tested!
THANKS A LOT TO @colaigor for his [BEGINNERS GUIDE]

Ok. So i dont have much time now but i can give some short directions.
1. Get unlock codes from sony for bootloader unlock
2. Instal adb and fastboot at your system(PC)
3. Instal z1c drivers
4. Instal flashtool
5. Unlock bootloader,root,flash recovery(search forum for "real recovery" ),flash root solution
6. Flash wanted rom,gaps
P.P. On second thought u dont need flashtool. All can be done with adb and fastboot commands from terminal

There is one thing I don't understand:
what is the difference between FLASHING REAL RECOVERY and FLASHING FAKE RECOVERY?
What I read is, that in both cases I get TWRP but on different partitions (real = Recovery Partition, fake = Boot partition) but do I need both or do I choose just on of them?

derjango said:
There is one thing I don't understand:
what is the difference between FLASHING REAL RECOVERY and FLASHING FAKE RECOVERY?
What I read is, that in both cases I get TWRP but on different partitions (real = Recovery Partition, fake = Boot partition) but do I need both or do I choose just on of them?
Click to expand...
Click to collapse
Real recovery have its own partition(after that update to bootloader). Custom recovery dont have that and its stored somewhere else(FOTA,onetime boot image , etc). Choose real recovery. New stuff works good with it.

Ok thank you :good:

flashtool log of openbootloader.ftf failed:
01/015/2018 13:15:58 - INFO - Device connected in flash mode
01/017/2018 13:17:19 - INFO - Selected Bundle for Sony Xperia Z1 Compact(D5503). FW release : 1. Customization : openbootloader
01/017/2018 13:17:19 - INFO - Preparing files for flashing
01/017/2018 13:17:19 - INFO - Please connect your device into flashmode.
01/017/2018 13:17:19 - INFO - Using Gordon gate drivers version 3.1.0.0
01/017/2018 13:17:20 - INFO - Opening device for R/W
01/017/2018 13:17:20 - INFO - Device ready for R/W.
01/017/2018 13:17:20 - INFO - Reading device information
Click to expand...
Click to collapse
solved, I skipped step 5.2, flashing the .236.ftf in advance
but how can I start TWRP?
doesnt work with POWER + Vol-, vibrate & release power
I tried to flash the following recovery solution using this command:
smartphone in fastboot mode (blue LED enabled)
fastboot flash recovery recovery.img
TWRP from step 5.1 of the GUIDE
TWRP 3.0.2
My formerly flashed .236.ftf rom works fine, but I cant start TWRP the device goes directly to my rom

zlata said:
Real recovery have its own partition(after that update to bootloader). Custom recovery dont have that and its stored somewhere else(FOTA,onetime boot image , etc). Choose real recovery. New stuff works good with it.
Click to expand...
Click to collapse
Thats where I'm stuck right now, any ideas how to fix?

okay got it, basically i do not know what the problem is but:
after BLU
flash .236 :good:
flash openbootloader
flash twrp :good:
--> failed to install openbootloader and probably thus twrp failed
solution: I skipped to flash .236 as recommended by the author of the GUIDE (step 5.2)
flash open bootloader :good:
flash twrp :good:
--> failed to start twrp, though it was installed successfully
flash .236 :good:
flash openbootloader (failed again, but it's already on the device and I guess I could have skipped this here)
flash twrp :good:
first boot of twrp is successful :good:
And basically the author explained it in his text, FIRST INSTALL OPEN BOOTLOADER BEFORE WRITING STH TO RECOVERY PARTITION

I think you should use Aicp 14 pie instead of 13.1 Oreo
I feel Aicp 14 PIE is very stable and flash port camera stock this link https://forum.xda-developers.com/crossdevice-dev/sony-themes-apps/port-stock-camera-nougat-roms- t3628791

Nice thread, thank you! Wish I had that when I started rooting and flashing

@lm089 Haha it's quite some work to get into it, right? I just saw that we are running on the same device & custom rom, how did you solve the issue with the not working camera? I'm still reading stuff about some mod, but I'm curious and open for tested solutions on z1c
best, dj

derjango said:
how did you solve the issue with the not working camera? I'm still reading stuff about some mod, but I'm curious and open for tested solutions on z1c
best, dj
Click to expand...
Click to collapse
Had this situation twice with 2 different oreo ROMs. Both times I solved it following a rather strange sounding suggestion I found on the AICP 13.1 discussion thread. The basic idea is to go back to a stock Sony ROM. Boot into it and make sure the camera is working which for me was the case both times. Then - if necessary - re-root your phone (on first occasion I flashed a pre-rooted .236 version but that caused some extra trouble so next time I decided to flash an unrooted version). And from then on it's the standard way as you described it in your OP.
Good luck!

Okay, thanks a lot for your hint! Unfortunately the camera mod didn't fix the problem, my android-task for this evening is defined:
AICP 13.1 Oreo 8.1 on z1c, root, ulb, magisk 17.1
1. backup my system (done)
2.0 flash stock rom lollipop 5.1.1 (14.6.A.1.236.ftf) with flashtool via usb (done),booting the os for the first time takes quite long (~10m), check camera in the os (done)
interesting fact: recovery is deleted by flashing the rom via flashtool - I thought I can go the lazy way and skip the step of installing twrp again into recovery
2.1 okay, let's do it: install twrp (done) and boot into twrp, NOT into ROM!! (done) (Vol- & Power, wait for vibration & release Power but keep Vol- until TWRP starts up)
3. flash aicp 13.1 following this (full wipe as an advanced wipe: select all EXCLUDING THE SD STORAGE)
Again here, I recognized the first boot of the rom takes quite longer.
4. check camera (done)
!!!! IT WORKS !!!!
(I did it two times)

alright, lets start flashing my second device - now I know how to do it
Thanks guys!!

derjango said:
!!!! IT WORKS !!!![/SIZE]
Click to expand...
Click to collapse
Weird, isn't it?

lm089 said:
Weird, isn't it?
Click to expand...
Click to collapse
Totally But hey, it's a solution
btw @lm089, boots your ota-updater directly into twrp and start the flashing procedure? In my case I had to boot twrp manually and flash the zip manually, too

derjango said:
btw @lm089, boots your ota-updater directly into twrp and start the flashing procedure? In my case I had to boot twrp manually and flash the zip manually, too
Click to expand...
Click to collapse
No, updater is booting into recovery, doing a nandroid backup and wiping caches (because I told it to), then flashing and finally rebooting into system. All by itself :good:
I remember having trouble with that in the past though. Do you by any chance have an SD card formatted as adoptable storage?

lm089 said:
No, updater is booting into recovery, doing a nandroid backup and wiping caches (because I told it to), then flashing and finally rebooting into system. All by itself :good:
I remember having trouble with that in the past though. Do you by any chance have an SD card formatted as adoptable storage?
Click to expand...
Click to collapse
Yes, its used as an external storage

derjango said:
Yes, its used as an external storage
Click to expand...
Click to collapse
ok, that's something different; adoptable storage means that your SD or part of it is setup to extend internal storage. If you can access all of your SD from TWRP then it is indeed formatted a external storage.

1) How to unlock bootloader:
https://developer.sony.com/develop/...ed/unlock-bootloader/how-to-unlock-bootloader
2) Download Platform-tools (adb & fastboot) r.26.0.2 as latests version does not work (or just for me):
https://xiaomifirmware.com/downloads/download-platform-tools-adb-fastboot-r-26-0-0/
3) Download TWRP 3.2.3-0 https://androidfilehost.com/?fid=11410963190603854057 and place file in Platform Tools folder on PC
4) Restart in fastboot mode and flash revovery:
fastboot flash recovery Z1C_twrp_3.2.3-0.img
fastboot reboot
5.1) Download AICP Oreo 8.1 http://dwnld.aicp-rom.com/device/amami/WEEKLY/aicp_amami_o-13.1-WEEKLY-20181204.zip and place file in Platform Tools folder on PC
5.2) Download Gapps Pico https://opengapps.org/?download=false&arch=arm&api=8.1&variant=pico and place file in Platform Tools folder on PC
5.3) Download stable Magisk 17.1 https://github.com/topjohnwu/Magisk/releases/download/v17.1/Magisk-v17.1.zip place file in Platform Tools folder on PC
6.1) Load TWRP. Advance>ADB Sideload (for Oreo)
adb sideload aicp_amami_o-13.1-WEEKLY-20181204.zip
(do not restart)
6.2) Repeat Advance>ADB Sideload (for Gapps)
adb sideload open_gapps-arm-8.1-pico-2018XXXX.zip
(do not restart)
6.3) Repeat Advance>ADB Sideload (for Magisk)
adb sideload Magisk-v17.1.zip
(restart)

Question Find Device storage corrupted. Your device is unsafe now.( POCO F3 and Other MIUI Devices)

Last night I do have a problem with the custom rom that I have installed, because of the battery problem keeps on dropping, so I decided to go back to the official stock rom which is for global however after flashing the fastboot rom via Miflash Tool, I have a welcome message that says Find Device storage corrupted. Your device is unsafe now. I thought that I just need to activate this to the device admin, after a reboot I tried to check it out if this message if this message will still pop up, and it keeps on popping up. I have flashed the rom again and it keeps on happening.
Things that I have Tried:
So I tried to check for other ways that I could get rid of this but this doesnt work on the terminal via TWRP. "
[GUIDE] How to fix "Find Device storage corrupted. Your device is unsafe now".
[GUIDE] How to fix "Find Device storage corrupted. Your device is unsafe now". How to fix "Find Device storage corrupted. Your device is unsafe now" ? (At your own risk... I'm not responsible for damage or brick) Required : - Be rooted and...
forum.xda-developers.com
".
The one that works:
Things that you needed:
1. Download Mi Flash Tool(https://www.xiaomiflash.com/)
2. Minimal ADB and Fastboot
3. 7zip or BreeZip
4. TWRP A12(
TWRP A12.rar
drive.google.com
) if you are using other MIUI and devices and want to check it this will work then just use your twrp that is recommended for your mui device.
5. Global Rom (https://xiaomifirmwareupdater.com/miui/alioth/stable/V12.5.6.0.RKHMIXM/)
warning: make sure that you are using the right rom for your device, my device that I am using is a global variant so I need to flash a global version, if you are using other MIUI device and want to check it out just download the miui that works for you must be on a later update of the rom if the latest current rom that you are working on right now didnt work.
Steps to follow.
1. Extract the Rom which you have downloaded using the 7zip or BreeZip, so for me I extracted the version 12.5.6.0 take note that this is not the latest rom but for this to work we need to be in a later update this rom is an android version 11.
2. after extracting the fastboot rom file type TGZ you will notice that the one that you extracted is on a TAR file type, and you need to extract the TAR file type for you to have the folder "alioth_global_images_V12.5.6.0.RKHMIXM_20220210.0000.00_11.0_global_62b4f5d6ca"
3. Using the Mi Flash Tool, just pick the clean all and start the flashing.
4. After flashing the rom set up the phone but do not update it.
5. On your extracted folder for the rom go to the folder that says images and look for 'persist" this is an img file. copy the persist img file and paste it on your Internal memory of your phone.
6. Turn off your phone and go to fastboot by pressing the volume down as well as the power button. You will notice that the fastboot logo is the older version since we are using an older rom.
7. Extract the TWRP A12 and you should have the disc recovery image of it, copy and paste it on your Minimal ADB and Fastboot folder and rename it "recovery".
8. While you are on the Minimal ADB Fastboot folder make sure that your phone is plug in to the usb port on your computer, click the cmd here on the Minimal ADB and Fastboot Folder and you should able to run the cmd.
9. run the following commands:
fastboot devices (then press the enter)
warning: make sure that the fastboot devices is able to see your device.
after seeing the device run this command:
fastboot boot recovery.img (then press enter)
the device should boot to the twrp if its on chinese look for settings and set it to english. we are not flashing the twrp we are just going to use it temporarily thats why we are only going to boot it to twrp recovery.
10. On your twrp, go to install, click the install image and look for your persist.img that we have copied earlier to your internal memory
you should find it on the sdcard folder. just flash and you will see that you have successfully flashed the persist image and then just reboot your phone.
After rebooting your phone you will notice that the "Find Device storage corrupted. Your device is unsafe now." will not prompt. Since I already have the current fastboot rom I have tried to flash the current fastboot rom and locked my device and fixed the problem permanently without any problem.

You wrote too much for something that could be written in a few sentences. And why would anyone downgrade an android or flash a clean fastboot ROM? (Android or MIUI version doesn't matter)
Summary guide:
1. Download the fastboot ROM from here and extract the "persist.img" image or dump the "persistbak" partition from your device and rename this file to "persist.img"
2. Put persist.img into your device's internal memory and go to TWRP
3. In TWRP, go to: Install> select install image> select file persist.img> select "Persist" partition
4. Restart the device, it should work fine

uvzen said:
You wrote too much for something that could be written in a few sentences. And why would anyone downgrade an android or flash a clean fastboot ROM? (Android or MIUI version doesn't matter)
Summary guide:
1. Download the fastboot ROM from here and extract the "persist.img" image or dump the "persistbak" partition from your device and rename this file to "persist.img"
2. Put persist.img into your device's internal memory and go to TWRP
3. In TWRP, go to: Install> select install image> select file persist.img> select "Persist" partition
4. Restart the device, it should work fine
Click to expand...
Click to collapse
Wrote it down for the newbies that doesnt know how to fix anyway thanks for the summary. I have to downgraded it because the latest current rom doesnt work give me "invalid sparse file format at header magic" error as I flash the persist.img file, via twrp.

mizuhored said:
Wrote it down for the newbies that doesnt know how to fix anyway thanks for the summary. I have to downgraded it because the latest current rom doesnt work give me "invalid sparse file format at header magic" error as I flash the persist.img file, via twrp.
Click to expand...
Click to collapse
If you are using TWRP from Nebrassy then use skkk TWRP or OrangeFox. Flashing persist should work fine on both recoveries (I did it myself recently).

uvzen said:
If you are using TWRP from Nebrassy then use skkk TWRP or OrangeFox. Flashing persist should work fine on both recoveries (I did it myself recently).
Click to expand...
Click to collapse
Thats great but this is the one that works for me anyways. At least we have found out the things that we needed in order for it to be fixed. Just sharing my ideas and how did I fixed the problem myself. Thanks for sharing of your ideas. Hoping that we could share our ideas to others as well. Been on a nightmare last night cant sleep because of this problem. Trying to figure out what to do since using the cmds via terminal on twrp doesnt work for me. Need to downgrade for me to fix it.

mizuhored said:
Thats great but this is the one that works for me anyways. At least we have found out the things that we needed in order for it to be fixed. Just sharing my ideas and how did I fixed the problem myself. Thanks for sharing of your ideas. Hoping that we could share our ideas to others as well. Been on a nightmare last night cant sleep because of this problem. Trying to figure out what to do since using the cmds via terminal on twrp doesnt work for me. Need to downgrade for me to fix it.
Click to expand...
Click to collapse
Could you please confirm if flashing persist.img doesn't mess up with sensor like fingerprint, l1, compass etc..? I have seen other forums talking about possibility of losing these in case perist is flashed from rom. I have this message for some time now, but all other sensors work fine, even l1 certification and saftynet. Thanks in advance.