yashsingh1/xdaforums huggingface dataset:
[Sony Xperia 10 Plus Questions & Answers] Rebel_X:
Do you mind to elaborate about the steps taken to get and patch boot image?

What I did is I grabbed the "boot_X-FLASH-ALL-8F02.sin" file, used UnSIN tool to convert it to "boot.img" and then Android Image Kitchen AIK to unpack and repack the image (this step is necessary on older Xperia phone, is that the case here?), then finally patch the repacked boot image using Magisk.

But when flashing the new patched boot image, I get a non functional touch screen and wifi. I was able to control the phone using ScrCpy tool to mirror the phones screen on my computer and control the phone from the window that appears on the computer. But since WIFI won't even turn on, I couldn't even verify that Magisk was working or not.

What is worse, is that if I tried to flash the original untouched Boot image SIN or the converted IMG, the phone still has non-working touch-screen and WIFI.

FlashTool by Androxyde and EMMA tools do NOT support this phone yet. I ended up using Newflasher tool to go back to stock (still unlocked bootloader) and everything works fine, but no root.

I have the US model I3223 btw.

Thank you kindly, awaiting your response.
[Sony Xperia 10 Plus Questions & Answers] Zaben:
Magisk Manager (the app) was able to patch boot_X-FLASH-ALL-8F02.sin directly and return an img file. I used fastboot to flash the patched boot.
[Sony Xperia 10 Plus Questions & Answers] Rebel_X:
Thanks a lot!! And it was as simple as that. :) It works fine. :good:
[Sony Xperia 10 Plus Questions & Answers] MAREK10747:
I can do kernel with magisk for you :) I need only sin file boot_X-FLASH-ALL from .ftf file :) Who want to get the kernel , please send to me pm with this file and variant (I32XX or I42XX) !!
[Sony Xperia 10 Plus Questions & Answers] yishisanren:
Hi,me devie is I4293

I have unrar the rom , so i get the boot_X-FLASH-ALL-8F02.sin

would you mind to make the kernel for me?

the file is here :

https://drive.google.com/file/d/1sywqfBtELSTgRXtTBEvlI454K_1ul-1h/view?usp=sharing

my gmail is zhangweiwei444@gmail.com

you can send it to me.

thank you.
[Sony Xperia 10 Plus Questions & Answers] yishisanren:
You patched boot with magisk19 or 19.1?

Now i use magisk19.1, my phone always go into a boot loap.
[Sony Xperia 10 Plus Questions & Answers] Zaben:
See https://xdaforums.com/10-plus/how-to/magisk-19-1-7-1-2-notes-t3926611
[Sony Xperia 10 Plus Questions & Answers] yishisanren:
So now Xperia 10 or 10 plus can not be rooted by magisk. Because Maigsk 19.1 will be failed
[Sony Xperia 10 Plus Questions & Answers] wang4632:
yes, i think so. it caused looping on my Xperia 10. (by Maigsk 19.1)

do you know any place and download older version of Maigsk??
[Sony Xperia 10 Plus Questions & Answers] yishisanren:
older version can not patch boot.img, because when you click "install the zip",it will let you update the new verison.
[Sony Xperia 10 Plus Questions & Answers] surdee:
Any news on the boot loop situation? I also encounterd this problem and back to running original boot.img. having an unlocked bootloader is useless without root ?
[Sony Xperia 10 Plus Questions & Answers] guoyifu2007:
Did you lose any feature like super vivid mode and camera focusing after unlocking the bootloader?
[Sony Xperia 10 Plus Questions & Answers] satitaevas:
can't find the driver, the model is l421dual sim, can't rooting, have i already patched the boot img?
[Sony Xperia 10 Plus Questions & Answers] Zack_U:
My I4293 stuck in bootloop~~help ~!

After installing Magisk19.3 with TWRP, my phone stuck in bootloop and can not enter the recovery mode.

I tried to flash I4293_53.0.A.6.96_1318-2077_R1A.ftf (Factory ftf. downloaded from experifirm) with flashtool to solve this problem.

when I tried to create bundle, I found that I4293 did not show in the ID list.

I can't do anything about it.

Anybody can help me plz~~ I'm fresh in XDA and just try to root my phone first time :crying:
[Sony Xperia 10 Plus Questions & Answers] satitaevas:
This phone cannot be rooted at this time due to the lack of the img.patch and no driever.
[Sony Xperia 10 Plus Questions & Answers] Zaben:
Are you still stuck? For all of the latest Sony phones try NewFlasher instead.

https://xdaforums.com/crossdevice-dev/sony/progress-newflasher-xperia-command-line-t3619426

Flashtool doesn't support our phones. Magisk 19.1+ currently doesn't work with our phones. Hopefully 19.4 will fix that.
[Samsung Galaxy S10e Guides, News, & Discussion] LucaFraga:
So, I have a Exynos variant of the S10E and I'm having mixed result with battery life:

If I use my phone a lot (and I mean a lot) for example when I'm traveling i get about 6 hours of SoT which is great with a 3.100mah battery and heavy usage.

However on a regular day the phone just seems to discharge itself when in standby mode and I don't even reach 3 hours of SoT.

My setup is simple: all apps are disabled when on standby except for WhatsApp, Telegram and some e-commerce stuff and in the Battery stats "Android OS" in on top of everything (except for screen).

Are you having the same issue? Did you manage to find the cause? Let's discuss it.
[Samsung Galaxy S10e Guides, News, & Discussion] abysstheking:
This solution was posted on the S10 forum and certainly helped me.

There's a bug that stops the phone from going into a deep sleep mode post making a call (audio/video) on apps like WhatsApp, Skype et al. The solution for the time being is to reboot the phone once before going to bed. I tried a lot of other things but had a ~2% hourly standby drain which reduced to <5% overnight after figuring out this solution. I have both WiFi and Bluetooth on at night.

You may try to play around with the battery saving tweaks in ONE UI but nothing worked as well as this has. Hopefully there'll be a more practical fix to this soon.

Cheers!
[Samsung Galaxy S10e Guides, News, & Discussion] LucaFraga:
Hi! Thanks for your feedback.

I have my S10E scheduled to reboot every night but this doesn't seem to fix the issue and I also don't use whatsapp/telegram voice/video calls, so I don't think is is quite the issue.

There's probably something else preventing deep sleep, but I think that waiting for an update from Samsung will be my best bet
[Samsung Galaxy S10e Guides, News, & Discussion] abysstheking:
That's interesting. There are over two dozen people on the s10 page confirming this to have solved their drain.

For how many days have you had your device? Mine took a while to understand my usage pattern

I am currently getting over 5 hours SoT over 18-20 hours now, it was ~3 hours previously.
[Samsung Galaxy S10e Guides, News, & Discussion] daemmon:
I'm having the same issue. No video calls and still losing ~2% per hour. Restart doesn't help.
[Samsung Galaxy S10e Guides, News, & Discussion] arsenal74:
Mine too, lost 3% in under an hour sitting in my pocket doing nothing. As usual the battery stats are not much use.
[Samsung Galaxy S10e Guides, News, & Discussion] techhahn:
There's a bug with the proximity sensor. The phone gets turned on automatically in the pocket which might cause battery drain.

BTW putting the phone on battery saver (Medium power saving) mode stops battery drain. Until we get a fix from Samsung this seems like a worthy option.
[Samsung Galaxy S10e Guides, News, & Discussion] ijuanp03:
Nope. It's not only when sitting in the pocket. Basically put it on a table and the battery will drain.
[Samsung Galaxy S10e Guides, News, & Discussion] the_wing:
There's people on the S10 forum reporting a much better battery performance after a software update (ASC8) on the Exynos S10 / S10+ (see here or here) that should fix the drain issues. Do you know if they are rolling it out also for the S10e Exynos?
[Samsung Galaxy S10e Guides, News, & Discussion] raulillo88:
It seems ASC8 has been stopped, and they are releasing ASCA. For now it has only released for Germany firmwares. Let's see what's new in this update. Regards
[Samsung Galaxy S10e Guides, News, & Discussion] Milovv:
Same issue

I have the same problem, when phone is in use it gets great SoT of around 6 hours, but when not in use throughout the day battery still drains very quickly. I was hoping the update will fix it , but even after updating, nothing changed. Hopefully there is a solution soon.
[Samsung Galaxy S10e Guides, News, & Discussion] Edgrr000:
Seems like battery drain issue was fixed in the latest update ASCA. Mine was previously draining 15% overnight. Now it only drained 4% in 8 hours!! Which is pretty amazing.
[Samsung Galaxy S10e Guides, News, & Discussion] ermacwins:
Anyone have the Hong Kong model G9700? I've noticed standby drain is quite high.
[Samsung Galaxy S10e Guides, News, & Discussion] route9:
I have German ASCA version, but battery is draining awfully. I use both SIM cards and loose 25 percent half a day being in standby-mode.
[Samsung Galaxy S10e Guides, News, & Discussion] techhahn:
View attachment 4740529 View attachment 4740528

Expected at least 5 hours of SOT from a phone at this price point. This is bad. Even with the second sim turned off, battery drains heavily.
[Samsung Galaxy S10e Guides, News, & Discussion] Edgrr000:
I was also having pretty bad battery drain, 15% overnight. But after the ASCA update I'm getting about 5% overnight, maybe it's just my phone?
[Samsung Galaxy S10e Guides, News, & Discussion] romaninja:
Used this guide:

https://xdaforums.com/s10-plus/how-to/galaxy-s10-battery-optimisation-guide-t3911988

After i made the tweaks the standby is decent compared to my OP6
[Samsung Galaxy S10e Guides, News, & Discussion] l_mike:
I disabled bixby on the Maine screen 4 hours ago and I do have a feeling my battery od much better. Will see...
[Samsung Galaxy S10e Guides, News, & Discussion] jasons1004:
ASDA update seems to help with drainage for me.

Using 970U1 TMB version. Attached is typical usage for me last few days. I get another 6-8 hours sot average by 15% or so and about ~5% overnight drain
[Samsung Galaxy S10e Guides, News, & Discussion] exeon:
S10e Weird 999:MAILBOX_CP2AP Wakelock

Not sure why the "Android OS" always so high usage, I think in normal case, it should be lower than "Android System"..

And by using Battery Historian, I saw this kernel wake up, does anyone knows what's that?

I'm having a lot of RILJ_ACK_WL too.. Sigh.
[LG V20 Questions & Answers] Ak7J4:
I've rooted my phone around 3 times now, and something I noticed on complete stock was there was a counter for how many times the phone OEM unlocked. I wanted to know if it was possible to wipe this number.
[Xiaomi Mi 5 Questions & Answers] Zenec:
Hi

Either my mi 5 usb port is damaged or all my cables are faulty but I am unable to access adb/fastboot. I currently have unlocked bootloader + twrp + custom MIUI rom + Magisk and I want to go back to full stock (locked bootloader, stock recovery, stock ROM). Can I do that without a computer? I am currently thinking of doing this:

Download both fastboot and standard ROM from en.miui.com

Extract boot.img and recovery.img from the fastboot rom

Flash boot and recovery using Flashify app

Flash standard ROM via flashify app

Reboot

Would this work? I would also save the standard ROM as update.zip on my phone in case if I need flash it with stock recovery.

Thanks!
[Xiaomi Mi 5 Questions & Answers] panchovix:
I mean you can just flash any official ROM and you will be able to boot without problems; just the bootloader won't be ever be again locked; and you will lose TWRP in the process, since the default recovery will replace it

What are you thinking via in-phone probably won't work, I mean I can't guarantee that it won't work but I'm 90% sure that it won't
[Nextbit Robin] npjohnson:
[IMG="LineageOS logo"]https://cygwin.de/rr/lineage-os-logo.png[/IMG]

Nextbit Robin

- Your warrenty is now void.
- You have been warned.
- Use at your own risk.

Introduction:

This is the Official Lineage OS 16.0 thread for the Nextbit Robin, codename ether.

How to Install:

Please follow the instructions on our Official LineageOS Wiki page here.

If you don't follow these instructions, please don't expect support here. We also don't support 3rd party addons (Magisk/XPosed/Dolby/Viper/etc.), so please don't seek support if you use these.

Known Bugs:

IMS (VoLTE/VoWi-Fi/Carrier Video Calling) cannot be made to work on any version past Android 8.1 (LineageOS 15.1) due to compatibility issues with proprietary binaries. To remedy this, we've opted to ship LineageOS 15.1 and 16.0 simultaneously. 15.1 will continue to get weekly releases, while 16.0 will get nightly releases. *If you need/want VoLTE/VoWi-Fi/Carrier Video Calling, please use LineageOS 15.1 found here.

ANT+ is currently broken in LineageOS 16.0, while it works in 15.1, use the builds linked above if you want/need ANT+ functionality.

Notes:

Official Lineage OS builds will not pass CTS/SafetyNet.

Download:

LineageOS Updater

You're also welcome to use npjohnson's personal builds, but these are experimental, and likely to destroy your data. These builds include GApps, and Pixel-Goodies, among other things -- you'll only find no support for these, so please don't discuss them here.

XDA:DevDB Information

[OFFICIAL] [NIGHTLIES] LineageOS 16.0, ROM for the Nextbit Robin

Contributors

npjohnson, mikeioannina, javelinanddart

Source Code: https://github.com/LineageOS/

ROM OS Version: 9.x Pie

ROM Kernel: Linux 3.10.x

ROM Firmware Required: N108 Firmware

Version Information

Status: Nightly

Created 2019-03-22

Last Updated 2019-08-06
[Nextbit Robin] pay_omar:
:eek: thank you so much, i´m flashing this ASAP
[Nextbit Robin] Mchasard:
How is this official lineage os 16.0 ? Could we use for a dally driver?
[Nextbit Robin] AnierinB:
Great work guy's! :highfive:

Out of curiosity, what's the difference between the twrp linked on Los wiki compared to the one on twrp.me?
[Nextbit Robin] freddd1:
I have performed the upgrade as per wiki instructions. I performed "sideload" to get the file and then "Install" to upgrade.

Afterwards all my data was gone as if it was a clean install even though I did no wiping in the recovery.

Using the latest official TWRP from the website, version 3.2.3.0.
[Nextbit Robin] JayAbbhi:
Just to make sure, is IMS is needed to enable the phone to switch between 3g and lte for calls? I'm on tmobile, which uses Volte fro incoming call audio, but if I switch the phone manually(on other ether pie roms) to 3g, I can get incoming call audio, but no LTE until I switch it back. Is this the case with this rom?
[Nextbit Robin] blackmonk19:
Thanks [MENTION=5848265]npjohnson[/MENTION] for making this possible... :D I have reviwed the initial Pie release build...

Build Lineage-16.0-20190322

Overall a really good and stable ROM... Absolutely loved it!

All animations are smooth and the battery life is pretty decent...

I've not found any issues so far in my limited time of use, however it's very much suitable to be used as a daily drver.

p.s. - Installed the rom on top of Official Lineage OS 15.1 with Gapps mini for Android 9, wiped cache, dalvic etc. :)
[Nextbit Robin] AnierinB:
It should auto switch to 3g when you receive or make a call. That's my experience on T-Mobile and pie ROMs
[Nextbit Robin] iluvatrix:
Did you lose any data?
[Nextbit Robin] JayAbbhi:
I tried to do that, but it didn't automatically switch. I used the latest aroma gapps as well
[Nextbit Robin] blackmonk19:
Didn't loose any data at all... However the initial boot took about 5 minutes... Had to be very very patient! ?
[Nextbit Robin] PutoFace:
Anyone else having an issue with not being able to hear anything on the other end of incoming calls, and them not being able to hear you? Been having that issue for every incoming call, even after every nightly update.
[Nextbit Robin] iluvatrix:
So basically you just dirty flash the ROM and Android 9 Gapps, clear dalvic and cache and boot?
[Nextbit Robin] KUJO1001:
Thats what JayAbbhi is talking about. I had a similar issue and its completely 100% related to VOLTE. If you use 3g it'll work.
[Nextbit Robin] vandyswa:
Took the dive, am now daily driving. It's quite attractive, and maybe a little smoother than 15.1. Calls/cell/wifi/notifications are all fine, not seeing any big change in battery life. The biggie for me (BIG plus) is that 15.1 always had this little glitchy audio thing going periodicially when streaming music to Firefox. It also had a sibilant timbre to all the music. On 16.0 the glitch is pretty much gone, and it also seems like the audio has lost some of that sibilance. A change to the audio change? Better filter defaults? Dunno. But I'm pretty happy with my switch to 16.0!

Other notes: I just used the old TWRP which was there from my 15.1 install. It worked fine. As instructed, I did the clear sys/cache, then install my zip plus SU.

One disconcerting change is that when you draw the unlock pattern, the first part of the pattern will disappear as you draw, which in the past meant it accidentally registered a finger lift. But they've changed the pattern unlock so the whole path no longer displays; just where your finger is and some segments before your current position. Your unlock pattern input is fine.
[Nextbit Robin] iluvatrix:
Did you end up doing a clean install? Lose data?

Thanks
[Nextbit Robin] vandyswa:
The instructions said to wipe system and cache, so that's all I did. After install all my apps and data were intact.

One app, when started, warned me that it might not be fully compatible with the Android version. but it worked anyway. Otherwise all appears fine.
[Nextbit Robin] JayAbbhi:
Just tried to flash the rom again and only used pico gapps, and it still doesn't automatically switch
[Nextbit Robin] vandyswa:
Should have mentioned; I'm a non-gapps user. No problem with phone calls here, AT&T LTE network.

Third day as a daily driver, one freeze-up (when I tried to turn the screen on). I'm pretty happy with this ROM!
[Nextbit Robin] JayAbbhi:
what kind of gapps did you use, and do you still have incoming call audio?
[Nextbit Robin] vandyswa:
No gapps at all. Just LOS itself. I use f-droid (plus apk's from Mozilla and VLC) once the phone's running. No Google apps, no Google services.
[Nextbit Robin] iluvatrix:
Currently I am on 15.1 & opengapps nano. When I make a call or get a call LTE drops to H+ & I am fine with that.

So if I upgrade to 16 + opengapps nano will I still have the same experience?

Thanks for your help
[Nextbit Robin] jabashque:
The device tree for the official TWRP builds haven't been updated since the Marshmallow days and has very awful graphical performance. The one linked in the wiki was built off the Lineage trees instead, if I recall right, and graphics performance isn't utter crap.
[Nextbit Robin] AnierinB:
[MENTION=5848265]npjohnson[/MENTION] [MENTION=3839575]mikeioannina[/MENTION] [MENTION=5795145]javelinanddart[/MENTION] Is there source code of the omni_ether device tree that was used to compile such recovery.img?
[Nextbit Robin] npjohnson:
Do not just blindly tag us all. That's annoying and isn't going to get anywhere.

That was compiled with LineageTWRP: https://github.com/LineageTWRP - its much easier to manage encryption with this variant, builds in our trees (doesn't require a completely different device tree), and is more secure (no adb by default, etc.)
[Nextbit Robin] AnierinB:
I apologize for tagging all of you, I suppose I was just excited to get this done; I was able to create an up to date twrp device tree for ether by using TwrpGenerator.jar against the twrp.img linked on los wiki. Had to fix some issues with the fstab and boardconfig files (jars fault) and it seems to work (adb, encryption, etc) pretty smoothly. Thanks for the response
[Nextbit Robin] naveed.hasan:
My post on the other (?) ether LOS 16.0 thread

I just upgraded from 15.1 to 16.0 (MindTheGapps - I don't think Gapps matters for this issue)

Incoming calls do not hear me and I don't hear them when I am on LTE (preferred) setting in Mobile Network. The call automatically hangs up at 20 seconds. This is on T-Mobile US.

If I set the mobile data setting to 3G, all calls work fine.

I see this commit to Nuke IMS stack which is most the most likely changeset causing this issue.

[MENTION=5848265]npjohnson[/MENTION] what cellular voice network (if any) do you use on ether? T-Mobile US is definitely broken at the moment.

Anyone have any luck with incoming calls with LTE data on since last month? I can't find any setting, environment variable, database entry to alter to change this behavior.

Thanks for any leads!
[Nextbit Robin] naveed.hasan:
[MENTION=5848265]npjohnson[/MENTION]

Attaching 2 relevant logcat snippets of call activity:

1. call_type-UMTS.txt is where the incoming call phone is manually set to 3G data network only. The call connects correctly and audio is heard on both ends as expected. Manual hang up after about 12 seconds.

2. call-type-LTE.txt is where the incoming call phone is set to LTE (recommended) data network. The call is picked up but no audio is heard on either end in the earpiece or speakerphone. The call lingers in this state and automatically hangs up at about 20 seconds with no user interaction.

Leaving the phone in 3G is the only way to get an incoming call to work, there is no way to manually toggle the data network preference once a call is already ringing. Disabling mobile data does not help either, it has to be set something other than LTE.
[Nextbit Robin] JayAbbhi:
I don't know how, but when i was flashing one of the latest builds (5/13), I was actually able to hear the other end and the robin was switching from lte to 3g to h+ all on its own, though it did not do this consistently, and it only happened 4 out of the 15 calls i tried. My question is whether or not there is a way to know if the phone is in "enhanced lte mode" like we can in oreo?
[Nextbit Robin] naveed.hasan:
I'm having no such luck and LOS 16 on the Robin has basically turned the phone part of the device into a one way radio where I have to always call back anyone who tries to call me.

There are many places now where there is *only* LTE T-Mobile US network coverage, so leaving the device in 3G mobile data mode leaves it with no cellular voice or data connectivity.

Not ideal, to say the least. Are there still any active maintainers for ether? Thanks.
[Nextbit Robin] naveed.hasan:
Submitted GitLab bug to track this issue.
[Nextbit Robin] brendonla:
I'm on Mint Mobile which is a NVMO that uses T-Mobile's network on bands 4 and 12.

Is the autoswitching between LTE and 3G still an issue for this ROM? Would like to switch but not if basic calling is an issue.
[Nextbit Robin] naveed.hasan:
Not working yet, no updates on GitLab bug

Stay on Lineage OS 15.1 if you want to be able to receive calls on the T-Mobile US network while at the same time leaving LTE data enabled.
[Nextbit Robin] brendonla:
Thanks for the update!
[Nextbit Robin] freddd1:
[MENTION=5848265]npjohnson[/MENTION]

Is there a possibility of LineageOS 17.1 being made available for the Nextbit Robin?
[Nextbit Robin] Raiz:
Hi there, you can see the list of device currently supported by LOS 17.1 here.

And also the LOS Gerrit (17.1) with merged modification for the Robin. here.

With these 2 links you can follow the evolution of Linageos for the Robin.

I'll let this here so you updated at least on the device list.

Have a good one.

Edit #1:

I'm letting here so people don't keep asking every five minutes about how LOS 17.1 is doing.

But your question, if it is the only time you ask it, is legit (to me at least lol)
[Nextbit Robin] xWolf13:
Just adding to your response. That change was abandoned.
[Nextbit Robin] johnwazhere:
Camera

Camera crashes in latest nightly, seems to be a gcam thing
[Nextbit Robin] freddd1:
Working fine for me. I am not using Google Apps, it might be related to that.
[Nextbit Robin] johnwazhere:
Also can report on the latest pie build safetynet works out of the box surprisingly.
[Nextbit Robin] xWolf13:
Clean flashed and getting error 7? Anyone else?

Update: Fixed a while ago. Something weird with TWRP.

On another note, I've seen 17.1 has been ready and is waiting to be merged on Gerrit. Any update on this [MENTION=5848265]npjohnson[/MENTION]?
[Nextbit Robin] npjohnson:
Nope.

News will come when it's ready.