Related
Hi
I am unable to root my tmobile (uk) htc G2 Touch, I have tried the following:
xda developers forum guide by Dayzee (unable to download image)
theunlocker 1 click method
(receive error on step 10 - backup failed)
Model: T-Mobile G2 Touch
Firmware 1.5
Build Number: 2.73.110.26
Can anyone help?
Usual problem with the G2 Touch...
Follow his procedure and you should be fine
http://forum.xda-developers.com/showthread.php?t=572683
Thanks mate, I'll give it a try
ok, iv tried the above link, but its still not working, im getting the same error message, any ideas
three different approaches to root and you are getting the same error message?
yup, at exactly the same stage
Try using the HEROIMG.ZIP method. If you go to http://forum.xda-developers.com/showthread.php?t=575448, there are some instructions. To clarify on where the actual ROM.zip file you have to find is, it will be in C:\Users\Username\AppData *(a hidden folder, might need to unhide/type in the folder name)\Local\Temp\some folder with long nonsense name\another nonsense name\ROM.ZIP
You'll need a gold card to do this though, but this is how HTC does it themselves for upgrading phones in for service.
This will get you back to an old, easily rootable (using flashrec/fastboot) firmware.
HTH
EDIT: I would recommend using the oldest available RUU (1.73, as that gives an unlocked fastboot, and is also definitely easy to root, as I've done it myself. Others should work, but no personal experience of them)
checked that but it no one has said that it actually works, so no point trying it really,
it seems to be when I use flashrec to back that I receive the error
Hi guys I have a generic unbanded hero running 2.73.405.66 and have been trying to root it for the past few days with no sucess.
Ive managed to create a goldcard ok (I think) and am able to start the install of the earlier rom ok, but once the install starts and reboots the phone, after a minute or so i get an incorrect bootloader error and the install stops.
Just wondering if anyone using this ROM has managed to downgrade to gain root, if so a prod in the right direction would be appreciated
Oh and I know some of you are going to say search the forums, but I cannot seem to find any info on this latest rom, all the guides seem to cover earlier or carrier specific ROMS.
I dont think you need to downgrade the 405 bootloader. Have you tried the one click method at unlocker.com.
rosso22 said:
Hi guys I have a generic unbanded hero running 2.73.405.66 and have been trying to root it for the past few days with no sucess.
Ive managed to create a goldcard ok (I think) and am able to start the install of the earlier rom ok, but once the install starts and reboots the phone, after a minute or so i get an incorrect bootloader error and the install stops.
Just wondering if anyone using this ROM has managed to downgrade to gain root, if so a prod in the right direction would be appreciated
Oh and I know some of you are going to say search the forums, but I cannot seem to find any info on this latest rom, all the guides seem to cover earlier or carrier specific ROMS.
Click to expand...
Click to collapse
My guide can be used for all users.
You just need to downgrade! You need the correct driver, check my ADB / Sync guide for the driver.
Hello all, I'm new to this site and I've never rooted a phone. Actually, the Eris is my first smartphone. I've read a lot of forums about rooting the Eris and from what I understand I shouldn't have installed the 2.1 ota update. I bought this phone soon after they were released so maybe I have a 1.47 hboot? I'm unsure how to check this, but if so does this mean I can root using the 1.5 method?
I just bought a class 6 8GB microsd card with the hopes of installing a custom rom, overclocking, and installing apps2sd. Now I'm getting very discouraged because it seems 2.1 can't currently be rooted.
Hopefully a senior user can help me out. Please put your response in lamens terms. I've seen some other forums where junior users are getting bashed for asking stupid questions so I'm putting it out there....please don't bash me for this one.
http://forum.xda-developers.com/showthread.php?t=684049
everything you need and more. To answer your next question. As long as your phone was never updated with leak, the process for root of 1.5 and 2.1 are the same.
happy rooting!
Thanks Spencer! If I root using the method at that page will I be able to flash other roms or will I be stuck with this 2.1 ROM? I'd like to install the evileris rom and (again I'm a newbie) I don't want to end up stuck like the people who installed the leaked 2.1.
you should be able to flash a custom rom to the phone as i believe you have to first load a custom recovery image to it. i could be wrong though just a guess.
SDK Not Working?
HELP!! I just rooted my phone, installed java, installed SDK and I can't get the command prompts to work. I followed the steps exactly (or so I think) and I'm opening sdksetup.exe. When I try to type I get nothing. Am I opening the wrong file or doing something wrong. I've not been able to install the recovery or custom rom to my phone yet, so I'm very vulnerable right now. Any ideas anyone?
Ok, maybe this is my problem...
Before the root, I could go into device manager from my computer and I got a yellow exclamation mark. After the root, I cannot find it. I can click on portable devices and it shows an Android Phone so I'm guessing my computer doesn't recognize it anymore. If that's the case I probably need to update the driver for SDK to work, but I need to find the device for that to work. I have USB debugging on. Any help is appreciated.
If it says android phone with no exclamation point that means it is recognized. Its when there is an exclamation point that means it is not recognized. I probably won't be able to help you further because I'm a rooting noob (I've only rooted my Eris and I had no problems) but I am a computer expert and I would suggest rebooting your computer and then trying it again... unless you already have.
-------------------------------------
Sent via the XDA Tapatalk App
joshw0000 said:
HELP!! I just rooted my phone, installed java, installed SDK and I can't get the command prompts to work. I followed the steps exactly (or so I think) and I'm opening sdksetup.exe. When I try to type I get nothing. Am I opening the wrong file or doing something wrong. I've not been able to install the recovery or custom rom to my phone yet, so I'm very vulnerable right now. Any ideas anyone?
Click to expand...
Click to collapse
What exactly do you mean when you say "I can't get the command prompts to work"?
joshw0000 said:
HELP!! I just rooted my phone, installed java, installed SDK and I can't get the command prompts to work. I followed the steps exactly (or so I think) and I'm opening sdksetup.exe. When I try to type I get nothing. Am I opening the wrong file or doing something wrong. I've not been able to install the recovery or custom rom to my phone yet, so I'm very vulnerable right now. Any ideas anyone?
Click to expand...
Click to collapse
Ok, calm down its not the end of the world, i ran into the same problem. What we need for us to help you, is at what point are you in trying to root your phone. Do you have SDK installed and updated?
I'm following the how to root instructions. I've completed I: Gaining Root and made it to 9. In II: Prerequisites. Java and SDK are both saved and extracted on my c: drive. I downloaded the USB drivers package in #6 of II. USB debugging was enabled and the phone was set to charge only. When I opened device manager on my pc, their was no yellow exclamation like the instructions indicated. I clicked on "Android Phone" and attempted to update the drivers found in SDK but Windows said they were up to date. I moved on to step III. Flashing a Custom Recovery and saved the zip file to my SD (should I save that to my c: drive?). I extracted it to tools in Android SDK and attempted to use the command prompt in SDK. It was unresponsive. It did not recognize my phone. I'm unsure if it does that automatically, if I need to take action, or if I should use the pc command prompt.
I went back to #9 of II and tried to troubleshoot. I tried every way I could think of to get the exclamation mark to show up in device manager so I could update the USB drivers. I hooked up my wife's unrooted Eris and it had the exclamation. I restarted my phone, restarted my computer, reflashed PB00IMG.zip and still had no luck.
Anybody had this probem? Any suggestions?
I’m stuck in a rut. I got a Motorola Atrix 4G (AT&T) last week and was trying to unlock it using the following instructions: http://wiki.cyanogenmod.com/wiki/Motorola_Atrix_4G:_Full_Update_Guide#Unlocking_the_Bootloader
I installed RSD Lite 5.7, the Motorola Drivers, and downloaded the unlockable bootloader. I got to step 12, and then everything quickly went downhill. I got stuck on the horrid “Failed to boot 0x1000” screen, along with the list of options. I have tried booting into RSD, running RSD Lite, and loading the bootloader, but I get a “Device Interface” prompt…not exactly sure of the wording at the moment. I drained the battery last week messing with it, and had to buy a standalone charger (which I just received today).
I am not sure of the Android version/firmware version that was on the phone prior to doing this. I know, mistake #1.
My computer is recognizing the Atrix, but the RSD Lite is not able to install the unlockable bootloader (listed on the above site). I have downloaded one “Stock Restore” MFBSR.zip (I can’t seem to find the link to the thread) but this was not able to fix the problem. It recognized my device, but the Atrix wouldn’t accept any of the commands.
I am not sure of what to do, short of calling Motorola and trying to get them to help. I’m sure they would either want to replace it (charging me) or just basically tell me I’m SOL.
I wanted to try FruitCake’s recovery tool, and found the following thread, which has mirror links of some of the files:
http://forum.xda-developers.com/showthread.php?p=24472332#post24472332
I have no clue as to what I would use, so I haven’t even tried downloading one of them. I’m seriously at my wit’s end..I have been Googling and trying to avoid making a post about this. Any help is greatly appreciated. I am about to try the following directions:
http://forum.xda-developers.com/showpost.php?p=19986512&post=234
Also probably important to note that I tried unlocking it using Fastboot, but it was "Waiting for device" for forever and did nothing. When I try to go into Recovery, it says Magic Value Mismatch.
Thanks guys.
http://forum.xda-developers.com/showthread.php?t=1857099
Try! Good Luck!
maggedo said:
I was stuck on the Moto Dual Core Screen as well. I used the automatic unlock MAIN program to unlock, root and install custom recovery. When I tried to flash epinter's CM10 ROM I got boot hang at the Moto screen.
You can RSD back to stock (e.g. I found the AT&T .151 sbf file and restored my phone to working condition on 2.3.6 GB).
In the end I figured out that the recovery in the auto unlock tool (both the telfar and CWM options) was borking the CM10 flash. I ended up:
1. RSD lite AT&T .151 GB 2.3.6 sbf file
2. Unlock Bootloader with automatic unlock
3. Root and install custom recovery
4. Boot into android
5. download goo.manager from play store
6. Install open source recovery with goo.manager
7. reboot into recovery
8. Make backup of everything
9. Flash JB CM10 & GApps
Phone is up and running w/o issues. A bit of googling should find you the necessary sbf to get you on your feet again.
Good luck!
Click to expand...
Click to collapse
I am trying this...but when I am in RSD Lite, it says "Failed Flashing Process: Unable to retrieve interface handle (0x7027)". It does detect my device before this, saying Port Type: USB, IMEI/ESN/MEID: NA, and Status: Connected...
Please help!
KokoATL said:
I am trying this...but when I am in RSD Lite, it says "Failed Flashing Process: Unable to retrieve interface handle (0x7027)". It does detect my device before this, saying Port Type: USB, IMEI/ESN/MEID: NA, and Status: Connected...
Please help!
Click to expand...
Click to collapse
http<delete>://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
Go there and unlock your bootloader first.
Then flash the sbf above on post#2 again.
have u solve your problem?
Sent from my MB860 using xda premium
maggedo_defy said:
http<delete>://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
Go there and unlock your bootloader first.
Then flash the sbf above on post#2 again.
Click to expand...
Click to collapse
He can't. Fastboot doesn't respond. Also he can't flash any SBF, everything fails.
Looks more like a hard brick to me...
Perhaps... (option number 3)
http://forum.xda-developers.com/showthread.php?t=1182871
soft bricked
KokoATL said:
I’m stuck in a rut. I got a Motorola Atrix 4G (AT&T) last week and was trying to unlock it using the following instructions: http://wiki.cyanogenmod.com/wiki/Motorola_Atrix_4G:_Full_Update_Guide#Unlocking_the_Bootloader
I installed RSD Lite 5.7, the Motorola Drivers, and downloaded the unlockable bootloader. I got to step 12, and then everything quickly went downhill. I got stuck on the horrid “Failed to boot 0x1000” screen, along with the list of options. I have tried booting into RSD, running RSD Lite, and loading the bootloader, but I get a “Device Interface” prompt…not exactly sure of the wording at the moment. I drained the battery last week messing with it, and had to buy a standalone charger (which I just received today).
I am not sure of the Android version/firmware version that was on the phone prior to doing this. I know, mistake #1.
My computer is recognizing the Atrix, but the RSD Lite is not able to install the unlockable bootloader (listed on the above site). I have downloaded one “Stock Restore” MFBSR.zip (I can’t seem to find the link to the thread) but this was not able to fix the problem. It recognized my device, but the Atrix wouldn’t accept any of the commands.
I am not sure of what to do, short of calling Motorola and trying to get them to help. I’m sure they would either want to replace it (charging me) or just basically tell me I’m SOL.
I wanted to try FruitCake’s recovery tool, and found the following thread, which has mirror links of some of the files:
http://forum.xda-developers.com/showthread.php?p=24472332#post24472332
I have no clue as to what I would use, so I haven’t even tried downloading one of them. I’m seriously at my wit’s end..I have been Googling and trying to avoid making a post about this. Any help is greatly appreciated. I am about to try the following directions:
http://forum.xda-developers.com/showpost.php?p=19986512&post=234
Also probably important to note that I tried unlocking it using Fastboot, but it was "Waiting for device" for forever and did nothing. When I try to go into Recovery, it says Magic Value Mismatch.
Thanks guys.
Click to expand...
Click to collapse
Did the same to mine about 5hr 's ago, but i found These SBF files (https://sites.google.com/site/motosbf/atrix-sbf-files ) found the one i was running ,booted the phone into RSD mode again and ran it in RSD Lite ,took a while about 30mins but it worked .
hope this works for you
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