Need help with root for Galaxy SM-J320VPP / android 6.0.1 - Android Q&A, Help & Troubleshooting

i know this is a newer phone but i'm still pretty surprised i haven't been able to find anyone that's rooted it yet. i've been all over the internet it seems. this is the :
Samsung Galaxy J3(6)
SM-J320VPP
Android 6.0.1 Marshamllow
Verizon pre-paid plan/network
i see lots of videos and guides for other j320f or j320p (close but no cigar) and nothing works. what i've tried so far:
- Dev mode enabled, USB debugging and OEM unlocked.
- any/all 1 click root apps. none worked, and i'd like to avoid these anyway unless you know it works 100% for my version. at this point i'll try anything.
- recovery / flash superSU. only i haven't even gotten past flashing a recovery. i've tried several different versions of Odin with several different versions of recovery .tar's and for each combination i've tried Odin simply fails. big red FAIL button in upper left corner. sadness. this seems like what i need help with. i have SuperSU downloaded so if i can just get a custom recovery working for my phone i'm hoping it's a simple process from there of booting into the custom recovery and then installing the SuperSU. presto.
is there no hope? is there no tested, confirmed working recovery that i can flash to my phone using Odin? i've tried Odins 3.07, 3.09, and 3.11.1. various custom recovery .tars but the only one i know for sure is the J2 version official from TWRP's website (yes i know it says J2 but someone on another thread said it's similar enough to someone ELSE's model "j320f" or something so i gave it a shot) the other recovery .tars i tried are suspect since they had generic names "recovery.tar" and were downloaded from links provided in many different "guides" that i've googled.
internet, you have failed me. thus do i issue this challenge to all those mighty phone hackers of the land. come forth and slay the evil giant that is my phone's ludicrous security (seriosuly how is this even a thing still in 2016. my phone can do so much more, so much better but for these shenanigans).
thanks so much in advance!
EDIT: not sure about the bootloader. i may be a complete idiot. yes. ok. i'm onto something. gonna post this anyway for any other poor soul that has this version phone, but i think Odin's probably failing because the bootloader is still locked. and Samsung doesn't make this easy like motorola or HTC. T_T. once more into the fray! i'll see if i can't track down a method for unlocking the bootloader on my phone. should i return victorious i'll go ahead and share my steps with the rest of the class.
EDIT2: there is no waking from this nightmare. i dig and dig and dig and can find no root. *sigh*
-- i've got android studio installed. and the java SDK platform-tools which contains the adb.exe, fastboot.exe, etc.
-- something i should explain here: in all these guides whenever there's a step that requires the phone to be connected to the PC, it simply says to, you know...connect your phone. but MY phone by default only uses the cable for battery charging. i have to (on my phone) swipe down from the top, select the "connected for charging" message bringing up "Use USB For" options, then select "Transferring media files" option. THEN my phone shows up both in my windows explorer and displays as a device when i run "adb devices".
--when i run "adb reboot bootloader" this does the same thing as holding down pwr/home/vol down - phone boots up into a blue (teal?) background with a large down arrow in center, below that it says "downloading...do not turn off target". in the upper left are several lines of system font style text:
ODIN MODE
PRODUCT NAME: SM-J320VPP
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
FRP LOCK: OFF*
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T1, H1, R1, A1, P1*
SECURE DOWNLOAD: ENABLE
*the R's above may be A's or vice versa...hard to read font. sorry
--but as soon as i've rebooted into this mode, my phone disappears from adb devices' list of devices attached. regardless when i run the "fastboot oem unlock" command from the adb shell on my PC at this point i get the infamous "waiting for any device" message and then, of course, nothing....forever. i've also installed PDAnet but i think it's hitting the same road block where my phone is only using the cable for battery charging and i can't toggle that option from ODIN MODE. there's also a "USB Configuration" choice under development options on the phone that has the same options as "Use USB for" but this doesn't stick when booting into ODIN MODE. sadness. i need to retire my brain thoughts at this point. will post TL;DR. you're a saint of geeks if you've made it through my WoT to here.
EDIT3: just an observation - the only thing (so far) that will detect my phone in ODIN MODE is ODIN itself. is there a way to use ODIN to unlock the bootloader?
TL;DR: i think odin is failing when attempting to flash because of locked bootloader. need help with unlocking bootloader first? phone defaults to use USB cable for charging only so i CAN change that to MTP while phone is on normal and then run "adb reboot bootloader" but then phone vanishes from adb devices list once it reboots (and cable is then only charging). thus, cannot run "adb fastboot oem unlock" cuz it hangs displaying "waiting for any device" -- can i unlock the bootloader on this phone? or did i buy a phone that's IMPOSSIBLE TO ROOT!?!?

I have the same problem! I need to root it to install the Patch to change from CDMA to GSM! Because I tried without root and it tells me "E: Signature verification failed"
Thanks

Still nothing?
This is starting to look hopeless

we need the stock recovery.img to be able to mod it and flash it through odin. the recovery for the verizon version does not match so odin wont allow it. i asked on sammobile and they said verizon only releases ota on the device. so idk what to do. perhaps someone with knowledge on this will help.
so far what ive figured out our situation is:
we need root to get root.
more specifically we need root to pull the recovery and then mod that recovery with twrp and use twrp to gain root. The root methods that worked for the other variant SM-J320P dont appear to work for ours, probably due to having android 6.0.1
till we get root we are stuck. the rest is easyish

News?
There is nowbody that had been rooted his J3 Verizon yet?? We need help with this trouble!
In this forum (http://forum.xda-developers.com/android/help/galaxy-j3-sm-j320vpp-configuring-cdma-t3414049) Sergio said:
" try root with this root is only for Snapdragon 410 MSM8916
http://forum.gsmhosting.com/vbb/f723...t1994-1946985/ "
The J320VPP has a "1.2 GHz, Quad-Core". There is no place that sais it's a "Qualcomm Snapdragon 410 Msm:8916" processor. You think this suggestion could work?

NerdmastaX said:
we need the stock recovery.img to be able to mod it and flash it through odin. the recovery for the verizon version does not match so odin wont allow it. i asked on sammobile and they said verizon only releases ota on the device. so idk what to do. perhaps someone with knowledge on this will help.
so far what ive figured out our situation is:
we need root to get root.
more specifically we need root to pull the recovery and then mod that recovery with twrp and use twrp to gain root. The root methods that worked for the other variant SM-J320P dont appear to work for ours, probably due to having android 6.0.1
till we get root we are stuck. the rest is easyish
Click to expand...
Click to collapse
I think I've managed to get the recovery.img with KIES... However flashing the image I've extracted doesn't work but if anyone is ready to help me port a recovery I might try !

Whusky said:
I think I've managed to get the recovery.img with KIES... However flashing the image I've extracted doesn't work but if anyone is ready to help me port a recovery I might try !
Click to expand...
Click to collapse
im gonna try and do a reflash with kies and grab that file myself, ill work a bit on it because i love this phone but no basic root is driving me insane. if you can beat me to posting tell me how you got the file, otherwise ill post here once i find out. I'm not a top of the line developer but i can work my way around and try my best since nobody else is offering to help.
wish me luck.

sorry for the double post but got the files via the verizon software assistant no problem. it ended up in C:\Users\YOURNAME\AppData\Roaming\Verizon_AR\SM-J320VPP_J320VPPVRU1APC3_FACTORY for me, and even decrypted and unzipped itself for me, now we just need to mod a custom thingy into those files and we can work towards rooting. so as i sit here and watch my phone finish flashing back to factory i will look into how we can mod the recovery. if someone is capable of doing it faster i can upload the files very quickly as its only 1.4 gb

well turns out verizon locks the flashing with signature verfication. so unless verizon changes or root is found for marshmellow there will be zero possible root for this phone.

NerdmastaX said:
sorry for the double post but got the files via the verizon software assistant no problem. it ended up in C:\Users\YOURNAME\AppData\Roaming\Verizon_AR\SM-J320VPP_J320VPPVRU1APC3_FACTORY for me, and even decrypted and unzipped itself for me, now we just need to mod a custom thingy into those files and we can work towards rooting. so as i sit here and watch my phone finish flashing back to factory i will look into how we can mod the recovery. if someone is capable of doing it faster i can upload the files very quickly as its only 1.4 gb
Click to expand...
Click to collapse
Hi I'm currently rooted with TWRP 3.0.2 recovery and mabey this might help http://forum.xda-developers.com/general/help/samsung-galaxy-j3-sm-j320fn-how-to-root-t3369511

Sparko612 said:
Hi I'm currently rooted with TWRP 3.0.2 recovery and mabey this might help http://forum.xda-developers.com/general/help/samsung-galaxy-j3-sm-j320fn-how-to-root-t3369511
Click to expand...
Click to collapse
verizon blocks flashing of modified recoveries. so unless someone finds a root exploit for marshmallow we will have no luck.

Has the kingroot method worked for root on your device ??

NerdmastaX said:
we need the stock recovery.img to be able to mod it and flash it through odin. the recovery for the verizon version does not match so odin wont allow it. i asked on sammobile and they said verizon only releases ota on the device. so idk what to do. perhaps someone with knowledge on this will help.
so far what ive figured out our situation is:
we need root to get root.
more specifically we need root to pull the recovery and then mod that recovery with twrp and use twrp to gain root. The root methods that worked for the other variant SM-J320P dont appear to work for ours, probably due to having android 6.0.1
till we get root we are stuck. the rest is easyish
Click to expand...
Click to collapse
Hi to all, im new here and i am having the exact same problem! You say that there has to be a root specifically for the 6.0.. So i found that in the Chainfire page they have this https://download.chainfire.eu/986/CF-Root/CF-Auto-Root/CF-Auto-Root-j3lteusc-j3lteusc-smj320r4.zip already (i dont know if i can post links, so if i cant, sorry), it is marshmallow but the model is J320R4, so i was wondering if this could be the solution. i'll be waiting here for a response, i seriously love this phone :c

MetAJFA said:
Hi to all, im new here and i am having the exact same problem! You say that there has to be a root specifically for the 6.0.. So i found that in the Chainfire page they have this https://download.chainfire.eu/986/CF-Root/CF-Auto-Root/CF-Auto-Root-j3lteusc-j3lteusc-smj320r4.zip already (i dont know if i can post links, so if i cant, sorry), it is marshmallow but the model is J320R4, so i was wondering if this could be the solution. i'll be waiting here for a response, i seriously love this phone :c
Click to expand...
Click to collapse
No, this is not the solution. When using a utlity like CF Auto Root, it must be specific to your model / carrier. Trying to install that will do 1 of 2 things.
1) Just fail in Odin
or
2) Soft brick your device
Since VZW doesn't bother to put out the full firmware files to reflash the device, it's not worth attempting without having the backup plan of the original firmware to flash via Odin.

an twrp is already available for j320p u can try to root your device using it

es0tericcha0s said:
No, this is not the solution. When using a utlity like CF Auto Root, it must be specific to your model / carrier. Trying to install that will do 1 of 2 things.
1) Just fail in Odin
or
2) Soft brick your device
Since VZW doesn't bother to put out the full firmware files to reflash the device, it's not worth attempting without having the backup plan of the original firmware to flash via Odin.
Click to expand...
Click to collapse
Understood, thank very much you for clearing that out. Since all this is pretty much a kick in the butt, do you think there will be some kind of solution to this or should we just lose hope? :/

can Someone here help me with this.
someone wrote:
I have the same problem, I already got 4G LTE data with the correct APN and also I change to lte/gsm with the help of a network app and with commands in adb shell :
pm clear com.android.providers.telephony
settings put global preferred_network_mode 9
settings put global preferred_network_mode1 9
settings put global preferred_network_mode2 9
Click to expand...
Click to collapse
but i dont know how to initiate this adb mode in the phone. anyone?

anyone fix ?
i have few units J320VPP same problem .. searching for service .

That's a Verizon device with a locked bootloader, you cannot try twrp or modified files meant for 320f or other models on this one.
Sent from my SM-N920G using Tapatalk

So has anyone found any luck with this device? It's driving me crazy not having root

Related

[Q] All in one Root tool

Hi folks. I am not allowed to post in the developer forums since I am a new user so I figured I'd try here and hopefully some developer will be watching this forum.
I want to root my new Verizon Samsung Galaxy S4. I found the thread regarding the all in one tool for doing the root and installing recovery.
I followed the instructions, downloaded the tool, connected my phone, invoked the tool and selected Option 1 (Root my phone). The cursor skipped down one line and then nothing. I waited 15 minutes to make sure it wasn't doing anything but that's it, nothing.
I am new to Android and therefore new to Rooting so I thought this all in one tool would be perfect for me to get the job done. But I now have no idea why nothing happens when I invoke the tool and select Option 1.
Is there somebody in this forum who can help me please?
Thanks ............ Rob
goldberg96 said:
Hi folks. I am not allowed to post in the developer forums since I am a new user so I figured I'd try here and hopefully some developer will be watching this forum.
I want to root my new Verizon Samsung Galaxy S4. I found the thread regarding the all in one tool for doing the root and installing recovery.
I followed the instructions, downloaded the tool, connected my phone, invoked the tool and selected Option 1 (Root my phone). The cursor skipped down one line and then nothing. I waited 15 minutes to make sure it wasn't doing anything but that's it, nothing.
I am new to Android and therefore new to Rooting so I thought this all in one tool would be perfect for me to get the job done. But I now have no idea why nothing happens when I invoke the tool and select Option 1.
Is there somebody in this forum who can help me please?
Thanks ............ Rob
Click to expand...
Click to collapse
Once you select Option 1, you need to go back to the main windows to uncheck one box (F something) and then click start before it does the rooting. I missed it yesterday also and just keep waiting until I realized there was a step I didn't do.
goldberg96 said:
Hi folks. I am not allowed to post in the developer forums since I am a new user so I figured I'd try here and hopefully some developer will be watching this forum.
I want to root my new Verizon Samsung Galaxy S4. I found the thread regarding the all in one tool for doing the root and installing recovery.
I followed the instructions, downloaded the tool, connected my phone, invoked the tool and selected Option 1 (Root my phone). The cursor skipped down one line and then nothing. I waited 15 minutes to make sure it wasn't doing anything but that's it, nothing.
I am new to Android and therefore new to Rooting so I thought this all in one tool would be perfect for me to get the job done. But I now have no idea why nothing happens when I invoke the tool and select Option 1.
Is there somebody in this forum who can help me please?
Thanks ............ Rob
Click to expand...
Click to collapse
Delete the root toolkit, restart your computer and download it again. Same thing happened to me :thumbup:
Sent from my SCH-I545 using xda app-developers app
Help!
I am having the same problem and my phone is sitting there with a large android icon and message reading "Downloading.. Do not turn off target!!" I am afraid to disconnect the phone from the USB. What should I do?
ThugosaurusRex said:
Delete the root toolkit, restart your computer and download it again. Same thing happened to me :thumbup:
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Same here, Verizon Samsung g s4.
I followed the instructions: unchecked the F. reset box, and selected tar and clicked start. The "<OSM> All threads completed. (succeed 0 / failed 0) line showed up, and nothing else.
goldberg96 said:
Hi folks. I am not allowed to post in the developer forums since I am a new user so I figured I'd try here and hopefully some developer will be watching this forum.
I want to root my new Verizon Samsung Galaxy S4. I found the thread regarding the all in one tool for doing the root and installing recovery.
I followed the instructions, downloaded the tool, connected my phone, invoked the tool and selected Option 1 (Root my phone). The cursor skipped down one line and then nothing. I waited 15 minutes to make sure it wasn't doing anything but that's it, nothing.
I am new to Android and therefore new to Rooting so I thought this all in one tool would be perfect for me to get the job done. But I now have no idea why nothing happens when I invoke the tool and select Option 1.
Is there somebody in this forum who can help me please?
Thanks ............ Rob
Click to expand...
Click to collapse
Did you enable USB debugging and third-party? USB debugging can be found by tapping on build number (i think) under about phone like 7 times. Developer options should appear in your settings after that. Third-party sources is under security I believe. Hope that helps!
whichonespink73 said:
Did you enable USB debugging and third-party? USB debugging can be found by tapping on build number (i think) under about phone like 7 times. Developer options should appear in your settings after that. Third-party sources is under security I believe. Hope that helps!
Click to expand...
Click to collapse
I don't mean to hijack any responses here, but seeing as I have the same problem as OP I think it's safe to say that he also enabled USB debugging and third-party sources. Nothing
dabs delicious said:
I don't mean to hijack any responses here, but seeing as I have the same problem as OP I think it's safe to say that he also enabled USB debugging and third-party sources. Nothing
Click to expand...
Click to collapse
I actually found my problem. Even though I had the usb debugging flag set, when I tried to root, a popup window came up in the background asking me to confirm that I wanted to enable usb debugging. Because it was in the background I kept missing it. Once I saw it and replied, everything worked perfectly. Hope this maybe helps someone.
goldberg96 said:
I actually found my problem. Even though I had the usb debugging flag set, when I tried to root, a popup window came up in the background asking me to confirm that I wanted to enable usb debugging. Because it was in the background I kept missing it. Once I saw it and replied, everything worked perfectly. Hope this maybe helps someone.
Click to expand...
Click to collapse
You're talking about the popup window on your phone, right? Because It pops up for me too, and I click "confirm" each time, but to no avail
Does anyone else have any suggestions?
Question about using the 3 in 1 tool
I am wondering a few things. I have the Samsung Galaxy 4 that has not been activated by Verizon yet. I want to use it on Straight Talk which uses GSM. After running this tool with the unlocking and rooting, will I be able to do this?
Super Noob
Hello everyone this is my very first post, I am looking to root my verizon s4 using the one tool kit i dont believe i will have any trouble doing so i have rooted a few phones in my past before, my only question is about unrooting. i didnt want to start a whole new thread for this so figured i would ask here. is the VRUAMDK Factory Image (modified with No-Wipe) that you download from http://forum.xda-developers.com/showthread.php?t=2301259 is that the stock verizon firmware the only thing holding me back from rooting is not being sure that i have the stock firmware to flash, i might mess up and wanna make sure i have that for any situation that might come up. would someone plz confirm that that is the file i want to return to no root stock
missjamie said:
I am wondering a few things. I have the Samsung Galaxy 4 that has not been activated by Verizon yet. I want to use it on Straight Talk which uses GSM. After running this tool with the unlocking and rooting, will I be able to do this?
Click to expand...
Click to collapse
Root just allows you to hack the software on your phone, and the "unlock" refers to the bootloader. It does not unlock the phone for other carriers; this is done (from what I understand) by dialing a specific set of codes, generally provided to you by the original carrier of the phone if you have an account in good standing with them and you tell them you plan on travelling out of the country and need to use GSM. I have never needed to do this and as such only have a minor theoretical knowledge of the subject; I would appreciate it if somebody with more knowledge on this would confirm or deny my suspicion that you are better off trading the phone for an AT&T/T-Mobile one that actually was meant for GSM, or otherwise obtaining one.
JNava420 said:
Hello everyone this is my very first post, I am looking to root my Verizon s4 using the one tool kit i don't believe i will have any trouble doing so i have rooted a few phones in my past before, my only question is about unrooting. I didn't want to start a whole new thread for this so figured i would ask here. is the VRUAMDK Factory Image (modified with No-Wipe) that you download from http://forum.xda-developers.com/showthread.php?t=2301259 is that the stock Verizon firmware the only thing holding me back from rooting is not being sure that i have the stock firmware to flash, i might mess up and wanna make sure i have that for any situation that might come up. would someone plz confirm that that is the file i want to return to no root stock
Click to expand...
Click to collapse
This is the original bootloader; not the stock firmware. You need to flash this after you successfully root, start the phone, start SuperSU, and update the SU binary.
The full stock firmware is rather large and available here:
http://forum.xda-developers.com/showthread.php?t=2289325
might not know as much as i thought
thanks for telling me this first of all, so let me see if i get this right and im hoping you or someone will tell me if im correct or not. The all in one root method does that take care of the whole SuperSu, and update part or do i still need to do that after the root tool does its business? With unrooting do i just need to flash the stock firmware in odin use triangle away and i should be good correct, im not quite understanding the whole thats the original bootloader....the file that downloads is a .tar i thought that was firmware/rom....what do i need the original bootloarder for exactly? I honestly am to the point id be willing to pay someone who has a credible rep to video chat and walk me through it all
If you need assistance. Pm me. If I sm available ill help you.
JNava420 said:
thanks for telling me this first of all, so let me see if i get this right and im hoping you or someone will tell me if im correct or not. The all in one root method does that take care of the whole SuperSu, and update part or do i still need to do that after the root tool does its business? With unrooting do i just need to flash the stock firmware in odin use triangle away and i should be good correct, im not quite understanding the whole thats the original bootloader....the file that downloads is a .tar i thought that was firmware/rom....what do i need the original bootloarder for exactly? I honestly am to the point id be willing to pay someone who has a credible rep to video chat and walk me through it all
Click to expand...
Click to collapse
The original bootloader is locked and doesn't allow for us to use the exploit to install SuperSU and root the phone.
We are installing the unlocked bootloader via Odin...
Then running motochopper to exploit a vulnerability to gain root...
Then MANUALLY (this can't happen automagically) opening SuperSU and updating the SU binary...
Then rebooting the phone to make sure you still have root (personal preference)...
Then re-loading the original bootloader (we don't need the modified one anymore!) via Odin...
Then we are done!
The steps in the how to are very precise and accurate. If you would like to PM me, I am available for another hour or so.
OverkillSD said:
The original bootloader is locked and doesn't allow for us to use the exploit to install SuperSU and root the phone.
We are installing the unlocked bootloader via Odin...
Then running motochopper to exploit a vulnerability to gain root...
Then MANUALLY (this can't happen automagically) opening SuperSU and updating the SU binary...
Then rebooting the phone to make sure you still have root (personal preference)...
Then re-loading the original bootloader (we don't need the modified one anymore!) via Odin...
Then we are done!
The steps in the how to are very precise and accurate. If you would like to PM me, I am available for another hour or so.
Click to expand...
Click to collapse
Well said. Only correction is the bootloader still remains locked. The recoveries included are loki patched. This bypasses the bootloader. All roms and kernels are loki patched so flashing them is safe. This is as close as we're gonna get to an unlocked bootloader for now.
Ah. I was under the impression the bootloader was unlocked. Thanks for the info.
I'm getting an error in Odin: "Cannot open serial port." I have debugger mode enabled and whatnot, any help?
dabs delicious said:
I'm getting an error in Odin: "Cannot open serial port." I have debugger mode enabled and whatnot, any help?
Click to expand...
Click to collapse
I am also coming up with this error. My computer says that device is not responding. I am a first time "rooter" but I read the instructions carefully and now im stuck.....any suggestions?
chrisxstyle1182 said:
I am also coming up with this error. My computer says that device is not responding. I am a first time "rooter" but I read the instructions carefully and now im stuck.....any suggestions?
Click to expand...
Click to collapse
Could be a couple of things first make sure your using the cable that came with your phone. Try switching usb ports. Alsi try rebooting your pc

Samsung Galaxy S3 can't flash recovery

Have a Verizon SCH-I535 running android 4.4.2 I have been trying in vain for two days now to root this phone and replace the stock recovery. I'm aiming for running clockworkmod recovery and cyanogenmod. I've followed their instructions using terminal and heimdall which DOES WORK and communicate with device.
Problem is EVERY TIME I boot to recovery and try to run anything...a stock zip to downgrade it says "failed to verify whole-file signature" and "signature verification failed."
The only thing I can do is run towelroot.apk, install superSU.apk, and use the stock ROM. Using ODIN is a waste of time and fails every file every time. At this point I'm honestly kinda amazed I don't have a brick I've done so many transfers! I also always wipe data/cache before I install zips off SDcard.
I'm out of answers. Oh! At one point my counter was too high and it was also saying, "System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help. " I downloaded TriangleAway and it reset the counter back to zero and the error went away, but there for a while I couldn't even get to recovery (take battery out and cancel out of download mode FYI to boot back into device).
Samsung Kies is the closest glimmer of hope I've gotten. Twice now it has returned my phone back to stock; so I don't think its a hardware issue ie. bad ram or ROM memory...
I've rooted a couple older Galaxy S3's running 4.3 with no issue. It's been a couple years but that was a simple ODIN flash and I kept standard ROM/recovery as I was flashing carriers and didn't want to risk breaking anything.
I'd like to think I'm not an idiot, but what the hell am I missing. I've watched dozens of youtube videos and read hundreds of guides that all seem to work. It's something with this phone and kies or some type of heightened security...
Thanks in advance! You can also email me at [email protected]
Anyone? Even a, "Yeah, that's weird man! Sounds like you did everything right!" Would make me feel better...
Yes I've tried it and it worked make sure u have the unofficial safestrap the one for your phone and do the busy box and terminal emulator thing and it works if you try to install safestrap without the other things you will brick I did it twice but it very easy to unbrick so download busybox terminal emulator and the correct safestrap for you device and also I'm on 4.4.2 also and there is only one rom i have found that works and its called superliter there ya go hope I help would provide download links but I'm not home
Also I forgot to mention your bootloader won't be unlocked it'll be bypassed and you will have a custom recovery
androidforums.com/threads/verizon-verizon-bootloader-unlock.856221/page-2[/url]
forum.xda-developers.com/showthread.php?t=2605648
device specific safestrap recovery and image
4.4.2 has a 'locked bootloader' courtesy of Verizon! This is what has been giving me fits... Going to try to go back to totally stock 4.4.2 (right not my bootloader is the international version and locked out), then towelroot to root, then install root explorer/supersu, then I'll try safestrap and hopefully its the miracle cure!
schmitey said:
Have a Verizon SCH-I535 running android 4.4.2 I have been trying in vain for two days now to root this phone and replace the stock recovery. I'm aiming for running clockworkmod recovery and cyanogenmod. I've followed their instructions using terminal and heimdall which DOES WORK and communicate with device.
Problem is EVERY TIME I boot to recovery and try to run anything...a stock zip to downgrade it says "failed to verify whole-file signature" and "signature verification failed."
The only thing I can do is run towelroot.apk, install superSU.apk, and use the stock ROM. Using ODIN is a waste of time and fails every file every time. At this point I'm honestly kinda amazed I don't have a brick I've done so many transfers! I also always wipe data/cache before I install zips off SDcard.
I'm out of answers. Oh! At one point my counter was too high and it was also saying, "System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help. " I downloaded TriangleAway and it reset the counter back to zero and the error went away, but there for a while I couldn't even get to recovery (take battery out and cancel out of download mode FYI to boot back into device).
Samsung Kies is the closest glimmer of hope I've gotten. Twice now it has returned my phone back to stock; so I don't think its a hardware issue ie. bad ram or ROM memory...
I've rooted a couple older Galaxy S3's running 4.3 with no issue. It's been a couple years but that was a simple ODIN flash and I kept standard ROM/recovery as I was flashing carriers and didn't want to risk breaking anything.
I'd like to think I'm not an idiot, but what the hell am I missing. I've watched dozens of youtube videos and read hundreds of guides that all seem to work. It's something with this phone and kies or some type of heightened security...
Thanks in advance! You can also email me at [email protected]
Click to expand...
Click to collapse
Verizon spends a pretty penny when it comes to making sure their devices................. stay theirs i guess you can say when it comes to the boot-loader! To my knowledge their isn't a way of getting around that with a permanent recovery flash that completely replaces Verizon's stock recovery. I can almost guaranteeing you that your problem is Verizon locked boot loader. Stock recoveries are solely only their for their technicians, so unless someone somehow has leaked a program that they use to get around that stuff without screwing it up, we the general public will never be able to flash anything permanent with any phones stock recovery unless we have their "secret" software! Every once in a while you do find a leaked one. I got lucky and found one for the T-mobile galaxy S6 Edge. As far as Odin I've noticed that the new versions seem to be very particular. Meaning if a dot or a space is misplaced anywhere in the zip or what not it will always fail. With my t-mobile S6 I spent two days figuring out I had to take a letter out of the name of the file i was trying to Odin. One letter that was it and once I did that it went flawlessly. Otherwise man i really don't know what to tell you, seems like ya followed the lines as described. Just remember its a Samsung Galaxy in my opinion Galaxies are unbrickable. Ive even pulled the cord in the middle of a Odin flash to see if i could brick it for good and was still able to go right into download mode and flash stock back onto it and everything working. So don't be afraid of bricking it. It will be way easier (sorry to say) for you to re-flash stock right now! Good luck bro wish you the best!
---------- Post added at 08:25 PM ---------- Previous post was at 08:18 PM ----------
schmitey said:
4.4.2 has a 'locked bootloader' courtesy of Verizon! This is what has been giving me fits... Going to try to go back to totally stock 4.4.2 (right not my bootloader is the international version and locked out), then towelroot to root, then install root explorer/supersu, then I'll try safestrap and hopefully its the miracle cure!
Click to expand...
Click to collapse
Are you able to disable Signature verification in the recovery?
Are you able to disable Signature verification in the recovery?
You can once I flash to say clockworkmod recovery. Stock I don't know of a way to...hence the Catch 22 there's no going forward and no going back...you're stuck with stock ROM/recovery but at least its rooted.
Well ****. Take my word for it you CAN brick a galaxy s3.
I used KIES to restore back to factory stock recovery etc etc.
I then used towelroot to root phone and install supersu. I then installed safestrap which totally worked! I was able to bypass the stock recovery and everything was running smoothly...I got overzealous and tried to install the cyanogenmod vrale6 bootloader zip through safestrap. I currently have a brick. It won't boot, no led's, no screen, no vibrate. I have another galaxy s3 charging batteries and swapped it out...removed sim and micro sd. I should have just installed the cyanogenmod app and done it that way...
So close and now I bricked it...
OK got my brick back by writing image to microSD card...pretty happy about that little trick. And that's utter nonsense about needing the same size card as your internal memory! I used a 32gig card on a 16gig phone...
Still trying but this locked 4.4.2 bootloader is BULL****. Going to try to downgrade but I'm not sure I'm going to end up with anything but a rooted stock rom...
So does anyone know of a way to downgrade or change recovery on Verizon 4.4.2?
I have s3 Verizon I-535 & clockworkmod recovery is not gonna work cuz of the locked bootloader, I used safestrap that's the only recovery for 4.4.2
slimcyril said:
I have s3 Verizon I-535 & clockworkmod recovery is not gonna work cuz of the locked bootloader, I used safestrap that's the only recovery for 4.4.2
Click to expand...
Click to collapse
Thanks for the reply. But with safestrap its a step in the right direction but every zip fails...so I don't see what it really does for us. Don't see myself ever running cyanogenmod at this rate unless you know something I don't...
schmitey said:
Thanks for the reply. But with safestrap its a step in the right direction but every zip fails...so I don't see what it really does for us. Don't see myself ever running cyanogenmod at this rate unless you know something I don't...
Click to expand...
Click to collapse
Well no zip has ever failed on my end using safestrap, does your device have init.d support?
No point me to it! I'm basically stock rom running safestrap atm. If you can walk me through this I'd be grateful.. Just remember I'm locked Verizon bootloader...
And may I say I finally got the I535 switched to selectel (was on a flashed sprint L710) and holy cow 4G LTE is fast...faster than my home internet!
schmitey said:
No point me to it! I'm basically stock rom running safestrap atm. If you can walk me through this I'd be grateful.. Just remember I'm locked Verizon bootloader...
And may I say I finally got the I535 switched to selectel (was on a flashed sprint L710) and holy cow 4G LTE is fast...faster than my home internet!
Click to expand...
Click to collapse
Go to mount on safestrap & see if your system partition is checked(mounted) e.t.c & go to playstore install universal init.d app
Note; uncheck verify signature checks if you're trying flash anything via recovery or else it will definitely fail
slimcyril said:
Go to mount on safestrap & see if your system partition is checked(mounted) e.t.c & go to playstore install universal init.d app
Note; uncheck verify signature checks if you're trying flash anything via recovery or else it will definitely fail
Click to expand...
Click to collapse
system partition is NOT checked within safestrap. Installed universal init.d but I'm out of my league on it... Init.d says stock kernel does not have support...

Samsung S5 Active G870A Softbricked - Need stock 5.1.1 kernel or help with recovery

Hi all-
Thanks for the awesome wealth of information-this forum has helped me out more times than I can count! So, I pulled a bonehead move yesterday with my new (to me) AT&T S5 Active - I'm fairly familiar with using Odin and read what I later found to be the outdated root method and unfortunately soft bricked my phone...I started out with a totally stock phone and followed the instructions here - http://forum.xda-developers.com/showthread.php?t=2799754 - to try to downgrade my phone from the most current 5.1.1 PB5 firmware to NE4 in order to use Towelroot. As I did more research I found that the later 5.1 updates prevent downgrading...Odin still allowed me to push the NE4 firmware but now my phone only boots into recovery. I've tried a number of .zip recoveries and later (but not PB5) kernels through Odin but I either get kernel mismatch or other errors and can't get it to boot. Now that I know this phone can't be rooted (which seems crazy to me...thanks Samsung!) I'm just wanting to get it back to stock so I can give it to my Dad and get him off of his Lumia - does anyone have a stock ROM that would work or any ideas how to get back up and running? I'm not finding any newer firmware out there and any help would be appreciated. Thanks!
yamaholic said:
Hi all-
Thanks for the awesome wealth of information-this forum has helped me out more times than I can count! So, I pulled a bonehead move yesterday with my new (to me) AT&T S5 Active - I'm fairly familiar with using Odin and read what I later found to be the outdated root method and unfortunately soft bricked my phone...I started out with a totally stock phone and followed the instructions here - http://forum.xda-developers.com/showthread.php?t=2799754 - to try to downgrade my phone from the most current 5.1.1 PB5 firmware to NE4 in order to use Towelroot. As I did more research I found that the later 5.1 updates prevent downgrading...Odin still allowed me to push the NE4 firmware but now my phone only boots into recovery. I've tried a number of .zip recoveries and later (but not PB5) kernels through Odin but I either get kernel mismatch or other errors and can't get it to boot. Now that I know this phone can't be rooted (which seems crazy to me...thanks Samsung!) I'm just wanting to get it back to stock so I can give it to my Dad and get him off of his Lumia - does anyone have a stock ROM that would work or any ideas how to get back up and running? I'm not finding any newer firmware out there and any help would be appreciated. Thanks!
Click to expand...
Click to collapse
Do you have adb on your computer? If not download it, if you do, boot to recovery and hit "apply update from adb". Now, assuming you are familiar with adb and it's commands, adb sideoload it. If that doesn't work do the Odin thing again and make sure your device is in download mode and after the flash is complete you will have to wipe data/factory in recovery otherwise you'd be stuck in a bootloop.
RAZERZDAHACKER said:
Do you have adb on your computer? If not download it, if you do, boot to recovery and hit "apply update from adb". Now, assuming you are familiar with adb and it's commands, adb sideoload it. If that doesn't work do the Odin thing again and make sure your device is in download mode and after the flash is complete you will have to wipe data/factory in recovery otherwise you'd be stuck in a bootloop.
Click to expand...
Click to collapse
Hi RAZERZDAHACKER - Thanks for the reply - yeah, unfortunately tried that and all I'm getting is 'E:footer is wrong E:signature verification failed' errors...it's the same whether I try to apply any of the ROM .zips I have via ADB or from the SD card. I'm guessing I need a matching version ROM to the PB5 that I had? I've looked but I can't find a download for it anywhere since it's only a few weeks old...I'd just throw in the towel and bring it to the AT&T service center (as much as I hate the thought of it) if it wasn't about a 6 hour round trip for me.
I can see the pain for a 6hr trip + you are lucky if they even will accept it since you tamper with device. Have you looked at this thread? It might help you.
---------- Post added at 10:07 AM ---------- Previous post was at 10:01 AM ----------
I think I have the solution!! Remove battery for 5min and boot into download mode and flash via odin! If that didn't work, report the odin log.

Is there a root for the J106M Galaxy mini prime?

Hi, everyone. I've successfully rooted several Android phones in the past, but this one's got me stumped. Has anyone successfully rooted this specific model, and if so, how?
I have a J1 mini prime, specifically a J106M. It is running Marshmallow 6.0.1 with a pending update that I've paused. I was under the impression the bootloader would be unlocked since it's not tied to a carrier. I now assume it isn't because I've tried:
kingoroot, kingroot, iRoot, towelroot (doesn't work with modstring codes either), latest framaroot (device not vulnerable to exploits error), framaroot 1.5.3 (same error), chainfire (causes soft brick bootloop, but has since been restored).
I can't even figure out how to verify if the bootloader is unlocked for sure. I tried using ADB. cd fastboot command simplay restarts the phone, and fastboot oem unlock command my phone or just sits there saying "waiting for device."
When I boot the phone holding down the volume, home, and power buttons, it brings me to a blue screen that I believe is Odin mode. Others seem to get a different screen that has the bootloader info right there.
It's been a few weeks since I've had time to mess with this. I'm pretty sure that's everything I attempted.
To verify, I have developer mode on, OEM unlocking on, debugging on, allow unknown sources on.
Other specs:
Baseband version : J106MUBU0AQF1
Kernel: 3.10.65-11653963
Build: MMB29Q_J106MUBU0AQF2
Thanks in advance to anyone who can assist a semi-noob. I've never posted on a forum before, and I'm not usually one to ask for help, but I'm out of ideas here lol.
Hello Bahamut,
Are you familar with the Odin tool flashing Samsung firmware? If yes, there is a universal root method Magisk root. There are two ways to root using Magisk:
1. install a TWRP recovery (flash by Odin) & install Magisk Root using TWRP recovery
2. Extract boot.img from the firmware; modify it by Magisk apk; flash the modified img by Odin.
Both ways successfully rooted my Samsung J3 Pro. I've google search for a while & see firmware/TWRP are available for your device J106M.
You should study Odin, Magisk before you go ahead.
Thanks. Somewhat familiar, I was saving that as a last resort out of apprehension that I completely brick the device lol I used Odin when attempting the chainfire files.
I forgot I had downloaded TWRP at one point, but I must be missing something because it appears to be a catch 22 as TWRP was asking for root access in the first place to perform this function. Is there a work around such as using a PC version instead of the app or am I just way off base here?
If TWRP recovery has a problem, you could try method 2 which involve Odin flashing only.
chankk0101 said:
If TWRP recovery has a problem, you could try method 2 which involve Odin flashing only.
Click to expand...
Click to collapse
Unfortunately, the Odin flashing is how I wound up soft-bricking it twice and decided I'd need assistance on this model. I was hoping someone could walk me through it with the specifics, but I guess this isn't a very popular phone.:

Unlocking/rooting an A21?

I have a brand new Galaxy A21 (SM-S215DL). In Developer Options, there is NO OEM Unlock toggle (not even a grayed out one; it simply does NOT exist anywhere in settings). I have tried several different variants of the date/time trick to try to get it to appear, and none of them worked. But while in Download Mode, KG Status is shown as `CHECKING`, so doesn't that mean it should at least be visible? Do I even need to unlock my bootloader? Is it even possible?
Using Frija, I managed to get what I believe to be the correct stock firmware for my device. I also grabbed both of the latest official and patched versions of Odin. Flashing the stock firmware works, but flashing the patched Magisk AP fails with an AUTH error for file `vbmeta.img`, which leads me to believe that I actually DO need to unlock my bootloader... but if that's the case, I'm having trouble figuring out how to do so without the OEM toggle.
Is there anything else can I try?
SpectreCular said:
I have a brand new Galaxy A21 (SM-S215DL). In Developer Options, there is NO OEM Unlock toggle (not even a grayed out one; it simply does NOT exist anywhere in settings). I have tried several different variants of the date/time trick to try to get it to appear, and none of them worked. But while in Download Mode, KG Status is shown as `CHECKING`, so doesn't that mean it should at least be visible? Do I even need to unlock my bootloader? Is it even possible?
Using Frija, I managed to get what I believe to be the correct stock firmware for my device. I also grabbed both of the latest official and patched versions of Odin. Flashing the stock firmware works, but flashing the patched Magisk AP fails with an AUTH error for file `vbmeta.img`, which leads me to believe that I actually DO need to unlock my bootloader... but if that's the case, I'm having trouble figuring out how to do so without the OEM toggle.
Is there anything else can I try?
Click to expand...
Click to collapse
I also have the Samsung A21 from T Mobile (SM-A21UZKATMB). The phone is unlocked by T Mobile but there is no OEM bootloader unlock button under the Developer mode. Changing the date (forward and backward in time), then run the software update did not solve the OEM bootloader unlock button problem. I suspect the carrier (T Mobile) has disabled this function. You will need to unlock the bootloader to install the stock firmware.
To those who have enabled the OEM bootloader in the A21. Is your phone locked to a carrier in the USA like Verizon or T Mobile?
I also have the SM215DL, using straight talk utilizing verizon service, I also cannot unlock the bootloader. Everything you guys did, I did. Nothing worked.
samsung has done this to all A series phones intended for the U.S. from what i understand
Where there's a will, there's a way... someone has messed with my phone too do doesn't that mean that they're altering the data/data partition to r/w. Did you guys try fastboot flashing unlock vs. fastboot oem unlock. I'm going to contact Samsung about this and let u all know what's up.
And also why would there be a usb debugging port if this phone can't be modded? Idon't know the answer but maybe someone more expediency could come in and help us out. I also wonder if the flash_image command or just dd it would bypass it?
... there is NO way, to root the A21(s), see here: https://forum.xda-developers.com/t/root-possibility.4130739/page-12#post-84944589
MaBo2020 said:
... there is NO way, to root the A21(s), see here: https://forum.xda-developers.com/t/root-possibility.4130739/page-12#post-84944589
Click to expand...
Click to collapse
I confirm that I have rooted my A21S sucessfully using this modified magisk (U3 Rom). No need to patch the whole AP.tar file, just patch boot.img file only. I upload my patched boot.img for those who need it. Just flash it via odin in AP slot. Thank you very much @grccorps.
https://forum.xda-developers.com/attachments/boot-tar.5299081/
thatha said:
I confirm that I have rooted my A21S sucessfully using this modified magisk (U3 Rom). No need to patch the whole AP.tar file, just patch boot.img file only. I upload my patched boot.img for those who need it. Just flash it via odin in AP slot. Thank you very much @grccorps.
https://forum.xda-developers.com/attachments/boot-tar.5299081/
Click to expand...
Click to collapse
... exactly Step-by-Step, how u do it with downloadlinks of all Software, what u used !
Many Peoples writes, that they have rooted the A21s, but no one shows, how ! With the newest Firmware u cant rooted the Phone, because there is no working TWRP, SuperSU or MAGISK - Version out for this Phone !
MaBo2020 said:
... exactly Step-by-Step, how u do it with downloadlinks of all Software, what u used !
Many Peoples writes, that they have rooted the A21s, but no one shows, how ! With the newest Firmware u cant rooted the Phone, because there is no working TWRP, SuperSU or MAGISK - Version out for this Phone !
Click to expand...
Click to collapse
Extract boot.img from AP.tar, then use modified-magisk to patched it
... this Methode is not working, i try it many Times, no RootAcess ! Again: if u have newer Firmware on this Phone (End 2020 - until now) u cant root this Phone ! Maybe on ure Phone an older Firmware ...
And this is my U5 patched boot.img
MaBo2020 said:
... this Methode is not working, i try it many Times, no RootAcess ! Again: if u have newer Firmware on this Phone (End 2020 - until now) u cant root this Phone ! Maybe on ure Phone an older Firmware ...
Click to expand...
Click to collapse
I have just made a post here, you can try it
[SHARING] HOW TO ROOT A21S STOCK ROM WITH MAGISK
Hello friends I just want to share how to root A21S stock rom in case anybody needs it: 1. Unlock bootloader 2. (On PC) Extract boot.img.lz4 from AP...tar file, then copy it to phone 3. (On phone) Install ZArchiver to extract boot.img from...
forum.xda-developers.com
... and u shure, it its for the A21s or for A21 ?
The only hope of getting root on this phone is if you find a Dev who's interested enough to build a bootstrap recovery. I've not looked at the firmware & have no idea if there's an exploit that would work for that purpose.
Bootstrap recovery was the only way of getting root/custom recovery back in the days of Motorola D2 & Droid X, the original Droid X. Motorola was THE phone for development... Liberty ROM, Gummy ROM, Simply Stunning, etc.
I would not hold out hopes for that to happen here.
Peace - MS
Seriousfreedom said:
samsung has done this to all A series phones intended for the U.S. from what i understand
Click to expand...
Click to collapse
No, Samsung has done this to ALL North American models ever since the Galaxy S8. The bootloaders are not user-unlockable, like they are on international models. However, some models can be rooted via a software exploit if they're running very old firmware, or some models can even be bootloader unlocked via special files, if their firmware version is old enough
SpectreCular said:
I have a brand new Galaxy A21 (SM-S215DL). In Developer Options, there is NO OEM Unlock toggle (not even a grayed out one; it simply does NOT exist anywhere in settings). I have tried several different variants of the date/time trick to try to get it to appear, and none of them worked. But while in Download Mode, KG Status is shown as `CHECKING`, so doesn't that mean it should at least be visible? Do I even need to unlock my bootloader? Is it even possible?
Using Frija, I managed to get what I believe to be the correct stock firmware for my device. I also grabbed both of the latest official and patched versions of Odin. Flashing the stock firmware works, but flashing the patched Magisk AP fails with an AUTH error for file `vbmeta.img`, which leads me to believe that I actually DO need to unlock my bootloader... but if that's the case, I'm having trouble figuring out how to do so without the OEM toggle.
Is there anything else can I try?
Click to expand...
Click to collapse
Mine is rooted. But you have to buy a token.
o.class.jav said:
Mine is rooted. But you have to buy a token.
Click to expand...
Click to collapse
what token??
[email protected] said:
what token??
Click to expand...
Click to collapse
The one generated by the SamPwns steady.bin flash.
{Mod edit: Quoted post removed}
and where does one get 'TWRP' for the Samsung Galaxy A21S?? Thanks for the post its very detailed with very clear instructions, and i agree with you this is the tried and tested and perfect way of rooting your phone, only problem is that this is an unperect world a world where 'TWRP' for the SM-A217F does not exist
I just received a refurbished SM-S215DL (A21,) not as my provider's solution to the VoLTE soon to be required for 4G devices thing and right now it's a pretty severe downgrade for me since it lacks a lot of basic functionality I'm used to from my 2017 phone running LineageOS. Obviously it's pretty unlikely or probably outright impossible to ever see a real LineageOS ROM for this thing (and even if someone ever does it probably would be insanely unstable or incomplete,) but if I could at least root it (even if I have to manually patch or something) it would really help me out a lot. Has just nothing really been found short of sending some unknown person online some very very key device details and money (which I don't have or I'd be buying something else anyway)? (Also kind of suspicious that whatever method they're using isn't something available to the public anyway...)

Categories

Resources