I've searched but to no avail. I have a personal folder I created in my Desktop user folder on windows 11. At some point it just disappeared. I have selected show hidden items and even did a name search but neither process allows me to locate it. However when I try to create a new folder with the same name a popup asks me to confirm the folder replacement. It states the destinaltion already has a folder with the same name. Even if I click yes to replace it, the new folder immediately disappears. I have created other folders with different names and they show up just fine. Any thoughts?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It's a Registry issue. You can still go to it through Windows explorer's address bar by manually typing the address or the run box.
To quickly access the run box, press CTRL then the R key, then type in %USERPROFILE%\Desktop\Tools then press enter. It should take you to that folder.
Another thing you could do is that you could rename that folder to a different name through the command line.
To do so, using the same shortcut to access the run box, CTRL and R, then type in cmd and enter. Once the command line shows up, type in cd %USERPROFILE%\Desktop
Once the directory in cmd change into the Desktop, you can rename that folder by simply typing ren Tools Tools_2
I hope this helps, there are a couple other things you could try, but I believe that should do it.
Gearninja said:
It's a Registry issue. You can still go to it through Windows explorer's address bar by manually typing the address or the run box.
To quickly access the run box, press CTRL then the R key, then type in %USERPROFILE%\Desktop\Tools then press enter. It should take you to that folder.
Another thing you could do is that you could rename that folder to a different name through the command line.
To do so, using the same shortcut to access the run box, CTRL and R, then type in cmd and enter. Once the command line shows up, type in cd %USERPROFILE%\Desktop
Once the directory in cmd change into the Desktop, you can rename that folder by simply typing ren Tools Tools_2
I hope this helps, there are a couple other things you could try, but I believe that should do it.
Click to expand...
Click to collapse
Thank you for the response and it is greatly appreciated. Gave all of the methods a go and Windows still cannot see that folder. I thought utilizing the command line would really work but no luck there. I decided to just add another folder to my 2nd drive for now so it is not really an issue. So far this is the only folder that has done this that I am aware of and I hope it stays that way.
aybarrap1 said:
Thank you for the response and it is greatly appreciated. Gave all of the methods a go and Windows still cannot see that folder. I thought utilizing the command line would really work but no luck there. I decided to just add another folder to my 2nd drive for now so it is not really an issue. So far this is the only folder that has done this that I am aware of and I hope it stays that way.
Click to expand...
Click to collapse
You're welcome. I'm willing to attempt to fix it on TeamViewer if you're interested, just give me a good time that works for you. If not, I recommend using Recuva or some other recovery software, that'd allow you to access the files for sure, the issue still seems like it's a Registry issue, preventing everything from seeing that this folder exists. I'm not sure what could've caused it, would have to troubleshoot the problem to know and see whether it's just that folder.
However, you could also try to quickly move the folder content into a temporary folder by doing the following. CTRL and R, cmd, cd %USERPROFILE%\Desktop, mkdir Tools_2, move Tools\* Tools_2
Let me know how this goes
Gearninja said:
You're welcome. I'm willing to attempt to fix it on TeamViewer if you're interested, just give me a good time that works for you. If not, I recommend using Recuva or some other recovery software, that'd allow you to access the files for sure, the issue still seems like it's a Registry issue, preventing everything from seeing that this folder exists. I'm not sure what could've caused it, would have to troubleshoot the problem to know and see whether it's just that folder.
However, you could also try to quickly move the folder content into a temporary folder by doing the following. CTRL and R, cmd, cd %USERPROFILE%\Desktop, mkdir Tools_2, move Tools\* Tools_2
Let me know how this goes
Click to expand...
Click to collapse
Gave the command line a go and it actually discovered and moved a couple of shortcuts I had created. When trying to create the folder I still get the same message and Recuva did not assist. I am good on time. I don't know when you are available. I am usually available from 8pm to 1130pm EST.
It's interesting that you were able to move some shortcuts, If it moved shortcuts from there then there might not be other files. Recuva might have marked the folder as existing, that's probably why it didn't recover it. I'm available tomorrow at said times, message me whenever you wanna get started. It shouldn't take that long to figure out
Meanwhile, you could try running a system check in case any part of OS is corrupted. Run cmd as admin by pressing the Windows key and X the selecting Command Prompt (Admin). Enter sfc /scannow. Once it's done, type in DISM /Online /Cleanup-Image /RestoreHealth
Gearninja said:
It's interesting that you were able to move some shortcuts, If it moved shortcuts from there then there might not be other files. Recuva might have marked the folder as existing, that's probably why it didn't recover it. I'm available tomorrow at said times, message me whenever you wanna get started. It shouldn't take that long to figure out
Meanwhile, you could try running a system check in case any part of OS is corrupted. Run cmd as admin by pressing the Windows key and X the selecting Command Prompt (Admin). Enter sfc /scannow. Once it's done, type in DISM /Online /Cleanup-Image /RestoreHealth
Click to expand...
Click to collapse
I only had 2 shortcuts. I was working on a fresh install so had not done much. Just more surprised about the folder...and it being the only one that I am aware of.
I ran the system check. The check did find some corruption and fixed it according to the scan. I ran DISM as well. However, it still did not restore the folder and I am still getting the same error when I try to create it again.
Gotcha. I could check It out on TeamViewer if interested in finding what happened, but you could simply delete than folder through the command line. Run it as admin just in case, you can use the Windows key and X shortcut, then cd %USERPROFILE%\Desktop and type in rmdir Tools
Gearninja said:
Gotcha. I could check It out on TeamViewer if interested in finding what happened, but you could simply delete than folder through the command line. Run it as admin just in case, you can use the Windows key and X shortcut, then cd %USERPROFILE%\Desktop and type in rmdir Tools
Click to expand...
Click to collapse
Well now we got somewhere. rmdir did the trick. I was able to create the folder again and it actually shows now. I will keep an eye for any other folders going missing. Hope this was just a one off. I definitely appreciate the help. If it does happen again any time soon I will follow up here.
Glad to hear that it worked out. Seems like that folder's attributes got messed up in the registry somehow. Sure thing, let me know if you're faced with any other issues, hopefully it'll be fine though. Take care
So within a couple of days of this, I uninstalled a feature from Windows because I don't use it and my computer doesn't even support it. Did this in Windows 10 on this hardware with no issues. As soon as I removed it, Windows 11 UI froze. I waited for over an hour and still frozen. I force restarted, reinstalled the feature. Everytime I booted up and logged in, the UI would freeze after about 2 to 3 minutes. I decided to go back to my last restore point when the PC worked and was still freezing.
Reinstalled Windows 10 via disk image and scanned my hardware for errors (ssd, RAM, hardware stress tests for CPU and GPU) and all tests were good.
I created a new Windows installation media using a different USB drive and reinstalled Windows 11. I did all of my usual configurations, which included removing the feature that seemed to have started the freezing, and so far no issues for the last 5 days. On my last 11 install sfc \scannow found corruption but as of today has found nothing on the reinstall. I have not found or seen any other issues.
I truly believe that my last install of Windows 11 was a bad install. I took a disk image just to be sure.
Glad to hear that it worked out. Freezing could be caused by many things, software or hardware related. Could be overheating, slow hard drive or bad sectors, one of the RAM sticks going back, corrupt system files and registry, memory leaks causing high RAM usage, bugs in certain windows services causing CPU spikes, and conflicting software, services or drivers. Depending on the how and when the issue started, you'd be able to diagnose it, perhaps check the error logs in event viewer and see what changed last like you did. I don't see how an unneeded feature removal could cause issues, unless other features depend on it, but either way seems like removing it wasn't the issue since you removed it with no issues after reinstallation. I agree with you, there was probably other underlying issues in the previous installation, especially if you haven't installed any 3rd party software that could've been problematic. Hopefully it's all good now, but in case anything comes up in the future, in cause it isn't an obvious recent change, use safe mode to see if it's a 3rd party software related issue, disable unnecessary startup 3rd party services and software from msconfig and task manager, check event viewer for errors, check task manager and see if there is any high resource usage or CPU spikes, install a Temperature monitor, check the hard drives health or run a defragment, run the system repair commands just in case, if non of that helps find the issue or fix then it could be a rootkit backdoor that's causing issues, but it's highly unlikely. General advice for viruses, use Sandboxie to run software and executable that you download from unofficial sources, it runs things in an isolated environment, so they won't effect your system installation in case something is wrong with them. I believe that pretty much covers most factors. Take care
Gearninja said:
Glad to hear that it worked out. Freezing could be caused by many things, software or hardware related. Could be overheating, slow hard drive or bad sectors, one of the RAM sticks going back, corrupt system files and registry, memory leaks causing high RAM usage, bugs in certain windows services causing CPU spikes, and conflicting software, services or drivers. Depending on the how and when the issue started, you'd be able to diagnose it, perhaps check the error logs in event viewer and see what changed last like you did. I don't see how an unneeded feature removal could cause issues, unless other features depend on it, but either way seems like removing it wasn't the issue since you removed it with no issues after reinstallation. I agree with you, there was probably other underlying issues in the previous installation, especially if you haven't installed any 3rd party software that could've been problematic. Hopefully it's all good now, but in case anything comes up in the future, in cause it isn't an obvious recent change, use safe mode to see if it's a 3rd party software related issue, disable unnecessary startup 3rd party services and software from msconfig and task manager, check event viewer for errors, check task manager and see if there is any high resource usage or CPU spikes, install a Temperature monitor, check the hard drives health or run a defragment, run the system repair commands just in case, if non of that helps find the issue or fix then it could be a rootkit backdoor that's causing issues, but it's highly unlikely. General advice for viruses, use Sandboxie to run software and executable that you download from unofficial sources, it runs things in an isolated environment, so they won't effect your system installation in case something is wrong with them. I believe that pretty much covers most factors. Take care
Click to expand...
Click to collapse
Thank you for the input. I used a variety of hardware tests and monitored temps as part of my rundown. On Windows 10 I never had these issues for the 7 months I used it. But admittedly I did not think about the possibility of a bad driver. Regardless at the moment everything seems to be working fine and I am monitoring for errors. I will keep you posted if anything else arises.
Related
Well, I'm not much of a guide person, but there's a great tool that's been out for a long time that has proven to be quite useful to me. THIS IS NOT A REPLACEMENT FOR FREEZA'S GUIDE. That's an excellent guide, and he deserves full credit for it. This guide is for those of you who want to trim/debloat after you flash. It also serves many other handy uses, which I shall explain in a few.
Also keep in mind, this will work on damn near ANY rooted Android phone. In fact, I used to use it QUITE a lot on my old Sprint Hero. This is essentially ADB without the need to know how to use the command line.
~~ This guide is a constant WIP ~~
What is Android Commander?
It's an all-in-one tool that was designed using adb. It provides the following:
[*]Complete root-based file manager
[*]Applications Manager
[*]Rebooting/Powerdown Abilities
[*]Storage Monitor
[*]All around awesome tool
It's completely free to use and is written by a talented XDA developer.
Requirements:
Windows XP or higher: As if I'm going to give you link to this
My little ADB Package: http://dl.dropbox.com/u/345001/Images/AC Guide/ADB.rar (For anyone wondering why I'm giving this seperate, it's to save you the trouble of having to download the entire android sdk and going through the convoluted method of using the SDK manager to grab adb)
Android Commander written by our very own XDA user PanPiotr: http://androidcommander.com/
1. Download my ADB package, and extract is somewhere. Inside is a folder called ADB, with two dlls and the adb executable. Remember where you put it.
2. Download and install Android Commander.
3. Right click and run Android Commander as administrator. It will ask you to set the ADB path near the bottom. Select the ADB folder that contains the 3 files above, which you downloaded already.
4. If it doesn't automatically start the app after selecting the folder, simply press exit, and run it again as administrator. This time, the app will start up
And this is what you see!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now for starters, you'll notice a plethora of information. Try not to get overwhelemd. Android Commander is a ridiculously comprehensive utility. And the best part is that it's based entirely on ADB. Now, by default, you'll see your Windows files on the left pane, and the Android files on the right.
Let's begin with the debloating. Start by finding the "System" folder first.
From here, head on over to the "app" folder.
So this should be pretty self explanatory. Start selecting checkboxes for apps and bloatware that you don't want/need. Then, just click the "delete" button. It will delete them all in one shot.
I know this seems a bit anticlimactic, but that's more or less it for the debloating guide, because that's only one of the many uses AC has. Read on to the next few posts for a few scenarios/possibilities that you may encounter while using custom ROMs.
Basic Scenarios/Uses
This post covers basic scenarios and uses for Android Commander.
[If you've been directly linked to this post, please see the post above for information on installing and getting Android Commander up and running]
Remember, AC can start functioning as quickly as just moments after you see the white HTC screen. It doesn't have to be fully on for you to use AC and all its features. Android Commander can also be used from recovery as well.
Help! I used SetCPU, checked "Set On Boot", overclocked too high, and now my device is in a boot loop
Not a problem! I've done this too many damn times to count. The solution comes down to two options; one, be super fast when booting up and try and clock down SetCPU when you get in (very frustrating), or use AC! Remember, Android Commander can be used either in recovery or even during boot! So what we're going to do is start it up, and uninstall SetCPU. Let's open up Android Commander, and select "Applications Manager". It will ask you if you would like to update the list of applications, click yes.
From this point on, you can now see all of your applications. Simply click on one of the applications, and either uninstall it using the buttons above, choosing to delete its data or not.
By the time your device finishes rebooting, or when you boot out of recovery, you'll find SetCPU gone and your device no longer locking up and bootlooping! Easy, huh?
Did you know you can reboot the device from Android Commander?
Yes, you can . Simply click on the "Phone" menu up top:
Pick what you want to boot in. Also, yes, you see "screenshot" in there, but it currently doesn't work for the EVO 3D. It should for older devices though.
Did you know you can flash a recovery image through AC?
Indeed, you can.
More to come!
Advanced Uses - For Devs/Themers
This section is intended for both budding and veteran ROM cooks, modders, and themers.
Did you know that you can set file permissions with Android Commander? You can do what root explorer does, just fine. If you choose to use the 7.9.9.9 beta and up, you can easily set file permissions of any file, as shown below
MORE TO COME
First part of the guide is up
Thanks for this, I look forwards to seeing what more comes to this guide. Well done man.
empiire said:
Thanks for this, I look forwards to seeing what more comes to this guide. Well done man.
Click to expand...
Click to collapse
Glad you find it useful. It's got a ton of potential for devs such as yourself, I'd highly recommend you experiment with it, there's stuff I still don't even know about yet.
It even has it's own pre-"su"'d command line built into it.
Updated the "basic use" post to include more awesome little details
This is a nice tool! im definitively gonna be using this! thanks!!
steal25 said:
This is a nice tool! im definitively gonna be using this! thanks!!
Click to expand...
Click to collapse
Let me know what other cool features you end up finding, I'm sure you'll run into plenty of stuff I haven't found yet.
This will be loaded before the sun sets. Thanks for sharing - great utility.
Sent from here using this. Black. Slab.
Thats a pretty slick app.
I did everything stated in the first post, and for some reason it doesn't say I am rooted. so I don't have the application manager. to be clear I don't need the SDK installed, just your file? I extracted it into a new directory and then set that as the path when I started up AC, it starts up, finds my phone, can explore it, reboot it, but it still says I am not rooted in the lower left corner of AC. I am not a noob when it comes to doing stuff with android, but am noobish with adb, never used it before, so i thought this would be a great tool for me to learn...if I can get it to work.
jbermi said:
I did everything stated in the first post, and for some reason it doesn't say I am rooted. so I don't have the application manager. to be clear I don't need the SDK installed, just your file? I extracted it into a new directory and then set that as the path when I started up AC, it starts up, finds my phone, can explore it, reboot it, but it still says I am not rooted in the lower left corner of AC. I am not a noob when it comes to doing stuff with android, but am noobish with adb, never used it before, so i thought this would be a great tool for me to learn...if I can get it to work.
Click to expand...
Click to collapse
Hmm. Did you run AC as admin?
LiquidSolstice said:
Hmm. Did you run AC as admin?
Click to expand...
Click to collapse
yep, followed everything in the first post...and yes, the phone is rooted. LOL. I am going to uninstall AC and try again, and see if that works...
problem - phones rooted - viper rom 1.2.1 stock kernal - downloaded the two files you have, installed your AC, and unzipped the ADB - start up, point it to that folder, then it has the little window that says DEVICE: NOT FOUND. have debug on, charge, i am the admin on the pc.
-----sorry------ now it runs only after i posted.... sometimes thats all it takes - now to test it out, looks very useful, and easy.... thank you
Thanks, Liquid. Way faster then using Root Explorer or manual adb. Wish I'd known about this ages ago.
Very usefull...but We realy need a UI manager to change icons ect....
Thanks Liquid - I used your LiquidSense ROMs over on the Hero side, and now that I've got my E3D, it's great to see you devving over here. I used Android Commander a lot on the Hero, so good to see it will still work for the E3D! Thanks for the Guide!
-mb
when i use the sign .zip file tool, i put a file on my desktop, then run the tool and cannot figure out where is put the new signed file at? Any help?
i changed the output folder to desktop, and nothing, it doesn't sign the file and ouput it....hmm...
Great guide! I use Android Commander for just about everything. Nice point on using it to get out of a boot loop. I discovered that when I had my Hero, and it saved me many times.
Sent from my s-off Shooter!
How to for n00bs:
Beaups Moonshine S-OFF for the Droid DNA
(Note: This guide will assume that you are complete noob with android and linux, BUT that you are not too dense to google basic things and infer basic differences between PC setups)
YOU WILL NEED:
1 Laptop or Desktop with internet access
1 32bit Linux (Ubuntu or Mint preferred, Mint to be used in this guide) liveUSB or liveCD (liveCD preferred, and what will be covered in this guide)
1 Stock Droid DNA with the 2.06 firmware update (2.04 is reported to work, but more success seems to be had with the updated firmware) WITH AT LEAST 80% BATTERY LIFE
1 Factory HTC/Droid micro-usb (Or any cable you know will work with ADB)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Prepping your computer:
1: Burn a liveCD of your linux distro of choice. Mint is my choice due to having great out of the box compatibility with hardware.
2: Insert liveCD into your PC, turn it on (or reboot), and enter boot menu (typically esc, f8, or f12 pressed during start up) and select “Boot from CD Drive”.
3: Allow liveCD to boot, it may take some time depending on the speed of your hardware. This is good time to prepare your phone for shining.
Prepping your phone:
1: Update to the 2.06 firmware update, if you have not already. If you cannot OTA, you can find guides to flash said firmware update elsewhere on XDA
a: If you are unsure what firmware you are on, go to “Settings”, “About”, and “Software Information” and it will have your firmware listed.
2: Disable any sort of screen lock. Image lock, facelock, pin lock, doesn't matter, it MUST BE DISABLED FOR THIS TO WORK
3: Disable “Fastboot”. “Settings”, “Battery”, UNCHECK “Fastboot”
4: Enable USB Debugging. “Settings”, “Developer Options”, “USB Debugging”
5: Boot into fastboot (turn off phone, reboot holding down POWER button and VOLUME DOWN button simultaneously). Select “Factory reset”. Allow phone to reset and reboot. Go back into settings, repeat sets 2 and 3 if necessary.
Downloading, unpacking, and excecuting moonshine.
1: On your live linux session, that is connected to the internet, go to www.moonshine.io
2: READ EVERYTHING
3: READ EVERYTHING AGAIN
4: Download the .tgz file relevant to your device (for most of us this will be the Verizon DNA file “moonshine_dlx_2.06.605.1.tgz”
5: Go to the folder your .tgz was just downloaded to. This should be your “downloads directory”
6: Right click anywhere in your download directory and select “Open in Terminal”
7: Extract the moonshine .tgz by typing out the following command into terminal “tar -zxf moonshine_<device>_<version>.tgz” For the Verizon DNA this will be “tar -zxf moonshine_dlx_2.06.605.1.tgz”
Your download directory should look like this when done
(Unfortunately, after this, the iPhone I was using to take pictures died, so there are no more pictures after this, but everything is very straightforward)
At this time plug your phone (which has been factory reset, rebooted, and all things listed in the “phone prep section” have been double checked) into your PC via your HTC/Android USB cable.
8: Execute the “Distiller” by typing the following command into terminal “sudo ./distiller”
9: Agree to the onscreen prompts, sit back, relax, DO NOT F**K WITH YOUR PHONE, and let the shine do its magic. This should take five to fifteen minutes and your phone will reboot several times.
10: Enjoy S-OFF and root.
ALL CREDIT GOES TO BEAUPS AND THE MOONSHINE DEV TEAM, this is simply a shoddy step by step guide by a n00b for n00bs to (hopefully) get more comfortable with the idea. This may be reproduced, altered, or edited in anyway as long as credit is given to me (DWC2134) for the original text and pictures and to the DEVS who brought us this awesome utility. In fact, PLEASE edit, improve, and revise this as you see fit for use by new android and linux users. Any changes suggested in this thread will be taken into account and incorporated into the OP.
Toubleshooting:
1: If you are experiencing the "temproot failed" problem, first try a hard reboot, then a factory reset + hard reboot if the reboot alone does not solve the problem.
2: There is some chatter of questionable validity that VZW is trying to push an update to stop SOFF. If you are having trouble, turn off your radios and/or put your phone in airplane mode while attempting moonshine. While most, myself included, doubt the validity of this claim it is better safe then sorry.
Beaups original moonshine thread
Moderators, if this is in the wrong section, or out of line, etc etc, please move, edit, delete, or do as needed.
Does it have to be the 32 bit version? If so I just have to redo my live usb.
sent from my droid DNA with xda premium
DaPitt84 said:
Does it have to be the 32 bit version? If so I just have to redo my live usb.
sent from my droid DNA with xda premium
Click to expand...
Click to collapse
Yes or the exploit will give an error saying there aren't enough 32 bit libraries. I tried on a 64 bit and got that error. I re did my live cd to use 32 bit ran the exploit and it worked flawlessly.
Sent from my HTC6435LVW using xda premium
Nice howto I did the s-off yesterday worked great. I'm on windows 7 64 bit and installed 32 bit mint.
For people doing this like op said install and use 32 bit just easier and if you're on a 64 bit system doesn't matter 32 bit installs fine.
Sent from my HTC6435LVW using xda premium
Very nice "How To' for us Windows PC peeps dwc2134...thank you.
I have a couple of questions if anyone can answer:
1) I haven't seen any other procedure where "Factory Reset" is called upon. Is there a specific reason?
2) I have a burned image of "Ubuntu-13.04-desktop-i386.iso" on USB Stick that runs v/smoothly on my laptop w/Vista Ultimate, but I can't seem to get to terminal screen. I do however see all of the Moonshine flies in download folder when in Ubuntu and "moonshine_dlx_2.06.605.1.tgz"
Please forgive the noobish Q's
Thx in advance
First of all, thank you dwc2134 for providing this guide! I am very new to this scene (Android rooting) and this guide helps out TREMENDOUSLY since I have no knowledge about terminal/command prompts.
However, after re-reading this guide and the instructions at moonshine.io, I have some questions in my head that are preventing me from going further (If anyone here can answer any of my questions, it would be most appreciated!)
1. At the Instructions page on moonshine.io, Step 8 says "Use the matchingStockRUU..", I have no idea what this, is this something I should worry about? I have not modified my Droid DNA in anyway whatsoever ever since I got the device. I only did the 2 OTA updates (2.04 and 2.06) and that's it.
2. In this guide (dwc2134's) on Step 8 where it says to execute the "Distiller", do I type it into the same terminal window I extracted the Moonshine.tgz file?
3. Once the whole process finishes, and I go back to the fastboot screen to see the glorious text that reads: "S-Off", does this mean my phone is rooted and I can install apps like SetCPU off the bat? Or do I have to flash a custom ROM and if so, can anyone recommend a "tried-and-true" ROM?
Once again, if anyone can answer my queries, it would be very helpful. Thank you in advance!
dfa7 said:
Very nice "How To' for us Windows PC peeps dwc2134...thank you.
I have a couple of questions if anyone can answer:
1) I haven't seen any other procedure where "Factory Reset" is called upon. Is there a specific reason?
2) I have a burned image of "Ubuntu-13.04-desktop-i386.iso" on USB Stick that runs v/smoothly on my laptop w/Vista Ultimate, but I can't seem to get to terminal screen. I do however see all of the Moonshine flies in download folder when in Ubuntu and "moonshine_dlx_2.06.605.1.tgz"
Please forgive the noobish Q's
Thx in advance
Click to expand...
Click to collapse
OK, fingered it out. This may just be of some help to others here. ubuntu-13.04-desktop-i386.iso wouldn't get into "terminal" BUT, linuxmint-15-cinnamon-dvd-32bit.iso does.
Does anyone know if it absolutely necessary to "Factory Reset" DNA with this Mooshine S-OFF method?
dfa7 said:
Very nice "How To' for us Windows PC peeps dwc2134...thank you.
I have a couple of questions if anyone can answer:
1) I haven't seen any other procedure where "Factory Reset" is called upon. Is there a specific reason?
2) I have a burned image of "Ubuntu-13.04-desktop-i386.iso" on USB Stick that runs v/smoothly on my laptop w/Vista Ultimate, but I can't seem to get to terminal screen. I do however see all of the Moonshine flies in download folder when in Ubuntu and "moonshine_dlx_2.06.605.1.tgz"
Please forgive the noobish Q's
Thx in advance
Click to expand...
Click to collapse
1: While not ENTIRELY necessary for a successful moonshining, performing the factory reset and hard reboot seems to solve the "temproot failed" problem several users (myself included) have expierenced.
2: Mint is my go to, so it may be slightly different in ubuntu. You can also open terminal by pressing ctrl-alt-T or by going to your applications menu (or the search in the dash) and searching for "Terminal" and then inputting "cd ~/downloads". This will, for lack of better words, open your download directory in terminal so that the commands you input specifically look for, and effect, the files there. You may have to alter the "~/downloads" portion slightly to get you to the correct directory, but looking at the filepath on your computer it should be pretty obvious.
AndroM31 said:
First of all, thank you dwc2134 for providing this guide! I am very new to this scene (Android rooting) and this guide helps out TREMENDOUSLY since I have no knowledge about terminal/command prompts.
However, after re-reading this guide and the instructions at moonshine.io, I have some questions in my head that are preventing me from going further (If anyone here can answer any of my questions, it would be most appreciated!)
1. At the Instructions page on moonshine.io, Step 8 says "Use the matchingStockRUU..", I have no idea what this, is this something I should worry about? I have not modified my Droid DNA in anyway whatsoever ever since I got the device. I only did the 2 OTA updates (2.04 and 2.06) and that's it.
2. In this guide (dwc2134's) on Step 8 where it says to execute the "Distiller", do I type it into the same terminal window I extracted the Moonshine.tgz file?
3. Once the whole process finishes, and I go back to the fastboot screen to see the glorious text that reads: "S-Off", does this mean my phone is rooted and I can install apps like SetCPU off the bat? Or do I have to flash a custom ROM and if so, can anyone recommend a "tried-and-true" ROM?
Once again, if anyone can answer my queries, it would be very helpful. Thank you in advance!
Click to expand...
Click to collapse
1: If you have not modified your phone in anyway, and have received the OTAs, then that is irrelevant to you.
2: Yes. Or in another terminal window opened in your "downloads" directory, though opening a second window seems kind of pointless.
3: Moonshine installs superuser to your device, so YES YOU CAN install custom apps like SetCPU right off the bat. I would recommend first installing a custom recovery (I am using CWMs new touch version) and making a nandroid backup before doing anything else, personally. I would also highly recommend installing a custom rom instead of putting in too much time with the stock sense rom. There are so many fantastic roms out for this phone, it would almost be a waste not to. A lot of folks swear by the ViperROM. I'm currently using it and love it.
dwc2134 said:
1: While not ENTIRELY necessary for a successful moonshining, performing the factory reset and hard reboot seems to solve the "temproot failed" problem several users (myself included) have expierenced.
2: Mint is my go to, so it may be slightly different in ubuntu. You can also open terminal by pressing ctrl-alt-T or by going to your applications menu (or the search in the dash) and searching for "Terminal" and then inputting "cd ~/downloads". This will, for lack of better words, open your download directory in terminal so that the commands you input specifically look for, and effect, the files there. You may have to alter the "~/downloads" portion slightly to get you to the correct directory, but looking at the filepath on your computer it should be pretty obvious
Click to expand...
Click to collapse
Thanks for clarrification. I decided to Mint and all is perfect! Ubuntu was a challenge considering I'm not an Apple guy and Linux is greek to me. As for the "Factory Reset", I'll gamble only 'cause I'm configured to my liking and not in mood yet to spend a day getting everything back. Thx again!
All's well that ends well. If you end up having the temp root problem, try a hard reboot first and then a factory reset.
Sent from my HTC6435LVW using xda app-developers app
dwc2134 said:
1: If you have not modified your phone in anyway, and have received the OTAs, then that is irrelevant to you.
2: Yes. Or in another terminal window opened in your "downloads" directory, though opening a second window seems kind of pointless.
3: Moonshine installs superuser to your device, so YES YOU CAN install custom apps like SetCPU right off the bat. I would recommend first installing a custom recovery (I am using CWMs new touch version) and making a nandroid backup before doing anything else, personally. I would also highly recommend installing a custom rom instead of putting in too much time with the stock sense rom. There are so many fantastic roms out for this phone, it would almost be a waste not to. A lot of folks swear by the ViperROM. I'm currently using it and love it.
Click to expand...
Click to collapse
Thank you so much for clearing away my doubts! Once I get the "S-Off" message, I'll look into your suggestions mentioned here.
dwc2134 said:
All's well that ends well. If you end up having the temp root problem, try a hard reboot first and then a factory reset.
Click to expand...
Click to collapse
dwc2134 - thanks for your help, patience and interset with some of us and this project! It does seem easier than revone.
Where do I find the Linux file to put on usb? I don't have any blank cd's either...will it work from usb stick?
HellRayzer said:
Where do I find the Linux file to put on usb? I don't have any blank cd's either...will it work from usb stick?
Click to expand...
Click to collapse
You can find the .iso image for any distro you want online. I prefer Linux Mint, though Ubuntu is another crowd favorite. You can make a bootable USB, but I find it easier to make and use liveCD/DVDs. A pack of burnable DVDs is $2.89 at CVS. Google is your friend for the rest of this, it is all VERY self explanatory and most distro sites put step by step instructions right on their website.
http://www.linuxmint.com/download.php
http://www.linuxmint.com/documentation/user-guide/english_15.0.pdf
Error When Trying To Download - 'This file reached max downloads limit"
Followed the guide...booted from USB Ubuntu. No problems. Connected to moonshine.io, clicked next, next, but when I selected the DNA version, I get the error:
"This file reached max downloads limit"
...and no download.
Any ideas? I see another person has posted this in the developers section. Is there a link problem?
Thanks.
dwc2134 said:
You can find the .iso image for any distro you want online. I prefer Linux Mint, though Ubuntu is another crowd favorite. You can make a bootable USB, but I find it easier to make and use liveCD/DVDs. A pack of burnable DVDs is $2.89 at CVS. Google is your friend for the rest of this, it is all VERY self explanatory and most distro sites put step by step instructions right on their website.
http://www.linuxmint.com/download.php
http://www.linuxmint.com/documentation/user-guide/english_15.0.pdf
Click to expand...
Click to collapse
This is spot on. I did my first live cd related to rescuing crucial data on a government computer with a corrupt OS a few weeks ago. I googled "How to make a bootable live cd USB drive" and literally in five minutes I was booted into my Ubuntu distro.
One thing I did learn is with Ubuntu there's a lot of alternative distros on their main site with all the links. After not having the option to boot without making any changes I went to my google-found guide again and realized only ubuntu distros with "desktop" in the filename would give me the live boot option I needed for the task at hand.
One of those small details I overlooked, that was solved by a quick recheck with google.
EXCELLENT GUIDE, I'm really impressed.
Max download limit reached.
I am having the same issue it says that the maxium download limit has been reached.:crying:
I can't donate if I can't download!
FUBAR'd
UntamedDarkness said:
I am having the same issue it says that the maxium download limit has been reached.:crying:
I can't donate if I can't download!
Click to expand...
Click to collapse
Link looks to be FUBAR'd. Maybe Verizon got pizzzed and did a bit of hacking themselves...
Several people now reporting the issues in multiple threads. I just rechecked...same error.
Out of curiosity, are you using Verizon Mobile Hotspot on your phone to connect to the internet via computer? I am.
CharliesTheMan said:
This is spot on. I did my first live cd related to rescuing crucial data on a government computer with a corrupt OS a few weeks ago. I googled "How to make a bootable live cd USB drive" and literally in five minutes I was booted into my Ubuntu distro.
One thing I did learn is with Ubuntu there's a lot of alternative distros on their main site with all the links. After not having the option to boot without making any changes I went to my google-found guide again and realized only ubuntu distros with "desktop" in the filename would give me the live boot option I needed for the task at hand.
One of those small details I overlooked, that was solved by a quick recheck with google.
EXCELLENT GUIDE, I'm really impressed.
Click to expand...
Click to collapse
Yep, google has most any answer you could ever need if you search enough. The only reason I promote liveCDs over liveUSBs is that I think they are a touch easier to make and use. For some reason I have always had a hard time getting liveUSBs to work.
Thank you! I'm really glad it seems to have helped some folks out!
UntamedDarkness said:
I am having the same issue it says that the maxium download limit has been reached.:crying:
I can't donate if I can't download!
Click to expand...
Click to collapse
ejohanss said:
Link looks to be FUBAR'd. Maybe Verizon got pizzzed and did a bit of hacking themselves...
Several people now reporting the issues in multiple threads. I just rechecked...same error.
Out of curiosity, are you using Verizon Mobile Hotspot on your phone to connect to the internet via computer? I am.
Click to expand...
Click to collapse
I doubt it is Verizon, most likely a bandwidth issue or hosting service issue. Seems to be common with everyone trying to download moonshine right now. Sounds like there is trouble with the download limit counter. I knew I should have kept a backup copy of the .tgz
No, when I tether I use one of the free solutions. I got bumped off of unlimited, so I tend to use more wifi then phone data. You NEED an internet connection that is not reliant on your phone for this to work. Moonshine actively connects to the internet during the ./distiller program.
dwc2134 said:
Yep, google has most any answer you could ever need if you search enough. The only reason I promote liveCDs over liveUSBs is that I think they are a touch easier to make and use. For some reason I have always had a hard time getting liveUSBs to work.
Thank you! I'm really glad it seems to have helped some folks out!
I doubt it is Verizon, most likely a bandwidth issue or hosting service issue. Seems to be common with everyone trying to download moonshine right now. Hopefully beaups will be able to set up some new downloads or someone else will be willing to host the files for him. I knew I should have kept a backup copy of the .tgz
No, when I tether I use one of the free solutions. I got bumped off of unlimited, so I tend to use more wifi then phone data. You NEED an internet connection that is not reliant on your phone for this to work. Moonshine actively connects to the internet during the ./distiller program.
Click to expand...
Click to collapse
I just checked it's a host download limit it's ABSOLUTELY not related to verizon.
Hi all. First, apologies if this is the wrong place for this sort of post. It's mainly just a collection of my notes on the Verizon LG G3 running stock software update VS98510B, so there are a lot of different topics touched upon. I'm usually pretty shy around forums, but I figured something I've found might be useful to someone else, so I finally decided to post here. Anyway, here's what I've found.
Autorun Installer
This really annoyed me for a while when I first got the phone. Every time I'd try connecting it to my computer, it'd enter some sort of installer mode for LG/Verizon drivers. It would stay in this mode for about 30 seconds unless I manually put it back into ADB mode. After a good bit of digging around, I found out how to disable it without root or any special permissions. Open the stock dialer app, then enter the code "##3328873" and press send. It'll prompt for a service code, which is (of course) "000000". While the Verizon G3 appears to be missing a large chunk of the hidden menus, this section still seems to work. One of the options is a checkbox for "Tool Launcher enable" - uncheck it to disable the Verizon autorun installer.
Sideloading in Recovery Mode
I was curious how IORoot worked, so I started taking it apart. Basically, on the G3, it just uses a .zip sideloaded in recovery mode to copy over the su and related binaries. There's a decent bit of documentation out there on how to create your own .zip for sideloading, but I found one catch - the .zip needs to be signed with the proper key, or recovery will reject it. It turns out that this key is located at "./bootable/recovery/testdata/testkey" in the AOSP project. I forget the exact command for signing the .zip, but using this key, you can create your own sideload applications. Edify provides a nice way to script your application; I used it to create a sideload application to replace the HotspotProvision apk with a slightly modified version that skips the billing checks. Doing so does not require root access, as the sideloaded application appears to run as root by default. Replacing "HotspotProvision.apk" also does not trigger the root detector. However, I also made my own sideload .zip to copy over the su binary I compiled from AOSP - as soon as I booted the phone, the software status indicator changed to modified. I have some more information on that below. If anyone wants either of these sideload applications, I can upload them somewhere with their source, just let me know.
Ramdisk Compression
The boot, recovery, laf, and factory partitions are all mostly in standard format and can be split into the kernel and ramdisk parts with existing tools. However, most tools seem to expect the ramdisk to be compressed using gzip. Since it's not, they'll fail to extract the cpio archive from it. The G3 ramdisk is compressed using LZ4 instead. Once decompressed using the standard LZ4 utility, it has the same structure as a normal boot ramdisk - the cpio archive can be extracted to view the boot filesystem. I haven't really looked into it, but I believe the boot images all have a device tree binary appended after the ramdisk as well.
AT Commands
When looking into the boot process, I stumbled upon the AT command framework for the G3, which proved to be rather interesting. When connected to my computer in ADB mode, the phone exposes two serial ports. One of these ports looks like it's supposed to accept plain-text AT commands, but it also has been rather buggy in registering the end of a command for me. The other port accepts commands in some sort of binary format that I have not taken apart yet. If you want to send AT commands to the phone from ADB shell, write them to "/dev/smd0" and read the response from there. Sometimes, the response is not put on the device for some reason, but instead just printed to the logs under the tag "Atd"; just use "logcat Atd:V" to view them. The requests seem to be handled by "/system/bin/atd", which largely uses "/system/lib/libatd_common.so" to work. Looking through the disassembly showed some interesting things, included what looked like a test command that involved the bootloader unlock status, though I haven't figured out exactly how it works yet. A lot of the commands began with "AT%", which I think is the vendor specific prefix for AT commands typically. For some reason, I couldn't get any of these commands to work, even though some of the standard commands worked fine. One particularly interesting function (to me) was one that claimed to be able to write the software bootloader, SBL1. The function was called "store_sbl1_image"; there are some other functions that affect sbl1 as well. There are also functions for qfuses/QFPROM and other things that may be of interest to us. A lot of these functions access the misc partition through "/system/lib/liblgftmitem.so", so that may be a partition worth looking into.
Volume Key Booting
Entering the dialer command "##228378" and pressing send brings up a menu that has an option called "Device Test". Choosing this option prompts you that the phone will reboot; if allowed, it will reboot into MiniOS mode, which is stored in the "factory" partition ("/dev/block/mmcblk0p40"). This mode allows you to run a number of device tests, though many options are disabled somehow. One interesting thing I've observed is that, if the phone is shut down from MiniOS mode, then turned on by holding the volume down and power buttons simultaneously (possibly while plugged into a computer, I forget if this is necessary), the phone enters a pseudo-recovery mode that vaguely resembles real recovery mode, but is actually implemented after boot. Another volume key command is to hold volume up while powering on and connected to a computer by USB (the USB connection is required). This boots into factory download mode from the "laf" partition("/dev/block/mmcblk0p33"). The only way I've found to exit this mode is to remove the battery from the case. One final note is that while booting into normal mode, but having done so by holding volume down and the power button, the bootloader logs a message that it is going to enter fastboot mode. However, it does not and just boots normally instead. It seems that fastboot can only be activated if aboot fails to boot normally. I've read of people accomplishing this by messing up the "laf" partition and then booting into download mode, but I've not tried it myself.
Root Checker ("/system/bin/rctd")
After already setting my system to the "modified" status, I looked into the root checker executable at "/system/bin/rctd". A quick disassembly showed almost no strings in the binary. This is because they are all obfuscated. To load the strings, as series of instructions store individual characters into the stack at the proper offsets, eventually forming all of the strings needed by the program. Because I don't have the "Pro" version of IDA, I can't just run the executable through the debugger to get the strings out, so I had to resort to writing a really hacky emulator for a few ARM instructions to produce the strings. I only did this for one function, but the results were rather interesting. This function constructed the following string(s): "mt6575 mt6577 /sbin/su ro.hardware /system/bin/su /system/xbin/su /system/sbin/su /data/local/tmp/su /system/bin/busybox /system/xbin/busybox /data/local/tmp/busybox /system/app/Superuser.apk /system/app/SuperUser.apk /system/app/superuser.apk /system/app/SuperuserPro.apk /data/local/tmp/Superuser.apk /data/local/tmp/SuperUser.apk /data/local/tmp/superuser.apk /data/data/com.noshufou.android.su". I'm assuming this is a list of all of the files that the program looks for to determine if the phone has been rooted. In theory, using some way of randomly naming these files could prevent the root checker from detecting a rooted presence. If anyone who has IDA Pro wants to run "rctd" through the debugger, they might find more interesting things.
fastboot oem-unlock
While I've not tried booting into fastboot mode myself, I have "manually" executed the "fastboot oem-unlock" command. By disassembling the "aboot" partition ("/dev/block/mmcblk0p5"), I found that oem-unlock writes the value 0x01 to offset 0x1FFE10 of the "aboot" partition. I replicated this action with the command from a root shell "echo -en '\x01' | dd of=/dev/block/mmcblk0p5 bs=1 seek=2096656 count=1 conv=notrunc". After doing so and rebooting, which seemed to take longer than usual, I checked the kernel logs in "/data/logger/kernel.log*", and, in the bootloader logs section, there was a line displaying "[ 0.355056 / 01-01 00:00:00.340] [580] use_signed_kernel=0, is_unlocked=1, is_tampered=0.", seemingly indicating that the device was unlocked. However, it is not, as I'll mention later.
LGFTMITEM Spam in logcat
On the two VS985 phones I've looked at, both seem to produce a large amount of spam to logcat under the tag "LGFTMITEM". This takes the form of several lines being logged every 500 ms, consistently. I believe that setting the property "sys.lgsetupwizard.status" to "1" should stop it, though I haven't been able to do so successfully yet.
Bootloader Unlocking
One of the main goals of my tinkering has been to find a method for unlocking the VS985 bootloader. I believe I have identified the path to do so while disassembling "aboot", but I do not know how to enable it. I'll try to describe it here. In "sub_F81FF5C" of the "aboot" partition (I created a basic ELF format binary from the partition by trimming the first 40 bytes of the partition dump and then creating a single section ELF file loading that trimmed portion to address 0x0F800000), there is code that verifies the kernel and ramdisk images of the loaded boot partition. The code refers to "FEATURE_LGE_QCT_HW_CRYPTO", if that has meaning to anyone. Before the verification takes place, however, the function calls function "sub_F81FF58" with a memory location passed in R2. If this function call stores the value 0x67661147 in the memory pointed to by R2, the function bypasses all of the verification checks and simply prints "Device UnLock". This is why I believe "fastboot oem-unlock" would not be effective - my bootloader logs still indicate that the bootloader is taking the cryptographic verification path even though I have "unlocked" the device. I've tried to follow the function calls from here, but they get rather complicated and refer to memory locations not within the executable itself, which confuses me. In one of the functions invoked from here, which seems to print out the results of some sort of command, there are the strings "READ_UNLOCK_DEVICE_CERTIFICATE", "UNLOCK_DEVICE_AUTHENTICATION", "ANTI_ROLLBACK", and most interesting to me, "BACKDOOR". I've been having trouble figuring out how this part of the code works, so if anyone has any ideas, I'd be interested in hearing them.
Well, I think that about covers most of what I've found out about this phone. I'd be happy to explain anything in more detail if it's not clear.
IllegalArgument said:
Hi all. First, apologies if this is the wrong place for this sort of post. It's mainly just a collection of my notes on the Verizon LG G3 running stock software update VS98510B, so there are a lot of different topics touched upon. I'm usually pretty shy around forums, but I figured something I've found might be useful to someone else, so I finally decided to post here. Anyway, here's what I've found.
Autorun Installer
This really annoyed me for a while when I first got the phone. Every time I'd try connecting it to my computer, it'd enter some sort of installer mode for LG/Verizon drivers. It would stay in this mode for about 30 seconds unless I manually put it back into ADB mode. After a good bit of digging around, I found out how to disable it without root or any special permissions. Open the stock dialer app, then enter the code "##3328873" and press send. It'll prompt for a service code, which is (of course) "000000". While the Verizon G3 appears to be missing a large chunk of the hidden menus, this section still seems to work. One of the options is a checkbox for "Tool Launcher enable" - uncheck it to disable the Verizon autorun installer.
Sideloading in Recovery Mode
I was curious how IORoot worked, so I started taking it apart. Basically, on the G3, it just uses a .zip sideloaded in recovery mode to copy over the su and related binaries. There's a decent bit of documentation out there on how to create your own .zip for sideloading, but I found one catch - the .zip needs to be signed with the proper key, or recovery will reject it. It turns out that this key is located at "./bootable/recovery/testdata/testkey" in the AOSP project. I forget the exact command for signing the .zip, but using this key, you can create your own sideload applications. Edify provides a nice way to script your application; I used it to create a sideload application to replace the HotspotProvision apk with a slightly modified version that skips the billing checks. Doing so does not require root access, as the sideloaded application appears to run as root by default. Replacing "HotspotProvision.apk" also does not trigger the root detector. However, I also made my own sideload .zip to copy over the su binary I compiled from AOSP - as soon as I booted the phone, the software status indicator changed to modified. I have some more information on that below. If anyone wants either of these sideload applications, I can upload them somewhere with their source, just let me know.
Ramdisk Compression
The boot, recovery, laf, and factory partitions are all mostly in standard format and can be split into the kernel and ramdisk parts with existing tools. However, most tools seem to expect the ramdisk to be compressed using gzip. Since it's not, they'll fail to extract the cpio archive from it. The G3 ramdisk is compressed using LZ4 instead. Once decompressed using the standard LZ4 utility, it has the same structure as a normal boot ramdisk - the cpio archive can be extracted to view the boot filesystem. I haven't really looked into it, but I believe the boot images all have a device tree binary appended after the ramdisk as well.
AT Commands
When looking into the boot process, I stumbled upon the AT command framework for the G3, which proved to be rather interesting. When connected to my computer in ADB mode, the phone exposes two serial ports. One of these ports looks like it's supposed to accept plain-text AT commands, but it also has been rather buggy in registering the end of a command for me. The other port accepts commands in some sort of binary format that I have not taken apart yet. If you want to send AT commands to the phone from ADB shell, write them to "/dev/smd0" and read the response from there. Sometimes, the response is not put on the device for some reason, but instead just printed to the logs under the tag "Atd"; just use "logcat Atd:V" to view them. The requests seem to be handled by "/system/bin/atd", which largely uses "/system/lib/libatd_common.so" to work. Looking through the disassembly showed some interesting things, included what looked like a test command that involved the bootloader unlock status, though I haven't figured out exactly how it works yet. A lot of the commands began with "AT%", which I think is the vendor specific prefix for AT commands typically. For some reason, I couldn't get any of these commands to work, even though some of the standard commands worked fine. One particularly interesting function (to me) was one that claimed to be able to write the software bootloader, SBL1. The function was called "store_sbl1_image"; there are some other functions that affect sbl1 as well. There are also functions for qfuses/QFPROM and other things that may be of interest to us. A lot of these functions access the misc partition through "/system/lib/liblgftmitem.so", so that may be a partition worth looking into.
Volume Key Booting
Entering the dialer command "##228378" and pressing send brings up a menu that has an option called "Device Test". Choosing this option prompts you that the phone will reboot; if allowed, it will reboot into MiniOS mode, which is stored in the "factory" partition ("/dev/block/mmcblk0p40"). This mode allows you to run a number of device tests, though many options are disabled somehow. One interesting thing I've observed is that, if the phone is shut down from MiniOS mode, then turned on by holding the volume down and power buttons simultaneously (possibly while plugged into a computer, I forget if this is necessary), the phone enters a pseudo-recovery mode that vaguely resembles real recovery mode, but is actually implemented after boot. Another volume key command is to hold volume up while powering on and connected to a computer by USB (the USB connection is required). This boots into factory download mode from the "laf" partition("/dev/block/mmcblk0p33"). The only way I've found to exit this mode is to remove the battery from the case. One final note is that while booting into normal mode, but having done so by holding volume down and the power button, the bootloader logs a message that it is going to enter fastboot mode. However, it does not and just boots normally instead. It seems that fastboot can only be activated if aboot fails to boot normally. I've read of people accomplishing this by messing up the "laf" partition and then booting into download mode, but I've not tried it myself.
Root Checker ("/system/bin/rctd")
After already setting my system to the "modified" status, I looked into the root checker executable at "/system/bin/rctd". A quick disassembly showed almost no strings in the binary. This is because they are all obfuscated. To load the strings, as series of instructions store individual characters into the stack at the proper offsets, eventually forming all of the strings needed by the program. Because I don't have the "Pro" version of IDA, I can't just run the executable through the debugger to get the strings out, so I had to resort to writing a really hacky emulator for a few ARM instructions to produce the strings. I only did this for one function, but the results were rather interesting. This function constructed the following string(s): "mt6575 mt6577 /sbin/su ro.hardware /system/bin/su /system/xbin/su /system/sbin/su /data/local/tmp/su /system/bin/busybox /system/xbin/busybox /data/local/tmp/busybox /system/app/Superuser.apk /system/app/SuperUser.apk /system/app/superuser.apk /system/app/SuperuserPro.apk /data/local/tmp/Superuser.apk /data/local/tmp/SuperUser.apk /data/local/tmp/superuser.apk /data/data/com.noshufou.android.su". I'm assuming this is a list of all of the files that the program looks for to determine if the phone has been rooted. In theory, using some way of randomly naming these files could prevent the root checker from detecting a rooted presence. If anyone who has IDA Pro wants to run "rctd" through the debugger, they might find more interesting things.
fastboot oem-unlock
While I've not tried booting into fastboot mode myself, I have "manually" executed the "fastboot oem-unlock" command. By disassembling the "aboot" partition ("/dev/block/mmcblk0p5"), I found that oem-unlock writes the value 0x01 to offset 0x1FFE10 of the "aboot" partition. I replicated this action with the command from a root shell "echo -en '\x01' | dd of=/dev/block/mmcblk0p5 bs=1 seek=2096656 count=1 conv=notrunc". After doing so and rebooting, which seemed to take longer than usual, I checked the kernel logs in "/data/logger/kernel.log*", and, in the bootloader logs section, there was a line displaying "[ 0.355056 / 01-01 00:00:00.340] [580] use_signed_kernel=0, is_unlocked=1, is_tampered=0.", seemingly indicating that the device was unlocked. However, it is not, as I'll mention later.
LGFTMITEM Spam in logcat
On the two VS985 phones I've looked at, both seem to produce a large amount of spam to logcat under the tag "LGFTMITEM". This takes the form of several lines being logged every 500 ms, consistently. I believe that setting the property "sys.lgsetupwizard.status" to "1" should stop it, though I haven't been able to do so successfully yet.
Bootloader Unlocking
One of the main goals of my tinkering has been to find a method for unlocking the VS985 bootloader. I believe I have identified the path to do so while disassembling "aboot", but I do not know how to enable it. I'll try to describe it here. In "sub_F81FF5C" of the "aboot" partition (I created a basic ELF format binary from the partition by trimming the first 40 bytes of the partition dump and then creating a single section ELF file loading that trimmed portion to address 0x0F800000), there is code that verifies the kernel and ramdisk images of the loaded boot partition. The code refers to "FEATURE_LGE_QCT_HW_CRYPTO", if that has meaning to anyone. Before the verification takes place, however, the function calls function "sub_F81FF58" with a memory location passed in R2. If this function call stores the value 0x67661147 in the memory pointed to by R2, the function bypasses all of the verification checks and simply prints "Device UnLock". This is why I believe "fastboot oem-unlock" would not be effective - my bootloader logs still indicate that the bootloader is taking the cryptographic verification path even though I have "unlocked" the device. I've tried to follow the function calls from here, but they get rather complicated and refer to memory locations not within the executable itself, which confuses me. In one of the functions invoked from here, which seems to print out the results of some sort of command, there are the strings "READ_UNLOCK_DEVICE_CERTIFICATE", "UNLOCK_DEVICE_AUTHENTICATION", "ANTI_ROLLBACK", and most interesting to me, "BACKDOOR". I've been having trouble figuring out how this part of the code works, so if anyone has any ideas, I'd be interested in hearing them.
Well, I think that about covers most of what I've found out about this phone. I'd be happy to explain anything in more detail if it's not clear.
Click to expand...
Click to collapse
You should rename the title of your thread to something more likely to be read by devs trying to unlock the bootloader. It's too generic in my opinion. Excellent work so far, though. Thanks for your efforts and interest!
Nice to see anyone working on an unlock, also thanks for sharing.
---------- Post added at 02:33 AM ---------- Previous post was at 02:25 AM ----------
I forwarded the post to Justin case to see if he may be able to get in touch
This was way over my head. Have you PM'd @autoprime or @thecubed (aka IOMonster)? They are a couple of the devs working on unlock.
Sent from my VS985 4G
Howdy there!
Just in time, too - since I just got back from vacation!
Hop on IRC (freenode) and join #lg-g3 and ask for IOMonster, and mention this thread. I'd be happy to explain what I can to you.
You've followed excellent logic and have come to many of the same conclusions as we have during our exploration of the device. Factory mode reads FTM items, and can enable/disable menu options at will (or you could just extract it like a boot.img and load the lgeftm_* binaries into IDA and see what they do).
RE: AT commands, there's a lot of good logic in there, however at the moment nothing that looks to give us our unlock.
RE: Unlocking, you're close, but a bit far off. There's some special sauce LG is using for unlocks, and last I was looking I believe LGE is obfuscating bits of code with a multi-stage loader. I'll discuss more about this on IRC if you're interested and the rest of the guys on IRC are alright with me doing so.
One of those memory addresses is a function pointer - before I left for vacation we were working on dumping the memory to pull the decompressed function out of RAM on another device that uses a (very) similar strategy.
I look forward to talking to you on IRC!
Hope you enjoyed I'm sure a much needed vacation.. Hopefully soon someone will be able to crack this boot loader and free the G3 variants.
They will unlock it because how can the great device be locked and have only the tmobile version be the only one unlocked... Lol that's crazy. They will unlock it in time
I think your right in time ,unfortunately these guys have full life schedules that don't allow them to stay on it all day! I hope all the g3 community gets to enjoy the full potential of such a great device in the future.
OP @IllegalArgument
Hats off for your first loaded post on XDA, really reassuring to see as many capable devs tinkering with this, welcome and keep em coming
dabug123 said:
....I hope all the g3 community gets to enjoy the full potential of such a great device in the future.
Click to expand...
Click to collapse
Near future hopefully
nerdo said:
OP @IllegalArgument
Hats off for your first loaded post on XDA, really reassuring to see as many capable devs tinkering with this, welcome and keep em coming
Near future hopefully
Click to expand...
Click to collapse
Will see im hopeful but I won't be upset since nexus is close
Nexus won't run on Verizon, you can book that.
Sent from my HTC6525LVW using Tapatalk
dbatech99 said:
Nexus won't run on Verizon, you can book that.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
Yep agreed, I'm making the switch
dabug123 said:
Yep agreed, I'm making the switch
Click to expand...
Click to collapse
With Xposed framework and the right modules I can make this stock ROM almost like any custom ROM. It will definitely hold me over until they can unlock it.
Jank4AU said:
With Xposed framework and the right modules I can make this stock ROM almost like any custom ROM. It will definitely hold me over until they can unlock it.
Click to expand...
Click to collapse
My thoughts exactly, and with the Wifi tether mod, I'm content, for now.
Jank4AU said:
With Xposed framework and the right modules I can make this stock ROM almost like any custom ROM. It will definitely hold me over until they can unlock it.
Click to expand...
Click to collapse
I enjoy it with xposed..Not the same in the end but the g3 is a great won't ever say different.
Ooh, exciting. I can't wait.
kdouvia said:
Ooh, exciting. I can't wait.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Jank4AU said:
Click to expand...
Click to collapse
Fail lol[emoji13]
Interesting read OP.
Jank4AU said:
Click to expand...
Click to collapse
Haha, bro, I was serious this is the most information I've heard about the boot loader unlock in awhile. I love the meme though. :victory:
I successfully installed Android Revolution 9.3 recently so thought I'd give some details for reference to anyone else it might help as I made a mistake (on purpose of course, just to make things interesting!) and encountered a few road blocks that made things a little tricky. I've not posted here many times and wouldn't claim to be an expert but have quite a bit of experience with Android (Kindle Fire was my first device to which was an uphill struggle all the way) and other tech experience with PC's and some Linux OS.
If you have a device with different specifications please be very careful when it comes to downloading and using software on your device. Doing so with the incorrect software (eg. software for a different device, wrong CID number...) can be disastrous so please be careful - soft-bricking is one thing but a hard-brick is always possible if you don't pay careful attention.
If anything here doesn't make sense or there are processes you don't understand, step back and re-consider before doing anything. You carry out these procedures at your own risk and I accept no liability. Think, think and think again, it's worth taking the time.
First things first, I have an HTC One m7 that I rooted and custom ROM'd almost as soon as I got it, so Root access is a pre-requisite for these procedures and everything described here is done with a Windows operating system.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[/IMG]
If you don't know what “Root Access” is or need help with it, here's a great guide and there is an abundance of other information on XDA for just about any question you might have.
I originally flashed TWRP 2.6.0.1 Custom Recovery and installed Trickdroid 11.0.0, an excellent, customisable ROM that gave me almost no problems apart from APEX Launcher not working, NOVA Launcher works brilliantly though. I haven't found any direct upgrades (please correct me if I'm wrong) but as it stands it's still a very smooth and stable ROM. My other interest was to improve my phone through firmware upgrades, which is a different process from those described here and require S-OFF (Security Off) unless you're using OTA (Over The Air) Updates, which requires a locked bootloader!
Initial Upgrade Problems
I'm quite fastidious when it comes to these things, researching, collecting and organising everything I need before hand so I was pretty annoyed that I missed the note towards the bottom of the Android Revolution HD (ARHD) page where it states that TWRP 2.6.3.3 or newer is required - I can confirm this is indeed the case! I also did a data wipe in TWRP before starting the AROMA installer - not sure this was problematic but it probably didn't help and certainly wasn't necessary so I would advise against doing that.
Whilst the AROMA installer completed apparently successfully (apart from one “error” message - set_perm: some changes failed), it became very clear it was not successful when the phone failed to boot normally and instead simply booted into Recovery every time. I was quite worried I was in dire straits because I didn't have any back up or alternative ROM on the SD card at the time, and was about to discover the joys Windows 8.1 brings to certain processes - more on that later.
So I was faced with a semi-useless phone that allowed me to get into the bootloader and Recovery but not much else, however it's a credit to TeamWin because TWRP continued to function flawlessly, despite my best efforts to screw everything up! No variation or combination of wiping outside of or in AROMA and re-installing ARHD achieved anything new - the partitions weren't mounting or being read correctly (the usb partition in particular “could not be mounted” according to TWRP), so it was clear I was sufficiently over the edge and needed to back up before I did any permanent damage.
Solutions
All of the steps I took may not be absolutely necessary, but because it was quite screwed up I was very keen to wipe the slate and get everything back to a point I was happy everything was fully functional.
The first problem was that fastboot was not working from the bootloader, by which I mean I was unable to use fastboot commands from Windows, and the phone wasn't recognized by the Device Manager, regardless of driver's installed, which I knew were correct - this was a Windows 8.1 quirk, however while the phone was in Recovery I was able to communicate via adb.
So connected to the computer, I opened a command prompt: simplest way to do this is opening the folder where adb is on your computer, which is usually your main hard drive eg. C:, where an adb folder will have been created during the installation of the tools, right-clicking in that folder with the SHIFT key held down, then selecting “Open command window here”:
C:\adb>adb push Trickdroid.zip /sd/
[If you don't follow that method, you simply have to open a standard Command window and navigate to the location of your adb folder eg. C:\>cd adb]
NOTE: the "/sd/" command at the end here is important as it tells adb the location for the file to go on your phone (the internal SD card). I've seen this push command in other tutorials without this part and the operation has failed.
You'll get a few lines in the command prompt window confirming the process starting and completing.
Then I followed the usual installation procedure for a custom ROM through TWRP (Install> Select Trickdroid .zip) - I used this ROM because I had it to hand and knew it worked.
Once the install was completed I had a functional phone again and could start to rebuild the shattered pieces of my pride. As mentioned before, I didn't have a backup on the phone - this was because I lost my original stock backup thanks to a self-destructing hard-drive (avoid Seagate hard drive's), so I started to hunt around. Thanks to the wonderful contributor's of XDA I found some excellent resources, but which you use depends on your preferred approach, and what you want to achieve but here are a few.
MIKE1986's STOCK ROM's
RUU Collection's
Nandroid Collection's
HTC Guru's Reset
Keep in mind - each of these resources have very important and specific processes that go along with each of them, so be very careful when it comes to using them.
Windows 8.1 Quirks
Windows 8.1 (originally) had some difficulty talking to attached Android devices through fastboot, and whilst having the correct HTC drivers is vital, I found a thread relating to a Windows Registry issue, requiring a Windows Update (which you may have already received) and an update to the Windows Registry (which is crucial).
Installing HTC Sync will give you the relevant drivers, but the program itself can interfere with many processes, plus it's a bit rubbish so if you uninstall it (just HTC Sync Manager) from the “Uninstall Programs” application in the Windows Control Panel, you'll just be left with the drivers and no unnecessary bloatware on your computer.
There's a simple download and instructions on how to apply the relevant changes to the Windows Registry which can be found here. If you haven't done anything like this before it can look quite intimidating but rest assured, follow these instructions to the letter and you'll be fine, maybe don't try screwing around with the other registry files though!
Recovery - Refresh and Upgrade
Whilst trying to get the phone to boot (in it's semi-disabled condition) I played around with the backup functions in Recovery, which unsurprisingly didn't work. I also deleted some of the folders within the TWRP “Backups” folder, thinking they might be confusing or causing some conflict.
So, to start afresh, I flashed a stock recovery, which can be found here.
Your phone needs to be in fastboot mode and attached to your computer - power off, then hold the volume down button and power button until the bootloader opens. Your recovery image needs to be in the adb folder, preferably named “recovery.img”. Open the Command Prompt for adb (right click in the adb folder whilst holding the SHIFT key) and flash the .img file over to the phone.
C:\adb>fastboot flash recovery recovery.img
Again you'll see a few lines in the command prompt window confirming the process starting and completing, once it's done shutdown and reboot the phone.
Of course the stock recovery isn't much use in terms functionality, and this process effects the ROM, essentially re-setting it - your SD will be fine but if you had eg. text messages, they'll be deleted so back anything like that up before doing this.
I shut down and re-booted once more just to be sure everything was ok, and then flashed the custom recovery in the same way as the stock, but now was the time to jump to a more up to date TWRP (or recovery of your choice) - I went with 3.0.0 in this case. Delete the stock recovery from the adb folder, then save the new custom recovery .img file (again re-naming it to “recovery.img”) in the same folder before fastboot flashing with the command prompt window:
C:\adb>fastboot flash recovery recovery.img
Sweet, now we've got a lovely new TWRP that looks a little different than the old version but with the same wonderful UI and functionality, and a few extras. The first time I booted into Recovery it asked me if I would like TWRP to be able to write onto the phone, or remain as “read only”. Whilst you might want to do this, there's no real reason and it kind of defeats the purpose of the recovery, plus you're not going to be able to do a backup or install files so just agree to that and you're good to go.
TWRP Information & Resources
System/ROM
Now running smoothly I was ready to upgrade, but to ensure there were no unpleasant ghosts in the system I went back to a stock ROM first. There's a variety of options as mentioned earlier, including any backup you may have saved yourself, but I went with a stock ROM provided by mike1986 this time which can be found here, whose incredible work and contributions can't be underestimated.
[NOTE: This *STOCK* ROM is NOT the same as the “out of the box” system my phone originally came with, which was 4.1.2 “Jellybean”, HTC Sense 5.0, however it served the purpose of wiping the phone slate clean to a stock system.]
I used the deodexed 6.09.401.12 - basically the difference between odexed and deodexed is the .apk structure - it's most specifically related to modifications and avoiding conflicts in the ROM. Here's a thread if you want to learn a bit more about it.
So just like any other ROM, copy the .zip file onto the SD card - simplest way to do this is having your phone connected to your computer, open up the browser window and navigate to your SD card, selecting a suitable location, just make sure you know where it is! (You can push it over via adb but it's really not necessary.) Then boot into Recovery, click Install, navigate to the .zip file location and select One_6.09.401.12_deodexed.zip (or whichever one you're using), then swipe to install.
The AROMA installer will kick in so just follow the on-screen instructions, reading each step carefully and soon you'll have the ROM installed with the usual Root access.
Don't forget the first boot after an install like this takes some time - that's completely normal, including an “Optimizing Apps” window before you get to the home screen so just be patient.
If you want to stop here then obviously that's your choice, however if you wanted to get/use OTA updates you'd need to follow some other steps to be totally stock, including locking your Bootloader, and there's a wealth of information here if that's your aim.
Custom ROM
Onto the Custom ROM of your choice - I recommend you do some research and check out reviews to find what you like the look of, but I've gone with mike1986's Android Revolution HD this time round. Download the ROM .zip and just like before, move it to your phone's SD card (no point in keeping the Stock ROM on the phone as well so delete that first to free up space, though you might want to keep it on just in case until the upgrade has completed successfully).
Reboot into Recovery via the bootloader, click Install and navigate to the .zip file, select Android_Revolution_HD-One_93.0_ef29f7.zip and swipe to install, carefully following the steps in AROMA and installing according to your preferences.
Once again after completion, reboot and be patient whilst the first boot runs its course and you're all set!
Don't forget you'll need to install the Xposed Framework to take full advantage of the Sense Toolbox within ARHD, without it simply won't work fully - it will work at a basic level but you'll get a warning/notification that you don't have full functionality. You can find lots of detailed information about this here - read it carefully because again, the correct software for your phone is very important - basically you need the latest installer, which is an .apk, and the relevant .zip files for your device.
For my phone (HTC One m7 - Quad-core 1.7 Ghz Snapdragon (Krait) 600 CPU, ARMv7 Soc (2Gb RAM) ARM CPU), one of the packages wouldn't install, claiming it wasn't correct for my device. Why exactly I'm not sure (because I absolutely, positively got the right packages!) so I'll update this when I know more, however the Xposed Framework software has worked fine since then, I'm not getting any error messages, it's all up to date and working fine.
That's it! Explore you're new ROM and enjoy. I hope this is helpful, if you've got any questions feel free to ask and I'll do my best to help. Much credit and thanks go to the people I've looked to for advice, and who have done incredible work compiling, modding and hosting the files used for these processes.
Thank and donate whatever you can to them so they can continue the sterling work.
Particular thanks to:
Mike1986
crushalot
matt95
sToRm1nG
… and anyone else in the XDA-Developers community I haven't named specifically but have been exceptionally helpful in sharing their knowledge and resources.
Hello,
I'm having an odd issue with Remix OS for PC, and wanted to see if anyone else experienced this and hopefully found a resolution. Please see the bottom of the thread for info on my PC setup. My laptop is definitely more than powerful enough to handle remix, and it used to run fine, but now I seem to have the following issues after not booting into Remix for a while:
***Wifi does not automatically connect, it only connects if I click the wifi icon in the tray (then it connects to my network automatically)
***Nearly all apps will not open, including the Settings app. I'll click on an icon on the desktop, and the icon lights up, registering my click, but the app never opens and the icon stays lit as if something froze. However, I can still "swipe" from the left desktop to the right one, and vice versa.
***When attempting to install an app (Eventually, without any rhyme or reason that I've noticed, I can open the Play Store and maybe the settings app), the app hangs on Installing after it downloads. I've tried waiting a good 20 minutes, but I know the apps install much quicker on this laptop, and I've tried this with small apps.
***Similarly to the above, clicking the Remix OS menu button does nothing as well.
With those symptoms in mind, it seems like there's something holding the system back, but the actual GUI performance is fine. For example, there's no lag or hesitation when an app finally eventually opens or when I click around through the Settings app (when it finally opens). It doesn't seem to only be with graphic intensive apps either, as I tried a simple text/memo app and when that one eventually opens, the desktop background is black and the app window is black with only a menu near the top.
My attempts to fix it
So far, I've tried running an e2fsck -f data.img command to repair the data.img file. It didn't appear to report any issues and the problem did not go away. I've rebooted the thing about a billion times, no luck! Getting into the Settings app is hit or miss and I haven't really had any idea of what setting might help, and installing third party apps appears to not be an option either.
The only other option I could think of would be to backup my data.img and reinstall the OS, and then restore the data.img file, but this seems like it will restore the problem with it. Also, I haven't experienced any problems in Windows, so I don't think there is any issue with the drive. Sorry for such a long thread, just wanted to be detailed!
Any ideas are much appreciated!
My PC: Lenovo Ideapad y510p
Windows OS: Windows 10 64-Bit
Remix OS for PC: 3.0.207 dual booted with the above Windows 10 installation
Hard Drive: 500GB SSD drive
RAM: 16GB
I don't have any of those issues. My issues are a bit different...
I can't seem to find a copy of RemixOS 3.xx that actually has "true" root access. I know there is a method you can use to remount the volume as r/w, but since I am running it from a flash drive, I apparently cannot access any of the system files in Windows with hidden files and folders visible. And, after first boot the USB drive running the OS will somehow end up with a corrupted "REMIXOSDATA" partition.
Good luck on your quest.
ViolentNeurosis said:
I don't have any of those issues. My issues are a bit different...
I can't seem to find a copy of RemixOS 3.xx that actually has "true" root access. I know there is a method you can use to remount the volume as r/w, but since I am running it from a flash drive, I apparently cannot access any of the system files in Windows with hidden files and folders visible. And, after first boot the USB drive running the OS will somehow end up with a corrupted "REMIXOSDATA" partition.
Good luck on your quest.
Click to expand...
Click to collapse
Thank you for the response! In reading the issue you're having, I'm wondering Remix OS for PC, in its current state, is more susceptible to corruption issues in under some circumstances rather than others. When I first installed it, I installed the 64-bit version and I kept having issues where I'd boot it up and it suddenly would not start. I found somewhere on a forum where someone recommended to just use the 32-bit version and the issue went away for a long time, until I had the issue described in my original post. I'm wondering if it just isn't stable enough yet to be run from a flash drive, as it seems to me like it has issues with being easily corrupted.
This brings me to my next comment, I was able to fix my issue! I tried a couple things that didn't work, reinstalling Remix and then choosing YES to erase the entire virtual drive, then copying a backup of my original data.img back into the directory so I don't have to reinstall everything. This didn't fix the issue, so instead I downloaded the 64-bit version and installed it, but this time I chose NO on the prompt to erase my data.
Upon booting into Remix, it gave the standard Android message about optimizing apps and is now running good. I wish I did this workflow with the 32-bit version, as I'm wondering if it would have worked. I suspect I'll experience the same issues I originally experienced with the 64-bit version.
Anyway, I hope this may shed any light on how you can try to resolve your issue. Good luck!