Related
I got my phone a few days ago and rooted it, installed most stuff etc.. So far I have TWRP and Magisk 14.0 Root active on it, not much else I can think of. The phone is running Android 7.0.
I left the Camera for last to check and when I did I noticed neither the camera nor its flash are responding. ("camera busy" error, other full-fledged cam apps showing black) I went through the initial steps of disabling OK Google's camera settings, disabling a bunch of apps that had cam access, checking safe mode etc. and none of them worked.
Finally I went into Device Helper's hardware list and noticed under "Imaging" there isn't even a camera listed. I don't know how the app works but even with cam busy it would at least be listed. I went through a few other hardware spec listing apps and all of them showed absolutely no camera hardware. Interesting enough, I know the phone has 2 cameras, I'm not sure if they're a single unified piece of hardware or not but there was no such thing as back or front camera even, there was quite simply nothing listed under camera.
At this point I'm left to wonder if the problem is either a setting or something to do with rooting, or actual hardware fault. Unfortunately having rooted the device, I also have no warranty for it.
I welcome any ideas, advices, anything about trying to detect or diagnose camera issues. If there were a TWRP way of checking the camera hardware, I'd be glad to try it out since it would rule out anything having related to the Android OS, or other versions of Magisk. 11.6 was recommended but it never worked for me. This is all before I open up the phone. I can't much afford much to do a factory reset at this point and would like to leave it as the last resort.
In the event of a camera issue, I'm of course hoping it's as simple as a loose connector, but I'd like to know of any known G5 hardware issues with the camera and if there's documented fixes.
Also in the event I DO have to do a hard reset - do I have a reliable way of backing up absolutely everything about the phone's current state(apps settings documents etc.) and restoring it all back?
I just spent good money on this phone, thank you for all advice!
Are you using stock rom or a custom rom?
You can use magisk uninstaller to remove magisk to see if that caused an issue (see magisk v14.0 thread)
In some custom roms some people did report camera stopped working - Iv never had this issue
I'm using LineageOS with the built in superuser via the su add on zip
In terms of the camera itself hardware wise & on unmodified stock there are no reported issues
TheFixItMan said:
Are you using stock rom or a custom rom?
You can use magisk uninstaller to remove magisk to see if that caused an issue (see magisk v14.0 thread)
In some custom roms some people did report camera stopped working - Iv never had this issue
I'm using LineageOS with the built in superuser via the su add on zip
In terms of the camera itself hardware wise & on unmodified stock there are no reported issues
Click to expand...
Click to collapse
Not using a custom ROM.
I went to the Magisk page where I got the install, got "latest uninstaller", ran it. It reported success but warned that no boot image backup was found. On restart it hanged indefinetly at the 5-second untrusted device warning. Did a hard poweroff and on, same result. I ended up installing the 14.0 back and the device again boots. I also did a dump of the boot logs.
In dmesg.log I see this:
Code:
<3>[ 5.684036,2] msm_camera_pinctrl_init:1277 Getting pinctrl handle failed
Code:
<3>[ 5.676660,2] msm_flash_get_pmic_source_info:895 alternate current: read failed
<3>[ 5.676664,2] msm_flash_get_pmic_source_info:915 alternate max-current: read failed
<3>[ 5.676667,2] msm_flash_get_pmic_source_info:935 alternate duration: read failed
<3>[ 5.676710,2] msm_flash_get_pmic_source_info:895 alternate current: read failed
<3>[ 5.676714,2] msm_flash_get_pmic_source_info:915 alternate max-current: read failed
<3>[ 5.676717,2] msm_flash_get_pmic_source_info:935 alternate duration: read failed
<3>[ 5.676760,2] msm_flash_get_pmic_source_info:1005 alternate current: read failed
<3>[ 5.676763,2] msm_flash_get_pmic_source_info:1025 alternate current: read failed
<3>[ 5.676806,2] msm_flash_get_pmic_source_info:1005 alternate current: read failed
<3>[ 5.676810,2] msm_flash_get_pmic_source_info:1025 alternate current: read failed
and respectively this:
Code:
<3>[ 5.664800,0] msm_camera_get_dt_vreg_data:1115 number of entries is 0 or not present in dts
I'm no expert reading these logs, is this signalling my issue?
Also this is from the non-working boot, near the end of the log:
Code:
>[ 33.292450,5] FAT-fs (mmcblk1p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
SearinoxNavras said:
Not using a custom ROM.
I went to the Magisk page where I got the install, got "latest uninstaller", ran it. It reported success but warned that no boot image backup was found. On restart it hanged indefinetly at the 5-second untrusted device warning. Did a hard poweroff and on, same result. I ended up installing the 14.0 back and the device again boots. I also did a dump of the boot logs.
In dmesg.log I see this:
Code:
<3>[ 5.684036,2] msm_camera_pinctrl_init:1277 Getting pinctrl handle failed
Code:
<3>[ 5.676660,2] msm_flash_get_pmic_source_info:895 alternate current: read failed
<3>[ 5.676664,2] msm_flash_get_pmic_source_info:915 alternate max-current: read failed
<3>[ 5.676667,2] msm_flash_get_pmic_source_info:935 alternate duration: read failed
<3>[ 5.676710,2] msm_flash_get_pmic_source_info:895 alternate current: read failed
<3>[ 5.676714,2] msm_flash_get_pmic_source_info:915 alternate max-current: read failed
<3>[ 5.676717,2] msm_flash_get_pmic_source_info:935 alternate duration: read failed
<3>[ 5.676760,2] msm_flash_get_pmic_source_info:1005 alternate current: read failed
<3>[ 5.676763,2] msm_flash_get_pmic_source_info:1025 alternate current: read failed
<3>[ 5.676806,2] msm_flash_get_pmic_source_info:1005 alternate current: read failed
<3>[ 5.676810,2] msm_flash_get_pmic_source_info:1025 alternate current: read failed
and respectively this:
Code:
<3>[ 5.664800,0] msm_camera_get_dt_vreg_data:1115 number of entries is 0 or not present in dts
I'm no expert reading these logs, is this signalling my issue?
Also this is from the non-working boot, near the end of the log:
Code:
>[ 33.292450,5] FAT-fs (mmcblk1p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Click to expand...
Click to collapse
Here is the original stock boot.img if you need to flash it after removing magisk
Stock boot image
You need to put your phone in bootloader mode & connect to pc via usb
Open a command/terminal prompt at your fastboot location
Code:
fastboot flash boot boot.img
Substitute boot.img for the name of your boot.img if different but I think I named it boot.img
You may have to flash the entire stock firmware & start again or try flashing Linageos
You can also try erasing user data by typing
Code:
fastboot erase userdata
But note this will erase all data from phone including anything in internal storage like photos music downloads etc (only data partition not system so phone will boot as if new)
The boot.img you sent me and the one I have both have the same hashes. So I was at least doing that right.
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.518s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.739s]
finished. total time: 1.258s
Is "bad key" normal? Now the 5-second untlocked untrusted warning says ID: bad key instead of N/A. Sadly, the device behaves the same. It hangs indefinetly at that one screen. Maybe something's off with the uninstaller; if I wanted to manually -disable- magisk by renaming say one file or folder that is an entry point, how would I do that?
I checked the boot logs again, and I'm still seeing the same camera stuff mentioned there, so I don't know if it fixed anything since I can't boot but it doesn't look different.
I uploaded the files here: https://drive.google.com/file/d/0B5_lN_xRgoTVTUZZX0ZaWmZGNkE/view
Please tell me if there's anything there shouldn't be about the camera in them.
Once I reinstall Magisk, the ID at the boot splash warning goes back to N/A. Funny enough it -does- say it's found a stock boot image and it's backing it up when you install, but on uninstall it never finds it.
If I were to try a stock reflash or another fw, do I have a way to image absolutely everything and if I want, to restore it back as if it never changed?
I forgot to mention that when I installed TWRP I also installed no-verity-opt-encrypt-5.1.zip. Does this have anything to do with it?
SearinoxNavras said:
The boot.img you sent me and the one I have both have the same hashes. So I was at least doing that right.
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.518s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.739s]
finished. total time: 1.258s
Is "bad key" normal? Now the 5-second untlocked untrusted warning says ID: bad key instead of N/A. Sadly, the device behaves the same. It hangs indefinetly at that one screen. Maybe something's off with the uninstaller; if I wanted to manually -disable- magisk by renaming say one file or folder that is an entry point, how would I do that?
I checked the boot logs again, and I'm still seeing the same camera stuff mentioned there, so I don't know if it fixed anything since I can't boot but it doesn't look different.
I uploaded the files here: https://drive.google.com/file/d/0B5_lN_xRgoTVTUZZX0ZaWmZGNkE/view
Please tell me if there's anything there shouldn't be about the camera in them.
Once I reinstall Magisk, the ID at the boot splash warning goes back to N/A. Funny enough it -does- say it's found a stock boot image and it's backing it up when you install, but on uninstall it never finds it.
Click to expand...
Click to collapse
it always says image signed with bad key for me
you can try going into twrp
click advanced
file manager
data
select magisk.img (or something like that)
then delete it
Other than reflashing the entire firmware via fastboot theres not alot else I can suggest
I would erase userdata though if you are trying the uninstall magisk as it does modify the data partition and its best to erase it if you no longer use magisk - but as I mentioned before anything on internal storage will be lost so move it to sd card
But I dont know of anyone else who has used magisk and the camera stops working so I dont even know if thats the problem
Without testing it on a fresh stock rom you wont know
I flashed LineageOS and it's seeing my camera! I haven't yet flashed the google apps, mainly to see if the camera works in as minimal a clean slate as possible. Now with that out of the way, whatever other issues I may encounter I will solve or possibly ask in another thread, but at least this fixed the cam. Now off to the long road of installing stuff.
for me is the same, flashing stock again, update all to august patch, and the camera stop working, if i uninstall magisk the phone not starts, is stuck in the boot logo, after install magisk 14 again, the phone boting but no camera works
woozie.2007 said:
for me is the same, flashing stock again, update all to august patch, and the camera stop working, if i uninstall magisk the phone not starts, is stuck in the boot logo, after install magisk 14 again, the phone boting but no camera works
Click to expand...
Click to collapse
After uninstalling magisk try flashing the kernel for your rom via fastboot
i tried but the phone won't boot
---------- Post added at 05:13 PM ---------- Previous post was at 05:12 PM ----------
the phone started only if i flash system sparsechunk0, 1, 2, 3 and 4, without these flashed the phone not starting
i flashed again the stock firmware, initial is with patch from january, i made ota update to march(the camera still works with magisk 14), and then i updated ota to august....now camera works, but i installed magisk and patched the boot....bang, the camera stops. So i decided is problem with magisk after the august update, i haven't twrp, only flash it via fastboot. I dont know what can i tried to works camera with magisk ((
woozie.2007 said:
i flashed again the stock firmware, initial is with patch from january, i made ota update to march(the camera still works with magisk 14), and then i updated ota to august....now camera works, but i installed magisk and patched the boot....bang, the camera stops. So i decided is problem with magisk after the august update, i haven't twrp, only flash it via fastboot. I dont know what can i tried to works camera with magisk ((
Click to expand...
Click to collapse
Why do you want to use magisk - it doesn't work fully on this device - eg magisk hide & modules do not work
Much better using supersu (either via twrp zip or CF-Auto-Root) or the lineageos root addon
TheFixItMan said:
Why do you want to use magisk - it doesn't work fully on this device - eg magisk hide & modules do not work
Much better using supersu (either via twrp zip or CF-Auto-Root) or the lineageos root addon
Click to expand...
Click to collapse
because i want to update via ota, cf auto root i tried but not works, i want to use stock firmware not lineageos, i have 7.0. Can you tell me how to root moto g5 without modify system, to be able to update ota? Thanks
woozie.2007 said:
because i want to update via ota, cf auto root i tried but not works, i want to use stock firmware not lineageos, i have 7.0. Can you tell me how to root moto g5 without modify system, to be able to update ota? Thanks
Click to expand...
Click to collapse
Then use supersu and flashfire app
https://play.google.com/store/apps/details?id=eu.chainfire.flash
I'm working on CF-Auto-Root - server is down at the moment - once Iv created a working package I'll post it
how? i am on stock now, not twrp, i have full stock
woozie.2007 said:
how? i am on stock now, not twrp, i have full stock
Click to expand...
Click to collapse
Flash twrp root then flash stock recovery
Obviously I presume you have unlocked the bootloader
yes, of course i have
woozie.2007 said:
yes, of course i have
Click to expand...
Click to collapse
hello
he
lp me please i have the same problem: camerera falled
Marie74 said:
hello
he
lp me please i have the same problem: camerera falled
Click to expand...
Click to collapse
i fixed the problem with clean flash stock rom, then update ota then flash twrp and root again with latest version of magisk
camera
woozie.2007 said:
i fixed the problem with clean flash stock rom, then update ota then flash twrp and root again with latest version of magisk
Click to expand...
Click to collapse
thank you for awser give me the link please please please! god bless you!
DisclaimerThis software comes wth no warranty,XDA staff ,myself or TeamWin stuff can't be hold responsible for any damage it may cause to your device.
Note: Currently Oreo 8.1 custom roms are not supported,only stock EMUI 8.x .
Download and Installation
* Download twrp recovery
* Start your device in fastboot mode
* Install the recovery using the following command:
Code:
fastboot flash recovery_ramdisk [filename].img --> ex: fastboot flash recovery_ramdisk twrp_p10_lite_0.1.img
* Restart with this command:
Code:
fastboot reboot
* As soon as you execute the restart command,remove the USB cable and keep pressing Volume UP,so the device will boot to TWRP.This is to avoid that the device boot to OS,overwritting TWRP recovery.
Features
Internal storage decryption = working
MTP and OTG connection = working
Backup&Restore = working
Note: There are no sources for this yet,because is based on the work of @zxz0O0 ,from Honor 9.
Contributors
**** Pretoriano80
**** @zxz0O0 - This wouldn't be possible without this guy,so big big thank to him.I used his base to make this recovery work ,so in sign of respect his nick will also be on the TWRP boot screen.Thank again buddy!
**** TeamWin project ,obviously.
**** @Tecalote - He was the main tester for the Mate 9
**** @Blackball
**** @Eurofighter_ty for testing on P10 Lite
**** Team OpenKirin - thanks for the "Oem Path wipe esclusion" code
Download links
twrp_p10_lite_0.1.img - initial release,OTG connection not working
twrp_p10_lite_0.2.img - minor fixes,OTG connection should be fixed (please test and report)
twrp_p10_lite_0.3.img - OTG is now fixed
twrp_p10_lite_0.4.img - fixed mount issues
Why after entering into TWRP I got "Mount Decrypt Data" menu and ask me for some password? What is this?
Then I press Cancel because I don't know what is this menu.
Also I can't make any backups because I got an error: "Failed to unmount '/data' (device or resource busy)" and "Failed to unmount '/system' (device or resource busy)"
Something is wrong with this TWRP.
Aalesund said:
Why after entering into TWRP I got "Mount Decrypt Data" menu and ask me for some password? What is this?
Then I press Cancel because I don't know what is this menu.
Also I can't make any backups because I got an error: "Failed to unmount '/data' (device or resource busy)" and "Failed to unmount '/system' (device or resource busy)"
Something is wrong with this TWRP.
Click to expand...
Click to collapse
Obviously it's asking for password, otherwise it couldn't decrypt the internal storage.
You have to use the same password/pin/pattern that you use in Android.
The feature Internal Storage Decryption is really cool!
And this TWRP has better compatibility with magisk, at last I can use recovery mode for mm.
Thanks!
The problem of not being able to unmount /system means that it'll always be mount read-only, which then means unless a whole system image is flashed, no modifications can be made to /system. This is the only gripe I have about this TWRP; otherwise it works brilliantly.
AndyYan said:
The problem of not being able to unmount /system means that it'll always be mount read-only, which then means unless a whole system image is flashed, no modifications can be made to /system. This is the only gripe I have about this TWRP; otherwise it works brilliantly.
Click to expand...
Click to collapse
Yes, that's right - I saw the issue with keeping system ready only yesterday night on Huawei Mate 10 Lite.
This TWRP works except this also brilliantly on Mate 10 Lite
i tried to flash my emui 5 p10lite with no success:
#
Code:
fastboot flash recovery_ramdisk ./twrp_p10_lite_0.3.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (24952 KB)...
OKAY [ 3.186s]
writing 'recovery_ramdisk'...
FAILED (remote: partition length get error)
finished. total time: 3.194s
dlewando said:
i tried to flash my emui 5 p10lite with no success:
#
Code:
fastboot flash recovery_ramdisk ./twrp_p10_lite_0.3.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (24952 KB)...
OKAY [ 3.186s]
writing 'recovery_ramdisk'...
FAILED (remote: partition length get error)
finished. total time: 3.194s
Click to expand...
Click to collapse
It only works on EMUI 8.
Tecalote said:
Yes, that's right - I saw the issue with keeping system ready only yesterday night on Huawei Mate 10 Lite.
This TWRP works except this also brilliantly on Mate 10 Lite
Click to expand...
Click to collapse
Here's a test build,i hope that system unmount issue is fixed -- > https://mega.nz/#!AscFxY5R!UdDKb-FIlZI2rjJyCZiMu2er1-HnTWdKYJfGpAoGJdM
Pretoriano80 said:
Here's a test build,i hope that system unmount issue is fixed -- > https://mega.nz/#!AscFxY5R!UdDKb-FIlZI2rjJyCZiMu2er1-HnTWdKYJfGpAoGJdM
Click to expand...
Click to collapse
Same deal unfortunately. Device is a Honor 7X, btw.
AndyYan said:
Same deal unfortunately. Device is a Honor 7X, btw.
Click to expand...
Click to collapse
Well, my magic crystal ball is broken so i will need logs this time.Next time please grab recovery.log and dmesg, otherwise i will start ignoring all these "not working" posts.
Pretoriano80 said:
Well, my magic crystal ball is broken so i will need logs this time.Next time please grab recovery.log and dmesg, otherwise i will start ignoring all these "not working" posts.
Click to expand...
Click to collapse
Done.
I'd need to know how to help (what logs you need) before I do so, no?
AndyYan said:
Done.
I'd need to know how to help (what logs you need) before I do so, no?
Click to expand...
Click to collapse
Just had a quick look, which device you were using to get the logs, it doesn't seem to be a Honor 7x?!
Pretoriano80 said:
Just had a quick look, which device you were using to get the logs, it doesn't seem to be a Honor 7x?!
Click to expand...
Click to collapse
Weird, I didn't have another device at hand when I was taking the logs, I'm fairly certain that it's from my 7X. I do see it mention this in the recovery.log:
Code:
persist.radio.current_version=BND-AL10 8.0.0.331(C00)
I captured logs again just in case.
I was on Oreo beta B331 and am now on LineageOS Treble GSI, if that matters.
AndyYan said:
Weird, I didn't have another device at hand when I was taking the logs, I'm fairly certain that it's from my 7X. I do see it mention this in the recovery.log:
I captured logs again just in case.
I was on Oreo beta B331 and am now on LineageOS Treble GSI, if that matters.
Click to expand...
Click to collapse
As far as i can see, your device is not encrypted! Also, custom roms are not supported yet. I will have a look later, after work, but loke i said, from logs is seems that your storage is not encrypted.
Pretoriano80 said:
As far as i can see, your device is not encrypted! Also, custom roms are not supported yet. I will have a look later, after work, but loke i said, from logs is seems that your storage is not encrypted.
Click to expand...
Click to collapse
Yes, I have modified fstab in vendor to disable storage encryption on /data (various reasons); I don't see how that's related to not being able to mount /system properly, however.
Probably the other guy who reported a similar problem would be able to get you the "clean" logs you need.
AndyYan said:
Yes, I have modified fstab in vendor to disable storage encryption on /data (various reasons); I don't see how that's related to not being able to mount /system properly, however.
Probably the other guy who reported a similar problem would be able to get you the "clean" logs you need.
Click to expand...
Click to collapse
I already know why it's happening in your case, the cause being the unencrypted storage. This TWRP was especially created to support encryption, otherwise there's already official TWRP without encryption support.
However, your logs are still useful! ?
Pretoriano80 said:
I already know why it's happening in your case, the cause being the unencrypted storage. This TWRP was especially created to support encryption, otherwise there's already official TWRP without encryption support.
However, your logs are still useful!
Click to expand...
Click to collapse
Pardon me, but which official? I don't see 7X / P10Lite / M10Lite on official TWRP site.
AndyYan said:
Pardon me, but which official? I don't see 7X / P10Lite / M10Lite on official TWRP site.
Click to expand...
Click to collapse
Oh, my bad, i thought someone already ported TWRP from Mate 10 Pro.
I might be able to fix system unmount issue with unencrypted devices, but i will need your help with testing cause i only have a Mate 10 Pro and it's encrypted. The best solution would be to add a workaround in the current version without building a new one for unencrypted devices.
Pretoriano80 said:
Oh, my bad, i thought someone already ported TWRP from Mate 10 Pro.
I might be able to fix system unmount issue with unencrypted devices, but i will need your help with testing cause i only have a Mate 10 Pro and it's encrypted. The best solution would be to add a workaround in the current version without building a new one for unencrypted devices.
Click to expand...
Click to collapse
I had for some days Mate 10 Lite - rebranded it from c432 to c185 on Android 7 (cause there was not Oreo-Update available for c432) and updated the phone to Oreo with Nocheck Recovery. I tested your TWRP for P10 Lite for Mate 10 Lite - on Stock its working pretty good. I had not any issues.
The owner of the phone like to have a Stock based Custom Rom, I flashed it and tested 3 different TWRPs.
The Dev of the Rom made one, but it does not working properly - Backup /restore without data is only possible on internal storage, no permission to external SD.... Same with two others.
Your TWRP had only issues with data (cause of the modified vendor/etc/fstab.hi6250 - avb and encryption disabled) and issues with system mount/unmount on Custom Rom. But on Stock Rom no issues.
Here are some Logs (from your TWRP). I had not time before to post it
Finally there is a TWRP capable of decrypting /data on android versions > nougat.
Big thanks @NeoArian
I haven't tested everything in detail as I mostly focused on decryption. If you experience issues or can confirm something working that's not green in the table down below, please share.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you. Hard & a lot.
*
*/
Status
List template by TWRP
Code:
[B]Blocking checks[/B]
- [COLOR="green"]Correct screen/recovery size[/COLOR]
- [COLOR="green"]Working Touch, screen[/COLOR]
- [COLOR="green"]Backup to internal/microSD[/COLOR]
- Restore from internal/microSD
- [COLOR="green"]reboot to system[/COLOR]
- [COLOR="green"]ADB[/COLOR]
[B]Medium checks[/B]
- update.zip sideload
- [COLOR="green"]UI colors (red/blue inversions)[/COLOR]
- [COLOR="green"]Screen goes off (and on :))[/COLOR]
- F2FS/EXT4 Support, exFAT/NTFS where supported
- [COLOR="green"]all important partitions listed in mount/backup lists[/COLOR]
- backup/restore to/from external (USB-OTG) storage
- backup/restore to/from adb
- [COLOR="green"]decrypt /data[/COLOR]
- Correct date
[B]Minor checks[/B]
- MTP export
- [COLOR="green"]reboot to bootloader[/COLOR]
- [COLOR="green"]reboot to recovery[/COLOR]
- [COLOR="green"]poweroff[/COLOR]
- [COLOR="green"]battery level[/COLOR]
- [COLOR="green"]temperature[/COLOR]
- encrypted backups
- [COLOR="green"]input devices via USB (USB-OTG) - keyboard, mouse[/COLOR]
- USB mass storage export
- [COLOR="green"]set brightness[/COLOR]
- [COLOR="green"]vibrate[/COLOR]
- [COLOR="green"]screenshot[/COLOR]
Limitations
Following limitations are known:
none
Click to expand...
Click to collapse
prerequisites
For reboot to recovery from your android system (and OTA updates) your ROM needs the following patches 1, 2 and 3. Following ROM's currently support this:
AICP 14
AICP 15
LineageOS 15
LineageOS 16
LineageOS 17
Click to expand...
Click to collapse
For correct time inside TWRP your ROM needs the following patch. Following ROM's currently support this:
AICP 15
LineageOS 16
LineageOS 17
Click to expand...
Click to collapse
Download
SourceForge
AndroidFileHost
Click to expand...
Click to collapse
How to build
https://github.com/115ek/manifest#build-twrp
Click to expand...
Click to collapse
XDA:DevDB Information
[RECOVERY][Unofficial][amami] TWRP 3.4.0, Tool/Utility for the Sony Xperia Z1 Compact
Contributors
115ek, NeoArian
Source Code: https://github.com/115ek/twrp_device_sony_amami
Version Information
Status: Beta
Created 2019-08-25
Last Updated 2020-08-22
Changelog
15.09.2020 3.4.0-1
again: fix non working OTA update in rare cases (rebooting to recovery and stucking there unable to install update automatically)
22.08.2020 3.4.0-0
latest TWRP changes
29.02.2020 3.3.1-0.4
display sony bootlogo at boot
show version number
remove TWRP app
19.09.2019 3.3.1-0.3
fix non working OTA update (rebooting to recovery and stucking there unable to install update automatically)
05.09.2019 3.3.1-0.2
enable reboot to bootloader (fastboot mode) (you have to connect the phone via usb BEFORE rebooting)
25.08.2019 3.3.1-0.1
decrease size
allow decryption in any case of patchlevel value
25.08.2019 3.3.1-0
initial release
Reserved
Backup to microSD seems to be working fine (haven't restored anything yet):good:
I uploaded a new build 3.3.1-0.1 with decreased size and a "more clean" way to allow /data decryption.
Furthermore I thought about getting this official.
BTW: You won't see the increased version number in TWRP. It's still 3.1.1-0
115ek said:
I uploaded a new build 3.3.1-0.1 with decreased size and a "more clean" way to allow /data decryption.
Furthermore I thought about getting this official.
BTW: You won't see the increased version number in TWRP. It's still 3.1.1-0
Click to expand...
Click to collapse
Hi, thank you for this build. I was waiting to try Pie on my z1 compact and I'm glad I did because the version of TWRP was blocking my use of encryption.
Sadly I didn't have luck installing the latest builds (the ones from 3 days ago and one week ago) on my Z1 Compact. I got this error:
Code:
fastboot: core/libsparse/sparse.cpp:131: int write_all_blocks(struct sparse_file *, struct output_file *): Assertion `pad >= 0' failed.
When trying to flash to recovery partition. The same command worked to flash back to 3.2.3 (not sure if necessary, done just in case). If there's any way you could look into these builds I'd appreciate it!
bananabytes said:
Hi, thank you for this build. I was waiting to try Pie on my z1 compact and I'm glad I did because the version of TWRP was blocking my use of encryption.
Sadly I didn't have luck installing the latest builds (the ones from 3 days ago and one week ago) on my Z1 Compact. I got this error:
Code:
fastboot: core/libsparse/sparse.cpp:131: int write_all_blocks(struct sparse_file *, struct output_file *): Assertion `pad >= 0' failed.
When trying to flash to recovery partition. The same command worked to flash back to 3.2.3 (not sure if necessary, done just in case). If there's any way you could look into these builds I'd appreciate it!
Click to expand...
Click to collapse
What command did you use?
Code:
fastboot flash recovery
or
Code:
fastboot flash FOTAKernel
Do you have the newest bootloader installed? So can you boot directly into recovery with VOL down and power pressed (with 3.2.3 version where flashing was successful)?
Or do you use the method with pressing VOL down when the LED lights up?
EDIT:
By looking at your error code I get the feeling it has something to do with fastboot directly. libsparse is a build dependency of the fastboot binary.
What version of fastboot are you using?
I'm using fastboot installed from the packetmanager with
Code:
apt install fastboot
.
Code:
fastboot --version
gives fastboot version 1:8.1.0+r23-5~18.04.
This would mean 27.0.0 or 27.0.1 according to this scheme. I don't know why they are using different naming schema
However, I'd guess you're using an outdated version (or a very current one - but I don't think so).
115ek said:
What command did you use?.
Click to expand...
Click to collapse
I used fastboot flash recovery, with the newest bootloader. This time I got into recovery by selecting it in my older TWRP because I always get the up/down method mixed up, I have done it before it's just easier that way.
115ek said:
By looking at your error code I get the feeling it has something to do with fastboot directly. libsparse is a build dependency of the fastboot binary.
...
However, I'd guess you're using an outdated version (or a very current one - but I don't think so).
Click to expand...
Click to collapse
I am actually indeed using a very current version, 29.0.2 (so your second less likely guess was correct!) I'm on Manjaro/Arch so we get the bleeding edge updates unlike if you are on a Debian/Ubuntu system that's tied to a lot of different libraries and held back. This is exactly why I stopped using those distros but this is the first time I've had the problem in reverse. I don't know if this is a bug that was introduced into fastboot or what. I do see that the more recent versions have things to do with partitioning. This may be a bug to open with fastboot or to look into further with them? But if it's not a bug with them it would be good to have the build working on the latest fastboot.
bananabytes said:
I used fastboot flash recovery, with the newest bootloader. This time I got into recovery by selecting it in my older TWRP because I always get the up/down method mixed up, I have done it before it's just easier that way.
I am actually indeed using a very current version, 29.0.2 (so your second less likely guess was correct!) I'm on Manjaro/Arch so we get the bleeding edge updates unlike if you are on a Debian/Ubuntu system that's tied to a lot of different libraries and held back. This is exactly why I stopped using those distros but this is the first time I've had the problem in reverse. I don't know if this is a bug that was introduced into fastboot or what. I do see that the more recent versions have things to do with partitioning. This may be a bug to open with fastboot or to look into further with them? But if it's not a bug with them it would be good to have the build working on the latest fastboot.
Click to expand...
Click to collapse
Can you please verify that you also fail with the fastboot binary from here
It's also 29.0.2 and it works fine for me.
I have tried this version with LOS 16 and it worked well. Some things to improve
boot to fastboot is not possible
backup and restore of boot is not possible
good catch with encryption, I have give it up :good:
Micha_Btz said:
boot to fastboot is not possible
Click to expand...
Click to collapse
Well, I actually didn't know this was possible in earlier versions. However it should work now --> see the changelog
You have to connect usb cable before rebooting to bootloader, otherwise it won't work and just reboot the system.
Micha_Btz said:
backup and restore of boot is not possible
Click to expand...
Click to collapse
I can't confirm that. What exactly was the problem for you? Backing up or restoring? Did you got any errors?
Have had a look yesterday, Backup and restore of boot is possible (don't now what happends)
@115ek,
I have a mysterious problem with 3.3.1-0.0.and 3.3.1-0.1:
I used all twrp versions before without problems and now your twrp did not show the correct date (1970-xx-xx) and time (7-8 hours back).
I tried the following several times:
1. reflash your twrp, clear recovery and flash again,
2. flash older versions: date and time was wrong even after reboot
The only way to get the correct date/time back in twrp was (at least for me) flash stock ROM with EMMA and after flashing twrp 3.2.3 my backup.
I do not want to repeat this as this is a lot of work incl. copying back the internal storage.
tramp20 said:
@115ek,
I have a mysterious problem with 3.3.1-0.0.and 3.3.1-0.1:
I used all twrp versions before without problems and now your twrp did not show the correct date (1970-xx-xx) and time (7-8 hours back).
I tried the following several times:
1. reflash your twrp, clear recovery and flash again,
2. flash older versions: date and time was wrong even after reboot
The only way to get the correct date/time back in twrp was (at least for me) flash stock ROM with EMMA and after flashing twrp 3.2.3 my backup.
I do not want to repeat this as this is a lot of work incl. copying back the internal storage.
Click to expand...
Click to collapse
Can you try the latest version?
At first you have to set the right timezone in TWRP settings.
The time is stored in a real time clock (RTC) which runs even if the device is powered off. Setting and reading it's value is done by a kernel driver. If you set the right time in android system it gets stored in the RTC. Then, if you boot into TWRP, the time is read again. And for me this works fine. However it takes some seconds (there's a wrong time at the beginning).
115ek said:
Can you try the latest version?
At first you have to set the right timezone in TWRP settings.
The time is stored in a real time clock (RTC) which runs even if the device is powered off. Setting and reading it's value is done by a kernel driver. If you set the right time in android system it gets stored in the RTC. Then, if you boot into TWRP, the time is read again.
Click to expand...
Click to collapse
Thank you. I know this all, I tried reset to default in TWRP and set TZ etc. but these two mentioned TWRP versions do not read the RTC time (AICP ROM).
All TWRP versions before were ok. I tried this several times.
I noticed this "bug" on my Z1c after a backup with your TWRP (Date from 1970 and a complete false time even after setting the TZ).
Even after flashing one of the older TWRP date/time are wrong (only in TWRP), after booting to Android date/time is correct until I boot to TWRP again.
As I wrote the way back to a correct date/time in TWRP was for me flashing stock ROM with EMMA.
Where is this "kernel driver"? In your TWRP version or in a hidden partition? Sorry I do not know much of these internals.
I assume you did not change in the newest version something regarding this problem.
I have not the time to try the last version for now
Generic question re: encrypting this device
Installed this twrp version and (unlike others) I don't see anything strange. Only thing I haven't tried so far is restoring a nandroid backup I created with this twrp release.
A few days back after I had installed this the first time Itried to encrypt my phone; after a while I received the message that encryption was completed.
Then upon reboot of the device I had to unlock it even before boot sequence had started. Aftter unlocking booting resumed and from then on everything appeared to be as before.
This surprised me a bit because on my other phone (OnePlus6 running stock OOS Pie) I have to unlock after boot sequence has completed. But OK, this may be the LOS 16 way.
Then I devided to unencrypt the phone (this is my secondary device and I only use it for playing around a bit, until I decide to sell it, maybe). Again, from my OP6 I'm used to the fact that if I remove any device locking pattern encryption is gone. But obviously not on my Z1c: after I had removed the security pattern (= set security to nothing) everything appeared to be normal. But after the next reboot all data were gone.
Question: is there a supported way to unencrypt this phone without losing any data?
If there isn't such a way: what happens to my Nandroid backups I took while the phone was encrypted? Are they still usable e.g. after I install a ROM update?
tramp20 said:
Thank you. I know this all, I tried reset to default in TWRP and set TZ etc. but these two mentioned TWRP versions do not read the RTC time (AICP ROM).
All TWRP versions before were ok. I tried this several times.
I noticed this "bug" on my Z1c after a backup with your TWRP (Date from 1970 and a complete false time even after setting the TZ).
Even after flashing one of the older TWRP date/time are wrong (only in TWRP), after booting to Android date/time is correct until I boot to TWRP again.
As I wrote the way back to a correct date/time in TWRP was for me flashing stock ROM with EMMA.
Where is this "kernel driver"? In your TWRP version or in a hidden partition? Sorry I do not know much of these internals.
I assume you did not change in the newest version something regarding this problem.
I have not the time to try the last version for now
Click to expand...
Click to collapse
Flashing stock ROM isn't necessary - I'm 99% sure. Maybe you can get a log with
Code:
adb pull /tmp/recovery.log
while your in TWRP and connected to a PC...
The kernel driver is - as the name says - located in the kernel, which is part of the recovery.img
So everyone flashing this image should have the same functionality (in theory). As it works for me (and some others) I'm just wondering.
lm089 said:
Installed this twrp version and (unlike others) I don't see anything strange. Only thing I haven't tried so far is restoring a nandroid backup I created with this twrp release.
A few days back after I had installed this the first time Itried to encrypt my phone; after a while I received the message that encryption was completed.
Then upon reboot of the device I had to unlock it even before boot sequence had started. Aftter unlocking booting resumed and from then on everything appeared to be as before.
This surprised me a bit because on my other phone (OnePlus6 running stock OOS Pie) I have to unlock after boot sequence has completed. But OK, this may be the LOS 16 way.
Then I devided to unencrypt the phone (this is my secondary device and I only use it for playing around a bit, until I decide to sell it, maybe). Again, from my OP6 I'm used to the fact that if I remove any device locking pattern encryption is gone. But obviously not on my Z1c: after I had removed the security pattern (= set security to nothing) everything appeared to be normal. But after the next reboot all data were gone.
Question: is there a supported way to unencrypt this phone without losing any data?
If there isn't such a way: what happens to my Nandroid backups I took while the phone was encrypted? Are they still usable e.g. after I install a ROM update?
Click to expand...
Click to collapse
The behaviour is totally expected as amami uses the deprecated full disk encryption (FDE). Most likely your oneplus 6 is using file based encryption (FBE). That's the reason it can boot to your lockscreen because some files necessary for booting aren't encrypted (or not encrypted using your password...). To boot a device with fully encrypted /data you have to decrypt it first. If you're interested in details have a look here.
The other thing sounds a bit strange. However I don't know if it's possible to remove the FDE completely. Maybe the device just sets a default password then?
Concerning your question:
What definitely should work is taking a backup in TWRP (of course need to decrypt /data before), then format /data and restore the backup. Anyhow - I didn't test such a case so far.
115ek said:
Flashing stock ROM isn't necessary - I'm 99% sure. Maybe you can get a log with
Code:
adb pull /tmp/recovery.log
while your in TWRP and connected to a PC...
The kernel driver is - as the name says - located in the kernel, which is part of the recovery.img
Click to expand...
Click to collapse
Flashing stock ROM was the only way that all older TWRP could read the correct date again after trying your twrp version.
I will try to get a log if I have enough time.
So the recovery.img = twrp.img or at least a part of it?
Thank you.
New update:
As I had problems with installing OTA updates (especially with /data encrypted, but not limited to) on LineageOS 16.0 I came up with a fix.
Download Currently only on sourceforge - android filehost is buggy at the moment...
19.09.2019 3.3.1-0.3
fix non working OTA update (rebooting to recovery and stucking there unable to install update automatically)
Edit:
As reminder for me / interested guys: This commit breaks the OTA updating in some cases (when mmap isn't sufficient). The buildflag
Code:
-D_FILE_OFFSET_BITS=64
doesn't work as intended on my setup. Maybe I missed something.
tramp20 said:
@115ek,
I used all twrp versions before without problems and now your twrp did not show the correct date (1970-xx-xx) and time (7-8 hours back).
Click to expand...
Click to collapse
Have the same time/date problem with twrp-3.3.1-0.3-amami.img
recovery.log >> https://pastebin.com/rBdHAmz2
Also does not reboot into the recovery from system (AICP 14), just shutdown and then power+volume down works.
Love (how the hell can you love a machine??? - sorry, I guess I have NO imagination, maybe you can ...) this phone. BUT!! After backing up and restoring using LR TWRP a number of times, then using fastboot to flash_all the original ROM a number of times when I got into flashing problems, my cavalier approach backfired in one of these repetitive actions. Surprisingly, at least to me, I have both IMEI's listed on the status page, but a constant "unknown baseband" version. SIM setting is grayed-out, and I am only on WiFi. Flashing the original ROM (V 10.4.2.0) fixed nothing. Tried V 10.4.1.0, but I can't downgrade: luckily the phone wasn't bricked. Flashed Havoc V 2.9, hoping all partitions would be overwritten, then flashed MIUI V 10.4.2.0, but no change.
Have found no solution from Hovatek (stated flashing original ROM usually repairs the unknown baseband issue), or other sites searched from Google. Any procedure to solve this MTK issue on this phone would be most appreciated.
fastboot flash_all IS already deleting & overwriting all partitions, but I found sth interesting going on both my RN8P:
1. Sometimes both of the bluetooth MAC is gone on normal reboot, replaced by generic one 00:00:46:00:00:01 (yes, both got identical MAC).
2. One of the phone can't recognize SIM card after reboot, need another reboot to fix it.
Turned out that somewhere in upgrading to MIUI 11 Android 10 ver, it's corrupting some partitions: nvcfg, ncdata, nvram, vendor, persist, misc, cust.
Here's my fix:
1. Boot to TWRP
2. Mount those partitions then go to Advanced > Terminal, issue: mount to list the ID of the partitions
3. Unmount all partitions
4. Back to terminal, issue: e2fsck -fy /dev/block/sdcX where X is the parition ID corresponding to the list of mount above
5. It'll show that some partition is getting fixed, if done, just issue: sync
6. Reboot to MIUI, let it sit for 5 minutes, then reboot to TWRP again, redo all steps & you'll see it's still getting some errors, it's normal. Redo for 2 more times, it'll get fixed for good.
Something in the systems doesn't right, it kinda needs to readjust all the fixed partitions but in the process it also corrupting it again, therefore needing 2 - 3 more e2fsck as I said above.
Oh, if you're rooted & using AdGuard, NEVER USE Move Certificate module in the Magisk, it's the one contributing to those corruption.
Wow!! Thank you so much! I will follow each step and report what I've found.
So impressed with the detail you have given; thanks to have experts such as you willing to share.
Later ....
Crescendo Xenomorph said:
fastboot flash_all IS already deleting & overwriting all partitions, but I found sth interesting going on both my RN8P:
1. Sometimes both of the bluetooth MAC is gone on normal reboot, replaced by generic one 00:00:46:00:00:01 (yes, both got identical MAC).
2. One of the phone can't recognize SIM card after reboot, need another reboot to fix it.
Turned out that somewhere in upgrading to MIUI 11 Android 10 ver, it's corrupting some partitions: nvcfg, ncdata, nvram, vendor, persist, misc, cust.
Here's my fix:
1. Boot to TWRP
2. Mount those partitions then go to Advanced > Terminal, issue: mount to list the ID of the partitions
3. Unmount all partitions
4. Back to terminal, issue: e2fsck -fy /dev/block/sdcX where X is the parition ID corresponding to the list of mount above
5. It'll show that some partition is getting fixed, if done, just issue: sync
6. Reboot to MIUI, let it sit for 5 minutes, then reboot to TWRP again, redo all steps & you'll see it's still getting some errors, it's normal. Redo for 2 more times, it'll get fixed for good.
Something in the systems doesn't right, it kinda needs to readjust all the fixed partitions but in the process it also corrupting it again, therefore needing 2 - 3 more e2fsck as I said above.
Oh, if you're rooted & using AdGuard, NEVER USE Move Certificate module in the Magisk, it's the one contributing to those corruption.
Click to expand...
Click to collapse
Okay,
No luck here:
I have not upgraded to MIUI 11 Android 10. Still on MIUI 10 Android 9.
LR. TWRP has no mount for NVRAM or for MISC. What version of TWRP do you have?
No error messages for the other remaining sdc's - sync after each e2fsck commands. Reboot to system and still unknown baseband - repeated procedure twice, after waiting 5 and 7 minutes.
Thanks for the heads-up on the Move Certificate module and AdGuard - never installed it as it seemed to be not for Xiaomi.
ppthom said:
Okay,
No luck here:
I have not upgraded to MIUI 11 Android 10. Still on MIUI 10 Android 9.
LR. TWRP has no mount for NVRAM or for MISC. What version of TWRP do you have?
No error messages for the other remaining sdc's - sync after each e2fsck commands. Reboot to system and still unknown baseband - repeated procedure twice, after waiting 5 and 7 minutes.
Thanks for the heads-up on the Move Certificate module and AdGuard - never installed it as it seemed to be not for Xiaomi.
Click to expand...
Click to collapse
it is indeed not possible to mount an NVRAM partition, maybe the one referred to is the Mount System, you must first check the mount system to restore or backup.
for TWRP files you can adjust to your current Android Version, please check the following post.
https://forum.xda-developers.com/re...overy-twrp-recovery-redmi-note-8-pro-t4033695
Coffeemi said:
it is indeed not possible to mount an NVRAM partition, maybe the one referred to is the Mount System, you must first check the mount system to restore or backup.
for TWRP files you can adjust to your current Android Version, please check the following post.
https://forum.xda-developers.com/re...overy-twrp-recovery-redmi-note-8-pro-t4033695
Click to expand...
Click to collapse
I always find out something new. Thank you. No mount NVRAM partition. As far as mount, I thought that SYSTEM partition was always auto-mounted. Not so, it is DATA and CACHE. I have backed-up and restored with this understanding. My bad, again.
Also LR. TWRP is the 1104 version, my goto recovery, as I am always able to get out of trouble using it, except now with no baseband version. However, after using Flash_all, I have to boot into the basic system to make changes before I can restore one of my backups. In this default setup, the status lists no baseband and no IMEI. It is only on restore to my latest backup that both IMEI's are also restored, but not the baseband.
ppthom said:
I always find out something new. Thank you. No mount NVRAM partition. As far as mount, I thought that SYSTEM partition was always auto-mounted. Not so, it is DATA and CACHE. I have backed-up and restored with this understanding. My bad, again.
Also LR. TWRP is the 1104 version, my goto recovery, as I am always able to get out of trouble using it, except now with no baseband version. However, after using Flash_all, I have to boot into the basic system to make changes before I can restore one of my backups. In this default setup, the status lists no baseband and no IMEI. It is only on restore to my latest backup that both IMEI's are also restored, but not the baseband.
Click to expand...
Click to collapse
if you have properly saved a backup file of all modem and IMEI partitions, all modem data will definitely be restored, I'm sure not all of the modem partitions have been successfully backed up.
for the modem partition, sensor and IMEI, here are the names of the partitions.
- nvcfg
- nvdata
- nvram
- persist
- protect_f
- protect_s
make sure all the partition names are in your TWRP backup file.
Sent from my Redmi Note 8 Pro using XDA-Developers Legacy app
You should be able to do a DD if=/image.bin of=/dev/block/sdcX to fix if you don't have a TWRP backup
- nvcfg is sdc7
- nvdata is sdc8
- nvram is sdc18
- persist is sdc10
- protect_f is sdc11 labelled protect1
- protect_s is sdc12 labelled protect2
I assume protect_f and protect_s is protect1 and 2 but hopefully someone can confirm.
Coffeemi said:
if you have properly saved a backup file of all modem and IMEI partitions, all modem data will definitely be restored, I'm sure not all of the modem partitions have been successfully backed up.
for the modem partition, sensor and IMEI, here are the names of the partitions.
- nvcfg
- nvdata
- nvram
- persist
- protect_f
- protect_s
make sure all the partition names are in your TWRP backup file.
Sent from my Redmi Note 8 Pro using XDA-Developers Legacy app
Click to expand...
Click to collapse
I have NOT "properly saved a backup file" with the modem partitions, and that is where my trouble lies. I am also not being reminded to set the SIM card info when booting up after flashing the stock 10.4.2.0 ROM, which is strange, because a week ago I was able to go back-and-forth between my restored backed-up files and the stock ROM. On first booting the stock ROM, I was reminded every 10 seconds that my SIM card was not correct (my card is only 3G and the default SIM setup was for LTE), interferring with setting up my WiFi for authenticating my Xiaomi account. Now, with an unknown baseband, the SIM is not recognised by the stock ROM, I can enter my WiFi account without interference; and there no entry for the baseband and nothing for the IMEI numbers.
As soon as my "not proper backup" is restored, the IMEI numbers are set correctly, but no baseband.
My goodness, I will see if anyone online can flash the stock zip file remotely and see if that corrects the problem.
Hey, thank you for paying attention to my problem, and I very much appreciate your time on this.
wang1chung said:
You should be able to do a DD if=/image.bin of=/dev/block/sdcX to fix if you don't have a TWRP backup
- nvcfg is sdc7
- nvdata is sdc8
- nvram is sdc18
- persist is sdc10
- protect_f is sdc11 labelled protect1
- protect_s is sdc12 labelled protect2
I assume protect_f and protect_s is protect1 and 2 but hopefully someone can confirm.
Click to expand...
Click to collapse
Thank you fellow Canadian :good:; I will try this as well. So great to have all these suggestions from people who know a hell of a lot more than I do. Thank you both Coffeemi and wang1chung.
ppthom said:
Okay,
No luck here:
I have not upgraded to MIUI 11 Android 10. Still on MIUI 10 Android 9.
LR. TWRP has no mount for NVRAM or for MISC. What version of TWRP do you have?
No error messages for the other remaining sdc's - sync after each e2fsck commands. Reboot to system and still unknown baseband - repeated procedure twice, after waiting 5 and 7 minutes.
Thanks for the heads-up on the Move Certificate module and AdGuard - never installed it as it seemed to be not for Xiaomi.
Click to expand...
Click to collapse
Better to use LR TWRP, it's the best for Xiaomi phone.
Sadly it's only available for Android 10 version. Better upgrade as Android 10 still way better than their 9 (too much bug).
Link to A10 LR-TWRP: https://mega.nz/file/Ad4TUTTA#_xT16vOzYK-O8qaWEHPYxfdi4wNpK5Ang9maN5iO_-U
If no error being corrected then sadly I dunno more except for hardware issue (baseband chip is broken, I saw one case in Mi Community forum). Hope not this case. :crying:
You're welcome friend. The Move Certificate module is for AdGuard actually, its to clear those network being monitored notification when you use AdGuard's HTTPS filtering.
Thank you Coffeemi, wang1chung and of course Crescendo Xenomorph. You've all paid attention to this problem, and it is very much appreciated.
Ok, ok. Not sure how I did not stumble accross this before, or, more likely, not paid attention to this procedure .
I choose to use RN8P with Miui V10.4.2.0 ROM. Gives me the most flexibility. Later Android versions restrict my wants, including using TWRP - just a personal opinion; yours may vary ...
Erased NVRAM and nvdata in this ROM, after having flashed it and rooted it, then installing X-plore File Manager apk (most other rooted file managers would work as well, if not better).
Rebooted, and the unknown baseband problem was solved, at least for me.
Then restored my latest TWRP backup of Data, Boot, System image, Vendor image and Cust image.
All seems well. No more unknown baseband, IMEI's listed as well as Bluetooth. Whew. So many good people out "there", and so many experts to thank. Thank you:good:.
ppthom said:
Ok, ok. Not sure how I did not stumble accross this before, or, more likely, not paid attention to this procedure .
I choose to use RN8P with Miui V10.4.2.0 ROM. Gives me the most flexibility. Later Android versions restrict my wants, including using TWRP - just a personal opinion; yours may vary ...
Erased NVRAM and nvdata in this ROM, after having flashed it and rooted it, then installing X-plore File Manager apk (most other rooted file managers would work as well, if not better).
Rebooted, and the unknown baseband problem was solved, at least for me.
Then restored my latest TWRP backup of Data, Boot, System image, Vendor image and Cust image.
All seems well. No more unknown baseband, IMEI's listed as well as Bluetooth. Whew. So many good people out "there", and so many experts to thank. Thank you:good:.
Click to expand...
Click to collapse
Can you provide me the steps. Because I'm having the same vesion but with IMEI Invalid. My phone accidently got update to MIUI 11 and the Baseband got ruined.!!!
Somehow Android 10 in this phone will corrupt something in nvdata if you do modification on the fly (somehow like they unable to load it properly, thus no baseband with corrupted BT MAC).
How to know if your BT MAC is corrupted? It'll default to 00:00:46:00:00:01.
BT MAC should be one step above WIFI MAC (if your WIFI MAC is AC:1C:05:AC:43:01, your BT should be AC:1C:05:AC:43:02).
Found the culprit: any Magisk version greater than 20.3 will cause this error on MTK devices.
Solution: use Magisk 20.3 stable, it's the only fix till the devs come up with the fix.
Hello all,
I've been having the hardest week, all my personal business at the halt (cant use bank apps, email etc.). One morning my phone suddenly entered a bootloop, then since then I was in a bit of hurry, I tried a stock rom recovery update from twrp, that made the phone enter a hardbrick status.
Then since we don't have a firehose for the 'lisa' I had to pay a guy to take it out. That solved the hardbrick but the softbrick remained. Since I am not an android expert just have mediocre knowledge I asked a kind persons help. They've been trying to help me for days but we still couldn't solve the issue and I thought other opinions would be nothing but helpful.
The details you should know:
1. Only hardware operation made on the device is changing a resistor. (Can explain it better, if requested). But the phone was working just fine after it for months.
2. We have identified the partitions are all messed up and and flashing stock rom doesn't solve it, tried Eu, global and Chinese roms.
3. The system was missing on the twrp advance wipe and there were:
dalvik
metadata
data
ınt storage
sdcard1
usb otg
4. I didn't understand all the things he/she tried but tried to fix the partitions mainly using these sources ( it could give you a better idea ):
How to create System partition in Android? Which is accidentally deleted when tried to increase size.
Tools needed can be downloaded from forum.xda-developers Section 3. parted_gdisk_fdisk_mkfs.ext4-AARCH64.zip - [Click for QR Code] ...
illitrateman.blogspot.com
How to fix "Partition does not start on physical sector boundary" warning?
I have one HDD on my laptop, with two partitions (one ext3 with Ubuntu 12.04 installed and one swap). fdisk is giving me the following warning: Partition 1 does not start on physical sector boundary
askubuntu.com
5. We tried 3 different custom roms but no avail.
6. At the moment the phone can enter in fastboot but giving trouble flashing twrp or orangefox.
I'm confident my expert angel has a solution for that but I think in general any thoughts, ideas, suggestions would be highly appreciated.
Thank you in advance...
Try to use Miflash with the oldest Fastboot rom.
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
MIFLASH[GUIDE]⚙ USE XIAOMI FLASH TOOL
FOR ALL XIAOMI BOOTLOADER MUST BE UNLOCKED https://new.c.mi.com/global/post/101245 https://en.miui.com/unlock/index.html ----------------------------------------------------------------------------------------------------------- All your data...
forum.xda-developers.com
NOSS8 said:
Try to use Miflash with the oldest Fastboot rom.
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
MIFLASH[GUIDE]⚙ USE XIAOMI FLASH TOOL
FOR ALL XIAOMI BOOTLOADER MUST BE UNLOCKED https://new.c.mi.com/global/post/101245 https://en.miui.com/unlock/index.html ----------------------------------------------------------------------------------------------------------- All your data...
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you for your input, yes we have thought of that and downloaded the oldest global rom but haven't tried to flash it yet because of another hardbrick possibility. We are trying to fix it with terminal within twrp (we can flash twrp now) attempting to fix the partitions.
Any other ideas?
stercorarius said:
Thank you for your input, yes we have thought of that and downloaded the oldest global rom but haven't tried to flash it yet because of another hardbrick possibility. We are trying to fix it with terminal within twrp (we can flash twrp now) attempting to fix the partitions.
Any other ideas?
Click to expand...
Click to collapse
Not sure that the Twrp for this device is 100% functional, especially since this device has A/B partitions and A13 has write restrictions.
You can try a Xiaomi Eu rom and flash the rom in fastboot mode with the first install.bat script included in the extracted folder.(xiaomi.eu_multi_MI11LE_XM11Lite5GNE_V14.0.6.0.TKOCNXM_v14-1)
Xiaomi.eu Multilang MIUI ROMs - Browse /xiaomi.eu/MIUI-STABLE-RELEASES/MIUIv14 at SourceForge.net
OFFICIAL mirror of MIUI Multilang ROM by https://xiaomi.eu/
sourceforge.net
Format data, erase your data and create a new partition if necessary (Twrp format data type yes, Miflash and Xiaomi Eu rom do it too).
The recovery roms do not contain all the system imgs unlike the Fastboot rom and Xiaomi Eu rom.
Could also be a HW problem.
stercorarius said:
Hello all,
I've been having the hardest week, all my personal business at the halt (cant use bank apps, email etc.). One morning my phone suddenly entered a bootloop, then since then I was in a bit of hurry, I tried a stock rom recovery update from twrp, that made the phone enter a hardbrick status.
Then since we don't have a firehose for the 'lisa' I had to pay a guy to take it out. That solved the hardbrick but the softbrick remained. Since I am not an android expert just have mediocre knowledge I asked a kind persons help. They've been trying to help me for days but we still couldn't solve the issue and I thought other opinions would be nothing but helpful.
The details you should know:
1. Only hardware operation made on the device is changing a resistor. (Can explain it better, if requested). But the phone was working just fine after it for months.
2. We have identified the partitions are all messed up and and flashing stock rom doesn't solve it, tried Eu, global and Chinese roms.
3. The system was missing on the twrp advance wipe and there were:
dalvik
metadata
data
ınt storage
sdcard1
usb otg
4. I didn't understand all the things he/she tried but tried to fix the partitions mainly using these sources ( it could give you a better idea ):
How to create System partition in Android? Which is accidentally deleted when tried to increase size.
Tools needed can be downloaded from forum.xda-developers Section 3. parted_gdisk_fdisk_mkfs.ext4-AARCH64.zip - [Click for QR Code] ...
illitrateman.blogspot.com
How to fix "Partition does not start on physical sector boundary" warning?
I have one HDD on my laptop, with two partitions (one ext3 with Ubuntu 12.04 installed and one swap). fdisk is giving me the following warning: Partition 1 does not start on physical sector boundary
askubuntu.com
5. We tried 3 different custom roms but no avail.
6. At the moment the phone can enter in fastboot but giving trouble flashing twrp or orangefox.
I'm confident my expert angel has a solution for that but I think in general any thoughts, ideas, suggestions would be highly appreciated.
Thank you in advance...
Click to expand...
Click to collapse
Which twrp version were you using and which version of MIUI did you try to flash when you hard bricked?
There's no system partition nowadays, it is now included in the "super" partition (system, system_ext, product and vendor) and developer removed the option to wipe it because you are not intended to wipe it.
My recomendation is to flash any fastboot rom, I've flashed 7 roms with fastboot and it always worked flawlessly.
Hi, I'm the person that has been helping.
Of course we flashed miui (in fastboot). Global and chinese. We haven't tried eu yet.
I think I've found the source of the problem, but I'm not sure if solving it will fix the bootloop. A partition that's called switch is corruped. It reports as 16EiB (yes that is correct, 16 exabytes, 18446744073709551607 sectors, reported by gptfdisk, full report). It could just be a program issue. The switch partition in located in /dev/block/sda1 and /dev/block/dm-5. I also found that a dummy.img file is being flashed to that partition.
I also got this error from trying to open the switch partition from a newer version of gptfdisk.
I'm not sure if that's the reason for the bootloop, but I think it can be.
These reports have been from /dev/block/sda1. From /dev/block/dm-5 it's like this.
If someone wants to look at the tools I found, they're here.
If someone has any suggestions or possible answers for us, please reply.
What is the error generated by Mi Flash?
Miflash log folder
NOSS8 said:
What is the error generated by Mi Flash?
Miflash log folder
Click to expand...
Click to collapse
Hi, there was is no error in miflash.
You can take a look here if you want to.
Indeed, no error.
Could be a boot sector problem but with dynamic+A/B partitions+A13 , it gets tricky.
NOSS8 said:
Indeed, no error.
Could be a boot sector problem but with dynamic+A/B partitions+A13 , it gets tricky.
Click to expand...
Click to collapse
Can we somehow repair the sector?
Sucharek 233 said:
Can we somehow repair the sector?
Click to expand...
Click to collapse
I saw that you changed a transistor, maybe there is a problem elsewhere that is causing this to happen.
Changing the motherboard with the flex cable might be preferable.
I doubt that what you are trying to do is possible due to the complexity of the current system and especially for boot sectors which are not likely to be accessible with current tools.
Especially since the problem has not been identified with precision.
A little update:
We tried flashing EU rom and the oldest rom, but still no luck. Phone is still bootlooping and switch partition is still broken.