Related
Hey guys, having some trouble rooting this SPRINT FLEX....
My build is the ZVA Build... KOT49I.LS995ZVA - It's on the Stock 4.4.2 Android, kernel is 3.4.0
I cannot find any information anywhere on this. Tried using iORoot and LG_ROOT to manually root, via ABD ... My device connects to ADB and everything but when i try to Push any root files via iOROOT Installation aborts ...
SOLUTION
http://androidxda.com/download-kingroot-application
You dont need kingoroot.
If you have never been rooted before just ut towelroot and bruteforce the root. Reboot and you're done. Install supersu from playsotre enjoy!
I am looking for an easy way to be able to receive OTA updates after rooting with the 'systemless' root method, the steps I mention below assume that the system partition remains untouched after rooting. I have searched and not found a clear answer on this.
Would I be correct in assuming that this procedure should work to receive an OTA update and keep stock recovery after rooting?
Start with completely stock Android 6.0
fastboot boot twrp-recovery.img (boot TWRP, NOT flash, to maintain stock recovery after rooting)
Flash systemless root with TWRP
OTA arrives (Android 6.0.1 for example)
fastboot flash boot boot.img (with stock 6.0 kernel, root lost)
Accept & install OTA update
Success?
So unless I am missing something, this method would leave the system in a stock, unrooted state after the OTA is installed, and could be repeated for future updates. Anybody have any experience with this yet?
Sounds like it will work, but why mess with the ota? More work and risk honestly.
Since you're already using fastboot just flash the newest boot and system.img. Then flash/boot twrp and flash su like you'd need to do anyway. Done. You don't lose anything flashing system.
yosmokinman said:
Sounds like it will work, but why mess with the ota? More work and risk honestly.
Since you're already using fastboot just flash the newest boot and system.img. Then flash/boot twrp and flash su like you'd need to do anyway. Done. You don't lose anything flashing system.
Click to expand...
Click to collapse
That is true, kind of just wondering/gathering information. It just seemed like with the new root method, OTA would be possible and less risky than before.
Sent from my MotoG3 using Tapatalk
@quakeaz there is one step missing on your guide. After boot.img you also have to flash stock recovery.img. From Lollipop, Google is also checking installed recovery, and for successful OTA, it has to be stock as well.
Otherwise, your guide should work, I've done same thing with my Nexus 5 and 7 for like last 3 months.
Srandista said:
@quakeaz there is one step missing on your guide. After boot.img you also have to flash stock recovery.img. From Lollipop, Google is also checking installed recovery, and for successful OTA, it has to be stock as well.
Otherwise, your guide should work, I've done same thing with my Nexus 5 and 7 for like last 3 months.
Click to expand...
Click to collapse
Thanks for your reply, but I intentionally left that step out, due to step 2 in my list. By only booting TWRP, instead of flashing, I assume stock recovery will remain after rooting.
Sent from my MotoG3 using Tapatalk
quakeaz said:
Thanks for your reply, but I intentionally left that step out, due to step 2 in my list. By only booting TWRP, instead of flashing, I assume stock recovery will remain after rooting.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Ah, sorry, I overlooked that.
Since I have flashed TWRP instead of stock recovery, I'm going by same process as you write, just reflash stock recovery. And can confirm, that the process is indeed working (no need to install system.img, as with previous system-based SuperSU).
Sounds good!
Sent from my MotoG3 using Tapatalk
quakeaz said:
I am looking for an easy way to be able to receive OTA updates after rooting with the 'systemless' root method, the steps I mention below assume that the system partition remains untouched after rooting. I have searched and not found a clear answer on this.
Would I be correct in assuming that this procedure should work to receive an OTA update and keep stock recovery after rooting?
Start with completely stock Android 6.0
fastboot boot twrp-recovery.img (boot TWRP, NOT flash, to maintain stock recovery after rooting)
Flash systemless root with TWRP
OTA arrives (Android 6.0.1 for example)
fastboot flash boot boot.img (with stock 6.0 kernel, root lost)
Accept & install OTA update
Success?
So unless I am missing something, this method would leave the system in a stock, unrooted state after the OTA is installed, and could be repeated for future updates. Anybody have any experience with this yet?
Click to expand...
Click to collapse
Instead of fastboot flashing boot.img, you can use "Settings --> Full Unroot" in SuperSU. During SuperSU systemless flash, your old boot image is backed up. Among other things, the full unroot option will restore the backup, assuming it hasn't been lost due to a factory reset and whatnot.
On many firmwares, this procedure also restores stock recovery. This requires that both the firmware supports recreating the recovery from the boot image plus a patch file (most do), and that TWRP did not remove said patch file (which some versions do).
That being said, if you're using fastboot anyway, flashing boot, recovery, system and vendor manually is always the safest thing before an OTA.
Thanks for the info. So I take it while using systemless root, installing ota without unrooting is a big nono? The January ota just downloaded and is asking me to install, should I do it manually?
Chainfire said:
Instead of fastboot flashing boot.img, you can use "Settings --> Full Unroot" in SuperSU. During SuperSU systemless flash, your old boot image is backed up. Among other things, the full unroot option will restore the backup, assuming it hasn't been lost due to a factory reset and whatnot.
On many firmwares, this procedure also restores stock recovery. This requires that both the firmware supports recreating the recovery from the boot image plus a patch file (most do), and that TWRP did not remove said patch file (which some versions do).
That being said, if you're using fastboot anyway, flashing boot, recovery, system and vendor manually is always the safest thing before an OTA.
Click to expand...
Click to collapse
Thank you for this thread and the procedure. I tried myself to avoid as much as possible to use a computer for super easy OTA update. But there is always one obligatory step: to root the phone.
Phone systemless rooted (2.66) - TWRP installed - OTA arrives.
In SuperSu app : Fully unroot
Install OTA - success
Fastboot boot (or install) TWRP
Flash superSu 2.66.zip
And that's it!
My question is the following: Does it exist a possibility to load on step 3. something that could flash superSu.zip from within the phone, no computer required?
Maybe FlashFire? I guess not, for it needs root and the point is to flash a rooting zip... You see the loop there...
Would it be theoreticaly possible at all?
Judim said:
Maybe FlashFire? I guess not, for it needs root and the point is to flash a rooting zip... You see the loop there...
Would it be theoreticaly possible at all?
Click to expand...
Click to collapse
Yes, this is one of the use-cases of FlashFire. I just haven't finished updating it to 6.0 yet.
Oh nice!
I didn't know it cause I never had the chance to try out FlashFire.
Thanks so much for everything you do for the Android community!
Cheers!
Srandista said:
Ah, sorry, I overlooked that.
Since I have flashed TWRP instead of stock recovery, I'm going by same process as you write, just reflash stock recovery. And can confirm, that the process is indeed working (no need to install system.img, as with previous system-based SuperSU).
Click to expand...
Click to collapse
mine fail here. i previously got systemless root 2.62, blu spark kernel and twrp. fastboot flash stock boot and recovery. reboot to update and it fail. any idea why?
ShanxRoux said:
mine fail here. i previously got systemless root 2.62, blu spark kernel and twrp. fastboot flash stock boot and recovery. reboot to update and it fail. any idea why?
Click to expand...
Click to collapse
Did you modify system?
Try flashing system, boot, and recovery.
Then try again.
Hi, I have a Oneplus One and today has been released an OTA, so I tried the method. I have COS13 JK (latest full rom) firmware, with systemless 2.84beta supersu and twrp.
The only apps that have root access are AdAway and Greenify (without mods to system apps). No Busybox installed.
I reverted via fastboot to original JK boot.img and recovery.img, and restored, via Adaway, the original hosts file, then I applied the OTA via stock Cyano Recovery, but update failed ("system partition has unexpected contents" error).
Why?
Thanks.
you have to unroot first from the app.Revert to original boot. and then flash
Sent from my ASUS_Z00LD using Tapatalk
caldent said:
you have to unroot first from the app.Revert to original boot. and then flash
Sent from my ASUS_Z00LD using Tapatalk
Click to expand...
Click to collapse
I tried: no way to install OTA, I had to wait for the full rom, and dirty flashed it via TWRP without a problem.
Then I rerooted.
Bye!
ok i seem to be getting the run around on where i need to be to ask my question(s)
i am very interested in systemless root....
that being said i am clueless and all info i am findingis just super confusing me.
if someone could humor a noob to systemless rooting that would be greatly appreciated!!
i recently bought 2 new phone for my household, both are the lg tribute hd (also called lg x style)
one click root and pc method of kingoroot etc dont work... i cant locate a twrp or a cwm for this model easily by searching so i am assuming there isnt one (maybe someone could located or help to build one?)- or maybe im not tech smart enough and i can use any?(i dont think so)
model is lg ls675,android 6.0.1, kernel version 3.10.49, build # MXB48T, software is ls676zv3
main reason at the moment for trying to get root is to remove bloatware and to be able to wifi tether without limitations buy the provider, on ther phone that i have obtained root on i used an app called WIFI Tether Router which works beautifully but requires root...
please help as this is how we use our computer with internet and its beneficial all the way around especially to get rid of bloatware and keep device running smoothly...
thanks again for any help. greatly appreciated.
if im not in the right thread please kindly direct me to the correct one. thanks
Hey XDA,
I'm currently rooted on T-Mobile's H811 version 20i. I just got the stupid update notification and I'd like to get rid of it (by updating to the latest version, and root the phone + install a custom ROM).
I can backup most of my data through Google and all my pictures are on my SD card, so I dont have to worry about losing data through the upgrade.
What steps do I need to take to:
• Update my G4 to the latest version + root
• (dont delete my photos from my SD card)
I'm afraid I'll brick my G4, since I almost brick it the last time I rooted my G4.
Thank you!
You still get over the air update even if your rooted. If you custom recovery it, you will no longer get over the air update from tmobile. Its a good thing i flash my stuff using twrp manager.
SilentBangHD said:
You still get over the air update even if your rooted. If you custom recovery it, you will no longer get over the air update from tmobile. Its a good thing i flash my stuff using twrp manager.
Click to expand...
Click to collapse
Do I keep my root and everything? Or does the root break (like on iOS devices)
NoWayIn said:
Do I keep my root and everything? Or does the root break (like on iOS devices)
Click to expand...
Click to collapse
Once rooted you will always be rooted unless you delete the root files. For every new version of android comes out, there need to be new method to root your phone. But since you've rooted, you will keep the root even if you updated to new android version. Even factory reset cant get rid of root. you cant get rid of it updating to new version of android. (correct me if im wrong)
Well, I clicked the install button and my phone went into two recovery but it failed to install the update. However , the notification is gone now so I guess that's ok
NoWayIn said:
Well, I clicked the install button and my phone went into two recovery but it failed to install the update. However , the notification is gone now so I guess that's ok
Click to expand...
Click to collapse
Lucky you ( Else you would have been stuck on TWRP Screen) till you flash the G4, best way to update when you are rooted and custom recovery installed is to use LGUP. Download latest KDZ file of 20o and flash it via KDZ you will loose recovery only but all your stuff and Root remains.
SignatureBoy said:
Lucky you ( Else you would have been stuck on TWRP Screen) till you flash the G4, best way to update when you are rooted and custom recovery installed is to use LGUP. Download latest KDZ file of 20o and flash it via KDZ you will loose recovery only but all your stuff and Root remains.
Click to expand...
Click to collapse
OMG that would suck, because I am leaving to go to the airport tomorrow so I NEED my phone.
I'm going to update tomorrow in the morning before I go, in case there was some problem.
Thanks man.
Mine is rooted and unlocked on 20i. I flashed TWRP 2.8.7.2. I did remove a couple OEM apps that were a bit annoying. I back-up the 3 suggested partitions, system, boot, data.
Can I update to the OTA using just TWRP or adb/fastboot without screwing the pouch?
Or do I need to take a different route to the OTA?
NoWayIn said:
Well, I clicked the install button and my phone went into two recovery but it failed to install the update. However , the notification is gone now so I guess that's ok
Click to expand...
Click to collapse
once you take 20o you stuck there so you cant downgrade or youll brick phone..
---------- Post added at 07:00 PM ---------- Previous post was at 06:58 PM ----------
metropical said:
Mine is rooted and unlocked on 20i. I flashed TWRP 2.8.7.2. I did remove a couple OEM apps that were a bit annoying. I back-up the 3 suggested partitions, system, boot, data.
Can I update to the OTA using just TWRP or adb/fastboot without screwing the pouch?
Or do I need to take a different route to the OTA?
Click to expand...
Click to collapse
if you do youll get camear and sound problems... the best way its to start fresh..
download LGUP and h811 20o KDZ. the flash using refurbished this will wipe everything.. then install twrp and root..
I really find LG way more annoying than HTC ever was. This should be a simple process.
Finally got LGUP working on Virtual Box 5.026 running W7, from Mavericks OSX. But it took some doing to get the 20o update in.
Had to add Guest additions to VB in order to enable USB 2 control, so VB would see the LG.
And the proper LG Mobile drivers v4.04.exe.
A restart or 2 of the Mac.
Then ran LGUP, changed the browse extension to .kdz and navigated to the H81120o_00_0613.kdz.
LGUP ran and the G4 restarted a few times over about 5 mins or so.
Can't get twrp flashed.
I get this error: FAILED (remote: unknown command).
So I disregarded and tried fastboot boot twrp-2.img.
File not found.
Ideas?
this from Macs Terminal app or I suppose the equal in Doze 7.
Terminal:
adb reboot bootloader
fastboot boot (drag and drop the twrpxxx.img into the Terminal window)
This will boot you into a "temp" TWRP recovery. Install twrp.img (select .img button bottom right)
Then install SuperSu 2.6.7.zip.
REBOOT SYSTEM
I know its a bit of an old build... but i'm trying to root my SM-G920V using PingPong Root
Every time I go through this process:
1. Install pingpongroot_beta6.apk
2. Open Ping Pong Root
3. Install SuperSU
4. Open Super SU
5. Get an error message: "There is no SU binary installed, and SuperSU cannot..."
6. Push Ok.
7. Goes back to PingPong Roof: Push "Get Root!"
8. Get Error: "Root failed. Did you install SuperSU before running the root?"
9. try "Download Data"
10. Still Get Error: "Root failed. Did you install SuperSU before running the root?"
I've read a few forums on this issue and i could never find a fix.
Anyone have any help with this please.
I'm trying to root my 920v also. I'm on 6.0.1. I've tried king root and kingo. Any info would be appreciated.
deepunderground said:
I know its a bit of an old build... but i'm trying to root my SM-G920V using PingPong Root
Every time I go through this process:
1. Install pingpongroot_beta6.apk
2. Open Ping Pong Root
3. Install SuperSU
4. Open Super SU
5. Get an error message: "There is no SU binary installed, and SuperSU cannot..."
6. Push Ok.
7. Goes back to PingPong Roof: Push "Get Root!"
8. Get Error: "Root failed. Did you install SuperSU before running the root?"
9. try "Download Data"
10. Still Get Error: "Root failed. Did you install SuperSU before running the root?"
I've read a few forums on this issue and i could never find a fix.
Anyone have any help with this please.
Click to expand...
Click to collapse
What firmware are you using.
Need help rooting Verizon s6 6 0.1!!!!! Is it possible if not who wants to buy it?
In using version 6.0.1
In using version 6.0.1
Pretty sure ping-pong root won't work with 6.0.1 just 5.0.2 I think.
Is there a autoroot .tar file for odin
I just got a sm-s906l from straight talk and got it rooted with kingroot. Now I'm trying to figure out how to flash custom roms.
---------- Post added at 04:55 AM ---------- Previous post was at 04:53 AM ----------
From the research I have done it couldn't seem to find anyone who has succeeded in rooting the 920v. So I just traded for a different model.
I using G920V Nougat DQE1 lastest fm. How can i root it & flash twrp ?
This Process Will Root Phone Unlock Your VZW EMMC 15 Chipset Bootloader Install TWRP Recovery And Install PreRooted Firmware Of Your Choice!.
I posted this because the current unlock methods are not easy to do. This should make process easier
If you already have unlocked bootloader and want to change bootloader versions then goto post 2
Downloads
EMMC_15_VZW_NOTE4_BOOTLOADER_UNLOCK_2021.7z
Instructions
1, You need working adb on your computer. The latest samsung drivers installed. A Sdcard inserted in the phone preferably a 32 gig or less. Must be at least 1 gig. Phone will be wiped! A data connection or wifi is also required.
2. Download and extract the EMMC_15_VZW_NOTE4_BOOTLOADER_UNLOCK.7z
3. Reboot phone to download mode (pwr+voldwn+home_button). In Odin_Files folder use odin and flash the COMBINATION_VZW_FA44_N910VVRU2APB1.tar.md5 in BL slot in odin
4. Once phone is booted up and connected to computer run 1Install_KingRoot.cmd. This will install kingo root and kingroot app on phone.
5. Once installed make sure phone has data via cell or wifi. Run kingo root to root phone. Phone may kernel panic and reboot just keep trying. Once root is successful move to step 6 if unsuccessful try kingroot if thats succesful click on root permissions in the kingo root app and click on system adb and change prompt to allow. This is not necessary if rooted with kingo app
6. Make sure phone is connected to computer and run1Replace_With_SuperSu.cmd then once this process finishes run 2UnlockBootloader.cmd. This will change CID to Dev edition and then unlock that bootloader. If first time unlocking phone it will change your cid to dev edition then reboot during process. This is fine you will not loose root. Close cmd window wait for phone to reconnect then run again this time it will unlock the bootloaders when done phone will once again power off. Remove sdcard this is very important so I will say again remove SDCard from Phone your phone will not boot with sdcard in until it is reformated! Reboot to download mode you should notice it says DEV Mode.
7. Reboot phone and now you are ready to choose your bootloader you want to be on for this guide we will assume you want to be on latest QL1 Marshmallow bootloader.
8. Make sure phone is connected and run 3UnlockBootloader_MM_QL1.cmd or what ever one you choose. When done Phone will power off and now the bootloader is updated.
9. Now choose the firmware that matches your unlocked bootloader from below
N910VVRU1ANJ5_DEV_ROOTED.tar.rar Kit Kat 4.4 Rooted Firmware
N910VVRU2BOG5_DEV_ROOTED_SUPERSU.tar.rar Lollipop 5.0 Rooted Firmware
N910VVRU2BPA1_DEV_ROOTED_MAGISK.tar.rar Lollipop 5.1 Rooted Firmware
N910VVRU2CQL1_DEV_ROOTED_MAGISK.tar.rar Marshmallow 6.0 Rooted Firmware
VZW_N910VVRU2CTI1_ROOTED_FORCE_WIPE.tar.7z Marshmallow 6.0 EFTSU Rooted Latest Firmware!!
10 Reboot phone to download mode and flash above firmware that matches your bootloader version Im using N910VVRU2CQL1_DEV_ROOTED_MAGISK.tar.rar as example. Extract N910VVRU2CQL1_DEV_ROOTED_MAGISK.tar.rar and use provide odin from EMMC_15_VZW_NOTE4_BOOTLOADER_UNLOCK and choose N910VVRU2CQL1_DEV_ROOTED_MAGISK.tar.md5 or the one you choose and in odin BL slot uncheck auto reboot and flash. When flash is done make sure to reboot to TWRP recovery which will be installed and wipe data then reboot. You are done!
11. Above firmware running magisk root may til you additional steps are needed and download magisk zip. You can skip this step if you want as it is rooted and magisk apk is installed but if you want I will provide magisk zip used in root if you want to reflash
Upgrade Bootloaders For EMMC 15 VZW DEV Unlocked Phones
This process requires flashing back all stock firmware in order to upgrade/downgrade bootloaders. So I have made a special rom just for doing this which should make process easy. Its all done with odin and flashire.
Downloads
EMMC_15_VZW_NOTE4_BOOTLOADER_UPGRADE_ZIPS_2021.7z
N910VVRU1ANJ5_DEV_ROOTED.tar.rar Kit Kat 4.4 Rooted Firmware
N910VVRU2BOG5_DEV_ROOTED_SUPERSU.tar.rar Lollipop 5.0 Rooted Firmware
N910VVRU2BPA1_DEV_ROOTED_MAGISK.tar.rar Lollipop 5.1 Rooted Firmware
N910VVRU2CQL1_DEV_ROOTED_MAGISK.tar.rar Marshmallow 6.0 Rooted Firmware
VZW_N910VVRU2CTI1_ROOTED_FORCE_WIPE.tar.7z Marshmallow 6.0 EFTSU Rooted Latest Firmware!!
Instructions
You must be on EMMC 15 unlocked bootloader if not goto post 1 to unlock bootloader
1. Download the EMMC_15_VZW_NOTE4_BOOTLOADER_UPGRADE_ZIPS.7z and extract this will contain the zips and special firmware for upgrading bootloader. Download above firmware you want to upgrade/downgrade too.
2. You will probably need to wipe data so reboot to TWRP recovery wipe data then reboot to download mode use provide odin in the Odin_Files folder and choose FIRMWARE_FOR_UPGRADE_DOWGRADE_BOOTLOADERS.tar.md5 and flash in BL slot.
3. This will reflash stock firmware and a prerooted special rom with a flashfire preinstalled and minimal files just to boot rom. Your bootloader will be locked for the time being as this is necessary to upgrade bootloaders.
4. When rom is booted choose the zip that matches the firmware you want to install from the FlashFire_Zips folder and place on phone storage.
5. Open flashfire grant root access choose add zip choose the zip you placed on phone click on reboot tab in flashfire and choose reboot to bootloader in will say dev mode this means your unlocked again
6, Now choose above firmware you downloaded extract the tar.md5 file from the rar file and flash in BL slot in odin Uncheck auto reboot when don flashing force reboot to TWRP recovery and wipe data again then reboot phone. You are now Upgraded or downgraded which ever you choose to do.
Mine
This has been needed in our forum for a long time. Fantastic work, thanks!
jrkruse said:
Mine
Click to expand...
Click to collapse
Hello
I want ask u do you know how to open bootloder for huawei mate 20 pro lya.l09
Thx
theohtc said:
Hello
I want ask u do you know how to open bootloder for huawei mate 20 pro lya.l09
Thx
Click to expand...
Click to collapse
Maybe ask in the huawei thread.
Sent from some device I modified
How many times does it usually take for kingroot?
UPDATE: Tried many times and eventually it said "Root Failed" "no strategy now"
DeeXii said:
How many times does it usually take for kingroot?
UPDATE: Tried many times and eventually it said "Root Failed" "no strategy now"
Click to expand...
Click to collapse
I would start over completely. Reflash the Odin files then make sure you have internet access i would use wifi when running kingroot app
Sent from some device I modified
jrkruse said:
I would start over completely. Reflash the Odin files then make sure you have internet access i would use wifi when running kingroot app
Sent from some device I modified
Click to expand...
Click to collapse
Ok I will reflash...
Yes I had internet access, Kingroot does not even function without it.
Thanks for the fast reply!
---------- Post added at 06:15 PM ---------- Previous post was at 05:54 PM ----------
Can't seem to get passed 35%
---------- Post added at 06:41 PM ---------- Previous post was at 06:15 PM ----------
UPDATE:
I used Kingroot desktop version and it rooted the first try.
On to the next step.
---------- Post added at 07:20 PM ---------- Previous post was at 06:41 PM ----------
How long does N910VVRU2CQL1_DEV_ROOTED_MAGISK.tar.md5 take to flash?
It has not errored out at all but it seems to be taking longer than I have ever seen.
It's on tz.mbn.
@jrkruse THANK YOU for putting this into such a simplified method that doesn't require large downloads, multiple command lines, or having to downgrade and re-upgrade just to be able to achieve an initial root, unlock, and TWRP!!! I read through way too many methods that were a MILE long before I happened across this one. The ONLY issue i ran into during this process (should help others), was that I had to insert a newer version (and rename it to match the script) of the KingRoot APK to be able to achieve root on my existing CQL1 firmware. I tried the provided APK many times without success, but a newer version was able to achieve root on CQL1 after only a few attempts/reboots. I downloaded the newer APK (version 5.3.7) from the post provided by @Kingxteam at https://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461. If anyone is looking for a simple way to root and unlock CQL1 without having to downgrade first, THIS IS IT!!! Thanks again jrkruse for the automated script, and thank you Kingxteam for the thread and links for a KingRoot APK that works with CQL1!!!
I'm getting a bit fustrated by the rooting process. Hopefully someone would be able to help me out.
Once I finished step #3 and boot into the dev and I try to root, it fails. I have tried several times and keep on failing. I took a different route and approach by reinstalling the image and re installing the kingroot and the same. Finally I gave up, and replaced the kingroot apk by its newest release. Eventually I get rooted, but once i try to unlock the boot loader i get the following message "/system/bin/sh: su: not found" .Randomly I was able to successfully run unlookbootloader once, but once the device reboots, i lose root.
Im not sure what to do, to keep root at this point.
Jalh said:
I'm getting a bit fustrated by the rooting process. Hopefully someone would be able to help me out.
Once I finished step #3 and boot into the dev and I try to root, it fails. I have tried several times and keep on failing. I took a different route and approach by reinstalling the image and re installing the kingroot and the same. Finally I gave up, and replaced the kingroot apk by its newest release. Eventually I get rooted, but once i try to unlock the boot loader i get the following message "/system/bin/sh: su: not found" .Randomly I was able to successfully run unlookbootloader once, but once the device reboots, i lose root.
Im not sure what to do, to keep root at this point.
Click to expand...
Click to collapse
Did you install the combo firmware because you don’t loose root when on the combo firmware
Sent from some device I modified
Hello all. I'll start by acknowledging that I am a noob with very little experience but can follow technical instructions to achieve desired results when they are described easily for the uninitiated. That said, I too have 2 Verizon note 4s running marshmallow with build numbers ending in CQL1. Following your tutorial, I was able to get one of my phones to step 4 where as described, it kept showing the kernel panic error no less than 10 times. I took the suggestion of another user and was finally able to achieve root with the Kingroot desktop app on my PC. I then clicked on root permissions and changed the prompt to allow. At this point I proceeded to step 6 and after clicking 2UnlockBootloader.cmd, the phone did not reboot as described and the command window returned the following message:
D:\Desktop\EMMC>adb wait-for-device
You May Need To Accept Root Dialog On Phone ...
Files/n4unlock\: 1 file pushed. 1.2 MB/s (23432 bytes in 0.018s)
cd /data/local/tmp/n4unlock
chmod 777 unlock
chown root.root unlock
./unlock
yes
exit
/system/bin/sh: su: not found
Process Complete.
Press any key to continue . . .
No dialog box appeared on my phone and I'm not sure why it says SU not found or what the significance of that missing item is to the process. Am I missing a step? Assuming I have not unlocked the bootloader with step 6, what now? What should I do at this point to achieve the desired result? I do realize that these are older phones and some might care less but making them work now could help my family in a big way. I'd gladly share some of those savings with anyone willing to help troubleshoot... thanks in advance.
Hanging on 1st BL file
Not my first time but seems like im getting hing up during the first flash. how long does it normally take for this 1st BL to flash over
<ID:0/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 636 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
Hung here for about 10min any help would be great thanks!
jrkruse said:
This Process Will Root Phone Unlock Your VZW EMMC 15 Chipset Bootloader Install TWRP Recovery And Install PreRooted Firmware Of Your Choice!.
I posted this because the current unlock methods are not easy to do. This should make process easier
If you already have unlocked bootloader and want to change bootloader versions then goto post 2
Click to expand...
Click to collapse
Working perfectly & really much much easier (than the original method which I have done twice so far so I know what I am talking about)!! Thank you
I have to throw in my hat saying that this method didn't work for me either. Like others I got stuck at the rooting stage, I tried numerous times to get root, it didn't work. I then used the upgraded KingRoot, it worked but step 6. 2UnlockBootloader.cmd script wouldn't take, since it seemingly kept losing root. But don't worry, if you've tried this method and are stuck you can still salvage it by going through the manual methods.
Make sure reactivation lock is off if you have the option (I didn't on the firmware that OP installed on the phone), usb debugging is on and adb devices brings up your phone)
----
Flash back to stock
----
I had to flash it to a stock rom using Odin (stick them in AP and make sure re-partition in options isn't checked) Android version 5.1.1, as going through the steps below (which are basically what's in 2UnlockBootloader.cmd) manually still wouldn't take: https://forum.xda-developers.com/no...mware-firmware-kernel-modem-recovery-t2942937
----
Root and bootloader unlock
----
I used the android version of KingORoot to root
I used this guide (the files used in this walkthrough are the ones largely used in the others below and downloads faster): https://forum.xda-developers.com/no...asy-guide-how-to-root-verizon-galaxy-t3454593
Which has a video here: https://www.youtube.com/watch?v=cfpehEkhfyg
and a text walkthrough with photos (that I like more) from the same guy here: https://galaxynote4root.com/galaxy-note-4-root/how-to-root-unlock-bootloader-on-galaxy-note-4/
(Since I largely used this make sure you put "samsung_unlock_n4-fix" in the fastboot folder)
Mine however began to bootloop (I'm unsure why they tell you to reboot to system on step 19 after installing the systemonly firmware but do it anyways I guess. But you had to install the kernel and superuser in twrp as addressed here: https://youtu.be/dhcV93GuHB4?t=1285
After that it booted up to 5.1.1 download rootcheck to root check it.
----
Rooting for Marshmallow
----
After that's done if you want to flash MarshMallow roms, including rooted stock 6.0.1 then you need to further go through the process here, which is basically doing it all over again:
https://forum.xda-developers.com/no...t/howto-bootloader-unlock-upgrade-to-t3398144
(Going through this process will kill your wifi connection, the KingORoot PC program didn't work to re-root mine, so you must have a sim card data connection I guess (or reverse tethering if you can get that to work(I had data so I didn't go through that).
then here when you get to the part about flashing a rom:
https://forum.xda-developers.com/no...firmware-safe-upgrade-to-marshmallow-t3402727
(Flashed with Odin (AP) not TWRP)
Anyway, I'm now rooted and bootloader unlocked. It wasn't too hard, once I found the guides it went pretty smoothly. Good luck!
using this method I get a black screen after booting up any aosp rom... logs from booted lineageos17.1:
https://pastebin.com/7yhL7FzM
I rooted 3 910v phones with this method. and am running unofficial Lineage 18.1 roms on all 3 kingroot for pc worked for me.
I updated root files and method too work on newer computers
Added latest firmware
VZW_N910VVRU2CTI1_ROOTED_FORCE_WIPE.tar.7z
jrkruse said:
I updated root files and method too work on newer computers
Added latest firmware
VZW_N910VVRU2CTI1_ROOTED_FORCE_WIPE.tar.7z
Click to expand...
Click to collapse
Thank you again for making our life easier, the ones who will appreciate your efforts are the ones who have done it manually ROCK ON!