yashsingh1/xdaforums huggingface dataset:
[JAMin, XDA Neo, S200 ROM Development] Gherudos:
I use this guide:

But the SPL.lnk is not running either using total commander or the file explorer.What to do?
[JAMin, XDA Neo, S200 ROM Development] l3v5y:
Use "Prophet Tools", there is a link in my signature.

This will allow you to HardSPL. Then, you need to get a ROM. I'd recommend one of gullums Coffie ROMs, as they have multilanguage support. They may not be WM6.1, but as far as I know, there are no WM6.1 Greek ROMs ATM.
[JAMin, XDA Neo, S200 ROM Development] Gherudos:
I used your tool but after i press the hardspl the screen goes white and then nothing.Also it says error connection 204
[JAMin, XDA Neo, S200 ROM Development] varanusvincent:
deactivated your firewall too.
[JAMin, XDA Neo, S200 ROM Development] l3v5y:
The screen should go white, as the new SPL does that!
[JAMin, XDA Neo, S200 ROM Development] Gherudos:
i dont have a firewall
[JAMin, XDA Neo, S200 ROM Development] l3v5y:
Are you using Windows XP or Vista?
[JAMin, XDA Neo, S200 ROM Development] Gherudos:
I am using windows Xp,please someone contact me on msn so i can tell you exactly whats going on and maybe help me fix it.It goes to the white screen but then it disconnects for some reason.Please add me to your msn Gherudos@hotmail.com

thanks a lot
[JAMin, XDA Neo, S200 ROM Development] Gherudos:
I wish to publicaly say a thanks to l3v5y for all his great help.

Thanks a lot m8...
[JAMin, XDA Neo, S200 ROM Development] Quiddix:
Would be quite usefull if you would post your solution here.

I also want to hard SPL my prophet but if i run the prophet tools select G4 and HARD SPL my PDA goes into a white screen and after a short time there is an error on my pc.

So i think i have almost the Same error but my code says ERROR 208 (CANT OPEN FILE)...
[JAMin, XDA Neo, S200 ROM Development] Gherudos:
Yes i did have the same error.

Download this file and you will be ok:

http://rapidshare.com/files/112210743/HardSPL_G4.zip.html

If you need any more information i ll gladly help you.
[JAMin, XDA Neo, S200 ROM Development] l3v5y:
That probably means I have the wrong/non existant file in Prophet Tools...
[JAMin, XDA Neo, S200 ROM Development] Gherudos:
I had the same problem so he will be ok.
[JAMin, XDA Neo, S200 ROM Development] martin-m81:
I have the same Problem. I tried the "Prohpet Tools" and the "HardSpl" tool (seems to be the same?).

As soon as i'm asked if i want to let jumpspl.exe access my prophet (TC500) and i choose yes the screen is fading to white, the usb-connection is closed and my prophet is doing nothing.

I tried it a few times and also tried another usb-cable and another usb-Port but nothing helped. My os ist xp sp3, firewall and Anti-Virus are disabled.

I tried to download the mentioned file in this thread but it isn't available anymore.

Please help me, this is getting on my nerves.

Thank you
[JAMin, XDA Neo, S200 ROM Development] wapvirus:
Try lazy tools by Dioxda2 ;)
[Huawei Y6 Questions & Answers] Hozrael:
Hello, I'm looking for gcam for Huawei y7 prime 2018. I am new at stuff like this, and I didn't find anything about gcam for my phone, so I write here. I don't know is it needed but I didn't root my phone. I will be grateful for your help.
[Huawei Y6 Questions & Answers] Waydez97:
هاي
[Android Q&A, Help & Troubleshooting] xaxaexdee:
Hello friends,

I've been trying to install the latest version of TWRP using Odin on my S8+ but it overwrites the system and doesn't function as it should.

At first I thought it was just a normal bootloop until I managed to get into the TWRP menu and went to see the storage only to see that I had 0 storage used which I found odd.

Could someone help me out and tell me what I'm dealing with? I'd greatly appreciate it.
[Android Q&A, Help & Troubleshooting] TPBWorks:
Can you provide more details?

What seems not to be working as it should?

What do you mean by bootloop and 0 storage used?

Have you had TWRP installed before the new version?
[Samsung Galaxy Note 9 Questions & Answers] AndyLangers:
Hi

Upgraded to Pie last Friday on EE in the UK on a carrier device so its the EE Firmware.

Prior to the upgrade I have VoLTE on the status bar at the top and since then never shown its face again, anyone else had this?
[Samsung Galaxy Note 9 Questions & Answers] raul6:
How did it upgrade via OTA or via Odin and if latter what did you use?
[Samsung Galaxy Note 9 Questions & Answers] cheeb:
Updated in US and the hack to allow VoLTE (via shortcut master) no longer works. Hopefully a fix (or real update from certain carriers) will arrive soon...
[Samsung Galaxy Note 9 Questions & Answers] Deleted member 7436581:
Sounds like Pie isn't fully baked yet.

I'll see myself out.
[Samsung Galaxy Note 9 Questions & Answers] willhemmens:
I'm on EE and have been using Pie for quite a while at this point. VoLTE works fine for me.
[Fire TV General] Intenti0n:
In my latest upload we look at some of the new features of Kodi 18 and how they compare to the tried & tested Kodi 17.6. The ones demonstrated include:

UI Changes when installing addons

​

On Kodi 17.6, to install a new addons required you to go to System first (to add in the repo) then go back to the homescreen to install from zip file and the addon). In Kodi 18, the system screen now has a section for both File manager & Addons.

Gaming - Kodi 18 brings gaming to the forefront. You get access to a large library of emulators with associated control support. No need to install manual repos / emulators.

Dependency changes - On Kodi 17.6, you could try and install an Add-on but if it failed, it was not easy to see exactly why it failed. Was there a missing dependency? What didn't install etc. In Kodi 18, each addon as a dedicated section for dependencies so you can see exactly what dependencies the add-on needs and what are already installed.

DRM Support - You can now install the official Netflix (or any DRM supported add-on) and watch it directly in Kodi 18 in full HD.

PVR Client updates

Overall speed and UI tweaks.

You can see a video of the new features, including retro gameplay here
[Fire TV General] JUSTINMARMER:
Kodi is dead. Just let it go man.
[Fire TV General] Spillunke:
WTF xD

Why should it? Give us reasons or **** up.
[Fire TV General] JUSTINMARMER:
Are you attempting to speak English?
[Fire TV General] Spillunke:
Hm? So why is KODi dead?

Explain...
[Fire TV General] pr1uk1:
So come on please explain your comment ?

I know some time ago the papers were reporting that Kodi is dead i.e you cannot used the program to watch this and that, all proved wrong Kodi is alive and well.
[Fire TV General] JUSTINMARMER:
It's dead. Just let it die. It's over. Stop hanging on.
[Fire TV General] pr1uk1:
You do not give any reason why you think Kodi is dead it sounds like you read all the rubbish that was printed in the media months ago and believed it.
[Fire TV General] JUSTINMARMER:
Yeah, it's dead. Just let it rest in peace. It was good back then but it's dead now. It's over. Stop hanging on. It's dead.
[Fire TV General] SacredDeviL666:
Hello Everyone,

Just a friendly reminder to keep the discussion on topic and if you have nothing valuable to contribute you might as well refrain from posting for the sake of it:highfive:

Thanks

SacredDeviL666.
[Fire TV General] Intenti0n:
Sorry, but its far from dead.

Kodi is stronger than ever.

With Kodi 18, we get DRM support (Netflix etc), We get built in emulators, we get slicker interface so we know exactly what dependencies are needed for each add-on.

Anyone who says "Kodi is dead" , needs to wake up.
[Fire TV General] TimmyP:
Highly recommend the Netflix plugin now. Especially if you get CEC problems in Netflix app.
[Fire TV General] pr1uk1:
Well said :-0
[Fire TV General] JUSTINMARMER:
Or you know, it's dead.
[Fire TV General] pontiffholychurch:
This might be off topic slightly, but is a root available for the Toshia Amazon Fire TV Edition? thanks.
[Fire TV General] chrisftlse:
Haha troll you...

Princess Leia is dead... You are right since Dec. 2016.

But Kodi Leia revived it.

I am using it each single day and never and will never watch this StarWar b...... T
[Fire TV General] pandiur@gmail.com:
Kodi 18.1 Le
[Fire TV General] _3rik:
Kodi isnt dead per se, but stremio is definitely better for most people who just want to watch movies and tv series.

That being said, the emulator support in kodi 18 is really nice
[Fire TV General] khadem2020:
hi

Kodi 18 no star-x tv logo frez

Kodi 17 is good
[Fire TV General] TimmyP:
Bring out cha dead bring out cha dead
[Fire TV General] briangjohnson:
The current version of Kodi is Kodi 20 Nexus, the beta version. Probably, it will go live by March 2023. Most of the Kodi Builds and Addons are stable with the Kodi 19 version.

When Kodi 20 is fully launched then, we may face some technical glitches as what happened during the launch of the Kodi matrix. Some Kodi Builds and addons stopped working because Kodi developers upgraded the python version 2 to 3. The same kind of error should not happen this time. Let us hope that.
[Fire TV General] pr1uk1:
I have installed 19 and there are builds out there and addons now that work
[Fire TV General] pr1uk1:
Add

Ezzyman wizard

Index of /repo

then try the KODI build
[Fire TV General] mrposyble:
Kodi is not dead. I am still using kodi. For a list of kodi builds and addons, take your time to navigate through the aforementioned listing. I am sure you will find something you would love.
[Xiaomi Poco F1 Questions & Answers] Intelligent_figure:
My portrait mode was working fine in the latest build(6.1.021) flawlessly and it used to take multiple burst shots(one normal and other with lens blur). Since yesterday it keeps on taking only the sharper photo and not the blurred one even though it's in portrait mode. What could be the problem and how do I fix it? Please help.
[Google Pixel 2 XL Questions & Answers] Lambetts:
Hey guys,

Quick one, I haven't installed anything new and suddenly am having my Pixel just not going into deep sleep.

Left phone still on table, no deep sleep.

Installed GSam BBS and can't find alot wrong, as in an app that's smashing it. Only thing I can see is no deep sleep! Like, more drain when screens off then on! Wtf! I've tried everything but a reset. Rather not. Shouldn't have too. I'm not even rooted. I was months ago but went back to stock.

Screenshot included. Any ideas?

Thanks guys.
[Google Pixel 2 XL Questions & Answers] Lambetts:
Sorry, missed this screenshot... Couldn't work out how to edit and add.
[Google Pixel 2 XL Questions & Answers] EeZeEpEe:
When's the last time you've restarted your phone? If it's been since last monthly update, sometimes it's as simple as restarting to get it back to normal.
[Google Pixel 2 XL Questions & Answers] Lambetts:
You mean rebooting yeah? Like on and off? Not factory reset? Yeah, rebooted so many times now. Haha. Thanks though, I know what you mean.
[Google Pixel 2 XL Questions & Answers] EeZeEpEe:
Yeah definitely only talking about restarting, not resetting. How long has it not been able to do sleep? If anything, see if today's update gets it back to working.
[Google Pixel 2 XL Questions & Answers] Lambetts:
About a week or so. I just checked for updates, none unfortunately. This is really frustrating and confusing. Lol. Is just not able to deep doze at all.
[Google Pixel 2 XL Questions & Answers] EeZeEpEe:
The OTA isn't out yet but it should be later today.
[Google Pixel 2 XL Questions & Answers] Lambetts:
Argh I see. I'm in Australia don't know if that makes a difference lol.
[Google Pixel 2 XL Questions & Answers] EeZeEpEe:
Yeah I think it's the first Monday of the month sometime early afternoon but Eastern Standard time.
[Google Pixel 2 XL Questions & Answers] EeZeEpEe:
Available now.

https://www.androidpolice.com/2019/...e-februarys-images-are-available-to-download/
[Google Pixel 2 XL Questions & Answers] Lambetts:
Thanks mate.

Yeah, put it through this morning. Not sure yet. I'm not hopeful as phones been off charge for 2 hours and I'm at 88% already lol. We'll see though.

Thanks! ☺
[Google Pixel 2 XL Questions & Answers] Lambetts:
Hrmm, I know I might have to give it a few days but, make anything of this?
[Google Pixel 2 XL Questions & Answers] EeZeEpEe:
I don't use GSam BBS so don't know how much kernel usage I got. All I know is that over night it was from 100% to 97% in about 7.5 hours. So pretty sure it dozed in deep sleep fine for me.
[Google Pixel 2 XL Questions & Answers] Lambetts:
Stock?
[Google Pixel 2 XL Questions & Answers] EeZeEpEe:
Stock and not rooted.
[LineageOS Questions & Answers] achretien03:
I want you to answer me if it is possible
[LineageOS Questions & Answers] kurtn:
Why not search yourself?

https://xdaforums.com/lg-g5/development/unofficial-cyanogenmod-14-1-lg-g5-h850-t3494001
[Xiaomi Redmi Note 5 Pro Questions & Answers] Kumaravel Madhan:
I've MI TV, in that m using chromecast on my redmi note 5 pro, the audio was not working, the video only playing. i need to put the phone on silent for twice or thrice:confused::confused::confused:, then only audio starts playing. for each video or audio play, i've to do the same for each & every time video playing.

My redmi note 5 pro runs on MIUI 10.2.1.0

But i tried with nokia 6.1 plus, it works well :good::good::good:
[Xiaomi Redmi Note 5 Pro Questions & Answers] JZJ:
I just bought this phone and had the exact same problem, video playing through chromecast no volume.. Try this as the video is playing touch the chromecast button and the volume for chromecast should come up, just turn that up. I found using the volume button for the phone does not turn the volume up, you have to access chromecast and its volume control.
[Magisk] trol_sg:
Hello everybody.

I've read that 18.1 supports 4.2+ so I've tried to install in two MTK6589T devices I've. One running 4.2, the other running 4.4

CMW/TWRP gave an error mounting system, so I mounted system manually and it started flashing. Firstly it detected old root installed and disabled the old root. But when it tried to find the boot, installation was aborted because installator claims cannot find the boot on both phones.

Then I though, okay, lets reboot back to android, I will try to install a few days later, maybe its buggy now, but both phones cannot boot.

I can easily fix them by flashing rom again I guess, but I would like to know where's the issue and also post it for more people could face the same problem.

Any idea where's the problem/how to fix without rom reflashing? I've tried magisk uninstaller but after mounting system in recovery it is also giving error.

Thanks

UPDATE: For now, if no other solution is found, bootloop can be bypassed by dirty installing the rom again. But it has to be an easier workaround...

We know now that the problem is caused because of two factors merging:

1- Using Magisk.zip installer through custom recovery

2-In the case that the custom recovery CMW/TWRP installed in the phone is very old (for instance, CMW automade for MTK6589X or TWRP 2.5.0).

While installing, Magisk tries to send commands to the custom recovery that cant be understood by it, leaving the installation incomplete after some modifications in /system (read below recovery log).

Acording to the recovery, it seems that Magisk did some modifications without running correctly survival script - Adding addon.d survival script ("Unrecognized option '-Xnodex2oat'") and .zip installer is not designed to revert actions in this case.

Also, Magisk couldn't reach the boot modification step, so boot is not damaged, therefore workarounds for restoring boot won't work.

Using Magisk Unistaller.zip is also not possible as the uninstaller is mainly designed for boot backup restoration, and again, this is not the case.

Currently needed: Find what's wrong in system due to the incomplete Magisk installation to revert it back to the original state (before faulty magisk.zip installation).

Recovery log:

************************

* Magisk v18.1 Installer

************************

- Mounting /system, /vendor

- Target image: /dev/bootimg

- Device platform: arm

- Removing system installed root

- Constructing environment

- Adding addon.d survival script

Unrecognized option '-Xnodex2oat'
[Magisk] trol_sg:
up!
[Magisk] Ato09:
I' also having the same problem. My Samsung J2 Prime stuck at logo after updating to 18.1. Any tips on how to fix it without resetting my phone? Thanks.

Update: Bootloop fixed. I used TWRP to restore boot image. I then update Magisk by flashing zip file from TWRP. Everything went back to normal. Hope this help.
[Magisk] Ato09:
If you have a backup of your boot image, you can just restore it using TWRP. But in case that you have no backup of boot image, you can try to get boot image from the internet and restoring using it. In my case, this is what I did.

1. Go to TWRP and then make backup of boot image of the faulty phone*. (Folder 1)

2. I used another J2 prime to create a boot image backup. (Folder 2)

3. Once that is done, copy and replace the files inside the Folder 2 into Folder 1.

4. Reboot to TWRP again then use that to restore the boot image on my stuck J2.

Tips: make backup in SD card so you can easily swap it in between the bad and good phone.

*This is to create a folder of the backup file. I did tried to directly copy and paste the backup boot image file from another good phone but TWRP didn't detect it. So this is the workaround that I come with. And it worked for me.
[Magisk] trol_sg:
Thanks for your answer but I doubt your case is mine. Your device is much newer than mine and according to your comment, you've sucesfully installed previous version of Magisk without issues. This is not a problem while updating, as Magisk v. earlier than 18.1 was not compatible with android 4.2+. I think Magisk is not compatible with MT6589T even if they run 4.2 or 4.4.

I think that it cannot be a boot problem as TWRP/CWM displayed msg 'Boot cannot be found' while installing Magisk, so that I don't think boot was replaced or modified in any ways. Moreover, the bootloop is not in the boot loading, as phone can pass boot image without any problem, but it is stuck in android loading image. I'm thinking in some script or root modification that Magisk did before trying to unpack the boot, however I'm not that deep into the Magisk install to find the proper workaround.

I can restore boot backup and also I can take boot file from the original rom and flash, because in Mediatek-based devices, boot.img is inside de zip, but I dont think it will solve the problem. Anyhow I'll get back ASAP with the answer.

Any more ideas??
[Magisk] trol_sg:
Nothing, boot/uboot restoration or flashing again just the boot won't fix the problem, so it's something that Magisk installator touch in /system or /data I guess, but what?
[Magisk] Ato09:
Have you read/tried this?

didgeridoohan(dot)com/magisk/MagiskIssues
[Magisk] trol_sg:
Yes, I've read them before I made the post. I've also looked for a solution in some of the threads and using search, but couldn't find a way.
[Magisk] trol_sg:
Here I attach recovery.log if someone is interested to see the detailed problem.

Also, here below I attach the lines concerning the installation. All other is uninstallation tries and so on:

************************

* Magisk v18.1 Installer

************************

- Mounting /system, /vendor

- Target image: /dev/bootimg

- Device platform: arm

- Removing system installed root

- Constructing environment

- Adding addon.d survival script

Unrecognized option '-Xnodex2oat'

dalvikvm: [options] class [argument ...]

dalvikvm: [options] -jar file.jar [argument ...]

The following standard options are recognized:

-classpath classpath

-Dproperty=value

-verbose:tag ('gc', 'jni', or 'class')

-ea[:<package name>... |:<class name>]

-da[:<package name>... |:<class name>]

(-enableassertions, -disableassertions)

-esa

-dsa

(-enablesystemassertions, -disablesystemassertions)

-showversion

-help

The following extended options are recognized:

-Xrunjdwp:<options>

-Xbootclasspath:bootclasspath

-Xcheck:tag (e.g. 'jni')

-XmsN (min heap, must be multiple of 1K, >= 1MB)

-XmxN (max heap, must be multiple of 1K, >= 2MB)

-XssN (stack size, >= 1KB, <= 256KB)

-Xverify:{none,remote,all}

-Xrs

-Xint (extended to accept ':portable', ':fast' and ':jit')

These are unique to Dalvik:

-Xzygote

-Xdexopt:{none,verified,all,full}

-Xnoquithandler

-Xjniopts:{warnonly,forcecopy}

-Xjnitrace:substring (eg NativeClass or nativeMethod)

-Xstacktracefile:<filename>

-Xgc:[no]precise

-Xgc:[no]preverify

-Xgc:[no]postverify

-Xgc:[no]concurrent

-Xgc:[no]verifycardtable

-XX:+DisableExplicitGC

-X[no]genregmap

-Xverifyopt:[no]checkmon

-Xcheckdexsum

-Xincludeselectedop

-Xjitop:hexopvalue[-endvalue][,hexopvalue[-endvalue]]*

-Xincludeselectedmethod

-Xjitthreshold:decimalvalue

-Xjitcodecachesize:decimalvalueofkbytes

-Xjitblocking

-Xjitmethod:signature[,signature]* (eg Ljava/lang/String\;replace)

-Xjitclass:classname[,classname]*

-Xjitoffset:offset[,offset]

-Xjitconfig:filename

-Xjitcheckcg

-Xjitverbose

-Xjitprofile

-Xjitdisableopt

-Xjitsuspendpoll

Configured with: debugger profiler hprof jit(armv7-a-neon) smp show_exception=1

Failed to initialize runtime (check log for details)

- Unpacking boot image

MagiskBoot v18.1(18100) (by topjohnwu) - Boot Image Modification Tool

Parsing boot image: [/dev/bootimg]

No boot image magic found!

! Unable to unpack boot image

- Unmounting partitions

E:Error executing updater binary in zip '/sdcard/Magisk-v18.1.zip'

Error flashing zip '/sdcard/Magisk-v18.1.zip'
[Magisk] Didgeridoohan:
[MENTION=6103239]trol_sg[/MENTION] I'm gonna guess it's got to do with the absolutely ancient TWRP you're using. It just can't handle everything that the Magisk installation script is trying to do...

Your best bet (if Magisk will work at all on your device) is to patch the boot image with the Magisk Manager and then flash the patched image manually. There are new and shiny installation instructions available here: https://topjohnwu.github.io/Magisk/
[Magisk] trol_sg:
Thank you so much for your answer. So it's the recovery, but can't find newer ones, sadly. Too old phones I know, but just curious if I could make Magisk working on them, lol.

I was going into the boot modification manually right now, but in order to patch the boot I need manager installed first, and phone couldn't boot so I did dirty flash of the rom to be able to boot into it again.

Lets see what happens then. I'll be right back.

Anyhow, this is not a solution to fix the problem of bootloop that I am requesting help in case someone could face the same and did not make a backup of the phone and didn't want to make dirty re-flash. Any idea?

Update: After I did dirty flash of the rom, and now Jiayu g3s android 4.4 booted.
[Magisk] trol_sg:
UPDATE: So, after patching manually boot and installing (using restore in TWRP 2.5 as image flash is not yet implemented AFAIK), phone booted and yes Magisk is working.

Magisk installation .zip through a very old recovery is making the bootloop. So that, a thing learnt now.

But, for other people facing this bootloop, can we do a research to find what magisk.zip did to the phones to leave them in bootloop? Maybe we can revert without rom flashing easily if we knew what's the issue...

Thanks in advance!
[Magisk] trol_sg:
Doing a bit more tests I found that magisk.zip did something in /system so that it is left in bootloop, but still no idea why/whats causing that...
[Magisk] Beytullah61:
There are delay complete boot like 4 5 second in j7 prime. I didn't love this version
[Magisk] trol_sg:
any more help?? up!!