Related
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
I recently installed the update 4.3 for my phone, which blocked the only thing I use the phone for free HOTSPOT. I tried to go back to 4.1.2 and obviously messed up somewhere along the way. Presently I can boot to download screen and recovery, but NOTHING works. Anything I try to install I get an error message. Currently, when I try to boot I get "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." Don't want to do that, since they already told me they will not revert back to previous software version.
I have Odin 3.09 installed, USB driver for my phone installed and downloaded multiple tar and md5 files that are the correct ones for my phone. When I try to install I get FAILED! every time. I am putting it in the PDA slot, with proper check marks.
Please help me, I will give additional details as you see fit, don't want to clog up the thread with everything I tried, like unlocking bootloader, installing custom recovery, etc.
I'll be here all day, hopefully I can get some quick responses.
duffycoug said:
I recently installed the update 4.3 for my phone, which blocked the only thing I use the phone for free HOTSPOT. I tried to go back to 4.1.2 and obviously messed up somewhere along the way. Presently I can boot to download screen and recovery, but NOTHING works. Anything I try to install I get an error message. Currently, when I try to boot I get "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." Don't want to do that, since they already told me they will not revert back to previous software version.
I have Odin 3.09 installed, USB driver for my phone installed and downloaded multiple tar and md5 files that are the correct ones for my phone. When I try to install I get FAILED! every time. I am putting it in the PDA slot, with proper check marks.
Please help me, I will give additional details as you see fit, don't want to clog up the thread with everything I tried, like unlocking bootloader, installing custom recovery, etc.
I'll be here all day, hopefully I can get some quick responses.
Click to expand...
Click to collapse
63 views but no replies? Maybe I'm in the wrong place? Is there anyone here who can help or point me to another forum?
duffycoug said:
63 views but no replies? Maybe I'm in the wrong place? Is there anyone here who can help or point me to another forum?
Click to expand...
Click to collapse
This is a GS3 correct? Did you unlock the bootloader? if you didn't unlock the bootloader then you will get this message. I had the same issue with my girlfriends SGS3 on verizon.
I followed the EXACT directions that were posted...if flashing VRALEC bootchain unlocks the bootloader than yes. I followed them step by step.
The good news is though, I finally gave up and hit accept on the software update and figured I'd just pay the extra $20 for the hotspot that was free on 4.1.2, but to my surprise the update failed. I still have my 4.1.2, my free hotspot and everything functions. Whatever I did messed up my phone enough to block the update, so I'm happy. Pretty crazy though that the methods followed to the T didn't work over and over again. I simply cannot root my phone no matter what I try. I'd love for someone to physically have my phone and try it with me present.
duffycoug said:
I recently installed the update 4.3 for my phone, which blocked the only thing I use the phone for free HOTSPOT. I tried to go back to 4.1.2 and obviously messed up somewhere along the way. Presently I can boot to download screen and recovery, but NOTHING works. Anything I try to install I get an error message. Currently, when I try to boot I get "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." Don't want to do that, since they already told me they will not revert back to previous software version.
I have Odin 3.09 installed, USB driver for my phone installed and downloaded multiple tar and md5 files that are the correct ones for my phone. When I try to install I get FAILED! every time. I am putting it in the PDA slot, with proper check marks.
Please help me, I will give additional details as you see fit, don't want to clog up the thread with everything I tried, like unlocking bootloader, installing custom recovery, etc.
I'll be here all day, hopefully I can get some quick responses.
Click to expand...
Click to collapse
give this a shot for verizon s3: http://forum.xda-developers.com/showthread.php?t=2581166. It will provide you with directions on how to flash the stock recovery and bootloader. My S3 would not turn on at all until I tried this method.
I was simply messing around with my old Verizon GN2, because I need a phone to use in the absence of my htc one M9. I went to flash the "stock" version of the bootloader (the bootloaderbaseline2.tar) before I went in to do any real damage and the phone rejected it. The phone screen read the error message "wrong magic string" and the odin display reported that it dropped out after sboot.bin. Just curious whether you guys and your wisdom would have any insight in the matter? I would really prefer not to have to go out and buy another phone.
Also, woohoo for a first post on the forums.
Cordially,
Nixon
logannixon.la said:
I was simply messing around with my old Verizon GN2, because I need a phone to use in the absence of my htc one M9. I went to flash the "stock" version of the bootloader (the bootloaderbaseline2.tar) before I went in to do any real damage and the phone rejected it. The phone screen read the error message "wrong magic string" and the odin display reported that it dropped out after sboot.bin. Just curious whether you guys and your wisdom would have any insight in the matter? I would really prefer not to have to go out and buy another phone.
Also, woohoo for a first post on the forums.
Cordially,
Nixon
Click to expand...
Click to collapse
Are you flashing the full firmware or just bootloader? What options did you have checked and where (in what slot, PDA?) did you put the file to run it? What version are you on, 4.4.2; 4.3? Have you unlocked it before?
bigmike35 said:
Are you flashing the full firmware or just bootloader? What options did you have checked and where (in what slot, PDA?) did you put the file to run it? What version are you on, 4.4.2; 4.3? Have you unlocked it before?
Click to expand...
Click to collapse
I had this phone rooted before, but it wasn't playing well with what my sister wanted it for. So, I flashed a stock image and it rebooted into its stock form. That was two ish years ago. The bootloader was never unlocked. When I brought it back out to begin tinkering, a lot of guides said to flash the stock bootloader (the bootloaderbaseline2 file) and to repartition it before going ahead with something like CASUAL. Considering my sister used it as a daily driver for quite a while, it was probably on 4.3 or whatever the last update Verizon handed out was. I do remember checking to see whether or not it had any available updates and it said it was completely up to date. When I set it up to repartition and flash the BB2 file, it was in the bootloader slot. The Odin flash then failed at the sboot.bin output and the phone proceeded to slide into the good old "connect to Kies" screen. I tried several attempts to get the BB2 file to stick (putting it in all the slots and trying it without partition and auto reboot), but all were to no avail. I have since flashed multiple firmwares in the PDA slot with only the root66_vzw_stock_system.tar.md5 version completing. However, it now displays the "Device firmware is not from verizon. Please bring it into a Verizon store for help." I know the verizon reps will be useless, so I asked you beautiful people.
The only odin boxes that I played with were the top three.
Also, thanks for responding. I appreciate it.
Nixon
logannixon.la said:
I had this phone rooted before, but it wasn't playing well with what my sister wanted it for. So, I flashed a stock image and it rebooted into its stock form. That was two ish years ago. The bootloader was never unlocked. When I brought it back out to begin tinkering, a lot of guides said to flash the stock bootloader (the bootloaderbaseline2 file) and to repartition it before going ahead with something like CASUAL. Considering my sister used it as a daily driver for quite a while, it was probably on 4.3 or whatever the last update Verizon handed out was. I do remember checking to see whether or not it had any available updates and it said it was completely up to date. When I set it up to repartition and flash the BB2 file, it was in the bootloader slot. The Odin flash then failed at the sboot.bin output and the phone proceeded to slide into the good old "connect to Kies" screen. I tried several attempts to get the BB2 file to stick (putting it in all the slots and trying it without partition and auto reboot), but all were to no avail. I have since flashed multiple firmwares in the PDA slot with only the root66_vzw_stock_system.tar.md5 version completing. However, it now displays the "Device firmware is not from verizon. Please bring it into a Verizon store for help." I know the verizon reps will be useless, so I asked you beautiful people.
The only odin boxes that I played with were the top three.
Also, thanks for responding. I appreciate it.
Nixon
Click to expand...
Click to collapse
So it it on 4.4.2 then since all updates are up to date? If that is the case, you can only root using towel root. You can downgrade to 4.3 or 4.2.1 but you would need to send it in ($75) i believe or try the method here that is posted. If it is still on 4.3 i believe you can flash the 4.2.1 firmware and then run root running casual (disable firewall and antim virus else wont complete). Then find Beanstown thread and download the zip for the updated wifi/bootloader for 4.3 with ND7 radio (zip somewhere as well) to upgrade completely to newest radio/images (so it would be a 4.2.1 or 4.3 stock with complete root and unlocked). Then install TWRP and roms
bigmike35 said:
So it it on 4.4.2 then since all updates are up to date? If that is the case, you can only root using towel root. You can downgrade to 4.3 or 4.2.1 but you would need to send it in ($75) i believe or try the method here that is posted. If it is still on 4.3 i believe you can flash the 4.2.1 firmware and then run root running casual (disable firewall and antim virus else wont complete). Then find Beanstown thread and download the zip for the updated wifi/bootloader for 4.3 with ND7 radio (zip somewhere as well) to upgrade completely to newest radio/images (so it would be a 4.2.1 or 4.3 stock with complete root and unlocked). Then install TWRP and roms
Click to expand...
Click to collapse
So, for the moment, is there any way to get it back to stock? I was trying to go the custom recovery route in the beginning, but I now just need a phone that works. I'm pretty sure it's the bootloader firmware that is preventing the device from booting completely. Thanks for all your help.
Nixon
logannixon.la said:
So, for the moment, is there any way to get it back to stock? I was trying to go the custom recovery route in the beginning, but I now just need a phone that works. I'm pretty sure it's the bootloader firmware that is preventing the device from booting completely. Thanks for all your help.
Nixon
Click to expand...
Click to collapse
You can see if you can flash the full Verizon firmware. Should be able to find it here or on Samsungs website.
bigmike35 said:
You can see if you can flash the full Verizon firmware. Should be able to find it here or on Samsungs website.
Click to expand...
Click to collapse
So the stock Verizon firmware will repair the broken bootloader? I'll give it a go. Thanks for the info.
Just a quick update. I flashed the stock firmware for 4.4.2 and everything went over swimmingly. The phone now boots all the way into the Verizon boot splash screen. It then sits there and will not progress. I've tried wiping cache and factory resetting, but it still hangs on the Verizon splash screen. Any pointers?
Thanks again,
Nixon
Another side update. It's still held up on the Verizon boot splash screen, but the led is now pulsing. *Shrugs in confusion
Nixon
logannixon.la said:
Another side update. It's still held up on the Verizon boot splash screen, but the led is now pulsing. *Shrugs in confusion
Nixon
Click to expand...
Click to collapse
Ya i have had that issue before, but I did what you did is to wipe cache, data, factory and that normal let me get a full boot in.
bigmike35 said:
Ya i have had that issue before, but I did what you did is to wipe cache, data, factory and that normal let me get a full boot in.
Click to expand...
Click to collapse
Yeah, I've tried the factory reset and wipe cache, it still gets caught in the Verizon boot loop. I'm not particularly sure what that else to do. The 4.4.2 stock md5 is the only one that will stick in Odin.
logannixon.la said:
Yeah, I've tried the factory reset and wipe cache, it still gets caught in the Verizon boot loop. I'm not particularly sure what that else to do. The 4.4.2 stock md5 is the only one that will stick in Odin.
Click to expand...
Click to collapse
are you flashing it with the PIT file as well?
bigmike35 said:
are you flashing it with the PIT file as well?
Click to expand...
Click to collapse
I think I tried with and without, but I'll give it a shot.
logannixon.la said:
I think I tried with and without, but I'll give it a shot.
Click to expand...
Click to collapse
Ya put that in the PIT tab and firmware in PDA. When it finished, does it say complete or done (box turns green, near top left?)
Also, maybe try another firmware/version?
bigmike35 said:
Ya put that in the PIT tab and firmware in PDA. When it finished, does it say complete or done (box turns green, near top left?)
Also, maybe try another firmware/version?
Click to expand...
Click to collapse
I tried the pit to no avail. Currently wiping again just for fun. Not sure if it helps, but the system recovery screen reads this
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
Samsung Galaxy S4 (SGH-I337) locked at AT&T bootup screen, then I "tried" to fix it..
Well, as the title suggests, I f***ed (Not sure if swearing is allowed...) up my device. I did the upgrade to 5.0.1 and keep root method by another user a while back, then yesterday, Super SU asked if I wanted to disable KNOX, which forgetting that I had a locked device I accepted. The phone died and I saw the issue on bootup. I went to Odin to try to flash the stock firmware back onto it, and that is to no avail. Now I am willing to redo the "keep root" method, but I need to backup my files! I opened Kies 3 with the device set in download mode, and it isn't detecting the device. I've tried both versions of Kies (2.6 & 3) & another 3rd party program.
TL;DR:
I basically need someone to tell me a way to backup my files, or a way to fix this without any data loss!
Thanks
- HyperFirez
Are you able to get into TWRP recovery and make a data backup to your SDcard?
Akti88 said:
Are you able to get into TWRP recovery and make a data backup to your SDcard?
Click to expand...
Click to collapse
Ya see, when they pushed the lollipop update to the phones, AT&T took the opportunity to lock the bootloader as well... So TWRP is a no go. Before the lollipop update, the bootloader was open, and I rooted the device before. I used this method (I'm sure this is on the forums here somewhere, I just can't find it): https://www.sammobile.com/forum/showthread.php?t=26464
This might help you if you can find a way to get into ADB you could do a backup from there http://forums.androidcentral.com/ge...n-can-t-access-recovery-mode.html#post3698554
If you can't get into ADB because of locked bootloader, try: http://www.howtogeek.com/239798/how-to-unlock-your-android-phones-bootloader-the-official-way/
Akti88 said:
This might help you if you can find a way to get into ADB you could do a backup from there http://forums.androidcentral.com/ge...n-can-t-access-recovery-mode.html#post3698554
If you can't get into ADB because of locked bootloader, try: http://www.howtogeek.com/239798/how-to-unlock-your-android-phones-bootloader-the-official-way/
Click to expand...
Click to collapse
I've used that exact guide before, and it doesn't work. AT&T are assholes.
HyperFirez said:
I've used that exact guide before, and it doesn't work. AT&T are assholes.
Click to expand...
Click to collapse
Man I'm sorry to hear that. Hopefully someone with some expertise jumps in this thread to help you out, as I can only suggest things you seem to already be aware of
I'll try to post some more threads that may help, maybe the thread bump will get an expert in here for you.
"Bootloader unlock Galaxy s4 sgh-i337 4.4.2 kitkat" https://forum.xda-developers.com/showthread.php?t=2785166
[Youtube] Install Safestrap Recovery & Custom ROMs on Your Bootloader-Locked Samsung Galaxy S4 [How-To] https://www.youtube.com/watch?v=GqmV8JwO7iY
Akti88 said:
Man I'm sorry to hear that. Hopefully someone with some expertise jumps in this thread to help you out, as I can only suggest things you seem to already be aware of
I'll try to post some more threads that may help, maybe the thread bump will get an expert in here for you.
"Bootloader unlock Galaxy s4 sgh-i337 4.4.2 kitkat" https://forum.xda-developers.com/showthread.php?t=2785166
[Youtube] Install Safestrap Recovery & Custom ROMs on Your Bootloader-Locked Samsung Galaxy S4 [How-To] https://www.youtube.com/watch?v=GqmV8JwO7iY
Click to expand...
Click to collapse
I already re-did the keep root method once more. I just hate that I lost my files...