Database Users

Root Status

Well, I've asked a mod to lock the other root status thread. It was getting kind of out of hand. After about page 80, people stopped looking at what we had done so far, and trying to help by putting ideas out that already failed.
This is what we know:
Fastboot is locked down in everything but oem-78 mode. You can get to this mode by typing "reboot oem-78" at an adb shell. Fastboot is essentially unlocked, allowing fastboot boot and fastboot flash, only the .img images we try to boot or flash NEED TO BE SIGNED.
Goldcards no longer allow non signed firmware to be loaded, only signed firmware with a different SID.
All known flashing methods require the .img files to be signed by HTC. We do not have the privatekey, nor do we have any way to decrypt the key as it is RSA. Meaning this is a NO GO.
All previous known exploits (asroot2, g1 telnetd, DROID update.zip method) have been patched. They won't work. And there isn't a way around this.
All the partitions except /data are mounted as read only. Meaning, without root access, there is NO way to modify them. In the init.rc file, they are mounted rw, and directly after that mounted ro. We can read and write to /data as we wish, but NOTHING important is here.
The only folder anything can run as root out of is /system/bin. Every other partition is mounted with the nosuid option, meaning code CANNOT be run as root. Simple enough. We can't run anything as the user root, or the group root.
Lets try to stay a little more on topic this time. Please don't let this become another 40 pages of complete crap. And please keep this thread about root access, any other problems should be posted in the appropriate forum.
Thanks, and lets get this root done!

I'm currently comparing superboot.img in a hex editor to the vanilla boot.img for that phone so I can better understand what he did, and how. I'll see what I can turn up, maybe we can make one for the eris.
EDIT: It seems it's not going to be so easy. There's a lot of things changed. It appears he changed something at the top of the file right after the header, and then there is some sort of (SHA1?) hash right below that, but I don't know what it's calculated from. This is beyond my skills at the moment, I think.

Are any of the fields changed from the original boot.img show up in our boot.img? Chance of searching for each field in our img and replacing with possibly what he did?

is it possible that the guy who made superboot has htc signature, or somehow decrypted it???? 8-O

Yes I guess anything is possable but I think their is a better chance of monkeys flying out of my butt.

well i guess it was time to lock the other thread as some people could not play nice..... so i guess we will use this one now..... next idea anyone, and i am guessing jman will no longer be joing us, so it looks like we are on our own.

im ready to get this done what have we got so far?

About 140 pages of failed attempts.

well i know that much i have been sitting back following from the begining now im ready to get my hands dirty, though i have no clue what im doing

binny1007 said:
well i guess it was time to lock the other thread as some people could not play nice..... so i guess we will use this one now..... next idea anyone, and i am guessing jman will no longer be joing us, so it looks like we are on our own.
Click to expand...
Click to collapse
Ok, I missed something I think. Thats what I get for not refreshing every 10 seconds What happened to jman? Or is it better off that I not ask

punk.kaos said:
Ok, I missed something I think. Thats what I get for not refreshing every 10 seconds What happened to jman? Or is it better off that I not ask
Click to expand...
Click to collapse
I don't think I'll be following these threads anymore. I try to help you guys, but in the end some of you just don't appreciate the help.
I don't claim to be an expert, and I never promised anybody that I could root their phone. I simply have information to share that I think has brought you guys to a greater understanding of your phones and the Android system. Most of you are thankful, but I really don't need to be attacked personally in these threads that don't even have anything to do with my phone.
I'd like to thank the moderator for locking down the other forum, I'd also like to thank whichever moderator deleted the message that was quite insulting to me.... I only happened to see it because it came into my email. Yes, I subscribed to the thread via email to try to keep up with you guys and offer any help I could as quickly as I could.
I'm sorry guys, I wish you luck, but I just don't need to be berated in open forum like that for trying to help the Eris owners out, so I won't be keeping up with your rooting efforts.
There are a couple of you that have been very appreciative, and please feel free to PM me.

Thanks jman and I understand, if I was in your shoes I would do the same and I reported that post almost right after it was posted hoping you would not see it. But I know for me I have a greater understanding of my phone and like I have said before Thank you very much for your help. It's a shame to see you go but we understand.
Binny

doubt this will help, its all that htc tech support would throw up at me.
http://developer.htc.com/
contains hero and adp but nothing about eris.

jmanley69 said:
I don't think I'll be following these threads anymore. I try to help you guys, but in the end some of you just don't appreciate the help.
I don't claim to be an expert, and I never promised anybody that I could root their phone. I simply have information to share that I think has brought you guys to a greater understanding of your phones and the Android system. Most of you are thankful, but I really don't need to be attacked personally in these threads that don't even have anything to do with my phone.
I'd like to thank the moderator for locking down the other forum, I'd also like to thank whichever moderator deleted the message that was quite insulting to me.... I only happened to see it because it came into my email. Yes, I subscribed to the thread via email to try to keep up with you guys and offer any help I could as quickly as I could.
I'm sorry guys, I wish you luck, but I just don't need to be berated in open forum like that for trying to help the Eris owners out, so I won't be keeping up with your rooting efforts.
There are a couple of you that have been very appreciative, and please feel free to PM me.
Click to expand...
Click to collapse
Thanks for sticking through with us. You've been extremely helpful since day one, and I would like to say thanks and basically say what Binny said above.
I haven't had a lot of time to follow the thread, but, I too, am happy that it was locked. Hopefully the Eris owners can regroup in a day or so after we all chill out. Sigh. Fingers are still crossed for root.

Has anyone been able to actually BOOT any of the images extracted from the rom.zip via fastboot in oem-78 mode? If so, and you could post how, I might have access to an image with root access. I've tried repeated times to perform "fastboot boot recovery.img" but it sends it and then sticks on "booting..." I have moved forward with the RUU at this point, but the device never actually boots into the img.
Unfortunately, I cannot not upload the image due to my job.

Also, if anyone can help with goldcard downgrading, I might be able to downgrade to an old version with root access. My downgrade continues to fail due to the bootloader version being too high. I created the goldcard per the appropriate thread and it appeared to work as the Cell South thread indicated, but still no dice on the downgrade.

If your gold card is made right it should work.... are you putting the .zip on you gold card and renameing it PB00IMG.zip?

binny1007 said:
If your gold card is made right it should work.... are you putting the .zip on you gold card and renameing it PB00IMG.zip?
Click to expand...
Click to collapse
Yes, but it still fails with error 43, I believe. "Main version check"

Did you run the simlock option in the bootloader, and it passed

binny1007 said:
Did you run the simlock option in the bootloader, and it passed
Click to expand...
Click to collapse
Yes. Perhaps goldcard doesn't work on this device like it's supposed to.

How to do a complete system restore?

Let me apologize for being a newbie as I come from 5 years of using Windows Mobile and just got my first Tab/Android 2 weeks ago. This is all new to me.
After messing up with some system files and factory applications (like I removed stk.apk and other things) I decided to do a full hardware reset. This is something I did many times in Windows Mobile... whats bad get overwriten in ROM and whats missing gets back where it was. But is seems on this Tab this is not the case.
After the full resetthings only got dramatically worse. All the missing system apps are still missing (I thought they be "restored") and nothing works, just crashes one after the next, cant use anything. I also tried with the system off the method of pressing and holding the “Volume Up” and “Power” buttons at the same time, then after recovery screen appears navigate and select “wipe data / Factory reset” and pressing the “Home” button, but after that and the system re-starts, same thing! All bad.
Can someone please explain to me how to do a full rstore where all system files, all and everythign gets back as it was in the Tab as it was shipped? What a flippin' nightmare... Windows Mobile, I love you!
Thanks in advance.

settings/privacy/factory reset.

natious said:
settings/privacy/factory reset.
Click to expand...
Click to collapse
No no, that doesnt restore anything! All missing files dont get restored. I need a full stock ROM image and restore EVERYTHING. Thats what I dont know where to get and how to do...

VeEuzUKY said:
No no, that doesnt restore anything! All missing files dont get restored. I need a full stock ROM image and restore EVERYTHING. Thats what I dont know where to get and how to do...
Click to expand...
Click to collapse
Yeh i realized that after reading your post properly sorry man, i guess you can just flash one of roms found here, like rotos or modaco's JMI, that would atlest give you a work tab till you can find a stock samsung rom
If you dont have cwm installed you can flash with odin or heidmill (sp)

natious said:
Yeh i realized that after reading your post properly sorry man, i guess you can just flash one of roms found here, like rotos or modaco's JMI, that would atlest give you a work tab till you can find a stock samsung rom
If you dont have cwm installed you can flash with odin or heidmill (sp)
Click to expand...
Click to collapse
Yeah, I enever flashed the Tab. Can U advise me on a stable "OK" ROM? Where can i find odin or heidmill and some sort of a guide to help me step-by-step? I have positively no clue what I am doing... sorry for my ignorance... I feel thoroughly stupid...

I got lucky and found this site. Hope yours is a Verizon Tab
I'm not allowed to post links. But go to google type in "galaxy tab system restore" and click on the "[How TO] Restore VZW Galaxy Tab to stock DJ11" link
It's in the droidforums. net

VeEuzUKY said:
Yeah, I enever flashed the Tab. Can U advise me on a stable "OK" ROM? Where can i find odin or heidmill and some sort of a guide to help me step-by-step? I have positively no clue what I am doing... sorry for my ignorance... I feel thoroughly stupid...
Click to expand...
Click to collapse
First of all, you need to post what "type" of Tab you have, which is generally going to be determined by your country and/or carrier.
Flashing a new Android ROM isn't a particularly complicated process, but it can seem daunting if you've not done it before - this is especially true when using Odin or Heimdall over a "recovery" based flash.
FWIW, the reason your "factory reset" didn't work is because all is essentially does it reformat the /data partition (a generalisation, but close enough for these purposes). On a stock Tab, you cannot mount /system as read/write, so you are unable to change the contents of that partition. This means that on a stock Tab, /system should never change.
However, when you root the device you give yourself the ability to remount /system as read/write and thus make changes which are not going to affected by a factory reset.
Take a look at this thread - lots of useful information there!
Regards,
Dave

foxmeister said:
First of all, you need to post what "type" of Tab you have, which is generally going to be determined by your country and/or carrier.
Flashing a new Android ROM isn't a particularly complicated process, but it can seem daunting if you've not done it before - this is especially true when using Odin or Heimdall over a "recovery" based flash.
FWIW, the reason your "factory reset" didn't work is because all is essentially does it reformat the /data partition (a generalisation, but close enough for these purposes). On a stock Tab, you cannot mount /system as read/write, so you are unable to change the contents of that partition. This means that on a stock Tab, /system should never change.
However, when you root the device you give yourself the ability to remount /system as read/write and thus make changes which are not going to affected by a factory reset.
Take a look at this thread - lots of useful information there!
Regards,
Dave
Click to expand...
Click to collapse
Thanks for the link... yes Ive seen that master thread... I just keep reading from link to link and thread to thread and all gets more complicated, I keep downloading more files and installing more stuff but in the end Im more confused and positively going no where. There is not one simple, from start to finish guideline on how to do the process of wiping all data and installing a new ROM. Ive done this endless times on many phones under WinMo, and with more or less difficulty never had any problems getting this done. But here, the more I read the more utterly chaotically confused I am.
I am yet to have anyone explain what type of Tab I have. Its GSM, I think its Euro, bought in Hong Kong. I have found out all bootloaders and stuff seem to be cleaer and I should be able to flash anything. Its a GT-P1000 and Baseband P1000ZHJJ1. This is all I know.

VeEuzUKY said:
Thanks for the link... yes Ive seen that master thread... I just keep reading from link to link and thread to thread and all gets more complicated, I keep downloading more files and installing more stuff but in the end Im more confused and positively going no where. There is not one simple, from start to finish guideline on how to do the process of wiping all data and installing a new ROM. Ive done this endless times on many phones under WinMo, and with more or less difficulty never had any problems getting this done. But here, the more I read the more utterly chaotically confused I am.
I am yet to have anyone explain what type of Tab I have. Its GSM, I think its Euro, bought in Hong Kong. I have found out all bootloaders and stuff seem to be cleaer and I should be able to flash anything. Its a GT-P1000 and Baseband P1000ZHJJ1. This is all I know.
Click to expand...
Click to collapse
Its pretty much the same as mine then, so i recommend you use modacos kernel and rom and installing cwm
cwm - http://forum.xda-developers.com/showthread.php?t=870690
Kernel - http://forum.xda-developers.com/showthread.php?t=925760
Rom - http://forum.xda-developers.com/showthread.php?t=941423
If you have and external sd card (one that you put into the side of the tab)
You can flash the ext4 kernel via odin, its pretty simple, there will be instructions in the threads.
Are you still able to go on the market? If so download the cwm app and use that so you get the awesome recovery menu and features, you can then use it to flash a new rom and make backups that are really really easy to restore. Seeing it looks like you like to mess around with stuff i suggest it the best way to go.
Hope this helps

Ok thanks for the tips. I have finally managed to get the Tab working again and flashed it with Roto JMI Pre-Rooted Firmware v2. All seems OK at this point. Ill check the links you sent me and follow-up. Flashing Roto JMI Pre-Rooted Firmware v2 with Odin3 1.7 is easy so I hope modacos kernel and rom and installing cwm are easy as well.

A little off topic:
I just got my SGT on Friday and want to root&/flash custom ROM. Gonna definitely root soon...But thinking of holding off on the custom ROM until CM7 is stable or a nice clean Honeycomb ROM is cooked
Does ClockWorkMod require root? I know Titanium Backup does. Can't really do any "fun" things with the tab until it's rooted it seems.

S.O.S. bricked my Toshiba Thrive need a stock(or rooted) boot.img

I attempted to flash the Motorola Xoom rooted boot.img on my Thrive.
It didn't work.
I have been unable to find a stock(or rooted) version of the Thrive boot.img so I can unbrick my device.
Can someone please
1.Provide a working boot.img
or
2.Instruct me on how to extract it from an intact Thrive?
I guess its safe to assume anyone working on rooting would have a copy of it
I would really appreciate the help!
Edit: I have been looking for hours for information on how to extract the boot.img from a device like this and have been having no luck.

Can someone please help me?
I realize what I did was idiotic...
I'll never mess with anything that says "boot" again unless I really know what I'm doing.

This is why we need a dev forum!

someone with a working thrive please try this.
mmcblk0p11 is the boot partition of the atrix 4g
please replace mmcblk0p11 with the boot partition mount point of the toshiba thrive.
adb shell
su
dd if=/dev/block/mmcblk0p11 of=/mnt/sdcard-ext/boot.img
then post your boot.img here please

In the meantime, I'm getting a call back from level 2 tech Toshiba support in an hour. Trying to convince them to give me a copy of the recent firmware update. So "I can see what they changed, as there was no changelog".
Odds I succeed?

what is the exact model of the thrive?

Toshiba AT105-T1032
P/N PDA01U-00501F

lol while your at it ask for the sbk

joe ferreira said:
lol while your at it ask for the sbk
Click to expand...
Click to collapse
Hah, that would definitely make for a quick and easy root for the masses using stock recovery wouldn't it?

joe ferreira said:
someone with a working thrive please try this.
mmcblk0p11 is the boot partition of the atrix 4g
please replace mmcblk0p11 with the boot partition mount point of the toshiba thrive.
adb shell
su
dd if=/dev/block/mmcblk0p11 of=/mnt/sdcard-ext/boot.img
then post your boot.img here please
Click to expand...
Click to collapse
Someone tried this over at Thriveforums.org
here's what they said
""su" ? no root ... I get "su: permission denied""

Well, 2nd level tech support never called me back. Called back tech support and they PROMISED they'd call me back this time, in 2-3 hours.
Here's hoping this lands us an OTA update file

Natolx said:
Someone tried this over at Thriveforums.org
here's what they said
""su" ? no root ... I get "su: permission denied""
Click to expand...
Click to collapse
try superoneclick first
http://forum.xda-developers.com/showthread.php?t=803682

Natolx said:
Hah, that would definitely make for a quick and easy root for the masses using stock recovery wouldn't it?
Click to expand...
Click to collapse
I heard that the thrive comes with a unlocked bootloader?
The sbk is the boot loader and has nothing to do with root access.
with a unlocked bootloader we can root the thrive with the same fastboot flash preinstall process as the atrix.
has anyone figured out how to get to the menu for android recovery, fastboot, etc?

btw root is a part of the system.img not the boot.img
boot.img is the kernel

joe ferreira said:
I heard that the thrive comes with a unlocked bootloader?
The sbk is the boot loader and has nothing to do with root access.
with a unlocked bootloader we can root the thrive with the same fastboot flash preinstall process as the atrix.
has anyone figured out how to get to the menu for android recovery, fastboot, etc?
Click to expand...
Click to collapse
yes, that's how I bricked my tablet, by using fastboot to flash a xoom rootboot.img. Fastboot and recovery are available from simple menu by holding down power and volume up when booting up.
The fastboot is completely unlocked from the factory, you don't even have to issue an unlock command.

Did you take a look at android-dls wiki site they've got tut's for extracting the kernel, if you have access to a working thrive. I used it to retrieve my friend's phone's kernel after bricking mine during one of my first root attempts ever.
I will be getting the thrive soon (Cant wait) and will be attempting to extract the kernel out of the machine. I'll post it soon as I get it, seems to be in high demand right now. Glad to hear the bootloader comes unlocked out of the box. Hopefully you can get yours back up and running.

D3MN5PWN said:
Did you take a look at android-dls wiki site they've got tut's for extracting the kernel, if you have access to a working thrive. I used it to retrieve my friend's phone's kernel after bricking mine during one of my first root attempts ever.
I will be getting the thrive soon (Cant wait) and will be attempting to extract the kernel out of the machine. I'll post it soon as I get it, seems to be in high demand right now. Glad to hear the bootloader comes unlocked out of the box. Hopefully you can get yours back up and running.
Click to expand...
Click to collapse
Which tutorial, this one? Its the only related one I've been able to find and it doesn't mention how to pull the kernel off the device itself.
http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
Also, when are you expecting your Thrive? I have a feeling you are the only one working on this :/

Natolx said:
Which tutorial, this one? Its the only related one I've been able to find and it doesn't mention how to pull the kernel off the device itself.
Also, when are you expecting your Thrive? I have a feeling you are the only one working on this :/
Click to expand...
Click to collapse
Wed. Thurs at the latest... Well we need to get developers working on these things. I sense huge potential in this device, as I'm sure everyone else who has half a brain and picked it up did as well.
Is you recovery.img shot? or did you back it up at all? Normally you need someone to release the source for a .zip to appear even one for the stock rom. Google's taking its sweet time releasing the source codes. 3.0 was obtained through asus or was it acer... always get those two mixed up... after all. I think we may have to cool our heels till icecream comes out for developers to start doing their thing (or some big to release the source code).

D3MN5PWN said:
Wed. Thurs at the latest... Well we need to get developers working on these things. I sense huge potential in this device, as I'm sure everyone else who has half a brain and picked it up did as well.
Is you recovery.img shot? or did you back it up at all? Normally you need someone to release the source for a .zip to appear even one for the stock rom. Google's taking its sweet time releasing the source codes. 3.0 was obtained through asus or was it acer... always get those two mixed up... after all. I think we may have to cool our heels till icecream comes out for developers to start doing their thing (or some big to release the source code).
Click to expand...
Click to collapse
My recovery is fine, its just the kernel.
My level 2 tech support discussion was a mixed bag. The guy essentially said it was extremely odd that the firmware update wasn't on the website and that they hadn't even heard about it. He sent an e-mail out to his entire department to find out what's going on. Hopefully that gets sent up the pipeline and it shows up under thrive downloads on the support website.

joe ferreira said:
try superoneclick first
http://forum.xda-developers.com/showthread.php?t=803682
Click to expand...
Click to collapse
Looks like none of the oneclick roots work, someone on thriveforums posted this in response to my request.
"Sorry, I tried both the gingerbreak and psneuter versioins, neither worked.
Oh, and I also ran the "Check Drivers" and it said no issue found.
Also found z4root on theunlockr.com and tried it, appears to have hung up my Thrive."

[Q] Ideapad K1: Creating .img files from OTA

Alright, now I realize this is the Thinkpad section but there doesn't seem to be an Ideapad one. I've been out of the Android game for a very long time, and finally came back with a Lenovo K1 Ideapad.
My big issue is I don't know how to create a system.img, boot.img or recovery.img from the Canadian OTA zip on the Lenovo site so I can flash them onto my tablet. I managed to use the root tool available in the development section to root my tablet with a US firmware. However after experiencing a lot of freezing and my tablet not responding, I felt as if I should revert back to the Canadian firmware. My problem is I forgot to create backups for the previously mentioned images so I can't flash them back and restore my tablet.
If someone could please explain or even direct me to where I can learn the steps in creating them (I just installed linux because so far it seems like that would be the first step), it would be a great help. I took the img files from a different root tool and tried those, they changed the system to a chinese firmware but I at least know it works if I could get the Canadian ones. I can go back to the US one if I really wanted but what I want is to just put this thing back into its original state that it came in.
Even if someone could just post those files, it would be greatly appreciated. I've been scouring the internet for days to try and gain some enlightenment, but it isn't happening. Probably since development on this thing isn't as hyped as others.
Thank you.

I'm still stock and not rooted so I would like to know how to back up my current system before rooting .....maybe I can be of some help if I can get my sys backed up
Sent from my HTC EVO 3D X515a using XDA App

***method doesn't appear to work***

maek_it_happen said:
I'm still stock and not rooted so I would like to know how to back up my current system before rooting .....maybe I can be of some help if I can get my sys backed up
Sent from my HTC EVO 3D X515a using XDA App
Click to expand...
Click to collapse
On the K1 you cannot. Lenovo has it locked down so there's no way to back it up without root. The only way to root it is to flash it which wipes it clean. Thee ole catch 22.
Now, if you read through the leaked keys and rooting tips, they talk about fastbooting to ASUS boot.bin and then backing up before you start rooting. It definitely works to backup, but I haven't found anyone that has successfully used them to restore from and I could not get them to restore. So, in my opinion, that backup method is worthless because you cannot use them.
TD
---------- Post added at 07:53 AM ---------- Previous post was at 07:48 AM ----------
MrZombieAndMe said:
Alright, now I realize this is the Thinkpad section but there doesn't seem to be an Ideapad one. I've been out of the Android game for a very long time, and finally came back with a Lenovo K1 Ideapad.
My big issue is I don't know how to create a system.img, boot.img or recovery.img from the Canadian OTA zip on the Lenovo site so I can flash them onto my tablet. I managed to use the root tool available in the development section to root my tablet with a US firmware. However after experiencing a lot of freezing and my tablet not responding, I felt as if I should revert back to the Canadian firmware. My problem is I forgot to create backups for the previously mentioned images so I can't flash them back and restore my tablet.
If someone could please explain or even direct me to where I can learn the steps in creating them (I just installed linux because so far it seems like that would be the first step), it would be a great help. I took the img files from a different root tool and tried those, they changed the system to a chinese firmware but I at least know it works if I could get the Canadian ones. I can go back to the US one if I really wanted but what I want is to just put this thing back into its original state that it came in.
Even if someone could just post those files, it would be greatly appreciated. I've been scouring the internet for days to try and gain some enlightenment, but it isn't happening. Probably since development on this thing isn't as hyped as others.
Thank you.
Click to expand...
Click to collapse
In Linux, you just mount system.img and then read and write to it. If you are using Windows then you can download drivers that let you mount the the system.img as a disk drive.
I use Windows for everything, no need to use Linux. For cooking, Google Cygwin which runs on Windows and is kitchen for 'cooking ROMS'.
TD

Alright thanks timmyDean for the answers. I noticed you uploaded a tool to revert back to stock. So I was thinking of giving it a shot. I'm just hoping it won't be too much of an issue if I install the US rom. I'm thinking it won't let me use OTA updates since I'm in Canada, but I can probably just do the manual method for installing the updates. The box for my K1 says US, and we usually get the same pieces of hardware as the states with just a modified OS.
Hoping this works, fingers crossed

MrZombieAndMe said:
Alright thanks timmyDean for the answers. I noticed you uploaded a tool to revert back to stock. So I was thinking of giving it a shot. I'm just hoping it won't be too much of an issue if I install the US rom. I'm thinking it won't let me use OTA updates since I'm in Canada, but I can probably just do the manual method for installing the updates. The box for my K1 says US, and we usually get the same pieces of hardware as the states with just a modified OS.
Hoping this works, fingers crossed
Click to expand...
Click to collapse
I loaded a tool to goto CA stock too and already tested it for you.

Thank you so much man, I just used your tool. Flashed the stock US, then put my CA one and it worked like a charm. You've honestly made me so happy.
Too bad the K1 in Canada is still at 3.1 and doesn't look like it'll get 3.2 (fingers crossed we for sure get ICS).
Anyway I am very thankful. I've looked over the tools but I don't see a lock thread option, hopefully a mod will do so promptly.

What LS997-compatible ROM contains *all* working LG Stock Apps?

So the whole reason I rooted this damn phone was to be able to install working stock apps. Not just the Music and Gallery apps either--ALL THE LG APPS. Which LS997-compatible 100%-working ROM can I flash and get them all, if any? I keep hearing one exists, but no one bothers sharing that info and when I search I find nothing.

Really? No one?

bgibson72 said:
Really? No one?
Click to expand...
Click to collapse
Look in the development section it's like the 5th one down has ls997 in the title

@bgibson72
Im the only person developing a STOCK LS997 rom currently.. It contains the LG base apps and all the removed ones that we didnt get shipped with out model . Includes a ton of extras as well, alternatively we have 3 or 4 aosp roms you can use, but make sure you use twrp and backup your efs before flashing as it tends to jumble your programming up and cause issues. Otherwise you can flash the stock rom the Dev who provided the dirty santa unlock method.
Theres a good bit of info here to locate everything you need to have a awesome experience with the LG V20!
My link
https://forum.xda-developers.com/v20/development/rom-ls997-stock-debloated-su-goodies-t3531923
READ THE ENTIRE FIRST 3 POSTS!!! A LOT OF TIME WENT INTO THIS TO CLEAR UP ANY CONFUSION!
I also itemized a list of 15 or so mods and add-ons that we can use to increase our enjoyment with perspective links to their home locations and the devs that built and maintain them.

jerrycoffman45 said:
Look in the development section it's like the 5th one down has ls997 in the title
Click to expand...
Click to collapse
This one?
{ROMS}[LS997] Stock-ish Magisk+3minit+ModControl 3/10/17
Other than DirtySanta, this is the only other one with LS997 in the title on that page. I'll give it a shot, and thanks for answering.

Team DevDigitel said:
@bgibson72
Im the only person developing a STOCK LS997 rom currently.. It contains the LG base apps and all the removed ones that we didnt get shipped with out model . Includes a ton of extras as well, alternatively we have 3 or 4 aosp roms you can use, but make sure you use twrp and backup your efs before flashing as it tends to jumble your programming up and cause issues. Otherwise you can flash the stock rom the Dev who provided the dirty santa unlock method.
Theres a good bit of info here to locate everything you need to have a awesome experience with the LG V20!
My link
https://forum.xda-developers.com/v20/development/rom-ls997-stock-debloated-su-goodies-t3531923
READ THE ENTIRE FIRST 3 POSTS!!! A LOT OF TIME WENT INTO THIS TO CLEAR UP ANY CONFUSION!
I also itemized a list of 15 or so mods and add-ons that we can use to increase our enjoyment with perspective links to their home locations and the devs that built and maintain them.
Click to expand...
Click to collapse
Hey thanks--I was fairly sure this was the ROM in question. Thank you for providing this! I was hesitant to flash because I'm always a little skeptical about the amount of help I'll get should I get stuck. I'm not exactly a noob at this, but I have plenty to learn. It looks like you've done a lot of work to provide a positive experience, so I'll give it a shot and see how it goes. I promise to read and re-read the instructions on the first 3 posts, and to NOT bother you with questions that have already been addressed in the thread. . Thanks!!

bgibson72 said:
Hey thanks--I was fairly sure this was the ROM in question. Thank you for providing this! I was hesitant to flash because I'm always a little skeptical about the amount of help I'll get should I get stuck. I'm not exactly a noob at this, but I have plenty to learn. It looks like you've done a lot of work to provide a positive experience, so I'll give it a shot and see how it goes. I promise to read and re-read the instructions on the first 3 posts, and to NOT bother you with questions that have already been addressed in the thread. . Thanks!!
Click to expand...
Click to collapse
if you made it through dirty santa the rest should be cake. 99% of the issues i covered for people were
after going to AOSP and not having a backup of their programing info in their efs and having to find a way to
manually go in and fix each fd up piece.
The other is being on older software and downloading a OTA and rebooting with it in your internal storage.
This one causes a endless boot loop into twrp, so be advised to delete the update if your on older software or be prepared to
hit my post # 3 for fixes and be near a pc as you need to fastboot erase the fota and misc directories to resolve the boot loop. A twrp wipe will not fix it and restores etc wont either lol.
Otherwise theres now a lil over 100 pages of chatting and troubleshooting, fixes and things that have gone on, and mostly its all outdated as ive provided the fixes for 99% of everything in the latest version 7.5
Just be prepared to take 15-20 minutes for the phone to boot up the 1st time. My rom is deodexed, and the 1st boot is doing 298 things before you get to the optimization part. There is not boot animations as the phone will always have the static screen issue on reboots so i went ahead a placed a disabled command there to just save time/batt life. The setup wizard is stripped and only there to give you the notice its done booting and time to get to playing around.
Magisk is kinda finicy being its systemless design. It takes some time to get used to it, and be aware that some older apps that dont support exotic root or systemless root may not request root and not fully work. Titanium backup is one i know is getting attacked by googles app scanning and needs to have that turned off before it will work, most of my apps have a option to set "force root" so it asks for a root request regardless if it understands MagiskSu's root methods.
just some food for thought. Hope everything goes well, and there is a ton of people on the forum here that have great knowlege and can help with troubleshooting issues you may have

Team DevDigitel said:
if you made it through dirty santa the rest should be cake. 99% of the issues i covered for people were
after going to AOSP and not having a backup of their programing info in their efs and having to find a way to
manually go in and fix each fd up piece.
Click to expand...
Click to collapse
Yeah, I didn't have many problems there, although I did get stuck in the TWRP loop once.
The other is being on older software and downloading a OTA and rebooting with it in your internal storage.
This one causes a endless boot loop into twrp, so be advised to delete the update if your on older software or be prepared to
hit my post # 3 for fixes and be near a pc as you need to fastboot erase the fota and misc directories to resolve the boot loop. A twrp wipe will not fix it and restores etc wont either lol.
Click to expand...
Click to collapse
I am on the ZV3 version of the software. I do have the ZV5 update in my cache folder--are you saying it's a good idea to delete the update.zip file?
Otherwise theres now a lil over 100 pages of chatting and troubleshooting, fixes and things that have gone on, and mostly its all outdated as ive provided the fixes for 99% of everything in the latest version 7.5
Click to expand...
Click to collapse
That's what I like to hear! :good:
Just be prepared to take 15-20 minutes for the phone to boot up the 1st time. My rom is deodexed, and the 1st boot is doing 298 things before you get to the optimization part. There is not boot animations as the phone will always have the static screen issue on reboots so i went ahead a placed a disabled command there to just save time/batt life. The setup wizard is stripped and only there to give you the notice its done booting and time to get to playing around.
Click to expand...
Click to collapse
Appreciate the heads up. Familiar with the long boot process from DS, lol.
Magisk is kinda finicy being its systemless design. It takes some time to get used to it, and be aware that some older apps that dont support exotic root or systemless root may not request root and not fully work. Titanium backup is one i know is getting attacked by googles app scanning and needs to have that turned off before it will work, most of my apps have a option to set "force root" so it asks for a root request regardless if it understands MagiskSu's root methods.
Click to expand...
Click to collapse
Magisk is a new animal for me, as I've had zero experience with it. I do have Titanium Backup installed, so I'll make a mental note on that.
just some food for thought. Hope everything goes well, and there is a ton of people on the forum here that have great knowlege and can help with troubleshooting issues you may have
Click to expand...
Click to collapse
Thanks again--I appreciate your hard work and dedication to this!

bgibson72 said:
Yeah, I didn't have many problems there, although I did get stuck in the TWRP loop once.
I am on the ZV3 version of the software. I do have the ZV5 update in my cache folder--are you saying it's a good idea to delete the update.zip file?
YES, dont boot into twrp until you remove it, or its back into the twrp loop you go hehe
Click to expand...
Click to collapse

Team DevDigitel said:
bgibson72 said:
Yeah, I didn't have many problems there, although I did get stuck in the TWRP loop once.
I am on the ZV3 version of the software. I do have the ZV5 update in my cache folder--are you saying it's a good idea to delete the update.zip file?
YES, dont boot into twrp until you remove it, or its back into the twrp loop you go hehe
Click to expand...
Click to collapse
Weeeeeeeeeeeeee!!!
Will do!
Click to expand...
Click to collapse