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.
Related
I have an old Z00A that has hardware problems (constant screen flickering, battery stuck at 50%) so I backed up every partition with TWRP including system, boot , data etc and purchased a new Z00A.
I used the new Z00A for a few days to ensure that there was no hardware problems and then proceeded to unlock the boot loader and flash TWRP recovery. At this point both sims were working.
I then restored the backup of the old Z00A with TWRP on the new Z00A (Had to change folder name so TWRP recognizes the backup from the old Z00A). After the restore was complete and the phone booted, sim1 stopped working.
After searching through the forums and Google I found some solutions to it but none of them seem to work
Solutions that I have tried
1. Factory reset the phone through TWRP
2. Wiped every partition through( exclude SD Card) TWRP, flashed stock recovery and installed the official firmware.zip file through stock recovery
3. Did a factory reset with the stock recovery flashed (skimmed through the setup)
4. I downloaded the latest RAW file firmware and installed it through ASUS Flash Tool (Had some issues at first but eventually it went through but sim1 doesn't work)
5. I installed the official Lollipop rom through fastboot and flashed a custom Lollipop rom
6. Flashed stock based MM rom (CleanStock), custom MM and N roms (CM, Lineage, RR) through TWRP and do factory resets
7. I have tried using the adb shell and root commands to set the IMEI but they still return to 004999--------
8. Placed the sims in the old Z00A and they still work
9. Swapped the sim trays of both phones (sim1 and sim2 works on old Z00A but sim1 still doesn't work on new Z00A)
10. Used phonetools to set IMEI but they still return to 004999--------
From flashing the custom roms and swapping the sim trays I can conclude that this is not a hardware problem. On most custom roms it recognizes that there is a sim inserted in sim1 (A pop up comes up about sim has changed etc...) but there is no signal and the phone says emergency calls only or no service. I believe that the baseband or modem file are somehow corrupted due to the TWRP restore from the old Z00A and need to be reflashed but this only seems possible on the Snapdragon variant.
All help is appreciated on this matter :fingers-crossed:
Captain Krunch said:
I have an old Z00A that has hardware problems (constant screen flickering, battery stuck at 50%) so I backed up every partition with TWRP including system, boot , data etc and purchased a new Z00A.
I used the new Z00A for a few days to ensure that there was no hardware problems and then proceeded to unlock the boot loader and flash TWRP recovery. At this point both sims were working.
I then restored the backup of the old Z00A with TWRP on the new Z00A (Had to change folder name so TWRP recognizes the backup from the old Z00A). After the restore was complete and the booted, sim1 stopped working.
After searching through the forums and Google I found some solutions to it but none of them seem to work
Solutions that I have tried
1. Factory reset the phone through TWRP
2. Wiped every partition through( exclude SD Card) TWRP, flashed stock recovery and installed the official firmware.zip file through stock recovery
3. Did a factory reset with the stock recovery flashed (skimmed through the setup)
4. I downloaded the latest RAW file firmware and installed it through ASUS Flash Tool (Had some issues at first but eventually it went through but sim1 doesn't work)
5. I installed the official Lollipop rom through fastboot and flashed a custom Lollipop rom
6. Flashed stock based MM rom (CleanStock), custom MM and N roms (CM, Lineage, RR) through TWRP and do factory resets
7. I have tried using the adb shell and root commands to set the IMEI but they still return to 004999--------
8. Placed the sims in the old Z00A and they still work
9. Swapped the sim trays of both phones (sim1 and sim2 works on old Z00A but sim1 still doesn't work on new Z00A)
10. Used phonetools to set IMEI but they still return to 004999--------
From flashing the custom roms and swapping the sim trays I can conclude that this is not a hardware problem. On most custom roms it recognizes that there is a sim inserted in sim1 (A pop up comes up about sim has changed etc...) but there is no signal and the phone says emergency calls only or no service. I believe that the baseband or modem file are somehow corrupted due to the TWRP restore from the old Z00A and need to be reflashed but this only seems possible on the Snapdragon variant.
All help is appreciated on this matter :fingers-crossed:
Click to expand...
Click to collapse
very first of all root your device. install any root explorer like es file explorer. enable root explorer and hidden files in options of file explorer.
now go to root storage of device meas (/)
find factory folder in factory go to telephony folder and take screenshot
find config folder and then go to telephony folder and take screenshot
post screenshots here then we will look further
sukhwant717 said:
very first of all root your device. install any root explorer like es file explorer. enable root explorer and hidden files in options of file explorer.
now go to root storage of device meas (/)
find factory folder in factory go to telephony folder and take screenshot
find config folder and then go to telephony folder and take screenshot
post screenshots here then we will look further
Click to expand...
Click to collapse
Screenshots posted
Captain Krunch said:
Screenshots posted
Click to expand...
Click to collapse
flash debug firmware and use intel phone tool
sukhwant717 said:
flash debug firmware and use intel phone tool
Click to expand...
Click to collapse
Can you link me to this debug firmware please?, I have already found the Intel phone flash tool
Captain Krunch said:
Can you link me to this debug firmware please?, I have already found the Intel phone flash tool
Click to expand...
Click to collapse
https://drive.google.com/open?id=0B72QQTXqZSRwTmZoQXZxZ0tvTmc
sukhwant717 said:
https://drive.google.com/open?id=0B72QQTXqZSRwTmZoQXZxZ0tvTmc
Click to expand...
Click to collapse
Thank you very much, after flashing this firmware how do I proceed?, I am currently downloading it and hopefully it flashes successfully
Mods can close this thread as he helped me resolve the issue through PMs
Same issue what to do?
Sent from my AO5510 using XDA-Developers Legacy app
My problem was because of a wrong IMEI, I had to flash the debug firmware he linked above and use phone tools 191 to change the IMEI then sim1 began working.
Send me that tool
mkaraniya said:
Send me that tool
Click to expand...
Click to collapse
Tools: https://yadi.sk/d/30q9w4KJjvgHd
You can also watch this video to help you use the tools: https://youtu.be/5oxug7ThayM
Hi everybody,
I also have a problem with sim card , but it is a little bit different then these that have been described above. First of all my sim is working but not all of the time. I do calls and also I receive a lot of calls. But from time to time sim card just restarts and wants again pin code to unlock ( the phone doesn't restart). A lot of people told me that when they are trying to connect me, their phones are ringing twice and after that they heard busy signal as the call was rejected or the line is busy. In the same time my phone doesn't show any incoming call. Also it is interesting that some people told me that they can't connect me for the hole day and in the same time there is no problem with receiving other calls. From time to time I also can't dial a number. The screen stacks on dialing screen for app. 30 seconds and after that just switch to contacts list.
So what I tried till now:
1. I did a clean install of OTA WW_4.21.40.327
2. Tried to use Sim2 slot, the problems didn't disappear
3. I changed my sim card with new one with no result
4. Tried the sim card with other phone, everything works fine
May be it's time to buy a new phone, but before that I want to be sure that the problems are not caused by software bug.
Any advices and help will be appreciated.
P.S.
The phone is rooted, Magisk 13.3 is installed. The phone is ZE551ML, Z00AD
Captain Krunch said:
Tools: https://yadi.sk/d/30q9w4KJjvgHd
You can also watch this video to help you use the tools: https://youtu.be/5oxug7ThayM
Click to expand...
Click to collapse
is your phone fixed now?
i have the same problem with my lenovo p90 (missing imei). but i cant enabled its com port (no way to fix it with intel phone tool without com port existed). no reference to enable it (the com port) nor imei repair on lenovo p90.
i need you to enter your phone with adb shell as root, and create image of /dev/block/mmcblk0p3 and /dev/block/mmcblk0p5. or just copy config and factory folder, then zipped them, then shared here. i need them, to restore what I accidently erased (config and factory partition).
trust me, i won't do any harm to your specific data.
you're my last hope. i hope you'll understand.
dejoebad said:
is your phone fixed now?
i have the same problem with my lenovo p90 (missing imei). but i cant enabled its com port (no way to fix it with intel phone tool without com port existed). no reference to enable it (the com port) nor imei repair on lenovo p90.
i need you to enter your phone with adb shell as root, and create image of /dev/block/mmcblk0p3 and /dev/block/mmcblk0p5. or just copy config and factory folder, then zipped them, then shared here. i need them, to restore what I accidently erased (config and factory partition).
trust me, i won't do any harm to your specific data.
you're my last hope. i hope you'll understand.
Click to expand...
Click to collapse
Am sorry but I recently sold my ZF2 and currently awaiting a new phone. Am sure someone else on the P90 forums can help you get the files you are looking for
Hi friend,
I installed custom rom 8.1 with twrp 64 bits and it was working fine. then i installed stock rom with fastboot mode and lost my imei.
went back to 8.1 rom and got imei back. I had already taken back up of my stock rom previously. so I though I should try that may be I will get imei back on stock. tried that and got Imei back on stock. everything fne till now.
now I have no 4G and started to fix 4G. flashed some back up found on some form thought may b it will resolve the issue.
restarted and no 4g.
tried to flash stock again and lost imei again.
now tried to flash custom 8.1 still no imei.
went back to back ups still no imei.
tried everything still no imei.
I don't know what happen.
Now lets discuss and fix this issue once for all.
Found some important information about our issue:
Network Related Partitions
modemst1 and modemst2: These partitions appear to contain non-essentials/temporary network related data. Interestingly, they are erased when flashing a stock rom, meaning they are probably not crucial, possibly some kind of ‘baseband cache’?
modem: The modem partition contains modem/baseband related files. These files store store settings that allow the device to communicate with cell towers, such as the frequencies. This partitions is region, not device, specific. This partition is flashed as part of the stock firmware flash procedure, so it also is likely not unique (again ensure to get firmware for the right region).
fsg: This partition also contains files related to the modem firmware/baseband. These files store store settings that allow the device to communicate with cell towers, such as the frequencies. This partitions is region, not device, specific. This partition is flashed as part of the stock firmware flash procedure, so it likely contains non-unique data (but ensure to get firmware for the right region).
Maybe ‘fsg’ and ‘modem’ are related to the modemst1 and modemst2 partitions?
Important/Unique Partitions
pds: This partition likely contains important device specific data like the IMEI, Serial Number, etc. It is important to backup this partition when you get the chance, as people in other threads attribute the loss of the IMEI to this partition. This is not included in stock firmware, reinforcing the importance of backing up this partition.
persist: Apparently this partition contains files related to WiFi, Bluetooth, MAC addresses etc. Nevertheless, it is quite important and should be backed up if possible.
hob and dhob: The exact function is not known, but they appear to contain very important information relating to the modem and/or IMEI.
fsc: Appears to be empty. Although, this partition could sometimes store important IMEI related info. Not included in factory firmware and so best left alone.
IMEI backup/restore scripts (pds partition)
Requirements:
- Device has to be rooted, with USB debugging enabled.
- Motorola fastboot (see attachment).
- ADB installed, minimal or the full ADK.
You can search the forum to find how to meet these requirements or for the terms described in this post beginning here:
http://forum.xda-developers.com/show....php?t=2558638
Installation:
Extract imei_scripts.zip (attached) and copy the scripts "imei_backup.bat" and "imei_flash.bat" into the ADB root directory.
Extract mfastboot_only.zip (attached) and copy "mfastboot.exe" into the ADB root directory.
Description/How to use:
These are batch scripts and can be run by double-clicking them or opening a command window from the ADB root. Help is also contained in the scripts. They are run interactively and won't execute anything without the user selecting a choice.
"imei_backup.bat"
Use this script to backup and restore normally using ADB.
"imei_flash.bat"
Use this script to flash the partition as an alternative to the other method using mfastboot while in bootloader mode. The backup, "pds.img" must be located in the ADB directory for the script to run.
The backup is made on the sdcard and is named "pds.img". You'll want to store this elsewhere once backed up. Once done, that's it! You don't need to do anything more. The purpose is as a preventative in the event of the loss of your IMEI.
Run the scripts for additional options and help.
Sources/Interesting information:
https://forum.xda-developers.com/moto-g/general/motorola-moto-g-partitions-explained-t3418644
https://forum.xda-developers.com/showthread.php?t=2675326
DISCLAIMER: Every information is form internet and xda and I will not be responsible for any loss of data or corrupt phones or sd card. That is, use only at your own risk!
Thanks to eastdata for making scripts.
And Professor Gibbins for providing important info.
Good evening. I am from Brazil and I am exactly with this problem. Since I do not speak English (sorry for this) I translated it through Google, but everything was confusing. Does this procedure go back to working the 4G or just backs up earlier to avoid this problem in the future? (but once sorry for not understanding the text) thank you.
When my Cedric was still alive, I tried to update the bootloader and the baseband to the latest January version using fastboot. I didn't touch the current ROM (LineageOS 15.1 unofficial). I flashed the following files to their adequate partitions: adspso.bin, bootloader.img, fsg.mbn, NON-HLOS.bin, and oem.img. The device worked well and was updated perfectly. Then... my curiosity got the best of me. Since the fastboot ROM includes commands to erase the modemst partitions, I thought it would be good to perform that operation (despite everything working well, stupid me). THIS killed IMEI for me:
Code:
fastboot erase modemst1
fastboot erase modemst2
My attempts to recover from this situation led me to try to downgrade to the November update, which ended in a dead device after trying to flash the November full ROM using RSD-Lite. I hope my experience can serve as a warning for others.
"If it ain't broke, don't fix it."
But then again, I've made that mistake many times as well xD
Cedric imei
Do I have to erase modemst1 and. 2 to install backup
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.
This is the new thread for Pie & 10 TWRP Recovery 3.3.1-x
Feature list:
- Pie stock ROMs are fully decryptable with this TWRP, either protected with secure startup or without :good: OREO encrypted userdata is not decryptable with 3.3 . However, if you're on encrypted oreo and update to pie stock, either via zip or kdz, crypto gets migrated and you're good to go in terms of access to your encrypted data with 3.3. So, with this recovery, the urgent need for flashing no-verity-opt-encrypt zip isn't really there anymore
- everything working: backup & restore even with encrypted userdata, no matter if it's from oreo or pie. If you restore a backup containing an encrypted userdata, you'll need to format userdata before, for crypto removal. But only when coming from another encrypted ROM, otherwise you can just restore, boot up (it will use the encryption settings you"ve set up) ; decryption; time & dat; mtp; adb; installing of ROMs and zips in general; themeable; .........
- Possibility to leave out lockscreen settings when restoring a backup (sometimes you were forced to delete them manually, otherwise no login into your restored ROM possible -.- You can bypass this with this. Note: lockscreensettings ≠ encryption pin/pw/pattern.)
- Time and date is shown correctly, independent of /data. This should work after a few boots of ROM and TWRP, TWRP needs to get the data once and later on it will then be calculated from persist's settings file.
- modem image support: backup, restore, flashing of modem images either taken directly from kdz or diskdump. Same for OP partition (not present on USA and some others possibly)
- For removing encryption completely you can now do it as already known, via format userdata. Crypto is removed with it now again.
- busybox instead of toolbox/toybox, for better zip compatibility as it looks for now
- Pie 3.3.1-x: compiled with full 9.0 TWRP sources
- capable of installing every ROM and zip files
- some extra partitions (see below)
Don't forget your timezone settings after flashing. Also there are some extra partitions you can mount/backup/flash/explore, like LAF, persist-LG and OP configs. There's the thought of some people to flash TWRP as a second copy to LAF partition to be on the sure side when it comes to ROM switching or sth like that. You can do this, anyway it's not really recommended (by me and some others) because you'll lose download mode, but you now have the option.
For extra partitions: Some of them are needed for decryption (modem / persist-lg (drm)), some are for VoLTE (OP), time is stored on /persist/time (and /data/vendor/time), modem should be known and the LAF partition should be known already too (described above).
For decryption: it works as it should. Therefore it is a little bit tricky to restore a backup of a ROM which had encrypted userdata, when you'd installed any other ROM in between. There are some points to remember when restoring, a little guide is available in old thread's third post (https://forum.xda-developers.com/showpost.php?p=77839649&postcount=3), and some tipps too.
Some instructions:
How to flash?
If starting fresh with an unmodified phone, this thread should help you installing it
When you already have TWRP installed, you can flash this recovery from within TWRP:
- Copy the new image file to one of your phone storages
- Tap "Install"
- Tap "Install image" button, located down right
- Locate your downloaded image and select it
- Select "recovery" from the list which shows up then
- Install; and reboot to recovery after installing immediately, don't use it for any other tasks until rebooted pls, as it may not function. Things can go bollox when phone wasn't rebooted to recovery after installing.
And of course you can flash it via fastbootmode. Reboot to bootloader (adb reboot bootloader; when magisk is installed, you can use magisk manager => module => menu on the top right => reboot to bootloader. You can reboot to recovery from there too) and then:
fastboot flash recovery <twrp-image-name.img>
How to (re)boot to TWRP?:
If your phone is rooted:
- Magisk has options to reboot to different targets like bootloader or recovery, but this menu is a little bit hidden: you can access it by starting Magisk.Manager, going to the "Module" menu, tapping on the three dot menu on the top right. Then select your target
- If a terminal emulator is installed, open it, type "su" followed by enter and type "reboot recovery"
- You can do the same with an adb shell, open a shell and type the commands from above, they're the same
- There also are apps for rebooting to recovery or other targets. Just search around in PlayStore
- The good old "button dance" When phone is powered off, press the volume down key and power button at the same time. When a first sign of life is seen on display, immediately release the power button, but just to instantly press it again. A menu will show, which wants you to do a factory reset: do it You have to confirm this two times, and afterwards TWRP will boot without performing a factory reset. TWRP is compiled with a flag which recognizes this procedure and hinders the bootloader to pass the command for factory resetting.
This time no optional version of TWRP is available, it's "one for all". This TWRP works for every V30 model, and only for them. I removed vendor partition too btw, there isn't any active development about that, so it's useless and only confuses ppl. DataImage function is available.
If you want to use data_image, system_image or internal storage included in data backup, first check your filesystem on your external sdcard. It needs to be capable of writing big files, which isn't the case with fat/fat16/fat32. You need exFAT (for stock) or ext4/ntfs (only available with custom kernel and/or AOSP based builds).
CHANGELOG:
February 23rd, 2020, TWRP 3.3.1-2:
- corrected blocksize for formatting crypto related partitions
- included timezone data, maybe helps some ppl with time still not showing correct; should speed up time calc
- used pre-compiled full mke2fs and e2fsdroid binaries
- enabled ntfs experimental support (rw in kernel, NTFS_3G flag in twrp / ofox)
- minimal tweaks
- enabled F2FS and NTFS support
January 1st, 2020, TWRP 3.3.1-1:
- Formatting problem solved, TWRP now removes crypto as it should when user initiates a data format
- small fixings like checkbox layout in restore menu
- Moved a LOGERR to LOGINFO: "E: Unable to decrypt FBE device". Couldn't get rid of it with our needed config...
Dec. 30th, 2019, TWRP 3.3.1-0:
- initial first version
- almost everything working like in 3.2 oreo TWRP
- Formatting your device doesn't remove crypto from disk, so a "fresh" (formatted) userdata gets disturbed by old security lock
DOWNLOADS:
Nougat, Oreo and Pie capable 3.3.1-0 TWRP, but decrypting support only for PIE (AOSP untested, stock confirmed):
Download links below (always the latest and newest only; one version for all):
File name: TWRP-JOAN-3312_2020-02-23.img
MD5sum: 2fd78a606b65274977f1cd63080d5f23
MAIN Download: MEGA, TWRP-JOAN-3312_2020-02-23.img
As always: Use it at your own risk! You are the one who changes stuff on your phone, I'm not responsible for anything which happens to your phone. TWRP is powerful, be careful at what you do with it :good: And it just works.
All you need to compile this yourself:
[url]https://github.com/seader/android_device_lge_joan-twrp[/url]
[url]https://github.com/minimal-manifest-twrp/platform_manifest_twrp_omni[/url]
[url]https://github.com/seader/android_kernel_lge_msm8998[/url] (not really needed as a prebuilt kernel is used)
[url]https://github.com/seader/bootable_recovery-twrp[/url] (copy of twrp recovery with the stuff added. Pie is "encrypt-9.0" branch. omni's android-9.0 branch almost fully compatible, beside not being able to remove crypto (dirty hack, sry )
Much appreciated for your hard work. Twrp after all is the base for all customization
Thanks!
sure, enjoy it
btw, is there someone with oreo encrypted...? would be nice to know if it's decryptable with this new twrp too, and we therefore only need this one (and the other one can be archived...?)?
which is spoken very early, there's a lot left to do for 3.3 running really flawlessly. but, of course, this will be continued and being further worked on :good: starting right now xD
@ChazzMatt: it will take a while until wtf can be updated with this new one here. this is in an late beta stage, it works but has some quirks left. nothing that can destroy a phone but this twrp isn't fully working at this point of time and therefore not possible to use "in productive threads".
Everything works as well as the previous stable recovery.
I have tried:
1. backing up and restoring ROMs
2. Flashing, ROMs(stock pie and aosp Q), kernels and other mods.
Big thanks ??
In my case time is still not correct, I have to choose a different timezone compared to actual.... When booted up normally, it is correct.
kanehun said:
In my case time is still not correct, I have to choose a different timezone compared to actual.... When booted up normally, it is correct.
Click to expand...
Click to collapse
it needs some boots and reboots to recovery. after setting up everything it showed in twrp as it should :good: i'll add the tzdata back, a registry of all timezones, used for calculation of time, maybe it helps.
Time zone is beyond screwed up, 3 hours off without DST. Also, I'm on Oreo and it's asking for the decrypt password to access internal SD.Going back to 3.2.3-7.
ldeveraux said:
, I'm on Oreo and it's asking for the decrypt password to access internal SD.Going back to 3.2.3-7.
Click to expand...
Click to collapse
Try using the Pie compatible Decryption Disabler and then Reformatting data...
Have you tried flashing the @Zackptg5 Disable_Dm-Verity_ForceEncrypt_08.18.2019 (encryption disabler) before reformatting?
Flash Magisk,
Flash Pie-compatible encryption disabler,
Flash JohnFawkes Root Checker disabler,
Reformat data (where you type yes),
Reboot to recovery from within TWRP,
Flash Magisk AGAIN,
Reboot phone.
See this post: https://forum.xda-developers.com/showpost.php?p=79972563&postcount=107
_____________
7. MORE TWRP ACTIONS - Now turn off data encryption and install essential items… all in TWRP:
(This is not a "menu" in TWRP, it's merely a list of what you NEED to do before booting to the OS)
a. Wipe Data – Factory Reset
b. Install – set storage to the External SD (if you have a microSD card) OR drag necessary files over from PC once in TWRP.
c. Install the Magisk zip. (This is to give the encryption disabler root privileges)
d. Install @Zackptg5 Disable_Dm-Verity_ForceEncrypt_08.18.2019 (encryption disabler).
e. Install @JohnFawkes AnyKernel 3 RCTD Remover (root checker disabler); this disables LG's firmware root checks, which may impede performance.
f. FORMAT DATA (Select WIPE, then FORMAT DATA, then select yes.)
Do NOT delete your OS, but you do need to FORMAT your data , not just "wipe" it this time. Otherwise you may get an encryption error when you boot up the first time. If you get any red mount errors, go back to the TWRP reboot menu and select reboot to recovery and try to FORMAT DATA again. Then, after successfully formatting...
g. Reboot – "Reboot Recovery" from TWRP reboot menu (choose to reboot back to Recovery). Now that the data partition has been formatted, TWRP needs to reload the recovery partition for usage. If you skip this step, when Magisk is installed again below, it may think that /data is still encrypted and set "preserve force encryption". This is also a good sanity check that LG encryption has been removed from /data.
h. Re-flash the Magisk zip again. (This is to make sure, due to Pie changes.)
i. Reboot – to System (NOW you are finally rebooting your phone! Until now this whole section has been done within TWRP.)
ChazzMatt said:
Try using the Pie compatible Decryption Disabler and then Reformatting data...
Have you tried flashing the @Zackptg5 Disable_Dm-Verity_ForceEncrypt_08.18.2019 (encryption disabler) before reformatting?
Flash Magisk,
Flash Pie-compatible encryption disabler,
Flash Root Checker disabler,
reformat data (where you type yes),
reboot to recovery from within TWRP,
flash Magisk AGAIN,
reboot phone.
See this post: https://forum.xda-developers.com/showpost.php?p=79972563&postcount=107
_____________
7. MORE TWRP ACTIONS - Now turn off data encryption and install essential items… all in TWRP:
(This is not a "menu" in TWRP, it's merely a list of what you NEED to do before booting to the OS)
a. Wipe Data – Factory Reset
b. Install – set storage to the External SD (if you have a microSD card) OR drag necessary files over from PC once in TWRP.
c. Install the Magisk zip. (This is to give the encryption disabler root privileges)
d. Install @Zackptg5 Disable_Dm-Verity_ForceEncrypt_08.18.2019 (encryption disabler).
e. Install @JohnFawkes AnyKernel 3 RCTD Remover (root checker disabler); this disables LG's firmware root checks, which may impede performance.
f. FORMAT DATA (Select WIPE, then FORMAT DATA, then select yes.)
Do NOT delete your OS, but you do need to FORMAT your data , not just "wipe" it this time. Otherwise you may get an encryption error when you boot up the first time. If you get any red mount errors, go back to the TWRP reboot menu and select reboot to recovery and try to FORMAT DATA again. Then, after successfully formatting...
g. Reboot – "Reboot Recovery" from TWRP reboot menu (choose to reboot back to Recovery). Now that the data partition has been formatted, TWRP needs to reload the recovery partition for usage. If you skip this step, when Magisk is installed again below, it may think that /data is still encrypted and set "preserve force encryption". This is also a good sanity check that LG encryption has been removed from /data.
h. Re-flash the Magisk zip again. (This is to make sure, due to Pie changes.)
i. Reboot – to System (NOW you are finally rebooting your phone! Until now this whole section has been done within TWRP.)
Click to expand...
Click to collapse
No, that's an insane amount of hassle for no apparent gain! I'm just sticking with the older TWRP [emoji6]
ldeveraux said:
No, that's an insane amount of hassle for no apparent gain! I'm just sticking with the older TWRP [emoji6]
Click to expand...
Click to collapse
Were you already on a decrypted ROM using the older version of TWRP? Trying to figure out if the same encrypted internal storage situation will happen to me if I bother to try this Pie version of TWRP. Just would stick with Oreo TWRP if it's going to be this whole hassle to upgrade.
Thanks!
:victory: thank you seadersn!
ldeveraux said:
No, that's an insane amount of hassle for no apparent gain! I'm just sticking with the older TWRP [emoji6]
Click to expand...
Click to collapse
It's the exact steps people have to do when installing TWRP to work with bootloader unlocked Pie KDZ.
We needed new Encryption Disabler and we needed new Root Checker Disabler and we needed to flash Magisk twice.
The order of steps had to be rewritten besides new files.
Those have been in effect ever since EU H930 got Pie. Works on Oreo AND Pie bootloader unlocked KDZ.
drewcu said:
Were you already on a decrypted ROM using the older version of TWRP? Trying to figure out if the same encrypted internal storage situation will happen to me if I bother to try this Pie version of TWRP. Just would stick with Oreo TWRP if it's going to be this whole hassle to upgrade.
Thanks!
Click to expand...
Click to collapse
I'm on the TWRP flashable US99820H, so no clue
ChazzMatt said:
It's the exact steps people have to do when installing TWRP to work with bootloader unlocked Pie KDZ.
Those have been in effect ever since EU H930 got Pie.
Click to expand...
Click to collapse
I guess. I don't have Pie and don't plan on updating soon. I don't even know what the decryption password was all about. My TWRP was working fine, I've learned one thing with Android: if it ain't broke...
ldeveraux said:
I'm on the TWRP flashable US99820H, so no clue
I guess. I don't have Pie and don't plan on updating soon. I don't even know what the decryption password was all about. My TWRP was working fine, I've learned one thing with Android: if it ain't broke...
Click to expand...
Click to collapse
Any TWRP flashable ROM was likely decrypted and is similar to my situation (except I'm on Pie VS99630c). Sounds like upgrading to TWRP 3.3.1 Pie is more hassle than it's worth and I'll stay put.
Thanks.
ldeveraux said:
I'm on the TWRP flashable US99820H, so no clue
I guess. I don't have Pie and don't plan on updating soon. I don't even know what the decryption password was all about. My TWRP was working fine, I've learned one thing with Android: if it ain't broke...
Click to expand...
Click to collapse
Sure. I'm still on stock rooted Oreo firmware, also.
But those two new files, different order of steps work with both Oreo AND Pie Bootloader Unlocked KDZ with 3 2.3.7 -- whereas the older method and (with original decryption and root check disabler files) were in place before Pie.
WTF has always had decryption and root check disabler files and reformat of data to install TWRP.
What's different now is newer files to be effective on Pie KDZ as well as different order of steps -- as well as flashing Magisk at the beginning and again at the end.
I am hoping those files and steps also work with this new TWRP 3.3.1.
---------- Post added at 05:54 PM ---------- Previous post was at 05:51 PM ----------
drewcu said:
Any TWRP flashable ROM was likely decrypted and is similar to my situation (except I'm on Pie VS99630c). Sounds like upgrading to TWRP 3.3.1 Pie is more hassle than it's worth and I'll stay put.
Thanks.
Click to expand...
Click to collapse
Those files and steps I posted work with all Pie KDZ on 3.2.3.7. If they don't work on this 3.3.1 that's strange.
ChazzMatt said:
Sure. I'm still on stock rooted Oreo firmware, also.
But those two new files, different order of steps work with both Oreo AND Pie Bootloader Unlocked KDZ with 3 2.3.7 -- whereas the older method and (with original decryption and root check disabler files) were in place before Pie.
WTF has always had decryption and root check disabler files and reformat of data to install TWRP.
What's different now is newer files to be effective on Pie KDZ as well as different order of steps -- as well as flashing Magisk at the beginning and again at the end.
I am hoping those files and steps also work with this new TWRP 3.3.1.
---------- Post added at 05:54 PM ---------- Previous post was at 05:51 PM ----------
Those files and steps I posted work with all Pie KDZ on 3.2.3.7. If they don't work on this 3.3.1 that's strange.
Click to expand...
Click to collapse
I am on John Fawkes' Pie VS99630c TWRP flashable ZIP using TWRP 3.2.3.7. The concern is whether upgrading TWRP to 3.3.1 is as simple is flashing the IMG file within TWRP 3.2.3.7, or whether we'll have to reflash multiple things in a whole list of steps. If it's the latter, then why not just stay on TWRP 3.2.3.7 which seems to do everything we need in terms of flashing Pie ROMs?
ChazzMatt said:
Those files and steps I posted work with all Pie KDZ on 3.2.3.7. If they don't work on this 3.3.1 that's strange.
Click to expand...
Click to collapse
it's only formatting data switched to "fastboot -w" (reformats cache and data) or "fastboot erase userdata" (reformats data). both remove eventually present encryptions. everything else works like in the default wtf recovery :good: and that's really an enerving point... i want to simply format my userdata in twrp and not have to switch to fastboot...
formatting now works :good:
drewcu said:
I am on John Fawkes' Pie VS99630c TWRP flashable ZIP using TWRP 3.2.3.7. The concern is whether upgrading TWRP to 3.3.1 is as simple is flashing the IMG file within TWRP 3.2.3.7, or whether we'll have to reflash multiple things in a whole list of steps. If it's the latter, then why not just stay on TWRP 3.2.3.7 which seems to do everything we need in terms of flashing Pie ROMs?
Click to expand...
Click to collapse
it's the first: flashing image easily. only thing is, as described above, removing encryption requires fastboot. atm not possible to do this in recovery as usual. therefore nod suitable for wtf thread, but for anybody else, especially the ones who have pie installed and want to acces their data in twrp when encrypted. i'll test oreo decryption compatibility soon, zip needs downloading time lol
oreo decryption compatibility not given with 3.3 but: you can easily migrate from encrypted oreo via fw zip to pie, it adopts the storage encryption then and 3.3 is able to unlock :good: i've got a solution for 3.3 not being able to remove encryption: i keep a copyof 3.2.3-7 image on external sd and install it when formatting needed xD then back to 3.3 and good to go.
workaround no more needed, working now
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.