Related
[Q&A] [SM-T525] CyanogenMod 11.0 UNOFFICIAL nightlies: Tab Pro 10.1 LTE (picassolte)
Q&A for [SM-T525] CyanogenMod 11.0 UNOFFICIAL nightlies: Tab Pro 10.1 LTE (picassolte)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [SM-T525] CyanogenMod 11.0 UNOFFICIAL nightlies: Tab Pro 10.1 LTE (picassolte). If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
RaiBinger said:
Hi again!
In 211014 ROM trouble with video in YouTub. If set pause then after play again video not work. Tell me please in last build ROM nightly update this issue resolved?
Click to expand...
Click to collapse
I have the same problem. at the same time when it occurs in other players turns off hardware decoding.
@crpalmer "As far as I am concerned, installing Xposed is the exact opposite of a clean install. Xposed can cause all kinds of problems (it just randomly changes how internals of the system work!).
If you have problems with a clean install (without Xposed), please provide logs.
---------------
Admin Note: this thread has a dedicated questions and answers section which you can access here -->."
I have factory reset, data wipe cache and delvik wipe and then just flashed Nightly from 24.10.2014 and gapps. Cannot even get through the set up before the screen flickers and the device reboots.
So installed the nightly from 27.10 and all was good for a few hours then the random reboots have started again. No xposed or any other mods. Will provide logs.
joeb690 said:
So installed the nightly from 27.10 and all was good for a few hours then the random reboots have started again. No xposed or any other mods. Will provide logs.
Click to expand...
Click to collapse
So I'm not sure what to do next, device is unfortunately unusable, I must of made a mistake somewhere along the line.
What I have tried so far:
1. boot into cwm recovery
2. wipe data/factory reset
3. wipe cache
4. wipe delvik cache
5. install nightly 27.10.2014
6. wipe cache
7. wipe delvik cache
8. install gapps from link provide in OP
9. repeat steps 6 & 7
10 reboot system.
Sometimes it will boot normally and allow me to proceed through set-up but will then very quickly crash/reboot and the it seems to be in a bootloop, or other times it will show the Samsung splash and then power off.
Yesterday I was able to use it for several hours with out a problem but then suddenly it restarted and was once again very unstable.
Also getting very erratic battery readings ( I preformed a battery calibration before wiping Touchwiz probably a big mistake I realise now )
Any help or ideas would be greatly appreciated. :good:
not sure how to provide logs as the device is so unpredictable.
joeb690 said:
So I'm not sure what to do next, device is unfortunately unusable, I must of made a mistake somewhere along the line.
What I have tried so far:
1. boot into cwm recovery
2. wipe data/factory reset
3. wipe cache
4. wipe delvik cache
5. install nightly 27.10.2014
6. wipe cache
7. wipe delvik cache
8. install gapps from link provide in OP
9. repeat steps 6 & 7
10 reboot system.
Sometimes it will boot normally and allow me to proceed through set-up but will then very quickly crash/reboot and the it seems to be in a bootloop, or other times it will show the Samsung splash and then power off.
Yesterday I was able to use it for several hours with out a problem but then suddenly it restarted and was once again very unstable.
Also getting very erratic battery readings ( I preformed a battery calibration before wiping Touchwiz probably a big mistake I realise now )
Any help or ideas would be greatly appreciated. :good:
not sure how to provide logs as the device is so unpredictable.
Click to expand...
Click to collapse
There isn't any crash in the last_kmsg. Are the logs pulled after a crash?
Yes. Will provide another log today.
Unfortunately cannot provide another log as it the device will not work long enough to email the log, will flash stock ROM and see what happens. Maybe it a physical problem.
So flashed stock using odin and problems persist. Rebooting at what seems like random times. And then during the reboot it will reboot and then sometimes nothing it's dead and doesn't react to any action except putting it in download mode. Doesn't matter if I have several apps running or if I let it idle. Never had any issues like this before rooting. Any ideas as to where I went wrong.
I know this has nothing to do with your ROM but any feedback would be appreciated. Thanks.
joeb690 said:
So flashed stock using odin and problems persist. Rebooting at what seems like random times. And then during the reboot it will reboot and then sometimes nothing it's dead and doesn't react to any action except putting it in download mode. Doesn't matter if I have several apps running or if I let it idle. Never had any issues like this before rooting. Any ideas as to where I went wrong.
I know this has nothing to do with your ROM but any feedback would be appreciated. Thanks.
Click to expand...
Click to collapse
Are you sure you flashed the right Odin images? Did you factory reset?
One thing to try would be to flash the CM recovery (twrp would also be fine if it supports last_kmsg and I forget if it does) and let it sit and see if it reboots. If so, then grab the last_kmsg via adb. If you want to flash CM again, you can try to use adb to get a last_kmsg via adb since it just has to boot long enough for adb to access it.
I flashed the latest image for the German sm t525 model from sammobile. I have performed a factory reset but I thought that when you flashed an image with odin the device is wiped clean? Do you mean CWM recovery you provide in the OP? Thanks for you reply.
Hi,
I have Bluetooth issues since some versions. Cannot connect to any device....
Other question: is it still ro.sf.lcd_density=320 ?
dft601 said:
Hi,
I have Bluetooth issues since some versions. Cannot connect to any device....
Other question: is it still ro.sf.lcd_density=320 ?
Click to expand...
Click to collapse
Do you know (and if you not would you mind trying a couple of versions) when bluetooth problems would have started?
I recently changed the density setting to ro.sf.lcd_density=320 because it seemed to fix some apps that had weird issues (e.g. Chrome Beta's tabs). Is it causing a problem for you?
crpalmer said:
Do you know (and if you not would you mind trying a couple of versions) when bluetooth problems would have started?
I recently changed the density setting to ro.sf.lcd_density=320 because it seemed to fix some apps that had weird issues (e.g. Chrome Beta's tabs). Is it causing a problem for you?
Click to expand...
Click to collapse
Hmm, sorry, do not know which version I had last before 200141109, I already deleted from my device.. at least 200141107....
No, I have no problem with the density. It fixes also problems for me (e.g. Swiftkey, Navigon,....) Till now I added this manually.
Mike
Autorotate and Contact view
Hi
I'VE installed the latest version and untill now everything is fine for me,
But whenn I open my contacts the autorotate function stops to work and I have to turn my tab by 180°
Hello there!
The rom is working great, battery time is better than stock rom, and its much faster and smoother!
Altough I am having one issue with my tablet. Sometimes on random (really random!), when I try to unlock the tablet it stops responding to touch - at all! I cannot unlock it, cannot restart it normally, cannot do anything. I have to reboot the tab by holding power button down.
I changed dpi to 240, because 320 was too high for me, everything was so big - but I don't think that dpi has something to do with the issue.
Also sometimes my Link2SD script doesnt load the 2nd sdcard partition - but this might not be connected with the rom.
But anyway this rom is great and I am happy to have it on my tablet! You're doing great job mate! Thanks a lot. The only thing I miss is multi- and floating- windows, but I can live without it.
PS I noticed you are working on Cyanogenmod 12 for exynos version, do you plan building and trying it for our snapdragon version?
poleq16 said:
Hello there!
The rom is working great, battery time is better than stock rom, and its much faster and smoother!
Altough I am having one issue with my tablet. Sometimes on random (really random!), when I try to unlock the tablet it stops responding to touch - at all! I cannot unlock it, cannot restart it normally, cannot do anything. I have to reboot the tab by holding power button down.
I changed dpi to 240, because 320 was too high for me, everything was so big - but I don't think that dpi has something to do with the issue.
Also sometimes my Link2SD script doesnt load the 2nd sdcard partition - but this might not be connected with the rom.
But anyway this rom is great and I am happy to have it on my tablet! You're doing great job mate! Thanks a lot. The only thing I miss is multi- and floating- windows, but I can live without it.
PS I noticed you are working on Cyanogenmod 12 for exynos version, do you plan building and trying it for our snapdragon version?
Click to expand...
Click to collapse
I posted a status update in the sm-t320 thread. The snapdragons are in much better shape than the exynos...
joeb690 said:
I flashed the latest image for the German sm t525 model from sammobile. I have performed a factory reset but I thought that when you flashed an image with odin the device is wiped clean? Do you mean CWM recovery you provide in the OP? Thanks for you reply.
Click to expand...
Click to collapse
So I sent my Tab in for repair and all went well, they never mentioned KNOX but this was a private company contracted by Samsung here in Germany to do repairs. Not sure of all the details but its was a hardware failure.
Unfortunately my Tab was "lost" by the courier firm contracted to return my device. In the process of making a claim and will probably receive a new device.
random touchscreen knockout
Hi there,
Just curious: do some more people have random loss of the touchscreen functionality for some seconds or even until a reboot is performed?
Hardware buttons are always fine, though.
I found one post related to this, but no clear answer.
Wiped data and cache but did not install latest nightly yet.
Is that a "known issue something" for build 20141112?
Maybe I should mention that I'm noob level: ultra...
CWMR (Recovery) flash file for ODIN
CWMR (Recovery): (use latest version)
Download: http://download.crpalmer.org/downloads/picassowifi/
* Unzip the .ZIP file and then flash the .tar.md5 that it contains using Odin
Click to expand...
Click to collapse
crpalmer could you pleas upload your flash file again? it's the best way for me because I hate to use the free alternative to ODIN...
EDIT: SORRY SHOULD BE FOR USING WITH SM-T520 DEVICE - DID USE WRONG THREAD!!!
When I got my SW3 last summer, I stupidly ignored all those warnings about flashing TWRP to recovery, mostly because I didn't see what harm could come of it. However, while investigating a battery drain that's persisted despite multiple flashes to stock and more than a few attempts to use crpalmer's LCA43 kernel, I discovered via my SW3's kernel log that it's got some serious weirdness going on with its firmware.
As it turns out, it's reloading the pedometer firmware every three seconds. This happens because every time it loads the firmware, it promptly encounters some manner of error while running it, which then prompts Android to try to reload the firmware. My first hint that this was a firmware issue came from the fact that I can't access any sensor data via the developer menu. Under 'Manufacturer: Menu-Launcher' at the bottom of Developer Options, the entries for Accelerometer, Gyro, Magnetometer, and Compass are all blank, while Ambient Light Sensor and Step Counter are perpetually stuck at 0.0.
After trying everything I could think of in my attempts to fix this issue, I then began investigating other variations from stock that I'd had over the months that I've had my SW3. Rooting didn't appear to change anything related to the firmware, and crpalmer's LCA43 kernel (and craigcharlie's simple MTP mod and, later on, alex6600's modified version of the kernel itself) didn't appear to cause any of the issues I'd been experiencing for anyone else. Finally, I found a comment somewhere about the fact that flashing TWRP to recovery instead of just booting it would really mess things up because it uses a device tree different from the SW3's stock device tree.
Since then, I've been trying everything I can imagine to fix this, but I haven't had any success thus far. Because of that and a few other reasons, I haven't been able to mess with this since the end of January, but I'm really getting tired of my SW3 only lasting for about 6-8 hours with pretty minimal use. I think the closest I got to any sort of progress was using dd to individually flash partitions that'd been uploaded, but I don't think I was ever able to find an upload of mmcblk0p19, dt-blob.
Does anyone have any ideas about what I might be able to do to fix this? Specifically, I'm curious to know whether or not dding partitions damaged when I flashed TWRP should work; if so, would someone be so kind as to either post or PM me dded copies of the relevant partitions? Thanks in advance for the help!
Repair with PCCompanion. Did that some weeks ago. Version is LCA43.
If pc companion does not work (and it probably wont), hold down the button on boot, and you can force it to usb mode. If that does not work, hit the button twice to go to fastboot and flash the original OS (look for the repair threads).
Good luck.
Sent from my SM-T810 using Tapatalk
Hi all,
I'm wanting to send my phone back to HTC as I am experiencing the same issues as https://forum.xda-developers.com/htc-10/help/random-shut-boot-loops-t3690547
I wanted to get as back-to-stock as possible before I did so, to limit any chances of additional charges.
I tried to flash the TWRP backup from the Stock HTC 10 thread by topjohnwu (the latest one). I'm now stuck in a bootloop - I see the white HTC logo, and then it reboots.
Anyone help? I'm annoyed as I had a working phone not long before this I've tried RUUs but the all fail with an invalid header, the exes don't work etc (fail after sending).
I just am not sure what to flash. I can access TWRP and bootloader etc. Just no system.
Also, if anyone has a thread that discusses which part of the system does what, for someone looking to gain a better understanding, that would be great. I really like the HTC 10 and, when working, have no problems with it, and I wouldn't mind keeping it for longer than i usually would a phone.
Thanks in advance
SOLVED - fixed by flashing a deodexed ROM zip found on here
I felt compelled to register here and post my success on getting LineageOS installed on my Verizon VK810 4G Altev LG G Pad tablet. It would not have been possible without this forum and the users who contribute, both with information and with uploads. I initially tried rooting with KingRoot and the OTA updated OS I had from Verizon but the app said there were 63 requests for rooting my device. Forget that idea. After also trying iRoot which wasn't working, I used the LG Flash Tool to downgrade to VK81035A and then was successfully able to root that. SuperSu definitely helped with the process. My guess is, even though both were Android 5.0.2, mine had OTA patches that I guess caused issues for rooting. Installing TWRP was a hassle though. None of the v500 TWRP images worked for me and many of the custom TWRP versions that I found on here did not work for me. You would not imagine the number of times I thought I bricked my device because I kept getting "Secure Booting Error! Cause: boot certification verify" errors. However, what did work for me was, using Platform-tools and VK810_twrp_2.7.0.1.zip for TWRP. For some reason, the other versions posted here did not work for me. It did take me a while to figure out how to get into TWRP because I kept using the Power-VolUp key combinations and it kept bringing me to what looked like LG's recovery menu. I didn't realize that the screen is actually fake and you have to click "Factory Reset/Wipe" on there to get into TWRP. It actually took me a long time to figure that out. With TWRP installed, I searched for ROMs that I could use that were newer than Android 5.0.2 and ended up downloading LineageOS as it came up for the VK810 and since VS500 ROMs weren't allowed to be installed. Now to be fair, the LineageOS Rom that I used (lineage-14.1-20171228_233442-UNOFFICIAL-vk810.zip) is pretty glitchy. The display likes to blink a lot, many apps crash on it and there is no cellular data working for me, but I assume that will possibly be fixed in the future and at least now, I can customize more than I could on stock. On first install, I also lost my root and forgot to install the GApps package from the Lineage website. Anyway, hope this helps at least one person here. Nothing was one-click for me, but I did learn a lot about the process of rooting and flashing, and now better than to automatically allow OTA updates. I do hope LineageOS or another ROM keeps updating for the VK810 because this tablet does not seem that popular and I would like to see Oreo. Thank you everyone for your help!
XDAnonymous said:
I felt compelled to register here and post my success on getting LineageOS installed on my Verizon VK810 4G Altev LG G Pad tablet. It would not have been possible without this forum and the users who contribute, both with information and with uploads. I initially tried rooting with KingRoot and the OTA updated OS I had from Verizon but the app said there were 63 requests for rooting my device. Forget that idea. After also trying iRoot which wasn't working, I used the LG Flash Tool to downgrade to VK81035A and then was successfully able to root that. SuperSu definitely helped with the process. My guess is, even though both were Android 5.0.2, mine had OTA patches that I guess caused issues for rooting. Installing TWRP was a hassle though. None of the v500 TWRP images worked for me and many of the custom TWRP versions that I found on here did not work for me. You would not imagine the number of times I thought I bricked my device because I kept getting "Secure Booting Error! Cause: boot certification verify" errors. However, what did work for me was, using Platform-tools and VK810_twrp_2.7.0.1.zip for TWRP. For some reason, the other versions posted here did not work for me. It did take me a while to figure out how to get into TWRP because I kept using the Power-VolUp key combinations and it kept bringing me to what looked like LG's recovery menu. I didn't realize that the screen is actually fake and you have to click "Factory Reset/Wipe" on there to get into TWRP. It actually took me a long time to figure that out. With TWRP installed, I searched for ROMs that I could use that were newer than Android 5.0.2 and ended up downloading LineageOS as it came up for the VK810 and since VS500 ROMs weren't allowed to be installed. Now to be fair, the LineageOS Rom that I used (lineage-14.1-20171228_233442-UNOFFICIAL-vk810.zip) is pretty glitchy. The display likes to blink a lot, many apps crash on it and there is no cellular data working for me, but I assume that will possibly be fixed in the future and at least now, I can customize more than I could on stock. On first install, I also lost my root and forgot to install the GApps package from the Lineage website. Anyway, hope this helps at least one person here. Nothing was one-click for me, but I did learn a lot about the process of rooting and flashing, and now better than to automatically allow OTA updates. I do hope LineageOS or another ROM keeps updating for the VK810 because this tablet does not seem that popular and I would like to see Oreo. Thank you everyone for your help!
Click to expand...
Click to collapse
Wow thank you so much I thought it was me having issues. I have a 410vk and as you said nothing was one click. I hope to continue to try and get root on the G Pad. Still an awesome device.
Sent from my LG-H932 using Tapatalk
XDAnonymous said:
I felt compelled to register here and post my success on getting LineageOS installed on my Verizon VK810 4G Altev LG G Pad tablet. It would not have been possible without this forum and the users who contribute, both with information and with uploads. I initially tried rooting with KingRoot and the OTA updated OS I had from Verizon but the app said there were 63 requests for rooting my device. Forget that idea. After also trying iRoot which wasn't working, I used the LG Flash Tool to downgrade to VK81035A and then was successfully able to root that. SuperSu definitely helped with the process. My guess is, even though both were Android 5.0.2, mine had OTA patches that I guess caused issues for rooting. Installing TWRP was a hassle though. None of the v500 TWRP images worked for me and many of the custom TWRP versions that I found on here did not work for me. You would not imagine the number of times I thought I bricked my device because I kept getting "Secure Booting Error! Cause: boot certification verify" errors. However, what did work for me was, using Platform-tools and VK810_twrp_2.7.0.1.zip for TWRP. For some reason, the other versions posted here did not work for me. It did take me a while to figure out how to get into TWRP because I kept using the Power-VolUp key combinations and it kept bringing me to what looked like LG's recovery menu. I didn't realize that the screen is actually fake and you have to click "Factory Reset/Wipe" on there to get into TWRP. It actually took me a long time to figure that out. With TWRP installed, I searched for ROMs that I could use that were newer than Android 5.0.2 and ended up downloading LineageOS as it came up for the VK810 and since VS500 ROMs weren't allowed to be installed. Now to be fair, the LineageOS Rom that I used (lineage-14.1-20171228_233442-UNOFFICIAL-vk810.zip) is pretty glitchy. The display likes to blink a lot, many apps crash on it and there is no cellular data working for me, but I assume that will possibly be fixed in the future and at least now, I can customize more than I could on stock. On first install, I also lost my root and forgot to install the GApps package from the Lineage website. Anyway, hope this helps at least one person here. Nothing was one-click for me, but I did learn a lot about the process of rooting and flashing, and now better than to automatically allow OTA updates. I do hope LineageOS or another ROM keeps updating for the VK810 because this tablet does not seem that popular and I would like to see Oreo. Thank you everyone for your help!
Click to expand...
Click to collapse
Can you link where you got the ROM? Is anyone actively working on it? Really too bad the vk810 never got much love, great little device. Been awhile since I've done anything with it, it's my dad's so I got it rooted on 5.0.2 and just kinda left it alone. What prompted me to come back to this forum is screen mirroring won't work. The tablet sees TV and vice versa, it tries to connect but never completes the connection, just kicks back to satellite TV after a couple of seconds of black screen. Don't suppose you tried casting on that lineage build?
AirForceOnes0010 said:
Can you link where you got the ROM? Is anyone actively working on it? Really too bad the vk810 never got much love, great little device. Been awhile since I've done anything with it, it's my dad's so I got it rooted on 5.0.2 and just kinda left it alone. What prompted me to come back to this forum is screen mirroring won't work. The tablet sees TV and vice versa, it tries to connect but never completes the connection, just kicks back to satellite TV after a couple of seconds of black screen. Don't suppose you tried casting on that lineage build?
Click to expand...
Click to collapse
I got the ROM from the Invisiblek ROMS site under /roms/lineage-14.1/vk810/ (Can't post the link as I'm currently under 10 posts)
It's definitely a start. There is screen glitching, and no LTE service (Wi-Fi only), so it definitely limits the tablet. I have not done much with it as it was a hassle just to get the root within the OS to work correctly. Some apps aren't detecting root when the OS is trying to give it to them.
XDAnonymous said:
I got the ROM from the Invisiblek ROMS site under /roms/lineage-14.1/vk810/ (Can't post the link as I'm currently under 10 posts)
It's definitely a start. There is screen glitching, and no LTE service (Wi-Fi only), so it definitely limits the tablet. I have not done much with it as it was a hassle just to get the root within the OS to work correctly. Some apps aren't detecting root when the OS is trying to give it to them.
Click to expand...
Click to collapse
It'll have to wait until/if LTE is ever functional then, my parents don't have internet other 4g out in the sticks lol. Google took me right to it, thanks. Will keep it bookmarked just in case
I'd like to write about my experience too as it took me some time to finally get the device up and running.
I will describe what I wanted to do, what mistakes I've made and what should've been the correct way.
The device itself is LG G Pad 8.3, Verizon LTE variant aka vk810
Initally I received it in a bricked state, on launching it showed the "Secure booting error" message and that's it.
1) Unbricking
The goal was to install an official LG system image and restore the tablet to a working state.
Basically, I did everything according to the steps outlined here: https://forum.xda-developers.com/lg-g-pad-83/general/vk810-4g-reliable-to-root-install-t3283027
Installed LG drivers
Downloaded the LG Flash Tool 2104
Downloaded a KDZ image
Plugged the device in the download mode into the PC and installed the KDZ using the flash tool
At that point I got a fancy idea to install a non-stock Android on this tablet.
2) Lineage OS
I chose this OS for my tablet, because it seems to be the current standard for non-stock Android installations.
I followed these installation instructions: https://wiki.lineageos.org/devices/v500/install
BEWARE: that page is for v500, so it won't work for vk810.
Lineage doesn't support vk810 officially. A mistake I've made was assuming that I can just roll along with a v500 installation. Actually, you kinda can, but for me it resulted in Wi-Fi not working and my device's MAC address being 02:00:00:00:00:00.
3) Rooting
I was quite confused here too: there are different rooting methods, and some of them can be applied in different ways.
Ultimately I found Stump to be the most comfortable for me: https://forum.xda-developers.com/lg...root-stump-root-lg-g3-sprint-verizon-t2850906
It works fine on this device and uses a very straightforward process: download APK to your PC, connect the tablet to the PC, "adb install <filename>.apk", then launch the app and that's it. It had to go through the bruteforce process to root, which took several minutes.
4) TWRP
I don't remember what exact TWRP I installed initially, but it was a 3.x version, and I encountered an issue where it couldn't mount any of the tablet's partitions. That was quite a pain in the ass.
For a while I resorted to using an older version, 2.7.x, and it worked fine.
Ultimately what I'm the most happy with is this: https://forum.xda-developers.com/lg-g-pad-83/general/vk810-twrp-3-1-1-0-unofficial-t3691551
The lesson learned here is that, again, you need to make sure stuff you install is compatible with your device.
Ultimately, after making mistakes at each step of the process, I figured out everything, and just followed the installation instructions on the Lineage page I linked earlier.
* Flash stock rom
* Root using Stump
* Enable USB debugging on the tablet, install Stump via adb and root the device
* Install vk810 variant of TWRP 3.2.1-0 via adb
* Reboot to recovery (turn off the tablet -> hold Volume Down + Power -> you should get a factory reset menu after the LG logo -> select factory reset, then confirm it and you'll be booted into TWRP. That factory reset is fake after you have TWRP installed)
* Wipe everything
* adb push the lineage / lineage's su / opengapps onto the device
* Install lineage, then su and opengapps and you're good to go
Main lesson learned: it is CRUCIAL to make sure stuff you install is compatible with your particular device. Do not assume that you can use another version, even if it is made for a device of the same family.
Just to provide an update here, this is where the ROM that I used came from: https://updater.invisiblek.org/vk810
The latest version at this time seems to be this: lineage-17.1-20200329-UNOFFICIAL-vk810.zip
XDAnonymous said:
Just to provide an update here, this is where the ROM that I used came from: https://updater.invisiblek.org/vk810
The latest version at this time seems to be this: lineage-17.1-20200329-UNOFFICIAL-vk810.zip
Click to expand...
Click to collapse
Thanks for all the great information, but I have the VK810 that has usb connection problems. It will connect, but it keeps dropping (it cannot be trusted with usb cord). I have wanted to root, twrp, magisk and other things just to play around to see what it can do or how far I can go with it. I am not afraid to trash it. Have you or anyone else had this problem? I have reset it, wiped it out, factory settings, but nothing seems to help that usb port. I was thinking that reflashing the rom might help. Any advice is appreciated.
Hi, I'd like to start off by saying I'm new here, and have went over all the newbie threads as best as I can. I appreciate how welcoming this forum is, I never took that much of a deep look at it besides looking at threads in the past for multiple things. Still very new to all this stuff in general. Due to being stuck rn, I cannot provide a proper signature, apologies.
Couple Days Ago- Unlocked bootloader on my Oneplus 7 Pro using adb, flashed TWRP for the then current version for the 7 Pro Guacamole referenced from the post here, then sideloaded Lineage through TWRP. Started using the device and it seemed to have went well and like a pretty average install as far as I can tell.
Note- I'm not sure if I installed TWRP properly, as I was able to boot into TWRP through power button and volume up, but I remember also accidentally booting into the Lineage Recovery at some point after my phone was already rooted after the next step, but idk honestly. I note this bc I seen that there might be another step to permanently install twrp once inside after flashing, but not sure, apologies. My lack of knowledge feels inexcusable with how abundant it is here.
I rooted the device soon after with magisk, which I installed the zip (which was simply placed in main directory) through TWRP, then finished the install in the OS and that seemed to be good. Mention I didn't actually know that the device was rooted after the first time, dumb ik, but I did this maybe 3 times before realizing that the device was indeed already rooted and I did it extra times.
Today I got the notification for a Lineage OS update in the OS. Because I know it's coming, yeah, ik how stupid this was to not make backups beforehand as I already have a good bit on there I don't wish to lose, although I have MEGA for all my super important stuff like my password database, etc. Needless to say, I have learned my lesson. Nonetheless, I downloaded the update and pressed the install button. It said installed and would need a reboot, so I did. Then it got stuck in the boot animation for 1.5+ hours.
Force shutting it off and into fastboot, I could boot into the updated lineage recovery, but no TWRP. I have tried reflashing the previous version of the lineage recovery and it did not make a difference. I also tried flashing the next newest version of TWRP for the 7 Pro running guacamole, but then I couldn't get any further than the bootloader.
I ended up reflashing the up to date version of the lineage recovery and it sat doing nothing for a while, so it's off now. I presume that Nebrassy and other devs for TWRP are working on a version for the new update, but idk how long that takes, not complaining though. (mad respect for all who make lineage, twrp and all this possible) (not to mention I don't even know the root of the problem)
Any thoughts or help would be much appreciated, and feel free to ask questions. I would preferably not have to wipe it all and restart, so I'm looking for solutions, although I'm willing to accept this might be for nothing and take the L. Lastly sorry if I have done anything "wrong" in this thread, lmk if I can do anything better, I appreciate it.