I'm not good at this at all so if someone wants to clean up the post they can. Anyway, I took the stock rom and converted to zip.
I was also able to do the following:
Add Root
Add Busybox (updated)
Add su.d support
Add Init.d Support via boot.img
Add /data/app support
Add insecure boot.img
Removed dm-verity from boot.img
Removed forceencrypt from boot.img
All this was made possible via SuperR's Kitchen (which is pretty awesome by the way)
Many thanks for his work, that made this all possible. Now I as able to make this same rom
work for the network B versions as well (I have network B). I added the script and files needed to the
ROM for it to work. Let me know how it works out.
Network A
Network B
And found this over at 4pda.ru. Its working great so far!
MyBeats
Is this ROM for p8000 2015 or 2016? What about the fingerprint and the Lag on wake up?
Which recovery do u use for flashing?
And, good job!
Its for the 2015, I did just notice the lag and I haven't tried the finger print yet but would assume those are not fixed. You should use the TWRP 3.0.2 from needrom.com to flash this.
Sent from my P8000 using Tapatalk
Of course after I say that the lag stops
Sent from my P8000 using Tapatalk
Would you be willing to build this for the 2016 version? (Stock 6.0)
In any case thank you for your contribution!
Dvalin21 said:
Of course after I say that the lag stops
Sent from my P8000 using Tapatalk
Click to expand...
Click to collapse
Im sorry i did not uderstand that. I was reffering to the Lag on wake up. You know when the phone is locked, and u press the power button. It takes ~2.5 secounds for the display to light up. That bug is still present?
Dvalin21 said:
I'm not good at this at all so if someone wants to clean up the post they can. Anyway, I took the stock rom and converted to zip.
I was also able to do the following:
Add Root
Add Busybox (updated)
Add su.d support
Add Init.d Support via boot.img
Add /data/app support
Add insecure boot.img
Removed dm-verity from boot.img
Removed forceencrypt from boot.img
All this was made possible via SuperR's Kitchen (which is pretty awesome by the way)
Many thanks for his work, that made this all possible. Now I as able to make this same rom
work for the network B versions as well (I have network B). I added the script and files needed to the
ROM for it to work. Let me know how it works out.
Network A
Network B
And found this over at 4pda.ru. Its working great so far!
MyBeats
Click to expand...
Click to collapse
sorry i am not able to install your rom first if i tryed i got twrp error 7 (this is for p8000 you have a k05ts_a) so i changed the updater-script to k05ts_a than i got twrp error 6 what to do please? or could you change the updater script?
thx
Edit:
I had to chane the two lines:
format("ext4", "EMMC", "/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/system", "0", "/system");
set_progress(0.100000);
mount("ext4", "EMMC", "/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/system", "/system");
set_progress(0.200000);
to:
format("ext4", "EMMC", "/dev/block/platform/mtk-msdc.0/by-name/system", "0", "/system");
set_progress(0.100000);
mount("ext4", "EMMC", "/dev/block/platform/mtk-msdc.0/by-name/system", "/system");
set_progress(0.200000);
with that the setup worked well but after that i got a bootloop
Try installing the image version of 6.0, format when you do, and then install it. This worked for me when I came from lollipop
Sent from my P8000 using Tapatalk
Dvalin21 said:
Try installing the image version of 6.0, format when you do, and then install it. This worked for me when I came from lollipop
Sent from my P8000 using Tapatalk
Click to expand...
Click to collapse
is the ROM good? Does it have the wake up bug again?
It doesn't seem to have that. I haven't experienced it but I've only been running it for two days now
Sent from my P8000 using Tapatalk
Dvalin21 said:
It doesn't seem to have that. I haven't experienced it but I've only been running it for two days now
Sent from my P8000 using Tapatalk
Click to expand...
Click to collapse
so when the phone is locked and the screen is off, once you click on the power button it wakes up normally? Without delay?
Dvalin21 said:
Try installing the image version of 6.0, format when you do, and then install it. This worked for me when I came from lollipop
Sent from my P8000 using Tapatalk
Click to expand...
Click to collapse
You mean format not factory reset? I only did a factory reset ...
Using the spftool format and install 6.0. Then install the twrp recovery with the tool and then install the zip. Make sure to wipe everything except your mico SD card
Sent from my P8000 using Tapatalk
Wake up delay is a kernel issue. No fixable for now.
boka18 said:
Im sorry i did not uderstand that. I was reffering to the Lag on wake up. You know when the phone is locked, and u press the power button. It takes ~2.5 secounds for the display to light up. That bug is still present?
Click to expand...
Click to collapse
Sorry, I do experience lag when waking up the phone from lock
No 4g Network
I installed this ROM for the P8000 version B, and I have managed to retrieve the IMEI , but I can not get 4G ... any idea how to solve it?
AispuroR said:
I installed this ROM for the P8000 version B, and I have managed to retrieve the IMEI , but I can not get 4G ... any idea how to solve it?
Click to expand...
Click to collapse
So you was able to install...but when you say retrieve IMEI, what do you mean?
Sent from my P8000 using Tapatalk
Dvalin21 said:
So you was able to install...but when you say retrieve IMEI, what do you mean?
Sent from my P8000 using Tapatalk
Click to expand...
Click to collapse
An apology for my English , I only speak Spanish ... I meant " recover the imeis " with a terminal. When I install a new ROM always I need to insert the IMEI again. I have already achieved in this ROM , but I could not turn on 4g . Engineer mode does not allow me to select the bands of my mobile operator (and it is a fact that is supported, as in android 5.1 I can definitely have 4g) . I need Band 4 for 4g and Band 2 and 5 for 3g. Thanks in advance, and hopefully someone can help with this.
So when you go into engineering mode, does it force close when you try to select Band and then Sim 1?
Sent from my P8000 using Tapatalk
Dvalin21 said:
So when you go into engineering mode, does it force close when you try to select Band and then Sim 1?
Sent from my P8000 using Tapatalk
Click to expand...
Click to collapse
It is not closed, simply are disabled for selection. Simply these are grayed out . I do not know how to post images , but could send a screenshot .
Related
Made this from the new 80220B Vodafone DE kdz.
This is the complete LG KK 20B ROM - nothing missing or messed with.
If you follow the method below exactly, no Audio glitches, no Touchscreen problems.
You can flash SuperSU and get root if you wish - your choice.
I provide this assuming you have an understanding of the terminology used below and appreciate that any flashing activity has some risk.
I strongly advise against using any form of restore from previous backups, such as TB or Nandroid.
Once the process is complete, custom recovery will be lost.
Method:
Download both the ROM zip file linked below and SuperSU zip file (if you want root) and copy to your SD card.
You need to be already on Rooted JB or PURE CM11 with either TWRP 2.6.3.3 or 2.6.3.4 or TWRP 2.7.0.0 (nothing else).
Reboot to TWRP recovery
Wipe: System, Data, Cache. Dalvik (nothing else)
Flash the ROM zip - ignore any "FAIL" warnings.
Wipe Cache and Dalvik (nothing else)
Go to the Mount page in TWRP and select System (leave the other defaults alone)
Flash the SuperSU zip - ignore any "FAIL" warnings
Reboot
Done
Don't use AutoRec to flash TWRP - you will lose Knock code.
Alternatively - if you have flashed TWRP on another KK Stock ROM (using AutoRec), you can full wipe (not SDCard) and flash this directly without going back to JB.
Download from here:
https://mega.co.nz/#!7EB0URZI!aYN6pBx9v7duPm2IaYFS0x_QEY89f0rhR66P9WP1EUc
Hey, you mentioned in this thread that you were going to upload a flashable ROM with knockcode.
Is this what you were talking about? You don't mention Knockcode in the OP. Also at the moment I'm running Stock Kitkat, rooted and with custom recovery. Do I just go into recovery and flash this? (Assuming I have the right TWRP and I wipe Cache and Davlik) You have said its okay to be on rooted JB, just wondering if being on rooted KK changes anything.
Yes this is the latest with Knock code. It would be fine to flash from any other KitKat ROM with custom recovery. Make sure you make the correct wipes.
You forgot download link!
Also PrimaryGPT.bin is partition table so may have issues with phone storage size after flash... I could be wrong and it could be fine...
Sent from my LG-D802 using Tapatalk
ephumuris said:
Yes this is the latest with Knock code. It would be fine to flash from any other KitKat ROM with custom recovery. Make sure you make the correct wipes.
You forgot download link!
Also PrimaryGPT.bin is partition table so may have issues with phone storage size after flash... I could be wrong and it could be fine...
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
Download link on its way - uploading to G Drive this time not effing Mega.
I'm not testing this build - I don't want Voda bloat and 80220C Open is perfectly fine for me in all ways - I cannot for the life of me understand the hankering for Kock code.
Tried knock code and its awful...seems like its basically a pattern/number pin with invisible buttons...
Sent from my LG-D802 using Tapatalk
ephumuris said:
Tried knock code and its awful...seems like its basically a pattern/number pin with invisible buttons...
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
Quite! lol
I did this on request from a couple of members.
Link now live
Thanks. Personally I like knock code. It is easier to unlock while driving. . What could those two binaries do?
If anyone has a Pioneering Spirit, or the necessary cajones to try it, please report back!
You are scaring me to try it.
PrimaryGPT.bin
is for the partition( 16gb or 32gb)
and it can be excluded from the rom
albsat said:
You are scaring me to try it.
Click to expand...
Click to collapse
well... of course the 2 additional .bin files could be excluded together or one by one... or left there.
Vodafone DE have both 16GB and 32GB variants, IIRC. Which may be why those files are there. So in theory it shouldn't matter if the whole ROM is flashed.
ROM wouldn't be stock if those files were removed.
Sent from my LG-D802 using Tapatalk
ephumuris said:
ROM wouldn't be stock if those files were removed.
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
Anyone who has flashed the kdz itself would have had the 2 files anyway, and it works.
Just need some feedback from those who have downloaded my flashable ROM and flashed in its entirety.
Hi, i have a stock 80220A and AutoRec installed. Do i need to go back to JB, or i can flash dirctly?
Sent from my LG-D802 using XDA Premium 4 mobile app
hristo2000 said:
Hi, i have a stock 80220A and AutoRec installed. Do i need to go back to JB, or i can flash dirctly?
Sent from my LG-D802 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
This info is in the OP...
Wipe everything except SDCard and flash.
I will give this rom a try in the afternoon. I have a 32 gb version. Hope no bad surprises for Easter.
Hi flash this as per instruction from open. I was previously on cloudystock rom so all I did was install twrp recovery and then flash rom then flash supersu. ....Rom is running smooth on a UK d802. ... plus knock code is working as it should. But I don't particularly like it but it's working ..
Will run this rom for rest of day to see if any problems
Thanks
Sent from my LG-D802 using XDA Premium 4 mobile app
Been running rom for about 5 hours
Just installed myself too. So far so good... Later on I will report for issues, if any. Installed recovery as well... Thanks for the rom.
---------- Post added at 04:04 PM ---------- Previous post was at 03:33 PM ----------
I think I got my first issue. Double touch to waken the screen and knock code do not respond while I am charging. Don't know why.
leegreggs said:
Hi flash this as per instruction from open. I was previously on cloudystock rom so all I did was install twrp recovery and then flash rom then flash supersu. ....Rom is running smooth on a UK d802. ... plus knock code is working as it should. But I don't particularly like it but it's working ..
Will run this rom for rest of day to see if any problems
Thanks
Sent from my LG-D802 using XDA Premium 4 mobile app
Been running rom for about 5 hours
Click to expand...
Click to collapse
Thanks!
albsat said:
Just installed myself too. So far so good... Later on I will report for issues, if any. Installed recovery as well... Thanks for the rom.
---------- Post added at 04:04 PM ---------- Previous post was at 03:33 PM ----------
I think I got my first issue. Double touch to waken the screen and knock code do not respond while I am charging. Don't know why.
Click to expand...
Click to collapse
Thanks
i have s6 sprint unlocked living outside USA and using sim other than sprint. i updated my phone to MM but i am not able to use hotspot as there is no option in settings for wifi tether ... pls help
Try THIS
1619415 said:
Try THIS
Click to expand...
Click to collapse
I am also putting out (soon) a zip flash that will correct the phone for wifi hotspot and also enabling init.d support. If you are rooted, you are welcome to test it out.
Sent from my SM-G920P using Tapatalk
tdhite said:
I am also putting out (soon) a zip flash that will correct the phone for wifi hotspot and also enabling init.d support. If you are rooted, you are welcome to test it out.
Sent from my SM-G920P using Tapatalk
Click to expand...
Click to collapse
Your old one still works
1619415 said:
Your old one still works
Click to expand...
Click to collapse
Yea, but init.d support is needed in stock ROM so it can do its work every boot to make sure it sticks. Besides, nice to have busybox support while we hack up some base setups on the way to real Roms.
Sent from my SM-G920P using Tapatalk
tdhite said:
Yea, but init.d support is needed in stock ROM so it can do its work every boot to make sure it sticks. Besides, nice to have busybox support while we hack up some base setups on the way to real Roms.
Sent from my SM-G920P using Tapatalk
Click to expand...
Click to collapse
Kernel Auditor has init.d emulation that's what I'm using, I just copied the code from the script and put it in
tdhite said:
I am also putting out (soon) a zip flash that will correct the phone for wifi hotspot and also enabling init.d support. If you are rooted, you are welcome to test it out.
Sent from my SM-G920P using Tapatalk
Click to expand...
Click to collapse
Thank you, i will wait for the zip file ☺
tdhite said:
Yea, but init.d support is needed in stock ROM so it can do its work every boot to make sure it sticks. Besides, nice to have busybox support while we hack up some base setups on the way to real Roms.
Sent from my SM-G920P using Tapatalk
Click to expand...
Click to collapse
Are you just going to make a kernel?
1619415 said:
Are you just going to make a kernel?
Click to expand...
Click to collapse
Yes, working on that. But the flash needs no kernel update (it modifies /init.rc to inject init.d support into stock or other roms missing init.d support).
It's up: http://forum.xda-developers.com/showpost.php?p=65864177&postcount=8
For kernels, I will use the same basic model, inject the kernel and any necessary init.rc support into the existing boot.img, not require a complete boot.img load. I also dislike modifying start scripts in /system/etc to try to inject init.d support because /init.rc can do it much easier and more controllably.
You are welcome to look at the flash in the above post to see how the tools in the "tools" directory perform boot.img extraction, explosion, fixup, then repack if that's not familiar. Only diff with a kernel is to replace the zImage with the custom kernel in the repack command. Makes the flash much smaller since I don't have to carry the ramdisk just for a kernel update.
tdhite said:
Yes, working on that. But the flash needs no kernel update (it modifies /init.rc to inject init.d support into stock or other roms missing init.d support).
It's up: http://forum.xda-developers.com/showpost.php?p=65864177&postcount=8
For kernels, I will use the same basic model, inject the kernel and any necessary init.rc support into the existing boot.img, not require a complete boot.img load. I also dislike modifying start scripts in /system/etc to try to inject init.d support because /init.rc can do it much easier and more controllably.
You are welcome to look at the flash in the above post to see how the tools in the "tools" directory perform boot.img extraction, explosion, fixup, then repack if that's not familiar. Only diff with a kernel is to replace the zImage with the custom kernel in the repack command. Makes the flash much smaller since I don't have to carry the ramdisk just for a kernel update.
Click to expand...
Click to collapse
I'll check it out later, thanks man:good:
tdhite said:
Yes, working on that. But the flash needs no kernel update (it modifies /init.rc to inject init.d support into stock or other roms missing init.d support).
It's up: http://forum.xda-developers.com/showpost.php?p=65864177&postcount=8
For kernels, I will use the same basic model, inject the kernel and any necessary init.rc support into the existing boot.img, not require a complete boot.img load. I also dislike modifying start scripts in /system/etc to try to inject init.d support because /init.rc can do it much easier and more controllably.
You are welcome to look at the flash in the above post to see how the tools in the "tools" directory perform boot.img extraction, explosion, fixup, then repack if that's not familiar. Only diff with a kernel is to replace the zImage with the custom kernel in the repack command. Makes the flash much smaller since I don't have to carry the ramdisk just for a kernel update.
Click to expand...
Click to collapse
Dude, i tried both the files, installed from twrp but none of them worked still no hotspot...
On lollipop i had no such issue of hotspot.
Screenshot
omar_31091 said:
Dude, i tried both the files, installed from twrp but none of them worked still no hotspot...
On lollipop i had no such issue of hotspot.
Click to expand...
Click to collapse
Screenshot
omar_31091 said:
Dude, i tried both the files, installed from twrp but none of them worked still no hotspot...
On lollipop i had no such issue of hotspot.
Click to expand...
Click to collapse
Are you rooted? Please attach the file at /data/local/tmp/tdh-hotspot.log so i can see what it is doing. On your phone.
Here is what my OTA had after flashing the mod -- hotspot is there.
Sent from my SM-G920P using Tapatalk
Yes ..
tdhite said:
Are you rooted? Please attach the file at /data/local/tmp/tdh-hotspot.log so i can see what it is doing. On your phone.
Here is what my OTA had after flashing the mod -- hotspot is there.
Sent from my SM-G920P using Tapatalk
Click to expand...
Click to collapse
Yes, i am rooted
Ok, thinking the db update might be too late in the boot process for the settings app to pick it up.
Can you reboot and resend that log file and also check settings again?
Sent from my SM-G920P using Tapatalk
tdhite said:
Ok, thinking the db update might be too late in the boot process for the settings app to pick it up.
Can you reboot and resend that log file and also check settings again?
Sent from my SM-G920P using Tapatalk
Click to expand...
Click to collapse
I installed it again restarted 2-3 times nothing has change in the settings, maybe i should wait for the custom rom to come....
I just rooted my HTC 10 and installed Xposed and got the Youtube Adaway Module. My previous phone was a Z3 where I had used GravityBox which ran fine. Since this is my first HTC device will the GravityBox MM work for this device or is there an alternative besides GravityBox.
Thanks Again.
As I remember GravityBox is programmed to run on and with AOSP based ROMs. Now when it comes to HTC, stock ROMs aren't AOSP based. I never used it myself though and I'm a long time HTC user. If you want you can try it if course, but should perform a backup prior to doing so.
Sent from my HTC 10 using XDA Labs
HTCNerdYoda said:
As I remember GravityBox is programmed to run on and with AOSP based ROMs. Now when it comes to HTC, stock ROMs aren't AOSP based. I never used it myself though and I'm a long time HTC user. If you want you can try it if course, but should perform a backup prior to doing so.
Sent from my HTC 10 using XDA Labs
Click to expand...
Click to collapse
Just tried and it works, only needed GravityBox to show the AM/PM and change the battery icons. Can't say about the other features on it as I only needed these two functions. Also got Xposed working with greenify, and Youtube Adblock. Looks like I am good to go for a while!
Sounds as if. Have fun with your new 10!
Sent from my HTC 10 using XDA Labs
Most GB features work. Lock screen features don't due to a non AOSP lock screen.
Adaway works.
Wish we'd get Sense Toolbox. Missing my secure lock screen.
Sent from my HTC 10 using Tapatalk
serophia said:
I just rooted my HTC 10 and installed Xposed and got the Youtube Adaway Module. My previous phone was a Z3 where I had used GravityBox which ran fine. Since this is my first HTC device will the GravityBox MM work for this device or is there an alternative besides GravityBox.
Thanks Again.
Click to expand...
Click to collapse
Which exact framework did you use? Thanks
Swarai said:
Which exact framework did you use? Thanks
Click to expand...
Click to collapse
Use the most recent version 84, sdk23 for arm64
Sent from my HTC 10 using Tapatalk
datafoo said:
Use the most recent version 84, sdk23 for arm64
Sent from my HTC 10 using Tapatalk
Click to expand...
Click to collapse
S-off?
Swarai said:
S-off?
Click to expand...
Click to collapse
We're talking about xposed and not s-off.
They're not related.
datafoo said:
We're talking about xposed and not s-off.
They're not related.
Click to expand...
Click to collapse
Okay thanks... I just flashed v84 sdk23 arm64 and it gave me "Updater process ended with ERROR: 1 what did you do to get your xposed working? thank you
first off, I mean this the best way possible. You need to be both more clear and more complete in your posts and questions. I could (and many would) very much give you a hard time but will try to help you.
1. If I'm not mistaken, that is a TWRP error. You can do a forum or google search and you'll find many threads about it with options.
2. Post the TWRP log so we can see what happend, or take a screenshot so we can see exactly what the output text on the screen was before the error.
3. Are you using TWRP? I assume so if you're on an HTC 10.
4. I simply flashed the proper exposed module in TWRP.
Long story short way too many variables to simply answer your question. You could wipe the cache and reboot into recovery, re copy the .zip to your SD or adb push it over. and reflash
datafoo said:
first off, I mean this the best way possible. You need to be both more clear and more complete in your posts and questions. I could (and many would) very much give you a hard time but will try to help you.
1. If I'm not mistaken, that is a TWRP error. You can do a forum or google search and you'll find many threads about it with options.
2. Post the TWRP log so we can see what happend, or take a screenshot so we can see exactly what the output text on the screen was before the error.
3. Are you using TWRP? I assume so if you're on an HTC 10.
4. I simply flashed the proper exposed module in TWRP.
Long story short way too many variables to simply answer your question. You could wipe the cache and reboot into recovery, re copy the .zip to your SD or adb push it over. and reflash
Click to expand...
Click to collapse
Yes, I am using TWRP3.0.2.2. When I flash xposed v84 sdk23 arm64 I get what you seen in the photo. When I open xposed installer (V 3.0 alpha4) I get "The latest version of xposed is currently not active". Though I'm still searching I still cannot find what my particular problem is. I hope these attachemnts can help. Thank you
Swarai said:
Yes, I am using TWRP3.0.2.2. When I flash xposed v84 sdk23 arm64 I get what you seen in the photo. When I open xposed installer (V 3.0 alpha4) I get "The latest version of xposed is currently not active". Though I'm still searching I still cannot find what my particular problem is. I hope these attachemnts can help. Thank you
Click to expand...
Click to collapse
If you look at the screenshot it tells you exactly what the problem is. Did you even read it?
Tell us what it says directly before the error?
"system mounted as read only file system" - you didn't mount as read/write. You have to mount R/W for SU and anything like this you're going to flash.
Try again, this time set the system to mount as R/W and be sure to read and watch what you're doing.
People are here to help but the trade-off is you must make efforts and not solely rely on others to solve your problems.
Sent from my HTC 10 using Tapatalk
datafoo said:
Most GB features work.
Click to expand...
Click to collapse
@datafoo Do you happen to know if the long press volume buttons to change tracks mod works from GB on the stock rom? TIA!
Sent from my HTC 10 using XDA-Developers mobile app
VolcanicSkunk said:
@datafoo Do you happen to know if the long press volume buttons to change tracks mod works from GB on the stock rom? TIA!
Sent from my HTC 10 using XDA-Developers mobile app
Click to expand...
Click to collapse
Just tested and it did not work for me.
datafoo said:
Just tested and it did not work for me.
Click to expand...
Click to collapse
Thanks so much!
Sent from my HTC 10 using XDA-Developers mobile app
im trying to get my Xxposed installed as well, and when trying to flash the v84 sdk23 arm64, It throws no errors, and immediately reboots TWRP? Any tips or anyone else seen the same? Thanks
datafoo said:
Just tested and it did not work for me.
Click to expand...
Click to collapse
VolcanicSkunk said:
Thanks so much!
Click to expand...
Click to collapse
Xposed additions worked though! It's a great module
Hello, Is anyone doing anything special to get Xposed to work? It says it's installed and active but no modules work.. Im stock rooted if that helps
Sent from my 2PS64 using XDA-Developers mobile app
l1ttl3z said:
Hello, Is anyone doing anything special to get Xposed to work? It says it's installed and active but no modules work.. Im stock rooted if that helps
Sent from my 2PS64 using XDA-Developers mobile app
Click to expand...
Click to collapse
Did you mount system in TWRP before flashing the SDK? That's what I didnt do, then after I did, all was well
Sent from my HTC6545LVW using Tapatalk
Here's a fairly simple fix to a lingering issue that affected the VZW m9. The fix came about during a discussion with the repair efforts @beaups made on one of the many phones that either end up without service or dead in his hands. Guess you could say this was a lemons to lemonade moment. The key to this was the realization that unlike the m8, the stock recovery on the m9 forward NO LONGER resets the golden nv radion settings. This process will do just that....
Remove volte from account. (If already enabled).
Then latest ruu and factory reset
Run this fastboot commands while booted to the white bootloader screen. For the HTC 10 remove the _ from the modem name.
fastboot erase modem_st1
fastboot erase modem_st2
Then reboot and try volte activation.
Thanks for this, will be testing out once i have the chance to go through the process.
Hey gang-
Just wanted to drop a note that i'm moving on. As such, I have requested my threads to be closed as I won't be around to support them much anymore. Any download links (if applicable) will also be removed shortly as well.
Thanks and peace out.
@dottat thanks for reopening the thread and I know you don't offer much support but could you shed some light on the details on how to remove Volte from your account and if you can flash custom ruu vs going back to stock and flashing stock ruu with stock recovery.
Sent using Tapatalk
I did the steps and I get "We encountered a problem activating Advanced Calling 1.0. Please try again later." Any ideas @dottat?
EDIT: Went to my account and enabled it on VZW. Rebooted my device and it was enabled on my device. Awesome!
Flyhalf205 said:
I did the steps and I get "We encountered a problem activating Advanced Calling 1.0. Please try again later." Any ideas @dottat?
EDIT: Went to my account and enabled it on VZW. Rebooted my device and it was enabled on my device. Awesome!
Click to expand...
Click to collapse
How did you deactivate it? Did you flash custom ruu or stock
Sent using Tapatalk
Tommydorns said:
How did you deactivate it? Did you flash custom ruu or stock
Sent using Tapatalk
Click to expand...
Click to collapse
I deactivated using the MyVerizon app. Once loaded up just turn deactivate the feature.
Flyhalf205 said:
I deactivated using the MyVerizon app. Once loaded up just turn deactivate the feature.
Click to expand...
Click to collapse
OK. Thank you what about the ruu which one did you flash? Are you using the new venom rom
Sent using Tapatalk
Tommydorns said:
@dottat thanks for reopening the thread and I know you don't offer much support but could you shed some light on the details on how to remove Volte from your account and if you can flash custom ruu vs going back to stock and flashing stock ruu with stock recovery.
Sent using Tapatalk
Click to expand...
Click to collapse
The basic premise of this fix has nothing to do with stock recovery. It's actually about doing what stock recovery USED to do for us. It used to reset nv radio info by wiping the modems during a factory reset. It no longer does so manually wiping them does the same thing. You probably could do it without RUU'ing as long as you know you are on vzw firmware/radios only.
Tommydorns said:
OK. Thank you what about the ruu which one did you flash? Are you using the new venom rom
Sent using Tapatalk
Click to expand...
Click to collapse
I used the only one that is available right now. I use my own stock rom.
dottat said:
The basic premise of this fix has nothing to do with stock recovery. It's actually about doing what stock recovery USED to do for us. It used to reset nv radio info by wiping the modems during a factory reset. It no longer does so manually wiping them does the same thing. You probably could do it without RUU'ing as long as you know you are on vzw firmware/radios only.
Click to expand...
Click to collapse
Thank you for the clarification. I thought I had to go back to stock rom, that's why I thought stock recovery. So as long as I have Verizon firmware / radios I can those fast boot flash those commands on Viper 5.0 after removing HD voice from my plan than reactive it after the commands ...
Sent using Tapatalk
Tommydorns said:
Thank you for the clarification. I thought I had to go back to stock rom, that's why I thought stock recovery. So as long as I have Verizon firmware / radios I can those fast boot flash those commands on Viper 5.0 after removing HD voice from my plan than reactive it after the commands ...
Sent using Tapatalk
Click to expand...
Click to collapse
Can't hurt it...
dottat said:
Can't hurt it...
Click to expand...
Click to collapse
OK... After setting up adb and fastboot, deactivating HD voice, putting the phone in Download Mode, making sure fastboot works by testing the reboot command. I tried those commands and it's basically saying that "erase" is not a valid command for modem_st1 and modem_st2 in CMD. Rebooted and reactivated HD voice on plan and phone and trying and it's saying I don't have a Verizon SIM on the phone, (It was saying this before) so I reboot to get data working again. I'm still on Viper 5.0. I did flash the Marshmellow RUU before flashing 4.3 back in February. Could I have lost a radio or something. @hallstevenson did you ever try it and get it to work?
Sent using Tapatalk
Tommydorns said:
OK... After setting up adb and fastboot, deactivating HD voice, putting the phone in Download Mode, making sure fastboot works by testing the reboot command. I tried those commands and it's basically saying that "erase" is not a valid command for modem_st1 and modem_st2 in CMD. Rebooted and reactivated HD voice on plan and phone and trying and it's saying I don't have a Verizon SIM on the phone, (It was saying this before) so I reboot to get data working again. I'm still on Viper 5.0. I did flash the Marshmellow RUU before flashing 4.3 back in February. Could I have lost a radio or something. @hallstevenson did you ever try it and get it to work?
Sent using Tapatalk
Click to expand...
Click to collapse
Take away the _ on the modem name
Sent from my HTC6545LVW using Tapatalk
dottat said:
Take away the _ on the modem name
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
Thank you for the help.. It's keeps telling me failure, erase st1 is not supported. It will also say partition table does not exist. Ive verified I do have the corrected radio and firmware. I've tried both commands with modemst1 and modem_st1 with the same failure message in CMD.
Sent using Tapatalk
Tommydorns said:
Thank you for the help.. It's keeps telling me failure, erase st1 is not supported. It will also say partition table does not exist. Ive verified I do have the corrected radio and firmware. I've tried both commands with modemst1 and modem_st1 with the same failure message in CMD.
Sent using Tapatalk
Click to expand...
Click to collapse
In bootloader or download mode?
Sent from my HTC6545LVW using Tapatalk
Both. It doesn't have a fastboot where it says fastboot mode like on previous devices so I take it you use download mode. So I tried it in both. fastboot reboot command works in both modes.
Sent using Tapatalk
Tommydorns said:
Both. It doesn't have a fastboot where it says fastboot mode like on previous devices so I take it you use download mode. So I tried it in both. fastboot reboot command works in both modes.
Sent using Tapatalk
Click to expand...
Click to collapse
You are doing it wrong.
Sent from my HTC6545LVW using Tapatalk
Oh Ok, what am I doing wrong? I would love to get this to work. Thank you for your help.
Sent using Tapatalk
dottat said:
You are doing it wrong.
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
OK, these are my steps, USB debugging enabled on Dev Options. Disabled HD Voice from My Verizon go into bootloader hook phone to PC type in CMD Those commands it says FAILED (remote: Partition modest 2 erase not supported) I've also typed in fastboot oem rebootRUU which it takes me to a blank screen HTC logo on it and gives me a warning then I typed those commands still same Failed message in CMD. Is there something I'm missing. Haven't had anybody come out and say they were successful. Only thing I haven't done it go all to stock RUU bit I have the latest radios and firmware so I don't know
Sent using Tapatalk
As some of you certainly know, Magisk manager has capability of rooting system.
The needed thing is kernel image, boot.img, very the same which seats in the device.
If the stock ROM was available to download then the kernel image would be possible to obtain by pulling it out from the ROM file (preferably zip).
So where to get the stock ROM file, please?
Sent from my LM-Q610.FG using Tapatalk
plejadrian said:
As some of you certainly know, Magisk manager has capability of rooting system.
The needed thing is kernel image, boot.img, very the same which seats in the device.
If the stock ROM was available to download then the kernel image would be possible to obtain by pulling it out from the ROM file (preferably zip).
So where to get the stock ROM file, please?
Sent from my LM-Q610.FG using Tapatalk
Click to expand...
Click to collapse
Here is the kdz file for tmo variant that @jlink38 linked here.
I never had any luck extracting it.
kc6wke said:
I never had any luck extracting it.
Click to expand...
Click to collapse
And how have you tried?
Sent from my LM-Q610.FG using Tapatalk
plejadrian said:
And how have you tried?
Sent from my LM-Q610.FG using Tapatalk
Click to expand...
Click to collapse
LGExtract.exe
Here is a link to the Q610TA10K firmware
I'm thinking about the LG tablet I had. No root for it so someone did the Magisk thing also. Tablet was easily unlocked allowing us to put the image in place.
For the Q7, once a boot image is modified how would you get it in place on a running ROM? Far as I know the device is still locked down.
LG G3 D851, AospExtended v5.7 ROM, NanoDroid-microG (NoGapps), MultiROM, XDA Legacy
marcdw said:
I'm thinking about the LG tablet I had. No root for it so someone did the Magisk thing also. Tablet was easily unlocked allowing us to put the image in place.
For the Q7, once a boot image is modified how would you get it in place on a running ROM? Far as I know the device is still locked down.
LG G3 D851, AospExtended v5.7 ROM, NanoDroid-microG (NoGapps), MultiROM, XDA Legacy
Click to expand...
Click to collapse
Yes, it is locked. Unless there is a way to flash it the way you flash the kdz file, I think we are Sol.
I gave up on root on this device.
kc6wke said:
Yes, it is locked. Unless there is a way to flash it the way you flash the kdz file, I think we are Sol.
I gave up on root on this device.
Click to expand...
Click to collapse
My LG Q7+ has this developer option
knusto said:
My LG Q7+ has this developer option
Click to expand...
Click to collapse
So does every other phone. The fact is the bootloader is not unlockable.
kc6wke said:
LGExtract.exe
Here is a link to the Q610TA10K firmware
Click to expand...
Click to collapse
So doesn't LGextract.exe work, or what?
BTW. We're talking on ROOTing the device, not unlocking.
We can root it without unlocking, I've a Huawei tablet with MediaTek too and it has been rooted by KingoRoot without touching anything else.
Sent from my LM-Q610.FG using Tapatalk
plejadrian said:
So doesn't LGextract.exe work, or what?
BTW. We're talking on ROOTing the device, not unlocking.
We can root it without unlocking, I've a Huawei tablet with MediaTek too and it has been rooted by KingoRoot without touching anything else.
Sent from my LM-Q610.FG using Tapatalk
Click to expand...
Click to collapse
LGextract.exe did not work for me. Even If the boot img could be modified, as @marcdw stated "how would you get it in place on a running ROM?"
Without unlocking the bootloader this is not possible.
Kingroot, kingoroot will not work on this device atm, I've tried every method possible that's why I gave up on root on this device.
Maybe some day it will but I doubt it.
kc6wke said:
LGextract.exe did not work for me. Even If the boot img could be modified, as @marcdw stated "how would you get it in place on a running ROM?"
Without unlocking the bootloader this is not possible.
Kingroot, kingoroot will not work on this device atm, I've tried every method possible that's why I gave up on root on this device.
Maybe some day it will but I doubt it.
Click to expand...
Click to collapse
I had this problem with my q7+ I bought in Brazil where I live, it did not have Norwegian language, and I'm Norwegian. So I had to use an app; custom locale. This app needs root, but I was able to give right permission using ADB, so now I have Norwegian language. (Or any language I want).
kc6wke said:
LGExtract.exe
Here is a link to the Q610TA10K firmware
Click to expand...
Click to collapse
Excuse me, where to get LGExtract.exe from?
Why haven't you managed to extract boot.img? What were the errors like?
Sent from my LM-Q610.EMW using Tapatalk
plejadrian said:
Excuse me, where to get LGExtract.exe from?
Why haven't you managed to extract boot.img? What were the errors like?
Sent from my LM-Q610.EMW using Tapatalk
Click to expand...
Click to collapse
Here
It says file is corrupt.
good luck
Please, post to this thread and describe the problem. Maybe someone knowledgeable join the effort
Sent from my LM-Q610.EMW using Tapatalk
plejadrian said:
Please, post to this thread and describe the problem. Maybe someone knowledgeable join the effort
Sent from my LM-Q610.EMW using Tapatalk
Click to expand...
Click to collapse
Sorry, not gonna kick a dead horse.
Even if the boot img could be modified with magisk, there still is no way to install to device without unlocked bootloader.
And have you refferred to this method ?
What do you think of these instructions:
https://www.techdroidtips.com/lg-q7-2018-unlock-bootloader/
especially this:
In conclusion, Android versions later than lollipop come with an option of OEM Unlock in the developer options. So, its quite easy to unlock the bootloader on any latest smartphone devices. And Still, some of the smartphones may not come with this option. Hence, in order to unlock the bootloader, you need to manually do it via PC.
Click to expand...
Click to collapse
There is the option OEM Unlock in this device, so?
Sent from my LM-Q610.EMW using Tapatalk
plejadrian said:
And have you refferred to this method ?
What do you think of these instructions:
https://www.techdroidtips.com/lg-q7-2018-unlock-bootloader/
especially this:
There is the option OEM Unlock in this device, so?
Click to expand...
Click to collapse
LG Q7+ is not on the list of supported devices from LG.
And mine is LM-Q610.EMW, it isn't "plus", so has it a potential?
Sent from my LM-Q610.EMW using Tapatalk
plejadrian said:
And mine is LM-Q610.EMW, it isn't "plus", so has it a potential?
Click to expand...
Click to collapse
Not on the list
However this list is extremely scarce. It seems something is wrong with it.
This is why wanted to try. The first obstacle is it is impossible to reboot into bootloader (which is needed to obtain device ID). When the command "adb reboot bootloader" is executed then the phone simply reboots into system again. (Attention: when "adb reboot recovery" is executed then it does Factory Reset!)
How to make it boot into bootloader? Is there any keys combination for it?
Wysłane z mojego LM-Q610.EMW przy użyciu Tapatalka