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
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 :/
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...
Hi guys.
First of all, all credits go to @ZeroPDA. The processo is from him. Im just making this tut for everyone to see.
Requirements - root
1-download root explorer and terminal emulator
2-download universal init.d
3-go in the universal init.d APP and turn it on.
4- go in root explorer, go to etc/init.d and create a filé named deviceidle. Note that you have to give all permissionários to etc folder and init.d folder in order to be allowed to creat the file.
5-open the file that you just created, deviceidle, with a text editor, and write the line "dumpsys deviceidle disable". Save. Nós erase everything else from the folder init.d.
VERY IMPORTANT - BEFORE THE BELOW 6 STEP, GO TO SETTINGS, ADMIN PERMISSIONS, AUTO INICIALIZE APPS AT BOOT, AMD GIVE PERMISSION TO UNISERSAL iNIT.D
6-reboot your phone.
7-please allow some seconds when it boots, to see the message that universal init.d has been granted with supersu permissionários. This may take 30 seconds after boot.
8-when you see the message, go in terminal emulator and type "su"
9-type "dumpsys deviceidle enabled". If it returns 0 your good to go. If it returns 1 you've done something wrong.
Gonna include a video recorded imeadiatly after boot
New video with steps
https://youtu.be/-FJ6YsVJgxM
Did not work, getting 1 and I redid and followed every step.
Thank you for recognizing my efforts. I decided to make it even more clearer with reference to the apps
Requirements - root
Download root explorer and Terminal Emulator for Android
Download Universal Init.d
Go in the Universal init.d app and turn it on.
Go in root explorer, go to /etc/init.d and create a file named deviceidle with permissions rw- --- --- (Only Owner can Read and Write).
Open the file that you just created, deviceidle, with a text editor, and write the line dumpsys deviceidle disable. Save. You can delete everything else from the folder /etc/init.d Just leave one file deviceidle there (You can also leave 99SuperSUDaemon if it is present)
Reboot your phone.
Please allow some seconds when it boots, to see the message that Universal init.d has been granted with supersu permissions. This may take 30 seconds after boot.
After seeing the message, go to the terminal emulator and type "su"
Type "dumpsys deviceidle enabled". If it returns 0 your good to go. If it returns 1 you've done something wrong.
New vídeo with the steps
https://youtu.be/-FJ6YsVJgxM
I did these exact steps, does still not work..
MFRCNS said:
I did these exact steps, does still not work..
Click to expand...
Click to collapse
do it again. sometimes you have to check the permissions again. at first, with me, i had to check them twice. also, put all permissions in the file created. when yoiu reboot, please allow a few seconds till the message "universal init.d has been granted su privileges"
I writed a new step. its very importan and might be the reason some people arent being sucessfull with this.
before you reboot the phone, GO TO SETTINGS, ADMIN PERMISSIONS, AUTO INICIALIZE APPS AT BOOT, AnD GIVE PERMISSION TO UNISERSAL iNIT.D
For some reason this method does not work for me
I donwload and install everything, but when i try to go through the steps this is what happens:
I open universal init.d and nothing happens , no way to turn it on!
Then, in Root Browser i have no init.d folder inside etc and if i try to create it, the browser gets stuck and no folder is created!!! Please Help
maurosch said:
For some reason this method does not work for me
if i try to create it, the browser gets stuck and no folder is created!!! Please Help
Click to expand...
Click to collapse
Probably either you are not rooted or not given root permissions.
ZeroPDA said:
Probably either you are not rooted or not given root permissions.
Click to expand...
Click to collapse
thank you for your reply. I am rooted and permissions for the etc folder are 777 all clicked!!!i want to do this cause i really miss notifications!!!! at first they work, but after a while i have to reboot the phone to start getting them again!!!
What kind of notification doesn't work? GMail, WhatsApp, Viber? All of them?
Sent from my HUAWEI M2-A01L using Tapatalk
maurosch said:
thank you for your reply. I am rooted and permissions for the etc folder are 777 all clicked!!!i want to do this cause i really miss notifications!!!! at first they work, but after a while i have to reboot the phone to start getting them again!!!
Click to expand...
Click to collapse
give permissions to etc folder and also to init.d folder. when you create the deviceidle file, before you write anything, save the file without nothing and give also full permissions to that file
nosidefcp said:
give permissions to etc folder and also to init.d folder. when you create the deviceidle file, before you write anything, save the file without nothing and give also full permissions to that file
Click to expand...
Click to collapse
i have been usinf this method for awhile, and has worked perfectly.
but since i am on a different firmware now, i had to redo it, and yes it still works...
BUT, only for some time and then it reverts back. (so when checking in Terminal it reads 0, and stays like that for an hour or two, and then automatically turns to 1)
Sent from my HUAWEI NXT-AL10 using XDA Labs
I tried it the first time did not work. Then I opened the Universal Init app and it showed ON and below were the scripts, so I went to SuperSu app to make sure Init app gained permissions, and that was the problem it didn't work in the beginning because did not gain Root. So, went back to the Init app and click the TEST button at the bottom, and there appeared the SuperSu window asking for Root permissions, so, granted permissions, rebooted the phone and opened terminal to make sure it worked this time. SUCCESS, it showed 0 this time. I don't know if it changes back to 1 like someone mentioned above, but I'll check and come back here. Good luck
maurosch said:
thank you for your reply. I am rooted and permissions for the etc folder are 777 all clicked!!!i want to do this cause i really miss notifications!!!! at first they work, but after a while i have to reboot the phone to start getting them again!!!
Click to expand...
Click to collapse
Freeze phone manager. I'm not sure how people are reporting success with this when doze is a feature for all Marshmallow devices and none have this issue. I have no doubt that the problem is with phone manager and I'm sure if we were able to decompile the file properly there would already be a solution.
On B321 after selecting keep wifi on during sleep and keep mobile data on during sleep I have zero notification issues. I don't even have to move any apps to system/app anymore.
The problem is that there is no B321 for L29 officially. Any try to flash B321 to L29 is connected with risk to brick the phone. And there is no reliable guidance how to return back to B180 from B321 if someone doesn't like it.
ajsmsg78 said:
On B321 after selecting keep wifi on during sleep and keep mobile data on during sleep I have zero notification issues. I don't even have to move any apps to system/app anymore.
Click to expand...
Click to collapse
I couldnt find "keep mobile data on during sleep" option. Where is it?
hi my friend
testing this tip
for lock app after sleep facebook line email etc. show noti. but drain batt'
unlock after sleep not show noti. but save batt.
making by wipe down lock frist wipe down unlock second make in recent app
looking at image
{
"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"
}
b180 fixed the gmail notification issue for me, it is already stated in the official change log that it fixes gmail notification.
That's maybe why the report for b180 drains more battery, doze is half disabled on b180 but so far the notification is working like it should.
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
ANNOUNCEMENT: I'M STOPPING THE FOLLOW UP AND UPDATE OF THIS TOPIC TODAY, IF SOMEONE WANTS TO TAKE OVER, CONTACT THE MODERATOR IN THIS LINK.
THE TOPIC REMAINS AS IT IS AND WILL NOT BE UPDATED ANYMORE (BY ME ANYWAY!)
GOOD CONTINUATION TO ALL
Installing an OTA.zip Update with ADB Sideload
- Disclaimer: I don't take any responsibility for anything you do to your tablet, which is to transform it into brick, break, or transform it into coffee machine -
Click to expand...
Click to collapse
In this thread you will find different ways to install an OTA update :
Via ADB SIDELOAD (this post) - Via Recovery Mode - Via Local Upgrade
I am writing this tutorial on ADB Sideload, one more on this topic, in order to be able to push an OTA Zip update, which for some reason could not be done properly.
Sometimes manufacturers allow users to make links or zip files of OTA updates available to other users. Once you have downloaded the OTA zip file, you will need this tutorial to proceed with the installation.
I borrowed the first two screenshots from the web so that I could explain clearly with pictures.
In the end it is very simple and requires little command line knowledge. But you will need to check some things:
- Firmware stock
- Unmodified system partition
- Third party apps like Magisk, Xposed Framework, and as a precaution TWRP Recovery should not be installed on your smartphone
Before starting, here is the list of prerequisites to perform the sideloading of the OTA package.
1. Have a backup of your data, even if theoretically performing a sideload will not erase your data,
2. Download the USB Drivers from the manufacturer, or the latest one from Google ( Link )
3. If you haven't already done so, you must download and install Android SDK Platform-tools (platform-tools_r33.0.2-windows.zip)
4. Don't forget to push on this folder "platform-tools" the file named "Global full Nothing OS 1.1.0.zip" - for example- that you need
4. And finally you will have to activate the USB debugging of your Phone(1) : to do so, you have to go to : Settings => System => Advanced => Type 7 times on the build number => once done, a pop-up will appear and will tell you that you have become a "Developer" => On some devices you will have to type in the Pin code.
5. Once you have become a developer => go back to System => Developer Options => Enable the USB Debug toggle
6. That's it if you are ready to do a Sideload, but also other operations!
{
"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"
}
These prerequisites are essential for this and a number of other operations.
You are ready, the tension is rising! You will succeed!
To do this, you must reboot your Phone(1) into the standard recovery system and you have 2 ways to reboot into Recovery.
1. You can use the hardware key combination specific to your smartphone.
2. Or use the ADB command
Booting into Recovery Stock mode with the ADB command
You go to the start screen of your PC and in the search bar you type:
Code:
cmd
and then press Enter. The command prompt starts.
Depending on where you have placed your "Platform-tools" folder you type:
Code:
C:\WINDOWS\system32>cd c:\platform-tools
and you should see on your command line screen
Code:
c:\platform-tools>
Once you are in your Platform-tools folder, connect your smartphone to your PC, making sure that USb debugging is effective.
Type the following command: adb devices and you should see the identification of your smartphone
When you run an ADB command, you should see an RSA key prompt on your smartphone screen asking you to allow USB debugging. Press OK to allow it.
Type the following command: adb reboot recovery
Then the command: adb sideload "file name".zip - For the example, I typed the full name of the file, but you can rename the file shorter like "nothing_ota".zip
That's it, normally the installation is started and you just have to wait for the update to be installed on your device. Once the installation is successful, you can restart your device.
I hope this tutorial has helped you to push an OTA.zip update.
Go ahead now
Installation via recovery mode
The recovery mode of the Phone(1) is similar to that of the Google Pixel. This allows you to easily sideload the update packages via the recovery interface.
To perform this process, here are the steps and requirements:
Have downloaded the .zip file of the update to your computer
Your Phone(1) must be recognised by the ADB command on your computer
The Process:
Go to your Shell terminal, then run the recognition command:
Code:
adb devices
then the command :
Code:
adb reboot recovery
On your Phone(1) screen, you should see this "No command"
While pressing the Power button, press the Volume Up button then release both buttons quickly. The Android recovery menu should be visible.
Nothing Phone 1 recovery mode
On your Phone(1) screen, select the option: Apply update from ADB.
On your computer, run the command:
Code:
adb devices
This should return the serial number of the device with the 'sideload' next to its name, indicating that your device is connected to the computer in sideload mode.
On your computer, run the command:
Code:
adb sideload "filename".zip
The "filename" part should be replaced with the full path, followed by the name of the file downloaded in step 1.
The update will be installed on your phone.
Once the installation is complete, select "Reboot system now" on your phone to reboot into the new version.
Well done, you have installed the new update of Nothing OS to your Phone(1) with success
To date I still haven't received my phone(1). Once I have it in my hands, I will make screenshots about this tutorial.
Install OTA using Local Upgrade method
Create a folder named “ota” (without the quotes) at the root of the internal storage. Meaning outside every folder.
Copy the OTA update ZIP file from above to that folder.
Open the phone app and Dial ##682##
This should launch an offline update tool.
The tool will scan for an OTA file from internal storage and install it.
If that fails, you can manually browse for the OTA package.
After selecting the OTA file, the wizard will apply the update.
Reboot the device and you are on the latest firmware.
Reserved 3
I think also after update, reboot, redo the step and sideload also Magisk for keep root
Pho3nX said:
I think also after update, reboot, redo the step and sideload also Magisk for keep root
Click to expand...
Click to collapse
Yes I agree, but those tutos are for everyone, and everyone doesn't rooted his smartphone like us
So I won't confuse them
hello, thanks for the guide, when I do all the steps without any problems and reboot, it opens with the old version, where could I be doing wrong?
This will work to downgrade the phone also?
pankspoo said:
This will work to downgrade the phone also?
Click to expand...
Click to collapse
no, np1 has a very strict anti rollback check. I don't suggest to downgrade this phone
sh4tteredd said:
no, np1 has a very strict anti rollback check. I don't suggest to downgrade this phone
Click to expand...
Click to collapse
So we can use your Windows tool to downgrade ?
pankspoo said:
So we can use your Windows tool to downgrade ?
Click to expand...
Click to collapse
I won't downgrade this phone at all. Btw maybe I'm wrong and it can work but I'm not sure and I don't suggest to do it
Hi, I am currently trying to update from Nothing OS 1.1.3 to 1.1.4 but i keep receiving this error even though i have uninstalled magisk, didn't modify my system partition and have a stock firmware. The phone is still able to boot correctly after this failed installation but i cannot flash the new update.
demiii said:
Hi, I am currently trying to update from Nothing OS 1.1.3 to 1.1.4 but i keep receiving this error even though i have uninstalled magisk, didn't modify my system partition and have a stock firmware. The phone is still able to boot correctly after this failed installation but i cannot flash the new update.
View attachment 5716899
Click to expand...
Click to collapse
Which version of ADB Sideload do you use ?
Post 1 or Post 2
Sib64 said:
Which version of ADB Sideload do you use ?
Post 1 or Post 2
Click to expand...
Click to collapse
What I did was reboot to recovery, navigate to Apply Update via Sideload through the recovery interface and from there entered the command adb sideload filename.zip so i guess it is the method in post 2
UPDATE:
I have tried the method in Post 1 and this error shows up:
UPDATE 2:
I have tried revoking USB DEBUGGING authorization, adb kill-server, adb start-server and authorizing again
I have tried deleting adbkey and adbkey.pub files in C:Users/$Name/.android
I have tried following suggestions about solving this error both from this and this StackOverflow thread
Nothing worked for me.
You don't need to use ADB to sideload an OTA, the nothing phone contains an OTA updater In the phones os already, the only thing you need the computer for is to move the OTA to the phone
Here is what someone on the nothing discord said to do and it worked
dont sideload
Create a folder named “ota” (without the quotes) at the root of the internal storage of your phone. Then copy the update ZIP file to that folder.
Dial `*#*#682#*#* `to open up the offline update tool.
You can also use an activity launcher app to locate and execute the “OfflineOTAUpgrade” tool. The package name of the tool is com.nothing.OfflineOTAUpgradeApp.
Hi, I have just tried your method but an error window pops up:
Hello, can I normally use in built in recovery updater to upgrade to 1.1.4 if I'm rooted and have Nacisk installed?
Ky0sHiR0 said:
Hello, can I normally use in built in recovery updater to upgrade to 1.1.4 if I'm rooted and have Nacisk installed?
Click to expand...
Click to collapse
You can only upgrade not downgrade
demiii said:
Hi, I have just tried your method but an error window pops up:
View attachment 5717197
Click to expand...
Click to collapse
If you go on nothing discord and put that error maybe they can help