Related
[RC-FAQ] >> Frequently Asked Questions for Motorola Moto G [Updated : 2015/09/23]
[SIZE=+3]Frequently Asked Questions[/SIZE]
[SIZE=+2] Motorola Moto G
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[/SIZE]
Read Before Asking Please
[SIZE=+1]This a short list of frequently asked questions in this device forum and the answers often given as a response. It should serve as a starting point for gathering knowledge and finding solutions to many common problems. Please only post in this thread with feedback on how to improve this document. Do not post "Thank you" type responses. If you have additional questions or require more help, try to find an existing thread or create your own. Do not use this as a general help thread.[/SIZE]
To Browse quickly the FAQ and find what you need, Ctrl+F is the key feature
You may search in Motorola help topics too
Table of content :
FAQ part 1
General advices about debugging
Unlocking Bootloader
Rooting your device :
- Option 1, using SuperBoot [external thread, on MoDaCo]
- Option 2, using a customized recovery [external thread, on MoDaCo]
- Option 3, for 4.4.2 using SuperSU [external thread, on swedroid.se]
Useful Links
build.prop collection
Refer to :
@Perseus71 Ressource Guide for tech specifications, ROMs, Kernels, Root ...
@Mr hOaX Tips and Tricks thread for more Up-To-Date informations
@72off Android related terms and abreviations
@pinguijxy FAQ, for CM11 related issues.
THIS FAQ IS MADE FOR Moto G 'old' editions (NOT FOR 4G/LTE MODEL or 2d Gen [aka 2014])
FAQ
[SIZE=+1]Q1: What are Moto G tech specs ?[/SIZE]The Motorola Moto G is named XT1032/XT1033/XT1034/XT1035/... aka Falcon
XT1028: Verizon US CDMA - 8GB/16GB
XT1031: Boost US CDMA - 8GB/16GB
XT1032: EU/Global GSM/GPe - 8GB/16GB. (GPe = Google Play edition)
XT1033: Brazil - 8GB/16GB (Colors Edition) (Dual Sim) + Moto G (Music edition) (Dual Sim) (16GB Only)
XT1034: US GSM - 8GB/16GB.
XT1035: Brazil - 8GB/16GB (Colors Edition) (Unconfirmed)
Moto G 4G/LTE aka peregrine : ==> /!\ Roms made for standard edition (non-4G) are not compatible with these devices!
XT1045: Moto 4G - 8GB
XT1039: Moto 4G - 8GB UK/EU
XT1040: Moto 4G - 8GB Brazil
Complete specifications available in @Perseus71 Guide or @Mr hOaX Tips and Tricks thread
[SIZE=+1]Q2: What is the .................................................. .................................................. ....?[/SIZE][...]
[SIZE=+1]Q3: Why doesn't the LED work ?[/SIZE]maybe you disabled LED on you older device (or it didn't even have one) setting up you google account disabled the LED on you new Motot G use Notification Light Widget From Motorola to fix this issue (more info)
[SIZE=+1]Q4: How to access Fastboot?[/SIZE]Hold PowerButton and VolDown during boot.
[SIZE=+1]Q5: How to unlock Bootloader?[/SIZE]Boot to Fastboot and follow this guide
or Motorola guide on Motorola's website
[SIZE=+1]Q6: How do i get adb and fastboot drivers ?[/SIZE]For windows, follow this guide or this one
although, it seems Motorola Device Manager works ok for win7x86-32 (but not for win7x64-64?) i cannot answer this i'm under linux
other USB drivers if first method failed, source
For Linux, get fastboot files here also, adb and fastboot can be installed using repos for ubuntu-based distros packages needed are : android-tools-adb and android-tools-fastboot (android-tools-fsutils may be useful too)
eg:
Code:
sudo apt-get install android-tools-fastboot
[SIZE=+1]Q7: How to flash Stock Firmware?[/SIZE]For windows, follow this guide or this video
The above is for non-4G devices, for Moto G 4G version refer to this thread
[SIZE=+1]Q8: How to Root my device ?[/SIZE]Until now,you first need to unkock your bootloader,
Option 1 : then follow this guide [original thread - on MoDaCo]
Option 2 : via a customized recovery [original thread, on MoDaCo]
paulobrien said:
The first method is recommended as it doesn't mess with the recovery. But the second is there as a backup.
Click to expand...
Click to collapse
==> Option 1 seems not to work properly for some users, in that case : Try Both.
After you get root, please read Q19
[SIZE=+1]Q9: Why dosen't my .apk get installed manually?[/SIZE]
Until i get a better solution, here are some workaround :
Check you've enabled Unknown sources (settings>security>unknown sources)
If you did so, there are some workaround :
At the phone first set-up (you may need to factory-reset to get that) - When Motorola assistant asks for data safety (just before the Google accounts question comes up), don't click accept, but tap on "data safety guidelines" and tick both settings to off. Then accept.
Use adb :
Code:
adb install packagename.apk
Use google drive to download the app (gdrive has an antivirus scanner that checks the app, since then it is considered as "safe" for the device and is correctly installed
other workaround
[SIZE=+1]Q10: Where can i find a Custom recovery ?[/SIZE]
TWRP Recovery ported by @a1Pha
CWM recovery ported by @a1Pha
CWM Advanced Edition PhilZ Touch by @Phil3759
TWRP 2.7.1.0 by @TeamMex
[SIZE=+1]Q11: How to access bootloader?[/SIZE]- Via ADB :
Code:
adb reboot bootloader
- The hard(ware) way :
With the phone powered off, press the VOL DOWN KEY for 2-3 seconds then POWER key then release.
The device will display different BOOT OPTIONS
Use the VOL DOWN Key to SCROLL to Recovery and VOL UP Key to select
[SIZE=+1]Q12: How to access recovery?[/SIZE]
using terminal, if the device is already rooted
Code:
su
reboot recovery
via adb
Code:
adb reboot recovery
via bootloader
boot to bootloader (see Q11) and select recovery (use Use the VOL DOWN Key to SCROLL to Recovery and VOL UP Key to select)
via external app
[SIZE=+1]Q13: How to force reboot my frozen device?[/SIZE]
Press and hold the Power button for 10 - 20 seconds, the device will restart and go through the boot-up sequence [source]
(VOL DOWN hold + a quick tap on POWER should force reboot when in bootloader) [source]
[SIZE=+1]Q14: How to charge my device and extend battery life?[/SIZE]Follow Motorola tips:
How do I properly charge my device?
How can I extend my battery life?
[SIZE=+1]Q15: Does rooting/unlocking your phone invalidate its warranty? (In EU)[/SIZE]In short: No. Just the fact that you modified or changed the software of your device, is not a sufficient reason to void your statutory warranty. As long as you have bought the device as a consumer in the European Union.
[source]
[SIZE=+1]Q16: What to do if my battery is fully discharged and not re-charging?[/SIZE]
Motorola said:
If your battery is completely discharged, it may take several minutes for the device to begin charging. The battery needs to charge to a minimum voltage before the system can boot up, and this may take a few moments to achieve.
Click to expand...
Click to collapse
You may have experienced the 'sudden battery drop' : go to Q25 [source]
Also refer to Moto G will not power up (Q28)
[SIZE=+1]Q17: OMG i really bricked my device... Any chance getting it back to life ?[/SIZE]If your device is apparently dead, and does not look like a phone when connected to PC, then have a look at this guide by @Boss442
[SIZE=+1]Q18: How to flash Stock Radio (aka Baseband) / Kernel and why?[/SIZE]Flashing the latest Radio may help if you have problems with poor signal or wifi coverage. Flashing the SS (Single Sim) radio on a Dual Sim device may cause one or both Sims to stop working. Likewise, flashing the radio from a non-CDMA device to a CDMA one, is a very bad idea.
Flashing a newer / different Radio or Kernel may improve battery-life and general performance
ClockWorkMod Recovery or TWRP is required to flash these images.
http://forum.xda-developers.com/showthread.php?t=2649763
[SIZE=+1]Q19: Lost IMEI ? : How to backup / restore PDS partition and why?[/SIZE]On Motorola devices the 'pds' partition contains information specific to your machine: IMEI, MAC address, serial number, etc. This partition can be lost by accidental format or over time due to filesystem corruption. If you have made a backup, there is a good chance you can bring your handset back to life.
==> PDS backup will help to restore lost IMEI. It is a situation when the phone reports that the IMEI is unknown. ; This works like a vaccine, apply before having issue with IMEI, after it will be too late !
Instructions:
**Root Required**
Using ADB you can make a copy of the partition and move it to a safe place (Google Drive?):
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/pds of=/sdcard/pds.img
To restore in the event of corruption or loss:
adb shell
su
dd if=/sdcard/pds.img of=/dev/block/platform/msm_sdcc.1/by-name/pds(assuming you've pushed pds.img to internal SDcard storage first)
If for some reason this doesn't work, maybe your IMEI isn't destroyed but only not "readable" by system (file system issue? misread cluster reading frame ? no idea), in that case you may read the following story : http://forum.xda-developers.com/showthread.php?p=52648789
[SIZE=+1]Q20: HOw to disable/enable auto On/Off screen with Flip Shell?[/SIZE]
for stock rom : (disabling, since it's enabled by default)
install Xposed framework (and reboot)
install and enable MotoMagnetOff (and reboot)
for CM11: (enabling, since it doesn't work by default)
Follow this FAQ
[SIZE=+1]Q21: how to remove the 'unlocked warning' message?[/SIZE]Follow @ffosilva method and default Motorola logo will be back
[SIZE=+1]Q22: Why and How convert Moto G GPe to non-GPe ?[/SIZE]GPe uses EXT4 for it's 'userdata' filesystem, non-GPe uses f2fs. The GPe kernel expects an EXT4 partition and gives an encryption error if there isn't one. So just flashing a custom ROM won't work on GPe.
Converting a GPe MOTO G to a non-GPe Moto G:
(we would need someone to approve this method, and if you made it a different way, please, tell us)
1) Fastboot flash retail US XT1032 stock firmware found here:
http://sbf.droid-developers.org/phone.php?device=14
2) This will wipe the device, replace GPe kernel and radio with stock non-GPe versions and create a new partition table with f2fs filesystem for 'userdata.'
3) Custom ROMs will now work and as will all Motorola Moto G apps.
[SIZE=+1]Q23: How to reboot into 'safe mode'?[/SIZE]
Press power button, on the pop up, either keep pressing 'shut down' [stock] or 'reboot' [AOSP based]
more infos about this feature
[SIZE=+1]Q24: How to keep backups on my 8GB device without loosing space?[/SIZE]
To backup :
Use a micro USB-OTG adapter and a USB-storage
boot to recovery
go to backup and storage > backup to /storage/usbdisk
wait (it is really slower than when done to /sdcard ==> especially when generating md5sum!)
reboot your system
To restore your backup :
Use a micro USB-OTG adapter and the USB-storage where the backup is located
boot to recovery
go to backup and storage > restore from /storage/usbdisk
wait (it is really slower than when done to /sdcard)
reboot your system
Enjoy !
You now have a way to keep all your backups, without over flooding your device's storage ! (make sure you won't loose the external storage and keep it safe!)
[SIZE=+1]Q25: Abrupt Drop Battery Issue (Battery suddenly drops to 0%)[/SIZE]
Description: This issue appears to affect all versions of Moto G; while some people never experience it, others have it frequently. Most likely to occur when tethering / using USB cable. Android versions 4.3 and 4.4.2 are vulnerable.
Solution: Issue fixed in Android 4.4.3.
Kirk Stromberg said:
If anyone else experiences this abrupt drop on your Moto G *after* updating to 4.4.3, we'll need your serial number/IMEI for further investigation and may need to be in more direct contact. Please send an email to:
[email protected]
- with the title "Abrupt Drop" and
-include your serial number (Settings>About Phone>Status) and
- note to please forward to me (Kirk Stromberg).
We'll obviously keep working this here in the forums as well but want to isolate anyone still having this on 4.4.3, especially if it is repeats with some frequency. I know it is reproducible fairly reliably for some of you (tethering/USB cable).
Click to expand...
Click to collapse
https://forums.motorola.com/comment/785885
[SIZE=+1]Q26: Isssues with MMS on boost mobile with Moto G ?[/SIZE]
Apply the following changes :
apns-config.xml
Code:
<apn carrier="Boost Mobile" mcc="311" mnc="870" apn="n.boost.ispsn"
mmsproxy="68.28.31.7" mmsport="80" mmsc="http://mm.myboostmobile.com"
type="default,supl,mms,fota,dun" carrier_enabled="false" protocol="IPV4V6"
roaming_protocol="IPV4V6" bearer="13" />
build.prop
Code:
ro.cdma.home.operator.numeric=311870
ro.cdma.home.operator.alpha=Boost Mobile
ro.telephony.default_network=13
telephony.slteOnCdmaDevice=1
get more here
[SIZE=+1]Q27: Miracast / TV Screen-mirroring / DNLA app not working?[/SIZE]
Description: Android 4.4.2 added a 'Settings > Display > Cast screen' (Miracast) option, but it does not function - missing settings menu.
Solution: (Root Required)
This feature now works correctly with Android 4.4.3. However, you still need to enable the 'Cast screen' settings menu by adding the following line (if not already present) to /system/build.prop:
persist.debug.wfd.enable=1
For quick access to the feature, install: Miracast Widget.
Additionally, 4.4.3 improves compatibility with Allcast and BubbleUPnP, along with other DNLA apps that did not operate correctly in 4.4.2
Simultaneous Internet connection and Screen-mirroring is not possible in Stock Motorola Firmware 4.4.3 or 4.4.4. This may change with a future update or with the release of Android 'L.' Most Custom ROMs do however support this ability.
The utility SecondScreen (root required) allows Moto G's screen resolution to be easily changed when Screen-mirroring - e.g. 720p or 1080p. The app has several additional features such as turning the phone's screen off and disabling haptic feedback in order to save battery usage while Screen-mirroring.
[SIZE=+1]Q28: Moto G will not power up (addition to Q16 and Q25)[/SIZE]
Plug it into the charger
Hold the VOL DOWN key
While still holding the VOL DOWN key, press and hold the POWER key
Hold both keys down for over 120 seconds. This is more than two minutes and will seem like a long time. You might want to time yourself to make sure you hold it longer than two minutes.
After holding the keys down for more than two minutes, release them.
The Flash Boot screen will display, and the Normal Reboot option will be highlighted
Press the VOL UP key and the device will start a normal reboot.
If you have tried the above and it didn't work, try this:
Plug in the phone for 15 minutes.
Proceed to Step 2 above.
Source: https://forums.motorola.com/posts/3d5eadc25d
[SIZE=+1]Q29: 4.4.3 / 4.4.4 update issues[/SIZE]If after getting the update to 4.4.3 / 4.4.4 you encounter some problem, there are several options:
App-specific issues: Some apps may simply not be compatible with the latest version of Android and you have to wait until they are. You could always mention it to the App developer via Google Play.
Anything else: Could be solved be doing a Factory reset: (Back up anything important!)
Setting > Backup & reset > Factory data reset (erase all data on phone)
The best and cleanest way to get to 4.4.4 from a previous version of Android; is to Fastboot flash a Motorola Stock Factory Firmware Image. This can avoid any potential issues that may arise when upgrading via an Over the Air (OTA) update. Also see: "Q7: How to flash Stock Firmware?" in this FAQ.
Stock Factory Firmware Images are available here:
http://sbf.droid-developers.org/phone.php?device=14
When new images are available they are announced here:
http://forum.xda-developers.com/showthread.php?t=2546251
[SIZE=+1]Q30: i encounter '(bootloader) Preflash validation failed' error message when flashing Firmware Image[/SIZE]You may have updated to Android 4.4.4 via firmware image or OTA update. In this case you now also have the latest version of the Bootloader. That is why you get the above output when attempting to flash a 4.4.2 firmware image. ==> simply flash 4.4.4 images instead.
If the error still occurs, even with a 4.4.4 firmware image, then unlocking bootloader will be necessary.
[SIZE=+1]Q31: Various way to fine tune your Moto[/SIZE]Greenify : prevent unwanted apps from awaking device or runing in background (works on both rooted and not devices, but best performances are with rooted+Xposed.
MinFree settings : if you think the moto G (4.4.4) is too aggressive about killing apps to free memory so that you can't switch between two large apps without it killing one app and restarting it. then try tuning MinFree settings, rooted devices only.
[SIZE=+1]Q32: What can i do with my Notification LED?[/SIZE]Actually your device has 2 LEDs [source] and here is how to play with it : http://forum.xda-developers.com/moto-g/development/led-moto-g-led-custom-controls-t2951463
it can be used as a eMMC activity monitoring, or for charging or USB connected!
[SIZE=+1]Q33: Spare space needed? using /cache partition[/SIZE]Moving /data/dalvik-cache to /cache/dalvik-cache to use the 600MB of /cache for something useful
==> only using Dalvik.
==> http://forum.xda-developers.com/moto-g/general/mod-save-data-space-cache-partition-t2942765 (by @Bert98)
[SIZE=+1]Q34: How can I add init.d Support to Stock ROM without using a Custom Kernel?[/SIZE]This can be done by adding the following to: /system/etc/init.qcom.post_boot.sh
Code:
# init.d support
busybox run-parts /system/etc/init.d/
Busybox also required. (Don't know what it is? search a little, it won't hurt you
[SIZE=+1]Q35: I reduced brightness to 0 and got stuck with a black screen?[/SIZE]This appears to be a bug in 'Adaptive brightness.' Turning it off and on should stop this happening.
If you are in this situation, try shining a torch light on the screen at an angle to make out the very dim display. You can also try swiping down the 'quick toggle' notification menu and changing brightness via the sliding bar. [Source]
[SIZE=+1]Q36: I flashed a ROM and GPS has stopped working?[/SIZE]
Flash this 'no-GPS' fix zip via custom recovery.
Alternatively, enter Fastboot mode and type the following commands:
Code:
fastboot erase modemst1
fastboot erase modemst2
[SIZE=+1]Q37: How can i update my bootloader ?[/SIZE]Understand the risks and simply choose between an automated process (for Windows users only) or the step by step one (for Linux users mainly) here
[SIZE=+1]Q35: [?][/SIZE][...]
[SIZE=+1]Q35: [?][/SIZE][...]
[SIZE=+1]Q35: [?][/SIZE][...] *
Forum Rules | New Users Guide | XDA Tour | Report Posts
This FAQ is part of a Recognized Contributor Group Initiative. Please look for a similar FAQ thread when visiting another device forum. A special thanks to everyone who contributed to the production of this FAQ
Reserved for part 2
Stock firmware links for a bunch of Moto devices :
http://goo.gl/Qa5WRW
some usefull lines of commands for any user wanting to know what's going on:
requirements :
On Windows : install Moto G drivers and
On Linux : set your rules following that guide (3. Set up your system to detect your device.) : add to /etc/udev/rules.d/51-android.rules the following code
Code:
#motog normal mode
SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", ATTR{idProduct}==”2e82″, MODE="0666"
#motog debug mode
SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", ATTR{idProduct}==”2e76″, MODE="0666"
#motog fastboot mode
SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", ATTR{idProduct}==”2e80″, MODE="0666"
For specific access by one group of users, add GROUP="[groupname]"
______________________________
______________________________
______________________________
Let's start ! :
in terminal, just type the lines,
in ADB, add "adb" before the commands
if you want not to display the output in terminal, specify the path :
Code:
command > /where_you_want_your_output_to_be_stored/name_you_want_for_the_log
to know if KSM is really turned on : KSM means Kernel Samepage Merging, may not exist on Moto G stock or custom roms
Code:
cat /sys/kernel/mm/ksm/run
to know what modules are running :
Code:
lsmod
install an app from terminal :
Code:
pm install /sdcard/app1.apk
from adb :
Code:
adb install /home/user/app1.apk
(if your .apk is located there )
your kernel crashed?
Code:
cat /proc/last_kmsg
ex : from adb, and stored in /home/user/last_kmsg1
Code:
adb cat /proc/last_kmsg > /home/user/last_kmsg1
an app crashed, you want to know why?
Code:
logcat
ex : from adb and stored in /home/user/myfirstlogever
Code:
adb logcat > /home/user/myfirstlogever
don't have an USB cable ?or adb "other the air" :
connect to your home wifi network (both device and pc)
in settings/dev options/ enable adb on TCP/IP
Code:
adb connect xxx.xxx.xxx.xxx:5555
(the IP is the one displayed in the option you choose previously
and then, since it is connected, catch the log :
Code:
adb logcat > /home/user/myfirstlogever
All commands and syntax used for ADB can be found here
__________________
More is coming
enjoy !
Unlocking Bootloader
Rusty! said:
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed.
* YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Click to expand...
Click to collapse
>>> Unlocking Bootloader will overwrite any data stored on your device, backup your files before proceeding <<<
For 4.4.2, an updated guide is available here
For real GPe devices (not ones with a GPe ROM added on it after the purchase), NO code is needed, simply skip to "3. Unlock"
1- Register to Motorola website
2- get your Device ID
Put your device in fastboot mode (power off, then press the power and volume down buttons simultaneously).
On your desktop, open a command prompt or terminal, and go to the directory where you installed the Android SDK tools (or make sure fastboot is in your $PATH)
At the prompt, type
Code:
$ fastboot oem get_unlock_data
The returned string will be used to retrieve your unlock key.
Example: On a Windows Desktop, the returned string format would be
Code:
$ fastboot oem get_unlock_data
(bootloader) 0A40040192024205#4C4D3556313230
(bootloader) 30373731363031303332323239#BD00
(bootloader) 8A672BA4746C2CE02328A2AC0C39F95
(bootloader) 1A3E5#1F53280002000000000000000
(bootloader) 0000000
On a Mac OS Desktop, the returned string format would be
Code:
INFO0A40040192024205#4C4D3556313230
INFO30373731363031303332323239#BD00
INFO8A672BA4746C2CE02328A2AC0C39F95
INFO1A3E5#1F53280002000000000000000
INFO0000000
Paste together the 5 lines of output into one continuous string without (bootloader) or ‘INFO’ or white spaces. Your string needs to look like this:
Code:
0A40040192024205#4C4D355631323030373731363031303332323239#BD008A672BA4746C2CE02328A2AC0C39F951A3E5#1F532800020000000000000000000000
3- Unlock
Check if your device can be unlocked by pasting this string in the pecific field on the Motorola website, and clicking “Can my device be unlocked?”
NOTE: If your device is unlockable, a "REQUEST UNLOCK KEY" button will now appear at the bottom of that page.
after you got the code type the following :
Code:
fastboot oem unlock <code>
or for GPe devices :
Code:
fastboot oem unlock
and wait your device to reboot !
4- Enjoy
5- to relock, (pointless, isn't it?)
First you'll need a stock firmware for your specific device [make sure the device number is the right one at least...]
Then follow these steps:
Open the zip
Find 'flashfile.xml'
Make sure to check integrity of EACH img/bin files in the stock firmware zip before proceeding (to do that, look at the flashfile.xml)
e.g.:
Code:
<step MD5="daae9a555a3789558ee44f9e1fddc8c5" filename="gpt.bin" operation="flash" partition="partition"/>
check that gpt.bin MD5 is really daae9a555a3789558ee44f9e1fddc8c5 and has not been corrupted during download/unpacking
Prepare your device (boot to fastboot) and start relocking:
Code:
fastboot oem lock begin
Flash in the order:
Code:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0 // note that you may have more or less sparsechunks, FLASH THEM ALL
mfastboot.exe flash system system.img_sparsechunk.1 // alternatively the files could be named system.img_sparsechunk[1-3] instead
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
Finish relocking:
Code:
mfastboot oem lock
Done!
having all this, do you know of anyone who is already working on cyanogenmod and other custom roms and kernels?
toby913 said:
having all this, do you know of anyone who is already working on cyanogenmod and other custom roms and kernels?
Click to expand...
Click to collapse
i don't know, but if the community is cool, calm, willing to work and contribute, thankful and "not flaming people that try to build something" then maybe there will be some devs coming for some work around here
matmutant said:
i don't know, but if the community is cool, calm, willing to work and contribute, thankful and "not flaming people that try to build something" then maybe there will be some devs coming for some work around here
Click to expand...
Click to collapse
well then i'll ask differently do you think that the device needs something like a custom-rom or kernel?
what do you think generally about it?
toby913 said:
well then i'll ask differently do you think that the device needs something like a custom-rom or kernel?
what do you think generally about it?
Click to expand...
Click to collapse
With custom kernels (they generaly are better optimised than stock) we'll get overclock (some extra performance but mostly useless) ; Undervolt (extremely efficient for getting higher battery life when the device is idle ie: nearly no drain in deep sleep contrary to non undervolted device) ; other IO shedulers (that can give better perf in IO : i made some work about this on my old device see here and here and many otehr cool features.
With Custom roms like CM, PA, AOKP, PAC ... we'll get many features as personalizations, theming, performances settings... and many things you could get on stock rooted rom + Xposed, but that's better when things are in the code
But at first, i mean when a kernel/rom is young we'll get instabilities, crashes, maybe some soft bricks : That's the price for cool and fully working Customs
All is based on what you want :
stability (mostly) and simpleness = stay on stock
performance, long lasting battery, fully optimised kernel, extra features, BUT instabilities or littles crashes/drawback = go on Customs
So are you already cooking a kernel for the moto g
Sent from my LG-E610 using xda app-developers app
toby913 said:
So are you already cooking a kernel for the moto g
Sent from my LG-E610 using xda app-developers app
Click to expand...
Click to collapse
No, because i am neither a cooker, nor a developer... Only a Contributor
Code:
adb install packagename.apk
Is going to be easier than using package manager via adb shell.
Rusty! said:
Code:
adb install packagename.apk
Is going to be easier than using package manager via adb shell.
Click to expand...
Click to collapse
thx,
is that full syntax ? no path for app name ?
I'm summing adb in the same location as the apk, or (as I have it) in the path.
Also unlocking your bootloader does still void your warranty, it's only the developer versions that it doesn't.
Rusty! said:
I'm summing adb in the same location as the apk, or (as I have it) in the path.
Also unlocking your bootloader does still void your warranty, it's only the developer versions that it doesn't.
Click to expand...
Click to collapse
ok thx,
i'll correct this.
matmutant said:
ok thx,
i'll correct this.
Click to expand...
Click to collapse
you should remove that part its confusing and unneeded.
also what is falcon_umts
can you or anyone with the device pull the build.prop and post it here.
Dark Passenger said:
you should remove that part its confusing and unneeded.
also what is falcon_umts
can you or anyone with the device pull the build.prop and post it here.
Click to expand...
Click to collapse
Ok, removed.
about falcon_umts : i don't know, but Falcon was one of Motorola's series (i1 was part of the Falson series) but Moto G is part of the XT series ... maybe a codename ; and UMTS is a network system based on GSM
is that what you wanted ?
edit : regarding the build.prop, Falcon is MotoG codename
matmutant said:
Ok, removed.
about falcon_umts : i don't know, but Falcon was one of Motorola's series (i1 was part of the Falson series) but Moto G is part of the XT series ... maybe a codename ; and UMTS is a network system based on GSM
is that what you wanted ?
Click to expand...
Click to collapse
kind of though it would be awesome if you could attach your build.prop here
adb pull
No need for image dumps, the factory images are available here: http://sbf.droid-developers.org/falcon/list.php
Intel Android Devices Root / Temp Recovery Session
social-design-concepts said:
Disclaimer:
Before you proceed to the rooting instructions below, please read this disclaimer:
XDA-DEVELOPERS.COM and I are not responsible for what you are doing to your device. You understand and agree that you are doing this at your own risk.
as for warranty the rule of thumb is if you root you should always consider your warranty voided : i will make no claim otherwise on the subject.
i am just a simple hobbyist from Cinti. OH USA i have no intention to buy devices or users getting mad that they were under some impression this wouldn't void the warranty.
if you root you should always consider your warranty voided
Click to expand...
Click to collapse
Tethered Temporary CWM / TWRP Recovery Session :
Note : This is a Temporary CWM / TWRP Recovery Session for some Intel Devices with locked bootloaders.
This recovery is not installed to the devices and has to be launched from a computer ( tethered ) each time you need to access the CWM / TWRP Recovery. . .
WARNING : This Temporary CWM / TWRP Recovery Session is for some Intel Devices with locked boot loaders.
It is not intended for installing custom roms as if the devices has a locked bootloader the device will fail to boot the unsigned images
Intel Fastboot Tethered Temporary Recovery Session Launcher download :
Current Version : IntelAndroid-FBRL-07-24-2015.7z
Generic Instructions for use better instructions coming later just wanted to get the thread up :
notes :
make sure you have downloaded and installed the adb / fastboot drivers for your device . . .
make sure you have enabled developer options / adb debugging under settings on your device . . .
make sure you have download the latest : UPDATE-SuperSU-vX.Xx.zip and place it on your internal or external_sd
1 : download and extract IntelAndroid-FBRL-07-24-2015.7z some where on your computer.
2 : double click the launcher.bat file to start , type " ACCEPT " case sensitive without quotes to continue
check that the tool is reporting as either :
DEVICE STATUS: ADB-ONLINE
DEVICE STATUS: FASTBOOT-ONLINE
If " DEVICE STATUS: UNKNOWN " please check your cable connection and driver installation under Windows Device Manager
If " DEVICE STATUS: UNAUTHORIZED " please check if your devices is displaying an authorization prompt be sure to check Always allow from this computer and then press ok
3 : select the trigger to launch the Temporary CWM Recovery Session support fastboot oem triggers are :
T1 oem startftm ( very few devices support this command , but its the original used so )
devices supported : coming soon
T2 oem backup_factory ( limited devices support this command )
devices supported : coming soon
T3 oem stop_partitioning ( should work on alot of kitkat builds )
devices supported : coming soon
T4 oem stop_partitioning ( probably works on all devices that are supported (Jellybean , KitKat , Lollipop) )
devices supported : coming soon
4 : after selecting the trigger your device should reboot in to fastboot and begin to copy files to your device
note : if your device hangs at the waiting-for-device screen and you see droidboot CMD Waiting on your devices double check that the fastboot driver installed correctly.
note : if you see unknown oem command the trigger isn't supported by your device.
5 : The temporary cwm recovery session should be started at this point select install zip from the recovery menu using vol up / vol down to navigate and power to select
6 : select install zip from sdcard / external_sd depending on where you placed the file and select the UPDATE-SuperSU-vX.Xx.zip you downloaded earlier
7 : confirm the installation
8 : after install completes reboot your device
note :
some devices have limited space under /system and the supersu app wont install
if you don't see the supersu app on your device attempt to install it from the playstore
more than likely the su binary installed correctly but there want enough room on the device for the app.
This recovery uses the CWM Recovery @vampirefo built for the Dell Venue 8 3830 NoModem original thread : Dell Venue 8, CWM, unsecure boot/recovery
You know it's annoying to find this on so many other forums. with other people taking credit for it. sad face : (
APPRECIATE MY WORK, I DON'T DRINK, SO CLICK HERE DONATE NOW AND BUY ME COFFEE
XDA:DevDB Information
Intel Android FBRL, Tool/Utility for the Android General
Contributors
social-design-concepts
Version Information
Status: Stable
Created 2015-07-28
Last Updated 2015-07-28
Supported Devices List / Trigger
Supported Devices List / Trigger
Acer :
B1-730 T2
B1-730HD T2
A1-830
A1-840FHD T3
A1-840 (HD) T3
Asus :
ME170C T2 & T3
ME176C T2 & T3
Dell :
Venue 7 3730 / Venue 8 3830 All Triggers Should Work
Venue 7 3740 / Venue 8 3840 T3
Venue 7 3741 / T3
Venue 8 7840 T3
Iview :
i700 T2 & T3
Kurio :
Xtreme 7 Only had a chance to test trigger T3
Odys :
intellitab 7
Nabi:
Dreamtab model IN08A trigger T3 reported working
Prestigio :
MultiPad Thunder 7.0i
Tesla :
L7 Tablet T3
Tesco :
Op3n Dott 8 T2 & T3
Toshibia :
Excite 7 T3
Links to devices specific threads / forums
Links to devices specific threads / forums
If you have created a devices specific thread / forum for your devices please PM the link so that i can post a link to it here to make it easier to help new users . . . . Please put Intel Device Specific Thread in the supject . Thank You .
The Concept / Source Code
The Concept / Source Code
Collected Device Dumps / Captured OTA Updates
Collected Device Dumps / Captured OTA Updates
Generic / Tips for Unbricking
Generic / Tips for Unbricking
Ahh!
Just my luck lol. Had a feeling I would end up bricked for some reason, maybe I jinxed myself.
Anyways... everything was going ok, I selected trigger 3 to try first, reboots to droidboot (with "waiting for fastboot command") then I select recovery and get android dude laying down with a red exclamation point coming out his belly and it just said "no command" now I am soft bricked, only getting the USB symbal with the white line under it. Please help!
GeeKerGurL said:
Just my luck lol. Had a feeling I wouls end up beicked for some reason, maybe I jinxed myself.
Try to manually boot to droidboot
Anyways... everything was going ok, I selected trigger 3 to try first, reboots to droidboot (with "waiting for fastboot command") then I select recovery and get android dude laying down with a red exclamation point coming out his belly and it just said "no command" now I am soft bricked, only getting the USB symbal with the white line under it. Please help!
Click to expand...
Click to collapse
We can remote around 1130pm est and I'll get you running v8 correct?
Sent from my XT907 using XDA Free mobile app
social-design-concepts said:
We can remote around 1130pm est and I'll get you running v8 correct?
Sent from my XT907 using XDA Free mobile app
Click to expand...
Click to collapse
Yeah 3830. Thanks a bunch. Now what do I have to do to remote? I am on a win7 PC with 1gig that is so slow I wanna scream. Also I am in another timezone so how long would that be from now?
GeeKerGurL said:
Yeah 3830. Thanks a bunch. Now what do I have to do to remote? I am on a win7 PC with 1gig that is so slow I wanna scream. Also I am in another timezone so how long would that be from now?
Click to expand...
Click to collapse
1 hour 30 minutes
Sent from my XT907 using XDA Free mobile app
social-design-concepts said:
1 hour 30 minutes
Sent from my XT907 using XDA Free mobile app
Click to expand...
Click to collapse
Okie dokie. Ill be here.
social-design-concepts said:
We can remote around 1130pm est and I'll get you running v8 correct?
Sent from my XT907 using XDA Free mobile app
Click to expand...
Click to collapse
Woot!!!YA! no need, I got it back all by myself just had to boot with vol down and go back through the process and everything copied fine and worked this time! :good: thanks a ton for offering to help me though buddy!
BTW trigger 3 works for the 3830 V8 no modem
WOOOHOOOOHOOOOWOOOO! root check cleared, I am SOO happy to finally have root on this thing. Besides my minor hiccup for whatever reason this method was pie too! YAHOO. I went from about to cry to jumping around happy like a crazy person haha.
recovery fstab
What needs to be change for jb 4.2.2?
I am able to open and edit the file.
b.g.
whgarner said:
What needs to be change for jb 4.2.2?
I am able to open and edit the file.
b.g.
Click to expand...
Click to collapse
recovery.fstab may or may not need to be edited for some devices especially if the device doesn't use by label partitioning. What device do you have?
Sent from my XT907 using XDA Free mobile app
asus aa3-600
I have an asus aa3-600-ur10
android 4.2.2
Intel Celeron J1850 Quad-core 2 GHz
21.5" Full HD (1920 x 1080) 16:9
Intel HD Graphics with Shared Memory
2 GB, DDR3 SDRAM
500 GB HDD
The problem I'm having is no usb debugging, only debugging via lan. I can get adb to work but not working with fastboot in the bootloader(droidboot). I have a post about it in this section, search for "aa3-600"
b.g.
Hi, SDC
I know this has been ask before, I searched and couldn't find the answer though, I would like to get the source code for the launchers , I use the Linux version of this method, cause I don't have windows, and would like to convert the recovery.launcher triggers and so forth into a shell script rather that use binary file.
If you have a shell script already can you post it if not, can you post or give me a link to your binary files source code?
tomtom1265 said:
Hi, SDC
I know this has been ask before, I searched and couldn't find the answer though, I would like to get the source code for the launchers , I use the Linux version of this method, cause I don't have windows, and would like to convert the recovery.launcher triggers and so forth into a shell script rather that use binary file.
If you have a shell script already can you post it if not, can you post or give me a link to your binary files source code?
Click to expand...
Click to collapse
I'm going to post the source after I finish getting the thread put together I just wanted to get it up yesterday.
As for doing it through shell scripts the reason its binary is because if /system is mounted or any prebuilt binary has a dependency on a shared library it makes it extremely difficult some times impossible to stop services and unmount /system and such.
But I hope to have everything finish by the end of the day.
Sent from my XT907 using XDA Free mobile app
whgarner said:
I have an asus aa3-600-ur10
android 4.2.2
Intel Celeron J1850 Quad-core 2 GHz
21.5" Full HD (1920 x 1080) 16:9
Intel HD Graphics with Shared Memory
2 GB, DDR3 SDRAM
500 GB HDD
The problem I'm having is no usb debugging, only debugging via lan. I can get adb to work but not working with fastboot in the bootloader(droidboot). I have a post about it in this section, search for "aa3-600"
b.g.
Click to expand...
Click to collapse
You use Linux or windows? If Linux, you may need to use my fastboot binary, anyway if using Linux while in fastboot mode use terminal type lsusb.
Do you see your device listed?
Sent from my T1 using XDA Free mobile app
Root!
Thank you for this!
I successfully rooted my V8 3830 KK4.4 V1.33 no modem with T3 - in about 4 mins. tops.
FYI:
I connected and launched the launcher from the IntellAndroid-FBRL folder. Typed ACCEPT and got the green screen. Chose T3. The tablet rebooted into fastboot and files where loaded, But then fastboot turned red and said "device unauthorized" when CWM popped onto my tablet. (maybe it's suppose to do that, DK) and yes, US debugging was on, I flashed the SU zip, rebooted, all is well. SU updated and working fine. I was able to remove all the crapwear. :laugh:
thank you SDC!
Quick question - Do any of the intel devices have unlocked bootloader?? Thought I read somewhere somebody was able to install a factory 4.3 or 4.2 on a Dell venue and the bootloader unlocked?
I am trying it, but doesent work already?, anybody do it?
According to an article I found online at http://www.gizbot.com/how-to/how-root-android-m-developer-preview-3-on-nexus-devices-027527.html, it's a more complicated process now.
"Google introduced major changes to the kernel in the Android M developer preview 3, which means it won't be easy to gain root access Android M. Hence, users need to flash a custom kernel like Despair Kernel in order to gain root."
---------- Post added at 06:53 AM ---------- Previous post was at 06:28 AM ----------
http://www.ibtimes.co.uk/how-root-n...id-m-build-mpa44g-developer-preview-3-1515927
It seems like rooting Android M Preview 3 is only possible on certain Nexus phones and tablets at this time so Nexus Player users will just have to wait.
@zulu99 is the great developer who provided the modified kernel in order to allow root access so credit goes to him for that. Here are the detailed instructions:
* Download the newboot.img file on to your computer from https://mega.nz/#!WQx2DBYB!kU5f2O_QsgcburdjS8yZAYxRViJb8YD-hKgvwTDXElY and save it to the Android SDK platform-tools folder.
* Download the latest version of TWRP for the Nexus Player from https://dl.twrp.me/fugu/ and save it to the Android SDK platform-tools folder.
* Download the latest SuperSU beta version zip file from http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133 and save it on to your Nexus Player.
* If you're using Windows, search for cmd.exe and run it. Navigate the current directory to the Android SDK platform-tools folder by typing in something like cd c:\androidsdkslim\platform-tools as an example.
* Type in adb devices and see if it displays your device's serial number. If so, you're ready to move on to the next step.
* Type in adb reboot bootloader and wait a few seconds.
* Type in fastboot flash boot newboot.img and wait for it to complete.
* Type in fastboot flash recovery twrp-2.8.7.0-fugu.img and wait for it to complete.
* Use the physical button underneath the Nexus Player to access recovery mode.
* Plug in a mouse or keyboard / mouse in to a micro USB OTG cable connected to your Nexus Player, then accept the TWRP prompt by using the slider at the bottom of the screen.
* Install the latest SuperSU zip file and when it's done, reboot the system. Your device is now rooted.
Is Netflix blocked with root?
No, you can still Netflix and chill with your phone rooted.
Might be a tad bit early to ask. But does this work on the final Marshmallow that was released today?
I found it
aritz007 said:
I am trying it, but doesent work already?, anybody do it?
Click to expand...
Click to collapse
youtu.be/JNI77zNG8OI
Use this link to root your Android M
thanks for this!
Android_Unlocker
I am not responsible for any problems with your smartphone so proceed with caution!!!
REQUIREMENTS
- Windows 10 or Linux
- Python 3.x
- CMD(Windows), PowerShell(Windows) or Terminal(Linux)
INFO
This program makes it easy to unlock bootloaders of various smartphone brands using FASTBOOT and ADB (Android Debug Bridge) following the official unlocking modes and also unlocking for general devices.
ALL DATA WILL BE DELETED AND THE WARRANTY WILL BE LOST
SUPPORTED DEVICES
- Google Pixel Phone
- Huawei
- Nokia-ONLY_8
- Samsung
- Sony
- Xiaomi
- General Devices NEW
- General Devices OLD
INSTRUCTIONS
FOR WINDOWS
- Enable OEM Unlock and ADB Debug on your smartphone (Developer Settings)
- Install Python3 from the official website: https://www.python.org/
- Open the cmd and start the program by typing <dir python.exe> <dir Android_Unlocker-V1.0.0.py>. remember to also write python.exe and Android_Unlocker-V1.0.0.py. ES. C:\python\python.exe C:\Users\<name of your user>\Download\Android_Unlocker-V1.0.0.py
- Follow the instructions displayed in the program
OR LINUX
- Enable OEM Unlock and ADB Debug on your smartphone (Developer Settings)
- Open the terminal and type `sudo apt install python3` to install Python3
- Now type `python3 <dir file Android_Unlocker-V1.0.0.py>` remember to also write Android_Unlocker-V1.0.0.py
- Follow the instructions displayed in the program
LINK GITHUB: FabioFabRob7/Android_Unlocker (github.com)
Nice work! Any idea if this works with the S10+ US Snapdragon model, SM-G975U1? Its bootloader is locked down tight and aside from a "paid service" that unlocks the BL with a generated key. It'd be nice to have a means of doing so that everyone has access to. I guess I'd have to test it to find out, though I thought it'd be worth inquiring with you beforehand as to if it's possible with known BL locked devices where the OEM unlock toggle isn't visible.
I have a Note 9 with a broken screen. No Debug apparently.
Would this enable me to flash a custom recovery that's adb accesible?
SuperIronOut said:
Nice work! Any idea if this works with the S10+ US Snapdragon model, SM-G975U1? Its bootloader is locked down tight and aside from a "paid service" that unlocks the BL with a generated key. It'd be nice to have a means of doing so that everyone has access to. I guess I'd have to test it to find out, though I thought it'd be worth inquiring with you beforehand as to if it's possible with known BL locked devices where the OEM unlock toggle isn't visible.
Click to expand...
Click to collapse
I have not tried. I have only reported the official methods of these brands. So I believe it can work.
Castle2-5 said:
I have a Note 9 with a broken screen. No Debug apparently.
Would this enable me to flash a custom recovery that's adb accesible?
Click to expand...
Click to collapse
You need to enable ADB Debug and OEM unlock from developer settings. I'm sorry
FabioFabRob7 said:
SUPPORTED DEVICES
- Google Pixel Phone
- Huawei
- Nokia-ONLY_8
- Samsung
- Sony
- Xiaomi
- General Devices NEW
- General Devices OLD
Click to expand...
Click to collapse
Does this also support a Huawei VOG-L29?
FabioFabRob7 said:
Android_Unlocker
I am not responsible for any problems with your smartphone so proceed with caution!!!
REQUIREMENTS
- Windows 10 or Linux
- Python 3.x
- CMD(Windows), PowerShell(Windows) or Terminal(Linux)
INFO
This program makes it easy to unlock bootloaders of various smartphone brands using FASTBOOT and ADB (Android Debug Bridge) following the official unlocking modes and also unlocking for general devices.
ALL DATA WILL BE DELETED AND THE WARRANTY WILL BE LOST
SUPPORTED DEVICES
- Google Pixel Phone
- Huawei
- Nokia-ONLY_8
- Samsung
- Sony
- Xiaomi
- General Devices NEW
- General Devices OLD
INSTRUCTIONS
FOR WINDOWS
- Enable OEM Unlock and ADB Debug on your smartphone (Developer Settings)
- Install Python3 from the official website: https://www.python.org/
- Open the cmd and start the program by typing <dir python.exe> <dir Android_Unlocker-V1.0.0.py>. remember to also write python.exe and Android_Unlocker-V1.0.0.py. ES. C:\python\python.exe C:\Users\<name of your user>\Download\Android_Unlocker-V1.0.0.py
- Follow the instructions displayed in the program
OR LINUX
- Enable OEM Unlock and ADB Debug on your smartphone (Developer Settings)
- Open the terminal and type `sudo apt install python3` to install Python3
- Now type `python3 <dir file Android_Unlocker-V1.0.0.py>` remember to also write Android_Unlocker-V1.0.0.py
- Follow the instructions displayed in the program
LINK GITHUB: FabioFabRob7/Android_Unlocker (github.com)
Click to expand...
Click to collapse
Nothing to get excited about... just calls fastboot.exe oem unlock. Pretty useless for most bl locked devices. Title misleading too.
ttesty said:
Nothing to get excited about... just calls fastboot.exe oem unlock. Pretty useless for most bl locked devices.
Click to expand...
Click to collapse
You're right. Just had a look on the Python-Script. This won't unlock my Huawei-Device
Praetoriani said:
Does this also support a Huawei VOG-L29?
Click to expand...
Click to collapse
If Huawei supports unlocking and then you can get the code yes. Anyway try to start the program made by me, select the operating system of your PC and then select Huawei. You will be redirected to Huawei's web page for unlocking. If you manage to get the code you will be asked for the Huawei code in my app and then done this will do everything automatically
ttesty said:
Nothing to get excited about... just calls fastboot.exe oem unlock. Pretty useless for most bl locked devices. Title misleading too.
Click to expand...
Click to collapse
I have reported only the official methods. With xiaomi no problem because all devices support unlocking via the official app. It's just a way to make life easier. NO UNOFFICIAL METHODS ARE SHOWN IN THE APP
FabioFabRob7 said:
I have reported only the official methods. With xiaomi no problem because all devices support unlocking via the official app. It's just a way to make life easier. NO UNOFFICIAL METHODS ARE SHOWN IN THE APP
Click to expand...
Click to collapse
The title is misleading... "
Official Android_Unlocker for almost all smartphone"
No way it's for almost all smartphones.... will fail on a large percentage. Unlock operation not permitted.
It takes less time to run the usual commands instead of running them through your deliverable. It could also have a virus. Not really smart.
ttesty said:
The title is misleading... "
Official Android_Unlocker for almost all smartphone"
No way it's for almost all smartphones.... will fail on a large percentage. Unlock operation not permitted.
It takes less time to run the usual commands instead of running them through your deliverable. It could also have a virus. Not really smart.
Click to expand...
Click to collapse
Try my method before paying for a servire.
FabioFabRob7 said:
Try my method before paying for a servire.
Click to expand...
Click to collapse
Or ask a service center. And see what they tell you
FabioFabRob7 said:
Or ask a service center. And see what they tell you
Click to expand...
Click to collapse
I don't think you understand. The title of the post is bogus. Has nothing to do with paying for a service or service centers.
It's not hard to type 2-4 lines that do the same thing and fails on a large percentage of devices.
ttesty said:
I don't think you understand. The title of the post is bogus. Has nothing to do with paying for a service or service centers.
It's not hard to type 2-4 lines that do the same thing and fails on a large percentage of devices.
Click to expand...
Click to collapse
Do some examples and I add it
Castle2-5 said:
I have a Note 9 with a broken screen. No Debug apparently.
Would this enable me to flash a custom recovery that's adb accesible?
Click to expand...
Click to collapse
If you have TWRP with adb enabled you can access with this. Enter in recovery then adb devices
In order for you title to be correct - your program should be able to provide the unlock codes.. If it doesn't - title is misleading!
Anyone can use the basic fastboot commands - if they have the unlock code - on ie. Huawei - they have stopped providing the code to their customers - Therefor your program is worthless (sorry to say) - If your program could generate the code... Now that would be something!
FabioFabRob7 said:
- Google Pixel Phone
- Huawei
- Nokia-ONLY_8
- Samsung
- Sony
- Xiaomi
- General Devices NEW
- General Devices OLD
Click to expand...
Click to collapse
supports samsung note 20?
nishanloshan said:
supports samsung note 20?
Click to expand...
Click to collapse
This is the official method if is supported now by Samsung
Hi,
I updated my Oneplus 7 pro to OS12, is there any possibility to copy mcfg_sw.mbn to the device, so i can try VoLTE to work??
Thanks.
shtozo_78 said:
Hi,
I updated my Oneplus 7 pro to OS12, is there any possibility to copy mcfg_sw.mbn to the device, so i can try VoLTE to work??
Thanks.
Click to expand...
Click to collapse
You need to habve acces to engineering mode to be able to load mbn on your phone.... But unortunately at the moment there is no a free option to get acces to engineering mode ... You need a token to have acces to engineering mode so you could load your MBN profile...
Secrecy unlock
WARNING - THIS (ORIGINAL) METHOD IS NOT WORKING WARNING - BE CAREFULL REGARDING (your) IMEI SHARING ! You need to enable Developer Options and USB Debugging in the Phone Download the Oppo_Free_Unlock_v1.0.zip Secrecy Auto Unlocker : Open the...
forum.xda-developers.com
Check on this thread to see how you could get a token