Related
Firstly: I'm a total n00b for this. I have flashed custom ROMs before, but not for Nexus, so this is my first attempt, so far failing spectacularly.
That said, I'd appreciate advice on both what I did wrong and how to un-brick my phone.
I searched and my problem seems strictly linked to bad flashing, but all solutions are phone specific and I haven't found a thread for Galaxy nexus, so here goes:
I chose this firmware for my flash. I also used the toolkit from stickied post above.
I unlocked the bootloader and then ran (not installed) the CWM tools. Using them I flashed the image directly. The phone was not rooted though I later ran the rooting procedure and it finished without reporting any particular errors. Android naturally never booted during this procedure.
Anyway, my phone now stays in boot animation indefinitely. Recovery mode with fastboot works, but no android joy.
Help greatly appreciated.
More info is needed you didn't mention toro, toro plus, maguro. Ask you need to do is bout into bootloader and fastboot your images back to stick look in your models thread on how to do that so you can get the correct ones.
Sent from my Galaxy Nexus using xda premium
Sorry for panicking too soon. Phone unbricked. Would still appreciate info on what I did wrong to brick it in the first place.
Beamer9408 said:
More info is needed you didn't mention toro, toro plus, maguro. Ask you need to do is bout into bootloader and fastboot your images back to stick look in your models thread on how to do that so you can get the correct ones.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Hm, I've been reading on toolkit and roms for a couple of days now and I still can't really say what toro or maguro is. In what way would they be important for my troubles?
velis74 said:
Hm, I've been reading on toolkit and roms for a couple of days now and I still can't really say what toro or maguro is. In what way would they be important for my troubles?
Click to expand...
Click to collapse
It's very important to know what type of google nexus you have. Majority of custom ROMs are only compatible to certain type of GNex. Maguro is for GSM GNex while TORO is for CDM/LTE GNex. Check the link below for more info:
https://groups.google.com/forum/#!msg/android-building/qzSxFEqWvNg/qanfxMkzXHMJ
One more thing, aside from Maguro and Toro, you still need to know what build or version of GNex you have (yakju or takju). This can also be considered when flashing new custom ROMs. I know majority (or all) of the ROMs works well with either yakju or takju, there is still a slight possibility that you will encounter an issue with the version. Check out the links below for more info regarding yakju and takju:
http://forum.xda-developers.com/showthread.php?t=1778543
http://forum.xda-developers.com/showthread.php?t=1617685
Oh, in that case, I have a GSM version, Maguro it would seem.
The ROM I downloaded doesn't specifically say, but the same developer posted another ROM for which he confirmed GSM compatibility.
So can I myself find out what ROM this is since I can't ask the question in the development thread (I don't have 10 posts yet)?
did you clear all the caches via custom recovery? Although I haven't hit issues with my nexus while flashing, past devices, a factory reset sorts the bootloop most often (unless it was a bad flash). Just note that factory resetting the nexus gets rid of ALL of your data since there isn't an external SD to house your files and keep them protected from a wipe.
I would recommend you making a nandroid backup now that you're up and running again btw
Just my 2 cents
Kohawk09 said:
did you clear all the caches via custom recovery? Although I haven't hit issues with my nexus while flashing, past devices, a factory reset sorts the bootloop most often (unless it was a bad flash). Just note that factory resetting the nexus gets rid of ALL of your data since there isn't an external SD to house your files and keep them protected from a wipe.
I would recommend you making a nandroid backup now that you're up and running again btw
Just my 2 cents
Click to expand...
Click to collapse
Yes, I cleared everything I found in main menu and advanced menu of CWM.
Do I *NEED TO* root my phone in order to install a custom ROM? I would think not, but one can't be sure. That's why I only unlocked bootloader before flashing.
Edit: Yes, I found about the factory reset the hard way. Executed full wipe, then tried to flash...
velis74 said:
Yes, I cleared everything I found in main menu and advanced menu of CWM.
Do I *NEED TO* root my phone in order to install a custom ROM? I would think not, but one can't be sure. That's why I only unlocked bootloader before flashing.
Click to expand...
Click to collapse
I would think you should have rooted... my logic is that you're flashing a zip, so you're making changes to /system, which requires root. I'm not technical enough to say whether or not installing a zip can work around not having root access, but I would think not. If you were flashing system images, I would think you could get by without rooting, but not for just a zip file.
Have you taken a look at the toolkit? Soon as I got my nexus I did the one click to unlock, root, install CWM. Took less than 10 min. I already knew fastboot commands, so no reason for me to do it manually if I can get it done automatically.
Kohawk09 said:
I would think you should have rooted... my logic is that you're flashing a zip, so you're making changes to /system, which requires root. I'm not technical enough to say whether or not installing a zip can work around not having root access, but I would think not. If you were flashing system images, I would think you could get by without rooting, but not for just a zip file.
Have you taken a look at the toolkit? Soon as I got my nexus I did the one click to unlock, root, install CWM. Took less than 10 min. I already knew fastboot commands, so no reason for me to do it manually if I can get it done automatically.
Click to expand...
Click to collapse
no to toolkits... just no...
you do not need root to flash custom roms, only an unlocked bootloader and CWM or TWRP for your recovery.
Zepius said:
no to toolkits... just no...
you do not need root to flash custom roms, only an unlocked bootloader and CWM or TWRP for your recovery.
Click to expand...
Click to collapse
Why all the hate for the toolkit? Probably the only confusing thing to me since moving to the nexus is why so many seem to be against its use... I think its a great and helpful tool.
Kohawk09 said:
Why all the hate for the toolkit? Probably the only confusing thing to me since moving to the nexus is why so many seem to be against its use... I think its a great and helpful tool.
Click to expand...
Click to collapse
go look at Q&A
everyday there are at least 5-10 threads saying "HELP I BRICKED MY NEXUS... i used this toolkit but i have no idea what happened to my phone"
if someone is too lazy to type in these 2 commands and then flash su.zip to their phone, they dont need to be dinking with custom ROMs
Code:
fastboot oem unlock
fastboot flash recovery nameofclockworkortwrp.img
nexus phones are some of the easiest phones to unlock and root. there is no real need for a toolkit.
I'm currently making another attempt, but this time I'm rooting the phone and trying an image that is confirmed GSM.
Zepius said:
go look at Q&A
everyday there are at least 5-10 threads saying "HELP I BRICKED MY NEXUS... i used this toolkit but i have no idea what happened to my phone"
if someone is too lazy to type in these 2 commands and then flash su.zip to their phone, they dont need to be dinking with custom ROMs
Code:
fastboot oem unlock
fastboot flash recovery nameofclockworkortwrp.img
nexus phones are some of the easiest phones to unlock and root. there is no real need for a toolkit.
Click to expand...
Click to collapse
makes sense.... agree its probably more of a hinder than a help for those without basic fastboot knowledge. Especially since that knowledge is needed for getting out of a bind many times. Was just curious why I see some much negativity towards it...I still think its a useful tool to save time, at least from my perspective, if you already have that background. The files are all downloaded together and it was more of a convenience thing for me at least. The driver piece is probably the most helpful, since they can be a real PITA if there are leftovers from previous devices...
Just thought I pop my head in and say you were bootlooped. Not bricked. Not even soft bricked as that would constitute you had no recovery, which you did have. Just getting you clear on the lingo we use here.
Sent From My Toro+ via SkyBlue Tapatalk
Seems I chose a bad ROM after all. Flashing to CdTDroid's other ROM worked immediately.
Well, almost: after flash it would continuously report "system UI stopped working" or some such. I had to perform another factory reset before it actually worked as it should.
Now to go test if my issues with this phone are finally over or not.
velis74 said:
Seems I chose a bad ROM after all. Flashing to CdTDroid's other ROM worked immediately.
Well, almost: after flash it would continuously report "system UI stopped working" or some such. I had to perform another factory reset before it actually worked as it should.
Now to go test if my issues with this phone are finally over or not.
Click to expand...
Click to collapse
before you install a rom, always wipe data/cache.
That's the problem: I thought I did. Anyway, it's working now. Will have another go at CM later. Since I'm on custom ROM I might as well go all the way
Sent from my Galaxy Nexus using xda app-developers app
velis74 said:
I'm currently making another attempt, but this time I'm rooting the phone and trying an image that is confirmed GSM.
Click to expand...
Click to collapse
You don't need to root, as flashing the ROM will wipe the root. Most ROMs come with root access already, so people don't notice when they flash.
Yeah, figured as much + stopped doing all the unnecessary crap. Turns out flashing takes few steps but I dare not be as careless to say it's easy.
I have now successfully flashed the CM10 ROM by CdTDroiD straight from stock 4.0.4.
Turns out I misinterpreted "wipe data/factory reset" in CWM. It doesn't clear the filesystem (/sdcard) as I thought. Seems I managed to delete my files some other way during the first flashing attempt. Not clearing data was the cause of bootloop as Über reminds me it's called.
I did all that plus kept the original ICS animation which I like better than JB one. I'm really happy thus far having used it for a couple of hours.
Hello everyone,
First of all my problem. Since about 2 weeks I started getting random crashes. The phone is unresponsive and the screen goes from really bright to a greenish/grey color (hard to explain). I googled but I didn't find an answer. If anyone here knows the problem that'd be great but I doubt it since there are so many this that could cause this. So now my question is, how can I be certain it's not an software issue? Further info: My phone is rooted, and I didn't change the ROM. However, I don't actually have root permissions and when I open SuperSU it asks me to update the binary which always fails. I tried to Root it again with the Galaxy Toolkit and it says it's already rooted. Also, Under the google logo is a unlocked lock sign.
Thanks
I would recommend you to try some custom stable ROM, based on 4.1.2. CM, AOKP are among top ones.
better make a backup using recovery, and flash a new ROM. It will give you a fresh start with SU too.
If you dont like using a custom ROM, restore an earlier backup if you already have..
marcusabu said:
Hello everyone,
First of all my problem. Since about 2 weeks I started getting random crashes. The phone is unresponsive and the screen goes from really bright to a greenish/grey color (hard to explain). I googled but I didn't find an answer. If anyone here knows the problem that'd be great but I doubt it since there are so many this that could cause this. So now my question is, how can I be certain it's not an software issue? Further info: My phone is rooted, and I didn't change the ROM. However, I don't actually have root permissions and when I open SuperSU it asks me to update the binary which always fails. I tried to Root it again with the Galaxy Toolkit and it says it's already rooted. Also, Under the google logo is a unlocked lock sign.
Thanks
Click to expand...
Click to collapse
ahsanali.pk said:
I would recommend you to try some custom stable ROM, based on 4.1.2. CM, AOKP are among top ones.
better make a backup using recovery, and flash a new ROM. It will give you a fresh start with SU too.
If you dont like using a custom ROM, restore an earlier backup if you already have..
Click to expand...
Click to collapse
My only expercience with custom roms got me into a boot loop, so I don't prefere that. I actually want a "out-of-the-box" phone without any modifications. Therefore I tried a factory reset but that keeps the root and unlock.
marcusabu said:
My only expercience with custom roms got me into a boot loop, so I don't prefere that. I actually want a "out-of-the-box" phone without any modifications. Therefore I tried a factory reset but that keeps the root and unlock.
Click to expand...
Click to collapse
ok, if you want to get the total old look, relock the bootloader, and install official GNex image that comes straight from Google. Hope this sorts the issue out.
Yes, Custom ROMs are a bit time taking to setup in the start, but thats the whole point - a lot of options. I flashed alot of ROMs and luckily, I have had no boot issue still. I think following the proper instructions(which are simply wiping and formatting data, cache, and dalvik) are easily gonna keep the boot loops away.
You can rule out a sw issue by starting fresh.
http://forum.xda-developers.com/showthread.php?t=1626895
Sent from my i9250
After tinkering with my Androids over the years, (Infuse, Captivate, G2, and now G3) I have finally decided to become a member of the forum that I primarily use as a source of information and links to downloads. I'd like to first say thank you to all those that have unknowingly help me over the years with my roots. Great place you've got here.
Now the fun part, after two days of ownership, I have experienced the first issue was not able to resolve on my own, what appears to be a hard brick. I downloaded Flashify after my initial root, installed TWRP Manager, ran the patch for writing to the SDcard, and installed TWRP Recovery from AutoRec. All appeared to go well and it said the instal was successful. I followed the instructions I found online that had great results for my particular model and version 5.0.1. Well, when I went to boot into recovery to make my initial backup, the phone shut down and would not come back up. No response at all. It wont power up by any method, tried letting the capacitors drain, still no go. After tinkering with it for a few hours (I've owned this phone for a total of 2 days now), I finally came to the conclusion that it would need JTAG and the original boot image flashed over the one that I mucked up.
Any ideas on where I made my mistake? I'm near 100% certain I downloaded the proper files for my phone model.
Also forgot to mention, I have not changed anything else on the phone. Only installed apps and root browsers I planned on using. So stock kernel, stock ROM, nothing until I started getting ready to make myself a save point, ironic really!
jamguitarist said:
After tinkering with my Androids over the years, (Infuse, Captivate, G2, and now G3) I have finally decided to become a member of the forum that I primarily use as a source of information and links to downloads. I'd like to first say thank you to all those that have unknowingly help me over the years with my roots. Great place you've got here.
Now the fun part, after two days of ownership, I have experienced the first issue was not able to resolve on my own, what appears to be a hard brick. I downloaded Flashify after my initial root, installed TWRP Manager, ran the patch for writing to the SDcard, and installed TWRP Recovery from AutoRec. All appeared to go well and it said the instal was successful. I followed the instructions I found online that had great results for my particular model and version 5.0.1. Well, when I went to boot into recovery to make my initial backup, the phone shut down and would not come back up. No response at all. It wont power up by any method, tried letting the capacitors drain, still no go. After tinkering with it for a few hours (I've owned this phone for a total of 2 days now), I finally came to the conclusion that it would need JTAG and the original boot image flashed over the one that I mucked up.
Any ideas on where I made my mistake? I'm near 100% certain I downloaded the proper files for my phone model.
Also forgot to mention, I have not changed anything else on the phone. Only installed apps and root browsers I planned on using. So stock kernel, stock ROM, nothing until I started getting ready to make myself a save point, ironic really!
Click to expand...
Click to collapse
Post the guide that you followed
You would have to kick your phone into Qualcomm USB Loader 9008 in order to fix it
http://www.androidbrick.com/unbrick-recover-your-dead-lg-g3-all-variants/
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.