This method is not mine. Original thread is HERE. I am simply making it work for our Verizon LG x8.3 VK815.
With the introduction to the newer OTA update, rooting ability using the old method has been broken. This means we have to follow the new method for achieving root similar to the LG G4. This requires pulling the system image, injecting root, pushing the system image back to the device.
Here are the steps to Root your Verizon LG x8.3 VK815
Follow JUST the first step here to get setup with the Download Mode and send_command:
http://forum.xda-developers.com/g4/general/lg-g4-100-root-success-directives-root-t3180586
It has links to the VERIZON drivers and the resources to get this done.
Here is the specifics for the LG VK815 to backup SYSTEM image:
STEP 1: BACKUP SYSTEM IMAGE said:
From Download Mode, using the send_command.exe
Code:
dd if=/dev/block/mmcblk0 bs=8192 skip=44992 count=458752 of=/data/media/0/system.img
Once that is done, we have to change permissions
Code:
mv /data/media/0/system.img /data/media/0/Download
Code:
chown media_rw:media_rw /data/media/0/Download/system.img
Code:
chmod 664 /data/media/0/Download/system.img
Code:
chcon "u:object_r:media_rw_data_file:s0" /data/media/0/Download/system.img
Type LEAVE to reboot back into Android. Open a ADB terminal and copy the System.img to your PC
Code:
adb pull /storage/sdcard0/Download/system.img .
Click to expand...
Click to collapse
STEP 2: INJECT ROOT (SKIP STEP IF VERSION ISN'T LISTED BELOW) said:
You need a Linux environment for this.
I used VirtualBox and this Ubuntu 12.10 Image:
http://sourceforge.net/projects/vir...untu Linux/12.10/ubuntu-12.10-desktop-i386.7z
user/pass: ubuntu/reverse
Load up Ubuntu and Log in. Download Inject Root Files. Copy system.img and contents of Inject_Root_G4.zip to desktop.
Load up a Terminal and "cd Desktop"
Code:
sudo chmod +x autoroot.sh
sudo ./autoroot.sh
Your "system.img" should change to "rootedsystem.img"
Copy this out of your VM and copy back to the root of your internal storage on your LG G Tab x8.3 VK815
Click to expand...
Click to collapse
I am uploading the 11A Stock OTA System Image Here:
StockSystem
Code:
MD5:cda4e8ce36f009403a45f00f29c58fff
Here is the ROOTED 11A OTA System Image:
Download Rooted System Image - Mirror
Code:
MD5: 165bc9152f20e66623477870c574500b
STEP 3: PUSH ROOTED SYSTEM IMAGE said:
Boot back into Download Mode. Now we copy and install the rootedsystem.img into our operating system partition:
Code:
dd if=/data/media/0/rootedsystem.img bs=8192 seek=44992 count=458752 of=/dev/block/mmcblk0
Type LEAVE and reboot.
Click to expand...
Click to collapse
ENJOY!
Special Thanks to @smason for help and @hackarchive for the original walkthrough!
{
"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"
}
Wrong device, wrong Forum.
Please ask in the Q and Forum for your device - thanks.
Yea the new update breaks the existing root methods. There currently is no way TO root, but I think we can root it similarly like we do on the G4.
You basically pull the system image (using the command I posted), open it up on the PC, copy in the root files, and push the whole root system image (3.5gb) back to the phone.
I would recommend doing a factory reset and do not sign in to google, install apps, etc. The tablet is 16gb and you'll have both images on your G4. You might not have enough internal storage space with apps installed.
I do not have the UPDATE installed, nor do I want the update unless I KNOW it can be rooted. So if you can pull the system image for me and upload it, I will try to inject the root and you can try it. You'll have BOTH system images on your tablet, so if the rooted one doesn't work, you can just flash the original.
Anyone on the OTA able to pull a stock system image to upload?
I have no intention of taking the OTA if it cannot be rooted. I will help anyone looking to root the new update.
player911 said:
Anyone on the OTA able to pull a stock system image to upload?
I have no intention of taking the OTA if it cannot be rooted. I will help anyone looking to root the new update.
Click to expand...
Click to collapse
Hi there, im now trying to root it using this method. If its right i would update my img :cyclops:
I am having problems copying the image off of the device. I tried doing it though adb pull and shell and just a straight copy. Keep getting permission errors. I rerooted my 11A tab to try permissions.
player911 said:
I am having problems copying the image off of the device. I tried doing it though adb pull and shell and just a straight copy. Keep getting permission errors. I rerooted my 11A tab to try permissions.
Click to expand...
Click to collapse
I have the same problem too, i can't move/copy the system.img. Any solutions of this?
Update to pull system.img
Code:
#mv /data/media/0/system.img /data/media/0/Download
#chown media_rw:media_rw /data/media/0/Download/system.img
#chmod 664 /data/media/0/Download/system.img
#chcon "u:object_r:media_rw_data_file:s0" /data/media/0/Download/system.img
#ls -laZ /data/media/0/Download/system.img
-rw------- media_rw media_rw u:object_r:media_rw_data_file:s0 system.img
#
Thanks to @smason for the help.
I have pulled the stock OTA system image, injected root, and about to flash it now. If successful, I will upload the rooted system.img.
The OP is sort of a mess right now while I am adding notes and steps. If I am successful, I will organize it better. The steps for flashing is 1 line
EDIT!
SUCCESS!
Another thread that should be stickied.
Agreed as this method will probably be the standard for all updates going forward unless LG blocks it.
Unlike the G4, additional steps need to be taken to get the image off your device because they locked down permissions.
I am interested in hearing of how this works for others. I've been all over this for a while and my instructions may skip details.
Is the link for the rooted system file broken?
Skizzy034 said:
Is the link for the rooted system file broken?
Click to expand...
Click to collapse
I confirm that the download link doesn't work for me. Like you said in the other thread, it just takes me to the site's main page.
roirraW "edor" ehT said:
I confirm that the download link doesn't work for me. Like you said in the other thread, it just takes me to the site's main page.
Click to expand...
Click to collapse
=/ That sucks.
This worked for me. I FINALLY got my x8.3 rooted. Uploading the rootedsystem.img file to FileDropper right now. Will share the link as soon as it is uploaded.
Edit:
FileDropper wouldn't hand over the link to the file so I'm uploading it to MediaFire now. Will post link as soon as it is uploaded.
Edit:
File is uploaded (Remove spaces): www . mediafire .com /download/ qnx4f9bzxage96o/ rootedsystem.img
Cool!
I'll update the OP links with your mirror.
Can you provide a MD5 checksum? I think I zipped the original to save file size so the MD5 will be different.
Looks like both of my links have died. I'll reupload the Original and Rooted images up to other services tonight. I was excited when I finally got it and threw it up on the first host that would support the size.
player911 said:
Cool!
I'll update the OP links with your mirror.
Can you provide a MD5 checksum? I think I zipped the original to save file size so the MD5 will be different.
Looks like both of my links have died. I'll reupload the Original and Rooted images up to other services tonight. I was excited when I finally got it and threw it up on the first host that would support the size.
Click to expand...
Click to collapse
I'd be glad to post the MD5... as soon as I figure out how to get that... I have no idea, never done that before. xD Normally I just wait for everyone else to fix things like this and I download their hard work but I decided it was time for me to step up to the plate.
EDIT:
I believe I got the MD5 for it. I used WinMD5Free v1.20 so I hope I'm not just being an idiot here (Never learn until you stick your neck out.)
MD5: 5e151c2126263423a1602fd39eb2db47
So the only step we need to do is push the system image you provided?
I would back up your system image too, but not needed.
You should just copy the rootedsystem.img to your internal storage and use the DD command from Download mode to copy it over.
player911 said:
I would back up your system image too, but not needed.
You should just copy the rootedsystem.img to your internal storage and use the DD command from Download mode to copy it over.
Click to expand...
Click to collapse
Will an android terminal work?
Related
Credits/Disclaimer
Code:
[U][B]
This is not my guide, you dont have to thank me for this.
Thanks to Ocnbrze over at AndroidForums for this.
we are not responsible if your device(s) cause(s) a nuclear war[/B][/U]
This will show you how to FULLY unroot your evo to stock. S-ON *****(LOCKED OOW)*****
THIS ONLY WORKS IF YOU USED HTCDEV METHOD!!!!!
Please read thru this guide once or twice before actually taking steps !
Your phone MUST be on a stock sense rom so go get that installed now !
Download these files if you do not have them
ADB.exe http://d-h.st/Vsv
FastBoot.exe http://d-h.st/KB3
AdbWinApi.dll http://d-h.st/MJn
flash_image.zip http://themikmik.com/attachment.php?attachmentid=5377&stc=1&d=1327588554
mtd_eng.zip http://themikmik.com/attachment.php?attachmentid=5378&stc=1&d=1327588554
PC36IMG_SuperSonic_GB_Sprint_WWE_4.67.651.3 http://d-h.st/n1U
Before you do anything else, your phone MUST be on a stock sense rom !
step #1 downgrading the misc partition
1.download the first three files and create a folder and call it android then move the downloaded files to the android folder.(you should have already have this setup when you rooted with HTCdev)
2.download and install (do not run) htc sync: http://www.mediafire.com/?cdcjs0ue8tne4cy
3.connect your phone to the pc via usb cable
4.we need to extract and then move the flash_image and the mtd-eng files on to the sd card. make sure that you do not put the extracted files in any folders. they need to be on the root of the card (very top level)
5.change the setting from disk to charge only, make sure that usb debugging is turned on, settings>apps>development>check usb debugging, and lastly make sure that fastboot is disabled, settings>apps>uncheck fastboot.
6.on your pc hold shift while right clicking on the android folder. select open command window here option.
7. in the command window type:
Code:
[B][I]adb shell
ok you should get # in the command window if not then something went wrong.
if you do get # then type:
Code:
cat /sdcard/flash_image > /data/flash_image
then:
Code:
chmod 755 /data/flash_image
and last:
Code:
/data/flash_image misc /sdcard/mtd-eng.img
the command screen should look like this when all the commands are entered:[/I][/B]
{
"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"
}
download the 4.67 PC36IMG file and rename it by deleting everything but the PC36IMG part in the name. make sure not to add an extra zip as windows hides extensions.
move it to the root of the sd card that means on the top level of the card and not in any folders.
power off then press and hold power+vol down. this will take you to the bootloader. if you named the file right and it is on the root of the card then it will ask you to update. select yes.
before you reboot your phone double check your bootloader screen. at the top it should say locked and your hboot should be 2.18 with s-on. if that is what you see then congrats!!!!!!!!!! you are now unrooted!!!!!!!!!!!!
XenonV said:
First things first- Not my guide, You are fully responsible for whatever happens. It is not XDA's fault, its not my fault, its all on you.
This will show you how to FULLY unroot your evo to stock. S-ON *****(LOCKED OOW)*****
THIS ONLY WORKS IF YOU USED HTCDEV METHOD!!!!!
Download these files if you do not have them
ADB.exe http://d-h.st/Vsv
FastBoot.exe http://d-h.st/KB3
AdbWinApi.dll http://d-h.st/MJn
flash_image.zip http://themikmik.com/attachment.php?attachmentid=5377&stc=1&d=1327588554
mtd_eng.zip http://themikmik.com/attachment.php?attachmentid=5378&stc=1&d=1327588554
PC36IMG_SuperSonic_GB_Sprint_WWE_4.67.651.3 http://d-h.st/n1U
Now lets begin
step #1 downgrading the misc partition
1.download the first three files and create a folder and call it android then move the downloaded files to the android folder.(you should have already have this setup when you rooted with HTCdev)
2.download and install (do not run) htc sync: http://www.mediafire.com/?cdcjs0ue8tne4cy
3.connect your phone to the pc via usb cable
4.we need to extract and then move the flash_image and the mtd-eng files on to the sd card. make sure that you do not put the extracted files in any folders. they need to be on the root of the card (very top level)
5.change the setting from disk to charge only, make sure that usb debugging is turned on, settings>apps>development>check usb debugging, and lastly make sure that fastboot is disabled, settings>apps>uncheck fastboot.
6.on your pc hold shift while right clicking on the android folder. select open command window here option.
7. in the command window type:
Code:
[B][I]adb shell
ok you should get # in the command window if not then something went wrong.
if you do get # then type:
Code:
cat /sdcard/flash_image > /data/flash_image
then:
Code:
chmod 755 /data/flash_image
and last:
Code:
/data/flash_image misc /sdcard/mtd-eng.img
the command screen should look like this when all the commands are entered:[/I][/B]
download the 4.67 PC36IMG file and rename it by deleting everything but the PC36IMG part in the name. make sure not to add an extra zip as windows hides extensions.
move it to the root of the sd card that means on the top level of the card and not in any folders.
power off then press and hold power+vol down. this will take you to the bootloader. if you named the file right and it is on the root of the card then it will ask you to update. select yes.
before you reboot your phone double check your bootloader screen. at the top it should say locked and your hboot should be 2.18 with s-on. if that is what you see then congrats!!!!!!!!!! you are now unrooted!!!!!!!!!!!!
Click to expand...
Click to collapse
I've actually been dealing with this most of the day trying to unroot and go back 100% stock and have had no success. It was suggested elsewhere that I need to be on a stock rom? I'm dl'ing one now to try as I am currently on an ics rom.
yes you do need to be on a stock sense rom so download a stock sense rom, and then follow the guide
XenonV said:
yes you do need to be on a stock sense rom so download a stock sense rom, and then follow the guide
Click to expand...
Click to collapse
Perhaps a good bit of info to add to the op
Relentless D said:
Perhaps a good bit of info to add to the op
Click to expand...
Click to collapse
already on it, thanks
So I noticed you said this isn't your guide, but I see no credits in your post for where the guide originated, or who originally wrote the info? I'm sure this will help a lot of people though.
Captain_Throwback said:
So I noticed you said this isn't your guide, but I see no credits in your post for where the guide originated, or who originally wrote the info? I'm sure this will help a lot of people though.
Click to expand...
Click to collapse
i dont know who the original writer is, which is why. if i know then i always list that info :good:
XenonV said:
i dont know who the original writer is, which is why. if i know then i always list that info :good:
Click to expand...
Click to collapse
Where did you get it from, then?
It looks strikingly similar to this guide:
http://androidforums.com/evo-4g-all-things-root/526575-guide-unrooting-gingerbread-2-3-5-a.html
In fact, the inordinate number of exclamation points and the use of my command prompt screenshot makes me think it originated over there.
Captain_Throwback said:
Where did you get it from, then?
Click to expand...
Click to collapse
somebody PM'd me the guide on another website (the tech game) , just the text, no link
XenonV said:
somebody PM'd me the guide on another website (the tech game) , just the text, no link
Click to expand...
Click to collapse
http://androidforums.com/evo-4g-all...-rooting-gingerbread-2-3-5-dummies-guide.html
If this is where it originated (as it seems to have) it was written by user oznbrze at androidforums.com
Relentless D said:
http://androidforums.com/evo-4g-all...-rooting-gingerbread-2-3-5-dummies-guide.html
If this is where it originated (as it seems to have) it was written by user oznbrze at androidforums.com
Click to expand...
Click to collapse
problem solved thanks :good:
and yes this is my guide. however, you do not need to be on stock sense, just not on ics roms for this to work. just throwing that out there.
I tired this and when I put the first command in the window I get a $ sign not the # sign can some one help please..
bgsl1ck said:
I tired this and when I put the first command in the window I get a $ sign not the # sign can some one help please..
Click to expand...
Click to collapse
make sure you are running command prompt as admin. or logged in to an admin account. and all the files are in correct directories
bgsl1ck said:
I tired this and when I put the first command in the window I get a $ sign not the # sign can some one help please..
Click to expand...
Click to collapse
Are you running a rooted ROM? You need to have root access for this to work. Try typing "su" at the prompt and see if it changed to a #.
thanks
Can this be done using a Mac?
XenonV said:
make sure you are running command prompt as admin. or logged in to an admin account. and all the files are in correct directories
Click to expand...
Click to collapse
i have tried that and it still doesnt work, any help!?
im running a brand new computer like seriously out of the box, windows 7 ultimate and it wont give the #
Chirpout said:
Can this be done using a Mac?
Click to expand...
Click to collapse
yes, i believe the guide states something about that..not exactly sure, you can also use google for more help
Hi, I know this is really out of date, but I have to send my phone back because the screen is cracked (inner touch screen) and I wanted the phone to be completely stock. I never rooted the phone. I only unlocked the bootloader. I found this thread hoping I could relock the bootloader to make it look like I never unlocked it in the first place. Of course once I reached Step 7, I don't get the # sign. I get the $ sign and I don't know what to do :/
Droid Turbo System Image Tutorial
So I've noticed there isn't yet a guide on how to modify a system image for the Turbo and thought I would write one up. Note that anything you do here can very easily brick your phone, and I'm not responsible for anything that breaks, bricks, catches on fire, causes Skynet to become sentient, or eats your cat.
Here's what you need:
A rooted system image (can be found here)
A linux distro, either running natively or in VirtualBox (Ubuntu is a good choice)
IF YOU'RE USING LINUX NATIVELY:
Put the system image somewhere on an ext4 file system you have access to, such as in your home directory (/home/user)
Make sure loop device support is installed (this will vary by distro but should be installed by default on Ubuntu)
Make sure the loop kernel module is loaded:
Code:
lsmod | grep loop
As long as the command returns text, you're good.
If it is not, load it:
Code:
sudo modprobe loop
Make a mountpoint:
Code:
sudo mkdir /mnt/turbo
And finally, mount the image:
Code:
sudo mount -t ext4 -o loop /path/to/turbo/image /mnt/turbo
And the image will be accessible at /mnt/turbo/. Note that you'll need root permissions to access the files. To open the file manager as root under Ubuntu:
Code:
sudo nautilus
Navigate to /mnt/turbo to access the image and modify whatever you feel like.
IF YOU'RE USING VIRTUALBOX:
Please note that I'm writing these instructions under Linux. YMMV.
You'll have to convert the turbo's system image to something VirtualBox can recognize. To do this:
Code:
VBoxManage.exe convertdd turbo_system.img turbo_system.vdi
Load VirtualBox, but don't start your virtual machine yet.
Right click on your VM and open Settings.
Navigate to Storage and select Add Hard Disk.
{
"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"
}
Select your Turbo's system image in vdi format.
Click OK and close the settings window.
Start the VM.
Once you're all logged in, you can open your file manager and see if the image is already visible in the sidebar for mounting. If so, just click to mount and you're all good, although as above you'll have to be root in order to modify it. To open the file manager as root under Ubuntu:
Code:
sudo nautilus
If the image is not in the sidebar of your file manager, you'll have to mount the image manually. Use blkid to find a list of devices attached to the virtual system; the one we want is of type ext4, and *should* be the last device in the list. You can double check by finding the size of the device:
Code:
sudo blockdev --getsize64 /dev/sdX
where X is the letter of the device. This should return 3 GB or so.
Make a mountpoint:
Code:
sudo mkdir /mnt/turbo
Mount the image:
Code:
sudo mount -t ext4 /dev/sdX1 /mnt/turbo
where X is the letter of the device.
Open your file manager as root and navigate to /mnt/turbo. Under Ubuntu this would be:
Code:
sudo nautilus
Shut down your VM when you're done playing around.
Once you're done modifying the image, you need to convert it back to a raw .img format.
Code:
VBoxManage.exe clonehd turbo_system.vdi turbo_system.img --format raw
And that's it! Try not to break anything too badly. Make sure you unmount the image and/or stop your VM before flashing! This is the first guide I've written, so let me know if there's any questions you have or any improvements I can make.
First off, thanks for putting this tutorial together. I am running Windows 7 and I have downloaded all of the files that are needed to set up my virtual machine as well as the /system image that you linked to. I have, as far as I can tell, successfully added the Ubuntu image but I am stuck at adding the /system image as a HDD. I click the "Add Hard Disk" button followed by "Choose existing disk" then browse to the path that my image is in. With the default settings I can't see the .7z archive that I downloaded or the .img file that I extracted from it using WinRar. Next I tried changing the file type drop down to "All files" which allowed me to see both file types. I tried selecting both of them (at different times) and both files produce the following error when I click "Open":
Failed to open the hard disk file C:\Users\Chris & Kymber\Droid Turbo\Shared VM\xt1254.system.Blur.21.44.12.quark_verizon.rooted.ext4.img\xt1254.system.21.44.12.quark_verizon.rooted.ext4.img.
Could not get the storage format of the medium 'C:\Users\Chris & Kymber\Droid Turbo\Shared VM\xt1254.system.Blur.21.44.12.quark_verizon.rooted.ext4.img\xt1254.system.21.44.12.quark_verizon.rooted.ext4.img' (VERR_NOT_SUPPORTED).
Click to expand...
Click to collapse
I get the same error message whether I attempt to add it as an IDE or SATA drive. Am I doing something wrong or missing a step here?
Ok, I think I may have figured it out. I used the VBoxManage.exe convertdd command to convert the .img file to a .vdi file that VirtualBox can handle. I now have the drive mounted in my VM and using the command "sudo nautilus" (gksudo said it was not installed, I'm guessing this varies between different copies of Linux?) I was able to achieve root access to the drive so that I can modify it. When I'm done, can I simply use the VBoxManage.exe convertdd command from windows to convert the file back from .vdi to .img?
If you are changing things and flash an unbootable system image can you just flash a good image to recover? I would assume so since your reflashing the entire system partition.
thecaptain0220 said:
If you are changing things and flash an unbootable system image can you just flash a good image to recover? I would assume so since your reflashing the entire system partition.
Click to expand...
Click to collapse
Yep, basically flash the image that is in the mofo guide and you're back in action.
Good Idea!
Thanks for this primer on the subject! Would it be possible to please throw us some links on how to install Xposed framework, updated SuperSU Pro, wifi tethering, or remove bloatware? With any luck we can start altering the stock Moto images we have in the Dev section.
BEDickey said:
Thanks for this primer on the subject! Would it be possible to please throw us some links on how to install Xposed framework, updated SuperSU Pro, wifi tethering, or remove bloatware? With any luck we can start altering the stock Moto images we have in the Dev section.
Click to expand...
Click to collapse
You wouldn't want to alter those imaged, as they are not pre-rooted (unless you feel like doing that part yourself). It would be best to modify the image that comes with mofo as a starting point.
brennam7 said:
You wouldn't want to alter those imaged, as they are not pre-rooted (unless you feel like doing that part yourself). It would be best to modify the image that comes with mofo as a starting point.
Click to expand...
Click to collapse
I'm not saying we can't. I'm completely new to this,just trying to wrap my brain around it and participate.
I mounted the image in Linux and removed a few files to test it out. Then I unmounted the image. It seems like the modified image is the same size. Does the image retain its size? Is there a way to compact the image? I am going to try flashing it now and see if my changes are there.
thecaptain0220 said:
I mounted the image in Linux and removed a few files to test it out. Then I unmounted the image. It seems like the modified image is the same size. Does the image retain its size? Is there a way to compact the image? I am going to try flashing it now and see if my changes are there.
Click to expand...
Click to collapse
Yes, the image will retain its size.
BEDickey said:
Thanks for this primer on the subject! Would it be possible to please throw us some links on how to install Xposed framework, updated SuperSU Pro, wifi tethering, or remove bloatware? With any luck we can start altering the stock Moto images we have in the Dev section.
Click to expand...
Click to collapse
I'll look into this later today
cstone1991 said:
Ok, I think I may have figured it out. I used the VBoxManage.exe convertdd command to convert the .img file to a .vdi file that VirtualBox can handle. I now have the drive mounted in my VM and using the command "sudo nautilus" (gksudo said it was not installed, I'm guessing this varies between different copies of Linux?) I was able to achieve root access to the drive so that I can modify it. When I'm done, can I simply use the VBoxManage.exe convertdd command from windows to convert the file back from .vdi to .img?
Click to expand...
Click to collapse
Yes this should work, I'll update the OP to include this information, sorry
Edit: this doesn't work, I'll be working on a solution today, hang tight everyone
Ekkoria said:
[*]Navigate to Storage and select Add Hard Disk.
[*]Select your Turbo's system image.
Click to expand...
Click to collapse
So virtualbox doesnt let you mount an img as a harddrive. I used
VBoxManage.exe convertdd system.img system.vdi
I was able to then add the system.vdi as a harddrive, booted up ubuntu and finished following guide/making changes. (putting in my own hosts file.. 5mb addition)
After shutting down guest, I did the reverse of the above command to get back to an img...
Its 600megs short of the original img, so obviously something isnt right. Mofo says its not a valid ext4 so I did something wrong.
I really just want the modified hosts file working, adaway and adfree modify the hosts at first, and after a while it gets corrupt/reverts, I imagine because it was modified after the phone boots.
Ugh.
ntxct said:
So virtualbox doesnt let you mount an img as a harddrive. I used
VBoxManage.exe convertdd system.img system.vdi
I was able to then add the system.vdi as a harddrive, booted up ubuntu and finished following guide/making changes. (putting in my own hosts file.. 5mb addition)
After shutting down guest, I did the reverse of the above command to get back to an img...
Its 600megs short of the original img, so obviously something isnt right. Mofo says its not a valid ext4 so I did something wrong.
I really just want the modified hosts file working, adaway and adfree modify the hosts at first, and after a while it gets corrupt/reverts, I imagine because it was modified after the phone boots.
Ugh.
Click to expand...
Click to collapse
Odd. Virtualbox may have compressed the image. See if you can turn that off. I'll work on it myself later today, see if I can get it working
http://forum.xda-developers.com/nexus-4/general/diy-manually-installing-xposed-t2369618
Found this guide to install xposed manually will try it out soon
ntxct said:
So virtualbox doesnt let you mount an img as a harddrive. I used
VBoxManage.exe convertdd system.img system.vdi
I was able to then add the system.vdi as a harddrive, booted up ubuntu and finished following guide/making changes. (putting in my own hosts file.. 5mb addition)
After shutting down guest, I did the reverse of the above command to get back to an img...
Its 600megs short of the original img, so obviously something isnt right. Mofo says its not a valid ext4 so I did something wrong.
I really just want the modified hosts file working, adaway and adfree modify the hosts at first, and after a while it gets corrupt/reverts, I imagine because it was modified after the phone boots.
Ugh.
Click to expand...
Click to collapse
Try the following:
Code:
VBoxManage.exe clonehd path/to/turbo.vdi turbo.img --format raw
Ekkoria said:
Try the following:
Code:
VBoxManage.exe clonehd path/to/turbo.vdi turbo.img --format raw
Click to expand...
Click to collapse
Hey! Same size as original now. Thanks, Ill keep moving forward
UPDATE:
Flashed completed, booted normally. Verified the edited hosts file was there, it was. Everything seems to be working how I was hoping! Oddly the system did create (or I did along the way) a second hosts file in the etc folder, "hosts~" which is a default hosts file. However the system doesnt seem to use it, just the edited one so its no big deal but maybe its a permission issue?
ntxct said:
Hey! Same size as original now. Thanks, Ill keep moving forward
UPDATE:
Flashed completed, booted normally. Verified the edited hosts file was there, it was. Everything seems to be working how I was hoping! Oddly the system did create (or I did along the way) a second hosts file in the etc folder, "hosts~" which is a default hosts file. However the system doesnt seem to use it, just the edited one so its no big deal but maybe its a permission issue?
Click to expand...
Click to collapse
Not sure about the hosts deal, but hey, if it works right?
OP updated to include the new information.
Ekkoria said:
Not sure about the hosts deal, but hey, if it works right?
OP updated to include the new information.
Click to expand...
Click to collapse
So i got this going finally. Removed a bunch of bloat, shot the lollipop boot animation in there, as well as some xposed parts. Compiling it back to system.img now, but its sitting at 0% for quite some time. Not sure if thats normal?
EDIT: oh dear christ it just went to 10%. This is going to take some time
EDIT 2: And now it sits at the boot animation but never boots. Not sure why, as i didn't really make any major changes. time to pick this think apart.
hi, have you installed xposed successfully and does it function correctly?
123421342 said:
http://forum.xda-developers.com/nexus-4/general/diy-manually-installing-xposed-t2369618
Found this guide to install xposed manually will try it out soon
Click to expand...
Click to collapse
Haven't seen this mentioned, but might have missed it: can we symlink /system/etc/hosts to /data/data/hosts (before flashing) to maintain write access to the hosts file?
Guide: Getting Xposed RunningThis morning, I finally managed to get Xposed up and running on my Turbo. So I thought I'd write up a guide as to how!
What you'll need:
A paid copy of Mofo (obviously)
Either a modified system image containing Xposed already, or if you like, you can modify one yourself as described in this tutorial. I've already created a modified system image to include Xposed as well as Wifi Tethering and a modified hosts file for ad blocking.
The Xposed Installer apk
Xposed Installer needs to be installed on your phone
Terminal Emulator and ES File Explorer from the play store need to be installed on your phone
A rooted image flashed to your phone
Before flashing anything, this is what you need to do:
On your computer, find your de.robv.android.xposed.installer_v33_36570c.apk and rename it to be a .zip file.
Open this .zip file and extract /assets/XposedBridge.jar and, if you're modifying your own system image, extract /assets/arm/app_process_xposed_sdk16 as well.
Put XposedBridge.jar somewhere on your phone, I like to use the Downloads folder so I don't lose track of it later.
In ES File Explorer, navigate to /data (NOT SDCARD/DATA)
{
"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"
}
Make sure it doesn't say sdcard > data!
Create a folder called "xposed"
Long press the folder, select properties, and set permissions to 755
Set the owner of the folder to root and the group to shell
Move XposedBridge.jar into the xposed folder we just created.
Make the permissions of XposedBridge.jar 644
As before, make the owner root and the group shell.
Open the Xposed Installer app on your phone.
Open terminal emulator and type
Code:
ps | grep xposed
This will return a pattern like the following. Make a note of the first seven characters, as shown (the first is a lowercase u)
Return to /data/xposed
Create two new files: modules.list and modules.whitelist
Make the permissions on both files 644 as above
Set the owner to the seven characters we noted down earlier and the group to shell on both files
If you're flashing a pre-compiled image with Xposed, you're done here! Go ahead and flash, and enjoy!
If you're modifying your own system image, you've got some more work to do. Take app_process_xposed_sdk16 from the Xposed apk and rename it to app_process.
In your turbo system image, navigate to /bin/ and replace app_process with the one from Xposed Framework. Make sure its permissions are set to 755:
Code:
sudo chmod 755 /path/to/img/bin/app_process
Linux does not allow setting the group of a file to a nonexistent group, so on your pc you'll have to make a shell group:
Code:
sudo groupadd shell
Change the group of app_process to shell:
Code:
sudo chgrp shell /path/to/img/bin/app_process
You're ready to flash!
NOTE: If XposedBridge.jar reports problems, try setting installation mode in the Xposed installer app to recovery (flash manually) and hitting install, then reboot.
You're done! Xposed should show up as installed! Don't use any modules that require system write access, such as replacing system icons, but most modules (ie GravityBox) work fine without it.
Ekkoria said:
This morning, I finally managed to get Xposed up and running on my Turbo. So I thought I'd write up a guide as to how!
Click to expand...
Click to collapse
Gahhh I was working all day on getting Xposed baked in
Thanks for the write up! I'm finding modifying the image file and flashing it to be just as addictive if not more than flashing someones prebuilt roms on other devices. I never got into compiling android so this feels like a way to tinker on my own without jumping into the deep end of code.
ntxct said:
Gahhh I was working all day on getting Xposed baked in
Thanks for the write up! I'm finding modifying the image file and flashing it to be just as addictive if not more than flashing someones prebuilt roms on other devices. I never got into compiling android so this feels like a way to tinker on my own without jumping into the deep end of code.
Click to expand...
Click to collapse
Same here! When I finally opened Xposed Installer and saw it read the framework as installed, I've almost never been so excited about something Android.
i dont need it but its a great guide, easy, short and with pictures!
Does the phone need to be flashed with a rooted image, like that in the tutorial of how to modify system images? I can't write to /data, presumably because I don't have the rooted image flashed yet. Also my /data directory is empty.
I have a copy of mofo, and copies of the rooted system image and your already compiled system image. Is there something I am missing? Thank you in advance.
Thanks so much man, about to flash. Will let you know how it goes.
Ah damn, I actually just did a bit different process of installing Xposed on a image for myself, (which involved baking it into the rom that didn't have it) totally got it working and I've rebooted 3 times so far and everything sticks. Loving having battery percentage now! I can write a quick tutorial writing xposed files into a fresh rooted image via Virtualbox and such... Took me a few hours
It did not work for xposedbridge.jar
aven1357 said:
Does the phone need to be flashed with a rooted image, like that in the tutorial of how to modify system images? I can't write to /data, presumably because I don't have the rooted image flashed yet. Also my /data directory is empty.
I have a copy of mofo, and copies of the rooted system image and your already compiled system image. Is there something I am missing? Thank you in advance.
Click to expand...
Click to collapse
Yes, you will need to be rooted first to perform these actions. Apologies for not originally including this. OP updated
savagebunny said:
Ah damn, I actually just did a bit different process of installing Xposed on a image for myself, (which involved baking it into the rom that didn't have it) totally got it working and I've rebooted 3 times so far and everything sticks. Loving having battery percentage now! I can write a quick tutorial writing xposed files into a fresh rooted image via Virtualbox and such... Took me a few hours
Click to expand...
Click to collapse
Yes please do so. I'd be very interested.
Sent from my XT1254 using XDA Free mobile app
I am having trouble with es file explr it tells me the operation failed when trying to do anything I have root and I enabled root for ES it seemed to work on root browser fine (I reset my device and just installed es so far)
edit checked and the root enhancement options are greyed out?
After following directions for all files and then subsequent flashing of your pre-built image xposed installer still reports framework problem. I've gone back and double checked the user:group and perm masks and everything looks good. Any ideas what else I should check?
I am having same problem as u smokie
smokie75 said:
After following directions for all files and then subsequent flashing of your pre-built image xposed installer still reports framework problem. I've gone back and double checked the user:group and perm masks and everything looks good. Any ideas what else I should check?
Click to expand...
Click to collapse
What's reporting a problem? Is it XposedBridge.jar?
If so, try setting the installation mode to recovery (flash manually) and hitting install, then reboot.
Ekkoria said:
What's reporting a problem? Is it XposedBridge.jar?
If so, try setting the installation mode to recovery (flash manually) and hitting install, then reboot.
Click to expand...
Click to collapse
Thanks! That worked!
Thanks for this , works great , now we just need one with busybox preinstalled
Stuck at this point any help?[/ATTACH]
Ekkoria said:
What's reporting a problem? Is it XposedBridge.jar?
If so, try setting the installation mode to recovery (flash manually) and hitting install, then reboot.
Click to expand...
Click to collapse
so will doing this enable gravitybox to work on the turbo?
hmltnjrmy7 said:
Stuck at this point any help?[/ATTACH]
Click to expand...
Click to collapse
You should be able to foloow the instruction you quoted from that point. You should go back and check your permissions, ownership and group for the 4 files. first
Do the change in install mode to manual. Hit install and go to recovery
recovery should give you the dead droid an then reboot
Also don't worry if the group "shell" shows up as something else in app_proces
rayjr13 said:
You should be able to foloow the instruction you quoted from that point. You should go back and check your permissions, ownership and group for the 4 files. first
Do the change in install mode to manual. Hit install and go to recovery
recovery should give you the dead droid an then reboot
Also don't worry if the group "shell" shows up as something else in app_proces
Click to expand...
Click to collapse
Lol the dead droid freaked me out at first, but I'm so happy xposed finally works!!!
***BOOST VARIANT ONLY*** ***BOOST VARIANT ONLY*** ***BOOST VARIANT ONLY***
CLEAR/DELETE DALVIK-CACHE FOLDER FROM "/data/dalvik-cache" IN ROOT EXPLORER OR TWRP AFTER INSTALLING BOOT IMAGE TO ALLOW SYSTEM TO ADJUST
##FLASH THE LATEST SUPERSU ZIP BELOW##
P.S. I NOTICE IT IS NO LONGER SYSTEM-LESS MODE. SO WE CAN TRIM THE SUPERSU SYSTEM-LESS CONTENT FROM THE RAMDISK.
Tweaked the contents of the boot image to allow for faster boot and better runtime performance. I use it as my daily driver. App performance is snappier. Only for the Boost Desire 626s. Unzip and flash with Flashify, TWRP, or your choice of image flasher. I also added some optimization scripts to supplement the boot image. Run them with Smanager, Root Explorer or in the terminal. Also here is a zip 601626SPIEFIX.zip that when flashed in TWRP recovery will allow the system to run non-pie executables and it works great. You'll be able to run custom binaries without any issue or error. All zips in this thread are the latest.
If you have ISSUES WITH DATA SPEEDS in certain areas, especially if you tether, GO INTO THE DIALER and DIAL *#*#4636#*#* then ACCESS PHONE INFORMATION and SELECT CDMA auto (PRL) UNDER SET PREFERRED NETWORK TYPE. LTE seems to be problematic in certain areas with speeds dropping to 150kbps and with this solution you'll be getting about 600 to 700kbps so at least it'll be a gain until you get into an area with better LTE coverage. In a good coverage area, I get download speeds of up to 5 to 7 mbps with LTE on, but in bad areas, CDMA works better. If you want to tether with a wireless third party solution make sure to run in a terminal window or adb shell as root : pm disable com.htc.tetheringguard
DOWNLOAD BOOT IMAGE: http://forum.xda-developers.com/attachment.php?attachmentid=3917986&d=1477604429
DOWNLOAD SUPERSU BETA: https://download.chainfire.eu/1009/SuperSU/SR2-SuperSU-v2.78-SR2-20161029143931.zip?retrieve_file=1
DOWNLOAD SCRIPTS: http://forum.xda-developers.com/attachment.php?attachmentid=3863279&d=1472880351
DOWNLOAD PIE FIX: http://forum.xda-developers.com/attachment.php?attachmentid=3844539&d=1471383163
DOWNLOAD BOOT IMAGE TOOL : http://forum.xda-developers.com/attachment.php?attachmentid=3917995&d=1477605263
DOWNLOAD HTC DRIVERS AND MINIMAL ADB + FASTBOOT: http://forum.xda-developers.com/attachment.php?attachmentid=3868562&d=1473328405
ANDBLOCKDEV.sh from scripts zip will speed up file input and output speeds, its contents have been incorporated into the boot image so the scripts files are for your own archival.
The zip DESIRE626SIMGTOOL.zip contains the android image kitchen and the 6.0.1 Boost Desire 626S boot image contents already extracted into two folders split_img and ramdisk with recent modifications. Enjoy!
http://www.vysor.io/ is a great tool to control your android device from a computer within chrome. You should try it out.
I provided a zip named HTCDrivers.zip containing the installation for both fastboot and adb drivers for the Boost Desire 626S, and minimal adb and fastboot. This will help you connect your device up with Vysor.
COPY the FILES; fastboot.exe, adb.exe, AdbWinUsbApi.dll and AdbWinApi.dll FROM - C:\Program Files (x86)\Minimal ADB and Fastboot - TO - C:\Windows\System32 - AND - C:\Windows\SysWOW64
Once you have installed the drivers for HTC devices,
and copied the minimal adb and fastboot files specified above to both system folders, you should be able to run adb commands without a problem by just opening a command prompt as administrator,
and RUNNING the command:
adb devices
- to start the adb server. This will allow connection with Vysor.
##########
For those who prefer nightbreed813's 6.0.1 slim rom version, I uploaded 601VPNDIALOGSFIX.zip to fix the issue with authorizing VPN clients, but first YOU HAVE TO CREATE /system/priv-app/VpnDialogs in Root Explorer or any other root filesystem browser, then reboot to TWRP recovery and flash the zip.
DOWNLOAD VPNFIX : http://forum.xda-developers.com/attachment.php?attachmentid=3860930&d=1472669879
##########
Also, you can get your MSL/SPC security code easily.........
Use the info in this thread to get your MSL/SPC security code so you can write new values to NV entries in the modem. Some values are locked but you can change the BC config for both LTE and CDMA so that would at least be helpful.
INFO HERE: http://forum.xda-developers.com/spri...k-sim-t3314755
##########
Android settings can be changed in the terminal for three namespaces; system, global and secure.
In the terminal run:
settings list system
settings list global
settings list secure
For each namespace all associated settings and their values will be listed. To change a setting type:
settings put system setting_name_here value_here
settings put global setting_name_here value_here
settings put secure setting_name_here value_here
##########
{
"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"
}
Look now has working VPN......
***BOOST VARIANT ONLY*** ***BOOST VARIANT ONLY*** ***BOOST VARIANT ONLY***
anthonykb said:
Tweaked the contents of the boot image to allow for faster boot and better runtime performance. I use it as my daily driver. App performance is snappier. Only for the Boost Desire 626s. Unzip and flash with Flashify, TWRP, or your choice of image flasher. I also added some optimization scripts to supplement the boot image. Run them with Smanager, Root Explorer or in the terminal. Also here is a zip 601626SPIEFIX.zip that when flashed in TWRP recovery will allow the system to run non-pie executables and it works great. You'll be able to run custom binaries without any issue or error. All zips in this thread are the latest.
Click to expand...
Click to collapse
Will this run on the Metro Variant?
As far as I know no but you can try in case it might.
Enter these commands in a new terminal window:
cd /dev/block/platform/soc.0/7824900.sdhci/by-name
dd if=boot of=/sdcard/backup.img
The backup boot image can be flashed from the sdcard in TWRP recovery if the device fails to boot into the system after flashing the boot image contained in the zip in the attachments.
Is there anyway you would be able to make one for the metro Variant if i upload my boot image?
MetroPCS Boot Image
GotHeart said:
Is there anyway you would be able to make one for the metro Variant if i upload my boot image?
Click to expand...
Click to collapse
Did you try unzipping the boot image and flashing it already? I don't think it could work that way. I would do it if I had the metro version myself.
anthonykb said:
Did you try unzipping the boot image and flashing it already? I don't think it could work that way. I would do it if I had the metro version myself.
Click to expand...
Click to collapse
Thats what im saying.if i upload my metro boot image would you be able to optimize it like you did before with the boost Variant?
GotHeart said:
Thats what im saying.if i upload my metro boot image would you be able to optimize it like you did before with the boost Variant?
Click to expand...
Click to collapse
I meant so you tried the boost version and it wouldn't boot?
anthonykb said:
I meant so you tried the boost version and it wouldn't boot?
Click to expand...
Click to collapse
No i havent tried it yet
GotHeart said:
No i havent tried it yet
Click to expand...
Click to collapse
Backup your kernel boot image to your sdcard and flash the boost version just to make sure.
cd /dev/block/platform/soc.0/7824900.sdhci/by-name
dd if=boot of=/sdcard/backup.img
Then unzip the 601bootimg.zip file with Zarchiver in the Play Store and flash the extracted boot image.
anthonykb said:
Backup your kernel boot image to your sdcard and flash the boost version just to make sure.
Click to expand...
Click to collapse
Okay ill do it now and let you know
The phone booted but it corrupted my sdcard,so i lost everything i had on there.
GotHeart said:
The phone booted but it corrupted my sdcard,so i lost everything i had on there.
Click to expand...
Click to collapse
Flash back the backed up boot image in TWRP and see if the sdcard mounts right. The mount point contained in the boost boot image is probably wrong for the the sdcard/emmc in the metropcs phone.
I did but my sdcard got corrupted so i was forced to format it.
GotHeart said:
I did but my sdcard got corrupted so i was forced to format it.
Click to expand...
Click to collapse
I'm so sorry the process turned out to be a dud for you I have the boost model myself. Hope you can recover your files with one of those forensic data recovery tools.
anthonykb said:
I'm so sorry the process turned out to be a dud for you I have the boost model myself. Hope you can recover your files with one of those forensic data recovery tools.
Click to expand...
Click to collapse
Its nothing important lol.any chance you can share what you did or how?
Use the Android Image Kitchen by osm0sis
GotHeart said:
Its nothing important lol.any chance you can share what you did or how?
Click to expand...
Click to collapse
Use the tool at the link below to unpack the image, make your modifications, and repack the image contents (The ramdisk and split_img folders.) It's available for Windows, Linux and Android. It's a simple process expect for knowing what you'd need to do to the image.
http://forum.xda-developers.com/showthread.php?t=2073775
anthonykb said:
Use the tool at the link below to unpack the image, make your modifications, and repack the image contents (The ramdisk and split_img folders.) It's available for Windows, Linux and Android. It's a simple process expect for knowing what you'd need to do to the image.
http://forum.xda-developers.com/showthread.php?t=2073775
Click to expand...
Click to collapse
My mistake i was in a hurry when i typed that last reply.
Im aware of how to unpack/repack boot images and i appreciate the link,but i was wondering what modifications that were made.if youd prefer not to share,i can upload my boot image if youd like to make the modifications yourself.im just trying to make this compatible with the metro version.
The same modifications done for the Boost Desire 626S might not work well for the MetroPCS version so upload the image you backed up yesterday as an attachment in a reply post and I'll work on it.
Thanks a ton!
MetroPCS Boot Image
GotHeart said:
Thanks a ton!
Click to expand...
Click to collapse
Run busybox top in the terminal on your phone and post some screenshots so I can see what might need to be done. We want to see what processes would be the culprit behind bogging down precious processor time and reducing the snappiness of the device in reacting to realtime input and handling current requests.
Sprint
Note! the reason i did not just do a flashfire update to ph9 from pgc was i have no idea what was changed filewise. i was given the full on firmware so i literally remodded the new system.img, and updated the links for it and for the BL and CP files. This Will put you on the newest sprint firmware with root and everything working
I am not responsible for anything that happens to your device by doing this! If you break it, brick it or just plain blow it up. it is your phone and your responsibility for what happens to it.
Here it is. Full Sprint With Root - since this is Sprint based all bands should work as well
This is Based on the Sprint PH9 Firmware and is Completely Stock and Unmodified
To Avoid Repeat Questons. READ! READ IT AGAIN! and then READ it once more! if you do not Understand any part of this. Do Not Continue!!!
This Guide assumes you have some basic knowledge and can at least copy and paste for the most part! It is Intended for advanced users!!!!!!!!
This Guide also Assumes you have an sdcard inserted in your phone(however some of you may not and this will not work.)
This Does NOT Trip Knox.
Read this entire post before doing anything to avoid issues and FOLLOW Directions - if you don't things will not work right.
Note! if at anytime during the following steps you see the samsung boot animation before step 11. start over cause you screwed up!
Step 1. Initial PreSetup Requirements and Downloads
Make Sure your ExtSDCard(the one you put in your sim tray) is formated exfat(backup your card before you do this in windows or linux(whichever you use))
https://www.androidfilehost.com/?fid=24651430732237653 bbx.rar
https://www.androidfilehost.com/?fid=24723785898787307 Sprint_System.rar - link updated
https://www.androidfilehost.com/?fid=24723785898787308 Sprint Bootloader - link updated
https://www.androidfilehost.com/?fid=24723785898787306 Sprint Modem - link updated
Step 2. extract system.rar and bbx.rar and then copy system.img and bbx to your extsdcard(the sdcard you inserted into your phone)
Step 3. odin sprint userdebug firmware available here. http://forum.xda-developers.com/sprint-note-7/how-to/root-super-leaky-bros-sprint-galaxy-t3447202
Step 4. Directly after odin is done with the sprint file you will immidiatly be presented with an update screen
Step 4a when this process of erasing your phone is finished it will reboot(this is the point you want to do the next step)
Step 4b. press and hold power, home and vol up to enter recovery
Step 4c If you see the samsung boot animation. you did NOT do this right and i would suggest you start over
Step 5. open a command prompt in your adb folder and do the following steps 1 at a time(these are case sensative)
Step 5a. adb shell
Step 5b. su
Step 5c. setenforce 0
Step 5d. export PATH=$PATH:/sbin
Step 5e. mount -o remount,rw /
Step 5f. on your phone, go to apply update from sdcard(this will mount your extsdcard as /sdcard and you should see the system.img file and the bbx file) do not select anything, go back to adb and continue(it is not a big deal if those files don't show. we just needed the extsdcard mounted as sdcard - the files exist, just continue to the next step)
Step 5g. cp /sdcard/bbx /sbin/bbx
Step 5h. chmod 777 /sbin/bbx
Step 5i. cd /sbin
Step 5j. ./bbx --install /sbin
Step 5k. umount -l /system
Step 5l. /sbin/dd if=/sdcard/Sprint_System.img of=/dev/block/platform/soc/624000.ufshc/by-name/system
Note. you will see a blinking cursor. just be patient
Step 7. when it is done you will see something similar to this
11161600+0 records in
11161600+0 records out
5714739200 bytes (5.3GB) copied, 268.668086 seconds, 20.3MB/s
Step 8. if all went well you should be at your prompt and not in adb anymore
Step 9. from your command prompt simply type
Step 9a. adb reboot bootloader
Step 10. open odin and click the bl button and select this file - BL_N930PVPU1APH9_CL8706608_QB10711091_REV00_user_low_ship_MULTI_CERT.tar.md5
Step 10b. now click the cp button and select this file - CP_N930PVPU1APH9_CL8706608_QB10711091_REV00_user_low_ship_MULTI_CERT.tar.md5
Step 10c. now click start. it will reboot when done let it fully boot this time.
Step 11. once booted and you have setup your phone, first we need to enable usb debugging
Step 11a. to do this go to settings>about device or device information and tap the build number repeatedly until it says dev options enabled, now backout of about and go into dev options and enable usb debugging
Step 11b. Now we need to add the root files or supersu as most of you know it
Note! pertaining to Step 12. these instructions were taken Explicitly from @freeza thread which is listed in step 3
Step 12. Now we need to add supersu and the needed files for it to work
Step 12a. download this file - https://www.androidfilehost.com/?fid=24651430732236679
Step 12b. Extract the sun7 file to your adb folder making sure the files are in a folder called sun7(mine looks like this - c:/adb/sun7 and contains 4 files)
Step 12c. Open a command prompt where your ADB executable and sun7 folder are.
Step 12d. adb shell
Step 12e. su - Note! if your adb prompot changes from a $ to #(you are good and have root access)
Step 12f. type exit twice to get back to the command prompt. - Your Phone should be fully booted when you do this
Step 12g. adb push sun7 /data/local/tmp/su
Step 12h. adb shell chmod 0777 /data/local/tmp/su/*
Step 12i. adb shell
Step 12j. cd data/local/tmp/su
Step 12k. su
Step 12l. ./root.sh - Note. this command begins with a . do not leave it out
Step 12m. Your Phone will now reboot
Step 13. when booted back up go to playstore and install busybox on rails or a similar app and install busybox to /system/xbin(if your given an option of where to install it)
Step 14. Thats Pretty Much it. most of all enjoy it
Note! now since your are rooted on stock, you are going to see security warnings. to get rid of these simply freeze securitylogagent or delete it from /system/app
Note! 2 atm you cannot update via ota to PH9, someone needs to get a hold of the update and fix it so it can be flashed via flashfire and make sure it does not replace the kernel
Additional Notes!
If for any reason you do a factory reset. you will break root and need to redo this method to get it back
If you use shealth do not update it or allow playstore or galaxy appstore to auto update it or it will break it
Enjoy and FOLLOW Directions - if you don't things will not work right.
thank you to the following:
@freeza - for posting the original userdebug file
@ted77usa - for testing
@bajasur - for the initial idea which ultimately led to this
@Surge1223 - for the busybox installer and the adb help and android commands that make this work
@galaxyuser88 - for testing this and pointing out some flaws
@Hashcode - for inspiration
@lightning413 - for the PH9 Firmware
and anyone i missed
this was a complete collaboration and is only available because of those mentioned so be sure to give them thanks
testing was done by @jamice4u - ty for confirming it works
ScreenShots:
{
"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"
}
This Method Completely replaces the Sprint PH3 files with the stock PGC. with exception to the kernel, recovery and the su binary which are still PH3 userdebug.
as we don't have an unlocked bootloader, there is no twrp recovery. but flashfire takes it place. so any changes you want to make are basically done the same way as they would be for twrp except they are now flashed through flashfire.
to get rid of the security notice you will get(because the system is now rooted) simply install root explorer(or any root browser) and go to /system/app and delete securitylogagent or go into the folder and rename it adding .bkp to the end of the file name and reboot.
If you don't see the Sprint_System.img and bbx files after doing the apply update from sdcard on your phone. try this as it has worked for some on t-mobile
create 3 folders on your sdcard
create "files" inside of that, create one called "image" and then inside of that crate one called "file" so on your sdcard you would have /files/image/file and place the 2 files into it, you have to do this with the phone in recovery so just pop out your sim tray. plug the sdcard into your pc and create the folders and move the files into it, then force your phone into recovery(basically reboot your phone and instantly go into recovery) and start step 5 again. hopefully the files now appear and you can continue
now when you get to step 5g step 5l, you will need to modify them to reflect the new path to the files so it would now look like this
step 5g. cp /sdcard/files/image/file/bbx /sbin/bbx
step 5l. /sbin/dd if=/sdcard/files/image/file/Verizon_System.img of=/dev/block/platform/soc/624000.ufshc/by-name/system
and continue on with the guide
post 3 just in case
First!
This is exciting. Thanks
Sent from my SM-N930P using XDA-Developers mobile app
Amazing work as always bud....[emoji106]
Sent from my SM-N920T using Tapatalk
Very nice work @OvrDriVE. Your work here is much appreciated sir!
Does Samsung Pay work after rooting? Can other Galaxy Apps be updated?
ALooneyGuy said:
Does Samsung Pay work after rooting? Can other Galaxy Apps be updated?
Click to expand...
Click to collapse
@ALooneyGuy
All galaxy apps updated
TWIST3D_N930T
Samsung Pay
Does any one know is Samsung Pay work with this method.
Thanks
Victor
vbadillopr said:
Does any one know is Samsung Pay work with this method.
Thanks
Victor
Click to expand...
Click to collapse
Samsung pay would not work with any kinda root method.... until we find the way to bypass Samsung knox security or something.
Sent from my SM-N920T using Tapatalk
ted77usa said:
Samsung pay would not work with any kinda root method.... until we find the way to bypass Samsung knox security or something.
Sent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
Still exciting, but I've kind of gotten used to not having to take my wallet to the grocery store
Everything in life is a trade off...
vbadillopr said:
Does any one know is Samsung Pay work with this method.
Thanks
Victor
Click to expand...
Click to collapse
T-mobile root is the same way and samsung pay does not work.
Josephigloe said:
T-mobile root is the same way and samsung pay does not work.
Click to expand...
Click to collapse
@Josephigloe
U got sprint note 7 too right or still on note 5?
TWIST3D_N930T
ted77usa said:
@Josephigloe
U got sprint note 7 too right or still on note 5?
TWIST3D_N930T
Click to expand...
Click to collapse
Yes i have note 7 and note 5 on Sprint
ALooneyGuy said:
Still exciting, but I've kind of gotten used to not having to take my wallet to the grocery store
Everything in life is a trade off...
Click to expand...
Click to collapse
Grabbed the Samsung pay logcat after rooting and permission denied...... maybe @OvrDriVE @Surge1223 can figure it out or some others devs[emoji4]
https://www.dropbox.com/s/ptdoe4dt7jct7b6/alogcat.2016-09-14-09-37-12-0700.txt?dl=0
Swyped From TWIST3D_N930T
How is this method better/different from other one?
SptMogul said:
How is this method better/different from other one?
Click to expand...
Click to collapse
Same method for root this is not deodexed or debloated its stock. And Bluetooth doesn't forget after a reboot.
Sent from my SM-N930P using XDA-Developers mobile app
sml2004 said:
Same method for root this is not deodexed or debloated its stock. And Bluetooth doesn't forget after a reboot.
Click to expand...
Click to collapse
Does WiFi calling work?
kirschdog1 said:
Does WiFi calling work?
Click to expand...
Click to collapse
No, PH9 update is needed
Sent from my SM-N930P using XDA-Developers mobile app