Related
So i have gone into the about section and tapped the build number many times, had the message saying im a developer etc
There is no menu, or at least i cant see one, I assume it should appear in the general tab under the heading system?
If i press build number again it just tells me No need, developer mode has been enabled.
I have rebooted the tablet
Any suggestions?
Android version 4.4.2
Baseband T705XXU1ANF7
kERNAL 3.4.39-2293707
Build number KOT49H.T705XXU1ANG2
Anyone?
Are you the primay user on your device?
DUHAsianSKILLZ said:
Are you the primay user on your device?
Click to expand...
Click to collapse
I am the only user on the device it shows as owner.
I have no idea then. What country is this tablet from? I dont even think a factory reset will do it.
UK, it's a 4G+wifi model. Got me pickled to, did a factory reset and nothing.
NJ3 firmware will have it
UpInTheAir said:
NJ3 firmware will have it
Click to expand...
Click to collapse
I need usb debugging to root to be able to change the firmware though
dajones89 said:
I need usb debugging to root to be able to change the firmware though
Click to expand...
Click to collapse
Nope. Odin it
UpInTheAir said:
Nope
Click to expand...
Click to collapse
Thought the device needs usb debugging for communication in the download mode?
dajones89 said:
Thought the device needs usb debugging for communication in the download mode?
Click to expand...
Click to collapse
Since you didn't even bother to try, this is my last reply to you.
If you tried, you would have answered your own question and had success ....................
UpInTheAir said:
Since you didn't even bother to try, this is my last reply to you.
If you tried, you would have answered your own question and had success ....................
Click to expand...
Click to collapse
Did it and it worked.
Sorry if you feel that way, my process has always been to enable usb debugging before attempting to root anything.
Help
dajones89 said:
Did it and it worked.
Sorry if you feel that way, my process has always been to enable usb debugging before attempting to root anything.
Click to expand...
Click to collapse
Did you manage to root the tab? If so how? Thanks
Hey mate. It worked without usb debugging.
I always thought usb debugging was needed as every guide mentions it.
help
dajones89 said:
Hey mate. It worked without usb debugging.
I always thought usb debugging was needed as every guide mentions it.
Click to expand...
Click to collapse
Thanks for quick response, Where did you find a guide to root. Cheers..
Just put root and Odin into a search term. Something should come up.
USB debugging is only needed in the operating system. It has zero effect and not needed in recovery or Odin mode.
Hello to you all! I know I shouldn’t mess with rooting but now it is too late. The damage is done. No I wonder if someone could help me restore it? I have a samsung galaxy s9+ modelnr: sm-g965f.
Before I started with rooting I unlocked oem in My settings.
I used odin to install twrp then i got message that frp was locked. Then I tried to unlock it with a tool and it was messed.
After that I tried to restore it with stock rom firmware from samsung and now I cant do anything.
I cant turn the phone off, just restart it. The message on the phone is ”an error has occured while updating device software. Use the emergency recovery function in the smart switch pc software”
Also tried to connect with smart switch but it couldnt finns My phone.
Now it seems to be oem lock ON and cant turn it off
FIKKI11 said:
Hello to you all! I know I shouldn’t mess with rooting but now it is too late. The damage is done. No I wonder if someone could help me restore it? I have a samsung galaxy s9+ modelnr: sm-g965f.
Before I started with rooting I unlocked oem in My settings.
I used odin to install twrp then i got message that frp was locked. Then I tried to unlock it with a tool and it was messed.
After that I tried to restore it with stock rom firmware from samsung and now I cant do anything.
I cant turn the phone off, just restart it. The message on the phone is ”an error has occured while updating device software. Use the emergency recovery function in the smart switch pc software”
Also tried to connect with smart switch but it couldnt finns My phone.
Now it seems to be oem lock ON and cant turn it off
Click to expand...
Click to collapse
Can you get into download mode?
*Detection* said:
Can you get into download mode?
Click to expand...
Click to collapse
Yes i can.
FIKKI11 said:
Yes i can.
Click to expand...
Click to collapse
Make sure you're using ODIN 3.13 or newer
Try enabling the "Repartition" option in ODIN while flashing all 4 parts of the firmware together, using CSC not HOME_CSC
*Detection* said:
Make sure you're using ODIN 3.13 or newer
Try enabling the "Repartition" option in ODIN while flashing all 4 parts of the firmware together, using CSC not HOME_CSC
Click to expand...
Click to collapse
You just won a gold medal. Many thanks for your help ??
FIKKI11 said:
You just won a gold medal. Many thanks for your help ??
Click to expand...
Click to collapse
Great :good:
Hello. Why cant i root my device using kingroot sm-g965F?
It just keeps scrolling, but nothing happens?
Damaged0ne said:
Hello. Why cant i root my device using kingroot sm-g965F?
It just keeps scrolling, but nothing happens?
Click to expand...
Click to collapse
You've already made a post on this.
This Work From Version NCQ26.69-56 up to NCQ26.69-64-X .
Solution One :
Download shortcut master
Then on app search to find
SETTINGS
select com.motorola.programmenu.PgmApnSettings
Launch > New APN
Solution Two :
Download Terminal Emulator .
on the terminal :
1. su
2. am start com.motorola.programmenu/.PgmApnSettings
3. NEW APN
Solution Three :
need adb tools. adb drivers
From The Computer
Open Cmd Or PowerShell Or Bash If Is On Linux
1. Enable Usb Debugging >> Connect The Phone To The Pc
2. adb devices >> Authorize on the Phone
3. adb shell
4. su
5. am start com.motorola.programmenu/.PgmApnSettings
3. NEW APN
Thanks Everybody :> no More Frustration Or Downgrading Or Hardbriking Trying To. Happy 4G LTE Hotspot
Thank you @ozmage, for your informative guide. This will undoubtedly benefit users who want the most recent firmware build AND the ability to use a GSM service provider. Nice work.
MotoJunkie01 said:
Thank you @ozmage, for your informative guide. This will undoubtedly benefit users who want the most recent firmware build AND the ability to use a GSM service provider. Nice work.
Click to expand...
Click to collapse
No Thank You Man Is An Honor Coming From You , And Yes Im Glad To Help And Share This Discovery.
someone knows how to get the msl code ? not calling the Carrier
Hi, I have a problem
Hello, I update my Moto E4 Sprint and now it does not let me create a new APN, these options need root, but I can not find the post to root this phone, if you know some post to root this phone, please can tell me, excuse my English because I do not know much. Thank you very much.
Leodanis said:
Hello, I update my Moto E4 Sprint and now it does not let me create a new APN, these options need root, but I can not find the post to root this phone, if you know some post to root this phone, please can tell me, excuse my English because I do not know much. Thank you very much.
Click to expand...
Click to collapse
1. Boot loader unlock (through official Motorola boot loader unlock) https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b
2. Flash twrp via (fastboot flash recovery recovery.img) https://forum.xda-developers.com/mo...velopment/twrp-twrp-moto-g4-qualcomm-t3655160
3. Flash Magisk On Twrp . https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Step 0 : Enable Developer Options , Enable Oem Unlocking , Enable Usb Debugging , Run Adb On The Computer With The Phone Connected And Authorize ADB , Reboot To Fastboot unlock bootloader etc
Done !!!
ozmage said:
1. Boot loader unlock (through official Motorola boot loader unlock) https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b
2. Flash twrp via (fastboot flash recovery recovery.img) https://forum.xda-developers.com/mo...velopment/twrp-twrp-moto-g4-qualcomm-t3655160
3. Flash Magisk On Twrp . https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Step 0 : Enable Developer Options , Enable Oem Unlocking , Enable Usb Debugging , Run Adb On The Computer With The Phone Connected And Authorize ADB , Reboot To Fastboot unlock bootloader etc
Click to expand...
Click to collapse
Thank you very much, I just needed to root my phone and with that magisk worked, I can create apn, thanks. :good::good::good:
Leodanis said:
Thank you very much, I just needed to root my phone and with that magisk worked, I can create apn, thanks. :good::good::good:
Click to expand...
Click to collapse
Glad To Help :good:
A question
ozmage said:
Glad To Help :good:
Click to expand...
Click to collapse
I used this method because I installed several custom rom (aicp_perry_n-12.1-UNOFFICIAL-20180202, aoscp_perry-4.1.2-20180127-unofficial and RR-N-v5.8.5-20171206-perry-Unofficial), but in all case my phone does not catch signal, but with the official is ok, What can be ?.
Thanks for your time.
Leodanis said:
I used this method because I installed several custom rom (aicp_perry_n-12.1-UNOFFICIAL-20180202, aoscp_perry-4.1.2-20180127-unofficial and RR-N-v5.8.5-20171206-perry-Unofficial), but in all case my phone does not catch signal, but with the official is ok, What can be ?.
Thanks for your time.
Click to expand...
Click to collapse
Yes This Is A Problem That Comes With The Last Ota Several People Have This Problem Included Myself , But Soon This Will Be Solved By Squid2 The Maintainer Of Lineage-Os For Moto E4 Perry , The RIL Binaries From New Stock Needs To Be Cooked In LOS
And Other Roms.
Leodanis said:
I used this method because I installed several custom rom (aicp_perry_n-12.1-UNOFFICIAL-20180202, aoscp_perry-4.1.2-20180127-unofficial and RR-N-v5.8.5-20171206-perry-Unofficial), but in all case my phone does not catch signal, but with the official is ok, What can be ?.
Thanks for your time.
Click to expand...
Click to collapse
Has anyone found a fix yet
Bailey36375 said:
Has anyone found a fix yet
Click to expand...
Click to collapse
No. The latest OTA update remove the ability to use a custom ROM to use it on a different network
Not try to use different networks want to stay on boost but when if flash from stock to a custom rom there's no data or signal i was hoping that dome one had a working custom rom on boost that could do a back up and send it to me to flash.
Bailey36375 said:
Not try to use different networks want to stay on boost but when if flash from stock to a custom rom there's no data or signal i was hoping that dome one had a working custom rom on boost that could do a back up and send it to me to flash.
Click to expand...
Click to collapse
You might need blobs and APN fix zip for boost
I've got blobs and apn but still not working.
---------- Post added at 04:00 AM ---------- Previous post was at 03:57 AM ----------
I flashed blobs and apn together and separated before I booted but still nothing can you explain what I may be doing wrong
Does it mean that if I follow the instruction to root, twrp, Magisk and then bring up the APN menu, I can use the E4 with other GSM carriers? As long as I stay stock?
nookin said:
Does it mean that if I follow the instruction to root, twrp, Magisk and then bring up the APN menu, I can use the E4 with other GSM carriers? As long as I stay stock?
Click to expand...
Click to collapse
Having root does not bring up the APN settings menu. You have to actually find the file in the system and edit it manually.
madbat99 said:
Having root does not bring up the APN settings menu. You have to actually find the file in the system and edit it manually.
Click to expand...
Click to collapse
That's what this command does, right?
am start com.motorola.programmenu/.PgmApnSettings
Can someone confirm that I can turn an XT1766 with latest OTA into a phone that works with GSM and remain stock firmware?
In other words, does editing APN gives stock firmware the ability to use GSM?
nookin said:
That's what this command does, right?
am start com.motorola.programmenu/.PgmApnSettings
Can someone confirm that I can turn an XT1766 with latest OTA into a phone that works with GSM and remain stock firmware?
In other words, does editing APN gives stock firmware the ability to use GSM?
Click to expand...
Click to collapse
Yep. Also check this post out. https://forum.xda-developers.com/mo...estoring-moto-e4-xt1766-t3820749/post77194110
If you get your MSL code from your carrier you can also enter the menu with ##3282# to edit your APN also a few other things including band priority.
See this post
madbat99 said:
Yep. Also check this post out. https://forum.xda-developers.com/mo...estoring-moto-e4-xt1766-t3820749/post77194110
If you get your MSL code from your carrier you can also enter the menu with ##3282# to edit your APN also a few other things including band priority.
See this post
Click to expand...
Click to collapse
I can bring up the ##3282# menu. You mean the lock code for Edit APN? It is a 6 digits number. I wonder if there is a limit on number of attempts? 6-digits is not a terribly large combination.
Hi --
Old Galaxy Tab Pro 10.1 running kitkat. I am using CF Auto Root to root it via Odin and I get the "pass" in Odin but then it just reboots into the existing OS and Supersu is not on the device. The instructions I have been following say that you should try again but switching off the "auto reboot" in odin. I did that, but it just remains in download mode. The instructions said to take out the battery...which, not really an option for the tablet.
I believe I followed all other instructions: I have the correct CF Auto Root file for my build; I have the drivers from Samsung ...
Any advice is appreciated.
tojotojo said:
Hi --
Old Galaxy Tab Pro 10.1
Click to expand...
Click to collapse
Which one?
tojotojo said:
running kitkat......
Click to expand...
Click to collapse
So you want to keep that?
If not why don't you flash TWRP and Lineage?
bmwdroid said:
Which one?
So you want to keep that?
If not why don't you flash TWRP and Lineage?
Click to expand...
Click to collapse
Hi, and thanks for the reply. Big picture is that I'd like to use the tablet but kitkat obviously is now not compatible with most apps. So really just any reliable way to root so that I can make use of up-to-date/current apps. I can research TWRP and Lineage -- I'm guessing there's a how-to on here somewhere.
Tablet version: SM-t520.
tojotojo said:
Hi, and thanks for the reply. Big picture is that I'd like to use the tablet but kitkat obviously is now not compatible with most apps. So really just any reliable way to root so that I can make use of up-to-date/current apps. I can research TWRP and Lineage -- I'm guessing there's a how-to on here somewhere.
Tablet version: SM-t520.
Click to expand...
Click to collapse
And , obviously, terminology may be/probably is "off" here (newbie and all) ... but I believe there's a step before being able to flash TWRP and Lineage - whether that's "rooting" or "unlocking" or whatever. I'm basically still "stock" at this point.
tojotojo said:
Hi, and thanks for the reply. Big picture is that I'd like to use the tablet but kitkat obviously is now not compatible with most apps. So really just any reliable way to root so that I can make use of up-to-date/current apps. I can research TWRP and Lineage -- I'm guessing there's a how-to on here somewhere.
Tablet version: SM-t520.
Click to expand...
Click to collapse
I see.
Imo it's necessary 1st of all to make sure it's on latest stock to have latest bootloader.
Flashing TWRP with Odin is extremly easy.
Here is a post/thread although written for S4 valid for most others as well.
Written a how-to myself as well but the english part is not as up-to-date as the german is.
tojotojo said:
And , obviously, terminology may be/probably is "off" here (newbie and all) ... but I believe there's a step before being able to flash TWRP and Lineage - whether that's "rooting" or "unlocking" or whatever. I'm basically still "stock" at this point.
Click to expand...
Click to collapse
No unlocking necessary with that old device.
Rooting means having SU or Magisk but flashing works without as well.
bmwdroid said:
No unlocking necessary with that old device.
Rooting means having SU or Magisk but flashing works without as well.
Click to expand...
Click to collapse
Great, will give this a shot later today. Appreciate the help!
Well, didn't get very far. My understanding is that you have to unlock the OEM bootloader under developer options...which, ... well, I don't have that option listed once I've accessed the developer options. Tried a bunch of options -- factory reset, changed date/time to long ago .... used Smart Switch to check for updates (which one post said would prompt it to appear. Any options for getting this modded without the OEM bootloader unlock option? One post somewhere said that having the USB debugging option checked would work, but .... questionable.
tojotojo said:
Well, didn't get very far. My understanding is that you have to unlock the OEM bootloader under developer options...which, ... well, I don't have that option listed once I've accessed the developer options.
Click to expand...
Click to collapse
As I said: not on this old device
tojotojo said:
Tried a bunch of options -- factory reset, changed date/time to long ago .... used Smart Switch to check for updates (which one post said would prompt it to appear. Any options for getting this modded without the OEM bootloader unlock option? One post somewhere said that having the USB debugging option checked would work, but .... questionable.
Click to expand...
Click to collapse
Just use Odin to flash latest TWRP,
Reboot to that TWRP,
Wipe everything plus "Format Data"
Flash suiting ROM and test if it works
reboot to TWRP and flash Gapps fitting this ROM version (I prefer Bitgapps ARM)
Be happy
@tojotojo remember that Odin can only flash .tar and .tar.md5 files
TWRP.....img are to flash later in an old TWRP to get a newer one.
you need check off auto-reboot. it still in dload-mode, then press power to reboot and just as you see it starts boot press recovery-mode key combination to enter recovery. if you are slow, tab will load default system without ur root and recovery. i hope this help you.
If your bootloader is locked, one of the dumbest things you can do is try to install potentially unstable firmware. If something goes wrong, you won't be able to recover your device.
If you did anyway, the only way you should try to return to stock is with the Android Flash Tool, which should work as long as OEM Unlocking is enabled.
If you're on a device that cannot be unlocked, you should wait the Android 13 official release.
V0latyle said:
If your bootloader is locked, one of the dumbest things you can do is try to install potentially unstable firmware. If something goes wrong, you won't be able to recover your device.
If you did anyway, the only way you should try to return to stock is with the Android Flash Tool, which should work as long as OEM Unlocking is enabled.
If you're on a device that cannot be unlocked, you should wait the Android 13 official release.
Click to expand...
Click to collapse
I got my device from T-Mobile and yes the bootloader is locked. I was on the A13 beta and opted out. I am now back on A12. Yes it took some extra steps to get back to A12 but you can do it with a locked bootloader.
truckerdewd said:
I got my device from T-Mobile and yes the bootloader is locked. I was on the A13 beta and opted out. I am now back on A12. Yes it took some extra steps to get back to A12 but you can do it with a locked bootloader.
Click to expand...
Click to collapse
Not everyone has been so lucky. Glad it worked for you, though.
roirraW edor ehT said:
Not everyone has been so lucky. Glad it worked for you, though.
Click to expand...
Click to collapse
True. I posted the steps I followed in this thread.
Android Beta to Factory Reset mucked up, plus a bunch of troubleshooting I've already tried
Okay. The android beta program was messing with an app I use regularly so I backed up my phone on google 1 and all that fun stuff then did the opt out and just ran stuff like it was supposed to. Then, it got stuck in fastboot mode and said that...
forum.xda-developers.com
I'm a firm believer that unless you are using some apps (mostly banking apps) that will absolutely not work with these enabled, that before doing anything you should toggle on "OEM unlocking" and "USB debugging", regardless if you're using Stable or Beta or whatever you're doing. It will open up a bunch of possibilities to recover your phone if you hit a glitch in the matrix.
For me it's the very 1st thing I do when getting a new phone.
Lughnasadh said:
I'm a firm believer that unless you are using some apps (mostly banking apps) that will absolutely not work with these enabled, that before doing anything you should toggle on "OEM unlocking" and "USB debugging", regardless if you're using Stable or Beta or whatever you're doing. It will open up a bunch of possibilities to recover your phone if you hit a glitch in the matrix.
For me it's the very 1st thing I do when getting a new phone.
Click to expand...
Click to collapse
I'm not sure toggling these would trip device security. As long as the bootloader remains locked the device should meet HARDWARE_BACKED integrity (key attestation), and if the firmware is factory the device should meet BASIC integrity as well.
Sorry, but if you just enable the OEM unlock? Then, just in case things go bad, you can unlock bootloader...
V0latyle said:
I'm not sure toggling these would trip device security. As long as the bootloader remains locked the device should meet HARDWARE_BACKED integrity (key attestation), and if the firmware is factory the device should meet BASIC integrity as well.
Click to expand...
Click to collapse
We are not actually talking about tripping device security or being able to pass Play Integrity API, etc.. Even with the bootloader locked, apps can still check to see whether OEM Unlocking and USB Debugging are enabled, and if so, make it so the app fails to work properly, if at all. Apps can even check to see if you have Developer Options enabled.
USB debugging definitely does interfere with some apps being able to work. I have to disable it to use one of my apps and many others have reported the same for a variety of apps. I have also seen having OEM Unlocking enabled interfere with some apps as well, as reported by others.
In my case I just disable USB Debugging, use the app, then re-enable when done using the app.
gpvecchi said:
Sorry, but if you just enable the OEM unlock? Then, just in case things go bad, you can unlock bootloader...
Click to expand...
Click to collapse
Basically yes, as long as you have an unlockable bootloader, can get into fastboot, etc..
For example, if things go haywire for you and you have OEM unlocking enabled, you can use Android Flash Tool to help recover your device. Or you can use fastboot to manually unlock the bootloader and flash whatever.
Lughnasadh said:
We are not actually talking about tripping device security or being able to pass Play Integrity API, etc.. Even with the bootloader locked, apps can still check to see whether OEM Unlocking and USB Debugging are enabled, and if so, make it so the app fails to work properly, if at all. Apps can even check to see if you have Developer Options enabled.
USB debugging definitely does interfere with some apps being able to work. I have to disable it to use one of my apps and many others have reported the same for a variety of apps. I have also seen having OEM Unlocking enabled interfere with some apps as well, as reported by others.
In my case I just disable USB Debugging, use the app, then re-enable when done using the app.
Click to expand...
Click to collapse
Yeah I think my brain was somewhere else. Interesting though.
@Lughnasadh Just curious which apps? I've not come across any.
bobby janow said:
@Lughnasadh Just curious which apps? I've not come across any.
Click to expand...
Click to collapse
Of the ones I use, Spectrum TV requires USB Debugging to be disabled.
Lughnasadh said:
Of the ones I use, Spectrum TV requires USB Debugging to be disabled.
Click to expand...
Click to collapse
I obviously do not use Spectrum TV. I almost always have debugging on and have never come across a need to turn it off, I actually didn't even know it was a thing. But it makes sense since it is an opening into the device. One thing I have noticed when I flip the OEM switch though. I only keep it active when I'm either sideloading or, heaven forbid, install a beta or custom rom. After it's done and booted I flip the switch back off and it has me reboot for added security that is not available when the switch is active. What's that all about?
bobby janow said:
I obviously do not use Spectrum TV. I almost always have debugging on and have never come across a need to turn it off, I actually didn't even know it was a thing. But it makes sense since it is an opening into the device. One thing I have noticed when I flip the OEM switch though. I only keep it active when I'm either sideloading or, heaven forbid, install a beta or custom rom. After it's done and booted I flip the switch back off and it has me reboot for added security that is not available when the switch is active. What's that all about?
Click to expand...
Click to collapse
Yeah, if you go through the Magisk, SafetyNet and similar threads you'll see people who have come across apps that won't work when USB Debugging is enabled. It's really up to the app developer as to whether it checks for it or not.
I'm not entirely sure why after you switch OEM Unlocking off that it has you reboot as I've never switched it off once switched on. My guess would be that a reboot is needed to set ro.oem_unlock_supported to 0. But that's just a guess.
V0latyle said:
If your bootloader is locked, one of the dumbest things you can do is try to install potentially unstable firmware. If something goes wrong, you won't be able to recover your device.
If you did anyway, the only way you should try to return to stock is with the Android Flash Tool, which should work as long as OEM Unlocking is enabled.
If you're on a device that cannot be unlocked, you should wait the Android 13 official release.
Click to expand...
Click to collapse
The way Google implements there otas and installs now is a fail safe, the devices will not be bricked what so ever, if on stock that is