Related
TWRP Recovery for the LG F3Q (codenames: fx3q, d520)
Background story (who ever wants to know):
As I'm currently testing around with flashing etc I hated it to re-flash the stock ROM again and again. It is sooo time consuming..
In that kind of ROM compiling learning process I also was able to build a working TWRP recovery for the LG F3Q so that was such a good feeling But as said the caveat was that because of the locked bootloader we can reach TWRP (or CWM) only when executing "adb reboot recovery" from the running system. That was not really satisfying me though..
Some day I've done a factory reset and well I saw that this is starting my TWRP recovery when executing it! Well it isn't such a surprise as TWRP sits on the recovery partition and will be triggered by the factory reset script but... well do you think what I think? When it would be possible to start TWRP fully and not that factory reset part of TWRP than we would have a workaround to reach the recovery mode without booting the system (which is in fact not possible anymore when flashing of system.img/boot.img fails)
That said.. I was in touch with the TWRP developers bigbiff and Dees_Troy and many thanks for the hint they gave me! I have build a new TWRP version based on that information I got and well the idea of that is:
Vol Down + Power -> LG Factory Reset screen appears
Confirming with power 2 times as asked
Voila: No factory reset anymore but TWRP is here!
Well that will have a caveat - READ CAREFULLY:
As you may think of the factory reset in the boot-up process and within the ROM will not working anymore until you flash another recovery!
But if you know that it is not such a caveat because you can choose the wipe options within TWRP to do a "manual" factory reset.
v2.8.1.0 build 5
USE THAT ON YOUR OWN RISK! BACKUP BEFORE!
Working (quickly tested):
Install (to flash a custom Kernel)
Mounting partitions
Reboot Recovery | System
adb shell (also see known issues)
Backup (compressed | uncompressed | encrypted (!) | unencrypted)
Restore (unencrypted | encypted (!) | compressed | uncompressed)
Internal storage /data/media
MTP which mounts the external storage!
File Manager
Terminal Command
Power charging while in TWRP
Displaying CPU temp
Totally untested:
WIPE (should work)
decrypting /data (but should work as it do so for encrypted backups already)
Every option which is not stated as "Known issue" or "Working"
Known issues (with workarounds):
ADB works only when screen "timed out" (manual locking does not help it must time out) therefore ADB can take up to 1 minute after boot until it becomes available (because screen need to be timed out first)
Workaround: set the time limit in the screen menu to e.g. 10 sec (that is the default value for now)
Timezone is not set correctly (that seems to be a well known bug in several devices using TWRP.... )
Workaround: set a timezone which displays the most accurate timezone
Known issues (without workarounds):
When you use the "Power Off" option in the "Reboot" menu the device will reboot instead of powering off
Wiping /data not possible after "factory reset buttons" used. You need to choose "wipe" and then "format data" manually (or use mke2fs on CLI).
Vibration is not working (I will not fix that atm because I like it that way)
Hardware keys at bottom doesn't work
If you use the factory reset button /data partition will be inaccessible and need to be re-flashed (means you will LOOSE your app and system configs when you use factore reset)
Download:
Attached you will find the TWRP v2.8.1.0 version ready to use even with locked bootloader:
BACKUP EVERYTHING BEFORE USING THIS. USE AT YOUR OWN RISK!
DD Image file:twrp_v2.8.1.0_build5_fx3q_FR-OFF.img.zip = FactoryReset is disabled / TWRP will be loaded instead (also see known issues)
Read the Installation & Usage instructions in this thread on how to install that file.
Installation & Usage instructions
Pre-Requirements
Read the FAQ
YOU NEED ROOT! (check FAQ)
YOU SHOULD do a NANDroid BACKUP! (check FAQ)
You need to boot up, enable USB debugging and then connect USB cable.(check FAQ get ROOT - the link contains a guide on that)
You better doing a NANDroid backup right? (I mentioned that before - but DO it! NOW!)
For the best usage experience install the sediKERNEL or use joel's debloated stock ROM which includes it already
Bulletproof Method 1: "the average user"
Use this guide if you simply want to install & use TWRP like it should be. If you're unsure use this guide!
Install:
Download the TWRP recovery file and unzip it
copy it to your device (e.g. adb push or simply copy & paste by your file browser)
Download the loki_tool (https://github.com/djrbliss/loki/raw/master/bin/loki_tool)
copy loki_tool to your device (e.g. adb push or simply copy & paste by your file browser)
execute:
adb shell
su (you may need to grant permission)
mount -oremount,rw /system
cp /PATH-WHERE-YOU-COPIED/loki_tool /system/bin/ && chmod 755 /system/bin/loki_tool
loki_tool flash recovery /PATH-WHERE-YOU-COPIED/twrp_X.X.X.X_recovery_FRoff/off.img
reboot recovery --> you should see the TWRP screen
Usage (sediKERNEL v2.0 or higher installed):
Power on the device
when you see the LG logo the first time do NOTHING!!
When the screen goes black THEN press Volume UP + Volume DOWN. Both the same time and hold them pressed.
Release the buttons when the screen goes black again
Wait. You will see the LG logo a third time and then you will see the recovery screen!
If you see a kernel crash then you have pressed the magic keys too early! Read and follow the above steps carefully and you should be fine.
Usage (without sediKERNEL v2.0 or higher):
boot into your ROM
execute "adb reboot recovery" from your PC or open a Terminal on your device and execute "su" then "reboot recovery"
Bulletproof Method 2: "developers only"
This is the developers preferred way of installing TWRP. It ensures that even when your ROM or Kernel gets damaged that you still be able to boot into recovery. This is to the developers or heavy testers who are knowing what they do ONLY!
But even when you think this is for you: Read the important hint at the end before deciding if you want to choose this method.
Install:
flash recovery image to your RECOVERY partition:
adb shell su -c dd if=/storage/external_SD/twrp_vXXXXX_fx3q_FR-OFF.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
adb reboot recovery
A user reports the the by-name does not worked for him but this one:
adb shell su -c dd if=/storage/external_SD/twrp_vXXXXX_fx3q_FR-OFF.img of=/dev/block/mmcblk0p17
-> If you can see TWRP now everything is fine - Otherwise DO NOT continue!
BACKUP YOUR WHOLE DEVICE NOW! I highly recommend to backup everything except /data from within TWRP because it is easy and works (from TWRP v2.8build5 or higher)
BACKUP /data is recommended to be done NOW and this way:
adb shell su -c dd if=/dev/block/platform/msm_sdcc.1/by-name/userdata of=/external_sd/userdata_backup_stock.img
--> This can take a long while but it contains also the backup for the internal storage not only /data and that internal part is not backupable over TWRP
while in TWRP flash the same recovery image to your BOOT partition now (do not think that this is dangerous. The boot partition is not a magic thing or so it is only the partition which will be started from the bootloader thats all about it. So yes you can install a recovery image on the boot partition without any harm.):
adb shell su -c dd if=/external_sd/twrp_vXXXXX_fx3q_FR-OFF.img.loki of=/dev/block/platform/msm_sdcc.1/by-name/boot
watch carefully that the process ended without errors and that the size is exactly the same as it should be (about 1,3GB)
adb shell sync
power off the device by taken out the battery (do not use reboot or something we want to be sure that the next step is absolutely really the normal boot up)
Boot up normally --> you should see TWRP !! You're NOT in recovery mode you're booting the normal boot mode!
Go on with flashing the sediKERNEL into your RECOVERY partition:
Download the sediKERNEL from here (the stock one could work, too but never tested ...)
push it to your device with adb or MTP (since v2.8build5)
Flash the sediKERNEL to your RECOVERY partition:
adb shell su -c dd if=/external_sd/sediKERNEL_JB-vXXXX.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
Reboot into Recovery by using TWRP GUI or by executing "adb reboot recovery"
Your ROM will boot.
Usage:
From now on every time your device booting up you will see the TWRP screen and need to choose Reboot-->Recovery to boot your ROM.
This is the absolute best way to use TWRP if you want to be sure that you will reach the recovery even when your ROM gets damaged and is confirmed to work very well (as always guarantees are not available )
Important hint:
Be sure that you keep in mind that from now on your recovery and boot partition are not the same anymore (you can always revert back to the normal behaviour, of course!). So if you want to flash a kernel image you need to ensure that it goes to the RECOVERY partition instead of the normal BOOT partition (because on boot partition is TWRP now).
If I got my ROM working I will definitively add an option to the installer where this will be ensured and I asked @joel.maxuel for his stock ROM to add that, too. As for now we are the only ones who are developing for the F3Q so you should be save enough atm but you will need to keep that always in mind when you want to replace the kernel and/or ROM.
What would happen if you forget about that? Well nothing really bad because when you install a kernel or ROM the boot image partition simply gets overwritten and that means only that your TWRP is not there anymore but the system will boot (if the new kernel/ROM is not buggy or damaged). You then could install TWRP by method 1 or using method 2 by using the boot image/Kernel you want to install.
Damage your device - booting (NOT RECOMMENDED will loose /data ):
You probably NEVER want to use this method. It is here for reference only.
I highly recommend to choose one of the above bulletproof versions instead of this one because it WILL damage /data and you need to restore that whole partition afterwards.
All my tests has shown that this comes not from TWRP (in one of my tests I disabled everything in the sourcecode of TWRP which wipes /data) but coming from LG itself. The factory reset button/option do something with the /data partition sturucture and afterwards you cannot use that anymore. I also tried to restore the partition info by trying all backup superblocks but that doesn't worked. No backup superblock is accessible.
Restoring them by mke2fs and e2fsck does not work unfortunately.. (mke2fs -S /dev/block/platform/msm_sdcc.1/by-name/userdata && e2fsck -yf /dev/block/platform/msm_sdcc.1/by-name/userdata)
So if you have loosed your /data and/or internal storage you need to have a DD imaged backup near.
Install:
same as for "Bulletproof Method 1" above
Usage:
When you choosen FR-OFF then TWRP will be able to start without booting up the whole system (also see known issues):
Power Off the device (remove battery)
Vol Down + Power --> Then put the battery back --> LG Factory Reset screen appears
Confirming with power button 2 times as asked - if you downloaded and flashed the FRoff version of TWRP it will NOT open the normal reset procedure but /data and the internal storage are not accessible afterwards (read above about the details). That means your app configs and systems configs get lost that way. You have been warned!
Voila: No (full) factory reset anymore but TWRP is here when you have damaged your ROM or for some dev approach
If you want the factory reset back simply choose the file twrp_2.7.1.0_recovery_FRon.img.lok and follow the above instructions. Afterwards you will have TWRP but it will be reachable only when you execute "adb reboot recovery" from the running system.
XDA:DevDB Information
sediTWRP for LG Optimus F3Q, Tool/Utility for the General Discussion
Contributors
xdajog
Source Code: https://github.com/xdajog/bootable_recovery_twrp_fx3q
Version Information
Status: Stable
Current Stable Version: v2.8.1.0 build 5
Stable Release Date: 2014-11-18
Created 2015-05-19
Last Updated 2015-07-20
FAQ
Frequently Asked Questions (FAQ)
What is that "adb" thing?
adb stands for: Android Debug Bridge and can help a lot when it comes to work with your device. It is not for developers only but they use it a lot of course.
But a normal user can use this to exchange files without the need of mounting, backing up the device, reboot the device and use it as a very comfortable way of having a terminal emulator.
Normally adb itself is not available as a standalone application - it comes with the Android SDK which is very big and heavy if you want to use adb and/or fastboot (another great tool) only.
But we live in a great world with many people wanting to make things easy so here you go when you want/need only adb and fastboot:
download & install adb at lifehacker
(Direct link for Windows users: Go to easy ADB install thread)
How to get root for the F3Q?
Here is the tool and guide: Saferoot
[*]What is a "nandroid" backup?
nandroid means essentially: "a full image of all your partitions" so it is a full snapshot of your ROM including all your apps and contents.
The name NANDroid is a portmanteau of "NAND" (as in Flash memory - NAND flash) and "Android." (Source)
[*]How to create a "nandroid" backup?
(See above for the meaning of "nandroid backup")
You have several options on how to do that.
The normal and absolutely recommended way is to do that "offline" (from within recovery mode) but you can also do it "online" (while Android is running).
.
Offline nandroid backup by using TWRP recovery: Guide
If you have no custom recovery installed read on.
.
Online nandroid backup:
by using an app:
There is 1 (known to me) "online" nandroid backup tool available which will backup from within your running Android: PlayStore.
I tested it and still using it since a while and I really like it but I would not fully resist on it.
I had no problems backing up but sometimes an app is lost when restoring. This may have been fixed but well it is like imaging a running Windows or Linux system:
Do not do it online if you can - it may/will work but there could be problems/inconsistencies later!!
If you never made a nandroid before doing it online will not harm anything and should be your first start. So install the Online Nandroid backup tool and begin.
Check out this guide for some hints: Guide
(If you like the Android app do not hesitate to buy the unlock key to support the developer!)
by using commandline tools:
First of all you need "adb" installed (check out the FAQ answer number 1 above).
Then you need someone who is telling you the device partition table and you need a big sized SD card to hold the images.
The reason is that you will use a special command named "dd" which images the whole partition (not the content only!).
dd is a VERY dangerous tool because if you use it wrong your device may get bricked so it is essential that you are using the
correct command and check that twice!
Check out the next FAQ on how to do this for the F3Q.
[*]How to create a "nandroid" backup for the F3Q - WITHOUT having a custom recovery?
The whole process will take a big amount of time but it is worth to follow each step including the md5sum checks at the end.
Please read the previous FAQ first because there you will find more information about background and other options you may have.
Ensure you have a SD card inserted which is big enough and having enough free space available (4GB at least! I recommend at least 8 GB but this depends on the size of your current data partition. A completely stock ROM with nothing installed and unused will need 3 GB space).
.
Install "adb" on your pc (check out the FAQ #1 above).
root your device (check out FAQ #2 above)
connect with adb to your (running) F3Q:
adb shell
(you should see a prompt)
su
(you need to grant permission if you haven't yet)
Then backup your current ROM and data:
dd if=/dev/block/platform/msm_sdcc.1/by-name/system of=/storage/external_SD/system.2015-07-20.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/storage/external_SD/boot.2015-07-20.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/userdata of=/storage/external_SD/userdata.2015-07-20.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/recovery of=/storage/external_SD/recovery.2015-07-20.img
# If you never backed up your EFS you really should do that once:
dd if=/dev/block/platform/msm_sdcc.1/by-name/modemst1 of=/storage/external_SD/modemst1.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/modemst2 of=/storage/external_SD/modemst2.img
Click to expand...
Click to collapse
Just to be sure you can do an online backup now, too ( Guide ) Online Nandroid backup App
.
copy the backup(s) to your device (connect USB cable - open your external storage and drag&drop) <--- DO NOT SKIP THIS STEP!!!! It is absolutely essential!
Check your copy on your device:
md5sum /storage/external_SD/system.2015-07-20.img
md5sum /storage/external_SD/boot.2015-07-20.img
md5sum /storage/external_SD/userdata.2015-07-20.img
md5sum /storage/external_SD/recovery.2015-07-20.img
md5sum /storage/external_SD/modemst1.img
md5sum /storage/external_SD/modemst2.img
Click to expand...
Click to collapse
Download a md5sum checker like this one Windows MD5 and load each file you copied to it (on Linux the "md5sum" command can be used of course).
compare the md5sums from the above output and ensure that they are all matching.
[*]Why is factory reset not working when installing TWRP? (or: AAAAaaaah my /data is inaccessible after doing a factory reset!!!!)
All my tests has shown that this comes not from TWRP (in one of my tests I disabled everything in the sourcecode of TWRP which wipes /data) but coming from LG itself. The factory reset button/option do something with the /data partition sturucture and afterwards you cannot use that anymore. I also tried to restore the partition info by trying all backup superblocks but that doesn't worked. No backup superblock is accessible.
Restoring them by mke2fs and e2fsck does not work unfortunately.. (mke2fs -S /dev/block/platform/msm_sdcc.1/by-name/userdata && e2fsck -yf /dev/block/platform/msm_sdcc.1/by-name/userdata)
So if you have loosed your /data and/or internal storage you need to have a DD imaged backup near. Sorry but you have been warned (known issues) before.
.
if you want the factory reset back simply choose the file twrp_2.7.1.0_recovery_FRon.img.lok and follow the above instructions. Afterwards you will have TWRP but it will be reachable only when you execute "adb reboot recovery" from the running system. v2.7. is not recommended to use but atm the only option if you really want that. Instead I would better try the wipe options from within TWRP and re-installing your ROM of choice or simply using the official LG flashing tool to get your F3Q fully reset.
.
History / Changelog
Previous development (v2.7.1.0)
I HIGHLY RECOMMEND USING v2.8 instead of this version!
You have been warned.. If you still want that buggy version go on here:
USE THAT ON YOUR OWN RISK! I STRONGLY RECOMMEND TO BACKUP EVERYTHING BEFORE PROCEEDING.
Working:
Install (to flash a custom Kernel)
Mounting partitions (see known issues for the internal one)
Reboot Recovery | System
adb shell
File Manager
Terminal Command
Totally untested:
WIPE (may work)
Known issues:
If the device becomes locked and then unlocked by the user adb will restart on the device (or crash and start again. haven't had looked into that yet)
When you use the "Power Off" option in the "Reboot" menu the device will reboot instead of powering off
RESTORE (will NOT work!)
BACKUP (will NOT work!)
You cannot mount the external sd via USB or MTP
Vibration is not working (I will not fix that atm because I like it that way)
Timezone is not set correctly (that seems to be a well known bug in several devices using TWRP....
Internal storage is missing (/data/media)
Hardware keys at bottom doesn't work
If you use the factory reset button /data partition will be inaccessible and need to be re-flashed (means you will LOOSE your app and system configs when you use factore reset)
Download:
Attached you will find the loki'ed TWRP version (v2.7.1.0):
AGAIN: THIS IS A PROOF-OF-CONCEPT only. It definitively WILL have bugs and problems! I want to proof that it will be possible to have TWRP on this device and also have a way to boot up into TWRP without booting the whole system.
twrp_2.7.1.0_recovery_FRoff.img.lok = FactoryReset is disabled / TWRP will be loaded instead
twrp_2.7.1.0_recovery_FRon.img.lok = FactoryReset is enabled / TWRP can be reached with "adb reboot recovery" only
Read the Installation & Usage instructions in the OP on how to install that file.
Awesome work! Saves having to risk modifying the bootloader (for now). :laugh: :highfive: Thanks!
xdajog said:
TWRP Recovery for the LG F3Q / D520
...
Click to expand...
Click to collapse
I'm unable to get logs from TWRP, it does crash reliably when messing about in settings and such.
Timezone fix is needed. (Devices time is set to the correct local time, but TWRPs timezones arent correct.)
Device does not show internal storage.
Wipe menu does not differentiate from internal storage and /data
there's no /mnt, /storage or /sdcard present while in TWRP.
Uhm, I'm sure there's some more I've missed, but that's all I've got for now.
eriklion said:
I'm unable to get logs from TWRP, it does crash reliably when messing about in settings and such.
Click to expand...
Click to collapse
Uhm what do you mean? adb shell and then open /tmp/recovery.log? Clicking on the small mini icon at middle bottom of the screen? Both working for me. Have you tested the above attached version or the one I gave you at dropbox? The above is a more current one!
Timezone fix is needed. (Devices time is set to the correct local time, but TWRPs timezones arent correct.)
Click to expand...
Click to collapse
hm I will look into that
Device does not show internal storage.
Click to expand...
Click to collapse
yeah forgot to mention that. Is that shown in CWM btw?
Wipe menu does not differentiate from internal storage and /data
Click to expand...
Click to collapse
Could you explain what does that means?
there's no /mnt, /storage or /sdcard present while in TWRP.
Click to expand...
Click to collapse
/mnt and /storage are not needed or am I wrong? /sdcard would point to the internal storage I think but I decided to use /external_sd instead which is accessible in the latest version.
Finally got around to test. Looks great, I love having TWRP over CWM!
Unfortunately the backup function is not working. TWRP errors out and reloads itself. I have a pastebin, sorry it's so long but I wanted to try a couple different backup options before I gave up and produced a log file:
http://pastebin.com/QUfNw6Rk
The portions of interest are:
Code:
Backing up Cache...
I:Creating backup...
I:Creating tar file '/external_sd/TWRP/BACKUPS/1db9cba/1970-01-24--22-43-59 JZO54K//cache.ext4.win'
I:addFile '/cache/recovery' including root: 0
Failed to get selinux context: Operation not supported on transport endpoint
I:addFile '/cache/recovery/log' including root: 0
Failed to get selinux context: Operation not supported on transport endpoint
...
Code:
Backing up Data...
I:Creating backup...
I:Creating tar file '/external_sd/TWRP/BACKUPS/1db9cba/1970-01-24--22-43-59 JZO54K//data.ext4.win'
I:addFile '/data/dontpanic' including root: 0
Failed to get selinux context: Operation not supported on transport endpoint
I:addFile '/data/dontpanic/last_kmsg0' including root: 0
Failed to get selinux context: Operation not supported on transport endpoint
I:addFile '/data/dontpanic/next_count' including root: 0
Failed to get selinux context: Operation not supported on transport endpoint
I:addFile '/data/dontpanic/last_kmsg1' including root: 0
Failed to get selinux context: Operation not supported on transport endpoint
I:addFile '/data/dontpanic/last_kmsg2' including root: 0
Failed to get selinux context: Operation not supported on transport endpoint
I:addFile '/data/dontpanic/last_kmsg3' including root: 0
Failed to get selinux context: Operation not supported on transport endpoint
I:addFile '/data/dontpanic/last_kmsg4' including root: 0
Failed to get selinux context: Operation not supported on transport endpoint
I:addFile '/data/dontpanic/last_kmsg5' including root: 0
Failed to get selinux context: Operation not supported on transport endpoint
I:addFile '/data/dontpanic/last_kmsg6' including root: 0
Failed to get selinux context: Operation not supported on transport endpoint
I:addFile '/data/dontpanic/last_kmsg7' including root: 0
Failed to get selinux context: Operation not supported on transport endpoint
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
Starting TWRP 2.7.1.0 on Sun Jan 25 03:44:01 1970
I:Single storage only.
I:No internal storage defined.
I:No storage defined, defaulting to /sdcard.
I:Lun file '/sys/devices/platform/usb_mass_storage/lun0/file' does not exist, USB storage mode disabled
I:Found brightness file at '/sys/class/leds/lcd-backlight/brightness'
I:TWFunc::Set_Brightness: Setting brightness control to 255
Starting the UI...Pixel format: 480x800 @ 32bpp
Pixel format: RGBX_8888
Not using qualcomm overlay, 'msmfb43_80201'
framebuffer: fd 4 (480 x 800)
=> Linking mtab
=> Processing recovery.fstab
I:Processing '/boot'
I:Processing '/cache'
I:Processing '/data'
I:Processing '/misc'
I:Processing '/recovery'
I:Processing '/external_sd'
I:Processing '/system'
I:Creating Android Secure: /external_sd/.android_secure
I:Backup folder set to '/external_sd/TWRP/BACKUPS/1db9cba'
I:Settings storage is '/external_sd'
Updating partition details...
I:Unmounting main partitions...
E:Unable to unmount '/data'
I have a stock based ROM to test, and I want to make sure I can enter recovery through the bootloader should things go sour. If TWRP can backup and restore, that allows me to go back to my true stock after the test. Any ideas?
joel.maxuel said:
Finally got around to test. Looks great, I love having TWRP over CWM!
Unfortunately the backup function is not working. TWRP errors out and reloads itself. [.....] Any ideas?
Click to expand...
Click to collapse
Yes.
There are several things coming in place when it comes to backing up out of TWRP atm...
You hopefully have read the big fat red warning ? What I mean is the part regarding /data gets lost when you do a factory-reset
That said if you have entered TWRP by pressing the physical keys your /data partition will be wiped (really bad thing but that it is made for and I haven't had the time to look into that further)
The result is a cleaned /data which is not mountable until you format it with mke2fs.
(e.g.: "adb shell mke2fs -T ext4 /dev/block/mmcblk0p15")
If you do not do that what MAY happens is that TWRP failing because of missing /data (and if not then you should ensure that /data was really backed up)
But as your log told me it seems to be not the problem here 'cause the /data partition is detected by TWRP. so it could be 2)
Mounting points.
As stated the mount points are not fully working in TWRP atm. That means when it comes to /sdcard which is the internal device storage it will fail, too because it cannot be found. The reason for this is that LG mounts /sdcard by the sdcard service but that is somehow tricky thats why it is not working atm.
And on top: the internal storage normally needs to be mounted to "/data/media" especially when we want to use MultiROM later.
So +1 for /sdcard or/and internal storage related
background info: http://teamw.in/DataMedia
The last one I could imagine is "something else" which could be catched by "/proc/last_kmsg"
The important thing is that this file gets written only after a crash and when the battery was not removed. So if the device reboots to TWRP again try to adb shell to the device and then paste the last_kmsg again. Maybe we can find something here.
When I will continue on TWRP I think of upgrading to v2.8 because they enable MTP here which could be good for copying data between device and pc..
BTW:
I have no idea what CWM port which is also be available would do in case of starting a backup especially what will REALLY gets backed up!!!!
IMHO the best way on doing a nandroid backup atm is "adb shell dd ...." Takes a long time but then you can be sure. I can give you all the mountpoints if you need them.
As I currently have not such much success with porting the ROM I will now come back here to TWRP and will finish it to have a hopefully fully working recovery. I cannot say the timeline for this but it will definitively be the next what I want to do because when this is done I can better match the rest for the ROM.
xdajog said:
<SNIP>
IMHO the best way on doing a nandroid backup atm is "adb shell dd ...." Takes a long time but then you can be sure. I can give you all the mountpoints if you need them.
As I currently have not such much success with porting the ROM I will now come back here to TWRP and will finish it to have a hopefully fully working recovery. I cannot say the timeline for this but it will definitively be the next what I want to do because when this is done I can better match the rest for the ROM.
Click to expand...
Click to collapse
This should work (I've done it before for eriklion):
Code:
adb shell
dd if=/dev/block/platform/msm_sdcc.1/by-name/system of=/storage/external_SD/system.2014-11-12.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/storage/external_SD/boot.2014-11-12.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/cache of=/storage/external_SD/cache.2014-11-12.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/userdata of=/storage/external_SD/userdata.2014-11-12.img
Now, is there a recommended adb command to wipe data and cache, since factory reset function is not the best choice? I see a few with the following process...
Code:
adb shell
su
format DATA
format CACHE
...but not much commentary on it.
I appreciate the second (third, whatever you are on) crack at TWRP. Hopefully the next version will squash the bugs. Btw, I will see if I can provide a /proc/last_kmsg tonight have posted a last_kmsg here.
joel.maxuel said:
This should work (I've done it before for eriklion):
Code:
adb shell
dd /dev/block/platform/msm_sdcc.1/by-name/system /storage/external_SD/system.2014-11-12.img
dd /dev/block/platform/msm_sdcc.1/by-name/boot /storage/external_SD/boot.2014-11-12.img
dd /dev/block/platform/msm_sdcc.1/by-name/cache /storage/external_SD/cache.2014-11-12.img
dd /dev/block/platform/msm_sdcc.1/by-name/userdata /storage/external_SD/userdata.2014-11-12.img
Click to expand...
Click to collapse
yes thats all you need to backup & restore
joel.maxuel said:
Now, is there a recommended adb command to wipe data and cache, since factory reset function is not the best choice? I see a few with the following process...
Code:
adb shell
su
format DATA
format CACHE
...but not much commentary on it.
I appreciate the second (third, whatever you are on) crack at TWRP. Hopefully the next version will squash the bugs. Btw, I will see if I can provide a /proc/last_kmsg tonight.
Click to expand...
Click to collapse
I always do it that way:
Code:
Starting TWRP
adb shell
("su" in TWRP not needed normally)
mke2fs -T ext4 /dev/block/mmcblk0p15 (for userdata)
mke2fs -T ext4 /dev/block/mmcblk0p14 (for cache)
Then you can be sure it is clean and well formatted. ext4 is for both cache and userdata and works fine for me.
twrp v2.8 with many enhancements and fixes is on its way
Stay tuned ....
if you get bored in the meanwhile ... click thanks
Is someone here with running the stock ROM (or absolutely not modified means formatted! /data partition) who is willing to give me a quick help? It must be stock or placed back to stock by using a backuped image dump if you have one.
The following need to be done in recovery so you need to have CWM or TWRP installed. Boot into recovery (adb reboot recovery) and then use "adb shell" to connect.
I need your output of this command:
Code:
mke2fs -n /dev/block/platform/msm_sdcc.1/by-name/userdata
This will not do/destroy/modify anything.
It should display some information about that partition. Read the details here http://linux.die.net/man/8/mke2fs
The reason is that LG factory reset seems to wipe superblocks (wanted by LG or not - fact is that they are thrown) and THEN forwarding to the recovery tool like TWRP but to be sure I need the above output from 1 or 2 people to be sure enough on how to proceed.
Thanks in advance
As Joel investigated that may destroy /data cause of a buggy version of mke2fs!! Oh man..
-----
Sent from my SGH-I927 using XDA Android mobile app
Ok thx to joel I'm able to investigate the LG facotry reset further.
In parallel I will try another way which will be (if I get it working) absolutely smooth and will not have such workaround character like the current idea (hijacking factory reset).
Give me some time but if that works it would be a great solution for accessing recovery..
Stay tuned some good things may happen...
-----
Sent from my SGH-I927 using XDA Android mobile app
Finally v2.8 for F3Q has arrived !!! I think a very good approach now!
Have fun and as usual any thx click.... and so on
Check out the OP for Download and details:
http://forum.xda-developers.com/showpost.php?p=55239027&postcount=1
UPDATE:
I have completely reworked the "Installation & Usage instructions" section in the OP. PLEASE READ and be happy
xdajog said:
Finally v2.8 for F3Q has arrived !!! I think a very good approach now!
Have fun and as usual any thx click.... and so on
Check out the OP for Download and details:
http://forum.xda-developers.com/showpost.php?p=55239027&postcount=1
UPDATE:
I have completely reworked the "Installation & Usage instructions" section in the OP. PLEASE READ and be happy
Click to expand...
Click to collapse
Great work.
Am looking at method two. If I was to install a ROM, wouldn't the boot partition (thus my new recovery) be overwritten by the ROM package's boot.img? And when I was cooking with the Kitchen, the ROM required a specific mount point for the boot partition. If it is supposed to point to recovery, seems to me that neither would boot (overwritten recovery, ROM pointing in the wrong location).
So, what is this solution getting around? So we have an option to load TWRP before a system we don't necessarily trust will boot? Thus avoiding the bootloader fallback even more? Or is it a broken boot.img breaks TWRP as well so even if we try to go in through the bootloader, TWRP fails to load as well?
Sorry for my confusion, still trying to grasp all this new information.
joel.maxuel said:
Great work.
Click to expand...
Click to collapse
Thanks
Am looking at method two. If I was to install a ROM, wouldn't the boot partition (thus my new recovery) be overwritten by the ROM package's boot.img?
Click to expand...
Click to collapse
Method 2 will suggest that if you install a custom ROM that you are be able to use/choose the boot.img partition (I hoped that the "hint" at the was clear enough but better to ask of course!)
And when I was cooking with the Kitchen, the ROM required a specific mount point for the boot partition. If it is supposed to point to recovery, seems to me that neither would boot (overwritten recovery, ROM pointing in the wrong location).
Click to expand...
Click to collapse
Well yes you either need to point to the recovery partition or (and that would be what I recommend) you let the user choose what he wanted to do.
So, what is this solution getting around?
Click to expand...
Click to collapse
The best we can do here (and that is what I will do for my custom ROM if I get it done some day) to use AROMA installer and ask the user if he has a recovery installed in the boot partition or not. Then you can choose what to do in the updater script.
I uploaded an example of my AROMA installation setup for the "sediROM for Samsung Captivate Glide" in this post. This one is VERY complex but you will get the idea and many input on how to do things.
So we have an option to load TWRP before a system we don't necessarily trust will boot? Thus avoiding the bootloader fallback even more?
Click to expand...
Click to collapse
Yes using method 2 we have always coming TWRP up when powering on the device. We then can choose to do things in there or to boot to "recovery" which will be the ROM. What do you meant with "bootloader fallback"?
Or is it a broken boot.img breaks TWRP as well so even if we try to go in through the bootloader, TWRP fails to load as well?
Click to expand...
Click to collapse
Not sure If I got you. When the boot partition gets overwritten TWRP and any possibility to get into TWRP will be lost because it sits only in the boot partition when using method 2. If you choose to do a factory reset when powering on the device or from within the ROM I have no idea what happens then unfortunately. That is untested but if you willing to test..
Sorry for my confusion, still trying to grasp all this new information.
Click to expand...
Click to collapse
No worry about that happy if that is useful for someone
xdajog said:
I uploaded an example of my AROMA installation setup for the "sediROM for Samsung Captivate Glide" in this post. This one is VERY complex but you will get the idea and many input on how to do things.
Click to expand...
Click to collapse
Thanks! I will take a look at this in the next few days.
xdajog said:
Yes using method 2 we have always coming TWRP up when powering on the device. We then can choose to do things in there or to boot to "recovery" which will be the ROM. What do you meant with "bootloader fallback"?
Click to expand...
Click to collapse
Bootloader fallback as in having to access TWRP via the bootloader. Our regular method is to access form the ROM, but if the ROM is bricked for whatever reason, the fallback is through the bootloader.
xdajog said:
Not sure If I got you. When the boot partition gets overwritten TWRP and any possibility to get into TWRP will be lost because it sits only in the boot partition when using method 2. If you choose to do a factory reset when powering on the device or from within the ROM I have no idea what happens then unfortunately. That is untested but if you willing to test..
Click to expand...
Click to collapse
I was alluding to the scenario if one was to choose method one, installed a ROM, and things got busted badly... Would you even be able to access TWRP with a bad boot partition? I think so, because recovery partition should be self sufficient (I think you proved it by swapping their places by way of method two), it is just getting into recovery by way of bootloader) I don't particularly like.
Had to face that fear last night, and ultimately, TWRP started up fast enough from the bootloader that it seemed like nothing happened, but when i went to dump the log, it could not recognize the sdcard. DD'ing my userdata partition back fixed that issue.
joel.maxuel said:
Bootloader fallback as in having to access TWRP via the bootloader. Our regular method is to access form the ROM, but if the ROM is bricked for whatever reason, the fallback is through the bootloader.
Click to expand...
Click to collapse
You mean "factory-reset" right? By either pressing the factory reset buttons (or by choosing from within the ROM) correct?
I was alluding to the scenario if one was to choose method one, installed a ROM, and things got busted badly... Would you even be able to access TWRP with a bad boot partition? I think so, because recovery partition should be self sufficient (I think you proved it by swapping their places by way of method two), it is just getting into recovery by way of bootloader) I don't particularly like.
Click to expand...
Click to collapse
If you install TWRP with method 1 and your boot partition gets corrupt you still be able to reach TWRP by using the factory-reset buttons. But you will loose /data then.
If you install TWRP with method 2 and your boot partition has gone you can not start TWRP anymore because it sits on there.
So you're more bulletproof by choosing method 1 because you would reach TWRP even when the boot partition gets damaged but you will loose /data then! Mentioned in the known issues in the OP.
Had to face that fear last night, and ultimately, TWRP started up fast enough from the bootloader that it seemed like nothing happened, but when i went to dump the log, it could not recognize the sdcard. DD'ing my userdata partition back fixed that issue.
Click to expand...
Click to collapse
When you have TWRP installed with method 1 you will reach TWRP by factory reset buttons and it will DO NOTHING ! Really! It simply starts TWRP because I patched TWRP that way that it will not wipe anything when triggered by the factory-reset command / button!
I can say that for double sure since today because:
1) In one of my tests I had disabled REALLY EVERY wipe option within TWRP - compiled it - installed it and even then /data gets lost!
2) I have installed the BOOT image means KERNEL on the RECOVERY partition today again and then used the factory-reset buttons again (after I restored /data of course)... and /data gets lost AGAIN--?!!
That means even when there is absolutely no custom recovery in place (like TWRP) which would normally handle wiping /data then nevertheless /data gets corrupted! I have tested that twice so I can say now for sure that this has nothing to do with TWRP but it comes from the LG bootloader instead! That bootloader is CRAP. sorry.
I had tested one approach which is build in boot image RAM disk which catches the keys which are pressed and then reboot into recovery. That would work but only as long as you have a working boot image partition. So that is the same good/bad as having TWRP sitting within the boot partition which is much easier to do so I decided to go this way for now.
One last word about the crappy factory-reset by LG: I have tried a lot to find out what really happens to the partition or partition table of /data when those keys are pressed but the only thing I can say is that the superblocks are inaccessible and the same for the backup superblocks. doing a "mke2fs -S" does not work (and wouldn't fix the root cause of the issue) and I have no idea what LG do here. Therefore cannot fix that ..
so I believe we will need to live with one of the 3 methods described in the OP....
Hope that answered some of your questions...
Bad news..
The Desire Z of my wife is completely broken now.
That means I cannot develop anymore..
- I ported and released the latest TWRP version to the F3Q
- I'm able to build AOSP JellyBean (not booting yet though),
- I compiled and released a custom AOSP Kernel (named sediKERNEL)
.... and a lot more..
I have everything I need to continue here in place...
I have the will and the ability to continue...
But no device anymore..
If someone has a F3Q to give away.. then I will continue but I'm not willing to buy a F3Q for developing only. So if you have an idea how we could continue let me know.
Update:
Check out the following link if you want to help http://forum.xda-developers.com/showthread.php?t=2952919
Otherwise that will end here for me unfortunately...
Hopefully not.
Yours
Xdajog.
-----
Sent from my SGH-I927 using XDA Android mobile app
I will update the installation instructions soon!
Because of the new sediKERNEL v2.0 the instructions will be made bullet proof only .. and i try to do it more detailed @Kediil
-----
Sent from my SGH-I927 using XDA Android mobile app
Team Win Recovery Project 3.X+, or twrp3for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface,but you can use hardware buttons too.The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Features since 3.1.0-0
vold decrypt on a few select HTC devices, TWRP will now attempt to use the system partition's vold and vdc binaries and libraries to decrypt the data partition (nkk71 and CaptainThrowback)
adb backup to stream a backup directly to or from your PC, see documentation here (bigbiff)
tweak MTP startup routines (mdmower)
support new Android 7.x xattrs for backup and restore to fix loss of data after a restore (Dees_Troy)
support POSIX file capabilities backup and restore to fix VoLTE on HTC devices and possibly other issues (Dees_Troy)
better indicate to users that internal storage is not backed up (Dees_Troy)
improve automatic determination of TW_THEME (mdmower)
minimal getcap and setcap support (_that)
try mounting both ext4 and f2fs during decrypt (jcadduono and Dees_Troy)
shut off backlight with power key (mdmower)
timeout during FDE decrypt (Dees_Troy and nkk71)
support for FBE decrypt and backing up and restoring FBE policies (Dees_Troy)
boot slot support (Dees_Troy)
TWRP app install prompt during reboot (Dees_Troy)
support for AB OTA zips (Dees_Troy)
support new Android 7.x log command (Dees_Troy)
update recovery sources to AOSP 7.1 (Dees_Troy)
numerous bugfixes and improvements by too many people to mention
This is thanks to the Xiaomi mi4i devs and @persona78 for porting it to 6045 (and @satana.nik.1996 for starting to port TWRP from other phones, in 4PDA)
Supported Devices
Any 6045 Variant
Installation Guide
There are multiple methods, i will post the 3 i know here
If you have stock recovery and you are on Lollipop
Install fastboot tools (Android) from google's Sdk on your PC
Reboot in Fastboot mode, pressing volume - and USB cable into the pc or enter into fastboot using in adb (with usb debug enabled) adb reboot-bootloader
Enter the command : fastboot -i 0x1bbb flash recovery twrp-3.1.0-0-m1_Idol3.img (I suggest to rename the file, for to example twrp.img, so you just write fastboot-i 0x1bbb flash recovery twrp.img)
write : fastboot reboot, and when the phone is starting, only press volume+ and you will enter to TWRP
If you have TWRP installed (Any android version)
Boot into TWRP using Vol+ and Power
Go to Install
Press Install Image and search twrp-3.1.0-0-m1_Idol3.img
Then Press Recovery, swipe and it is installed
If you have MM stock, without TWRP and ROOT
Install/Search Rashr from Play Store
Grant SD and Root Permissions
Press Recovery, then search twrp-3.1.0-0-m1_Idol3.img
Press install and you are done
Bug/s TWRP 3.1.0-0
You can't reboot into Recovery from Recovery (you can just press vol+ to avoid this)
It shows internal Storage 2 times, but does not affect in anything (just make sure when you wipe, just wipe 1 and not both at the same time)
You tell me
Bug/s TWRP 3.0.2-0-r5
You can't reboot into Recovery from Recovery (you can just press vol+ to avoid this)
Sort of Laggy (like TWRP 3.0.1-0)
You tell me
Download
TWRP 3.1.0-0 https://mega.nz/#!p4g2RYQS!uq4nFsef55JiKUoepU6kASGfI8sz6Tf970nEyNHHdE8
TWRP 3.0.2-0-r5 https://mega.nz/#!FxxxWYRS!PebYGrzogP8OohJ9IrjpAar8Ya2c4BK8NdmX4jFyJPw
Full ROM backup via ADB https://forum.xda-developers.com/idol-3/general/backup-adb-recovery-twrp-3-0-2-r5-twrp-t3574214
[TOOL] [WINDOWS] TWRP Backup & Restore Tool For PC (not tested on idol3) https://forum.xda-developers.com/android/software-hacking/tool-twrp-backup-restore-tool-pc-t3572241 (from xda, @dexbyte)
Creator
juliusssssmiui
Edited for Idol 3
@persona78
Source Code: https://twrp.me/devices/xiaomimi4i.html
Version Information
Status: Beta
Current Stable Version: 3.0.2-0-r5
Stable Release Date: 2016
Created 2017-03-10
Last Updated 2017-03-17
@panchovix I have twrp 2.74 version, can I flash twrp 3.1 using your step two or another way?
Sent from my 6045I using Tapatalk
belkoo said:
@panchovix I have twrp 2.74 version, can I flash twrp 3.1 using your step two or another way?
Sent from my 6045I using Tapatalk
Click to expand...
Click to collapse
You can, but i can't remember if TWRP 2.74 has that option (to install .Imgs)
panchovix said:
You can, but i can't remember if TWRP 2.74 has that option (to install .Imgs)
Click to expand...
Click to collapse
My bad, I had the 2.8.7.0 version and it can install images. Installed on 6045K without problems, I didn't tried to flash system or wipe data, I don't know will it be problems with that. Anyway, thanks a lot for EVERY single man for making such a great things for this phone including you @panchovix ☺.
Sent from my 6045I using Tapatalk
Just added the changelog, and it is a lot lol, this is good news if N get released (anyways i'm trying to use the adb backup to pc and i can't make it work)
also work on the 6045O?
panchovix said:
In my case shows Blade S6 when connected in TWRP mode to the PC (does not affect in anything)
Click to expand...
Click to collapse
Where exactly do you see this? I see "6045" in the Device Manager, and "recovery" when doing "adb devices".
i'm trying to use the adb backup to pc and i can't make it work
Click to expand...
Click to collapse
Same here... Nothing happens on the device, and the backup file that gets created on the PC has this one line:
Code:
/sbin/sh: /system/bin/bu: not found
When I checked /system/bin in unpacked ramdisk, I found it to be completely empty, but I did find /sbin/bu. So... Not knowing enough to figure out what exactly was wrong here, I just copied the contents of /sbin into /system/bin, repacked the img, and flashed it. Guess what? ADB backup works now. So, someone smarter than me should figure out how to "properly" fix it, because I am pretty damn sure what I did was not the right thing to do, even though it seemed to solve the problem... I didn't do much testing, other than completing the adb backup. Too late, going to bed now...
kt-Froggy said:
Where exactly do you see this? I see "6045" in the Device Manager, and "recovery" when doing "adb devices".
Same here... Nothing happens on the device, and the backup file that gets created on the PC has this one line:
Code:
/sbin/sh: /system/bin/bu: not found
When I checked /system/bin in unpacked ramdisk, I found it to be completely empty, but I did find /sbin/bu. So... Not knowing enough to figure out what exactly was wrong here, I just copied the contents of /sbin into /system/bin, repacked the img, and flashed it. Guess what? ADB backup works now. So, someone smarter than me should figure out how to "properly" fix it, because I am pretty damn sure what I did was not the right thing to do, even though it seemed to solve the problem... I didn't do much testing, other than completing the adb backup. Too late, going to bed now...
Click to expand...
Click to collapse
When you can ,please send me the IMG via pm (or here) and I can test some things
And thanks for finding one way to fix it!
Enviado desde mi 6045B mediante Tapatalk
jbach44 said:
also work on the 6045O?
Click to expand...
Click to collapse
I'm not sure since I don't have that model
If you want , you can test and say me here if it worked for you [emoji14]
Enviado desde mi 6045B mediante Tapatalk
kt-Froggy said:
Where exactly do you see this? I see "6045" in the Device Manager, and "recovery" when doing "adb devices".
Same here... Nothing happens on the device, and the backup file that gets created on the PC has this one line:
Code:
/sbin/sh: /system/bin/bu: not found
When I checked /system/bin in unpacked ramdisk, I found it to be completely empty, but I did find /sbin/bu. So... Not knowing enough to figure out what exactly was wrong here, I just copied the contents of /sbin into /system/bin, repacked the img, and flashed it. Guess what? ADB backup works now. So, someone smarter than me should figure out how to "properly" fix it, because I am pretty damn sure what I did was not the right thing to do, even though it seemed to solve the problem... I didn't do much testing, other than completing the adb backup. Too late, going to bed now...
Click to expand...
Click to collapse
Hi!
How do backup to pc, for me to understand.
So for what i can read insted of bin folder must be a symlink to sbin, right?
.
.
panchovix said:
Just added the changelog, and it is a lot lol, this is good news if N get released (anyways i'm trying to use the adb backup to pc and i can't make it work)
Click to expand...
Click to collapse
Hi!
How to backup?
.
persona78 said:
Hi!
How to backup?
.
Click to expand...
Click to collapse
He still didn't send me the IMG so idk how to
Enviado desde mi 6045B mediante Tapatalk
panchovix said:
He still didn't send me the IMG so idk how to
Enviado desde mi 6045B mediante Tapatalk
Click to expand...
Click to collapse
@panchovix
I already found it!
This is how to backup system for example:
Code:
adb backup -f system.img --twrp system
And in adb folder you will get system.img
How it works:
adb backup -f <filename> --twrp <options> ( --compress: compress data )
options:
system: backup system
cache: backup cache
data: backup data
boot: backup boot
etc for each partition.
Read this if you want to learn more about it:
https://github.com/omnirom/android_bootable_recovery/commit/ce8f83c48d200106ff61ad530c863b15c16949d9
And twrp-lux-3.0.2-r5 can do backup to in the same way! Just need to copy the bu file into /system/bin folder and compile it again... -_-
I think twrp-lux-3.0.2-r5 is better than TWRP 3.1 ...
The MTP works better on pc.
This is twrp-lux-3.0.2-r5_Idol3.img -> https://mega.nz/#!wsAgBSiY!DifwUCYvIoOmMXp14u0ZuBaekhCVmnEDdurU2_6UFfw
This is twrp-3.1.0-0-m1_Idol3.img fixed -> https://mega.nz/#!55hFCABY!GovSGXaQ1muuU0c-wDYN-40iapzey5Jp0AFhIp2B3qg
If you need help just tell me, maybe i can help!
.
persona78 said:
@panchovix
I already found it!
This is how to backup system for example:
Code:
adb backup -f system.img --twrp system
And in adb folder you will get system.img
How it works:
adb backup -f <filename> --twrp <options> ( --compress: compress data )
options:
system: backup system
cache: backup cache
data: backup data
boot: backup boot
etc for each partition.
Read this if you want to learn more about it:
https://github.com/omnirom/android_bootable_recovery/commit/ce8f83c48d200106ff61ad530c863b15c16949d9
And twrp-lux-3.0.2-r5 can do backup to in the same way! Just need to copy the bu file into /system/bin folder and compile it again... -_-
I think twrp-lux-3.0.2-r5 is better than TWRP 3.1 ...
The MTP works better on pc.
This is twrp-lux-3.0.2-r5_Idol3.img -> https://mega.nz/#!wsAgBSiY!DifwUCYvIoOmMXp14u0ZuBaekhCVmnEDdurU2_6UFfw
This is twrp-3.1.0-0-m1_Idol3.img fixed -> https://mega.nz/#!55hFCABY!GovSGXaQ1muuU0c-wDYN-40iapzey5Jp0AFhIp2B3qg
If you need help just tell me, maybe i can help!
.
Click to expand...
Click to collapse
thanks man! i'm an the unevirsity now but will add the 3.0.2.0 version too, for those who want to use it
just wondering, why you don't post the 6039 version here on Android dev too?
panchovix said:
thanks man! i'm an the unevirsity now but will add the 3.0.2.0 version too, for those who want to use it
just wondering, why you don't post the 6039 version here on Android dev too?
Click to expand...
Click to collapse
Maybe when i get home i will do it
.
Sorry guys, busy at work... :\
persona78 said:
Hi!
How do backup to pc, for me to understand.
So for what i can read insted of bin folder must be a symlink to sbin, right?
Click to expand...
Click to collapse
Looks like you already figured out the backup process... Just to note, it also creates the regular backup folder on the device, but also copies it over through ADB to the PC. Yeah, I think it should be either a symlink, or maybe some playing around with the PATH variable, not sure... I did the most simple thing, just to test it out: if a binary is expected in some folder, just put it there. But it's rather stupid, IMO...
panchovix said:
He still didn't send me the IMG so idk how to
Click to expand...
Click to collapse
Sorry, here it is, just for reference.
kt-Froggy said:
Sorry guys, busy at work... :\
Looks like you already figured out the backup process... Just to note, it also creates the regular backup folder on the device, but also copies it over through ADB to the PC. Yeah, I think it should be either a symlink, or maybe some playing around with the PATH variable, not sure... I did the most simple thing, just to test it out: if a binary is expected in some folder, just put it there. But it's rather stupid, IMO...
Sorry, here it is, just for reference.
Click to expand...
Click to collapse
Yeah np, seems he did it, anyways (since I'm not on my home still), did you try to restore the phone with the PC backup? If I'm not wrong it should be adb restore twrp-- ( I can be very wrong lol I don't remember)
That is the most important thing, since you can just move the file to the PC and save space on the phone always
Enviado desde mi 6045B mediante Tapatalk
panchovix said:
did you try to restore the phone with the PC backup? If I'm not wrong it should be adb restore twrp-- ( I can be very wrong lol I don't remember)
That is the most important thing, since you can just move the file to the PC and save space on the phone always
Click to expand...
Click to collapse
Nope, haven't tried it yet... I will try, but not sure when, as I am really crazy busy now between work and home (I am in the final stages of building my own house, lol).
But to me, honestly, this is just an added convenience over just copying over the standard TWRP backups to the PC. Even without adb backup, we can always copy over the TWRP backup folder(s) to the PC, and delete them from the device. Then simply copy them back to do a restore, when needed... Takes some extra time, sure, but still can easily be done.
kt-Froggy said:
Nope, haven't tried it yet... I will try, but not sure when, as I am really crazy busy now between work and home (I am in the final stages of building my own house, lol).
But to me, honestly, this is just an added convenience over just copying over the standard TWRP backups to the PC. Even without adb backup, we can always copy over the TWRP backup folder(s) to the PC, and delete them from the device. Then simply copy them back to do a restore, when needed... Takes some extra time, sure, but still can easily be done.
Click to expand...
Click to collapse
Yeah but for informatics people , less time =always better [emoji14] I will try once I get to home, since I was on University
Gratz with the own house!
Enviado desde mi 6045B mediante Tapatalk
Added new imgs with fixed adb pull, many thanks to @persona78 and @kt-Froggy for helping, finding and fixing the problem
posted a tool that does the adb backup automatized, from persona78
I am trying to automate my nandroid backups but apparently a/b devices mount /data/cache as /cache so I don't know how to make twrp read my openrecoveryscript file from /data/cache. Any help would be greatly appreciated.
darkfire404 said:
I am trying to automate my nandroid backups but apparently a/b devices mount /data/cache as /cache so I don't know how to make twrp read my openrecoveryscript file from /data/cache. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Have you solved this problem? if yes how did you solve your problem?
mauronofrio said:
Have you solved this problem? if yes how did you solve your problem?
Click to expand...
Click to collapse
I haven't yet. I don't know if it's possible without modifying TWRP to read from /data/cache on startup since the cache partition doesn't exist on a/b devices
I doubt it will help or not...
But I noticed when sideloading an OTA, that whatever the .zip file would be called would "extract" to the folder "sideload" (in the /sdcard, but there's a good chance that it's its own folder in the root directory...) as sideload.zip (i believe...I can easily be wrong....but I remember it was a simple and obvious one-word name....). I remember having issues with TWRP processing the initial .zip file, so I would extract the initial OTA .zip file, then manually input what was extracted into that folder under that specific name and TWRP was able to automatically start processing the OTA....
I'm not sure, but maybe you might find this process beneficial and/or interesting/inspiring...
darkfire404 said:
I am trying to automate my nandroid backups but apparently a/b devices mount /data/cache as /cache so I don't know how to make twrp read my openrecoveryscript file from /data/cache. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Have you tried to put the script in /data/cache/recovery/openrecoveryscript ? if the folder doesn't exist try to create it
mauronofrio said:
Have you tried to put the script in /data/cache/recovery/openrecoveryscript ? if the folder doesn't exist try to create it
Click to expand...
Click to collapse
I did that. It didn't work
I'm encountering the same behavior. OpenRecoveryScripts are not being executed.
Running TWRP-3.2.3-0, Pixel 2 on Android 9.0.
UncertainSpin said:
I'm encountering the same behavior. OpenRecoveryScripts are not being executed.
Running TWRP-3.2.3-0, Pixel 2 on Android 9.0.
Click to expand...
Click to collapse
I'm having the same problem too. I have been using Tasker to write to /cache/recovery/openrecoveryscript because that's all I could find online.
I intend to have this in the Run Shell command in Tasker.
chmod 0777 /cache/recovery
echo "backup SDCRBM weeklybackup" > /cache/recovery/openrecoveryscript
echo "reboot" >> /cache/recovery/openrecoveryscript
chmod 664 /cache/recovery/openrecoveryscript
I have verified that it is writing the file, and TWRP seems to be erasing it which from what I gather it is supposed to do. But it is not executing the command when TWRP starts.
LineageOS 16.0 unofficial/ TWRP 3.2.3 on Samsung Galaxy S7.
We need to bring TWRP developers awareness for this issue, it's already reported on GitHub (https://github.com/omnirom/android_bootable_recovery/issues/221) but not acknowledge by TWRP team... If you have a GitHub account, vote for that issue, if you know someone from TWRP, bring them attention to that.
IMO, having this script working is very important for truly automated backups of our devices, let's get this issue fixed...
rfgamaral said:
We need to bring TWRP developers awareness for this issue, it's already reported on GitHub (https://github.com/omnirom/android_bootable_recovery/issues/221) but not acknowledge by TWRP team... If you have a GitHub account, vote for that issue, if you know someone from TWRP, bring them attention to that.
IMO, having this script working is very important for truly automated backups of our devices, let's get this issue fixed...
Click to expand...
Click to collapse
Yup indeed needs to be fixed..
LG V30 Verizon VS996-20k ROMHi!
This Rom is 100% Stock. Most recent TWRP should first be installed. Then you can install this Rom and have Oreo with working TWRP.
This zip is created from the original KDZ. It contains almost the complete 20k firmware, but the partition table rewriting part and recovery image is removed. I changed the system.img, so you do not have to reinstall TWRP (recovery-from-boot.p deleted) when ROM once booted. I also changed the partition size of system.img, so the vendorized people can install this too without having problems because of a too small system partition. This is a continuation of westwood24's idea and work, I've updated it to the newest fw version and edited / advanced it a bit. I followed his idea and made this for users who can not take OTA's because they have Custom Recovery / Root installed.
Thanks to @gimpy1 and @nnjimmy59 for testing this zip! And to @ChazzMatt for searching testers
Features
Stock build made from official KDZ
Stock Build.prop(slightly modified to add dts and locksreen weather and custom EQ)
Added latest 7.0.14 com.lge.equalizer apk for equalizer in sound settings
Unrooted
system.img modified to keep TWRP
System image size shrunk for being able to flash this on a smaller system partition, mainly caused by vendorizing
Removed dm-verity
Removed rctd (LG's root checker tool daemon)
Enabled opt-encrypt, it's your choice now if you want to encrypt your phone, it's no more forced. TWRP now is capable of decryption (both AOSP and stock) since a few versions
Added DTS enabler prop and all lockscreen weather prop to stock build.prop and custom EQ prop
Installation
What you need
Unlocked Bootloader [How to do]
Working TWRP installed (should be installed already, otherwise you wouldn't need this zip )[Link to newest unofficial TWRP]
When you need Root, Latest Magisk [Download]
LATEST ZIP
john-fawkes.com VS99620K.zip [Click to Download]
OLDER ZIPS
AFH ZIPS [Download]
How to install
When you are still on Nougat,
you should start fresh: Reboot to recovery using button combo or reboot app (needs root; btw, Magisk offers this possibility too: Menu -> Modules -> three dot menu top right - Reboot to recovery)
Then flash this TWRP.img via image flashing function in TWRP, reboot to recovery again (for fully working new recovery) and do a backup, then copy this backup to your PC.
Then initiate a factory reset. Wipe your system partition too in TWRP advanced wiping menu, copy the 20k firmware zip to your SD and install it. Reboot and enjoy
From Oreo:
For clean install: Factory reset and wipe system
You can also keep your data by simply dirty flashing the zip. *Be aware that problems may occur, maybe you need to do a factory reset to start fresh*
Flash the 20k zip, then Magisk zip when you need root, then reboot to System = you're DONE
P.S.: could be, that you first need to boot up your fresh install and set it up before you can flash magisk.
At the first time you boot to system, it can be TWRP says No OS installed. You can ignore it.
If TWRP asks if you want to install SU, hit no (in newest TWRP SU is disabled, and the option to install the TWRP app is disabled too.)
Rom Version
Android Version: 8.0 Oreo
Android security patch level: 2019-5-1
DONATION
Don´t forget to hit the thanks-button if you like this zip! :good:
If you want to help me with a donation please click here to help out [Please Click Here]
#reserved
I am on the twrp vs 996_20f. Working very well. Thx, seadersn, and all others involved for your fine work.
Deleted
Third time is a charm. Finally got it to load, I think
nice, i can finally add security patch date now, thx!
@seadersn, the rom works perfectly, flashed it from DOTOS with US998a firmware. It works perfectly. Awesome, many thanks for making this and other TWRP flashable zips available!
I need native tether and so had to restore, and there was a quirk. I mention it not to complain but out of curiosity and to make others aware. TWRP complained about no partitions being selected when attempting to directly restore either my stock US998 setup or DOTOS. Flashing westwood's US998b rom fixed matters. Can you explain what is happening? It seems like TWRP backups are specific to a model firmware.
cmrntnnr said:
@seadersn, the rom works perfectly, flashed it from DOTOS with US998a firmware. It works perfectly. Awesome, many thanks for making this and other TWRP flashable zips available!
I need native tether and so had to restore, and there was a quirk. I mention it not to complain but out of curiosity and to make others aware. TWRP complained about no partitions being selected when attempting to directly restore either my stock US998 setup or DOTOS. Flashing westwood's US998b rom fixed matters. Can you explain what is happening? It seems like TWRP backups are specific to a model firmware.
Click to expand...
Click to collapse
hmm, that would be news for me: what exactly did you do to restore? just selected backup, chosen partitions, restore? or was the backup folder not visible? and: do you have a log of this?
I'll try to be specific and detailed and hopefully not offer too much useless fluff. The phone is an open market us998 v30s. It has never been flashed with any other firmware. I keep a stock and DOTOS TWRP backups. Restoring between them or with any of the other aosp roms has always worked perfectly. I've wanted to see what additional features might be in the Verizon rom so I downloaded the your fresh zip, verified md5sum , factory reset on TWRPv6a and flashed. After satisfying my curiosity, I button danced back to TWRP to restore. This is where things got weird. The names of the backups matched the phone serial number rather than the dated backup name. TWRP gave the no partitions selected error when attempting to restore. At this point I thought maybe the backups got damaged and so popped in the sdcard with extra backups, . Those backups did not register their names properly and would not restore either. At this point I was resigned to setting up the phone again and just moved forward with a factory reset and flash of ww's 998b zip. I thought maybe there was something about the firmware change the affected the ability to restore so I rebooted TWRP. The correct names for the backups appeared and they would flash.
No logs, but I can repeat the process and gather information.
seadersn said:
hmm, that would be news for me: what exactly did you do to restore? just selected backup, chosen partitions, restore? or was the backup folder not visible? and: do you have a log of this?
Click to expand...
Click to collapse
cmrntnnr said:
I'll try to be specific and detailed and hopefully not offer too much useless fluff. The phone is an open market us998 v30s. It has never been flashed with any other firmware. I keep a stock and DOTOS TWRP backups. Restoring between them or with any of the other aosp roms has always worked perfectly. I've wanted to see what additional features might be in the Verizon rom so I downloaded the your fresh zip, verified md5sum , factory reset on TWRPv6a and flashed. After satisfying my curiosity, I button danced back to TWRP to restore. This is where things got weird. The names of the backups matched the phone serial number rather than the dated backup name. TWRP gave the no partitions selected error when attempting to restore. At this point I thought maybe the backups got damaged and so popped in the sdcard with extra backups, . Those backups did not register their names properly and would not restore either. At this point I was resigned to setting up the phone again and just moved forward with a factory reset and flash of ww's 998b zip. I thought maybe there was something about the firmware change the affected the ability to restore so I rebooted TWRP. The correct names for the backups appeared and they would flash.
No logs, but I can repeat the process and gather information.
Click to expand...
Click to collapse
twrp has different mechanisms for setting backup folders names, the serial number is one of them (and the default). it may be that something boot.img or other related has changed in this new firmware, so that old backups have another name than newer ones.
would be nice to have some additional testing. with the new firmware installed. means: install the new firmware zip, then do a cache format, reboot to recovery and then try a restore: does this change everything back to normal?
It all repeated just like the first time. Clearing the caches had no effect. What is the best way to send you the logs?
seadersn said:
twrp has different mechanisms for setting backup folders names, the serial number is one of them (and the default). it may be that something boot.img or other related has changed in this new firmware, so that old backups have another name than newer ones.
would be nice to have some additional testing. with the new firmware installed. means: install the new firmware zip, then do a cache format, reboot to recovery and then try a restore: does this change everything back to normal?
Click to expand...
Click to collapse
pastebin.com :good:
seadersn said:
pastebin.com :good:
Click to expand...
Click to collapse
Oh well, if you remember me, i flashed your h930h twrp on us998 based with boombox before. I backup the Rom using latest twrp too. Then after i lost connection as i already told you, i tried to restore this backup, it show the name of backup correctly but there is no option to select which partitions to restore, i mean it completely blank without anything to select. Just then i thought it was corrupted backup but there is now someone like me. I kdz back to us998e but somehow lost twrp and fastboot unable to flash it back ( showing FAILED (remote: Requested download size is more than max allowed ). But after a few kdz back to nougat and us998b with relock and unlock bootloader i can flash twrp again. So not sure what really happened
cmrntnnr said:
It all repeated just like the first time. Clearing the caches had no effect. What is the best way to send you the logs?
Click to expand...
Click to collapse
the log is in /cache/recovery/last_log, you can copy it to sdcard within twrp or adb pull it.
Mrxyzl said:
Oh well, if you remember me, i flashed your h930h twrp on us998 based with boombox before. I backup the Rom using latest twrp too. Then after i lost connection as i already told you, i tried to restore this backup, it show the name of backup correctly but there is no option to select which partitions to restore, i mean it completely blank without anything to select. Just then i thought it was corrupted backup but there is now someone like me. I kdz back to us998e but somehow lost twrp and fastboot unable to flash it back ( showing FAILED (remote: Requested download size is more than max allowed ). But after a few kdz back to nougat and us998b with relock and unlock bootloader i can flash twrp again. So not sure what really happened
Click to expand...
Click to collapse
boombox; this was some weeks ago, right :good: i hope, this could be solved finally, i think this really could be firmware & partition table related, which indeed can only be fixed by a kdz flash or with the zip used before flashing this one (or relevant other firmware zip).
Apologies for disappearing in the middle of an activity, work called. The problem is a bug in TWRP. One could make the argument that backups are model-firmware specific, but the reason is not exciting and hardly genuine. The installed firmware model is being pre-pended to the serial number of the backup folder name. If model firmware changes then backups made with another model firmware aren't visible. Renaming the backup folder is probably an interim work-around to enable TWRP to see the backups and carry out the restore. A longer-term solution would be to just not prepend anything. Let me know if you still want the recoverly logs and I'll put them onto pastebin.
Here is a snippet from the recovery log with the VS996:
I:Setting up '/data' as data/media emulated storage.
I:mount -o bind '/data/media' '/sdcard' process ended with RC=0
I:mount -o bind '/data/media/0' '/sdcard' process ended with RC=0
I:Setting up '/data' as data/media emulated storage.
I:mount -o bind '/data/media' '/sdcard' process ended with RC=0
I:mount -o bind '/data/media/0' '/sdcard' process ended with RC=0
I:Backup folder set to '/data/media/0/TWRP/BACKUPS/VS996xxyyzzaa'
This is the same snippet after flashing back to US998D:
I:Setting up '/data' as data/media emulated storage.
I:mount -o bind '/data/media' '/sdcard' process ended with RC=0
I:mount -o bind '/data/media/0' '/sdcard' process ended with RC=0
I:Setting up '/data' as data/media emulated storage.
I:mount -o bind '/data/media' '/sdcard' process ended with RC=0
I:mount -o bind '/data/media/0' '/sdcard' process ended with RC=0
I:Backup folder set to '/data/media/0/TWRP/BACKUPS/LGUS998xxyyzzaa'
seadersn said:
pastebin.com :good:
Click to expand...
Click to collapse
cmrntnnr said:
Apologies for disappearing in the middle of an activity, work called. The problem is a bug in TWRP. One could make the argument that backups are model-firmware specific, but the reason is not exciting and hardly genuine. The installed firmware model is being pre-pended to the serial number of the backup folder name. If model firmware changes then backups made with another model firmware aren't visible. Renaming the backup folder is probably an interim work-around to enable TWRP to see the backups and carry out the restore. A longer-term solution would be to just not prepend anything. Let me know if you still want the recoverly logs and I'll put them onto pastebin.
Here is a snippet from the recovery log with the VS996:
...
Click to expand...
Click to collapse
aaaaaahhhh...! very nice finding :good: sounds and looks logical, and *is* logical: *and* makes sense: it appends the model number, which seems legit in terms of security for your phone while restoring. think about two different models which just aren't compatible to each other. what will happen if you restore a wrong firmware's or model's backup to another hardware? it won't boot. to prevent that, it changes the names of the backup folders. absolutely ok. unfortunately
so i just didn't fully get this problem and its meanings... sry for that: but thanks to you! now we know what happened / -s and can write a little tipp for a workaround in one of the first posts of recovery thread. as i said: i don't like the crossflashing stuff thank you
It absolutely makes sense as a safety feature. Perhaps it is best not to remove like I had suggested. Working around the folder naming convention for restores is a minor inconvenience compared to a brick, .
With regard to safety in TWRP, is there any way to increase the space between the radio buttons used for selection of partitions. I once had an unfortunate fat-finger event and a phone that would't boot.
Happy Armistice Day
seadersn said:
aaaaaahhhh...! very nice finding :good: sounds and looks logical, and *is* logical: *and* makes sense: it appends the model number, which seems legit in terms of security for your phone while restoring. think about two different models which just aren't compatible to each other. what will happen if you restore a wrong firmware's or model's backup to another hardware? it won't boot. to prevent that, it changes the names of the backup folders. absolutely ok. unfortunately
so i just didn't fully get this problem and its meanings... sry for that: but thanks to you! now we know what happened / -s and can write a little tipp for a workaround in one of the first posts of recovery thread. as i said: i don't like the crossflashing stuff thank you
Click to expand...
Click to collapse
I just want to be clear before flashing... this can be applied to an existing US998 -> VS996 phone, correct? I see "H930" in the first post, so I was concerned about that.
Also, the issue mentioned in the last few posts - I'm planning to dirty-flash from VS996 20d to this... that won't experience any issue, correct?
Will I need TWRP 3.2.3-6a or will my existing 3.2.3-5 work fine?
I prefer to be over prepared, instead of running into problems!
I am a Verizon customer with the Verizon vs996 phone I ordered new from them back in April or May of this year when I upgraded from the droid turbo. If you see the third or fourth post in this thread, I took a screen shot of the phone system. I am still currently on this rom but, am a "flashaholic", so in the next day or so will probably change it again (probably flash the twrp US998 rom or maybe pie 9).
In the first post, seadersn tells you how to install it on your phone from "oreo". That is the procedure I used. I am pretty sure that I used the most current version of twrp, the one that says something like 6a data IMG.
Edit: I just went into twrp and checked the version. It is the 6a data IMG version that I am on.
Sorry, I just reread your post. You went from the US998 to the VS996, not the other way around as I first thought. I would think it would still l work, but, again, I started out with the VS996.
schwinn8 said:
I just want to be clear before flashing... this can be applied to an existing US998 -> VS996 phone, correct? I see "H930" in the first post, so I was concerned about that.
Also, the issue mentioned in the last few posts - I'm planning to dirty-flash from VS996 20d to this... that won't experience any issue, correct?
Will I need TWRP 3.2.3-6a or will my existing 3.2.3-5 work fine?
I prefer to be over prepared, instead of running into problems!
Click to expand...
Click to collapse
changed the h930 to V30 sry, forgot to change this
but these issues were special ones, more related to twrp than to this firmware. firmware itself is fine, it's just all the images of the kdz converted to twrp flashable zip :good: when you experience problems, these problems will be there too when flashing the kdz
your recovery version is fine, beside the fact that it has wrong modem partition handling. updating is always the best :good: i would suggest to install -6a.
gimpy1 said:
I am a Verizon customer with the Verizon vs996 phone I ordered new from them back in April or May of this year when I upgraded from the droid turbo. If you see the third or fourth post in this thread, I took a screen shot of the phone system. I am still currently on this rom but, am a "flashaholic", so in the next day or so will probably change it again (probably flash the twrp US998 rom or maybe pie 9).
In the first post, seadersn tells you how to install it on your phone from "oreo". That is the procedure I used. I am pretty sure that I used the most current version of twrp, the one that says something like 6a data IMG.
Edit: I just went into twrp and checked the version. It is the 6a data IMG version that I am on.
Sorry, I just reread your post. You went from the US998 to the VS996, not the other way around as I first thought. I would think it would still l work, but, again, I started out with the VS996.
Click to expand...
Click to collapse
i don't know anything about all these conversions, can therefore not give any tipps if this will work or not. for info about that @schwinn8 has to search or ask on other places
Hi,
I did something wrong with my A2 Lite, i've updated the Magisk boot file from the Magisk app. Caused my phone to stop booting Android.
So i tried reflashing it with Mi Flash in EDL mode. That worked but i don't have any signal when i put a SIM in.
It shows my provider in settings so it recognizes the SIM but doesn't do anything with it.
Tried 10.0.13.0 manually and via Mi Flash = no signal
Tried 10.0.2.0 via Mi Flash = no signal
Loaded TWRP, switch A/B = no effect
Does anyone have a clue what i can do now?
Looks like the IMEI numbers are 0.
terrorsource said:
Looks like the IMEI numbers are 0.
Click to expand...
Click to collapse
I don't know how you got here, but it looks like some important stuff was overwritten.
The mobile network is probably blocking you due to the invalid IMEI...
This is typically something that is stored only in the phone's flash. I'm not sure you'll be able to recover the phone.
a1291762 said:
I don't know how you got here, but it looks like some important stuff was overwritten.
The mobile network is probably blocking you due to the invalid IMEI...
This is typically something that is stored only in the phone's flash. I'm not sure you'll be able to recover the phone.
Click to expand...
Click to collapse
Is it possible to write back the IMEI's if i have them?
terrorsource said:
Is it possible to write back the IMEI's if i have them?
Click to expand...
Click to collapse
It might be. In theory. You'd need to know the format of whatever was overwritten.
You can't rewrite the IMEI, I've have that issue before and I created a guide on how to fix it
https://forum.xda-developers.com/mi...-to-fix-efs-corruption-sim-card-t3928910/amp/
Enjoy ?
You can download the latest rom and install it (ignore the rom that's in the guide it is outdated, but the rest of the guide stays the same).
Noam5651 said:
You can't rewrite the IMEI, I've have that issue before and I created a guide on how to fix it
https://forum.xda-developers.com/mi...-to-fix-efs-corruption-sim-card-t3928910/amp/
Enjoy
You can download the latest rom and install it (ignore the rom that's in the guide it is outdated, but the rest of the guide stays the same).
Click to expand...
Click to collapse
Thanks, will check it out the next couple of days.
I do see some websites/youtube video's of people/apps claiming it is possible by re-writing the QCN file...
I do know where i made a mistake, i tried to manually install all files in an image folder, including flashing a not-so-good QCN file...
terrorsource said:
Thanks, will check it out the next couple of days.
I do see some websites/youtube video's of people/apps claiming it is possible by re-writing the QCN file...
I do know where i made a mistake, i tried to manually install all files in an image folder, including flashing a not-so-good QCN file...
Click to expand...
Click to collapse
https://forum.xda-developers.com/mi-a2-lite/how-to/sim-network-solution-alternatively-t3914161
if this doesn't work ,pm me
nikoman1987 said:
https://forum.xda-developers.com/mi-a2-lite/how-to/sim-network-solution-alternatively-t3914161
if this doesn't work ,pm me
Click to expand...
Click to collapse
Works partially!
I cannot install the latest "QPST_2.7.453" due to "Installation errors".
If i try "QPST_2.7.422" i can restore the created QCN but i cannot select "Enable Multi-SIM" and it only restores IMEI-1
nikoman1987 said:
https://forum.xda-developers.com/mi-a2-lite/how-to/sim-network-solution-alternatively-t3914161
if this doesn't work ,pm me
Click to expand...
Click to collapse
Works now! both IMEI's are now shown in the settings.
IMEI SV is still at 0 though.
Your manual needs some work though.
Latest QFI: https://androidmtk.com/download-qualcomm-flash-image-loader-qfil
Enable Multi-SIM is not in all versions. I've used v2.0.1.9
Restoring QCN with this version can take a while. DO NOT USE PC until done!
8. daisy_sprout:/ $ su
/system/bin/sh: su: not found
127|daisy_sprout:/ $ setprop sys.usb.config rndis,diag,adb
setprop: failed to set property 'sys.usb.config' to 'rndis,diag,adb'
16. is not "QPST.exe" but "QFIL.exe"
20. 21. 22. not needed. directly went to 23 from 19.
stopped at 27, rebooted phone, IMEI's are back. Did not proceed with the manual any further.
terrorsource said:
Works now! both IMEI's are now shown in the settings.
IMEI SV is still at 0 though.
Your manual needs some work though.
Latest QFI: https://androidmtk.com/download-qualcomm-flash-image-loader-qfil
Enable Multi-SIM is not in all versions. I've used v2.0.1.9
Restoring QCN with this version can take a while. DO NOT USE PC until done!
8. daisy_sprout:/ $ su
/system/bin/sh: su: not found
127|daisy_sprout:/ $ setprop sys.usb.config rndis,diag,adb
setprop: failed to set property 'sys.usb.config' to 'rndis,diag,adb'
16. is not "QPST.exe" but "QFIL.exe"
20. 21. 22. not needed. directly went to 23 from 19.
stopped at 27, rebooted phone, IMEI's are back. Did not proceed with the manual any further.
Click to expand...
Click to collapse
We'll I have never had an issue with losing my IMEI , the manual is not mine ,I'm glad that it worked!