Instead of flooding the bootloader thread, I humbly ask for anyone's help in getting my N4 rooted so that I can unlock the bootloader.
1. I am able to use Kingroot to obtain temp root
2A. I open Root Checker and N4 reboots
OR
2B. Root checker OK then I get to ADB and enter a push command, the N4 reboots
This is where I am stuck.
Bootloader
I have my boot loader unlocked and twrp flashed successfully using king root. I used version 4.8.5 to do it. Basically it's kind of a hit or miss of how long the temp root stays until the phone either freezes or reboots (in my experience). I have attempted this process multiple times and it doesn't seem to hurt the device if the device freezes while I am executing adb commands.
The process that I did was hook up the Note 4 to my pc, then verify in adb that the phone was showing up. I then followed the adb command "adb push samsung_unlock_n4-2 /data/local/tmp/" as it doesn't require root to copy the file to the phone. Then I used king root to temp root the phone and followed the rest of the steps immediately. The boot loader is unlocked and I was able to flash twrp with Odin afterwards without having any issues. It seems time is the key because you don't know how long king root will let you keep the root.
Where I'm stuck is obtaining perm root after unlocking the boot loader and flashing twrp. I thought I would be able to just grab the latest version of SuperSU and flash through twrp but every time I tried this it caused a boot loop after the Verizon logo. (I went through a couple of flashing the stock 5.1.1 image from Samsung and retrying). Now I've made a backup in twrp so if anything goes wrong I can return to the unlocked/custom recovery state that I have gotten it to. I just am not sure how to obtain the perm root after the unlock and custom recovery.
On the topic of king root again, there were a couple of instances where it froze either before trying the adb commands or during (even failing to root sometimes). I just restarted the phone, or pulled the battery when that happened and tried the process again. It always worked eventually.
coledeb said:
I have my boot loader unlocked and twrp flashed successfully using king root. I used version 4.8.5 to do it. Basically it's kind of a hit or miss of how long the temp root stays until the phone either freezes or reboots (in my experience). I have attempted this process multiple times and it doesn't seem to hurt the device if the device freezes while I am executing adb commands.
The process that I did was hook up the Note 4 to my pc, then verify in adb that the phone was showing up. I then followed the adb command "adb push samsung_unlock_n4-2 /data/local/tmp/" as it doesn't require root to copy the file to the phone. Then I used king root to temp root the phone and followed the rest of the steps immediately. The boot loader is unlocked and I was able to flash twrp with Odin afterwards without having any issues. It seems time is the key because you don't know how long king root will let you keep the root.
Where I'm stuck is obtaining perm root after unlocking the boot loader and flashing twrp. I thought I would be able to just grab the latest version of SuperSU and flash through twrp but every time I tried this it caused a boot loop after the Verizon logo. (I went through a couple of flashing the stock 5.1.1 image from Samsung and retrying). Now I've made a backup in twrp so if anything goes wrong I can return to the unlocked/custom recovery state that I have gotten it to. I just am not sure how to obtain the perm root after the unlock and custom recovery.
On the topic of king root again, there were a couple of instances where it froze either before trying the adb commands or during (even failing to root sometimes). I just restarted the phone, or pulled the battery when that happened and tried the process again. It always worked eventually.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=66371097&postcount=237
I had the same bootloop problem and following those directions fixed it for me. I had to use Emotion-TW-5.1.1-nightly-r21-RC1-SM-N910P.zip as my kernel. Later versions didn't work (wrong phone version?).
coledeb said:
I have my boot loader unlocked and twrp flashed successfully using king root. I used version 4.8.5 to do it. Basically it's kind of a hit or miss of how long the temp root stays until the phone either freezes or reboots (in my experience). I have attempted this process multiple times and it doesn't seem to hurt the device if the device freezes while I am executing adb commands.
The process that I did was hook up the Note 4 to my pc, then verify in adb that the phone was showing up. I then followed the adb command "adb push samsung_unlock_n4-2 /data/local/tmp/" as it doesn't require root to copy the file to the phone. Then I used king root to temp root the phone and followed the rest of the steps immediately. The boot loader is unlocked and I was able to flash twrp with Odin afterwards without having any issues. It seems time is the key because you don't know how long king root will let you keep the root.
Where I'm stuck is obtaining perm root after unlocking the boot loader and flashing twrp. I thought I would be able to just grab the latest version of SuperSU and flash through twrp but every time I tried this it caused a boot loop after the Verizon logo. (I went through a couple of flashing the stock 5.1.1 image from Samsung and retrying). Now I've made a backup in twrp so if anything goes wrong I can return to the unlocked/custom recovery state that I have gotten it to. I just am not sure how to obtain the perm root after the unlock and custom recovery.
On the topic of king root again, there were a couple of instances where it froze either before trying the adb commands or during (even failing to root sometimes). I just restarted the phone, or pulled the battery when that happened and tried the process again. It always worked eventually.
Click to expand...
Click to collapse
Why don't you guys flash a ROM that is rooted instead of flashing SU?
Edit:
But if whatever you guys are doing works eventually, keep doing that.
thanks for everyone's help - I finally got DEV mode to stick!
Related
I'm having serious problems trying to root this phone. To start I wanted to use the rage method but I couldn't get HTC sync to work with my phone and windows 7 and adb to work. So I then used black prince method off of you tube using visionary r14. I did everything he said. When I press volume down and power I see it says s-off but when I type SU into the terminal it says permissions denied. I even see the superuser app on my phone. I then did some searching and people who have the same problem and they said to do temp root then go to the terminal and type /data/local/tmp/root then sync it again. Still no luck. Any ideas?
My next concern is I have been trying to boot into clockwork recovery with no luck. I have re flashed and flashed the current version's of recovery to many times to remember and did fix permissions. I can not boot into recovery. Any ideas?
What version of ROM is it that you are trying to root ? The latest 1.72 Desire Z ROM cannot currently be rooted.
You need S-OFF to flash a custom recovery. Are you saying you are trying to boot into stock recovery ? If so, when you see the screen with the red triangle/exclamation mark, hold Volume Up and press Power, and it should go into stock recovery.
Your phone isn't fully s off. You need to delete visonary completely off your phone. (Probably have to wipe). Then download pdanet app. And when you plug usb in your computer that should fix the driver problem. Then run rage. Don't do the lock in root command, then follow gfree tutorial, then try lock in root command. If it gives you an error, let me know which error and we can work around it. Pm me when you run into trouble.
Fired from my 7.62mm bullet hose to your face using plunging fire.
long story short i have a Sprint galaxy s3 that is locked w a pattern lock and im unable to get in. i did ALOT of research and came across a few options but none work. one method says i should use adb to remove the lock ( http://forum.xda-developers.com/showthread.php?t=1800799) got stuck cause its not rooted and no custom recovery. i tried to flash CWM and root using this method (http://galaxys3root.com/galaxy-s3-r...gh-t999sgh-i747sph-l710-fail-proofnoob-proof/) odin said pass but i wasnt able to get into any custom recovery it would just hang when using the vol+ home power combination. stock recovery still works the same.
All i want to do is unlock this phone that has a pattern lock.Google account not an option.the owner passed away and im trying to unlock for her family to get contacts and internal photos etc. im not sure if usb debug is on however adb recognized the device so i assumed it was. the reason i guess im having a hard time is because not alot of information is available given the circumstances. Ive been reading for 7+ hours now afraid to ask for help as ppl always get flamed if there is already a solution somewhere. if there is i havent found it. Thanks for any help
Follow this to get custom recovery: http://forum.xda-developers.com/showthread.php?t=2011491
Then mount /data and delete /data/system/gesture.key from recovery
tried.that didnt work because i didn't have su in adb. i was finally able to root using cf auto root method and then install LATEST CWM and followed this guide to reset lock screen. success. http://forum.xda-developers.com/showthread.php?t=2437946
alfizzle said:
tried.that didnt work because i didn't have su in adb. i was finally able to root using cf auto root method and then install LATEST CWM and followed this guide to reset lock screen. success. http://forum.xda-developers.com/showthread.php?t=2437946
Click to expand...
Click to collapse
It probably does the same thing I just said, delete the data/system/gesture.key file
I have a Verizon LG G3 and wanted to root to change the ROM. I used kingroot to root and then was able to add superuser, root checkers showed I had root and superuser access. I read online a few people were able to use flashify to put Twrp on their device. I selected the VS985 and after it was done it would not boot into recovery. The phone loads and runs fine but now ot shows the phone does not have root, superuser says it needs update and fails, and I cannot even do a factory reset.
How do I fix the recovery so I can either finish the root and recovery installation, or just go back to stock?
Thanks!
Phone is on Marshmallow. Guides I found to fix say you need to be on lollipop. Phone boots right now, so I do not want to risk trying too much since it boots now.
Fixed it using lg flashtool but with this dll file http://forum.xda-developers.com/show...4&postcount=84
Hi there,
Proud owner of a new Pixel XL. Unlocked version. Tried rooting last night (i've rooted all devices i've owned and am not new to this). Followed the instructions to a "t". The device won't get past the white screen and dots leapfrogging each other. Now when going back to fastboot, device isn't recognised by ADB Fastboot etc...
Please help!!!!
My guide should be able to help you get back to the OS and then install root.
Keep in mind you may lose data if you don't remove the -w from the script mentioned in the guide.
http://forum.xda-developers.com/pixel-xl/how-to/info-how-restored-to-stock-soft-t3494478
Did you unlock bootloader?
Then immediately try rooting?
That is one cause for bouncing dots.
You should: flash factory image, then boot into device before any flashing. Setup device until you are at the home screen and OS settled. Use a pattern or pin security. That is needed to make recovery work properly. You need to decrypt at recovery boot. No ask for pin? Then power off and boot TWRP again.
Follow directions in TWRP and SuperSU threads to a Capital "T"...
Versions:
Latest "Q" firmware
Boot TWRP RC1 img, then flash zip installer
Use SuperSU 2.79 SR1.
You'll have no bootloop. I found first rooted boot to take just a few minutes.
Just in case: update SDK platform tools if you haven't cos that screws people up for days too.
Thanks mate. But i get to step 9 and nothing happens. My device is no longer recognised
thanks mate, but the problem is that now the device is simply not recognised by my computer. I can't flash anything
I should clarify.
SDK is 100% up to date.
I am trying on both Windows 10 and Mac.
Device drivers worked fine prior to trying to root.
I'm really worried that i might have just bricked a $1.4k(aud) device
I unlocked my bootloader and got a bootloop when I tried to fastboot to root. Would not recognize the device either. I redownloaded SU 3 as suggested in the third post and it worked. Good Luck.
I used the fastboot to root method and did not install TWRP.
http://forum.xda-developers.com/pixel-xl/help/bootloop-t3498140
Thanks, Mike01680. trying now
When i go into sideload i can see the device listed on adb devices!
Okay. Booted into recovery, found my firmware for NMF26O. Downloaded and ADB Sideloaded it can once again boot. thanks for all of your help!!!
Hello
I tried rooting my LG H815 and it didn't go so well.
I managed to successfully unlock the bootloader following the steps on the LG developer website.
I downloaded SuperSu (UPDATE-SuperSU-v2.46.zip) and placed it in the internal storage of the phone.
Afterwards in order to root the device, I booted into TWRP with "fastboot boot twrp-3.0.2-1-h815.img".
In TWRP I flashed SuperSu. After it finished flashing I rebooted the device. After it attempted to start up again, it froze at the LG logo. I waited around 10 minutes and figured it's not successfully boot.
I removed the battery and tried to fire it up again, but it didn't get past the Logo screen again.
I managed to send "adb reboot recovery" to it, but all I get is an image of a little dead android. I guess this is because I only booted TWRP and did not flash it.
When I get it in fastboot mode, "fastboot boot twrp-3.0.2-1-h815.img" does work anymore now. I just says < waiting for any device >.
I managed to get into default recovery with power up + vol down where it prompted me to do a reset by responding Yes twice, but after it rebooted, it still got stuck on Lg logo.
If you cannot get to the recovery then follow these steps:
i) Make sure you have the LG Drivers installed from here: http://oceanhost.eu/e4h2px4e0hkd/LGMobileDriver_WHQL_Ver_4.0.4.exe.htm
ii) Download the LG Bridge software from here: http://www.lg.com/us/support/product-help/CT10000025-1438110404543-preinstall-apps
iii) Remove the battery and reinsert it so the device it is fully off.
iv) While holding the up volume button, insert your USB cable.
v) You should enter download mode. Go to the Software Update tab of the LG Bridge. It will say connecting and then should say your device is up to date. Click on the recovery text on the bottom right and then follow the instructions. The software will download the system image for you and this is roughly 1.6GB so make sure your firewall doesn't block this connection.
This shouldn't delete your data (no guarantees) but you will have to grant app permissions again and reapply any changes to system files e.g. root, viper4android, xposed ect.
If you have problems try this method instead:
http://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848
If successful and you're brave enough to try again. Then make sure you actually flash TWRP. I think you are right in that you only booted TWRP .
You can follow my TWRP/root guide here: https://forum.xda-developers.com/g4/general/howto-complete-guide-to-unlock-twrp-t3370003
Good luck
Thanks a lot for answering.
LG Bridge wasn't detecting my device. I don't remember if I was in download mode when I tried this, though. I might've not been.
I didn't know how to fix it and asked a friend for help. He managed to flash the h815 stock firmware through some Taiwanese/Korean flash tool (Edit: It was LGUP and he flash a kdz file with the stock firmware).
I followed a similar guide to yours when I flashed SuperSU from TWRP, except I didn't install twrp permanently after booting it from the .img file. I thought it was not possible to install twrp if the device is not rooted first.
I still kinda want to root the device since I voided my warranty by unlocking the bootloader, but I'm afraid I'll break it again if I use the same method.
Edit: Managed to successfully flash twrp. Booted into recovery again after rebooting system. I am now creating and saving a full backup with TWRP. Will try flashing SU again afterwards.
Edit2: I flashed SU after properly installing TWRP and it worked like a charm.