Related
Hello everyone, Im new here so please dont kill me if this is a common question. I have searched all over but cant find the answer I need. Im excited to learn from all the wonderful information here and cant wait to get started.
Anyway, I had a Nexus S 4g flashed to work on Boost. I would like to root it so that I can change some things. However, I do not know if my phone was previously rooted. Is there anyway to find out? If it was, and I rooted it again, would that cause problems? Also, does rooting the phone cause problems with the flashing, or will it keep all of the necessary network information intact (so that it doesnt screw up my service)?
Rooting doesn't cause problems with the flashing, it just -potentially- opens up the system to damage. This is a user responsibility and not a fault of the rooting process; it's a possibility of having too much power over the system.
Most likely it would have had the bootloader unlocked and have been rooted. Turn off the phone and turn it on again by holding Vol. Up and Power simultaneously for a few seconds. If it was rooted, the best way to know is if it says "bootloader unlocked" in the upper half of the screen. If not, there is a high chance it isn't CURRENTLY rooted. If it is unlocked, the most work you need to give root access to android is going into recovery and installing a .zip file.
Exactly so after finding that out just look over one of the many guides we have here at XDA to flash the superuser package.
Sent from my Nexus S
I didnt see anything saying unlocked. I see 'Lock State - Locked', so Im assuming this means that it is not currently rooted. I guess now I will go through some guides and learn which method would be best for me. Thanks for the quick reply and help.
Most likely you aren't rooted either - you can test by typing "su" in terminal emulator.
Just remember if u unlock bootloader the internal data and sdcard will all be deleted.
Hi,
i need to get this phone rooted please, no root apps works, @Chainfire maybe can help?
Any one be able to help if this can be rooted?
xxmcvapourxx said:
Any one be able to help if this can be rooted?
Click to expand...
Click to collapse
Here we go. This is for S320VLUDU2API3 firmware, but probably works on any revision 2 firmware.
KNOX should remain 0x0
Instructions
1. Enable OEM UNLOCK
In Settings>About>Software info tap the build number 7 times to enable developer options. Once you've enabled developer options, developer options will appear in settings just above the About device option. Open developer options, the 4th or 5th option should be “OEM Unlock”. Turn on.
2. Flash the eng boot image.
This is a special boot image normally used by engineers, it allows selinux to be booted in permissive mode with relaxed root restrictions.
Do not replace this image with the stock image after rooting your device or you will possibly soft brick your device.
(See below for how to recover)
ENG_BOOT_S320VL_API3
3. Install boot image:
Download Odin v3.11.1
Reboot Phone in Download Mode (press and hold Home + Power + Volume Down buttons)
Connect phone and wait until you get a blue sign in Odin
Add the ENG_BOOT_S320VL_API3.tar to AP / PDA
Make sure re-partition is NOT ticked
Click the start button, sit back and wait few minutes
Reboot
Check in Settings>About>Software, your device should be in Selinux permissive mode.
4. Install and run Kingroot:
https://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
Make sure you have an internet connection.
You may need to run Kingroot several times to gain successful root.
5. Install and run SuperSU me to remove Kingroot and convert to SuperSU (not required) :
https://play.google.com/store/apps/...ore&pcampaignid=APPU_1_uzPDVbGyFcGNyATHrqmoCA
6. Wifi fix:
modify the line below in /system/build.prop:
ro.securestorage.support=true to false
Recovering from a soft brick:
Flash the stock firmware provided below wirh ODIN
https://firmwarefile.com/samsung-sm-s320vl
Good luck I hope it works for you.
.
ashyx said:
Here we go. This is for S320VLUDU2API3 firmware, but probably works on any revision 2 firmware.
Instructions
1. Enable OEM UNLOCK
In Settings>About>Software info tap the build number 7 times to enable developer options. Once you've enabled developer options, developer options will appear in settings just above the About device option. Open developer options, the 4th or 5th option should be “OEM Unlock”. Turn on.
2. Flash the eng boot image.
This is a special boot image normally used by engineers, it allows selinux to be booted in permissive mode with relaxed root restrictions.
Do not replace this image with the stock image after rooting your device or you will possibly soft brick your device.
(See below for how to recover)
ENG_BOOT_S320VL_API3
3. Install boot image:
Download Odin v3.11.1
Reboot Phone in Download Mode (press and hold Home + Power + Volume Down buttons)
Connect phone and wait until you get a blue sign in Odin
Add the ENG_BOOT_S320VL_API3.tar to AP / PDA
Make sure re-partition is NOT ticked
Click the start button, sit back and wait few minutes
Reboot
Check in Settings>About>Software, your device should be in Selinux permissive mode.
4. Install and run Kingroot:
https://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
Make sure you have an internet connection.
You may need to run Kingroot several times to gain successful root.
5. Install and run SuperSU me to remove Kingroot and convert to SuperSU (not required) :
https://play.google.com/store/apps/...ore&pcampaignid=APPU_1_uzPDVbGyFcGNyATHrqmoCA
6. Wifi fix:
modify the line below in /system/build.prop:
ro.securestorage.support=true to false
Recovering from a soft brick:
Flash the stock firmware provided below wirh ODIN
https://firmwarefile.com/samsung-sm-s320vl
Good luck I hope it works for you.
.
Click to expand...
Click to collapse
Hi quick question ,
i've done steps 1-3 worked fine - http://pastebin.com/raw/PbA49d0q
my next question cant i get a custom twrp to root it or custom rom cause kingaroot not working properly.
xxmcvapourxx said:
Hi quick question ,
i've done steps 1-3 worked fine - http://pastebin.com/raw/PbA49d0q
my next question cant i get a custom twrp to root it or custom rom cause kingaroot not working properly.
Click to expand...
Click to collapse
Unfortunately you can't install custom recovery on this device. This device has a locked bootloader.
What issues are you reporting, did you manage to gain root?
ashyx said:
Unfortunately you can't install custom recovery on this device. This device has a locked bootloader.
What issues are you reporting, did you manage to gain root?
Click to expand...
Click to collapse
when trying to root
By Kin9Root Won Chu chu in a few ROot failure 'not yet suitable ˉ a - condolence ˉ ˉ a ˉ a "` ` One by one - one 'one one '- one - the
i get i've tried the pc version and the apk a few tries i keep getting notifications in the settings it is set to permissive
ashyx said:
Unfortunately you can't install custom recovery on this device. This device has a locked bootloader.
What issues are you reporting, did you manage to gain root?
Click to expand...
Click to collapse
i keep getting stuck on this : https://s4.postimg.org/mxi70k1vx/Image3.png
figured it out -- it was the pin we just trying super me
xxmcvapourxx said:
i keep getting stuck on this : https://s4.postimg.org/mxi70k1vx/Image3.png
ok I tried 3 different cords, various lengths, and now no matter what I get this screen only
Click to expand...
Click to collapse
You're using the desktop version, please download and use the android English apk:
http://www.apkmirror.com/apk/kingro...-release/kingroot-5-0-5-android-apk-download/
.
Is there an update on this, did anyone achieve root?
.
ashyx said:
Is there an update on this, did anyone achieve root?
.
Click to expand...
Click to collapse
Hi,
Just update :
used the bootimge via odin works fine.
Installed kingaroot via app root takes a few times.
Superme (legit) brought removes kingaroot and installs super su and binaries then reboots <---- here i lose root again i have to use kingaroot sometimes it auto reboots it self.
My friend also has the same phone do you have skype or telegram so we can chat private
xxmcvapourxx said:
Hi,
Just update :
used the bootimge via odin works fine.
Installed kingaroot via app root takes a few times.
Superme (legit) brought removes kingaroot and installs super su and binaries then reboots <---- here i lose root again i have to use kingaroot sometimes it auto reboots it self.
My friend also has the same phone do you have skype or telegram so we can chat private
Click to expand...
Click to collapse
Does it reboot itself as soon as SuperSU me installs supersu? That's probably the reason for root not sticking.
You could try the script below, I have confirmation it still works for the same procedure.
Steps 3 to 12.
https://forum.xda-developers.com/ga...ide-how-to-root-tripping-knox-kitkat-t3129484
Obviously use updated apps and don't flash the boot partition.
You will also need to flash the system version of SuperSU not EverRoot.
When you get to step 12, don't flash the firmware.
Disable EverRoot and just flash this:
https://forum.xda-developers.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120
That should give you permanent root.
Sorry, but I don't use any of those apps you posted.
ashyx said:
Does it reboot itself as soon as SuperSU me installs supersu? That's probably the reason for root not sticking.
You could try the script below, I have confirmation it still works for the same procedure.
Steps 3 to 12.
https://forum.xda-developers.com/ga...ide-how-to-root-tripping-knox-kitkat-t3129484
Obviously use updated apps and don't flash the boot partition.
You will also need to flash the system version of SuperSU not EverRoot.
When you get to step 12, don't flash the firmware.
Disable EverRoot and just flash this:
https://forum.xda-developers.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120
That should give you permanent root.
Sorry, but I don't use any of those apps you posted.
Click to expand...
Click to collapse
Yes as soon as super su me installs ask to install binaries ans ask to reboot it will lose root.
I will try the script without flashing firmware
Thank you ill let you know how i get on
ashyx said:
Does it reboot itself as soon as SuperSU me installs supersu? That's probably the reason for root not sticking.
You could try the script below, I have confirmation it still works for the same procedure.
Steps 3 to 12.
https://forum.xda-developers.com/ga...ide-how-to-root-tripping-knox-kitkat-t3129484
Obviously use updated apps and don't flash the boot partition.
You will also need to flash the system version of SuperSU not EverRoot.
When you get to step 12, don't flash the firmware.
Disable EverRoot and just flash this:
https://forum.xda-developers.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120
That should give you permanent root.
Sorry, but I don't use any of those apps you posted.
Click to expand...
Click to collapse
My friend done a tutorial what he did on the process when losing root he followed your first guide http://pastebin.com/raw/ZSZExWt6
xxmcvapourxx said:
My friend done a tutorial what he did on the process when losing root he followed your first guide http://pastebin.com/raw/ZSZExWt6
Click to expand...
Click to collapse
It's not related to the bootloader, the bootloader is still locked, it's simply an incomplete installation of SuperSU. Probably due to permissions.
Follow the guide posted above and you should be good. I'd also suggest using root package disabler to disable knox.
Hit search in the app and type knox. Disable all knox related files.
https://play.google.com/store/apps/details?id=com.kunkunsoft.rootpackagedisablerfree
.
So can anybody confirm where we're up to with this. Has root been achieved? Are we good to post this as a viable root solution?
ashyx said:
So can anybody confirm where we're up to with this. Has root been achieved? Are we good to post this as a viable root solution?
Click to expand...
Click to collapse
Hi,
still not rooting perm -- Followed the exact tutorial you have gave us , me and my friend and we both lost root.
stock > odin > kingroot apk > supersu me > flashfire > supersu-sytemmode.2.79 rebooted lost root.
the only way we can do this is not to ever reboot....to keep root
xxmcvapourxx said:
Hi,
still not rooting perm -- Followed the exact tutorial you have gave us , me and my friend and we both lost root.
stock > odin > kingroot apk > supersu me > flashfire > supersu-sytemmode.2.79 rebooted lost root.
the only way we can do this is not to ever reboot....to keep root
Click to expand...
Click to collapse
So even when flashing root with Flashfire still losing root? Did you try using the script posted above?
Also could you post a screenshot of Root validator after losing root?
I would also suggest flashing the stock firmware with FLASHFIRE.
Ensure to Uncheck the boot partition and disable EverRoot.
Add the system supersu zip to the install.
It may be remnants of Kingroot causing the issue. Flashing this way will ensure a clean system with just supersu.
Having the same problem
I can't even do the OEM unlock and wondering if Knox is stopping me from doing it. Kingroot gets to about 77% before giving up. Also tried "one click root" and "odin" and a couple of others. Tried to uninstall Knox with many different aps but noway will it let me. I bought this J3 in HongKong and it is full of crap and adds that pop up and cover the whole screen. I have had some negative affects on the phone with all the playing around I've done to the point where when I hold down the buttons (power volume etc) the phone just goes into its first normal boot screen and stays there. Hope I haven't hijacked the thread but thought I may have the same problem as the original thread poster
stanfox said:
I can't even do the OEM unlock and wondering if Knox is stopping me from doing it. Kingroot gets to about 77% before giving up. Also tried "one click root" and "odin" and a couple of others. Tried to uninstall Knox with many different aps but noway will it let me. I bought this J3 in HongKong and it is full of crap and adds that pop up and cover the whole screen. I have had some negative affects on the phone with all the playing around I've done to the point where when I hold down the buttons (power volume etc) the phone just goes into its first normal boot screen and stays there. Hope I haven't hijacked the thread but thought I may have the same problem as the original thread poster
Click to expand...
Click to collapse
Why can't you enable OEM unlock? Remove any pin/password from the device first.
ashyx said:
Why can't you enable OEM unlock? Remove any pin/password from the device first.
Click to expand...
Click to collapse
I was surprised at first when you directed me to this thread ashyx, the first word I saw was Kingroot and I was sure a dev such as yourself wouldn't use that.
I write against Kingroot all the time. It is information stealing malware that doesn't even give true root, packs PUPs, and sends IMEI and other info to China upon install (check the logcat).
And it's nortoriously hard to get rid of and replace with a different SU. From what I read above, true root hasnt' been achieved yet. Ive used KR a few times in the past, but never again. It used to be easier to replace KingUser w SuperSU. Not so much anymore.
Please folks, Kingroot IS NOT actual root ; please quit posting about it in a true professional developer site.
Ahyx, PM me if you wish. I'd like to work on any methods other than this. I can get the bootloader unlocked from Net 10. But not until having it hooked up w/ lthem for a year. I've already chosen to disconnect this device anyhow because I can't stand using a non-rooted phone. Too bad, it's a good machine. I got a great buy on it. $50US brand new. Same store today $99. WalMart = $120
I just bought an LG G3 for $45. Verizon model, interesting root. I had to downgrade firmware to achieve root. It's TWRPd, and running Dirty Unicorns 10.6, a nice rom, better once I mod it.
Tried the latest RR rom for it. Nougat was cool, but too early, too many bugs.
Well the title says alot... let me explain..
I've got a note 5 and LG g5. This note 3 is an extra phone. So I figured I would root and rom it.
I started on 4.4.2 and it wouldn't boot...
Ran Odin 3.09 and loaded pl1...couldn't root.
Ran Odin 3.09 again with ob6. Root success.
I then followed instructions for unlock_n3 for the bootloader and also installed twrp.
Last night I went on a spree with roms trying to find a working rom with data... no success... I felt like I was doing something wrong so I went back to Odin and ran ob6 again which is where I'm at now.
In the process I dev'd my phone... and now I cannot get root and lost twrp in the process.
Did I eff up?
What's next from here? I don't care about Knox and like I said I've got 2 other phones both working and paid off. This is my "car phone". I use it for music and that's about it. That being said I would rather have working data instead of using my note 5 with Hotspot mode.
My device is now hlte... not hltevzw... I think I did something very wrong. Please halp.
If it helps I did take pictures along the way when running the unlock_n3 over adb. I've got the original emmc ID but I'm not sure if this step is reversable.
I also made a backup with twrp... but it seems my SD card was wiped at some point last night.
Please don't flame... I admit this was my stupidity and I'm sure I'm not the only one who makes mistakes. At this point I'll be happy with anything 5.0 and root. As I said above if Knox is a concern I don't really care. Phones paid off... and I've got a note 5 and when that dies I'll get a 7. Also have LG g5 as a backup.
What are my options now oh wise xda gods?
Edit: I ran arabictool again, and got a 5.0 not found error. Decided to try kingoroot, and it says succeeded, however upon running root checker, it says "Sorry! Root access is not properly installed on this device"
Edit2: After trying edit 1... im now im a bootloop, and I check vol+, home, and power and twrp is indeed gone.
When I get home I plan to Odin OB6 again, as it worked, and since i've already done it once I assume I cant do any further damage :\
Edit3: I've successfully flash back to OB6, and as expected, ive finally tripped knox. Damn near 5 years with a note 3, and JUST tripped it. Not bad if I do say so my self... although, theres still more work to be done :\
GGRRRR, I wont give up so easily! But I could use some advice
tbonedude said:
Well the title says alot... let me explain..
I've got a note 5 and LG g5. This note 3 is an extra phone. So I figured I would root and rom it.
I started on 4.4.2 and it wouldn't boot...
Ran Odin 3.09 and loaded pl1...couldn't root.
Ran Odin 3.09 again with ob6. Root success.
I then followed instructions for unlock_n3 for the bootloader and also installed twrp.
Last night I went on a spree with roms trying to find a working rom with data... no success... I felt like I was doing something wrong so I went back to Odin and ran ob6 again which is where I'm at now.
In the process I dev'd my phone... and now I cannot get root and lost twrp in the process.
Did I eff up?
What's next from here? I don't care about Knox and like I said I've got 2 other phones both working and paid off. This is my "car phone". I use it for music and that's about it. That being said I would rather have working data instead of using my note 5 with Hotspot mode.
My device is now hlte... not hltevzw... I think I did something very wrong. Please halp.
If it helps I did take pictures along the way when running the unlock_n3 over adb. I've got the original emmc ID but I'm not sure if this step is reversable.
I also made a backup with twrp... but it seems my SD card was wiped at some point last night.
Please don't flame... I admit this was my stupidity and I'm sure I'm not the only one who makes mistakes. At this point I'll be happy with anything 5.0 and root. As I said above if Knox is a concern I don't really care. Phones paid off... and I've got a note 5 and when that dies I'll get a 7. Also have LG g5 as a backup.
What are my options now oh wise xda gods?
Edit: I ran arabictool again, and got a 5.0 not found error. Decided to try kingoroot, and it says succeeded, however upon running root checker, it says "Sorry! Root access is not properly installed on this device"
Edit2: After trying edit 1... im now im a bootloop, and I check vol+, home, and power and twrp is indeed gone.
When I get home I plan to Odin OB6 again, as it worked, and since i've already done it once I assume I cant do any further damage :\
Edit3: I've successfully flash back to OB6, and as expected, ive finally tripped knox. Damn near 5 years with a note 3, and JUST tripped it. Not bad if I do say so my self... although, theres still more work to be done :\
GGRRRR, I wont give up so easily! But I could use some advice
Click to expand...
Click to collapse
You need to go thru your original steps again, root, unlock and then TWRP make sure it is the hltevzw version,
Sent from my SM-N900V using Tapatalk
donc113 said:
You need to go thru your original steps again, root, unlock and then TWRP make sure it is the hltevzw version,
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply, as of edit 3, I am back on OB6, and cannot seem to get root. Are my chances better with OF1?
Ive tried yemen tools (says 5.0 not found)
I've tried kingo root (says successful, never reboots, and shows "this phone root isnt properly setup" when checking with root checker from joey kilm (think thats his name)
Does it matter my emmc ID is ending with 43100?
https://cdn.discordapp.com/attachments/221482708063223809/378367914388094981/image.png <- image from unlock_n3 after success, emmc checker shows same value AFTER odin ob6 (this held, nothing else did)
Edit: After taking donc's recommendation of OF1, I am now able to run yemen tools. As a side note, I seem to have more bars of service with OF1... coincidence?
Edit2: I HAVE ROOT! on OF1 using yemen tools (downgraded from PL1 to OB6 finally to OB1 and it worked.) Now to re-unlock bootloader. Thanks guys for the support thus far, this is a journey and having qualified accomplices makes this SOOOO much easier.
So heres where im at now.. as a recap for personal use, and anyone else who may be on a similar path.
Start to finish, this is what I did, where im at now, and where I want to be by tonight
Got phone, 4.4.2 with bootloop, couldn't find 4.4.2 firmware online
Flashed 5.0 (PL1), no root available.
Flashed 5.0 (OB6) rooted, unlocked boot loader, twrp, played with roms, got frustrated, re-flashed OB6 and couldn't root again (seems flimsy)
Flashed 5.0 (OF1) rooted, unlocked boot loader, verified several times root is working. Installed SuperSu and busybox.
This is where im at now, about to install twrp since i've done this already with ob6, and was working fine (though, I would prefer to have philz, and multi rom slots)
This entire process i've been using Odin 3.09, Twrp 3.0.2-1. My note 3 has been changed to a dev ID ending in 3100 (see above posts) this seems to have held through entire process with multiple recoveries.
I am going to make a full backup (again...) and unlike last time... store this copy onto my PC instead of SDcard alone... this was my mistake, and I need to learn from it.
For the @dev's out there, is there anything I can provide to help this overall process and community in general? I'm fairly literate in adb/linux and have no issues running commands, uploading files, or anything similar.
Shout out to @donc113 above for stating the obvious (since i failed to search and find the proper methods) as well as giving me the kick in the pants I needed to push onwards and succeed. Thanks brotha. :good:
tbonedude said:
So heres where im at now.. as a recap for personal use, and anyone else who may be on a similar path.
Start to finish, this is what I did, where im at now, and where I want to be by tonight
Got phone, 4.4.2 with bootloop, couldn't find 4.4.2 firmware online
Flashed 5.0 (PL1), no root available.
Flashed 5.0 (OB6) rooted, unlocked boot loader, twrp, played with roms, got frustrated, re-flashed OB6 and couldn't root again (seems flimsy)
Flashed 5.0 (OF1) rooted, unlocked boot loader, verified several times root is working. Installed SuperSu and busybox.
This is where im at now, about to install twrp since i've done this already with ob6, and was working fine (though, I would prefer to have philz, and multi rom slots)
This entire process i've been using Odin 3.09, Twrp 3.0.2-1. My note 3 has been changed to a dev ID ending in 3100 (see above posts) this seems to have held through entire process with multiple recoveries.
I am going to make a full backup (again...) and unlike last time... store this copy onto my PC instead of SDcard alone... this was my mistake, and I need to learn from it.
For the @dev's out there, is there anything I can provide to help this overall process and community in general? I'm fairly literate in adb/linux and have no issues running commands, uploading files, or anything similar.
Shout out to @donc113 above for stating the obvious (since i failed to search and find the proper methods) as well as giving me the kick in the pants I needed to push onwards and succeed. Thanks brotha. :good:
Click to expand...
Click to collapse
You're welcome. Just an FYI, the ending of the CID doesn't matter, it's the first 2 numbers that count, and they MUST be 15
I used Flashify (available on Google Play) to load TWRP... worked great (but you must have root and busybox installed to use it to flash TWRP)
Sent from my SM-N900V using Tapatalk
Here's my Cheat Sheet ! This is the same procedure I used a while back with N910VVRU2CPD1 . I just updated the thread to work with the newer package.
1. Odin SamMobile N910VVRU2BPA1
reboot and factory reset a few times if needed to remove custom icon
2. Odin hsbadr's N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar HERE
3. Unlock with the samsung_unlock_n4-fix PROCESS use SIM card for data. Wi-Fi will not work at this point.
4. Odin twrp-3.0.2-0-trltevzw.tar Uncheck Auto Reboot, Manually boot into TWRP
5. Odin hsbadr's N910VVRU2CPD1_StockRestore.tar HERE
6. TWRP BETA-SuperSU-v2.71-20160331103524, Factory Reset, boot system
7. Use FlashFire to Flash firmware package SamMobile N910VVRU2CQI2
( ! System and Cache only ! )
Your mileage may vary.
Before I install my personal apps I remove as much Verizon, Samsung and Google spyware as possible.
-------------------------------------------------------------------------------------------------
EDIT: I was able to skip the recommended rooting and unlocking of 5.1.1 and make the jump I described.
I did not do the unlock using Kingroot until step 3 and I did not permanent root with Super Su until step 6.
No matter how you get there the phone has to be on [Firmware] [MM] [6.0.1] [RetEd/DevEd] Safe Upgrade to Marshmallow [N910VVRU2CPD1] then you can use FlashFire.
Hyperlinks are in the text to most of what's needed.
Credit AstonsAndroid I found it HERE
I keep seeing people saying there is a way to just flash TWRP and Magisk and you're done. I'd like to avoid SuperSU and the other root methods if possible. How would that work with your updated guide? Thanks
My main concern is the spyware the guys on Reddit bring up. Not to use kingroot and the like. Was there any resolution to this thread you posted Dr cool? Want to unlock my bootloader and flash the MODest ROM but I want to be able to avoid spyware too. Thanks for your work.
https://forum.xda-developers.com/no...spyware-fix-fixed-lag-wi-fi-problems-t3433839
RootMyNote4Please said:
My main concern is the spyware the guys on Reddit bring up. Not to use kingroot and the like. Was there any resolution to this thread you posted Dr cool? Want to unlock my bootloader and flash the MODest ROM but I want to be able to avoid spyware too. Thanks for your work.
https://forum.xda-developers.com/no...spyware-fix-fixed-lag-wi-fi-problems-t3433839
Click to expand...
Click to collapse
I'm not sure if it was spyware or what. but my phone performance better after cleaning out that folder.
Thanks doc. Is that a folder that gets overwritten when you flash a new room?
This says "Continue with sim card data because wifi wont work at this point."
What if we don't have any data right now? Will it still work?
lodilovesmuffins said:
This says "Continue with sim card data because wifi wont work at this point."
What if we don't have any data right now? Will it still work?
Click to expand...
Click to collapse
Kingroot needs to connected to root. I never seen it work without a connection. N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar brakes wifi but you get it back with N910VVRU2CPD1_StockRestore.tar, I dont know why. It just works
RootMyNote4Please said:
Thanks doc. Is that a folder that gets overwritten when you flash a new room?
Click to expand...
Click to collapse
My best guess now is it's some kind of provisioning issue that is cleaned up. Some of the files deleted you may actually need some day.
does this require the developer version? btw how do i backup
I seem to lose root after I flash CPD1. Still have TWRP though and says developer mode. What could be causing this?
Edit - When I flash stock restore I mean. I get rooted on BPA/CPD and then when I go to the next step I'm losing root and Kingroot says it has no solutions. I must be doing something wrong.
RootMyNote4Please said:
I seem to lose root after I flash CPD1. Still have TWRP though and says developer mode. What could be causing this?
Edit - When I flash stock restore I mean. I get rooted on BPA/CPD and then when I go to the next step I'm losing root and Kingroot says it has no solutions. I must be doing something wrong.
Click to expand...
Click to collapse
As long as you have TWRP installed still you are in good shape. At that point, you could either flash (through TWRP) SuperSu or magisk (on certain kernels magisk install errors out in twrp). The main objective is to get the custom recovery (twrp) installed on the 6.0.1 bootloader and once that's done it's just a matter of flashing your preferred rooting method or flashing a rom that has root included.
You can use an app like this to check your bootloader to make sure it's the right one.
kevintm78 said:
As long as you have TWRP installed still you are in good shape. At that point, you could either flash (through TWRP) SuperSu or magisk (on certain kernels magisk install errors out in twrp). The main objective is to get the custom recovery (twrp) installed on the 6.0.1 bootloader and once that's done it's just a matter of flashing your preferred rooting method or flashing a rom that has root included.
You can use an app like this to check your bootloader to make sure it's the right one.
Click to expand...
Click to collapse
That's weird. I flashed SuperSU but it didn't show up in the apps and when I tried to use Flashfire it said I didn't have root.
Got there. SuperSU had an error message when I tried to install it the 1st time after flashing full system. So I rebooted and installed again. Now Flashfire crashes and won't open. Switched to Flashify and it seems to work ok.
Edit - Stuck here for now. Flashify can't seem to find the CQI2 file and I still haven't been able to get Flashfire to work. Tried an older version and still crashes when it checks to see if I have the pro version or not.
In case someone else has the same problem with Flashfire, it's because the program expired April 1st, 2018. Turn the date back on your phone and it will load.
Finally completed it!!!
Ok, so the things I learned from my trials and errors.
1) DON'T flash the kernal and SU after you root with the N4 fix. I did this the 1st 15 times and could never get Flashfire to work later on. So skip all of the stuff in that post after you flash TWRP. Then flash the next firmware step.
2) Uncheck auto time and date on your phone and roll it back to before 4/1/18 to get Flashfire to work.
I'm sure there are some more things and I'll add whatever else I think can help the next guy along. Good luck! And thanks for the guide doc!
Note: Did the phone icon on your lock screen disappear as well when you were done? The camera is there on the bottom right like normal, but the phone is gone on the bottom left and it displays the charging info there now.
Thanks for this - it was helpful to make clear that in my mind that despite what other guides say, there is no need to unlock a Lollipop bootloader with a Lollipop kernel + ROM first, and that we can boot a Lollipop kernel + ROM with a Marshmallow bootchain and unlock the Marshmallow bootloader from the get-go.
I tracked down the CQI2 full Odin and I made hybrid Odins that get you "rooted on N910VVRU2CQI2" in fewer steps, following hsbadr's file naming scheme:
N910VVRU2BPA1_N910VVRU2CQI2_FullFirmware.tar.md5: MM CQI2 bootchain/firmware/modem, LL BPA1 ROM/kernel/recovery
N910VVRU2CQI2_StockRestore.tar: MM CQI2 ROM/kernel (no recovery - TWRP isn't overwritten)
These should be fine as drop-in replacements for the files mentioned in steps 2 and 5 of your guide.
Using these obviously means that you are unlocking the CQI2 aboot instead of the CPD1 aboot in step 3 while temprooted, and - importantly - step 7 is unnecessary to get to a CQI2 ROM, which is good because Flashfire is now expired :3
I doubt there's much of a real benefit to being on the newer aboot, but hey, why not.
Hey, no one answered my question from a while ago. So I'll ask again, does this require the developer version of the Note 4?
lodilovesmuffins said:
Hey, no one answered my question from a while ago. So I'll ask again, does this require the developer version of the Note 4?
Click to expand...
Click to collapse
No, this will work with both versions of the verizon note 4.
kevintm78 said:
No, this will work with both versions of the verizon note 4.
Click to expand...
Click to collapse
Ok, thank you very much. I'll try and root my phone with this tutorial now.
Please help!!!!
I followed this link because its supposed to be a way to downgrade from 6.1.0 to 5.1.1 so I can unlock boot loader. However, these instructions make no sense to me. Can someone PLEASE help me. I've been searching and searching for a way to root my note 4 (N910VVRS2CQA1) and can't seem to find a way. I've never done this before so I'm pretty clueless. When I read these instructions, I just don't understand what I'm supposed to be doing. A lot of this tech lingo means nothing to me unfortunately. I'm starting to thing I should just give up the idea of rooting this Note 4 that's getting slower and slower and just get a new one. I don't really want to though bc I love the fact that you can replace the battery. It'd be much easier to just root and upgrade.....well, easier if I actually knew how.
EDIT 3: It appears this device has a locked bootloader, which means that twrp wont work, and that device tree was a waste of time... I guess I'll just wait until someone or Samsung releases the firmware for Magisk.
EDIT 2: I have successfully built a device tree for this device using TWRPBuilder's script on github. Although it might not be fully complete, it is still a start. Note: I built using an android 8 release. Does the boardconfig.mk file still work for android 9????
I plan on comparing it with a different device tree to make sure nothing is blatantly wrong with it, but I'm not a developer so I don't know if that will help.
(Anyone willing to help me? If I could efficiently navigate the linux CLI I would probably be much faster...)
My current plan is to build TWRP for this device to back up the ROM so that I can use Magisk.
https://github.com/TwrpBuilder/twrpbuilder_tree_generator/blob/master/README.md
Link to device tree builder for those interested. Dont even ask how long it took me to realize I had to add the commands to the end of the java executive instead of typing TWRPBuilder -r recovery.img. command.
-------
EDIT: To those that read, Samsung has restrictions against downgrading apparently. Currently, the only way for root is by waiting for someone to share the official stock ROM. The first half of this method about getting the firmware Does Not Work I don't know about the rest...
-----
Hello everyone,
I would first like to say that I think this is a working method, but I want to double check with someone who has rooted before.
I have the above mentioned phone, and after a ton of research, have determined a path to rooting it through Magisk. I'm currently running Android Pie 9, on the latest stock firmware from att.
This phone does not have A/B partitioning, but has system-as-root and it will require a copy (and Magisk patched) ROM to root.
One of the main problems I have is not having the latest firmware for my device. (Don't tell me to look it up. Its non-existent on the web) I have found that Samsung's Smart Switch will allow you to obtain the official ROM.
However, to download the ROM, I have to have an outdated phone. The most recent update for my phone was to upgrade from Android 8.0 to 9.0.
I assume such an upgrade requires the whole ROM to be downloaded.
Is it possible to use an outdated ROM for my phone (Yes, I have one for android 8) and downgrade my OS so that I can then update from Smart Switch and get a copy of the current firmware to use with Magisk?
Edit: apparently Samsung has protections against downgrading. I tried samfirm but to no avail.
Anyone know of any compatible custom ROMs?
Will keep trying to root though...
I know many people will immediately say yes, but this phone is different.
There is no OEM unlock in Developer options (read more about this further!), and there is no fastboot. There is no TWRP for this phone either (some older threads on Magisk mentioned TWRP, so I am confused if I need it for rooting via Magisk)
I have discovered, that if you were to hold HOME + POWER + UP, on powerup, you can get to a warning about installing custom OSes and an option to continue.
I pressed continue.
Someone on the web said pressing up will wipe the phone, since it unlocks the bootloader.
My phone did not get wiped.
Is my phone's bootloader/OEM unlocked?
I want to know because I Think Magisk requires an unlocked bootloader.
If Magisk doesn't, I'm all good, and I am glad I can install custom OSes (not my goal, but will do if desperate)
If it does require it, I believe my hone already has an unlocked bootloader/OEM
One last note, does downgrading trip anything? I have no warranty, but I know there are other protections (like KNOX) that could affect the outcome.
(I've heard downgrading won't change anything)
Is there anything I need to turn off?
To Recap:
Downgrade OS
Update via Smart Switch to get stock ROM
Use Magisk to root my phone.
I'm simply asking if everything will turn out OK.
(Sorry for the exceedingly long post)
Thanks.
I don't have this phone but I wanted to have one, but after I realized there is no method to unlock it, you are out of luck I also have a phone laying around (Zte Avid Plus with android lolipop), I built a ROM and recovery for it but I realized there is no method to unlock the bootloader. The only method is to get your hands on the bootloader from this device and try and modify it and pray that it works. That is just how a lot budget devices are built nowadays. And that's sad. The thing is that there was a successor to the Zte Avid with the same specs but it ran Android Oreo. Meanwhile the Avid ran Lolipop. A method from manufacturers to always force us to buy new phones.