Develop Bugs

Slot Swappin'

Some info first:
Carrier: Sprint
Running the Latest TWRP (packaged with Pantheon Kernel), and SuperSu (Huge thanks to joemossjr, Uzephi, and enetec for their respective works, and others!)
So, I'm just trying to grab a little clarity...
Currently I am on "Slot A". When I first purchased the phone, I was on Slot B, and the series of events occurred as such:
Performed all security updates to October
Unlocked Bootloader
Flashed TWRP
Flashed SuperSu
-profited-
Stuck a fork in electrical socket and pressed "reboot system [SLOT A] (When I was on Slot B) - *womp womp*
Was unable to boot to anything except fast-boot
Flash-alled fresh system (Thanks again to all the work over in the development section!)
Performed all security updates to October
Flashed TWRP
Flashed SuperSu
-back in the money-
^^^ Where I am at now, except on SLOT A
So... here's where I need some clarity... if the Slot A / Slot B system works as a pass/trade system between two OS's, effectively allowing consecutive updates.. why did my system hit the crapper when i switched slots?
Theoretically, it should have simply booted into whatever my prior to flashing [what goes here? was it SuperSu that caused the derp, or TWRP?]
Also, now that we have a functioning TWRP as well as a functioning Security check for October, will we get to the point where we are able to actually just flash to separate partitions easily, and thus boot into separate roms easily?
I totally assume I'm missing some vital information above with my understanding about the discrepancies between Slots, as well as other partitions , so feel free to point at laugh at the short-bus kid... so long as you fill me in the gaps in my understanding.
Thanks!

My experiences are according with all you reported... I've done some "stock system" backups too (both A & B...) and I can confirm they differ from day one too...
It seems to be clear that things are a bit more complex than our speculations on them...

So far what I've tested: When you flash all, you go back to slot A (I assume the fastboot erase DDR is what causes it to go back to slot A). In essence, I have had October update on slot A and B by choice by choosing a different flashall zip.
oem is one partition. it is one HUGE partition, but one none-the-less (about 600 MB). The phone sees it as two though (sde19 and sdf19) User data is one partition. (sdb21) SSD is one partition (sdb1).
This means dual booting an OS needs to be similar (where they can share userdata and not cause boot loops) as user data (/data) is shared across both boot-a/boot-b ; system_a/system_b (sde17/sdf17 ; sde18/sdf18)
A lot of vendor specific issues in /crypto of the kernel causes some idiosyncrasies with encryption. any kernel update I do that involves /crypto or /fs edits causes a plethora of headaches.... one kernel update broke ADB and partially broke fastboot
Edit: your user data was decrypted with SU. So slot B was not encrypted. when you went to slot A (was encrypted) your phone couldn't read it.

Uzephi said:
...
This means dual booting an OS needs to be similar (where they can share userdata and not cause boot loops) as user data (/data) is shared across both boot-a/boot-b ; system_a/system_b (sde17/sdf17 ; sde18/sdf18)
Click to expand...
Click to collapse
I agree. When I made some speculations about dual booting (in another thread) I was thinking the same OR switching/recovering different /data by TWRP backup/restore...
Uzephi said:
...
Edit: your user data was decrypted with SU. So slot B was not encrypted. when you went to slot A (was encrypted) your phone couldn't read it.
Click to expand...
Click to collapse
If things here works as on Moto Z (Griffin) your sentence should be... "You have /data decrypted since of SuperSU tweak. Slot B has no more force encryption enabled since of this tweak. When you went to slot A (still with force encryption enabled since of no tweak installed), your phone will begin to encrypt /data partition again (it can read both encrypted and not encrypted, but if not encrypted it will encrypt at first boot) and, since of the long time required by operation on any /data partition not just formatted, it seems to hang/bootlooping..."

enetec said:
If things here works as on Moto Z (Griffin) your sentence should be...
Click to expand...
Click to collapse
The Griffin is different. The kryo msm8998 has it's own encryption chip built on the CPU. our kernels disable that so then everything goes software encryption which causes a bunch of issues. It's the only way we could get TWRP to decrypt the phone.

Uzephi said:
The Griffin is different. The kryo msm8998 has it's own encryption chip built on the CPU. our kernels disable that so then everything goes software encryption which causes a bunch of issues. It's the only way we could get TWRP to decrypt the phone.
Click to expand...
Click to collapse
...interesting!

enetec said:
...interesting!
Click to expand...
Click to collapse
https://www.qualcomm.com/documents/snapdragon-835-mobile-platform-product-brief Page 2 of the PDF, they call it "Qualcomm Haven Suite."

So essentially, Qualcomm took the initiative to "secure" us... For **our** benefit... Potentially against our will... Whereas before, we could choose to software encrypt if we wanted, and software decrypt at our discretion...
Obviously I'm being facetious, this seems to me to clearly be for the benefit of OEMs and Providers. Don't get me wrong, hardware microchipped encryption is kick-ass, especially how fast it manages it.... Just not how it's been utilized here.... As a massive firewall against 3rd party fingers in the pie.

Some_Donkus said:
So essentially, Qualcomm took the initiative to "secure" us... For **our** benefit... Potentially against our will... Whereas before, we could choose to software encrypt if we wanted, and software decrypt at our discretion...
Obviously I'm being facetious, this seems to me to clearly be for the benefit of OEMs and Providers. Don't get me wrong, hardware microchipped encryption is kick-ass, especially how fast it manages it.... Just not how it's been utilized here.... As a massive firewall against 3rd party fingers in the pie.
Click to expand...
Click to collapse
Yes, it's a simple flag in the defconfig file

Here is the slot swappin' solution you were looking for!
Download the most current official Google fastboot:
https://developer.android.com/studio/releases/platform-tools.html
Go into fastboot mode and type on PC:
fastboot set_active _a
(then boot to recovery, check TWRP to see you are on slot _a)
fastboot set_active _b
(then boot to recovery, check TWRP to see you are on slot _b)
Please note: I am sure the a/b switch inside our phone's TWRP will eventually work, but it doesn't currently (as of 17NOV2017); other a/b phones have had the same issue.

What is interesting to me is that flashall flashes both slots, and you can manually choose to flash a specific boot with $flash boot_a or $flash boot_b. With this ability and enough experimenting I'm sure there's a workaround somewhere.

Some_Donkus said:
What is interesting to me is that flashall flashes both slots, and you can manually choose to flash a specific boot with $flash boot_a or $flash boot_b. With this ability and enough experimenting I'm sure there's a workaround somewhere.
Click to expand...
Click to collapse
this method works for me
https://forum.xda-developers.com/showpost.php?p=74543389&postcount=10

jhofseth said:
this method works for me
https://forum.xda-developers.com/showpost.php?p=74543389&postcount=10
Click to expand...
Click to collapse
Oh, haha! I totally missed this post in the thread. Herp-A-Derp! Thank you! (I've been peepin' stuff via the XDA labs on my phone and I'm not used to the notifications and such, thanks for the rewind redirect!)
So... theoretically... if I used the above method to swap into the "other" slot and flash both slots identical, with TWRP and SuperSu... I would be able to swap slots back and forth as I pleased... (even though they would be the same.. and thus making swapping between them.. kind of pointless...) because both would then have the same flag...
If i wanted to modify -ONE- of them, I would have to ensure that it matched the encryption state of the other... correct?

jhofseth said:
Download the most current official Google fastboot:
https://developer.android.com/studio/releases/platform-tools.html
Go into fastboot mode and type on PC:
fastboot set_active _a
(then boot to recovery, check TWRP to see you are on slot _a)
fastboot set_active _b
(then boot to recovery, check TWRP to see you are on slot _b)
Please note: I am sure the a/b switch inside our phone's TWRP will eventually work, but it doesn't currently (as of 17NOV2017); other a/b phones have had the same issue.
Click to expand...
Click to collapse
Great!
Anyway, looking at my a & b backups, it seems to me TWRP a/b switch is already working (they are different...).
---------- Post added at 02:52 PM ---------- Previous post was at 02:50 PM ----------
Some_Donkus said:
What is interesting to me is that flashall flashes both slots, and you can manually choose to flash a specific boot with $flash boot_a or $flash boot_b. With this ability and enough experimenting I'm sure there's a workaround somewhere.
Click to expand...
Click to collapse
I could be wrong but... I've intended from my tests that fastboot without any slot specified flashes only the current one, not both...
---------- Post added at 02:56 PM ---------- Previous post was at 02:52 PM ----------
Some_Donkus said:
...
So... theoretically... if I used the above method to swap into the "other" slot and flash both slots identical, with TWRP and SuperSu... I would be able to swap slots back and forth as I pleased... (even though they would be the same.. and thus making swapping between them.. kind of pointless...) because both would then have the same flag...
If i wanted to modify -ONE- of them, I would have to ensure that it matched the encryption state of the other... correct?
Click to expand...
Click to collapse
Theoretically... yes!
(But don't bet your ass on it... :laugh

Some_Donkus said:
Oh, haha! I totally missed this post in the thread. Herp-A-Derp! Thank you! (I've been peepin' stuff via the XDA labs on my phone and I'm not used to the notifications and such, thanks for the rewind redirect!)
So... theoretically... if I used the above method to swap into the "other" slot and flash both slots identical, with TWRP and SuperSu... I would be able to swap slots back and forth as I pleased... (even though they would be the same.. and thus making swapping between them.. kind of pointless...) because both would then have the same flag...
If i wanted to modify -ONE- of them, I would have to ensure that it matched the encryption state of the other... correct?
Click to expand...
Click to collapse
Once you have successfully booted into the other slot's boot (TWRP), you can see what condition the data partition is in with respect to encryption. If files are encrypted and you already backed up important data (i.e., same data partition shared by both slots, but different systems, boots, etc.), I would recommend formatting data in TWRP. After that, you should do this:
https://forum.xda-developers.com/showpost.php?p=74540731&postcount=21
This way, you will always be able to access data on the data partition, because it won't be encrypted.
(Either system partition can cause data to become encrypted again, so if you have to format data in one and run the above linked command, you would need to do the same in the other boot (TWRP).)

jhofseth said:
Once you have successfully booted into the other slot's boot (TWRP), you can see what condition the data partition is in with respect to encryption. If files are encrypted and you already backed up important data (i.e., same data partition shared by both slots, but different systems, boots, etc.), I would recommend formatting data in TWRP. After that, you should do this:
https://forum.xda-developers.com/showpost.php?p=74540731&postcount=21
This way, you will always be able to access data on the data partition, because it won't be encrypted.
(Either system partition can cause data to become encrypted again, so if you have to format data in one and run the above linked command, you would need to do the same in the other boot (TWRP).)
Click to expand...
Click to collapse
https://plus.google.com/+DeesTroy/posts/i33ygUi7tiu
Hopefully... Encryption won't be a worry

Uzephi said:
https://plus.google.com/+DeesTroy/posts/i33ygUi7tiu
Hopefully... Encryption won't be a worry
Click to expand...
Click to collapse
That all sounds like an insane amount of redundant PitA!!
I really wish I could be of more service in the coding department to help chip away at these types of lockdowns. Unfortunately, my skills are limited to Python and basic C++ console stuff.
This kind of stuff makes me pine for the days when my biggest challenge was trying to modify the UI in Qbasic and installing a power supply without a keyed molex lol.
So, IF we end up at a wall regarding this severe encryption despite the progress made so far, would we be able to patch in security updates "off the cuff" via custom made twrp or fastboot packages?

Uzephi said:
https://plus.google.com/+DeesTroy/posts/i33ygUi7tiu
Hopefully... Encryption won't be a worry
Click to expand...
Click to collapse
Very interesting article about how much Google "love us"...
Please note that at lower level even Motorola did the same on old Griffin (Moto Z)... if you upgraded bootloader (by OTA or by a flashall) during MM->N upgrade, you'll never able to install MM or downgrade bootloader (soft brick in first case and refuse to flash in second one...).
Obviously newer bootloader was't required and gave no benefits on older one...
For this reason on Moto's I ever hint not to flash bootloader even during flashall/debrick...

enetec said:
Very interesting article about how much Google "love us"...
Please note that at lower level even Motorola did the same on old Griffin (Moto Z)... if you upgraded bootloader (by OTA or by a flashall) during MM->N upgrade, you'll never able to install MM or downgrade bootloader (soft brick in first case and refuse to flash in second one...).
Obviously newer bootloader was't required and gave no benefits on older one...
For this reason on Moto's I ever hint not to flash bootloader even during flashall/debrick...
Click to expand...
Click to collapse
Tried adding the code from the pixel 2 because the xl 2 is it's own beast and due to the fact were not running Oreo like there it broke right around 78% and it was due to missing proprietary Google files

Can't flash back from Android 10 back to Android 9

I've spent about 6 hours trying various things and I'm not sure how to continue.
I did a backup then started upgrading to Android 10. Long story short, I want to go back to 9.
Every time I try to flash-all.bat crosshatch-pq1a.181205.006.a1-factory-99bead33 back, it fails on:
Sending sparse 'vendor_b' 1/2 (262140 KB) FAILED (Error reading sparse file)
fastboot: error: Command failed
It always fails on that line, and only after succeeding on 34 other counts of flashing. I've tried multiple cables. After this, there's a constant stream of fastboot and recovery warnings, and nothing works right until I flash crosshatch-qq2a.200405.005-factory-2d1c5652 back on. I've tried a handful of manual flashing of the vendor file without success.
It seems like something changed in the phone that simply disallows flashing back.
Has anyone successfully done this?

bizaff said:
I've spent about 6 hours trying various things and I'm not sure how to continue.
I did a backup then started upgrading to Android 10. Long story short, I want to go back to 9.
Every time I try to flash-all.bat crosshatch-pq1a.181205.006.a1-factory-99bead33 back, it fails on:
Sending sparse 'vendor_b' 1/2 (262140 KB) FAILED (Error reading sparse file)
fastboot: error: Command failed
It always fails on that line, and only after succeeding on 34 other counts of flashing. I've tried multiple cables. After this, there's a constant stream of fastboot and recovery warnings, and nothing works right until I flash crosshatch-qq2a.200405.005-factory-2d1c5652 back on. I've tried a handful of manual flashing of the vendor file without success.
It seems like something changed in the phone that simply disallows flashing back.
Has anyone successfully done this?
Click to expand...
Click to collapse
I am assuming you are on a device which has an unlocked bootloader? If not, you can't go back.

Eudeferrer said:
I am assuming you are on a device which has an unlocked bootloader? If not, you can't go back.
Click to expand...
Click to collapse
Correct - first thing I did when I got it a couple years ago was unlock it. On the fastboot screen it has always said unlocked as well.
Like I said, I can flash Android 10 on it (which it has right now with Magisk installed via copying boot.img and updating it through the app), but I'd like to go back to the image I had (either 9.0.0 (PQ1A.181205.006, Dec 2018) or 9.0.0 (PQ1A.181205.006.A1, Dec 2018, Docomo) - not sure what the Docomo is).
Android 10 (crosshatch-qq2a.200405.005-factory-2d1c5652) installed from flash-all.bat just fine, but neither of the above 9.0.0 images install - they both fail on the vendor_b and only on the vendor_b.
Thoughts?

bizaff said:
Correct - first thing I did when I got it a couple years ago was unlock it. On the fastboot screen it has always said unlocked as well.
Like I said, I can flash Android 10 on it (which it has right now with Magisk installed via copying boot.img and updating it through the app), but I'd like to go back to the image I had (either 9.0.0 (PQ1A.181205.006, Dec 2018) or 9.0.0 (PQ1A.181205.006.A1, Dec 2018, Docomo) - not sure what the Docomo is).
Android 10 (crosshatch-qq2a.200405.005-factory-2d1c5652) installed from flash-all.bat just fine, but neither of the above 9.0.0 images install - they both fail on the vendor_b and only on the vendor_b.
Thoughts?
Click to expand...
Click to collapse
I'm not an expert by any means but my thoughts on this would be: perhaps some file needed is not properly extracted to the right folder. I like to extract everything to the same file and then run the commands I'm using. Don't know how necessary this is but it works for me. Also, perhaps try the commands with a .\ in front of it. For some reason, it doesn't work for me unless I do this.

Have you tried fastboot erase userdata just for giggles? I've gone back to 9 before. I always extract the contents of the factory zip to the fastboot folder directly then just run the flash-all.bat are you using the latest fastboot tools?

Check what slot it is on and switch slots.

Eudeferrer said:
I'm not an expert by any means but my thoughts on this would be: perhaps some file needed is not properly extracted to the right folder.
Click to expand...
Click to collapse
This kinda sorta seems like it might be something wrong? It always fails on the same file. If I recall correctly, I downloaded the archive again and it still failed on the same file..
Eudeferrer said:
I like to extract everything to the same file and then run the commands I'm using. Don't know how necessary this is but it works for me. Also, perhaps try the commands with a .\ in front of it. For some reason, it doesn't work for me unless I do this.
Click to expand...
Click to collapse
I don't think it's that, it's finding and executing everything.
Maybe I could try this on Linux? I don't know, I'm kind of at a loss.

UmbrellaTakedown said:
Have you tried fastboot erase userdata just for giggles? I've gone back to 9 before. I always extract the contents of the factory zip to the fastboot folder directly then just run the flash-all.bat are you using the latest fastboot tools?
Click to expand...
Click to collapse
I haven't tried that, but it's most definitely vendor_b. I wonder if I should erase that partition and see if that works.. but I'm still stumped why updating to 10 works.. just checked the archive and there is a vendor.img in the 10 image.
Yep, that's how I run it too.
I downloaded the "latest", which gave me platform-tools_r30.0.0-windows. I also went back and downloaded 27, 28, and 29, and tried a few of those - no dice.

wangdaning said:
Check what slot it is on and switch slots.
Click to expand...
Click to collapse
I guess that's one thing I didn't try.. is there a decent guide somewhere to select the slot to program, boot, and install Magisk to? I had found something about querying which slot was active, but not about selecting..
Hopefully I can update to the final 9.0 version then not worry about it till I switch to 10..

fastboot -help will tell you the command to select, something like fastboot --set-active=a/b. The bootloader screen should tell you which is active. Once you change active slot use fastboot reboot bootloader and run the flash-all of the factory image you want.

[ROM][11] LineageOS 18.1 [OFFICIAL]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 10, which is designed to increase performance and reliability over stock Android for your device.
Code:
/*
* Your warranty is now void.
*
* I am 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 me for messing up your device, I will laugh at you.
*/
NOTE
Should you ever face any issues, capture logs. I also need to know what build you're on (build number or at least a date).
Hint: "It doesn't work" is not a bug report and posts like this will be ignored.
KNOWN ISSUEs
The Sony stock camera does not work at the moment.
INFO
This ROM does not use the device trees/kernel from sonyxperiadev (aka SODP). The device tree was made from scratch, and the stock kernel (based off 52.1.A.x.y) has been used.
DOWNLOAD
Official builds
NOTE: Since the official builds are signed, you can't simply upgrade from my unofficial builds -- you can either migrate to an official build using a script or do a clean install.
All unofficial builds
INSTRUCTIONS
Just flash the builds as usual. Make sure to be on the latest stock firmware.
SOURCE
LineageOS
Kernel

CHANGELOG
20210516:
- fixed WiFi display/screen casting
- addressed performance issues and lags
20210515:
- updated to 18.1
- fixed remaining most of the bugs
- set SELinux to enforcing
20201128:
- fixed NFC
20201127:
- initial public release.

Thanks a lot. Great to know you are working on LOS18.
I tried sideloading with the latest LOS17.1 recovery (and LOS 17.1 on the phone, naturally). I get an error. Do I absolutely have to be on stock?

Are you still working on this one?

I am trying to flash a LOS image onto a single SIM Phone, but it always fails with error "unknown fuse request opcode 2016" in the recovery.log, and the system image is empty after the flash.
I am using the latest STOCK TWRP 2020-06-14_21-07-37_twrp_apollo.tar.gz.
It fails on all LOS images I have tried, 18.0 17.1 etc. So far I haven't been able to flash a LOS image at all successfully.
The flash performs normally, but fails with an error after 2-3 minutes, and afterwards the system partition is empty.
The unit is a SONY XZ2 Compact Single SIM.
After discussion with someone, this maybe due to the LOS image having an incorrect System partition size(?). Why does it flash correctly on most people's units, but not on this one?
Anyone has an idea? I am attaching the twrp.log files.

Garfield24 said:
I am trying to flash a LOS image onto a single SIM Phone, but it always fails with error "unknown fuse request opcode 2016" in the recovery.log, and the system image is empty after the flash.
I am using the latest STOCK TWRP 2020-06-14_21-07-37_twrp_apollo.tar.gz.
It fails on all LOS images I have tried, 18.0 17.1 etc. So far I haven't been able to flash a LOS image at all successfully.
The flash performs normally, but fails with an error after 2-3 minutes, and afterwards the system partition is empty.
The unit is a SONY XZ2 Compact Single SIM.
After discussion with someone, this maybe due to the LOS image having an incorrect System partition size(?). Why does it flash correctly on most people's units, but not on this one?
Anyone has an idea? I am attaching the twrp.log files.
Click to expand...
Click to collapse
Hi!
I'got the same situation, with a bad downloaded los.zip file. Maybe it's the problem.
But what i saw in your description, the used twrp. If i known good, for Android 11 the working twrp for coming from stock to los is here what works for me ( apollo ):
" https://androidfilehost.com/?w=files&flid=318609 " ;
And don't flash it to the recovery or boot partitiom, just temperoraly boot it with fastboot.

lba810701 said:
Hi!
I'got the same situation, with a bad downloaded los.zip file. Maybe it's the problem.
But what i saw in your description, the used twrp. If i known good, for Android 11 the working twrp for coming from stock to los is here what works for me ( apollo ):
" https://androidfilehost.com/?w=files&flid=318609 " ;
And don't flash it to the recovery or boot partitiom, just temperoraly boot it with fastboot.
Click to expand...
Click to collapse
Nope, not working.
I flashed a stock image with newflasher and booted to the apps. Original image boots fine.
Then I rebooted into fastboot and did: fastboot boot twrp.img like you suggested.
TWRP runs fine, I wipe the partitions, and flash LOS. No operating system installed afterwards.
I don't think it's a corrupt .zip file, since I tried about 5 different ones.
When flashing I get a message: "Unable to find partition for path /cache" in red colour.
Anyone knows what that means?

Garfield24 said:
Nope, not working.
I flashed a stock image with newflasher and booted to the apps. Original image boots fine.
Then I rebooted into fastboot and did: fastboot boot twrp.img like you suggested.
TWRP runs fine, I wipe the partitions, and flash LOS. No operating system installed afterwards.
I don't think it's a corrupt .zip file, since I tried about 5 different ones.
When flashing I get a message: "Unable to find partition for path /cache" in red colour.
Anyone knows what that means?
Click to expand...
Click to collapse
H
Garfield24 said:
Nope, not working.
I flashed a stock image with newflasher and booted to the apps. Original image boots fine.
Then I rebooted into fastboot and did: fastboot boot twrp.img like you suggested.
TWRP runs fine, I wipe the partitions, and flash LOS. No operating system installed afterwards.
I don't think it's a corrupt .zip file, since I tried about 5 different ones.
When flashing I get a message: "Unable to find partition for path /cache" in red colour.
Anyone knows what that means?
Click to expand...
Click to collapse
Do you disabled the verified boot before rhe whole twrp process?
" fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img "

lba810701 said:
H
Do you disabled the verified boot before the whole twrp process?
" fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img "
Click to expand...
Click to collapse
Yes, I have tried that, too, just now again. As before, not working. I have tried so many things by now. The flash of the LOS image completes, but in step 2/2 I get "Unable to find partition for path /cache" , and it says completed. In the recovery log, there is an error "unknown fuse request opcode 2016" . The system partition is empty after the flash (7MB used).
I wonder, if there is a difference in the partitions on this specific phone. I am attaching the output of the following command:
cat /proc/partitions > /external_sd/partlog.txt
It writes an overview of partitions and their sizes to a file on the SD Card. There are 74 partitions on /sda. I wonder why anybody needs 74 partitions?
Can someone run the same command on their phone with a working and installed LOS and compare it to my file, if there is any difference to a phone that is working (partitions-sizes/-ordering?)?
I run the command from TWRP. Start up recovery TWRP and go to Advanced -> Terminal. There you can run the command.
cat /proc/partitions > /external_sd/partlog.txt
I would appreciate if someone could run that command on a phone where the LOS image works, and compare the file to my file, if there are any differences in the partitioning scheme or sizes. Sizes are important.
Any other suggestions also welcome.

Garfield24 said:
Yes, I have tried that, too, just now again. As before, not working. I have tried so many things by now. The flash of the LOS image completes, but in step 2/2 I get "Unable to find partition for path /cache" , and it says completed. In the recovery log, there is an error "unknown fuse request opcode 2016" . The system partition is empty after the flash (7MB used).
I wonder, if there is a difference in the partitions on this specific phone. I am attaching the output of the following command:
cat /proc/partitions > /external_sd/partlog.txt
It writes an overview of partitions and their sizes to a file on the SD Card. There are 74 partitions on /sda. I wonder why anybody needs 74 partitions?
Can someone run the same command on their phone with a working and installed LOS and compare it to my file, if there is any difference to a phone that is working (partitions-sizes/-ordering?)?
I run the command from TWRP. Start up recovery TWRP and go to Advanced -> Terminal. There you can run the command.
cat /proc/partitions > /external_sd/partlog.txt
I would appreciate if someone could run that command on a phone where the LOS image works, and compare the file to my file, if there are any differences in the partitioning scheme or sizes. Sizes are important.
Any other suggestions also welcome.
Click to expand...
Click to collapse
I attached it, but I'm on 17.1. Maybe help? But first round, it's seems the same except the last two line of the logs... In yours, there are "mcblk0" and "mmcblk0p1" what's missing from mine, but I haven't got sdcard so, maybe thats why.

lba810701 said:
I attached it, but I'm on 17.1. Maybe help? But first round, it's seems the same except the last two line of the logs... In yours, there are "mcblk0" and "mmcblk0p1" what's missing from mine, but I haven't got sdcard so, maybe thats why.
Click to expand...
Click to collapse
Yes, that definitely helps. Thank you. The last two lines is the SDCard, that's correct.
That means my phone has the same ROM size and partition size than yours, so the System partition is the same size.
I find an additional partition in your file in line 19:
254 0 1048576 zram0
I don't have a zram0 partition in my file and my phone.
The question now is: does that make any difference? Can that missing partition on my phone can cause the flash to fail?

After a LOT of trial and error I am making a description, how to get a running LOS on your SONY XZ2 Compact Single SIM (and probably Dual SIM). This is not a description for people, who got it running the easy way. It's for people that tried everything, and can't get it running, and are in desperation and lost.
General description first: The SONY XZ2 Compact is a phone with 2 slots. These phones don't have a recovery partition, so you cannot meaningfully boot into a recovery partition like on old phones. It now has a boot partition (2 of them - slot A and slot B), and you can boot an operating system from these slots. These slots are completely separate, you can boot an operating system in slot A and another separate one in slot B. These slots (from a user perspective) are separate, and there is very little interchange between them (or more or less none).
Prerequisits: TWRP, I used the Version from MartinX 2020-06-14_21-07-37_twrp_apollo.tar.gz , link is here: https://androidfilehost.com/?w=files&flid=306949
Use a STOCK TWRP
Extract the .img files with 7-zip (7-zip.org), until you have the .img file separate.
Newflasher:
[TOOL] Newflasher (xperia command line flasher)
Disclaimer: newflasher tool was made for testing and educational purposes, ME is not responsible for what you do on/with your device using newflasher, you must agree that you using newflasher on your own risk, I am not responsible if you brick...
forum.xda-developers.com
I used v42, probably newer versions work, too, try not to use an older version
Booting into fastboot: hold Volume-UP and then plugging a USB cable to the computer. The blue light should be lit, if fastboot is active, screen stays blank.
Booting into flash mode: hold Volume-DOWN and then plugging a USB cable to the computer. The green light should be lit, if flash mode is active, screen stays blank.
Now let's get to the process of flashing LOS:
Step 1 - Flash an original working SONY image into Slot A:
Boot into fastboot mode, so the blue light is on.
Type:
fastboot reboot bootloader
(Sometimes the computer doesn't recognise the phone after this command, then just unplug the USB, wait until the phone is off, and try again beginning Step 1. It can fail a couple of times, but it will also work in between).
fastboot --set-active=a
fastboot reboot bootloader
You can check that Slot A is active by typing the command
fastboot getvar all
in the output check the line current slot active: a
Run Newflasher (how to use Newflasher is beyond the scope of this post, google it) to flash an original stock SONY image. You need to be in flash mode for Newflasher with the green light lit.
Answer the first question what to do when done with Newflasher with 'p'=Power Off, and all others with 'n'=No.
When Newflasher completes, check the last few lines output, it should say setting slot A active and OKAY. That confirms that you flashed the original SONY image in Slot A.
You now have a fully working operating system in Slot A. However there is a bug in Newflasher and that bug destroys the boot process in Slot B, which means you'll be only able to boot Slot A, booting Slot B will fail.
Should you decide to boot the operating system (you don't have to), make sure you don't set up authentication (pin code, fingerprint), skip setting that up, so your data partition doesn't get encrypted.
Step 2 - Flash an original working SONY image into Slot B:
Boot into fastboot mode, so the blue light is on.
Type (similar to Step 1):
fastboot reboot bootloader
fastboot --set-active=b
fastboot reboot bootloader
You can check that Slot B is active by typing the command
fastboot getvar all
in the output check the line current slot active: b
WARNING: DO NOT BOOT Slot B, as it will fail 2-3 times (you'll notice the phone vibrating upon crash and reboot), because the phone will then put you back on Slot A, and you'll flash Slot A again. Make sure YOU DON'T BOOT the operating system in Slot B, or you'll end up in Slot A again.
Run Newflasher (how to use Newflasher is beyond the scope of this post, google it) to flash an original stock SONY image. You need to be in flash mode for Newflasher with the green light lit.
Answer the first question what to do when done with Newflasher with 'p'=Power Off, and all others with 'n'=No.
When Newflasher completes, check the last few lines output, it should say setting slot B active and OKAY. That confirms that you flashed the original SONY image in Slot B.
You now have a fully working operating system in Slot B. However there is a bug in Newflasher and that bug destroys the boot process in Slot A, which means you'll be only able to boot Slot B.
At this point in time, if you would try to boot into Slot A, it will boot up to the SONY logo, and then crash, and reboot up to the SONY logo, and then crash. Should you get stuck in that loop, insert a USB cable and hold Volume-UP, it'll catch the crashing loop, and you'll end up in fastboot.
Step 3 - Boot the original SONY image up to the home screen where the apps show:
Actually you should be in Slot B already, but if you are not:
Boot into fastboot mode, so the blue light is on.
Type (similar to Step 2):
fastboot reboot bootloader
fastboot --set-active=b
fastboot reboot bootloader
You can check that Slot B is active by typing the command
fastboot getvar all
in the output check the line current slot active: b
Boot the phone's operating original stock image in Slot B, until you are at the home screen with the apps. This sets up all the defaults for your phone, and updates any ROM images in the chips (like modem etc.).
Make sure you don't set up authentication (pin code, fingerprint), skip setting that up, so your data partition doesn't get encrypted.
Power off your phone.
Step 4 - Flash twrp into Slot B
Type (similar to Step 2):
fastboot reboot bootloader
fastboot --set-active=b
fastboot reboot bootloader
fastboot flash boot twrp.img
This will flash TWRP as boot in Slot B. Make sure in the screen output it was flashed in boot_b.
Should you make an error here, start with Step 1. The reason here is, we want LOS in Slot A, and not TWRP.
Boot your TWRP in Slot B.
WARNING: DO NOT flash VBMETA, it'll break the boot process, and you can start from Step 1.
Step 5 - Flash LOS into Slot A
Once TWRP is running, go to Wipe.
WARNING: DO NOT perform factory reset.
Go to Advanced Wipe, and ONLY WIPE 'Data' and 'Dalvic Cache'
WARNING: DO NOT WIPE System or Internal Storage. You'll loose mount points under Linux, and the LOS image flash will fail.
Go back to TWRP home screen.
From there go to Advanced and from there to ADB Sideload.
From the computer start installing your LOS image (sideload).
On the computer type:
adb sideload <Your LOS image>.zip.
ATTENTION: During flashing, the phone will show, which slot it flashes. It should flash and show: "flashing inactive Slot A". If you accidentally flash Slot B, start from the beginning Step 1.
Best results I had with the image from the LOS homepage https://download.lineageos.org/xz2c
Download the zip file, don't unpack it, use adb sideload to upload the zip file.
Forget about the Recovery image on the LOS homepage. You don't need it.
When flashing completes, you can wipe Delvic Cache.
WARNING: DO NOT WIPE 'cache', since a 2 slot phone doesn't have a cache partition, and it will fail to wipe it.
Do NOT install the TWRP app, skip this step.
Reboot
Step 6 - Boot LOS
LOS is in Slot A, TWRP is in Slot B.
You can alternate between the slots from fastboot.
fastboot reboot bootloader
fastboot --set-active=a
fastboot reboot bootloader
A reboot should boot LOS.
ATTENTION: When the LOS image has finished booting and you get to the date/time screen, the LOS will hang a while (30s). Just let it do it's job, I think (not sure), it's creating the data in the user partition. After 30s or so use the back key, and try setting the time again. This only happens on the very first boot.
Let me know as feedback, if I can clarify better or if this description is ok.

Hello,
if there is anything I can help with getting official support for LineageOS 18.1 pls let me know.

Garfield24 said:
After a LOT of trial and error I am making a description, how to get a running LOS on your SONY XZ2 Compact Single SIM (and probably Dual SIM). This is not a description for people, who got it running the easy way. It's for people that tried everything, and can't get it running, and are in desperation and lost.
General description first: The SONY XZ2 Compact is a phone with 2 slots. These phones don't have a recovery partition, so you cannot meaningfully boot into a recovery partition like on old phones. It now has a boot partition (2 of them - slot A and slot B), and you can boot an operating system from these slots. These slots are completely separate, you can boot an operating system in slot A and another separate one in slot B. These slots (from a user perspective) are separate, and there is very little interchange between them (or more or less none).
Prerequisits: TWRP, I used the Version from MartinX 2020-06-14_21-07-37_twrp_apollo.tar.gz , link is here: https://androidfilehost.com/?w=files&flid=306949
Use a STOCK TWRP
Extract the .img files with 7-zip (7-zip.org), until you have the .img file separate.
Newflasher:
[TOOL] Newflasher (xperia command line flasher)
Disclaimer: newflasher tool was made for testing and educational purposes, ME is not responsible for what you do on/with your device using newflasher, you must agree that you using newflasher on your own risk, I am not responsible if you brick...
forum.xda-developers.com
I used v42, probably newer versions work, too, try not to use an older version
Booting into fastboot: hold Volume-UP and then plugging a USB cable to the computer. The blue light should be lit, if fastboot is active, screen stays blank.
Booting into flash mode: hold Volume-DOWN and then plugging a USB cable to the computer. The green light should be lit, if flash mode is active, screen stays blank.
Now let's get to the process of flashing LOS:
Step 1 - Flash an original working SONY image into Slot A:
Boot into fastboot mode, so the blue light is on.
Type:
fastboot reboot bootloader
(Sometimes the computer doesn't recognise the phone after this command, then just unplug the USB, wait until the phone is off, and try again beginning Step 1. It can fail a couple of times, but it will also work in between).
fastboot --set-active=a
fastboot reboot bootloader
You can check that Slot A is active by typing the command
fastboot getvar all
in the output check the line current slot active: a
Run Newflasher (how to use Newflasher is beyond the scope of this post, google it) to flash an original stock SONY image. You need to be in flash mode for Newflasher with the green light lit.
Answer the first question what to do when done with Newflasher with 'p'=Power Off, and all others with 'n'=No.
When Newflasher completes, check the last few lines output, it should say setting slot A active and OKAY. That confirms that you flashed the original SONY image in Slot A.
You now have a fully working operating system in Slot A. However there is a bug in Newflasher and that bug destroys the boot process in Slot B, which means you'll be only able to boot Slot A, booting Slot B will fail.
Should you decide to boot the operating system (you don't have to), make sure you don't set up authentication (pin code, fingerprint), skip setting that up, so your data partition doesn't get encrypted.
Step 2 - Flash an original working SONY image into Slot B:
Boot into fastboot mode, so the blue light is on.
Type (similar to Step 1):
fastboot reboot bootloader
fastboot --set-active=b
fastboot reboot bootloader
You can check that Slot B is active by typing the command
fastboot getvar all
in the output check the line current slot active: b
WARNING: DO NOT BOOT Slot B, as it will fail 2-3 times (you'll notice the phone vibrating upon crash and reboot), because the phone will then put you back on Slot A, and you'll flash Slot A again. Make sure YOU DON'T BOOT the operating system in Slot B, or you'll end up in Slot A again.
Run Newflasher (how to use Newflasher is beyond the scope of this post, google it) to flash an original stock SONY image. You need to be in flash mode for Newflasher with the green light lit.
Answer the first question what to do when done with Newflasher with 'p'=Power Off, and all others with 'n'=No.
When Newflasher completes, check the last few lines output, it should say setting slot B active and OKAY. That confirms that you flashed the original SONY image in Slot B.
You now have a fully working operating system in Slot B. However there is a bug in Newflasher and that bug destroys the boot process in Slot A, which means you'll be only able to boot Slot B.
At this point in time, if you would try to boot into Slot A, it will boot up to the SONY logo, and then crash, and reboot up to the SONY logo, and then crash. Should you get stuck in that loop, insert a USB cable and hold Volume-UP, it'll catch the crashing loop, and you'll end up in fastboot.
Step 3 - Boot the original SONY image up to the home screen where the apps show:
Actually you should be in Slot B already, but if you are not:
Boot into fastboot mode, so the blue light is on.
Type (similar to Step 2):
fastboot reboot bootloader
fastboot --set-active=b
fastboot reboot bootloader
You can check that Slot B is active by typing the command
fastboot getvar all
in the output check the line current slot active: b
Boot the phone's operating original stock image in Slot B, until you are at the home screen with the apps. This sets up all the defaults for your phone, and updates any ROM images in the chips (like modem etc.).
Make sure you don't set up authentication (pin code, fingerprint), skip setting that up, so your data partition doesn't get encrypted.
Power off your phone.
Step 4 - Flash twrp into Slot B
Type (similar to Step 2):
fastboot reboot bootloader
fastboot --set-active=b
fastboot reboot bootloader
fastboot flash boot twrp.img
This will flash TWRP as boot in Slot B. Make sure in the screen output it was flashed in boot_b.
Should you make an error here, start with Step 1. The reason here is, we want LOS in Slot A, and not TWRP.
Boot your TWRP in Slot B.
WARNING: DO NOT flash VBMETA, it'll break the boot process, and you can start from Step 1.
Step 5 - Flash LOS into Slot A
Once TWRP is running, go to Wipe.
WARNING: DO NOT perform factory reset.
Go to Advanced Wipe, and ONLY WIPE 'Data' and 'Dalvic Cache'
WARNING: DO NOT WIPE System or Internal Storage. You'll loose mount points under Linux, and the LOS image flash will fail.
Go back to TWRP home screen.
From there go to Advanced and from there to ADB Sideload.
From the computer start installing your LOS image (sideload).
On the computer type:
adb sideload <Your LOS image>.zip.
ATTENTION: During flashing, the phone will show, which slot it flashes. It should flash and show: "flashing inactive Slot A". If you accidentally flash Slot B, start from the beginning Step 1.
Best results I had with the image from the LOS homepage https://download.lineageos.org/xz2c
Download the zip file, don't unpack it, use adb sideload to upload the zip file.
Forget about the Recovery image on the LOS homepage. You don't need it.
When flashing completes, you can wipe Delvic Cache.
WARNING: DO NOT WIPE 'cache', since a 2 slot phone doesn't have a cache partition, and it will fail to wipe it.
Do NOT install the TWRP app, skip this step.
Reboot
Step 6 - Boot LOS
LOS is in Slot A, TWRP is in Slot B.
You can alternate between the slots from fastboot.
fastboot reboot bootloader
fastboot --set-active=a
fastboot reboot bootloader
A reboot should boot LOS.
ATTENTION: When the LOS image has finished booting and you get to the date/time screen, the LOS will hang a while (30s). Just let it do it's job, I think (not sure), it's creating the data in the user partition. After 30s or so use the back key, and try setting the time again. This only happens on the very first boot.
Let me know as feedback, if I can clarify better or if this description is ok.
Click to expand...
Click to collapse
So this works for 17.1 - but have you tried it on 18.1?
Asking because 17.1 works well for me following the official install method (via stock LOS recovery), whereas 18.1 fails.

landsome said:
So this works for 17.1 - but have you tried it on 18.1?
Asking because 17.1 works well for me following the official install method (via stock LOS recovery), whereas 18.1 fails.
Click to expand...
Click to collapse
It works on my phone, however:
I only have a 18.0 image from Olivier. Link is here: https://androidfilehost.com/?w=files&flid=320371
Use the 700MB image, the 200MB image (dated 20201206) probably won't work, the file size is too small. Not sure what the 200MB image is for. At the time of this post the image that worked was dated 20201205.
Anybody working on a 18.1 image, please post it here? I don't have the expertise to help with 18.1 image.
Directly flashing 18.0 image by Olivier crashed my phone, I am not sure why. There is no real reason I know of, but it did.
I first flashed official LOS 17.1 image from LOS homepage using the method above, and it worked. Boot the image to the home screen to intialise everything on LOS. Should it fail, you have a corrupt LOS image. I only had nightly builds available at the time of this post. Maybe that changes soon...
I then went back to slot B and booted TWRP again. I then sideloaded the LOS 18.0 .zip image from Olivier with adb sideload <imagefile.zip> without wiping anything. Don't wipe any partitions, just flash the 18.0 LOS image over the existing installation in Slot A.
When booting the LOS 18.0 image, it says data corrupt (I don't know why), and it boots into the LOS recovery and asks for a factory reset. Do a factory reset, you'll loose all data on the phone, so backup what needs to be backed up first. You probably need to install the apps again as well.
After the factory reset, the phone boots LOS 18.0 just fine.
I noticed there is no email client in the LOS 18.0 image from Olivier. Should you need it, the following tip:
IMPORTANT: When in TWRP (before you flash LOS 18.0), MOUNT System and Data in the mount menu.
You can then find the apk for the LOS email client in the LOS 17.1 image:
/system/system/product/app/Email/Email.apk
/system/system/product/app/Exchange2/Exchange.apk
Copy these apk in the TWRP file manager to /data/media/downloads
Boot LOS 17.1 and backup these apk files to your PC to install on LOS 18.0. The apk files are in your phone's download directory after the copy operation in TWRP.
The Exchange.apk is an extension package to the Email.apk to add Exchange client functionality.
IMPORTANT: After installing the apk on LOS 18.0, and even before you start them for the first time, go to Settings, and give "Email" and "Exchange" all permissions on your phone. Just allow everything. If you don't do that, the applications will crash upon start.
Hope that helps. Any questions, please ask.

A new build is up, please check the OP. Feel free to test and report bugs - we'd like to enable official 18.1 weekly builds soon.

Olivier said:
A new build is up, please check the OP. Feel free to test and report bugs - we'd like to enable official 18.1 weekly builds soon.
Click to expand...
Click to collapse
Thanks. We appreciate this.

Hi,
I have a problem with Wire application.
Microphone is not working on call and video call.
Microphone is working to record a message. Permissions are OK.
I had the same problem on LOS 17 so I thought upgrade will resolve it. NO.
Did anyone experience the same problem?

Raphos said:
Hi,
I have a problem with Wire application.
Microphone is not working on call and video call.
Microphone is working to record a message. Permissions are OK.
I had the same problem on LOS 17 so I thought upgrade will resolve it. NO.
Did anyone experience the same problem?
Click to expand...
Click to collapse
I have the exact same problem with LOS 17, and with 18 too!
Wire is not only the affected program, skype has for example the exact same issue.
And unfortunately I do not know how to fix it.

Thanks for your reply.
Ok, good to know. I have a Z3 compact on LOS 17 and a Z5 Compact on LOS 15, Wire is working fine.
Microphone is working with whatsapp calls. Maybe Devs are whatsapp shareholders

Raphos said:
Ok, good to know. I have a Z3 compact on LOS 17 and a Z5 Compact on LOS 15, Wire is working fine.
Click to expand...
Click to collapse
I can confirm to that LOS 17 and 18 on other devices have no issues, thus it seems xz2c specific

[GUIDE][UPDATED] Unlocking JioFi 3 JMR540 & JMR541 for all networks

Unlocked Firmware for JioFi 3 JMR540 & JMR541
Disclaimer
I am not responsible for any kind of damage to your device.
Use this firmware at your own risk
Post is for educational purpose only.
ONLY FOR JMR 540 & JMR 541
​I was able to dump and reverse engineer JioFi 3's firmware to see if I can unlock the SIM restrictions. JioFi 3 is designed by Foxconn it uses generic firmware. Unlocking took time though. Tested with Vi, Airtel.
UPDATE 17-10-21: Jio pushed a firmware update which is locking boot loader. If your device is not updated yet it is advised to re-flash your firmware with patched image given below which basically disables auto updates. If you're already locked out, currently there's no easy fix for that.
If you haven't used your device from a long time or you're still on lower or equal version than below it is advised not to use JioFi with SIM, flash this firmware first if you want to test SIM unlock.
Guide
Make sure you're on same or lower firmware version
JMR 540 - FXN_JMR540_R6.16
JMR 541 - FXN_JMR541_R3.10
1. Locate your device model and download the respective Firmware and extract it to a known location
JMR540_unlocked_patched_system.zip​
JMR541_unlocked_patched_system.zip​
2. Install drivers and tools (skip if already installed)
Install Fastboot drivers ( google it for mac and linux it's easy to find)​
Install Fastboot ( google it for mac and linux it's easy to find)​
3. Prepare device
Remove battery from JioFi 3
Locate reset pin hole button
Lay down JioFi 3
Use Paper Clip / SIM Ejector Tool to press button inside (using sharp object is not recommended)
Keep pressing button down and insert USB cable
Release button as soon as all the LEDs in Display turns RED. This means device is in boot loader mode
4. Flashing Unlocked Firmware
Open adb and fastboot tools terminal
Enter following to check if device is connected
fastboot devices
It will return something like this
baxxxxx fastboot
This means device is connected. If your device doesn't show up here please check drivers in Device manager
Now first erase the system partition
fastboot erase system
It will return something like this
erasing 'system'...
OKAY [ 1.104s]
finished. total time: 1.105s
Now flash the firmware
fastboot flash system "D:\system.img" ( replace path )
It should return something like this
sending 'system' (34306 KB)...
OKAY [ 1.276s]
writing 'system'...
OKAY [ 9.462s]
finished. total time: 10.741s
Now send reboot command to device
fastboot reboot
You'll notice device will reboot normally now you can unplug the cable.
Congratulations your device is now unlocked and you can reinsert battery and another SIM for testing.
Firmware will take long time than usual to boot do not panic.​
4. Changing APN
Insert SIM connect with JioFi 3 wait it to intialize
Open Web UI from browser (http://jiofi.local.html/)
Now login (default username/pwd is administrator/administrator)
In Network Tab you'll find setting for changing APN
Put it on manual and enter "internet" as APN (without quotes)
Hit apply/save device will reboot again automatically and it'll auto connect
Just wait patience is the key here it'll connect.
If something goes WRONG or you want to UNDO you can re flash original firmware which is provided in this post.
Original backup
JMR_540_original_system.zip​
JMR_541_original_system.zip​
FAQs
Q. My device is not visible in fastboot devices
A. Confirm driver installation a faulty cable can also be the issue.
.
Q. Everything went well but still no changes in dashboard
A. After successful flash if you still don't see the changes your device is probably booting from recovery partition. Try flashing recovery partition by
fastboot erase recoveryfs
fastboot flash recoveryfs "D:\system.img"
.
Q. After resetting device from pin hole button it shows INVALID SIM.
A. This is supposed to happen just reboot the device it'll work again.
.
Q. Can I undo all this and get back to original firmware
A. Yes just flash the original firmware provided in post and reset the device.
.
Q. I 'accidentally' flashed my recovery and boot partition
A. Well accidentally I've backed up recovery and boot download from below
1. JMR540_boot_recovery.rar
2. JMR541_boot_recovery.rar
.
Q. FAILED: (remote: Image is locked) issue while erasing/flashing image
A. Jio recently pushed an firmware update which re-locks simlock and bootloader which basically means you can't flash unsigned/custom firmware. Currently there is no fix.
​
Mentions:
Thanks to Karuppusamy for testing it on JMR541.
What about JioFi 2, 4, 5, 6?
Reverse Engineering takes lot of time and coffee. Until I get physical access to device I won't be able to unlock it. I'm constantly searching them on OLX as soon as I get hands on I'll surely try to RE and unlock it. I'll update the same here if there is no update here at the time of your reading then I haven't got the device yet so please don't spam for update hope you understand that I don't get anything by doing these things, I do it for liberation of locked hardware to meet it's real destiny and of course for the people. I also have a day job so no I cannot guide or teach you, hope you understand why.
For Devs:
JMR_540_FLASH_DUMP.rar
​

Reserved

successfully unlocked my jiofi 3 JMR541. tested with voda and its working well and good. Thanks a ton for this bro.
I was late in checking this thread and got shipped airtel unlocked mifi from home.

sksinha said:
successfully unlocked my jiofi 3 JMR541. tested with voda and its working well and good. Thanks a ton for this bro.
I was late in checking this thread and got shipped airtel unlocked mifi from home.
Click to expand...
Click to collapse
Can you show us dashboard screenshot. This will help other users to verify

abhimortal6 said:
Can you show us dashboard screenshot. This will help other users to verify
Click to expand...
Click to collapse
...

Nice, enjoy!

abhimortal6 said:
Nice, enjoy!
Click to expand...
Click to collapse
bro is unlocking more 4g bands or manual selection of bands can be done ?

sksinha said:
bro is unlocking more 4g bands or manual selection of bands can be done ?
Click to expand...
Click to collapse
Totally possible even 3G but it can't be done through WebUI it'll requires shell access.

Totally working! thanks a ton a bro <3

srbhsngwn said:
Totally working! thanks a ton a bro <3
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Great

..

myapky said:
JMR540 ERROR
Click to expand...
Click to collapse
you haven't properly specified the address of system.img Please give the complete path

srbhsngwn said:
you haven't properly specified the address of system.img Please give the complete path
Click to expand...
Click to collapse
Fixed issue.

myapky said:
there is a issue with JMR540, however I have successfully flashed JMR541 file on friends JioFi 3.
There is definitely a issue with JMR540 system.img file. request @abhimortal6 to check the file and reupload.
I have added a device info details for JMR540
Click to expand...
Click to collapse
This issue is not related to flash file as I own JMR 540 and it's been tested on multiple devices (refer attached image). "Not working" and "Not flashing" are two different things.
"flash write error" is a sign of bad emmc/nand, bad partition table can also be the cause. Please first try with original firmware and collect information by different permutations (re-downloading image, erasing system before flashing etc) before spamming.

abhimortal6 said:
This issue is not related to flash file as I own JMR 540 and it's been tested on multiple devices (refer attached image). "Not working" and "Not flashing" are two different things.
"flash write error" is a sign of bad emmc/nand, bad partition table can also be the cause. Please first try with original firmware and collect information by different permutations (re-downloading image, erasing system before flashing etc) before spamming.
View attachment 5326935
Click to expand...
Click to collapse
I am not spamming i am facing issue so I mentioned at XDA. I am facing 'flash write error' with the original system.img file too. Unable to flash img files.. Any solution to that ?

myapky said:
I am not spamming i am facing issue so I mentioned at XDA. I am facing 'flash write error' with the original system.img file too. Unable to flash img files.. Any solution to that ?
Click to expand...
Click to collapse
A single post with all the details in it would be sufficient.
As stated in previous post please try the following.
Try flashing original firmware first
Try erasing system partition ( fastboot erase system)
Try re downloading image
If you're getting flash write error in original firmware too then you're nand is probably fried.
try flashing recoveryfs partition
Bash:
fastboot flash recoveryfs "system.img"

abhimortal6 said:
A single post with all the details in it would be sufficient.
As stated in previous post please try the following.
Try flashing original firmware first
Try erasing system partition ( fastboot erase system)
Try re downloading image
If you're getting flash write error in original firmware too then you're nand is probably fried.
try flashing recoveryfs partition
Bash:
fastboot flash recoveryfs "system.img"
Click to expand...
Click to collapse
nand was dead...due to all day work on JioFi, now all good thanks for help.

abhimortal6 said:
Unlocked Firmware for JioFi 3 JMR540 & JMR541
Disclaimer
I am not responsible for any kind of damage to your device.
Use this firmware at your own risk
Post is for educational purpose only.
ONLY FOR JMR 540 & JMR 541
​I was able to dump and reverse engineer JioFi 3's firmware to see if I can unlock the SIM restrictions. JioFi 3 is designed by Foxconn it uses generic firmware. Unlocking took time though. Tested with Vi, Airtel.
Guide
Make sure you're on same firmware version
JMR 540 - FXN_JMR540_R6.16
JMR 541 - FXN_JMR541_R3.10
If not please use the device for sometime it'll autoupdate.
1. Locate your device model and download the respective Firmware and extract it to a known location
JMR540_unlocked_system.zip​
JMR541_unlocked_system.zip​
2. Install drivers and tools (skip if already installed)
Install Fastboot drivers ( google it for mac and linux it's easy to find)​
Install Fastboot ( google it for mac and linux it's easy to find)​
3. Prepare device
Remove battery from JioFi 3
Locate reset pin hole button
Lay down JioFi 3
Use Paper Clip / SIM Ejector Tool to press button inside (using sharp object is not recommended)
Keep pressing button down and insert USB cable
Release button as soon as all the LEDs in Display turns RED. This means device is in boot loader mode
4. Flashing Unlocked Firmware
Open adb and fastboot tools terminal
Enter following to check if device is connected
fastboot devices
It will return something like this
baxxxxx fastboot
This means device is connected. If your device doesn't show up here please check drivers in Device manager
Now first erase the system partition (Skip for JMR 540 )
fastboot erase system
It will return something like this
erasing 'system'...
OKAY [ 1.104s]
finished. total time: 1.105s
Now flash the firmware
fastboot flash system "D:\system.img" ( replace path )
It should return something like this
sending 'system' (34306 KB)...
OKAY [ 1.276s]
writing 'system'...
OKAY [ 9.462s]
finished. total time: 10.741s
Now send reboot command to device
fastboot reboot
You'll notice device will reboot normally now you can unplug the cable.
Congratulations your device is now unlocked and you can reinsert battery and another SIM for testing.
Firmware will take long time than usual to boot do not panic.​
4. Changing APN
Insert SIM connect with JioFi 3 wait it to intialize
Open Web UI from browser (http://jiofi.local.html/)
Now login (default username/pwd is administrator/administrator)
In Network Tab you'll find setting for changing APN
Put it on manual and enter "internet" as APN (without quotes)
Hit apply/save device will reboot again automatically and it'll auto connect
Just wait patience is the key here it'll connect.
If something goes WRONG or you want to UNDO you can re flash original firmware which is provided in this post.
Original backup
JMR_540_original_system.zip​
JMR_541_original_system.zip​
FAQs
Q. My device is not visible in fastboot devices
A. Confirm driver installation a faulty cable can also be the issue.
.
Q. Everything went well but still no changes in dashboard
A. After successful flash if you still don't see the changes your device is probably booting from recovery partition. Try flashing recovery partition by
Bash:
fastboot flash recoveryfs "system.img"
.
Q. After resetting device from pin hole button it shows INVALID SIM.
A. This is supposed to happen just reboot the device it'll work again.
.
Q. Can I undo all this and get back to original firmware
A. Yes just flash the original firmware provided in post and reset the device.
​
Mentions:
Thanks to Karuppusamy for testing it on JMR541.
​
Click to expand...
Click to collapse
Hi, i just read ur article on unlocking jiofi 3 and that looked amazing.But i have a jiofi JMR815 and have been looking for help to unlock it from a couple of years.But till date only your post looks promising and i ask yourhelp in helping me unlock my JioFi JMR815.Kindly consider helping me.Also i created an account in XDA just to ask your help
View attachment 5327245
View attachment 5327247
View attachment 5327249
View attachment 5327251

This is completely genius! I am now able to use Airtel sim on my JioFi! Thanks!

Question how to boot from different slot ?

Мy bootloader is unlocked. My device is Le2127. I reboot into bootloader mode, switch the active slot, then reboot and get back into the bootloader. How to load firmware from another slot? Thanks.
OxygenOS 13.0 Stable F.17 GL
Android 13

stranger75 said:
Мy bootloader id unlocked. My device is Le2127. I reboot into bootloader mode, switch the active slot, then reboot and get back into the bootloader. How to load firmware from another slot?
Click to expand...
Click to collapse
What is your active slot now?

A (B not loaded) if I flash the firmware into another slot (B), then only B is loaded
In the installer script, the firmware commands write to both slots, but only the active one is loaded

stranger75 said:
A (B not loaded) if I flash the firmware into another slot (B), then only B is loaded
In the installer script, the firmware commands write to both slots, but only the active one is loaded
Click to expand...
Click to collapse
Then I don't truly understand what you are trying to do or what problem you are having.

I would like to boot from any slots, for example, if the system is damaged on one slot. As far as I know they have a common userdate section
here is a related article:
Installation of Stock ROM on both slots.
Hello friends, I have read in the threads about installation of oxygen OS on both slots to be safe to install custom ROM to avoid any error. I want to know the step by step procedure to install the stock ROM on both slots. Thanks.
forum.xda-developers.com
But it doesn't work here

stranger75 said:
I would like to boot from any slots, for example, if the system is damaged on one slot. As far as I know they have a common userdate section
here is a related article:
Installation of Stock ROM on both slots.
Hello friends, I have read in the threads about installation of oxygen OS on both slots to be safe to install custom ROM to avoid any error. I want to know the step by step procedure to install the stock ROM on both slots. Thanks.
forum.xda-developers.com
But it doesn't work here
Click to expand...
Click to collapse
Check into the "copyslot" script. Might be an answer for you

Where can you find it for os 13 ?
In that script, support only android 11

stranger75 said:
Where can you find it for os 13 ?
In that script, support only android 11
Click to expand...
Click to collapse
"fastboot getvar all" will tell you active slot while in fastboot.
fastboot --set-active=a
&
fastboot --set-active=b
is changing active slot

I know it and have done it. But loading from another slot does not happen.
Instead of loading the system, I get into Bootloader

stranger75 said:
I know it and have done it. But loading from another slot does not happen.
Instead of loading the system, I get into Bootloader
Click to expand...
Click to collapse
I have heard some say flash firmware twice to get same on both slots...otherwise I am out of ideas!

I tried several times when switching the slot via fastboot, but each time only the one installed in the current slot is loaded

@stranger75
I am not sure that it is still possable to have two seperate system levels installed since the intoduction of Dynamic Partitions.
Implementing Dynamic Partitions - [source.android] - [website] - Link
Cheers.