Related
Hello Everyone,
Firstly, I need to say that as a previous owner of an original droid, I was able to root it with no problems on the first go around. However, as a new owner of a Samsung Galaxy SII I am finding root a real challenge.
I have no problems getting into download mode and so on....I have successfully placed the clockworks rom onto the phone with again no problems and I have all the drivers working properly. I guess this is where I am obviously an idiot....because I start the Super One Click and it gets to Step 6 and then stops. I unplug the USB....click the debugg off and then back on and reconnect my USB like directed by many posters. However, in my case it will not continue on and finish the install.....
I reboot and do get the small triangle on boot up ( not that I care too much about that really...do have a jig on order however) but I simply can't seem to get it to root.
Again I have followed all the posts and guides for unplugging, unchecking and rechecking the debugging and then plug back in the USB and still nothing.
Phone works fine....everything works...love the phone...just seems puzzling to me. I have Odin 1.82, I have SuperOneClick 2.1.1 and like I said installed the .tar fine to the phone with no worries....just cant get it to root.
Any advice?
i used (this) with no issues.
Does your phone currently have the new KJ1 update? I've read that this new update will not root with the usual methods.. (I could also be wrong...)
RE: Rooting
TheElectricalGuru said:
Hello Everyone,
Firstly, I need to say that as a previous owner of an original droid, I was able to root it with no problems on the first go around. However, as a new owner of a Samsung Galaxy SII I am finding root a real challenge.
I have no problems getting into download mode and so on....I have successfully placed the clockworks rom onto the phone with again no problems and I have all the drivers working properly. I guess this is where I am obviously an idiot....because I start the Super One Click and it gets to Step 6 and then stops. I unplug the USB....click the debugg off and then back on and reconnect my USB like directed by many posters. However, in my case it will not continue on and finish the install.....
I reboot and do get the small triangle on boot up ( not that I care too much about that really...do have a jig on order however) but I simply can't seem to get it to root.
Again I have followed all the posts and guides for unplugging, unchecking and rechecking the debugging and then plug back in the USB and still nothing.
Phone works fine....everything works...love the phone...just seems puzzling to me. I have Odin 1.82, I have SuperOneClick 2.1.1 and like I said installed the .tar fine to the phone with no worries....just cant get it to root.
Any advice?
Click to expand...
Click to collapse
Try this rooter "su-3.0-efgh-signed.zip".
Here is the link for it: http://www.megaupload.com/?d=LBTUWW1J
After downloading copy the zipfile to your sdcard and flash it in
CWM recovery just like you would flash a rom using the option
"Install zip from sdcard" in CWM.
When its done reboot the phone and it should be rooted.
Misterjunky said:
Try this rooter "su-3.0-efgh-signed.zip".
Here is the link for it: http://www.megaupload.com/?d=LBTUWW1J
After downloading copy the zipfile to your sdcard and flash it in
CWM recovery just like you would flash a rom using the option
"Install zip from sdcard" in CWM.
When its done reboot the phone and it should be rooted.
Click to expand...
Click to collapse
that file is in the link I posted above...just an FYI.
I tried using the "su-3.0-efgh-signed.zip" and it failed.
I recently purchased a used Galaxy tab 10.1 I/O, and it had already received the 3.1 OTA update.
Now i want root access for various reasons, and can't seem to find a clear guide on how to do so.. I've found plenty about how to do so on the original 3.0 rom, and that it will carry through the 3.1 update, or for the regular version Galaxy Tab 10.1, but it's my understanding the ROMs were fairly different between the I/O and the retail version and that attempting to cross-pollinate root methods may not be a good idea
although I've rooted and ROMed my fair share of HTC devices and Nooks i'm a little more apprehensive with this unit, as it's my first android device to lack an SD card slot of some sort, so bricking seems like a much worse possibility
The best guide ever is in the development section, it works for your device.
http://forum.xda-developers.com/showthread.php?t=1239185
follow the guide its very easy and worked fine for me
I Return triumphant, and gentlemen, i must say you were incorrect.
The I/O edition does not give you the option to access recovery at any point, even with the Pwr+VOL DN boot.
You can put it into download mode, and certianly use ODIN to install the recovery rom, but you will have no method to actually access recovery to push zip files.
thanks to some quick self education on using fastboot, i was able to root successfully.
To those of you in a similar situation who stumble upon this thread, i invite you to visit:
http://droidbasement.com/db-blog/?p=2439
There you can download CWM in a .img format for use with fastboot.
This link is where you can download fastboot:
http://forum.xda-developers.com/attachment.php?attachmentid=596615&d=1305443483
and you'll need to install PDANet for Android to get the fastboot drivers:
http://junefabrics.com/android/
I belive you'll also need ADB installed from the Android SDK. i do have it installed on this computer, but did not use the ADB command at any point, just fastboot.
Instructions:
1. Download fastboot, PDANet for android, and the recovery image. You'll also need "Samsung_Galaxy_Tab_10.1_root.zip" found in Root.zip from the retail version instructions.
2. Copy the "Samsung_Galaxy_Tab_10.1_root.zip" to the tablet, and and power it off. Disconnect the USB connection
3. Unzip fastboot zip into it's own folder, and then copy your recovery.img file into the same folder.
4. Start the install of PDANet. It will ask you if you want to install drivers about half way through. say yes, and select "Samsung" when the time comes. it will install some drivers and then ask you to try and connect. windows may flare up and say they're unsigned. accept anyway.
5. watch this friendly video on how to start fastboot on your tablet:
http://www.youtube.com/watch?v=sR7vE4IueaU
"fastboot!"
Basically the same as the steps outlined for the retail version, but you will go to the usb icon instead of the box.
6. once the tablet is in fastboot, connect the USB cable. PDA net will recognize it as an ADB connection and try and load itself. it will fail, that's fine. Let the installer exit completely.
7. Open a command line in windows, and get it to the directory fastboot.exe and your recovery image are in.
8. run your fastboot command. i only used it temporarlily, so my command was:
"fastboot boot recovery-cwm_5.0.2.7-sam-tab-10.1.img"
9. the tablet should now boot into the recovery image presented. hooray! follow the remaining instructions from the retail version root, using recovery to load the "Samsung_Galaxy_Tab_10.1_root.zip" and reboot.
10. Once you've done all that, select to reboot. The tablet will reboot. i took the opportunity to disconnect the cable.
11. "Superuser" should now be in your apps, and you're rooted!
Extra Step: Download "Rom Manager" by clockwork from the android market, and install it. from here, opt to flash recovery. Once that's complete, you can now access recovery by launching that program and simply hitting "Reboot into Recovery"
I have no use for this myself but it's not often someone comes back and posts a complete howto on solving their own initial issue. I wish more people would do this. Thanks button clicked.
I just ran into this exact problem and only found this thread after figuring it out on my own. I figured my IO tab just didn't like having clockwork mod installed, but it certainly booted it. I nearly ruined it by accidentally wiping my rom trying to get it to boot at all. I had to repush my install files to the insternal memory using adb after I was able to boot into recovery with fastboot.
I haven't looked around too much (seeing as I only JUST got the damn thing to boot a rom) but is there a fix to that, perhaps installing the retail bootloader?
I'd hate to have to use fastboot everytime my rom doesn't boot. I've gotten used to wiping and installing roms from wherever I am on my other android devices.
I'm not familiar enough with the device to be able to give you a definite answer, but i imagine adding a bootloader from the retail version would give you the recovery option instead of fastboot.
personally, i'm a little more fond of having fastboot around right now, as it's easy enough to get into recovery when flashing things with it, and the bootloader for the I/O is unlocked... i can think of a few fun things to do in the future if i can load any ROM i want into memory, test it, and move on if it's no good... i may even give some of the ICS dailies a try thanks to this.
Always several ways of doing things... glad you got it worked out.
http://forum.xda-developers.com/showpost.php?p=15735928&postcount=2
RootzFan,
that method is flashing an entirely new rom, down to 3.0, just to gain root access and open recovery so you can then return to 3.1.. it has the added byproduct of installing touchwiz.
IMHO, my way is a little cleaner as there is actually zero flashing needed, and you get to keep everything active and installed.
i recommend just going for custom roms - it comes already rooted - yBoot into recovery and flash a custom ROM
I have the IO tab myseldf and have been flawlessly running GalaxyTask custom ROM - http://forum.xda-developers.com/showthread.php?t=1340064
shane86 said:
I recently purchased a used Galaxy tab 10.1 I/O, and it had already received the 3.1 OTA update.
Now i want root access for various reasons, and can't seem to find a clear guide on how to do so.. I've found plenty about how to do so on the original 3.0 rom, and that it will carry through the 3.1 update, or for the regular version Galaxy Tab 10.1, but it's my understanding the ROMs were fairly different between the I/O and the retail version and that attempting to cross-pollinate root methods may not be a good idea
although I've rooted and ROMed my fair share of HTC devices and Nooks i'm a little more apprehensive with this unit, as it's my first android device to lack an SD card slot of some sort, so bricking seems like a much worse possibility
Click to expand...
Click to collapse
oh, def not the best method... just saying it is nice that there are alternatives.
self delete
Fun Stuff.
Hello Everyone,
I'm quite new to android so, please pardon me if I say anything wrong.
Here's my story:
I rooted my Galaxy S2 following this video on Youtube.
http://www.youtube.com/watch?v=G3YP5bHo04Y
Rooting was successful, everything went fine. But later in the day, when I connected my phone to my computer, and opened Samsung Kies, it notified me that there's an firmware update. So ofcourse , I updated my firmware.
After updating, I found out that Superuser is gone and I no longer had root access.
So yeah, I tried rooting following the video above again, however, this time it did not work. It says something "permission" errors and It says "Cleaning up" then rebooted my phone.
After my phone rebooted, it says my phone is rooted but when i checked in my phone, it's not. No Superuser, no root access. Tried installing superuser in market, did not work. So here are my current phone details.
Current phone details:
Phone : Samsung Galaxy S2, GT-I9100
Android version : 2.3.6
Baseband Version : I9100DXKL1
Kernel Version: [email protected] #2
Build number : GINGERBREAD.DXKL3
How can I reset this phone completely (unrooted) so that I can root it again ?
i'm new to android os, so yeah, please help !
Thanks,
SotongzXc
Reading the FAQS and GUIDES is a starting point .
ROOT
Root + CWM .
http://forum.xda-developers.com/showthread.php?t=1103399
jje
The easiest would be to download a custom rom to your SD card (I suggest CheckROM RevoHD v6) and one of Chainfire's insecure kernels.
Step one: make sure you know the location of the custom firmware on your phone (it's in a ZIP file)
Step two: flash Chainfire's kernel with ODIN from your PC (now you will have CWM recovery)
Step three: enter recovery on your phone by holding volume up + home + power button. Do the wipes and install the ZIP update
Step four: uninstall KIES and rather install the drivers only (just google Samsung USB drivers 1.4.8.0)
I hope this helps. PM me if you still have issues.
Sent from my GT-I9100 using Tapatalk
You can also retry the method you first used, but do what is called the "RAM crash" method. Load apps on your phone and keep them active (by pressing Home instead of Back) until your phone is using over 500 MB of RAM. (Actual RAM. Not system storage. You may need an app to check this.) Then try that method again.
I have searched multiple threads and sites, however, I still haven't found someone that's had a similar problem to mine, so here it goes.
I have a Samsung Galaxy S III GT-I9300 and the Android version is currently 4.0.4 (More information about my device in the screenshots below)
I've been trying to update it to the latest Android version (Jellybean 4.3 I believe, since Kit Kat 4.4 is not yet available for Samsung Galaxy devices yet). However, whenever I try to do a Software update, it tells me "No update available". Someone suggested that I install the updates through Kies, and I did install Kies on my Mac (OS X 10.9.1), but it won't connect to my phone--as in, it will say "Connecting" for hours without ever connecting to the phone or it will say "Connecting" for a few seconds then tell me to "Please connect a device". I've checked with my phone, and it says "Connected as a media device" with the USB symbol to the left of it. I have also tried to unplug my USB cord, enable USB debugging mode, and plug it back into my Mac to no avail.
The phone is fairly new, I got it a couple of weeks ago from China. I believe that it is rooted since it had to be unlocked to work with US carriers (I'm on T-Mobile network), but at the same time I'm also not quite sure. The phone status says 'Modified', if that helps at all.
SuperSU is installed on my phone (I wasn't the one who installed it), but when I try to access the application, it tells me "There is no SU binary installed, and SuperSU cannot install it. This is a problem!
CWM Manager is also installed (v3.60), but it says "This version of CWM Manager should be used with CF-Root v5.0 or newer. It apepars you are running a different kernel. Various features have been disabled." I don't know what CF-Root is, and I don't think that it's installed on my phone either, since I can't find it in my Application Manager.
I installed an application called RootValidator from the Google Play store, and when I run it, it tells me "No, but you might have root as our request was denied. Did you deny root access? While you don't have a busy box, it is not required to root a device, some apps just need it." (See attachments for more information)
So now my questions are...:
Is my phone actually rooted or not? If it is, how can I grant or deny root access? (I want to download TitaniumBackup, but it requires root access, which I don't know how to give)
Since Kies isn't reading/connecting my device, how can I get Kies to connect to my phone?
And since my phone keeps on telling me "No update available" whenever I try to do a software update, I'm going to assume that I have to update my phone's firmware by using Kies. And if my phone is rooted/unrooted, but I can't connect to Kies, how can I update my Android 4.0.4 to the latest Jellybean 4.3 version?
Thank you for any help you can give!
wohuifei said:
I have searched multiple threads and sites, however, I still haven't found someone that's had a similar problem to mine, so here it goes.
I have a Samsung Galaxy S III GT-I9300 and the Android version is currently 4.0.4 (More information about my device in the screenshots below)
I've been trying to update it to the latest Android version (Jellybean 4.3 I believe, since Kit Kat 4.4 is not yet available for Samsung Galaxy devices yet). However, whenever I try to do a Software update, it tells me "No update available". Someone suggested that I install the updates through Kies, and I did install Kies on my Mac (OS X 10.9.1), but it won't connect to my phone--as in, it will say "Connecting" for hours without ever connecting to the phone or it will say "Connecting" for a few seconds then tell me to "Please connect a device". I've checked with my phone, and it says "Connected as a media device" with the USB symbol to the left of it. I have also tried to unplug my USB cord, enable USB debugging mode, and plug it back into my Mac to no avail.
The phone is fairly new, I got it a couple of weeks ago from China. I believe that it is rooted since it had to be unlocked to work with US carriers (I'm on T-Mobile network), but at the same time I'm also not quite sure. The phone status says 'Modified', if that helps at all.
SuperSU is installed on my phone (I wasn't the one who installed it), but when I try to access the application, it tells me "There is no SU binary installed, and SuperSU cannot install it. This is a problem!
CWM Manager is also installed (v3.60), but it says "This version of CWM Manager should be used with CF-Root v5.0 or newer. It apepars you are running a different kernel. Various features have been disabled." I don't know what CF-Root is, and I don't think that it's installed on my phone either, since I can't find it in my Application Manager.
I installed an application called RootValidator from the Google Play store, and when I run it, it tells me "No, but you might have root as our request was denied. Did you deny root access? While you don't have a busy box, it is not required to root a device, some apps just need it." (See attachments for more information)
So now my questions are...:
Is my phone actually rooted or not? If it is, how can I grant or deny root access? (I want to download TitaniumBackup, but it requires root access, which I don't know how to give)
Since Kies isn't reading/connecting my device, how can I get Kies to connect to my phone?
And since my phone keeps on telling me "No update available" whenever I try to do a software update, I'm going to assume that I have to update my phone's firmware by using Kies. And if my phone is rooted/unrooted, but I can't connect to Kies, how can I update my Android 4.0.4 to the latest Jellybean 4.3 version?
Thank you for any help you can give!
Click to expand...
Click to collapse
First of all, I suggest you reboot your device into download mode:
http://m.youtube.com/watch?v=1tdznfLJsyY
And check if the device info actually indicates its i9300 (just to be sure that you didn't fall into quality fake)
Second, (and I suggesting using a pc for following procedures) try to reinstall kies (make sure you aren't using kies3) and make sure your device is recognized as i9300. Most chances that you won't be able to update with kies, but samsung drivers are needed.
Third- you've got 2 options:
1- flash sumsung's newest official rom fron sammobile using this guide: http://forum.xda-developers.com/showthread.php?t=1671969
2- root your device using this guide:
http://forum.xda-developers.com/galaxy-s3#root
Than install this updated recovery: http://forum.xda-developers.com/showthread.php?t=2002953
If all goes well, you'll be able to install custom roms using the recovey. Like this awesome one: http://forum.xda-developers.com/showthread.php?t=2060403
Ps- if something isn't clear enough, feel free to ask.
Sent from my GT-I9300 using Tapatalk
amirTor said:
First of all, I suggest you reboot your device into download mode:
http://m.youtube.com/watch?v=1tdznfLJsyY
And check if the device info actually indicates its i9300 (just to be sure that you didn't fall into quality fake)
Second, (and I suggesting using a pc for following procedures) try to reinstall kies (make sure you aren't using kies3) and make sure your device is recognized as i9300. Most chances that you won't be able to update with kies, but samsung drivers are needed.
Third- you've got 2 options:
1- flash sumsung's newest official rom fron sammobile using this guide: http://forum.xda-developers.com/showthread.php?t=1671969
2- root your device using this guide:
http://forum.xda-developers.com/galaxy-s3#root
Than install this updated recovery: http://forum.xda-developers.com/showthread.php?t=2002953
If all goes well, you'll be able to install custom roms using the recovey. Like this awesome one: http://forum.xda-developers.com/showthread.php?t=2060403
Ps- if something isn't clear enough, feel free to ask.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
Thanks a lot for your help!
So for the first step, I rebooted it into the Download mode following the video tutorial you linked to, and it told me:
ODIN MODE
Product Name: GT-I9300
Custom Binary Download: Yes (4 counts)
Current Binary: Custom
System Status: Custom
So I'm assuming that yes, my Samsung is an official I9300 device?
For the second step, does it matter which version of Kies I install as long as it's not Kies 3?
For the first option in the third step, will flashing the newest official ROM still allow me to keep on the T-Mobile network? (Since I originally had this device bought in China then had someone else unlock it so that it could be compatible with the US network carriers)
Thanks again!
wohuifei said:
Thanks a lot for your help!
So for the first step, I rebooted it into the Download mode following the video tutorial you linked to, and it told me:
ODIN MODE
Product Name: GT-I9300
Custom Binary Download: Yes (4 counts)
Current Binary: Custom
System Status: Custom
So I'm assuming that yes, my Samsung is an official I9300 device?
For the second step, does it matter which version of Kies I install as long as it's not Kies 3?
For the first option in the third step, will flashing the newest official ROM still allow me to keep on the T-Mobile network? (Since I originally had this device bought in China then had someone else unlock it so that it could be compatible with the US network carriers)
Thanks again!
Click to expand...
Click to collapse
1-It seems so (but if you want to do a double-check: https://play.google.com/store/apps/details?id=com.cpuid.cpu_z and see if it says 'Exynos 4412' in the SOC tab, and 'GT-I9300' + '832MB of ram' in System.
2- Get the lastest available.
3- Then I suggest using the second method. If you already have working CWM recovery, than you should be able to install Philz recovery directly as a zip file in your current recovery.
After updating the recovery (and backing-up all important data!), download NeatRom zip file, and copy it into device's SD.
Reboot to recovery mode, do "wipe to install new rom" + "wipe cache partition" + "advance->wipe delvik cache", and than-
"instal zip from sd/sd1 (depends on where you saved the zip of neatRom) and follow installation instructions.
after the flashing is done, check if the sim works as it should, if not- than you'll have 2 option to unlock it (which costs about 5-7$):
1- https://play.google.com/store/apps/details?id=com.spocky.galaxsimunlock
2- http://www.youtube.com/watch?v=GefyYn63dR4
There are some free turorials online, but they seem to be for older versions / questioned reliability...
A word of caution- moving to 4.3 will change the EFS partition to V2, which by itself isn't a problem (but causing a real headache for those trying to downgrade).
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