No matter what TWRP version I use as my recovery, OOS loses all the emojis. I want to stay stock and rooted. I achieved root via magisk, but the OS is impossible to use without graphical symbols with square boxes instead of them. Please help me. I'm on oos 10.3.3
bythelaw said:
No matter what TWRP version I use as my recovery, OOS loses all the emojis. I want to stay stock and rooted. I achieved root via magisk, but the OS is impossible to use without graphical symbols with square boxes instead of them. Please help me. I'm on oos 10.3.3
Click to expand...
Click to collapse
So what's basically happening is that you somehow like many others don't have the Reserve partition which includes Emojis, Fonts and some OnePlus Apps.
There are a couple of things that you can try to fix it.
You can try to install OOS through local upgrade without wiping anything. This may work or not. From my experience it never worked but for some it did so it's worth to give a try.
If the first method doesn't work you can give this Magisk module a try, it contains everything that's included in the Reserve partition. Just install it via Magisk and reboot.
https://androidfilehost.com/?fid=1899786940962618515
For both methods you may need to wipe the app data and cache of your keyboard app for the emoji's to reappear.
If both methods don't work for you, you probably need to do a complete reinstall of OOS. You could try to clean flash OOS via TWRP or restore your device with the MSM Download Tool.
Good luck! :good:
Mr.FREE_Bird said:
So what's basically happening is that you somehow like many others don't have the Reserve partition which includes Emojis, Fonts and some OnePlus Apps.
There are a couple of things that you can try to fix it.
You can try to install OOS through local upgrade without wiping anything. This may work or not. From my experience it never worked but for some it did so it's worth to give a try.
If the first method doesn't work you can give this Magisk module a try, it contains everything that's included in the Reserve partition. Just install it via Magisk and reboot.
https://androidfilehost.com/?fid=1899786940962618515
For both methods you may need to wipe the app data and cache of your keyboard app for the emoji's to reappear.
If both methods don't work for you, you probably need to do a complete reinstall of OOS. You could try to clean flash OOS via TWRP or restore your device with the MSM Download Tool.
Good luck! :good:
Click to expand...
Click to collapse
I tried the first method, didn't work. I'll try the second method and reply here.
After installing "Reserve_V1" via magisk, do I have to data-reset via twrp? Wipe internal storage? Or anything else?
Or
Just reboot after flashing the zip, and hopefully emojies are back?
bythelaw said:
I tried the first method, didn't work. I'll try the second method and reply here.
After installing "Reserve_V1" via magisk, do I have to data-reset via twrp? Wipe internal storage? Or anything else?
Or
Just reboot after flashing the zip, and hopefully emojies are back?
Click to expand...
Click to collapse
Doesn't surprise me, never worked for me too...
No wipes needed, just install the Magisk module via Magisk and reboot. You may need to wipe the app data and cache of the keyboard app you are using like I mentioned but that's it.
Mr.FREE_Bird said:
Doesn't surprise me, never worked for me too...
No wipes needed, just install the Magisk module via Magisk and reboot. You may need to wipe the app data and cache of the keyboard app you are using like I mentioned but that's it.
Click to expand...
Click to collapse
Awesome, thank you so much. I'll try it and reply
Mr.FREE_Bird said:
Doesn't surprise me, never worked for me too...
No wipes needed, just install the Magisk module via Magisk and reboot. You may need to wipe the app data and cache of the keyboard app you are using like I mentioned but that's it.
Click to expand...
Click to collapse
It seems I didn't pay attention before, but now I see that after twrp and root, my internal storage is not working properly. No apps are installing, can't download anything either.
Mr.FREE_Bird said:
Doesn't surprise me, never worked for me too...
No wipes needed, just install the Magisk module via Magisk and reboot. You may need to wipe the app data and cache of the keyboard app you are using like I mentioned but that's it.
Click to expand...
Click to collapse
Reserve magisk worked wonderfully.
Thank you so much. Hopefully others can find this thread as well and root.
Im planning to root my op6, how do i not mess up the reserve partition??
bythelaw said:
Reserve magisk worked wonderfully.
Thank you so much. Hopefully others can find this thread as well and root.
Click to expand...
Click to collapse
Great to hear, glad that the Magisk module I shared was helpful. :good:
---------- Post added at 11:08 PM ---------- Previous post was at 11:06 PM ----------
Antieco said:
Im planning to root my op6, how do i not mess up the reserve partition??
Click to expand...
Click to collapse
I'm actually not quite sure what causes the reserve partition to go missing. But from my own experience it seems that wiping the /data partition after a clean install of OOS with he MSM Download Tool causes this to happen. But I am not 100% sure this is correct.
The Reserve zip file worked very well. Thanks to the zip creator and guy refering to the zip file.
Now with everything fixed I wanted to use the font changer magisk module which I couldn't due to the above module blocking/overwriting it.
Reserve file containing all the fonts and emojis in system/fonts folder. Surprisingly almost all the files were already present in the phones system folder but containing 0kb data, which was the problem.
Extracted the Reserve zip file, copied files from system/fonts and replaced them in the phones system/fonts folder via file manager. Rebooted and everything was working. Now all the fonts and emojis are working as well as I'm able to change fonts using font changer module. Hope this helps
Mr.Hunk said:
The Reserve zip file worked very well. Thanks to the zip creator and guy refering to the zip file.
Now with everything fixed I wanted to use the font changer magisk module which I couldn't due to the above module blocking/overwriting it.
Reserve file containing all the fonts and emojis in system/fonts folder. Surprisingly almost all the files were already present in the phones system folder but containing 0kb data, which was the problem.
Extracted the Reserve zip file, copied files from system/fonts and replaced them in the phones system/fonts folder via file manager. Rebooted and everything was working. Now all the fonts and emojis are working as well as I'm able to change fonts using font changer module. Hope this helps
Click to expand...
Click to collapse
Absolutely not a problem! Glad it was somewhat helpful.
Great solution and tip for others who might run into the same issue. I'm sure that will be helpful for others who might run into this thread. :good:
Related
how to copy TWRP nandroid backup to device?
I need to restore and I don't know how to copy from my hdd to the phone.
The phone is not booting but I can get to twrp recovery.
Latest TWRP has MTP mode.
but it doesn't allow me to copy one of the backup files which is: data.ext4.win000 and it's 1.5GB
You'll need to give us more information.
Why did it fail? Why did your phone stop booting?
1. flashed bigxie_hammerhead_LRX21O-signed.zip
2. flashed CF-Auto-Root-hammerhead-hammerhead-nexus5
3. booted fine but still had apps like Ti backup & TWRP not working due to root permissions
4. Went to recovery and performed Fix permission.
5. stuck in boot loop
gil80 said:
but it doesn't allow me to copy one of the backup files which is: data.ext4.win000 and it's 1.5GB
Click to expand...
Click to collapse
I have had the same problem with my motox 14 the way I found around it was to copy the file to a different fold and use twrp file explore to move it to the back up folder. That has worked for me and a few others try it out it will work.
how can you copy using twrp while in recovery? are you able to access your PC from recovery?
gil80 said:
1. flashed bigxie_hammerhead_LRX21O-signed.zip
2. flashed CF-Auto-Root-hammerhead-hammerhead-nexus5
3. booted fine but still had apps like Ti backup & TWRP not working due to root permissions
4. Went to recovery and performed Fix permission.
5. stuck in boot loop
Click to expand...
Click to collapse
You'll need to factory reset then reflash the ROM
Fix permissions was not required here. You need titanium beta from his twitter feed.
ok i got the phone working and lost my data but I have it backed on PC.
I just see that 10GB is used but when I browse the phone using file explorer, the device is empty.... what??
Is it a known issue?
when the phone is connected to PC I see that 10GB is used but when I i browse the device it shows as empty
No. Do a full flash of userdata.img
Please explain
What would I achieve by flashing it?
gil80 said:
Please explain
What would I achieve by flashing it?
Click to expand...
Click to collapse
A fix for your problem. I shouldn't really need to explain that.
Thanks!
I got it working now. Only need to figure out why it shows 16GB instead of 32 and why root permissions are not working
gil80 said:
Thanks!
I got it working now. Only need to figure out why it shows 16GB instead of 32 and why root permissions are not working
Click to expand...
Click to collapse
Well the answer in the 100 other threads about space say that you must wipe data and cache.
Root should be fine, but as already mentioned, not with official titanium release.
I already did a wipe data and cache. So I don't understand why I still get this but I'll try again.
The Ti Backup link in the twitter feed is no longer valid, but for example, ES file explorer and clean master and also TWRP app are not performing as if they are rooted.
I'll try to re-install CF-Auto-Root-hammerhead-hammerhead-nexus5
gil80 said:
I already did a wipe data and cache. So I don't understand why I still get this but I'll try again.
The Ti Backup link in the twitter feed is no longer valid, but for example, ES file explorer and clean master and also TWRP app are not performing as if they are rooted.
I'll try to re-install CF-Auto-Root-hammerhead-hammerhead-nexus5
Click to expand...
Click to collapse
ES doesn't work properly, correct. Not all apps have been updated to work with L yet either.
L is much more secure than KK. There are ways to root.
1) chain fire - makes small change in RAMdisk that allows sudaemon to work at boot
2)flash a permissive kernel - this lowers protection within selinux.
More apps work with the 2nd method, but still not all.
New titanium coming to play soon.
https://twitter.com/titaniumbackup
This is a guide to partition your ares 8, could be used on other intel tablets, you would need your own files though.
Anyway download https://www.androidfilehost.com/?fid=24438995911969251 extract to your computer, you need to have adb and fastboot set up and running on your computer.
Inside ares8_resize_partions.zip you will find several files, if linux user you will use fastboot.sh windows user you will use fastboot_cmd.bat.
Set permissions on files as needed, commands can be typed via hand if you choose not to run script, simply copy and paste in terminal window.
First use twrp to make a backup, back up data, system, boot.
once done boot into bootloader, open terminal window use either fastboot.sh, fastboot_cmd.bat or copy and paste commands in terminal. Note in Linux I simple drag and drop fastboot.sh into open terminal window, should be able to do same for windows with fastboot_cmd.bat.
Once partition is done, you are still in bootloader select to reboot to recovery, from there restore your backup and reboot.
I have made a smaller version of i708q rom I call BatVille, also made another partition.tbl just for BatVille rom
BatVille is just a smaller versions of I708Q rom, I added BatMan live wallpaper, It uses Nova Launcher, I removed a lot of stuff from i708q rom, to get BatVille rom small and still working as it should.
You can install BatVille without partitioning if you like, if you want to partition then install, that is the method I use.
To install partition just like above but use BatVille's partition.tbl instead of one above, when you are done partitioning reboot into recovery instead of restoring backup flash BatVille.zip and then flash SuperUser zip to get root, then reboot setup as normal.
Make sure to download and place BatVille.zip on external micro sdcard, internal sdcard will be formatted.
Download BatVille
https://www.androidfilehost.com/?fid=24438995911970819
Download BatVille partition.tbl
https://www.androidfilehost.com/?fid=24438995911970829
extract and rename batpartition.tbl to partition.tbl, replace the partition.tbl in ares8_resize_partions with this one before use.
Download SuperSU-v2.46.zip
https://download.chainfire.eu/696/SuperSU/
Place both BatVille.zip and UPDATE-SuperSU-v2.46.zip on micro sdcard.
reboot to recovery
factory Reset
select install zip
BatVille.zip
Add more Zips
UPDATE-SuperSU-v2.46.zip
reboot
Takes time before rom boots first time allow ten minutes or so.
I want to add more to /data than you added, and you said to edit partition.tbl if we want to change the sizes. Can you help me with editing it?
Startrek852 said:
I want to add more to /data than you added, and you said to edit partition.tbl if we want to change the sizes. Can you help me with editing it?
Click to expand...
Click to collapse
No, I have enough work to do myself, lf you look at stock and my modified one, you will see where I pulled from, cache and system then added the difference to data.
Added small rom BatVille and uploaded another partition.tbl just for BatVille rom.
Installed BatVille with the new partition table & it works great. Very small footprint and bloat is gone. I attempted a Titanium Backup, but the ext SD card isn't writable in Lollipop, so I resorted to backing up on internal memory and manually copying it to extSD. Although I was able to copy the backup and subsequently was able to copy it back to the Titanium folder on the internal memory after BatVille was installed, TB still refuses to see the files.
This is not a complaint, only a heads-up. Google had already restored all my market apps, and I only had 3 non-market apps installed (F-Droid and 2 Amazon market apps).
zerozed99 said:
Installed BatVille with the new partition table & it works great. Very small footprint and bloat is gone. I attempted a Titanium Backup, but the ext SD card isn't writable in Lollipop, so I resorted to backing up on internal memory and manually copying it to extSD. Although I was able to copy the backup and subsequently was able to copy it back to the Titanium folder on the internal memory after BatVille was installed, TB still refuses to see the files.
This is not a complaint, only a heads-up. Google had already restored all my market apps, and I only had 3 non-market apps installed (F-Droid and 2 Amazon market apps).
Click to expand...
Click to collapse
There is an app on playstore called NextApp SDFIX, that will change permissions on platform.xml to allow writing to external sdcard, so you can backup directly to external sdcard.
I just tested it, and it works, platform.xml needs to be edited, the above app will do that, then just reboot.
Sent from my i708Q using Tapatalk
I tried to install the BatVille rom, coming from the i708 rom you posted the other day, I used the new TWRP, but the tablet gets hung u on the i708 screen. I have "dirty flashed" it, installed from a factory reset, and tried after wiping tablet completely, nothing worked. The i708 rom is much improved over the stock rom, thank you greatly for it
vampirefo said:
This is a guide to partition your ares 8, could be used on other intel tablets, you would need your own files though.
Anyway download https://www.androidfilehost.com/?fid=24438995911969251 extract to your computer, you need to have adb and fastboot set up and running on your computer.
Inside ares8_resize_partions.zip you will find several files, if linux user you will use fastboot.sh windows user you will use fastboot_cmd.bat.
Set permissions on files as needed, commands can be typed via hand if you choose not to run script, simply copy and paste in terminal window.
First use twrp to make a backup, back up data, system, boot.
once done boot into bootloader, open terminal window use either fastboot.sh, fastboot_cmd.bat or copy and paste commands in terminal. Note in Linux I simple drag and drop fastboot.sh into open terminal window, should be able to do same for windows with fastboot_cmd.bat.
Once partition is done, you are still in bootloader select to reboot to recovery, from there restore your backup and reboot.
I have made a smaller version of i708q rom I call BatVille, also made another partition.tbl just for BatVille rom
BatVille is just a smaller versions of I708Q rom, I added BatMan live wallpaper, It uses Nova Launcher, I removed a lot of stuff from i708q rom, to get BatVille rom small and still working as it should.
You can install BatVille without partitioning if you like, if you want to partition then install, that is the method I use.
To install partition just like above but use BatVille's partition.tbl instead of one above, when you are done partitioning reboot into recovery instead of restoring backup flash BatVille.zip and then flash SuperUser zip to get root, then reboot setup as normal.
Make sure to download and place BatVille.zip on external micro sdcard, internal sdcard will be formatted.
Download BatVille
https://www.androidfilehost.com/?fid=24438995911970819
Download BatVille partition.tbl
https://www.androidfilehost.com/?fid=24438995911970829
extract and rename batpartition.tbl to partition.tbl, replace the partition.tbl in ares8_resize_partions with this one before use.
Click to expand...
Click to collapse
thew-tab said:
I tried to install the BatVille rom, coming from the i708 rom you posted the other day, I used the new TWRP, but the tablet gets hung u on the i708 screen. I have "dirty flashed" it, installed from a factory reset, and tried after wiping tablet completely, nothing worked. The i708 rom is much improved over the stock rom, thank you greatly for it
Click to expand...
Click to collapse
No ideal, you are flashing both BatVille and SuperSu before first boot?
https://download.chainfire.eu/696/SuperSU/
I factory reset.
Place both BatVille.zip and UPDATE-SuperSU-v2.46.zip on micro sdcard.
reboot to recovery
select install zip
BatVille.zip
Add more Zips
UPDATE-SuperSU-v2.46.zip
reboot
Not sure what I did wrong the first time, but it works great now. On a side note, your original i708Q rom for the ares 8 paritally works for the ares 11, the touchscreen doesnt work, but I downloaded a force rotation program from the playstore, the keyboard and mouse works perfectly well, even without the touch screen, it still runs better than the stock rom, thanks @vampirefo .
vampirefo said:
No ideal, you are flashing both BatVille and SuperSu before first boot?
https://download.chainfire.eu/696/SuperSU/
I factory reset.
Place both BatVille.zip and UPDATE-SuperSU-v2.46.zip on micro sdcard.
reboot to recovery
select install zip
BatVille.zip
Add more Zips
UPDATE-SuperSU-v2.46.zip
reboot
Click to expand...
Click to collapse
thew-tab said:
Not sure what I did wrong the first time, but it works great now. On a side note, your original i708Q rom for the ares 8 paritally works for the ares 11, the touchscreen doesnt work, but I downloaded a force rotation program from the playstore, the keyboard and mouse works perfectly well, even without the touch screen, it still runs better than the stock rom, thanks @vampirefo .
Click to expand...
Click to collapse
Upload your stock Ares 11 boot.img, I will swap out kernel, that should get touch working on Ares 11.
Sent from my BatDroid using Tapatalk
How do I upload?
vampirefo said:
Upload your stock Ares 11 boot.img, I will swap out kernel, that should get touch working on Ares 11.
Sent from my BatDroid using Tapatalk
Click to expand...
Click to collapse
thew-tab said:
How do I upload?
Click to expand...
Click to collapse
From you computer upload somewhere, mega, Google drive, Dropbox post download link.
OK, I think I may have done it right.l
vampirefo said:
From you computer upload somewhere, mega, Google drive, Dropbox post download link.
Click to expand...
Click to collapse
---------- Post added at 06:29 PM ---------- Previous post was at 06:25 PM ----------
https://drive.google.com/file/d/0B3dNJ0qSsln8ZV9aenVjbEpRWlk/view?usp=sharing
thew-tab said:
OK, I think I may have done it right.l
Click to expand...
Click to collapse
thew-tab said:
OK, I think I may have done it right.l
---------- Post added at 06:29 PM ---------- Previous post was at 06:25 PM ----------
https://drive.google.com/file/d/0B3dNJ0qSsln8ZV9aenVjbEpRWlk/view?usp=sharing
Click to expand...
Click to collapse
Try this boot.img
https://www.androidfilehost.com/?fid=24438995911973502
You uploaded Ares 8 boot.img
It's worked out, got boot.img from
http://forum.xda-developers.com/showpost.php?p=61314915&postcount=28
trying your link now, thanks. The second link was dead, but I had that img, so if anyone needs it here it is
https://drive.google.com/file/d/0B3dNJ0qSsln8YlFHZHQxR3lrQkk/view?usp=sharing
vampirefo said:
You uploaded Ares 8 boot.img
It's worked out, got boot.img from
http://forum.xda-developers.com/showpost.php?p=61314915&postcount=28
Click to expand...
Click to collapse
thew-tab said:
trying your link now, thanks. The second link was dead, but I had that img, so if anyone needs it here it is
https://drive.google.com/file/d/0B3dNJ0qSsln8YlFHZHQxR3lrQkk/view?usp=sharing
Click to expand...
Click to collapse
Touch working on Ares 11?
Thanks, vampirefo, touch screen seems to work perfectly. Much appreciated. Except for the forced rotation program, ( which doesn't bother me in the slightest) it seems like the ares 11 is now on android 5.1.1 as well!
vampirefo said:
Try this boot.img
https://www.androidfilehost.com/?fid=24438995911973502
Click to expand...
Click to collapse
---------- Post added at 10:59 PM ---------- Previous post was at 10:56 PM ----------
I have been testing the touchscreen more, touch seems to be right on
thew-tab said:
Thanks, vampirefo, touch screen seems to work perfectly. Much appreciated. Except for the forced rotation program, ( which doesn't bother me in the slightest) it seems like the ares 11 is now on android 5.1.1 as well!
Click to expand...
Click to collapse
thew-tab said:
Thanks, vampirefo, touch screen seems to work perfectly. Much appreciated. Except for the forced rotation program,
Click to expand...
Click to collapse
Try disabling the HW overlays in Developer options. That fixed rotation issues on the Ares 8.
I disabled the HW overlays, that took away the need for the forced rotation app, but once I enabled auto rotate thru the accessibility tab, the screen, inverted, stayed upside down when I went into portrait mode. I held the table upside down, then disabled the auto rotation so that when I docked it to the keyboard, the screen was right side up. The rotation, for me isn;t an issue, since I rarely take the tablet off the keyboard. Touchscreen still works, I am much happier with this "version" of the tablet, than stock, even after I had Xposed and the memory leak fix installed. now is is much smoother and faster.
freddy999 said:
Try disabling the HW overlays in Developer options. That fixed rotation issues on the Ares 8.
Click to expand...
Click to collapse
with little to no activity lately for the LGV20, specifically the H918 T-Mobile variant I decided to look into creating a TWRP flashable package for the recent H91810k release. these zips flash every partition included in the latest KDZ package with the exception of recovery to keep TWRP. standard disclaimer applies, you do all of this at YOUR OWN risk! I've tested this on my device after backing up and so far so good on the latest 10k release. please report back in this thread on whether it was successful or not.
NOTE: you can find the partitions that will be flashed in the updater-script. to be extra cautious you can back up all of the partitions that will be overwritten with the following: dd if=/dev/block/bootdevice/by-name/{partition} of=/external_sd/backup/{partition}.img.
Instructions:
download H91810k.zip file listed below and put on microSD card
backup any data from internal "SD card"
boot into TWRP (requires TWRP recovery to already be installed)
create a TWRP backup of the device
flash zip from microSD card by using "Install"
flash your choice of root, either Magisk or SuperSU *Note: v12.0 of Magisk does not work with the LGV20 device in general and v11.6 is recommended.
reboot
profit!
Download:
H91810k
md5sum: ab181ec82315b656a7af48f0017f4e8c - version 1 with misc partition included (SORRY)
md5sum: 8ad07ae70c4299b3ea6e2bf747dbec1c - version 2 with misc partition removed
Flashing Process:
flash necessary partition images with the exception of recovery (to keep TWRP) from the KDZ
rename /system/recovery-from-boot.p to /system/recovery-from-boot.bak to prevent stock recovery from being installed on boot
wipes dalvik-cache and cache
BIG thanks to @McNutnut on guidance, as well as his script to put all of this together!
also thanks to @bullghost for the KDZ extractor (https://forum.xda-developers.com/showthread.php?t=2600575)
@Tilde88 for the original updater-script template w/root (https://forum.xda-developers.com/v20/development/us996-nrd90m-modded-notsostock-rom-v5-1-t3526542)
First! This is sweet!
I just tried this and it works great. I prefer to use the stock rom and to get a rooted 10k that doesn't have any known security vulnerabilities is awesome. Some notes for others:
Copy SuperSU to the external SD card and flash it after this zip in TWRP.
Make sure to select all the partitions for back up in TWRP.
On the first boot after flashing, the phone will reboot by itself. This is probably normal. You will get an "Android is upgrading..." white screen. This is expected since the cache was wiped by the script. This will take a while to complete. Even when you get back into the system, an "Android is upgrading..." message will appear in the notification bar.
Clarification: The data on /sdcard doesn't get wiped, but it's a good idea to back it up just in case. The TWRP backup of the data partition does NOT include this stuff in the backup.
I had Busybox installed before, but I didn't have to reinstall it after the flash. I'm not sure why. I assumed that wiping out system would have required me to re-install Busybox. I guess Busybox doesn't get installed on the system partition?
Adblocking using apps like AdAway need to be rerun since the hosts.txt file will be reset.
Ignore the stuff under "Process" in the OP. It's explaining what the script does. You don't have to do any of that.
The script disables the updater software. You never have to worry about the next stock release causing you trouble!
I am having problems downloading this? I tried twice and it downloads but I cant find it?
Sent from my LG-H918 using XDA-Developers Legacy app
Big thanks for this! Have been patiently waiting for a 10k stock rom with firmware!
Sent from my LG-H901 using Tapatalk
what the hell man! I lost my twrp!!!! Now I only see stock recovery! DONT INSTALL THIS ROM!!!!
Hsinghr said:
what the hell man! I lost my twrp!!!! Now I only see stock recovery! DONT INSTALL THIS ROM!!!!
Click to expand...
Click to collapse
pretty sure if that's the case then YOU did something wrong... the recovery image is NOT in this package at all so TWRP is left untouched.
jason504 said:
I am having problems downloading this? I tried twice and it downloads but I cant find it?
Sent from my LG-H918 using XDA-Developers Legacy app
Click to expand...
Click to collapse
what are you using to download?
I HAD TWRP and and after a while it went back to stock recovery
You did something other than flash the rom in this thread. Maybe you're confusing this thread with this one? https://forum.xda-developers.com/v20/how-to/t-mobile-lgv20-h91810k-kdz-t3618021
If that's what you flashed, you will definitely end up with stock recovery and no root.
I've tried to install this ROM but it skips through each of partition rather quickly and it never installs. I'm on H91810j with root and TWRP installed. Any ideas? Thanks.
ctalbot said:
I've tried to install this ROM but it skips through each of partition rather quickly and it never installs. I'm on H91810j with root and TWRP installed. Any ideas? Thanks.
Click to expand...
Click to collapse
Did you have an external MicroSD card installed in your phone? Are you using that external MicroSD card to store the files to be flashed? What version of TWRP are you using?
Yep, on microsd. TWRP 3.0.2-1
OP says 10k, but you're on 10j?
Correct, currently on 10j
ctalbot said:
I've tried to install this ROM but it skips through each of partition rather quickly and it never installs. I'm on H91810j with root and TWRP installed. Any ideas? Thanks.
Click to expand...
Click to collapse
I would verify the md5sum of the downloaded file you have to what it should be, which is ab181ec82315b656a7af48f0017f4e8c
dimm0k said:
what are you using to download?
Click to expand...
Click to collapse
I got it I had to download it on my PC then send it to my phone. I flashed it and everything went fine thanks. I don't know why I was having problems downloading on my phone.
Sent from my LG-H918 using XDA-Developers Legacy app
-edit- bad cuestion, sorry
dimm0k said:
I would verify the md5sum of the downloaded file you have to what it should be, which is ab181ec82315b656a7af48f0017f4e8c
Click to expand...
Click to collapse
Hmm...the zip I downloaded has a checksum of 76bbccc0c9640d7f0005b529abf3873a and it uncompresses without issue!? Was there an earlier release?
Going to download again...
Hsinghr said:
I HAD TWRP and and after a while it went back to stock recovery
Click to expand...
Click to collapse
Can you provide more detail on what you did? You made a pretty strong statement that you lost TWRP.
Did you follow and flash what was written by the OP? Did you do flash something else after flashing what was provided by the OP? Or did you really have TWRP the whole time?
Not looking to cause an an argument but your 2 posts in this thread have made me hesitate flashing.
Sent from my LG-H918 using Tapatalk
So I found this many many months ago on 950U root and Xposed not being completely compatible with our s8,Like in previous Xposed versions Wanam and such have modified Xposed To properly work on Galaxy devices... Btw Thank you Wanam and Rovo for All the hard work. :good::good::good:
So What it comes down to is this is not a @partcyborg Rom issue.....
It is even talked about Here on github on Xposed
https://github.com/rovo89/Xposed/issues/294
Now there are files here for a possible fix But please be-aware that I have tried them out right many times today in different combinations today and from total FC to no boot To now Bluetooth just not turning on after reboots I have bricked every which way with these modified as they are as now.....
Some have had reports of fixing this issue Which is very similar to previous Samsung Models and root and forgetting WiFi upon each reboot if some of you remember correctly....
But Either way I figured I would toss this up for all to check out to put our heads together to get something possibly going....:good::good::good::good:
Tried this on Partctborgs ROM and got a kernel panic after reboot after my first try (BQL1). Haven't touched it since. I was hopeful though.
Sent from my Samsung SM-G950U using XDA Labs
bradical711 said:
Tried this on Partctborgs ROM and got a kernel panic after reboot after my first try (BQL1). Haven't touched it since. I was hopeful though.
Sent from my Samsung SM-G950U using XDA Labs
Click to expand...
Click to collapse
I did to I got as far as good reboots but Bluetooth wouldn't turn on. I ended up doing a stock system img with root. Unbloated and no xposed Bluetooth works great now. Since no xposed
Working Solution
I posted this in the PartCyborgRom ROM thread, and was asked to post here as well:
I can confirm that this (https://github.com/rovo89/Xposed/issues/294) fixes the issue with losing Bluetooth pairings after reboot . I was able to get this working with Xposed installed, and without reinstalling the rom or wiping data. It is not that clear what to do, so in case this helps anyone, here is what I did:
1) Uninstall Xposed, then reboot
2) Download the files from the "Lib directory" link, and copy them to /system/vendor/lib. Overwrite the existing files.
3) Download the files from the "Lib64 directory" link, and copy them to /system/vendor/lib64. Overwrite the existing files.
4) Modify build.prop by changing ro.securestorage.support to "false". I used the BuildProp Editor app.
5) Reinstall Xposed
6) Reboot into Recovery, and wipe Cache only (not Data)
7) Reboot, and voila! Bluetooth pairings that you create from now on will survive a reboot.
nationalicon said:
I posted this in the PartCyborgRom ROM thread, and was asked to post here as well:
I can confirm that this (https://github.com/rovo89/Xposed/issues/294) fixes the issue with losing Bluetooth pairings after reboot . I was able to get this working with Xposed installed, and without reinstalling the rom or wiping data. It is not that clear what to do, so in case this helps anyone, here is what I did:
1) Uninstall Xposed, then reboot
2) Download the files from the "Lib directory" link, and copy them to /system/vendor/lib. Overwrite the existing files.
3) Download the files from the "Lib64 directory" link, and copy them to /system/vendor/lib64. Overwrite the existing files.
4) Modify build.prop by changing ro.securestorage.support to "false". I used the BuildProp Editor app.
5) Reinstall Xposed
6) Reboot into Recovery, and wipe Cache only (not Data)
7) Reboot, and voila! Bluetooth pairings that you create from now on will survive a reboot.
Click to expand...
Click to collapse
Followed your steps and worked like a charm on s8+. Thanks!
Tried @nationalicon 's method and it worked flawlessly on Cyborg's (BQL1) ROM. I was a bit skeptical to try it on my s8 since when I had tried it the first time this didn't work but I hadn't tried this method. But after following these steps perfectly, everything works flawlessly. One less issue now with my ROM overall and it's even better than before. WiFi and Bluetooth connections were all lost at first but after repairing with them all and rebooting, everything is still connected now and works. Thank you!
Sent from my SM-G950U using XDA Labs
nationalicon said:
I posted this in the PartCyborgRom ROM thread, and was asked to post here as well:
I can confirm that this (https://github.com/rovo89/Xposed/issues/294) fixes the issue with losing Bluetooth pairings after reboot . I was able to get this working with Xposed installed, and without reinstalling the rom or wiping data. It is not that clear what to do, so in case this helps anyone, here is what I did:
1) Uninstall Xposed, then reboot
2) Download the files from the "Lib directory" link, and copy them to /system/vendor/lib. Overwrite the existing files.
3) Download the files from the "Lib64 directory" link, and copy them to /system/vendor/lib64. Overwrite the existing files.
4) Modify build.prop by changing ro.securestorage.support to "false". I used the BuildProp Editor app.
5) Reinstall Xposed
6) Reboot into Recovery, and wipe Cache only (not Data)
7) Reboot, and voila! Bluetooth pairings that you create from now on will survive a reboot.
Click to expand...
Click to collapse
The mediafire-sourced lib64 files aren't in my original lib64 directory. Is that a problem? Should I still add them? I all because i tried this before and it started not remembering wifi on reboot.
Thanks!
Bluetooth on the s8 is bad on a stock rom unrooted. It is a s8 problem. After a few hours Bluetooth drops and reenables itself. I have had it happen on rooted partcyborg rom. Also on a stock rom. Samsung and Google try to take over Bluetooth. Samsung has a factory Bluetooth app and Google has Bluetooth enabled for scanning location. I noticed when I get the location scan icon it drops Bluetooth even mid song. I tried turning it off but Samsung location also runs it too.
Supernoobsammyson said:
Bluetooth on the s8 is bad on a stock rom unrooted. It is a s8 problem. After a few hours Bluetooth drops and reenables itself. I have had it happen on rooted partcyborg rom. Also on a stock rom. Samsung and Google try to take over Bluetooth. Samsung has a factory Bluetooth app and Google has Bluetooth enabled for scanning location. I noticed when I get the location scan icon it drops Bluetooth even mid song. I tried turning it off but Samsung location also runs it too.
Click to expand...
Click to collapse
Thats weird I havnt had really any drop offs unrooted stock,Part cyborg rom,Or pure stock rooted.
Just paring loss upon reboots...
I actually commend Samsung for the most part.
My Bluetooth has been quite exceptional.
Maybe something is interfering and cutting yours out
I run several speakers 2 gear s2 watches My car and prob a few other items,Was actually looking into pairing my PS Vita with it and see what it will do
Supernoobsammyson said:
Bluetooth on the s8 is bad on a stock rom unrooted. It is a s8 problem. After a few hours Bluetooth drops and reenables itself. I have had it happen on rooted partcyborg rom. Also on a stock rom. Samsung and Google try to take over Bluetooth. Samsung has a factory Bluetooth app and Google has Bluetooth enabled for scanning location. I noticed when I get the location scan icon it drops Bluetooth even mid song. I tried turning it off but Samsung location also runs it too.
Click to expand...
Click to collapse
No problem with Bluetooth on my end either. I have to resynch after rebooting, but that is simple on my car stereo so I haven't done the fix. I am running Partcyborg ROM for quite a while now, but I didn't have any issues on stock either.
Smithfolk4 said:
No problem with Bluetooth on my end either. I have to resynch after rebooting, but that is simple on my car stereo so I haven't done the fix. I am running Partcyborg ROM for quite a while now, but I didn't have any issues on stock either.
Click to expand...
Click to collapse
That is the problem. It drops sync. When restarting. Also dropping for no reason. This is after playing all day. Both phone and Bluetooth device are right next to each. And not just on Bluetooth device and/or s8. It happens on one that has never been rooted. Only factory OTA updates.
https://www.google.com/amp/s/forum....lp/bluetooth-issues-oreo-update-t3765757/amp/
It is an issue.
Works thanks
jj972 said:
Followed your steps and worked like a charm on s8+. Thanks!
Click to expand...
Click to collapse
nationalicon said:
I posted this in the PartCyborgRom ROM thread, and was asked to post here as well:
I can confirm that this (https://github.com/rovo89/Xposed/issues/294) fixes the issue with losing Bluetooth pairings after reboot . I was able to get this working with Xposed installed, and without reinstalling the rom or wiping data. It is not that clear what to do, so in case this helps anyone, here is what I did:
1) Uninstall Xposed, then reboot
2) Download the files from the "Lib directory" link, and copy them to /system/vendor/lib. Overwrite the existing files.
3) Download the files from the "Lib64 directory" link, and copy them to /system/vendor/lib64. Overwrite the existing files.
4) Modify build.prop by changing ro.securestorage.support to "false". I used the BuildProp Editor app.
5) Reinstall Xposed
6) Reboot into Recovery, and wipe Cache only (not Data)
7) Reboot, and voila! Bluetooth pairings that you create from now on will survive a reboot.
Click to expand...
Click to collapse
Just wanted to confirm it does work follow steps. Only had to clear cache. I left the xposed installer installed and had no mods installes. Copy pasted the correct files files, edited the prop restarted into recovery. Then deleted only cache. Restarted paired with speaker then restarted one more time to test and boom.
Thanks for the help
dmosley said:
The mediafire-sourced lib64 files aren't in my original lib64 directory. Is that a problem? Should I still add them? I all because i tried this before and it started not remembering wifi on reboot.
Thanks!
Click to expand...
Click to collapse
Not sure, but I don't think there is any harm in trying. You can always delete the files later.
OKAY, Extremely excited here. I am ready to do everything but I am unclear as to how to uninstall Xposed. I was under the impression you'd need TWRP to do so. Unless all I need to do is the uninstall the Installer app that shows up in SETTINGS>APPS>XPOSED INSTALLER? Would I just uninstall that app and reinstall the apk from the official xposed thread?
we87 said:
OKAY, Extremely excited here. I am ready to do everything but I am unclear as to how to uninstall Xposed. I was under the impression you'd need TWRP to do so. Unless all I need to do is the uninstall the Installer app that shows up in SETTINGS>APPS>XPOSED INSTALLER? Would I just uninstall that app and reinstall the apk from the official xposed thread?
Click to expand...
Click to collapse
Thats what I did
nationalicon said:
I posted this in the PartCyborgRom ROM thread, and was asked to post here as well:
I can confirm that this (https://github.com/rovo89/Xposed/issues/294) fixes the issue with losing Bluetooth pairings after reboot . I was able to get this working with Xposed installed, and without reinstalling the rom or wiping data. It is not that clear what to do, so in case this helps anyone, here is what I did:
1) Uninstall Xposed, then reboot
2) Download the files from the "Lib directory" link, and copy them to /system/vendor/lib. Overwrite the existing files.
3) Download the files from the "Lib64 directory" link, and copy them to /system/vendor/lib64. Overwrite the existing files.
4) Modify build.prop by changing ro.securestorage.support to "false". I used the BuildProp Editor app.
5) Reinstall Xposed
6) Reboot into Recovery, and wipe Cache only (not Data)
7) Reboot, and voila! Bluetooth pairings that you create from now on will survive a reboot.
Click to expand...
Click to collapse
This worked for me. I didn't uninstall xposed. I just disabled all my mods. from xposed and followed the instructions.
Can confirm, worked for me as well. Even survived a factory reset.
im VERY confused but I cant seem to find these files ANYWHERE ... what am I missing?
nationalicon said:
I posted this in the PartCyborgRom ROM thread, and was asked to post here as well:
I can confirm that this (https://github.com/rovo89/Xposed/issues/294) fixes the issue with losing Bluetooth pairings after reboot . I was able to get this working with Xposed installed, and without reinstalling the rom or wiping data. It is not that clear what to do, so in case this helps anyone, here is what I did:
1) Uninstall Xposed, then reboot
2) Download the files from the "Lib directory" link, and copy them to /system/vendor/lib. Overwrite the existing files.
3) Download the files from the "Lib64 directory" link, and copy them to /system/vendor/lib64. Overwrite the existing files.
4) Modify build.prop by changing ro.securestorage.support to "false". I used the BuildProp Editor app.
5) Reinstall Xposed
6) Reboot into Recovery, and wipe Cache only (not Data)
7) Reboot, and voila! Bluetooth pairings that you create from now on will survive a reboot.
Click to expand...
Click to collapse
matthewd769 said:
im VERY confused but I cant seem to find these files ANYWHERE ... what am I missing?
Click to expand...
Click to collapse
Have you tried reading the thread and comments on GitHub? Lol the link for the files aren't that far down in the comments. Everyone else seemed to find the links pretty easily so idk.
Sent from my SM-G950U using XDA Labs
nationalicon said:
I posted this in the PartCyborgRom ROM thread, and was asked to post here as well:
I can confirm that this (https://github.com/rovo89/Xposed/issues/294) fixes the issue with losing Bluetooth pairings after reboot . I was able to get this working with Xposed installed, and without reinstalling the rom or wiping data. It is not that clear what to do, so in case this helps anyone, here is what I did:
1) Uninstall Xposed, then reboot
2) Download the files from the "Lib directory" link, and copy them to /system/vendor/lib. Overwrite the existing files.
3) Download the files from the "Lib64 directory" link, and copy them to /system/vendor/lib64. Overwrite the existing files.
4) Modify build.prop by changing ro.securestorage.support to "false". I used the BuildProp Editor app.
5) Reinstall Xposed
6) Reboot into Recovery, and wipe Cache only (not Data)
7) Reboot, and voila! Bluetooth pairings that you create from now on will survive a reboot.
Click to expand...
Click to collapse
bradical711 said:
Have you tried reading the thread and comments on GitHub? Lol the link for the files aren't that far down in the comments. Everyone else seemed to find the links pretty easily so idk.
Sent from my SM-G950U using XDA Labs
Click to expand...
Click to collapse
thanks for the reply .... VERY helpful. I did find it.
It is just as the title states. I would like to somehow fix my phone instead of just recovering.
I can still access twrp, and the app(https://play.google.com/store/apps/details?id=com.jumobile.manager.systemapp) is used to create it with has created some backup files that i can still access. Is there still hope?
Mi 8 Pro with lineage os 18 unofficial
PalanixYT said:
It is just as the title states. I would like to somehow fix my phone instead of just recovering.
I can still access twrp, and the app(https://play.google.com/store/apps/details?id=com.jumobile.manager.systemapp) is used to create it with has created some backup files that i can still access. Is there still hope?
Mi 8 Pro with lineage os 18 unofficial
Click to expand...
Click to collapse
If you have some idea which apps you uninstalled then you can put them back in the right directory/folder, the app you used probably created a folder to backup them anyway for the next this app is not recommended to use it blindly; it doesn´t have a good criteria to determine what´s important and what´s not.
Or you can flash only the system image and after that wipe caches, reboot.
SubwayChamp said:
If you have some idea which apps you uninstalled then you can put them back in the right directory/folder, the app you used probably created a folder to backup them anyway for the next this app is not recommended to use it blindly; it doesn´t have a good criteria to determine what´s important and what´s not.
Or you can flash only the system image and after that wipe caches, reboot.
Click to expand...
Click to collapse
do you know of a way to find out exactly whats missing? like some log or something like that?
PalanixYT said:
do you know of a way to find out exactly whats missing? like some log or something like that?
Click to expand...
Click to collapse
Yes, there are some apps on PlayStore that can do that but you can´t boot right now to use it, probably you can take some logs through adb while in TWRP, check this https://github.com/IzzySoft/Adebar
The app you used creates a folder in the SDCard, probably it keeps the apps there, if you have TWRP you can navigate to it and you´ll find them.
the app has created an xyz.apk.backup can i just use adb install, or should i do something different?
hmm, i think just reflashing the system image would be easier. So should i just reflash the lineageos.zip?
PalanixYT said:
the app has created an xyz.apk.backup can i just use adb install, or should i do something different?
Click to expand...
Click to collapse
Yes, the first is identify the apps and then you can install them using adb through TWRP or copying the app to the folder where it was previosuly.
PalanixYT said:
hmm, i think just reflashing the system image would be easier. So should i just reflash the lineageos.zip?
Click to expand...
Click to collapse
You can flash it just wiping caches.
ok thank you very much, you are a life saver
i'm sorry i messaged you
it didn't work. Maybe also flash gapps?
PalanixYT said:
it didn't work. Maybe also flash gapps?
Click to expand...
Click to collapse
What´s inside the LOS zip? And what exactly didn´t work?
it's just the zip i used when installing the custom rom. i can send the file if you wnat.
META-INF/com/android/metadata
system.new.dat.br
system.patch.dat
vendor.new.dat.br
vendor.patch.dat
META-INF/com/google/android/update-binary
META-INF/com/google/android/updater-script
boot.img
install/bin/backuptool.functions
install/bin/backuptool.sh
system.transfer.list
vendor.transfer.list
META-INF/com/android/otacert
i was still inside a boot loop
PalanixYT said:
it's just the zip i used when installing the custom rom. i can send the file if you wnat.
META-INF/com/android/metadata
system.new.dat.br
system.patch.dat
vendor.new.dat.br
vendor.patch.dat
META-INF/com/google/android/update-binary
META-INF/com/google/android/updater-script
boot.img
install/bin/backuptool.functions
install/bin/backuptool.sh
system.transfer.list
vendor.transfer.list
META-INF/com/android/otacert
i was still inside a boot loop
Click to expand...
Click to collapse
It could work if you do it correctly:
- Wipe system, caches and data (not format)
- Flash the LOS zip.
- Flash the GApps (if you had previously Google apps on it)
- Reboot.
it worked, thank you very much. Is there a way to restore my phone to its previous state? i made a twrp backup just in case
PalanixYT said:
it worked, thank you very much. Is there a way to restore my phone to its previous state? i made a twrp backup just in case
Click to expand...
Click to collapse
Great, you can restore it just at the same time you did take the backup, if at the moment that this happened you didn´t take a backup of course you can´t anyway if you had some apps synchronizing with the cloud then this will be the only way. It works similarly as Windows (or Linux distros) also work if you have some idea from.