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
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 :/
[APP][ROOT] Android 4.1.2 Rooting Universal Method
This method is single for rooting your mobile!
[install]
1. Download Root Explorer [Google Play]
2. Download Root Master
3. Unpack and install Root Master on your PC
4. Install drivers of your mobile
5. Run RootMaster and press first button on first screen
6. After this click the center button on all windows
7. You mobile is rooted - Reboot your mobile
8. Close the RootMaster
9. Install Root Explorer and delete superuser.apk
10. This release of superuser.apk is not english
11. Delete or replace your superuser.apk in /system/app
12. Unpack Superuser.apk from zip and copy to /system/app folder
13. Reply yes to replace your apk Superuser.apk
14. If you delete superuser.apk reinstall Only superuser from Zip
Root Explorer Download
<MOD EDITED - WAREZ LINK REMOVED>
Root Master Download
Superuser 3.1.3 Free
Screens and reports
First screen
{
"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"
}
Clique on center all screens
Final Screen to root
Root Start
Root screen
Root ok
Tried this on an lg p714,at some point the app asked me to restore my data in order to continue the rooting proccess,but failed.
So no luck for the LG p714,not even with framaroot.
kalel29 said:
Tried this on an lg p714,at some point the app asked me to restore my data in order to continue the rooting proccess,but failed.
So no luck for the LG p714,not even with framaroot.
Click to expand...
Click to collapse
Reboot device after install superuser.apk and rootexplorer.apk
hacker812c said:
Reboot device after install superuser.apk and rootexplorer.apk
Click to expand...
Click to collapse
why do i have to install the apps if i dont have root permissions? it doesnt make any sense for me.
it's just work for my stock rom 4.1 one X with 1 click
will try my wife's HTC One...
Thanks for sharing bro
Worked like charm on my Karbonn Titanium S5. Thaks a lot for the post
did it work with razr?
This looks like its just bin4ry's adb restore exploit packaged up in some chinese program.
tried many other root tools but could not seem to get root with them on a Blade V
this worked after numerous attempts at clicking root
many thanks
ando_uk said:
tried many other root tools but could not seem to get root with them on a Blade V
this worked after numerous attempts at clicking root
many thanks
Click to expand...
Click to collapse
Hello there..wanting to buy the phone is it any good?on virgin mobile uk..how did you manage to get one cant seem to see anything on their website ..tried calling them ..the lady told me they have it on their warehouse..so it comes up £99.99 handset plus £10 top up which is required..and delivery for about £8...any info. Would be much appreciated...is it worth the money for this phone..??thanks again...
Sent from my GT-I9505 using Tapatalk 2
Hy this is work, but I cant replace superuser.apk. Every time I do that I lose root. Please Help
hacker812c said:
[APP][ROOT] Android 4.1.2 Rooting Universal Method
This method is single for rooting your mobile!
[install]
1. Download Root Explorer [Google Play]
2. Download Root Master
3. Unpack and install Root Master on your PC
4. Install drivers of your mobile
5. Run RootMaster and press first button on first screen
6. After this click the center button on all windows
7. You mobile is rooted - Reboot your mobile
8. Close the RootMaster
9. Install Root Explorer and delete superuser.apk
10. This release of superuser.apk is not english
11. Delete or replace your superuser.apk in /system/app
12. Unpack Superuser.apk from zip and copy to /system/app folder
13. Reply yes to replace your apk Superuser.apk
14. If you delete superuser.apk reinstall Only superuser from Zip
steps 1-8 worked fine. My Blade ZTE V is now rooted. Thanks
Steps 9-14 are messy.
9. I install root browser and delete superuser.apk from system/app?
11. delete or replace superuser.asp? i thought I already did this in step 9?
12. copy superuser.apk? i thought this had already been done?
What I did:
1. I installed root browser.
2. I then unzipped and copied the superuser.apk to my memory card.
3. I replaced the chinese superuser.apk with the superuser.apk from my memory card
4. I done a reboot.
After doing this I lost my SU privileges and had to use the chinese root program again.
Can you tell me where I am going wrong?
Thanks
Click to expand...
Click to collapse
f4rell09 said:
Hello there..wanting to buy the phone is it any good?on virgin mobile uk..how did you manage to get one cant seem to see anything on their website ..tried calling them ..the lady told me they have it on their warehouse..so it comes up £99.99 handset plus £10 top up which is required..and delivery for about £8...any info. Would be much appreciated...is it worth the money for this phone..??thanks again...
Sent from my GT-I9505 using Tapatalk 2
Click to expand...
Click to collapse
Hello mate. I got my Blade V from the virgin shop. I am already a virgin media customer so I got the phone for £81.99 and they gave me a free PAYG sim card and £10 top up. I will sell the top up for 7 pound so I get the phone for £75 which is a damn good price.
Very impressed with the phone. It is not as sleek as the galaxy s4 mini or htc 1 but for the price it is 110% worth it.
Hy is any chance to unroot LGL3E430 with this tool
Here's the tutorial that works for XT910.
http://forum.xda-developers.com/showthread.php?t=2402943
picklepete said:
hacker812c said:
[APP][ROOT] Android 4.1.2 Rooting Universal Method
This method is single for rooting your mobile!
[install]
1. Download Root Explorer [Google Play]
2. Download Root Master
3. Unpack and install Root Master on your PC
4. Install drivers of your mobile
5. Run RootMaster and press first button on first screen
6. After this click the center button on all windows
7. You mobile is rooted - Reboot your mobile
8. Close the RootMaster
9. Install Root Explorer and delete superuser.apk
10. This release of superuser.apk is not english
11. Delete or replace your superuser.apk in /system/app
12. Unpack Superuser.apk from zip and copy to /system/app folder
13. Reply yes to replace your apk Superuser.apk
14. If you delete superuser.apk reinstall Only superuser from Zip
steps 1-8 worked fine. My Blade ZTE V is now rooted. Thanks
Steps 9-14 are messy.
9. I install root browser and delete superuser.apk from system/app?
11. delete or replace superuser.asp? i thought I already did this in step 9?
12. copy superuser.apk? i thought this had already been done?
What I did:
1. I installed root browser.
2. I then unzipped and copied the superuser.apk to my memory card.
3. I replaced the chinese superuser.apk with the superuser.apk from my memory card
4. I done a reboot.
After doing this I lost my SU privileges and had to use the chinese root program again.
Can you tell me where I am going wrong?
Thanks
Click to expand...
Click to collapse
I am also having the same problem with my cce sk504 and by chance someone knows this brand ai abroad with some similar model, since lenovo bought cce then I believe that this model is in some copies out there, but this is it also not able to translate the program, I'm Chinese version yet ... thank you help!
Click to expand...
Click to collapse
HTC One M7?
Has anyone tried this on the HTC One M7 with a locked boot. It would be jolly useful if it worked.
Success
Just rooted my LG L9 II . Worked like a charm
Swipe MTV Volt Rooted !!
Worked like a charm on Swipe MTv Volt !!
Thanks !
How do I solve the chinese SU issue ? ;( Can I download Superuser app from market and let it erase/override the chinese SU ?
Thanks a lot man
WARNING: IF YOU ARE NOT GOING TO START FROM STEP 1 AND FOLLOW EACH STEP EXACTLY HOW I HAVE WROTE IT THEN YOU WILL FAIL. THIS METHOD WORKS IF YOU CAN FOLLOW THE DIRECTIONS.
IF YOU DID NOT RESTORE YOUR PHONE AND FOLLOW EACH STEP EXACTLY HOW I LISTED BELOW THEN DO NOT SAY THIS DOESN'T WORK FOR YOU.
Step 1. Follow @evilpotatoman 's guide below to restore your phone to MJ5 FIRST
Guide:
1) Download and install Heimdall from here for windows. You'll need this and this to avoid missing .dll file errors
2) Download the following files:
MI9_fix.img.ext4
sec_csc.zip
2400258.zip
Put sec_csc.zip and 2400258.zip on your external SD card
3) Download and install the MJ5 partitions. Use Odin to flash these files (match the file names with the different upload slots)AP_N900AUCUBMJ5.zipBL_N900AUCUBMJ5.zipCP_N900AUCUBMJ5.zipHLTE_USA_ATT_32G.pit
{
"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"
}
4) Now is the time to use Heimdall.
Reboot into Download Mode once Odin finishes.
Install the vcredist packages downloaded from step 1.
unzip the heimdall .zip file to c:/
go to c:/Heimdall Suite/Drivers and click on zadig.exe
click the middle menu button to select "Show All Devices"
from the dropdown, select MSM8960
click the "install driver" button.
you should see a success message
5) Navigate on your computer to c:/Heimdall Suite/ and open heimdall-frontend.exe.
IMPORTANT -- Go to the Utilities tab and click the "Detect" button
Go to the Flash tab on Heimdall, click Browse and select the HLTE_USA_ATT_32G.pit file downloaded from step 3
Click the 'add' button, then next to 'partition name' select system from the dropdown.
click the Browse button underneath the dropdown, and select the MI9_fix.img.ext4 image you downloaded from step 2.
6) Click Start. ***I usually check the 'No Reboot' box to prepare for booting into recovery
7) Heimdall and your Note will report a bad flash at around 95% -- but don't worry -- your system.img got uploaded Reboot directly into recovery mode.
8) Once in recovery, select "Choose update from external" in the recovery, and select the sec_csc.zip you downloaded earlier (did you remember to put that file on your external SD card?). This will install the CSC files and run the preload checkin so you don't FC all over the place
9) IMPORTANT--After flashing the sec_csc, the Note will reboot.
Try to catch it in time to reboot BACK into recovery
Once in recovery, select "Choose update from external" in the recovery, and select the 2400258.zip you downloaded earlier.
END OF MJ5 RESTORE GUIDE - CONTINUE BELOW
Step 2. YOU ARE NOW ON MJ5 BE SURE TO DOWNLOAD AND INSTALL THE NB4 OTA UPDATE BEFORE CONTINUING!!!
Step 3. When you're finished the restore guide to MJ5 and updated to NB4 then delete any other files used from the restore guide so you don't mix them up and download the following 2 files:
1- Miata KitKat Fix v1
2- KitKat Ota ZipStep 4. Extract the Miata_KK_Fix_1.0.zip to the root of your BOTH your phone storage and your sd card. (make sure they are not in any folders!!!)
Step 5. Once both files in the Miata_KK_Fix_1.0.zip are extracted and copied to both your phone and the sd card... then reboot the phone.
VERY IMPORTANT TO REBOOT NOW
Step 6. Pick one of the follow options...
(Option A) - Wipes phone - I recommend this method
1. Rename 2400258.zip to update.zip and copy to EXTERNAL STORAGE (aka sd card)
UNPLUG USB CABLE BEFORE CONTINUING
2. Reboot into RECOVERY MODE (volume up + home) and select "Apply Update from external storage" and select your update.zip
3. It should start the update process and finish successfully! Enjoy!
If you made it this far and it fails or gives you an error then you did something wrong. Start from step 1 restoring your phone to MJ5
(Option B) - Doesn't wipe phone
1. You are going to need an ADB Side loader and it can be found here.
2. Extract to directory C:\Mini-SDK
3. Rename 2400258.zip to update. (DO NOT NAME UPDATE.ZIP, JUST "update".)
4. Place "UPDATE" into the same folder as your ADB C:\Mini-SDK
5. Hold shift and right click in the folder to "Open command window here"
6. Reboot your phone into RECOVERY MODE (volume up + home)
7. Select "Apply update from ADB"
8. Plug phone into usb on PC
9. In your command window type "adb sideload update" without quotes and enjoy!
If you made it this far and it fails or gives you an error then you did something wrong. Start from step 1 restoring your phone to MJ5
(Option C) - Untested
1. Settings, General, About, Software Update, Check for updates...
2. Download and install update
If you made it this far and it fails or gives you an error then you did something wrong. Start from step 1 restoring your phone to MJ5
Thanks @opsmgr3774 for the donation!
Thanks @Ciberious42 and @evilpotatoman and anyone else I forgot.
Q&A
1. Is this safe?
Yes it's using the same exploit from Root De La Vega to run a script that replaces the bad file that is stopping the OTA from installing.
What the script does:
Code:
mount -o rw,remount /system
rm /system/bin/mobicore-presetup.sh
cp /sdcard/mobicore-presetup.sh /system/bin
rm /sdcard/rldv.sh
2. It doesn't work for me!!!
Try it again from the very beginning and read step by step, slowly. Make sure you didn't miss anything! Download the files again also.
mazdamiata210 said:
Reserved
Click to expand...
Click to collapse
Im sure people would be a little more willing to try this is there was a little more info here.
What are these files fixing when flashed, how do i know that these good/ok files to flash that will not brick my device? Because you said it should work. Not nit picking or even saying that it doesnt work. BUT more info on what this is would be beneficial to everyone.
the2rrell said:
Im sure people would be a little more willing to try this is there was a little more info here.
What are these files fixing when flashed, how do i know that these good/ok files to flash that will not brick my device? Because you said it should work. Not nit picking or even saying that it doesnt work. BUT more info on what this is would be beneficial to everyone.
Click to expand...
Click to collapse
Well you're not flashing anything that isn't safe considering they're all the same files from different threads (that are safe) except for the script file in the miata fix zip that I made.
mazdamiata210 said:
Well you're not flashing anything that isn't safe considering they're all the same files from different threads (that are safe) except for the script file in the miata fix zip that I made.
Click to expand...
Click to collapse
Yes i understand have used the Evilpotato mans process. I was reffering to the miata Fix. Just want to know what we are flashing. I am not a dev i dont know how to look at a file and see if it will work/harm a phone.
the2rrell said:
Yes i understand have used the Evilpotato mans process. I was reffering to the miata Fix. Just want to know what we are flashing. I am not a dev i dont know how to look at a file and see if it will work/harm a phone.
Click to expand...
Click to collapse
It can't harm anything do not worry. If you followed this guide exactly it will work. Worst case scenario is that you will have to start over again. All it does is copy the missing file back onto the phone so it no longer fails at 27% it's a simple 3 line script you can open it in notepad and see what it's doing if you like.
I hope that posting this is not bad form, as I don't mean to sound skeptical of the OP....
Has anyone tried this method and had success?
TeldenW said:
I hope that posting this is not bad form, as I don't mean to sound skeptical of the OP....
Has anyone tried this method and had success?
Click to expand...
Click to collapse
Yes! Me! Lol it's completely safe
This fix is failing. Error appears that the device is not using NB4 update.
mazdamiata210 said:
It can't harm anything do not worry. If you followed this guide exactly it will work. Worst case scenario is that you will have to start over again. All it does is copy the missing file back onto the phone so it no longer fails at 27% it's a simple 3 line script you can open it in notepad and see what it's doing if you like.
Click to expand...
Click to collapse
thats all that i think most people will need to know just add that to the OP. the more info the better. if it will help people with the update then hey people need to be here testing/using this method.
TheChefSLC said:
This fix is failing. Error appears that the device is not using NB4 update.
Click to expand...
Click to collapse
Whoops I forgot to mention to take the ota update for nb4 before continuing! Sorry I'm running on 0 sleep... Try it again and after the mj5 restore update to nb4... then continue from step 2
mazdamiata210 said:
Whoops I forgot to mention to take the ota update for nb4 before continuing! Sorry I'm running on 0 sleep... Try it again and after the mj5 restore update to nb4... then continue from step 2
Click to expand...
Click to collapse
Indeed
after MJ5 restore, I was able to run the RDLV script in order to replace the system file needed, Then I ran the OTA update from recovery for NB4, Upon reboot, I was then able to install the KK update NC2
TheChefSLC said:
Indeed
after MJ5 restore, I was able to run the RDLV script in order to replace the system file needed, Then I ran the OTA update from recovery for NB4, Upon reboot, I was then able to install the KK update NC2
Click to expand...
Click to collapse
How do you run the script?
opsmgr3774 said:
How do you run the script?
Click to expand...
Click to collapse
It is part of the OP, the RDLV.sh file that you copy to the root of the internal storage. This is a script file that will replace the other .sh file on your system partition.
opsmgr3774 said:
How do you run the script?
Click to expand...
Click to collapse
When you finish the mj5 restore and update to nb4... As long as the miata fix files are on your internal memory and you reboot the script will run
mazdamiata210 said:
When you finish the mj5 restore and update to nb4... As long as the miata fix files are on your internal memory and you reboot the script will run
Click to expand...
Click to collapse
Thank you. I had done everything but the nb4 update and it failed so I of course panicked, then noticed TheChefSLC said they "ran" the script and wondered if I had missed a step. It's all squared away and fully updated now. It worked. Hooray.
This deserves a news page recommendation
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
I am getting a temporary error when trying to download the miata_kitkat fix. new link please
EDIT...It is working now. THanks
I can confirm this works. I just did it and I am now on 4.4.2 NC2. Thanks!!
This worked for me...
But I did have to use "(Option B) - Doesn't wipe phone", Option A did not work.
Now to wait for root...
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!!!
Verizon
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 Verizon With Root - since this is Verizon based all bands should work as well
This is Based on the Verizon PH1 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=24723785898787028 Verizon_System.rar
https://www.androidfilehost.com/?fid=24713784966775399 Verizon Bootloader
https://www.androidfilehost.com/?fid=24713784966775400 Verizon Modem
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/Verizon_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_N930VVRS1APH1_CL8720001_QB10528330_REV00_user_low_ship_MULTI_CERT.tar.md5
Step 10b. now click the cp button and select this file - CP_N930VVRS1APH1_CL8720001_QB10528330_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
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
and anyone i missed
this was a complete collaboration and is only available because of those mentioned so be sure to give them thanks
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"
}
screenshots provided by @ohblindone
This Method Completely replaces the Sprint files with verizons. with exception to the kernel, recovery and the su binary. so everything once complete is now verizon and not sprint with verizon touchs thrown in to make it work.
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 Verizon_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
Here's a video Tutorial done by @TechBSwift to help if you have any questions on how this works.
https://m.youtube.com/watch?v=Oi-tuA_EIxA
Tested and working on my VZW Note 7 w/PH1 Firmware.
When you get to step 13, if you decide to go the route of using Busybox on Rails (free app) to install busybox then do the following (also see screenshot):
> Step 13a. If you're installing busybox on rails, it will ask you what you want to do and how you want to do it. Select "Cleanup & Install" and "Normal Method", then click "Next."
If you see "Custom" on screen while booting, don't worry, it doesn't indicate a tripped knox. It should go away after next reboot (after ./root.sh step).
You will probably get an annoying "Security notice" type notification after root (this is triggered by the root itself), if you want to gt rid of this download a root explorer (e.g. root explorer, root browser, etc.) and navigate to /system/app and delete the folder securitylogagent. Reboot and you should be good to go!
?
Sent from my SM-N930T using XDA-Developers mobile app
Xposed install instruction has been moved to :
http://forum.xda-developers.com/showthread.php?t=3461305
If you have any questions or comments about my instructions for xposed, please leave them in the link above.
Want to keep this thread here on topic with @OvrDriVE's new root method.
Thanks
Here we go again..... nice work guys.[emoji106]
Sent from my SM-N920T using Tapatalk
nice ..just have to wait for my replacemant and it's a GO GO GO
Sent from my SM-N930V using XDA-Developers mobile app
How long should you see a blinking curser at step 5L?
Been sitting there blinking for 5 minutes or so.
Wait another 10
Sent from my SM-N930T using XDA-Developers mobile app
nu2droid said:
How long should you see a blinking curser at step 5L?
Been sitting there blinking for 5 minutes or so.
Click to expand...
Click to collapse
It depends, but you should be looking at a roughly 10 minute wait time. Just be patient.
Don't do anything until the blinking cursor goes away.
gotcha, waiting....
just seemed long. thank you.
nu2droid said:
How long should you see a blinking curser at step 5L?
Been sitting there blinking for 5 minutes or so.
Click to expand...
Click to collapse
just wait. when it's done you will see something similar to what i have in instructions
sdcard speed can slow down or speed up that step
Hmmmm... root, fully functionality and doesn't trip Knox. I see myself trading my S7 Duos for a Samsung refurbished Note 7 in the near future!
OvrDriVE said:
just wait. when it's done you will see something similar to what i have in instructions
sdcard speed can slow down or speed up that step
Click to expand...
Click to collapse
Got it... I am good to go..
Setting up and trying everything..
thank you and all the others who helped bringing this to us...
nu2droid said:
Got it... I am good to go..
Setting up and trying everything..
thank you and all the others who helped bringing this to us...
Click to expand...
Click to collapse
Glad you got it working!
Have fun!
bajasur said:
Wait another 10
Sent from my SM-N930T using XDA-Developers mobile app
Click to expand...
Click to collapse
yea i would say like 10-12 mins also for everyone if you cant get past the very first part with adb and the files on the sd card and you know your sd card is formatted and did everything right its simply your sd card is carpped out in the sense of it shows in a computer but a phone wont notice it so throw that pos out and use diff one lmao other then that issue i had this **** is the easiest thing to do
---------- Post added 14th September 2016 at 12:09 AM ---------- Previous post was 13th September 2016 at 11:55 PM ----------
o also if the files dont show up on your phone when you hit apply update from sdcard dont worry their there just glitches out for some reason and doesnt show then only issue was the faulty sdcard i had which didnt show them either and then the new sdcard didnt as well so they may or may not pop up just continue
Once rooted, is it possible to implement the apps/features that Verizon removed and/or replaced when they decided to neuter our phone (Smart Manager, Force Touch, Samsung Cloud, Smart Caller ID, System Settings, etc.)? Personally, that's greatest impetus for me to root.
raneym305 said:
Once rooted, is it possible to implement the apps/features that Verizon removed and/or replaced when they decided to neuter our phone (Smart Manager, Force Touch, Samsung Cloud, Smart Caller ID, System Settings, etc.)? Personally, that's greatest impetus for me to root.
Click to expand...
Click to collapse
@OvrDriVE made Debloater.zip that you can flash using flashfire after you rooted for TMO .... he might be able to make for Verizon but might need to adjust the script little bit to compatible with Verizon device..... No more TMO bloatwares, less Samsung apps and knox free and still 0×00.[emoji4]
TWIST3D_N930T
Just to confirm.. its says doesnt trip knox.. does samsung pay still work?
Sent from my SM-N930V using Tapatalk