Related
I was using my N73G at home this evening and it spontaneously rebooted to the Google splash screen... and stayed there for well over 5 minutes. I tried long pressing power to reboot again, and it went back to the same screen.
TWRP is installed, and I am able to get into that. I tried wiping cache and dalvik, and it booted straight back to the splash screen again, solid for 3 minutes before I went back into TWRP. In the file manager my files all appear to be safe and sound. I am currently running a nandroid backup before I futz with it any further. TWRP has not given me any errors over the course of the backup.
I should note that I have had some trouble connecting to TWRP over ADB although I can use ADB when booted into the OS. So if I need to go fishing for files over USB, I hope I won't come up empty. If necessary I could try flashing CWM recovery instead, as I may be able to get my files more easily that way.
Anyway, ideas are welcome. I was running a bake of the Modaco custom ROM, and the zip for that ROM is still on the device, so I was thinking I might try reflashing that. But first I should try and get my nandroid off the slab.
As fortune would have it, I have already ordered an RMA device swap due to issues with the speaker blowing out. So if I fail to resuscitate it, help is already on the way. But I would like my tab to work again by the time I go back to work Monday
Update: Figured out the ADB recovery driver problem. Nandroid backup was successful. I'm now pulling the backup image to my desktop. Will try a ROM reflash next.
UPDATE UPDATE: The weirdest thing. I noticed while it was plugged into my machine, still stuck on the Google boot logo, that I was able to see the tab in ADB devices. So I typed in adb logcat and found some message about /system/xbin/busybox missing.
I browsed with ADB shell and found there is a busybox in /system/bin. So I did ADB remount, and then copied busybox from bin to xbin. Entered a reboot command, and bam! Five seconds on the Google splash, and then right to the booting X.
Why in the world would this have happened... maybe the busybox installer app got an upgrade and botched an attempt to upgrade busybox?
cmstlist said:
UPDATE UPDATE: The weirdest thing. I noticed while it was plugged into my machine, still stuck on the Google boot logo, that I was able to see the tab in ADB devices.
Click to expand...
Click to collapse
The adb daemon - adbd - is started by init as a service so long as you have previously enabled adb debugging. So, it happens before the whole android reboot sequence kicks off (checking that all .apks without odex files have up-to-date .dex entries in dalvik cache, permission checks, etc.) You can access it on devices that are "stuck" in the late stage of booting.
TWRP - for better or worse - does not claim the same USB vid/pid ID that is used by the N7's ADB facility, even though the exact same driver can be used for either adb mode ... so long as you manually went into the driver install package and add the "universal" vid/pid values used by TWRP to the driver's .inf file. I think this is done simply to minimize the effort keeping up with new device identifiers by the TWRP team. It does create the impression that separate drivers are needed - but only because neither of the two drivers (Google vs. Universal) have the "other's" vid/pid pair listed as matching devices in their .inf files.
Anyhow, you got it all sorted out - congrats.
Thanks! I had been worried maybe the whole file system was corrupted, so in comparison this was a relief.
Sent from my Galaxy Nexus using Tapatalk 2
Please note: This will not recover you from a bricked device. This applies to bootloops caused by modifications you made, AFTER successfully rooting.
So you changed your build.prop or deleted a system file you shouldn't have? Your phone is now constantly rebooting? Your variant doesn't have a KDZ available? Here's an easy, albeit time consuming method to recover. (without TWRP or KDZ and no data loss)
First off, if you haven't caused a bootloop yet and you are doing a lot of modifications, do the following. Go to SuperSU and allow su requests on boot. This will allow you to fix minor problems during the bootloop, such as restoring your backed up build.prop or other modified system file. Many times, people will forget to set permissions on a file, especially build.prop. This will cause a bootloop.
If you GRANTED su requests during boot in SuperSU:
Say you set the wrong permissions on build.prop:
While your phone is bootlooping, plug it into your PC, then execute the following commands:
Code:
adb shell
$ stop
$ su
# chmod 0644 /system/build.prop
# reboot
Say you screwed the build.prop up and need to restore a backup you made to your sdcard:
Code:
adb shell
$ stop
$ su
# cp /sdcard/build.prop /system/build.prop
# chmod 0644 /system/build.prop
# reboot
If you DID NOT grant su requests during boot in SuperSU (or if you have tried and failed other methods to recover):
While your phone is bootlooping, plug it into your PC, then do the following:
1. Locate the image you used to root your phone.
2. If the image is on your phone still, just re-root. Your phone will be fixed.
3. If you deleted it from your internal SD card continue to step 4.
4. Open command prompt in folder on your PC containing image, then issue the following command:
This will take a VERY long time (20-30 minutes)
Code:
adb push system_image_name.img /sdcard/system_image_name.img
Note: If you don't have adb mapped to your environment variables, move the image into your platform-tools folder, or whichever folder contains adb. Then run the above command.
5. Re-root
Can't wait to try this when i get home. I soft bricked my LG G4 with a bad system.img so i am trying to restore. Is this actually going to allow me to push the img file back to the phone even though i cant boot?
minirx7 said:
Can't wait to try this when i get home. I soft bricked my LG G4 with a bad system.img so i am trying to restore. Is this actually going to allow me to push the img file back to the phone even though i cant boot?
Click to expand...
Click to collapse
In your case I'd say 50/50. It depends if it at least gets to the part of the boot sequence which enables adb.
I KDZ back to stock, then re-rooted to fix mine. No data loss.
Sent from my VS986 using XDA Free mobile app
Meibs81 said:
I KDZ back to stock, then re-rooted to fix mine. No data loss.
Sent from my VS986 using XDA Free mobile app
Click to expand...
Click to collapse
That is a great method to use, but several variants don't have KDZs :crying:
I'm on the Sprint variant and am getting the Security Error loop. I have no system.img yet, however I can't seem to adb push anything (or see the phone with ADB at all)... am I doing something wrong?
pcrhckyman said:
I'm on the Sprint variant and am getting the Security Error loop. I have no system.img yet, however I can't seem to adb push anything (or see the phone with ADB at all)... am I doing something wrong?
Click to expand...
Click to collapse
That would not be considered a bootloop. That's a brick. I'm sorry, but in your case unless you already had a system image on your phone to flash, you are SOL until we get a TOT file.
tabp0le said:
In your case I'd say 50/50. It depends if it at least gets to the part of the boot sequence which enables adb.
Click to expand...
Click to collapse
Well i am able to access factory reset and i am able to get into download mode and see it from the send_command tool.. HOpe that means my odds are 100% instead!
minirx7 said:
Well i am able to access factory reset and i am able to get into download mode and see it from the send_command tool.. HOpe that means my odds are 100% instead!
Click to expand...
Click to collapse
Not necessarily. Download mode and factory reset(recovery) are located on different partitions than boot and system. Do you at least get to the carrier boot animation while attempting to boot? If so, your chances are good. If not, your chances are bad. The initial commands, including adb push have to be run while the phone is attempting to boot. NOT in download mode or recovery.
tabp0le said:
In your case I'd say 50/50. It depends if it at least gets to the part of the boot sequence which enables adb.
Click to expand...
Click to collapse
tabp0le said:
Not necessarily. Download mode and factory reset(recovery) are located on different partitions than boot and system. Do you at least get to the carrier boot animation while attempting to boot? If so, your chances are good. If not, your chances are bad. The initial commands, including adb push have to be run while the phone is attempting to boot. NOT in download mode or recovery.
Click to expand...
Click to collapse
I get stuck on the LG logo where the light flashes on and off. While this happens if the phone is connected to the computer i hear the USB connection sound in windows. I will be trying it in a few hours.. hope it works!
minirx7 said:
I get stuck on the LG logo where the light flashes on and off. While this happens if the phone is connected to the computer i hear the USB connection sound in windows. I will be trying it in a few hours.. hope it works!
Click to expand...
Click to collapse
You may be able to do it then. Let us know how it goes!
Delete
Peeptastic said:
Can I use this method to solve my particular problem (bypassing setup - I cannot move forward in the setup after a hard reset). Thanks (Can give you more info if you need it)
Click to expand...
Click to collapse
You may be able to. Does your phone boot? How far does it get in the booting process? If you get to initial phone setup, and can't get to the settings app to enable developer options and debugging, then you probably can't use this.. I'm not sure it would work, but you could try-During boot, debugging might enabled by default. (I'm not sure) Right when your bootanimation comes on you might be able to run the command:
Code:
adb shell stop
Then run the rest of the commands/follow this guide. It would be worth a shot.
Delete
Peeptastic said:
I will try it. I can get into the phone to the screen right after entering wifi, then it just stalls. It doesn't freeze, but it also doesn't go anywhere. This is with wifi and data (I left the phone on for a bit and data picked up). If it's related, I turned on Voice Assistance and when the phone gets to the first set up screen she says something about Google play services not working and then "Hangouts needs Google Play services". That could be why I can't move on.....
---------- Post added at 05:10 PM ---------- Previous post was at 05:07 PM ----------
I hear windows chime when it starts up, and the computer charges the phone. Running your command tells me: error: device not found.
Click to expand...
Click to collapse
How did you get in this situation to begin with? Are you able to get into settings at all?
Delete
Peeptastic said:
Factory reset because of the Google play error. Only it looks like Factory reset didn't fix it. And nope, can't get into settings because I can't get out of the set up screen (setup like when you first turn on the phone out of the box). I can get to download mode and stock recovery. As far as I know, there is no way to skip the original LG setup (clockwise button press doesn't work).
Can I adb sideload the image and try that way
Click to expand...
Click to collapse
Unfortunately that will not work. adb sideload is only for flashing .zip files.
tabp0le said:
Unfortunately that will not work. adb sideload is only for flashing .zip files.
Click to expand...
Click to collapse
Delete
every time I run the command while in bootloop it says "Device not found"
sarwaria23 said:
every time I run the command while in bootloop it says "Device not found"
Click to expand...
Click to collapse
This is what is happening to me too. I can see that the phone during boot loop is recognized. I check the device drivers and it shows up under windows as LG.
Crap. not good.
Hi Guys,
This is my first message in this forum even if I read so many useful stuff here in the last few years. So first of all thanks for the many useful tips
Now I am facing a problem that probably is prohibitive even for you gurus.
This morning I broke the screen of my nexus 4, I can still boot it and the os seems to work fine. Unfortunately the touch screen is totally gone and I am not able to unlock the security pattern and access the phone. The phone is stock and not rooted.
I would like to retrieve all the data stored in the phone and access some app, so I tought I could use [email protected] Unfortunately adb tool says: device unauthorized. Please check the confirmation dialog in your device.
Of course I can't access any confirmation dialog since the touch screen is not working. Then I tought I could go in recovery mode and do something but when I reboot in bootloader and then go into recovery mode I only see the green android and a message that sounds like "no command".
What can I do? The best option would be to unlock adb and take control of the device trough [email protected] Do you guys thinks it is possible?
Just a quick update: I was able to access the recovery mode but I can't find my device in adb devices list
_Braid_ said:
Just a quick update: I was able to access the recovery mode but I can't find my device in adb devices list
Click to expand...
Click to collapse
Do you have USB debugging enabled? Is you bootloader locked or unlocked? If you boot into the bootloader, try using the command "fastboot devices" instead. You can only access adb from recovery with a custom recovery like TWRP.
theminikiller said:
Do you have USB debugging enabled? Is you bootloader locked or unlocked? If you boot into the bootloader, try using the command "fastboot devices" instead. You can only access adb from recovery with a custom recovery like TWRP.
Click to expand...
Click to collapse
USB debugging should be available but if I try to use adb while the phone is turned on I get the "unathorized" message.
What should I do after I used command "fastboot devices"? I only see: "deviceidnumber" fastboot
In the bootloader menu I see "LOCK STATE - unlocked, SECURE NOOT- enabled"
What should I do then?
Thanks for your help!
_Braid_ said:
USB debugging should be available but if I try to use adb while the phone is turned on I get the "unathorized" message.
What should I do after I used command "fastboot devices"? I only see: "deviceidnumber" fastboot
In the bootloader menu I see "LOCK STATE - unlocked, SECURE NOOT- enabled"
What should I do then?
Thanks for your help!
Click to expand...
Click to collapse
I was able to flash a custom recovery! It is the clockwork 6.0.4.7.
Now when I am inside the clockwork and I run "adb devices" I get "unauthorized". Is there a way to authorize adb through the recovery mode?
_Braid_ said:
I was able to flash a custom recovery! It is the clockwork 6.0.4.7.
Now when I am inside the clockwork and I run "adb devices" I get "unauthorized". Is there a way to authorize adb through the recovery mode?
Click to expand...
Click to collapse
Try TWRP instead of CWM. I think that will work. If it doesn't I at least know that TWRP will give you access to your sdcard so you at least can copy what's on there.
theminikiller said:
Try TWRP instead of CWM. I think that will work. If it doesn't I at least know that TWRP will give you access to your sdcard so you at least can copy what's on there.
Click to expand...
Click to collapse
If I install latest TWRP recovery will it work with volume and power button? I can't use touchscreen and I am not able to find on google a version of the TWRP which is not touch
_Braid_ said:
If I install latest TWRP recovery will it work with volume and power button? I can't use touchscreen and I am not able to find on google a version of the TWRP which is not touch
Click to expand...
Click to collapse
Oh, heh, forgot about that. Lol. Umm, don't think so unfortunately. But I don't think you actually need to touch anything. Just boot into TWRP and plug it into the computer. I might be wrong about ADB working with it though. But I'm sure you will be able to access your sdcard. Or can you access your sdcard when booting normally without entering your pattern? If so then that part is useless [emoji14]
theminikiller said:
Oh, heh, forgot about that. Lol. Umm, don't think so unfortunately. But I don't think you actually need to touch anything. Just boot into TWRP and plug it into the computer. I might be wrong about ADB working with it though. But I'm sure you will be able to access your sdcard. Or can you access your sdcard when booting normally without entering your pattern? If so then that part is useless [emoji14]
Click to expand...
Click to collapse
Just flashed TWRP and I am able to use adb!!!
Now what should I do to "authorize" my device and be able to use [email protected] when reboot?
_Braid_ said:
Just flashed TWRP and I am able to use adb!!!
Now what should I do to "authorize" my device and be able to use [email protected] when reboot?
Click to expand...
Click to collapse
I'm not sure... Bit i think you should be able to get your data from the phone via adb without an app. I was originally going to suggest using the command "adb backup" but it seems like you have to allow that from your phone which you need your screen to do. You could try it when you are booted in TWRP maybe it won't need confirmation then? No idea. The command and it's various settings are detailed here: http://forum.xda-developers.com/galaxy-nexus/general/guide-phone-backup-unlock-root-t1420351. I honestly forgot about the app and just thought about how to get adb working... Sorry [emoji14]
theminikiller said:
I'm not sure... Bit i think you should be able to get your data from the phone via adb without an app. I was originally going to suggest using the command "adb backup" but it seems like you have to allow that from your phone which you need your screen to do. You could try it when you are booted in TWRP maybe it won't need confirmation then? No idea. The command and it's various settings are detailed here: http://forum.xda-developers.com/galaxy-nexus/general/guide-phone-backup-unlock-root-t1420351. I honestly forgot about the app and just thought about how to get adb working... Sorry [emoji14]
Click to expand...
Click to collapse
unfortunately as soon as I was able to run [email protected] I realided that it does not allow to control the device but only mirror the screen. Do you guys know if there is an app that allows to control the screen of a device? Now my device is debug authorized, rooted and with custom recovery.
_Braid_ said:
unfortunately as soon as I was able to run [email protected] I realided that it does not allow to control the device but only mirror the screen. Do you guys know if there is an app that allows to control the screen of a device? Now my device is debug authorized, rooted and with custom recovery.
Click to expand...
Click to collapse
What exactly are you trying to backup? If you want to backup the whole device I think it is possible to make a nandroid backup remotely from a computer with TWRP, but unfortunately I'm not sure how. Did you try the adb command? That should also backup everything I think, if it works that is...
theminikiller said:
What exactly are you trying to backup? If you want to backup the whole device I think it is possible to make a nandroid backup remotely from a computer with TWRP, but unfortunately I'm not sure how. Did you try the adb command? That should also backup everything I think, if it works that is...
Click to expand...
Click to collapse
I am trying to retrieve data from one application. The application is financisto and there I saved all my expense information for years. Probably this does not make sense to you but I really want to recovere those data. I don't know if financisto save the db somewhere inside the phone so I thought that the easiest way would be to control remotely the phone access the app and do a db backup and export.
_Braid_ said:
I am trying to retrieve data from one application. The application is financisto and there I saved all my expense information for years. Probably this does not make sense to you but I really want to recovere those data. I don't know if financisto save the db somewhere inside the phone so I thought that the easiest way would be to control remotely the phone access the app and do a db backup and export.
Click to expand...
Click to collapse
Ahh i see, unfortunately I am not aware of any way to do that, but I'm not that knowledgeable about that so it is very possible there exists a very easy and obvious way.
Guys I finally did it!
I pulled the db of the app with the following command: adb pull /data/data/ru.orangesoftware.financisto
Then I installed the same application in another phone and I pushed my old db with adb push. When I started the application everything was there again :victory:
Thank you very much for your help!
_Braid_ said:
Guys I finally did it!
I pulled the db of the app with the following command: adb pull /data/data/ru.orangesoftware.financisto
Then I installed the same application in another phone and I pushed my old db with adb push. When I started the application everything was there again :victory:
Thank you very much for your help!
Click to expand...
Click to collapse
Great! I'm glad you got your data xD
elonus said:
Great! I'm glad you got your data xD
Click to expand...
Click to collapse
scrcpy should give you control as well as video.
GitHub - Genymobile/scrcpy: Display and control your Android device
Display and control your Android device. Contribute to Genymobile/scrcpy development by creating an account on GitHub.
github.com
Retail Verizon Note 4 N910VVRU2BPA1 going to the Developer Mode, Relax and take your time, You're in no hurry. I reduced the number of steps to gain permanent root and unlock the bootloader.
Files and HYPERLINKS you may need:
View attachment SAMSUNG_USB_Driver_for_Mobile_Phones.zip
View attachment minimal_adb_fastboot_v1.3.1_setup.zip
View attachment samsung_unlock_n4-fix.zip
View attachment NewKingrootV4.85_C139_B255_en_release_2016_03_29_105203.zip
View attachment 3779589
View attachment Emotion-TW-5.1.1-nightly-r21-RC1-SM-N910P.zip
View attachment BETA-SuperSU-v2.71-20160331103524.zip
View attachment Odin3_v3.10.7.zip
View attachment twrp-3.0.2-0-trltevzw.tar.zip
View attachment Debloater-setup-v3.90.zip
( Re-partition sd card ) ( PaulPizz ROM-5.1.1 is under Past Builds )
Here we go....In Windows, Copy samsung_unlock_n4-fix to the "Minimal ADB and Fastboot" install folder location.
On Phone, after doing a Factory Reset and without a sim card, Skip all initial phone setup except wifi.
Rejected all popup offers and tick don’t remind me.
Connect phone to usb as a Media Device then Copy these files to the phones internal storage.
(1)NewKingrootV4.85_C139_B255_en_release_2016_03_29_105203.apk
(2)Emotion-TW-5.1.1-nightly-r21-RC1-SM-N910P.zip
(3)BETA-SuperSU-v2.71-20160331103524.zip
Disconnect usb cable and enable USB debugging, allow Unknown sources installations, also change Display timeout to 10 min. and format your sd card. Close all recent apps. Reconnect usb cable ( When prompted click Always allow usb debugging on this computer)
Install and open Kingroot ( decline Google offers...) and go to the point "Root access is unavailable" DO NOT start root yet, WAIT until the last second so the phone will remain stable. Copy the name "samsung_unlock_n4-fix" from the actual file so it will be on your clipboard and you can right click it into the adb commands.
Start the program "Minimal ADB and Fastboot" and use the commands
(1) adb devices
(2) adb push samsung_unlock_n4-fix /data/local/tmp/
(3) adb shell
{[ HERE NOW Start Rooting with Kingroot. Once phone is rooted continue with the adb commands }]
(4) su ( You have to grant root permission on the phone and continue)
(5) cd /data/local/tmp/
(6) chmod 777 samsung_unlock_n4-fix
(7) chown root.root samsung_unlock_n4-fix
(8) ./samsung_unlock_n4-fix
When prompted type in yes and Wait... Wait for the phone to go into a boot-loop then disconnect the usb cable, pull the battery and SD card.
Check in Download, you should now have MODE: Developer. The boot-loader is unlocked.
On computer close “Minimal ADB and Fastboot” and open Odin untick auto reboot. Connect usb cable then flash twrp-3.0.2-0-trltevzw.tar.md5. Wait a minute... untill Odin finishes then pull the battery.
Next to last thing, reinstall battery and manually boot into recovery. You now have a unlocked bootloader with TeamWin Recovery. STOP FIRST thing, use it to make a complete backup { Now at this point you could restore a TWRP backup or -HYPERLINK-install a custom ROM. OR To remain stock with root continue.......}
Install Emotion-TW-5.1.1-nightly-r21-RC1-SM-N910P.zip and BETA-SuperSU-v2.71-20160331103524.zip with TWRP from internal storage. Then do a Factory Reset with TWRP or from within the phones setting and it will be good to go. -HYPERLINK-To reuse the SD card re-format / re-partition it with your computer.
I have also been able to used Odin to flashed the SM-N910V Developer Edition up to date with the retail BPA1 file found on Sammobile then used the direction above to convert it back to Developer Mode. Have Fun and less get busy before Verizon closes the window.
I recommend using Gatesjunior's Debloater program to block SDM.apk before reconnecting wifi or someday you could get a over the air updated that could lock it back up.
Some people are having problems with Kingroot because they are starting off with a corrupted phone.
To clear up corruption, junk files or whatever from your phone Odin Stock 5.1.1, and do a Factory Reset twice in a row. Restore from within Recovery and from within the Phone Setting. Skip all the initial phone setup just do the clean up twice. After that you could still have some corruption but, That should clean it up.
doctor-cool said:
Retail Note 4 going to the Developer Mode, using the same files found HERE http://forum.xda-developers.com/note-4-verizon/general/guide-noobs-guide-to-perm-root-twrp-t3360883. Relax and take your time, Your in no hurry. I stabilized the process and reduced the number of steps to gain permanent root and unlock the bootloader.
Here it is....In Windows, Copy samsung_unlock_n4-fix & BETA-SuperSU-v2.71-20160331103524.zip to the Minimal ADB and Fastboot install folder location.
On Phone, after doing a factory reset in recovery and without a sim card, I skipped all the initial phone setup except for putting in my wifi password.
I rejected all popup offers and clicked don’t remind me later. I deleted the time widget to make room for shortcuts so I could work on the home screen.
Connect phone to usb as a Media Device then Copy these files to the phones internal storage.
1. Emotion-TW-5.1.1-nightly-r21-RC1-SM-N910P.zip
2. NewKingrootV4.85_C139_B255_en_release_2016_03_29_105203.apk
3. BETA-SuperSU-v2.71-20160331103524.zip
Disconnect usb cable and enable USB debugging, allow Unknown sources installations also I would change Display timeout to 10 min. and format your sd card. Close all resent apps. Reconnect usb cable (if and when prompted click Always allow usb debugging on the computer)
Install and open Kingroot on the phone go to the point that says "Root access is unavailable" DO NOT START ROOT yet WAIT!!! Close all resent apps and ok the popup about recent apps.
Pull the battery and if you haven’t already done it, install a formatted sd card. Power up the phone and connect usb cable.
{[Be ready to grant permission when asked by phone.}] Close all resent apps again. Open Kingroot and go to the point "Root access is unavailable" DO NOT start root yet, wait until the last second so the phone will remain stable. I would copy the name "samsung_unlock_n4-fix" from the actual file so it will be on your clipboard and you can right click it into the adb commands.
Start the program "Minimal ADB and Fastboot" and type the commands
(1) adb devices (if and when prompted click Always allow usb debugging on the phone)
(2) adb push samsung_unlock_n4-fix /data/local/tmp/
(3) adb shell
{[ HERE NOW Start Rooting with Kingroot once phone is rooted continues with adb commands }]
(4) su ( you have to grant permission on the phone and continue)
(5) cd /data/local/tmp/
(6) chmod 777 samsung_unlock_n4-fix
(7) chown root.root samsung_unlock_n4-fix
(8) ./samsung_unlock_n4-fix
Wait... Wait for the phone to go into a boot-loop then disconnect usb cable pull the battery and SD card.
Check in Download, you should now have MODE: Developer. The boot-loader is unlocked.
On computer close “Minimal ADB and Fastboot” and start Odin. Connect usb cable to flash twrp-3.0.2-0-trltevzw.tar.md5.
Here is a tricky part. As soon as Odin finishes and you can feel the phone vibrate off quickly pull the battery or it will reload stock recovery.
Next to last thing, reinstall battery and manually boot into recovery. Now you have a unlocked bootloader with permanent Kingroot root.
Now install Emotion-TW-5.1.1-nightly-r21-RC1-SM-N910P.zip then BETA-SuperSU-v2.71-20160331103524.zip with TWRP from internal storage do a Factory Reset with TWRP and it’s good to go.
I also used Odin to flashed the SM-N910V Developer Edition up to date with the retail BPA1 file found on Sammobile then used the direction above to convert it back to Developer Mode. Have Fun and less get busy before Verizon closes the window.
I think we should use Gatesjunior's Debloater program to block SDM.apk or we could get a over the air updated that could lock it back up.
Click to expand...
Click to collapse
Follow all steps and work like a charm thanks :good::good::good::good::good::good:
if we untick auto reboot we can access twrp after manual reboot without any problem
vvverma said:
Follow all steps and work like a charm thanks :good::good::good::good::good::good:
if we untick auto reboot we can access twrp after manual reboot without any problem
Click to expand...
Click to collapse
I have not tried the untick auto reboot. In should work in this case but be careful making changes to Odin.:fingers-crossed:
doctor-cool said:
I have not tried the untick auto reboot. In should work in this case but be careful making changes to Odin.:fingers-crossed:
Click to expand...
Click to collapse
That is a step mentioned in some of the other guides. It would make the experience a little less harrowing as during the last step people could simply power the phone back up in recovery themselves instead of having to try to pull the battery just after they feel the phone vibrate.
Point taken people can choose for themselves
MissionImprobable said:
That is a step mentioned in some of the other guides. It would make the experience a little less harrowing as during the last step people could simply power the phone back up in recovery themselves instead of having to try to pull the battery just after they feel the phone vibrate.
Click to expand...
Click to collapse
Thanks for the information. [/B]
Tested and EDITED untick auto reboot and other improvments. Works Great[/COLOR]
So glad there's another thread for this. Maybe my mailbox will stop blowing up.
It worked perfectly!! Thank you so much!
I was a little skeptical about that 910P kernel image, but no problems so far, and the SuperSU bootloop didn't occur this time.
I didn't even have to do a factory reset and it worked.
EDIT:
May have spoken too soon. I inserted my SD card and the screen went blank and the phone buzzed once, almost as if it had restarted. I held down the PWR and two VOL buttons to force restart it and I may be stuck at the Verizon logo screen. It hasn't rebooted, but it's not doing anything.
EDIT AGAIN:
I force-rebooted again on the Verizon screen and it booted up. No problems after formatting the SD card with a computer.
Zacharee1 said:
It worked perfectly!! Thank you so much!
I was a little skeptical about that 910P kernel image, but no problems so far, and the SuperSU bootloop didn't occur this time.
I didn't even have to do a factory reset and it worked.
EDIT:
May have spoken too soon. I inserted my SD card and the screen went blank and the phone buzzed once, almost as if it had restarted. I held down the PWR and two VOL buttons to force restart it and I may be stuck at the Verizon logo screen. It hasn't rebooted, but it's not doing anything.
EDIT AGAIN:
I force-rebooted again on the Verizon screen and it booted up. No problems after formatting the SD card with a computer.
Click to expand...
Click to collapse
Some people are having problems because they have already corrupted their phone rooting while it was unstable. They need to Factory Restore. Not only is Samsung and Verizon working to block root but so is Google. The SD Card need to be formatted with a PC.
doctor-cool said:
Some people are having problems because they have already corrupted their phone rooting while it was unstable. They need to Factory Restore. Not only is Samsung and Verizon working to block root but so is Google. The SD Card need to be formatted with a PC.
Click to expand...
Click to collapse
So the factory reset is a safety step?
For Security and to avoid corruption problems.
Zacharee1 said:
So the factory reset is a safety step?
Click to expand...
Click to collapse
At some time we all have given Google permission to gather information. For that reason and because Kingroot is connected to a Chinese Server. I would prefer not having my information on the phone when rooting with Kingroot.
I would call Kingrooting with your personal accounts on the phone HOT ROOTING. If I were going to HOT ROOT I would remove all my personal accounts from the phone. I have done it and it will work but I prefer to do a factory restore.
doctor-cool said:
At some time we all have given Google permission to gather information. For that reason and because Kingroot is connected to a Chinese Server. I would prefer not having my information on the phone when rooting with Kingroot.
I would call Kingrooting with your personal accounts on the phone HOT ROOTING. If I were going to HOT ROOT I would remove all my personal accounts from the phone. I have done it and it will work but I prefer to do a factory restore.
Click to expand...
Click to collapse
Oh, so privacy. Well I have nothing very important on this phone, so that's fine for me. If I do this on someone else's phone though, I'll definitely remember that.
I am an idiot that is stoned and had no issues following these directions thanks! Stupid question.. the stuff it copied to my sdcard during rooting.. do i need to keep that for anything? or is it basically used as swap space?
Icetech3 said:
I am an idiot that is stoned and had no issues following these directions thanks! Stupid question.. the stuff it copied to my sdcard during rooting.. do i need to keep that for anything? or is it basically used as swap space?
Click to expand...
Click to collapse
I read somewhere you should keep it because someday we might be able to make a backup out of it. I deleted mine. I am able to use Odin to restore the original N910VVRU2BPA1 any time I want it.
Need help please noon
So I followed all the steps and achieved permanent root and Developer Edition everything worked great I went back into the T wrp recovery 2 wipe my cash and ended up wiping everything including operating system so someone told me to just install a custom rom I install custom ROM two different ones actually the new cm marshmallow and another one both of them do not recognize my SIM card I am using a Straight Talk SIM inside of a Verizon Note 4 I don't know what to do at this point can someone please help me thank you for the great unlock directions extremely user-friendly much appreciated.
Was curious... i cannot get TWRP to see my external SD.. anyone else have this issue? not a major thing just annoying...
And to the guy above.. i put on the CM13 rom and using a ting sim it works fine.. so not sure.. sorry.
doctor-cool said:
At some time we all have given Google permission to gather information. For that reason and because Kingroot is connected to a Chinese Server. I would prefer not having my information on the phone when rooting with Kingroot.
I would call Kingrooting with your personal accounts on the phone HOT ROOTING. If I were going to HOT ROOT I would remove all my personal accounts from the phone. I have done it and it will work but I prefer to do a factory restore.
Click to expand...
Click to collapse
I would also format, not just wipe your data partition when you flash your first ROM as well.
---------- Post added at 03:26 PM ---------- Previous post was at 03:24 PM ----------
Icetech3 said:
Was curious... i cannot get TWRP to see my external SD.. anyone else have this issue? not a major thing just annoying...
And to the guy above.. i put on the CM13 rom and using a ting sim it works fine.. so not sure.. sorry.
Click to expand...
Click to collapse
You're not the first here to have problems with sd cards in TWRP. There are several threads here on how to fix that.
douger1957 said:
I would also format, not just wipe your data partition when you flash your first ROM as well.
---------- Post added at 03:26 PM ---------- Previous post was at 03:24 PM ----------
You're not the first here to have problems with sd cards in TWRP. There are several threads here on how to fix that.
Click to expand...
Click to collapse
Ah thanks.. will do a search
Am considering trying this, my thanks to doctor-cool for providing the instructions. I had kinda given up on being able to root my Note 4, and am attempting to get up-to-date with what's going on at this point.
Out of interest, are there any methods for doing this on a Verizon Note 4 that can be accomplished without the use of KingRoot or is that a must have? I'd really like to finally get this done, but have to admit to some reluctance over the unknowns that have been discussed on XDA when it comes to KingRoot. Honestly, I'm not even fully convinced that wiping your phone in advance of using KR will definitely resolve all potential problems that may exist. Would like to find a solution that just bypasses it altogether.
mray99 said:
Am considering trying this, my thanks to doctor-cool for providing the instructions. I had kinda given up on being able to root my Note 4, and am attempting to get up-to-date with what's going on at this point.
Out of interest, are there any methods for doing this on a Verizon Note 4 that can be accomplished without the use of KingRoot or is that a must have? I'd really like to finally get this done, but have to admit to some reluctance over the unknowns that have been discussed on XDA when it comes to KingRoot. Honestly, I'm not even fully convinced that wiping your phone in advance of using KR will definitely resolve all potential problems that may exist. Would like to find a solution that just bypasses it altogether.
Click to expand...
Click to collapse
Unfortunately, no.
My suggestion would be to disable wi-fi and remove your sim card until you can format your data partition.
douger1957 said:
Unfortunately, no.
My suggestion would be to disable wi-fi and remove your sim card until you can format your data partition.
Click to expand...
Click to collapse
Thanks for your response. I'd thought about that or similar solutions. The problem is there's so many question marks around KingRoot -- I figure if you're thinking it out, one of those questions has to be, what if anything does it leave on your phone even after you've finished the sort of process described here and removed KR? I'd feel so much more comfortable were it a solution that comes from one of the guys that have been around here for a long while. It seems the Note 4 agita never fully ends.
Hi All,
In the best interest to provide clarity I'm creating this quick and easy tutorial on how to root your Razer Phone 2 after the Pie Upgrade. Please send me any feedback to improve this post, we need to build up a strong community.
*As usual, I'm not responsible of any damage or brick to your phone, do it at your own risk.
Pre-Requirements:
-Be sure to have at least 70% of charges... or plug your phone to power
-Backup anything you consider important
-Already installed Pie Upgrade via OTA or Side Loaded
-Enable Developer Options
• Open Phone "Settings" and scroll down.
• You will see an option "Build Number".
• Simply tap on it 7 times to enable it on your Android Oreo based device.
• Your device immediately display a message on screen that will say "You are now a developer".
• The Developer Option is now available in the Settings>System>Developer Options. Enjoy!
- Install Android Drivers (https://developer.android.com/studio/run/win-usb) and ADB, I personally recommend -[TOOL]Minimal ADB and Fastboot [2-9-18] - https://forum.xda-developers.com/showthread.php?t=2317790
-Unlock Bootloader
• To enable OEM unlock, go to Settings > Developer options and check Enable OEM unlock
• Using ADB commands reboot on bootloader
adb reboot bootloader
• After reboot completes follow phone menus and select "UNLOCK BOOTLOADER"; accept all warnings, after restart you have completed the unlock.
Root and Installing Magisk
Since our phone doesn't have a proven customer recovery fully working (Ex TWRP) Magisk needs to be installed by manually patching the device boot image.
Making leverage of Warrior1988 post [Root Magisk Pie Update For Unlocked Devices] all credits to him. Download the image from his post
• Boot in fastboot mode To boot into fastboot, press and hold the Power button + Volume Down Keys for few seconds; Copy the image on the same folder as your ADB and Run the following commands:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot reboot
Install Magisk Download the apk and install it as usual on your RP2, that should be all.
DONE!!!! You now have a unleashed the beast! Please send me any recommendations to improved this guide.
chpimentelpr said:
Install Android Drivers and ADB
Click to expand...
Click to collapse
Your link has everything necessary for this step, right? Direct link to version 1.4.3 is here: https://androidfilehost.com/?fid=746010030569952951
Or are drivers and ADB two separate downloads?
chpimentelpr said:
• To enable OEM unlock, go to Settings > Developer options and check Enable OEM unlock
Click to expand...
Click to collapse
I assume this is where we plug our phone into our computer?
chpimentelpr said:
• Using ADB commands reboot on bootloader
Click to expand...
Click to collapse
For anyone dumb and new like me, I think this is with cmd.exe in Windows. Win+S -> type "cmd" (without quotation marks) and hit enter. Once open, you want to navigate to ADB, which you've already installed via the above instructions.
So your cmd will say:
C:\Users\YourName>
And you want to get to ADB, so you'll type "cd" (without quotation marks) which means you want to change directories, and then "cd adb" (if its in C:\ directory) or "cd [whatever the path is to the ADB folder]\adb"
Assuming it was directly in C:, you should see something like:
C:\adb>
Now you want to type "adb devices" to make sure it sees your phone is plugged in. You should see: "list of devices attached - [model] device" or something.
Now you're ready to go with the instructions starting at "adb reboot bootloader." If I'm wrong about this, someone less new and dumb than I am please correct me.
chpimentelpr said:
• Copy the image on the same folder as your ADB and Run the following commands:
fastboot flash*boot_a boot.img
fastboot flash boot_b boot.img
fastboot reboot
Click to expand...
Click to collapse
I'm confused on this one. The first one has "flash*boot_a," but the second one has "flash boot_b" without the * symbol. What does the * do, and what happens if we mess it up? Sorry if that's a dumb question.
AbsoluteContingency said:
Your link has everything necessary for this step, right? Direct link to version 1.4.3 is here: https://androidfilehost.com/?fid=746010030569952951
Or are drivers and ADB two separate downloads?
I assume this is where we plug our phone into our computer?
For anyone dumb and new like me, I think this is with cmd.exe in Windows. Win+S -> type "cmd" (without quotation marks) and hit enter. Once open, you want to navigate to ADB, which you've already installed via the above instructions.
So your cmd will say:
C:\Users\YourName>
And you want to get to ADB, so you'll type "cd" (without quotation marks) which means you want to change directories, and then "cd adb" (if its in C:\ directory) or "cd [whatever the path is to the ADB folder]\adb"
Assuming it was directly in C:, you should see something like:
C:\adb>
Now you want to type "adb devices" to make sure it sees your phone is plugged in. You should see: "list of devices attached - [model] device" or something.
Now you're ready to go with the instructions starting at "adb reboot bootloader." If I'm wrong about this, someone less new and dumb than I am please correct me.
I'm confused on this one. The first one has "flash*boot_a," but the second one has "flash boot_b" without the * symbol. What does the * do, and what happens if we mess it up? Sorry if that's a dumb question.
Click to expand...
Click to collapse
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot reboot
Warrior1988 said:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot reboot
Click to expand...
Click to collapse
No asterisk. Cool. Got it. Thank you, dude.
The drivers are the regular ones for android nothing specific, they can be downloaded from their SDK https://developer.android.com/studio/run/win-usb
App root detection?
If I root my Razer phone 2 using this guide, will certain apps like banking apps, and rideshare apps be able to detect root?
Bounty33 said:
If I root my Razer phone 2 using this guide, will certain apps like banking apps, and rideshare apps be able to detect root?
Click to expand...
Click to collapse
You can use magisk to hide the root from those apps. In general banking app are not affected by root. Google pay could be affected, but I don't use it so can't be sure. And you can always unroot.
AbsoluteContingency said:
No asterisk. Cool. Got it. Thank you, dude.
Click to expand...
Click to collapse
Did you rooted? Anything missing on the guide? I want make it as useful as possible so feedback is welcome.
chpimentelpr said:
Did you rooted? Anything missing on the guide? I want make it as useful as possible so feedback is welcome.
Click to expand...
Click to collapse
I have not, but I've been really sick and useless. I think I'll try tonight and let you know how it goes. Thanks for the guide, dude.
---------- Post added at 02:50 PM ---------- Previous post was at 02:45 PM ----------
Wait, yes, I do have a question. I download the drivers, and I download the Fastboot ADB thing. What do I do with the drivers? Do they just install in Windows like anything else, and that allows me to connect to the phone?
AbsoluteContingency said:
I have not, but I've been really sick and useless. I think I'll try tonight and let you know how it goes. Thanks for the guide, dude.
---------- Post added at 02:50 PM ---------- Previous post was at 02:45 PM ----------
Wait, yes, I do have a question. I download the drivers, and I download the Fastboot ADB thing. What do I do with the drivers? Do they just install in Windows like anything else, and that allows me to connect to the phone?
Click to expand...
Click to collapse
Yes, install them as any other driver.
After rooting can you relock the boot loader or will that brick the phone?
ndragon798 said:
After rooting can you relock the boot loader or will that brick the phone?
Click to expand...
Click to collapse
Not sure, but why you want to relock the boot.
chpimentelpr said:
Not sure, but why you want to relock the boot.
Click to expand...
Click to collapse
Mostly to get rid of the startup message
Very nice. I've rooted a ton of phones over the years, but they had more established communities and had well-explained (and tested) methods of rooting. The previous guide posted (that you referenced) was fine enough, but it was very much lacking a couple prerequisites that I was wondering/concerned about. This guide has cleared all of that up for me, and I now feel confident about rooting this phone.
Just as soon as I charge up the phone and install the OTA I've been avoiding until now... lol. Hoping somebody will make a Magisk module to move the clock back to where it belongs (if they haven't already).
EDIT: Just wanted to add my success story to this. Only thing I had to do that wasn't listed in the instructions (but makes sense) is that fastboot didn't work until I enabled USB Debugging (again, after the wipe and reboot), and I had to very manually tell the computer which driver to use (ADB) after that. Didn't have that issue for the bootloader instructions beforehand (that time, the driver worked automatically), so I figured I'd mention it.
chpimentelpr said:
Not sure, but why you want to relock the boot.
Click to expand...
Click to collapse
Also is there a way to turn back on the preboot authentication. Pretty much I just want to maintain full encryption and the built in security while having root.
ndragon798 said:
Also is there a way to turn back on the preboot authentication. Pretty much I just want to maintain full encryption and the built in security while having root.
Click to expand...
Click to collapse
I don't believe encryption is supported at the moment, and I don't encourage you to try it until TWRP is fully supported since you may end up in a boot loop. I'm eagerly waiting for the full encryption capability, so I will let you know as soon as something come up.
This has to be......one of the most usefull and noob friendly guides i have ever seen.....
You sir....are a God
Thank You.
ChronosTrigger said:
This has to be......one of the most usefull and noob friendly guides i have ever seen.....
You sir....are a God
Thank You.
Click to expand...
Click to collapse
i'm glad it helps.
Alright so after fighting with windows for a few hours, I discovered that my ADB was severely outdated.... Lesson learned there.
After getting the new boot image installed, though, I hit another problem... WiFi refuses to work. The toggle switch in the statusbar, nor the toggle in the system settings, will bring my wifi to life. Which is weird! Because I got through setup just fine, connected to wifi and signed into google... Yet now all wifi functionality has vanished. I tried a factory reset, to no avail. I'm gonna have to restore the factory boot image and start all over... But for now, figured I'd ask if anyone else has run into this weird bug?
***update***
I've now gone and flashed the global image for 8.1.0 to the phone... and it's telling me the OS is up to date???? How do I get back to pie?? It's late here and I've got wifi back now... but I'm stumped. Any help would be so greatly appreciated!
xttweaponttx said:
Alright so after fighting with windows for a few hours, I discovered that my ADB was severely outdated.... Lesson learned there.
After getting the new boot image installed, though, I hit another problem... WiFi refuses to work. The toggle switch in the statusbar, nor the toggle in the system settings, will bring my wifi to life. Which is weird! Because I got through setup just fine, connected to wifi and signed into google... Yet now all wifi functionality has vanished. I tried a factory reset, to no avail. I'm gonna have to restore the factory boot image and start all over... But for now, figured I'd ask if anyone else has run into this weird bug?
***update***
I've now gone and flashed the global image for 8.1.0 to the phone... and it's telling me the OS is up to date???? How do I get back to pie?? It's late here and I've got wifi back now... but I'm stumped. Any help would be so greatly appreciated!
Click to expand...
Click to collapse
I doubt the issue with the wifi is related with the image, since it doesn't have anything to do with it. If your phone doesn't detect the update you will need to sideload it. Then try the root guide again. Let us know how it goes, it the first time I hear something wrong with WIFI after rooting.