yashsingh1/xdaforums huggingface dataset:
[G4 General] BIG_BADASS:
All this trouble because no bootloader unlock... what a shame

---------- Post added at 10:27 AM ---------- Previous post was at 10:21 AM ----------

What is the difference between H and N versions?
[G4 General] sdembiske:
Will try and get to it sometime over the long weekend that we have coming up here and give it a shot as well as providing the DEBUG=1 log on a v10h .

Thanks again.
[G4 General] steadfasterX:
You may could ask the maintainer of :

https://xdaforums.com/g4/development/h815-freedom-rom-t3630056/post72866870

He made an installer for his ROM which let you select VoLTE so he may now what is needed to activate it. I know it's for the h815 but it should be similar..

.
[G4 General] sdembiske:
As suggested, here are the revert_root_injection logs (x2 - DEBUG =1 and DEBUG=0), plus the TWRP recovery log of system image restore of the 'n' version from 'h' internal.

Same problem with revert-root-injection when the DEBUG option was set to "0" to execute - i.e., soft brick ... lol.

And, perhaps not unexpected, the exFat formatted card was still not recognized but what did surprise me is that none of my settings, apps etc., were restored on the 'n' system image restore after.

Link to logs: https://gist.github.com/sdembis/89de74e401def3ed0e091c565a19e0e9

I then restored all (excluding system image) from my backup in external after the first restore attempt - it failed on the Data restore but everything was back to normal from what I could tell on the reboot.

PS: I pm'ed both you and ReeS86 the response from the rom author you suggested I contact re: the VoLTE install. He was very helpful and sounds like a good guy. Thanks for the suggestion. Much appreciated.

Best,

S.
[G4 General] steadfasterX:
Hm the following is not clear for me:

You have restored the system image of N to H as suggested. Ok. And then? Does it soft brick as well?

the recovery log shows the backup only.. But it wouldn't be helpful anyways or do you had an error while restoring?

Yes using the revert script on H was 99% sure that it soft bricks as well ;) that's why I said DEBUG=1 but it seems u like it so.. nvm ;)

Thx to the log It looks like the root method between H and N is not different btw..

.
[G4 General] sdembiske:
No, neither of the restores resulted in a soft brick. The first restore of the 'n' backed up system image (from internal) went fast with no issues but didn't have the apps and settings that I backed up - that is the TWRP log I attached in my last post. The 2nd restore (all except system image from external), done right after the first, failed on restoring Data but I was able to reboot from within TWRP and all settings and apps were back as they should have been.

Here is the link to that log: https://gist.github.com/sdembis/160047faa4b22717edf36658e5e42ea7

Any ideas as to why the reversion is failing and whether it might be able to be overcome?

Thanks again,

S.

.
[G4 General] steadfasterX:
The idea of restoring the system image (ONLY this!) from N to H :

this was a test to see if you have the VoLTE working afterwards - was VoLTE working?

.
[G4 General] sdembiske:
Sorry, I didn't check it because the other problem, namely exFAT was no longer recognized was still present. I'll re-check everything today.
[G4 General] sdembiske:
Thinking this through a little - as the rooted Roger's/Fido 'h' version does have VoLTE, I would expect it to have VoLTE when the 'n' version system image with VoLTE is restored over that 'h' version. I am going to try instead taking the 'n' version without VoLTE but recogning exFat that I've rooted and restore the system image from the pre-rooted 'n' version with VoLTE but not recognizing exFat, to see if VoLTE is present. If it is, I suspect that exFAT will still not be recognized as it was with the retored 'n' version over the 'h' version, I would only end up with the same problem I have now with the pre-rooted 'n' version - VoLTE with no exFAT recognition.

Or, did you mean restoring the rooted 'n' version system image without VoLTE over the rooted 'h' version with VoLTE and exFAT recognition?
[G4 General] ReeS86:
I was able to loop mount both the bell H812n and Rogers H812n rooted system images and run KDiff3 on both of the root directories. It seems there are a few config files here and there that reference VoLTE as well as the odd missing file between the two. I'm going to keep digging maybe I'll find something about ExFAT as well.

Edit: Looks like the rooted system image posted to the Canadian G4 thread is from Videotron in Quebec. Still don't see anything about ExFAT...
[G4 General] sdembiske:
I pm'd you a screen shot of the the related files on the pre-rooted 'n' version with VoLTE. steadfasterX has suggested copying those files and pushing them through to a rooted version of the stock 'n' version without Volte but with functional exFAT. I just checked the rooted version of the stock 'n' version and none of those same files were present or the build prop line that had a different value than the one that was from Kessaras work that I pm'd you earlier.

May be the best shot to get both VoLTE and exFAT support by copying those files from the 'n' version with VoLTE to the 'n' version that doesn't - then the exFAT solve may be irrelevant.

Addendum:

Videotron does not appear to offer VoLTE ... ? The Bell/Virgin version apparently has the VoLTE app/option but it is 'greyed-out' and while the carrier does offer VoLTE on selected phones, the LG G4 does not appear to be one of them but it may possibly be made operational with a few adjustments - may be worth checking out as well. The stock 'n' version that we were linked without VoLTE may in fact be Telus/Koodo or Videotron, for that matter..
[G4 General] BIG_BADASS:
Ah, so no more VoLTE??? You are doing the job of carriers now, by removing features??

---------- Post added at 05:16 AM ---------- Previous post was at 05:15 AM ----------

Why you cannot add to one with existing VoLTE???
[G4 General] steadfasterX:
hm yes it makes no sense this way... ok forget that copy image approach and go on with the copy of apps ;)

.
[G4 General] BIG_BADASS:
Ah, he has found way to get VoLTE on all the variants!

---------- Post added at 09:17 AM ---------- Previous post was at 09:15 AM ----------

What are you onto bro? You found how to get VoLTE on other carrier variants?
[G4 General] BIG_BADASS:
Someone has to confirm whether the H81210x versions are vulnerable to stagefright...

I'd do it... if I had the phone....
[G4 General] steadfasterX:
could u pls link both pre-rooted KDZ versions in the OP?

I want to check something and wanna be sure to have the correct one..

EDIT:

I have looked into the injection script again and understand now how it works under the hood:

the injection will:

1. moving app_process and app_process64 to files named xxxx_original and replace those by the su daemon instead. ok I now that already BUT I wondered when/how they get called then. moving those important files cannot be good right? It would prevent things from working so there has to be a way how they get executed. The answer is simple: the su daemon has strings in it with that exact xxxx_original filenames so even while it may be obvious I wanted to have a proof for it which I now have.

2. add a file /system/etc/install-recovery.sh . This file does not exists in a stock KDZ (checked h81210o) and is referenced in the su binary as well. this script just contains another way to start the su daemon.

So the app_process is the hook where the su daemon get started and then the su daemon itself will start app_process.

.
[G4 General] sdembiske:
Here you go ... sorry about the delay.

Link for rooted H81210n with exFAT (without VoLTE):

https://mega.nz/#F!EWwATSrS!go90j9Osn5ZtxdEmxo_idA

Link for rooted H81210n without exFAT (with VoLTE):

https://www.androidfilehost.com/?fid=24385658843825742

Thanks again - very much appreciated.

S.
[G4 General] steadfasterX:
great many thanks again.

so the next thing I investigated was supersu (and all its dependencies) itself.

Both images are using the exact same version of supersu which take out 1 approach I had..

but.. u see me confused again ;)

so u have a 10n version with exfat but no VoLTE

and another 10n with VoLTE but no exfat.

I always assumed that it was a H version where VoLTE was working.... :eek:

The both linked versions seems to be one from Rogers and the other one from Videotron correct?

My main question now is: do you use the same boot image for both system images??? Because my other approach was to use the same boot image where the exfat is working together with the system image where VoLTE is working.

Besides this I was re-reading the last posts and I found:

is exfat working in their images?

so any chance that you can link me that version as well? I think it would be easy to make it not greyed out but well maybe thats not enough but to find out I need the KDZ (I always prefer kdz but a system image would work as well)

.
[G4 General] sdembiske:
ReeS86 thought, I think, that the 'n' image without VoLTE was Videotron but I cannot confirm this - the only other possibility I thought was Telus/Koodo because of other members reporting that the Bell/Virgin image (version not confirmed by me but presumed 'o' from another member's post) had the VoLTE option but greyed-our or non-functional. The 'n' version with VoLTE was Rogers/Fido.

Here are the links for the Rogers/Fido 'h' versions that ReeS86 has confirmed have both exFAT and VoLTE support, posted by other members.

Stock: https://www.androidfilehost.com/?fid=24399994186367639

Pre-rooted: https://www.androidfilehost.com/?fid=24052804347824479

This is the link for what was posted by another member as a Bell/Virgin 'o' version that I presume (but have not confirmed myself) has the VoLTE greyed-out or non-functional. No confirmation available on whether exFAT is supported.

Pre-rooted (only): https://www.androidfilehost.com/?fid=24352994023702885

Thanks again.

S.
[G4 General] Usraek:
null
[G4 General] ReeS86:
The N version of the KDZ for the H812 is definately Videotron. I loop mounted the system images on a PC and they contained carrier specific items in the overlay folder (need to check if it was overlay for sure). I will play with it some more in the next week because I will be on vacation next 2 weeks. I'm thinking to take the N image from videotron (which is same as bell) that is not rooted and just merge in some Rogers specific items and flash back to device. If that works I will manually inject root and try exFAT again.
[G4 General] sdembiske:
Thanks.

I tried copying the VoLTE related items from the screenshot I pm'ed you before from the Rogers/Fido rooted version to the Videotron image that I injected root into. The end result was that I was getting two "Unfortunately 'call' has stopped" forced closes in a row on boot with the VoLTE related injections and couldn't overcome it. The VoLTE tab also wasn't listed in settings, so I suspect I didn't get all the VoLTE related files or some related network files that are different and required for proper implementation. Regular cell calls, however, didn't seem to be affected and the phone would operate normally in all other regards.

I hope you have better success and would be interested in what specific files that you end up transferring/copying over. Enjoy your vacation.
[G4 General] sdembiske:
Stumbling Block ... ?

cat /proc/filesystems command output: H81210n rooted system images without and with exFAT: [B

]See Attached Thumbnails

[/B], please.

and refer to: https://android.stackexchange.com/q...tted-external-sd-card-automatically-without-r

"exFAT support is kernel based. open terminal and run

cat /proc/filesystems

if in the subsequent listing you see

. exfat

your kernel supports exfat file system unless the build is skunky. if the in the listing you see

nodev exfat

then you don't have exfat support. In one instance i've seen, even though the kernel may have exfat support, the rom may not, or it's "broken" in some way. As to the formatting of the card, i believe it needs to be formatted exfat and unaligned. Else, it should mount like any other external card with one exception, the entry in your fstab (Editor: read vold) for the external card. If the entry for <type> is vfat, then you may have a problem. The entry should be auto or, if you know how to unpack and edit, then repack and flash your boot.img, you can specify exfat."
[G4 General] sdembiske:
exFAT related output from 'Mount' command output: H81210n with exFAT (without VoLTE)

/dev/block/vold/179:65 /mnt/media_rw/external_SD exfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=utf8,namecase=0,errors=remount-ro,discard,readahead_kb=512 0 0

/dev/block/vold/179:65 /mnt/secure/asec exfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=utf8,namecase=0,errors=remount-ro,discard,readahead_kb=512 0 0

NB: These lines are not in the 'Mount' command output from H81210n without exFAT (with VoLTE)
[G4 General] ReeS86:
[MENTION=6302635]sdembiske[/MENTION] - Ok so I finally got around to fiddling with this and I think I have something that I'm pretty happy with. Here's the steps I took to get where I'm currently at.

1. Made backups of apps using Titanium Backup, TWRP Backup, SMS Backup & Restore, etc.. (probably irrelevant for here)

2. Flash H81210h Rogers KDZ in Refurbish mode - wipe everything clean and start fresh.

3. Skipped any set-up other than the minimal required to get to home screen.

4. Boot into download mode and pull system image from H81210h clean flash.

5. Flash H81210n rooted Rogers system image directly over H81210h installation.

6. Finish set-up, restore apps, install TWRP in FIsH, create system backup. (Again, likely not relevant here).

7. My main 128GB SD card is formatted FAT32 so I unmount SD card and insert one with exFAT formatting (an old 4GB one I had laying around). Card not recognized, unreadable.

8. Loop mounted the H81210h system image I pulled and compared vs the H81210n rooted image that I flashed over system. Found that /lib/modules/exfatfs.ko is different between the two.

9. Copied the exfatfs.ko from the H81210h system image pulled earlier and replaced one currently on the phone.

10. Reboot and SD card is readable as exFAT.

So it looks like an incompatibility between the kernel and the modules has caused all this grief. I think I may try to actually replace all of the kernel modules as well - I'm not having any issues other than exFAT that I have notices but it's entirely possible that they are just not as noticeable (maybe less battery drain?).

If you want to give it a try I'd be curious to see if this is a fluke or something repeatable. If you're running your phone with H81210n with the original Videotron KDZ and the rooted Rogers system image you'd likely want to pull the kernel modules from the original Videotron KDZ instead of the Roges 10h image in my case. Let me know if you want me to dig up the modules and attach them, I have a pile of system images laying around from my testing.

Edit: Oh and I forgot to mention, overlaying the H81210n system image has resulted in a fully Rogers ROM that doesn't show any of the libstagefreight vulnerabilities. I can't confirm if VOLTE works but the option is there in call settings.

Cheers
[G4 General] steadfasterX:
Sorry that I was a little bit quiet the last weeks but you may have seen why :laugh:

yeah that is a really nice finding I thought this wouldn't work because the main reason why the modules are different is because they are built with the Kernel and so yes maybe something was compiled different or whatever but hey this is working you got it'

.
[G4 General] sdembiske:
Great find ReeS86 ! - excellent effort. I will pull the exfatfs.ko from the rooted H81210n Videotron system image and transfer to the Rogers image and report back.

Best,

S.

Addendum

:

Success !! I restored with TWRP-in-FiSH the rooted H81210n Videotron system image I had backed up on internal storage, put in the exFAT formatted SD card I had (also an old 4gb) and booted up. I then copied the /system/lib/modules/exfatfs.ko file in X-plore file manager to the SD card and transferred it to my android-sdk platform tools folder on my laptop, booted into TWRP-in-FiSH recovery restored the rooted H81210n Rogers/Fido system image I had backed up, powered off and reinserted my 32gb FAT32 SD card and re-booted into TWRP-in-FiSH recovery.

Using the following commands in TWRP-in-FiSH, I transferred the Videotron exfatfs.ko file over to the Rogers/Fido ROM:

adb push exfatfs.ko /system/lib/modules/

and then, still within TWRP-in-FiSH recovery, set the permission with the following commands:

adb shell

cd system/lib/modules

chmod 644 exfatfs.ko

Powered down, inserted the exfat formatted SD card, booted up and voilà, exFAT formatted SD card recognized! All else seems fine in the ROM, no changes anywhere else that I can ascertain as yet.

Thank you again, ReeS86 and steadfasterX (other members, please give them your Thanks if this proves to be helpful to you), for all your input and assistance in getting to this point. By far the easiest solution to get around the whole issue. Well done ReeS86 !!

Link for the H81210n exfatfs.ko file that was used to enable recognition of exFAT formatted SD card on the pre-rooted Rogers/Fido H81210n ROM. Note: The file, as it was taken from a rooted Videotron H81210n ROM, does not appear to be carrier dependent (at least as far as using it in a Rogers/Fido ROM, but not tested for other carriers) and may not be version dependent (i.e., may also work on, for example, an 'h' version - would appreciate any feedback if this is confirmed for use on other carrier versions). It will, however be kernel dependent, so it depends on whether your kernel supports exFAT in the first place. Both the Videotron and Rogers/Fido ROMS had the exact same kernel version (3.10.49) and we knew beforehand that the Videotron ROM did support exFAT.

H81210n exfatfs.ko file: https://www.androidfilehost.com/?fid=673368273298975915

H81210n rooted Rogers/Fido with exfat - rootedsystem.img: https://www.androidfilehost.com/?fid=817550096634790183
[General Questions and Answers] GWARslave119:
Not on all offers though, just ones where you fill out a form. I'm not able to click the dropdown menu arrrow...I've checked running processes and I don't see anything out of the ordinary. I'm using Android 6.0.1. If you need more info lemme know. I'm trying to record a video of it to show exactly what I'm talking about.
[General Questions and Answers] GWARslave119:
Ok I recorded on BlueStacks here: https://youtu.be/ipDItDdr9Dc

At the end though when I click the dropdown menu arrow, on my phone it doesn't restart the game, it just doiesn't do anything. This hapens with any type of offer where I have to fill out a form via the game app
[General Questions and Answers] Droidriven:
It should be opening in your default internet browser.

Are you using any kind of adblocker? It might be preventing it from loading.

I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
[Tilt, TyTN II, MDA Vario III General] nky:
Hi guys,

I seem to be having problems getting on any websites runing on my Tytn ii. The only ones that seem to work is the My3 Account page and Google. I'm able to browse using google's 'convert a page to work on a mobile' feature. but thats as far as it gets. I can't seem to access the My3 Today and Sevices page too.

Im currently using the following settings.

accesspoint = three.co.uk

and everything else blank

Thanks for you help!
[Tilt, TyTN II, MDA Vario III General] garratt:
Hi nky

It may be the data package you have on three. For PAYG there's an internet add on and a mobile broadband add on. I assumed the internet add on would probably be limited to simple wap surfing so I bought the mobile broadband add on. It works fine with the settings you said use used. I can browse to any site and also pick up pop3 email through outlook. The ither think to note is that wehen you roam onto one of their partner gsm networks (I do when I'm at home because 3's signal strength is really poor there) you can only access the my3 page. Also like you I've found you cannot view the today and services pages on the my3 site. I guess these are locked to only be usable on 3 branded devices with their client software pre-installed. I've decided I can live with that is it's really normal internet access I want not 3's 'toys'.

Ian
[Redmi Note 2 Q&A, Help & Troubleshooting] MrButcher:
Hi Guys,

my redmi note 2 suddenly stopped to work.

no fastboot or TWRP are avilable anymore.

I tried to use SP flash tool SP_Flash_Tool_v5.1628 to flash hermes_global_images_V8.1.2.0.img on my windows 10 machine.

Flashing always stops with: brom error s_ft_enable_dram_fail (4032)

As driver Mediatek USB Port is recognised.

Any other ideas to fix this issue and bring back my phone to life?

Thanks a lot for your strong support!!
[Redmi Note 2 Q&A, Help & Troubleshooting] MamasDanu:
Have you installed mt65xx vcom driver installation? Usually the error code (4032) is problematic with usb driver installation.
[Huawei Mate 9 Questions & Answers] Nickco43:
We have the source code now:

http://consumer.huawei.com/en/openso...e=10&curPage=1

Can someone please port Lineage OS to the Mate 9? I will buy them a coffee.
[Huawei Mate 9 Questions & Answers] ferry013:
beer!! from me
[Huawei Mate 9 Questions & Answers] 开羊啊:
me too.or can produce mokee
[Huawei Mate 9 Questions & Answers] Planet X:
Please, somebody can help us? We will need a reverse engineer for the drivers to port and somebody from Lineage crew.
[Huawei Mate 9 Questions & Answers] tusko5:
AFAIK, the problem with the published source code by Huawei is that the camera does not work.
[Huawei Mate 9 Questions & Answers] cr2:
Can you provide the technical details on the error messages ?

There is a LineageOS image for Honor8 (which has problems with random crashes) but the actual kernel interface differences between Honor8 and Mate9 are minimal.
[Huawei Mate 9 Questions & Answers] tusko5:
Sorry I don't know the details but there has been some discussion in this thread:

https://xdaforums.com/mate-9/help/kernel-source-code-t3556352
[Huawei Mate 9 Questions & Answers] ante0:
The camera itself works, it's when you take a picture that the image doesn't save.

I narrowed it down to a sqlite error when trying to save:

06-09 12:00:45.188 E/SQLiteDatabase(26762): android.database.sqlite.SQLiteConstraintException: UNIQUE constraint failed: gallery_media._data (Sqlite code 2067), (OS error - 2:No such file or directory)

I'm not sure how to fix that actually.

gallery_media._data seems to have a dot too many imo, but maybe it's supposed to be that way.

I never tried with another camera app, to check if it's just stock that doesn't work.

Edit: This can apparently mean 2 things, either the db is not read/write or the ID (gallery_media._data) already exists.

Edit 2: Actually, this error no longer exists on B185.

Google Camera works fine. It's just Huawei's camera app that doesn't work correctly.
[Huawei Mate 9 Questions & Answers] tusko5:
Then, if the kernel works, what are the general steps to start working on a Mate 9 Lineage port?

If the kernel interface is similar to that of Honor 8, shouldn't the Honor 8 Lineage sources be the base for a Mate 9 port?
[Huawei Mate 9 Questions & Answers] ante0:
Apparently the unofficial lineage for Honor 8 uses stock honor 8 kernel.

I'm syncing now, might take a while.

Hopefully we just need to edit the Honor 8 sources for Mate 9.
[Huawei Mate 9 Questions & Answers] Nickco43:
I hope so!
[Huawei Mate 9 Questions & Answers] Nickco43:
It seems like we need some serious talent to get a proper rom ported.
[Huawei Mate 9 Questions & Answers] thenellt:
I started messing around with building the kernel but, given my lack of experience, I wouldn't expect much.
[Huawei Mate 9 Questions & Answers] albertobom:
Any progress on this my friend? [MENTION=2247733]ante0[/MENTION]
[Huawei Mate 9 Questions & Answers] ante0:
I gave up, but might start again soon.