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
Testers wanted: Anyone who uses this method, let me know if you can access stock recovery after this method.
Summery
Thanks to the amazing work by our active member @bibikalka, a method was found to unbrick these devices Thread link here. The method he found was slightly tedious for some people, so I've decided to put together a Linux iso that you can boot into on your computer with everything you need to get your device running again. It uses the same methods proposed but makes things easier. This comes with all the necessary drivers, scripts to do everything you need, all the img files needed to flash, a hex editor for advanced users, and more. Before the scripts included in this OS, determining the option (A, B, or C) to take in order to unbrick the device required .part files to be evaluated manually. Now with the custom script, it can quickly evaluate what option to take.
Video Instructions
Brief Instructions
1. Download the Linux iso:
Linux ISO
2. Burn the iso to a USB drive or cd
3. Boot into the operating system
4. Type "root" at the login prompt
5. Right click on the desktop and choose file manager. Go to "aftv2-tools" folder
6. Right click on file manager and press "open in terminal"
7. From device turned off, enter command "./handshake.py", then plug in device. You may need to do this a couple times to get a connection. Try pressing volume keys & power etc to get it connected. See video if you have problems
8. After handshake is complete, run "./reader.sh"
9. After all addresses are read in, run "./determineOption.sh". You should get back a result of A, B, or C
10. Depending on the option returned (A,B,or C), run "./readerSpecialOptionA.sh", "./readerSpecialOptionB.sh", or "./readerSpecialOptionC.sh". This is an optional step but may be useful if you want to back up part files or their were no options available. Back up part files to a usb drive if you want to be safe.
11. Now the actual unbricking. Run "./unbrickOptionA.sh", "./unbrickOptionB.sh", or "./unbrickOptionA.sh" depending on your option. This can take about 40 minutes
12. hold volume up and run "./complete.sh" at the same time to get into TWRP
13. boot into your default operating system on your computer
BE VERY CAREFUL FROM NOW ON
13. We will be installing Fire OS 5.3.1. If you are not installing this ROM, make sure you know what you are doing. Download the ROM:
update-kindle-20.5.5.2_user_552153420.bin
14. Download 5.4.1_1133_stock_recovery_uboot.zip: 5.4.1_1133_stock_recovery_uboot.zip. Without this you could turn your device into a paperweight. This installs stock recovery and a uboot version that MUST be installed. This file was taken from the thread here: how-to-upgrade-to-lollipop-root-gapps
15. Rename the ROM extension from .bin to .zip
16. Transfer the two files to the Fire
17. Do a factory reset. Flash the ROM and uboot&recovery file
18. Reboot! Your device should now be working. It will take about 15 mins to boot up.
Big thanks to @bibikalka for helping work everything out and for the initial unbrick method.
Edit 10/13/21: Fixed Google Drive Link
Linux ISO Changelog
Updated 10/5/16:
*Optomized scripts
*Added "complete.sh" This reboots the device
Updated 9/27/16:
*Added script to auto-detect which unbrick option to use (determineOption.sh)
*Added scripts to write img files to correct addresses ( unbrickOptionA.sh, unbrickOptionB.sh, and unbrickOptionC.sh)
*Added scripts to read in and label part files (readerSpecialOptionA.sh, readerSpecialOptionB.sh, and readerSpecialOptionC.sh)
*Nemo open in terminal fixed
*.part files set to open with ghex by default
Updated 9/24/16:
*Nemo as default file manager
*Updated html page with instructions from forum
well, after seriously struggling with the parent thread mentioned in the OP I've managed to get to TWRP & am just waiting for my win10 machine to install it's updates before attempting to adb push the uboot & zip files for installation back to fireOS.
feels great to see the screen displaying something other than the looping amazon logo after months of frustration. I do not have the words to express my gratitude for @powerpoint45 for an excellent & well thought through tool and walkthrough. special mention also goes out to @bibikalka
gascomm said:
well, after seriously struggling with the parent thread mentioned in the OP I've managed to get to TWRP & am just waiting for my win10 machine to install it's updates before attempting to adb push the uboot & zip files for installation back to fireOS.
feels great to see the screen displaying something other than the looping amazon logo after months of frustration. I do not have the words to express my gratitude for @powerpoint45 for an excellent & well thought through tool and walkthrough. special mention also goes out to @bibikalka
Click to expand...
Click to collapse
great to hear! I hope everything works for you! After you get everything done, can you check if you can get into recovery.
after flashing both zips & rebooting I've now got my working fire (OS 5.3.1.0) back. thank you Mr PowerPoint!
i tried rebooting to recovery & it now takes me to the stock amazon recovery not TWRP..... which is unfortunate.
I did get asked if I wanted to install SuperUser which was a no-brainer YES. although I'm staying offline until I identify a functional (fast) flavour of android to flash. suggestions welcome.
gascomm said:
after flashing both zips & rebooting I've now got my working fire (OS 5.3.1.0) back. thank you Mr PowerPoint!
i be tried rebooting to recovery & it now takes me to the stock amazon recovery not TWRP..... which is unfortunate.
I did get asked if I wanted to install SuperUser which was a no-brainer YES. although I'm staying offline until I identify a functional (fast) flavour of android to flash. suggestions welcome.
Click to expand...
Click to collapse
Good to hear everything is working. Ya TWRP does not work with 5.x bootloader. Good to hear you can get into stock recovery because I had some incidents where I could not get into it. Thanks for responding. The only custom ROM ATM is CM13.
powerpoint45 said:
The only custom ROM ATM is CM13.
Click to expand...
Click to collapse
sorry to trouble you again but do you know where I can find a guide/walkthrough of how to root via adb & install twrp or cwm to allow flashing of a rom & gapps..
I can only find the kingroot method & the CM11 rom discussion. where might I find the CM13 you mentioned?
I have searched fruitlessly. I guess I just need a little guidance to avoid running straight into another brick.
cheers.
gascomm said:
sorry to trouble you again but do you know where I can find a guide/walkthrough of how to root via adb & install twrp or cwm to allow flashing of a rom & gapps..
I can only find the kingroot method & the CM11 rom discussion. where might I find the CM13 you mentioned?
I have searched fruitlessly. I guess I just need a little guidance to avoid running straight into another brick.
cheers.
Click to expand...
Click to collapse
I meant to say CM11. This guide is probably one of the best http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950/page1
This is a bit older one: http://forum.xda-developers.com/fire-hd/general/how-to-downgrade-to-4-5-3-root-device-t3139351/page1
In order to have TWRP, you must have a 4.x bootloader so CM11 would work with it.
Thank you
I have a question I can work downgrade from 5.3.1 to 4.5.3
I'm currently on version 5.3.1
PRInCEI7 said:
Thank you
I have a question I can work downgrade from 5.3.1 to 4.5.3
I'm currently on version 5.3.1
Click to expand...
Click to collapse
yes you should be fine doing that
Unfortunately, did not respond
I worked
MacBook-Air-2:ROOT IP$ ./handshake.py
Waiting for preloader...
Found port = /dev/cu.usbmodem1420
Handshake complete!
In the second step does not respond to the order ./reader.sh
Also tried
/.read_mmc.py 0x0000000 0x1000 0x0000000.part
Does not respond
By the way tried way on more than one device
And tried through the system Max os x and the system arch-custom-firehd67-unbrick100516.iso did not work and also the same result
MY device Amazon Fire HD 6 version 5.3.1 All functions work, but I need to work downgrade to 4.5.3
Is there a solution to my problem
[/SIZE]
@powerpoint45 thanks for the pointers. I am now the proud owned of an hd6 booting straight into cm11 & it's been well worth the wait. I am forever in your digital debt.
gascomm said:
@powerpoint45 thanks for the pointers. I am now the proud owned of an hd6 booting straight into cm11 & it's been well worth the wait. I am forever in your digital debt.
Click to expand...
Click to collapse
sweet!!!
PRInCEI7 said:
Unfortunately, did not respond
I worked
MacBook-Air-2:ROOT IP$ ./handshake.py
Waiting for preloader...
Found port = /dev/cu.usbmodem1420
Handshake complete!
In the second step does not respond to the order ./reader.sh
Also tried
/.read_mmc.py 0x0000000 0x1000 0x0000000.part
Does not respond
By the way tried way on more than one device
And tried through the system Max os x and the system arch-custom-firehd67-unbrick100516.iso did not work and also the same result
MY device Amazon Fire HD 6 version 5.3.1 All functions work, but I need to work downgrade to 4.5.3
Is there a solution to my problem
[/SIZE]
Click to expand...
Click to collapse
I am also getting the same results with my HD 7 4th gen. The handshake completes just fine, but the reader just hangs. When I'm in recovery, I get errors saying the /cache folder failed to mount. I'm thinking the memory is corrupt and there is no way to fix this.
nai1ed said:
I am also getting the same results with my HD 7 4th gen. The handshake completes just fine, but the reader just hangs. When I'm in recovery, I get errors saying the /cache folder failed to mount. I'm thinking the memory is corrupt and there is no way to fix this.
Click to expand...
Click to collapse
Unfortunately it appears that with the latest bootloader on the latest Amazon update that they have disabled these commands (such as reading and writing). Unfortunately if you can't get into recovery with (vol+ & power) then it is currently unrecoverable. Best option for an unrecoverable device would be to buy another motherboard from eBay or some place. They are pretty cheap and easy to replace. I've had to do it a couple times now.
Confused
First you say it should be OK to downgrade:
powerpoint45 said:
PRInCEI7 said:
Thank you
I have a question I can work downgrade from 5.3.1 to 4.5.3
I'm currently on version 5.3.1
Click to expand...
Click to collapse
yes you should be fine doing that
Click to expand...
Click to collapse
Although, it's unclear how, since reports indicate that sideloading older
firmware bricks the device (or, does that only apply to 5.x?).
Then, we learn that the preloader trick (from aftv2-tools) doesn't work anymore:
Code:
[[email protected] aftv2-tools]# ./handshake.py
Waiting for preloader...
Found port = /dev/ttyACM0
Handshake complete!
[[email protected] aftv2-tools]# ./reader.sh
^CTraceback (most recent call last):
File "./read_mmc.py", line 355, in <module>
if msdc_dma_status():
File "./read_mmc.py", line 146, in msdc_dma_status
return False if sdr_read32(MSDC_CFG) & MSDC_CFG_PIO else True
File "./read_mmc.py", line 82, in sdr_read32
check(dev.read(2), b'\x00\x00') # arg check
File "/usr/lib/python3.5/site-packages/serial/serialposix.py", line 450, in read
ready, _, _ = select.select([self.fd, self.pipe_abort_read_r], [], [], timeout)
KeyboardInterrupt
^CTraceback (most recent call last):
File "./read_mmc.py", line 355, in <module>
if msdc_dma_status():
File "./read_mmc.py", line 146, in msdc_dma_status
return False if sdr_read32(MSDC_CFG) & MSDC_CFG_PIO else True
File "./read_mmc.py", line 82, in sdr_read32
check(dev.read(2), b'\x00\x00') # arg check
File "/usr/lib/python3.5/site-packages/serial/serialposix.py", line 450, in read
ready, _, _ = select.select([self.fd, self.pipe_abort_read_r], [], [], timeout)
KeyboardInterrupt
^Z
[1]+ Stopped ./reader.sh
[[email protected] aftv2-tools]# kill %1
[[email protected] aftv2-tools]#
[1]+ Terminated ./reader.sh
[[email protected] aftv2-tools]#
The above is for a 4th gen HD7 with this device showing in 'lsusb':
Code:
Bus 001 Device 006: ID 0e8d:3000 MediaTek Inc.
powerpoint45 said:
Unfortunately it appears that with the latest bootloader on the latest Amazon update that they have disabled these commands (such as reading and writing). Unfortunately if you can't get into recovery with (vol+ & power) then it is currently unrecoverable. Best option for an unrecoverable device would be to buy another motherboard from eBay or some place. They are pretty cheap and easy to replace. I've had to do it a couple times now.
Click to expand...
Click to collapse
BTW, are we sure that this is *disabled* as opposed to _tweaked_?
(e.g. by changing the protocol slightly by, say, requiring an extra byte
or two "confirmation" before execution? has anyone bothered reversing
the bootloader? [Please excuse my ignorance, but would this be handled
by UBOOT, TEE1, or some other component?])
So, what's the current best option for 5.3.1?
---------- Post added at 11:23 ---------- Previous post was at 10:58 ----------
draxie said:
BTW, are we sure that this is *disabled* as opposed to _tweaked_?
(e.g. by changing the protocol slightly by, say, requiring an extra byte
or two "confirmation" before execution? has anyone bothered reversing
the bootloader?
Click to expand...
Click to collapse
OK. So, I found this post by @zeroepoch,
which makes it very clear that said exercise has been performed for the AFTV2...
No reason to believe that this would be different for the Fire HD7...
draxie said:
First you say it should be OK to downgrade:
Although, it's unclear how, since reports indicate that sideloading older
firmware bricks the device (or, does that only apply to 5.x?).
Then, we learn that the preloader trick (from aftv2-tools) doesn't work anymore:
The above is for a 4th gen HD7 with this device showing in 'lsusb':
BTW, are we sure that this is *disabled* as opposed to _tweaked_?
(e.g. by changing the protocol slightly by, say, requiring an extra byte
or two "confirmation" before execution? has anyone bothered reversing
the bootloader? [Please excuse my ignorance, but would this be handled
by UBOOT, TEE1, or some other component?])
So, what's the current best option for 5.3.1?
---------- Post added at 11:23 ---------- Previous post was at 10:58 ----------
OK. So, I found this post by @zeroepoch,
which makes it very clear that said exercise has been performed for the AFTV2...
No reason to believe that this would be different for the Fire HD7...
Click to expand...
Click to collapse
My understanding is that you only need to worry about bricking if You are downgrading to another lollypop ROM. We found out that the device has a fuse that is set in later lollypop ROMs where it will check against the current version. But this check only seems to be on lollipop ROM's. As for the aftv2 protocol, you might be right but I don't know enough about that yet to know. Currently we have no unbrick method for latest bootloader. If you can get into recovery then you could sideload but most can't get into recovery during brick.
I've followed the steps but not into twrp, only screen amazon and reset. I'm not good at English
error trying to unbrick hd6
[[email protected] aftv2-tools]# ./complete.sh
1: 0xd1
4: 0x00 0x00 0x00 0x00
4: 0x00 0x00 0x00 0x01
Traceback (most recent call last):
File "/usr/lib/python3.5/site-packages/serial/serialposix.py", line 468, in read
'device reports readiness to read but returned no data '
serial.serialutil.SerialException: device reports readiness to read but returned no data (device disconnected or multiple access on port?)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "./read32.py", line 69, in <module>
ret = read32(addr, size)
File "./read32.py", line 45, in read32
print_hex_byte(dev.read(2)) # status
File "/usr/lib/python3.5/site-packages/serial/serialposix.py", line 475, in read
raise SerialException('read failed: {}'.format(e))
serial.serialutil.SerialException: read failed: device reports readiness to read but returned no data (device disconnected or multiple access on port?)
[[email protected] aftv2-tools]#
kingwill101 said:
[[email protected] aftv2-tools]# ./complete.sh
1: 0xd1
4: 0x00 0x00 0x00 0x00
4: 0x00 0x00 0x00 0x01
Traceback (most recent call last):
File "/usr/lib/python3.5/site-packages/serial/serialposix.py", line 468, in read
'device reports readiness to read but returned no data '
serial.serialutil.SerialException: device reports readiness to read but returned no data (device disconnected or multiple access on port?)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "./read32.py", line 69, in <module>
ret = read32(addr, size)
File "./read32.py", line 45, in read32
print_hex_byte(dev.read(2)) # status
File "/usr/lib/python3.5/site-packages/serial/serialposix.py", line 475, in read
raise SerialException('read failed: {}'.format(e))
serial.serialutil.SerialException: read failed: device reports readiness to read but returned no data (device disconnected or multiple access on port?)
[[email protected] aftv2-tools]#
Click to expand...
Click to collapse
You are on any version.
You can access to recovery now
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
QLink Scepter 8 TabletBy Hot Pepper Mobile
{
"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"
}
Bootloader Unlocking
& Rooting Guide
For Gen 1 & Gen 2 Models
TABLET MODELS & VARIANTS:
For those members familiar with the firmware restoration thread, there are a total of four model variants of the QLink Scepter 8 tablet: two variants of the Gen 1 model, and two variants of the latest Gen 2 model. Determining which Scepter 8 you have is a very simple two-part check. First, if you don't already know your Android OS version, go to device Settings> About tablet, and locate your Android version. If you are running Android 11 (Go Edition), you have the original Gen 1 model. If you are running Android 12 (Go Edition), your tablet is the latest Gen 2 model. Secondly, you will need to locate the device S/N in order to determine your tablet variant. Your S/N is printed on the manufacturer's label affixed to the exterior of the tablet's rear housing. From the Android OS, you can also locate your S/N by opening device Settings>About tablet>Model. Regardless of whether you have the Gen 1 or the Gen 2, the first two letters of your S/N will be either CF or MD. This is the codification of your tablet variant. To alleviate some of the legwork of rooting, and to keep this thread simple to follow, I have provided boot images pre-patched for Magisk v25.2 systemless root support. I have categorized the download links for each of the boot images in accordance with the respective model and S/N variant. To avoid potential bugs, instabilities, boot loops and the like, it is crucial that you download the boot image that corresponds with your model & variant. OVERVIEW:
This guide outlines step-by-step instructions for unlocking the bootloader and rooting all variants of the Gen 1 & Gen 2 QLink Scepter 8 tablet. This guide also includes a detailed section on properly installing the ADB, fastboot, & USB device drivers on your Windows PC or laptop, as well as steps to troubleshoot & manually update these drivers in the event the tablet is not being recognized while in fastboot mode.
DISCLAIMER:
Unlocking your bootloader and rooting your device are both procedures that carry inherent risks. Because these procedures involve modifying the device from it's stock factory configuration, it is possible to corrupt, damage, or even render your tablet completely inoperable. By proceeding further, you are assuming sole responsibility for the integrity and operability of your device, therefore absolving me of any liability in the event something goes south. I have, however, tested these guides and feel confident that things will go smoothly as long as you follow the instructions carefully. Moreover, I encourage all members to read the instructions fully before starting the steps, in order to first gain a fundamental understanding of the concepts and methods involved.
PLEASE PLAY NICE & FOLLOW XDA RULES:
This thread was created with the intent of being a noob-friendly forum. This simply means that new and inexperienced members are fully welcome here, and will be provided with extra guidance and assistance if needed. Please keep in mind that XDA is a global community of developers, enthusiasts and device users. As such, and although English is the only permitted language in the forums & threads, not all members speak English as their first language, and often rely on text translation tools when asking questions & posting. Accordingly, it is very common for words to be misconstrued, meanings to be misinterpreted, and the context as a whole lost in translation. I ask members to be patient, compassionate and respectful to others on this thread. Those members with the knowledge to do so are urged and asked to help newer members, and recall back when you were new here and others helped you.
Please help me with keeping this thread on point by ensuring that all subject matter herein be kept relevant to the topics of rooting and OEM unlocking the QLink Scepter 8. Any posts about other devices or subject matter run afoul of XDA rules and are subject to removal by moderators -- and potential sanctions imposed upon the offending member. Moreover, an on-topic thread keeps things organized and easier to follow. Thank you for your consideration.
PREREQUISITES:
To unlock the bootloader and root the QLink Scepter 8 tablet, you will need a laptop or PC running on Windows 7/8.1/10/11. (A Mac or Linux machine can also be used. For purposes of this guide, however, I am focusing on a Windows setup.) You will also need the OEM-supplied or a quality equivalent micro USB to USB-A data sync cable. Last but not least, you will need to install compatible USB device drivers for ADB & Fastboot on your PC/laptop. I have included the 15-Second ADB Driver Installer below, under the DOWNLOADS section. This Installer will configure ADB & Fastboot system-wide, and installs the universal Google USB device drivers. I would encourage members to first read the instructions in their entirety prior to actually starting the guide.
•INSTALLING USB DEVICE DRIVERS•
This section is included to install and configure ADB, Fastboot and the proper USB device drivers on your Windows computer. This section can also be used to troubleshoot and fix issues involving your tablet not being recognized by Windows while connected in fastboot mode. If you have already installed the ADB & Fastboot tools (& the proper USB device drivers), and you are not experiencing fastboot recognition issues, you may skip this section and proceed to the bootloader unlocking section.
Many members have reported issues with device recognition while in fastboot mode. I have also noticed a persistence problem with Windows drivers on this tablet. I can manually update the driver using Windows Device Manager, enabling fastboot recognition; yet, once the tablet is disconnected from my PC the updated driver does not always persist, requiring a manual driver update each time fastboot mode is needed. Follow these steps to enable fastboot recognition of your device.
• 1. If you have not yet done so, install the 15-Second ADB Installer from the link below on your Windows PC or laptop. Open the utility and follow the prompts to install the ADB & Fastboot drivers. Next, opt to install ADB system-wide. Lastly, you will be prompted to install the Google USB device drivers. Select Y and install them. You should see an interface informing you that the drivers were successfully installed. NOTE: If you get a warning notification that the drivers are unsigned, select the option to install anyway;
• 2. With your tablet powered off, hold the Power and Volume Down buttons simultaneously until the QLink logo appears, at which time you release the Power button but continue holding Volume Down. When a green Android graphic appears on your display, you are in fastboot mode;
• 3. Connect your tablet to your Windows machine using the OEM-supplied or a quality equivalent micro USB to USB-A data sync cable;
• 4. Open a command window in the path of your ADB/Fastboot directory. Execute this command:
Code:
fastboot devices
If properly connected, the command window will return an alphanumeric string which is synonymous with your tablet serial number. If this occurs, you are finished with this section and may proceed to the instructions for unlocking the bootloader/rooting. If the command window displays Waiting on Any Device, or if your serial number is not displayed, continue with the following steps;
• 5. Keeping your device connected to your Windows PC/laptop, right click your Windows Start icon and select Device Manager. Locate your tablet in the menu. It will likely be located under either the Portable Devices or Android Device heading;
• 6. Right click your device and select Update Driver. Next, select Browse My Computer for Drivers. On the next screen choose the option for Let Me Pick From a List... Now you will see a list of drivers to select from. Depending on the manner in which Windows recognized your tablet in the Device Manager menu, the driver selection menu can vary. If you see an option for Android Device, select that option and then select Android Composite ADB Interface. Or, you may be directly presented with options for Android Bootloader Interface, Android ADB Interface and Android Composite ADB Interface. In any event, choose Android Composite ADB Interface and then click Next. Click Yes in the Update Driver Warning dialogue screen, at which time the drivers will be installed.
• 7. Return to your command window and again execute the fastboot devices command. If your serial number is displayed, your drivers are now properly installed. If you are still experiencing fastboot recognition issues, try using another data sync cable, change USB ports on your computer, and/or reinstall the drivers using the 15-Second ADB Installer.
I. UNLOCKING THE BOOTLOADER:
If you plan on rooting your tablet, this step is mandatory. If your bootloader is already unlocked and you only wish to root your device, skip down to the rooting instructions in the next section below.
WARNING: Unlocking your bootloader forces the device into a factory data reset, which will effectively wipe all saved user data from the device. Make a backup at this point if there are files and media on your tablet that you wish to keep.
INSTRUCTIONS:
1. Enable Developer Options on your tablet by going to device Settings>About tablet and tap Build number approximately seven times. Android will notify you that Developer Options are enabled; this menu will appear under device Settings>System>Advanced.
2. Enable USB Debugging and OEM Unlocking in the Developer Options menu. NOTE: Users have reported the OEM Unlocking option being greyed-out unless you are signed in to your Google account.
3. Now to boot into fastboot mode, and this particular step is extremely important. Android 10 introduced a new fastboot mode for dynamic partitions, known as FASTBOOTD, which is relocated from the bootloader to userspace. This particular fastboot mode supports resizeable partitions within the dynamic scheme, and enables the user to create, resize and delete various logical partitions. However, FASTBOOTD mode cannot be utilized to unlock the bootloader, and will not recognize the unlock command. As such, the user must rely upon legacy fastboot mode in order to unlock the bootloader. From stock recovery mode, you may simply choose the option to reboot to bootloader. DO NOT CHOOSE THE OPTION TO ENTER FASTBOOT, as this option will boot to FASTBOOTD. From the Android OS, you can boot into legacy fastboot mode by executing:
Code:
adb reboot bootloader
Once you see a green Android graphic appear in the center of your display, you are in the correct fastboot mode.
4. Connect your tablet to your PC/laptop using the OEM-supplied or a quality equivalent micro USB to USB-A data sync cable. Next, open a command window in the path of your ADB/Fastboot directory. Check your connection by executing this command:
Code:
fastboot devices
If you are properly connected, the command window will return an alphanumeric string synonymous with your device's serial number. If you do not see this, there is a problem with communications between your tablet and PC/laptop. To troubleshoot the issue, switch to another USB port, try another data sync cable, and/or reinstall the ADB/Fastboot drivers on your PC or laptop. Also, see my instructions above on installing USB device drivers on your Windows computer;
5. Once a proper connection has been verified, execute this command:
Code:
fastboot oem unlock
Once you see the Okay notification in the command window, your bootloader is now unlocked. Execute this command:
Code:
fastboot reboot
Your tablet will now initiate a factory data reset and then reboot into the initial setup for the Android OS.
II. ROOTING THE QLINK SCEPTER 8
Now that the bootloader has been unlocked, rooting this tablet is very straightforward. Again, I have provided pre-rooted boot image files in the DOWNLOADS section for all four models & variants.
INSTRUCTIONS:
A. Gen 1 QLink Scepter 8Android 11 (Go Edition)
NOTE: If your tablet is running Android 12 Go Edition, you're in the wrong place. Skip down to the next section.
1. Download the Gen 1 patched boot image that matches your S/N variant using the links below, and save the file on your PC/laptop in the ADB/Fastboot directory. Note that the file is named patched_boot.img. The flashing command below assumes that you leave this file name unchanged;
2. Go to device Settings>About tablet and tap Build number 7 times or until Developer Options are enabled. (This step is necessary if you unlocked your bootloader using the previous section, due to the factory data reset.) Enable USB Debugging in the Developer Options menu;
3. Power your tablet off. Hold the Power and Volume Down keys simultaneously until the QLink logo appears, at which time you release Power but continue holding Volume Down. The green Android will appear on the display to indicate fastboot mode;
4. Connect your tablet to your PC or laptop using a quality data sync cable. Verify your connection using the instructions in Step 4 of the bootloader unlocking section above;;
5. Once a solid connection is verified, execute these commands:
Code:
fastboot flash boot patched_boot.img
fastboot reboot
NOTE: Your active boot slot should be boot_a. Regardless, the above command flashes your active slot by default, without having to specify slot _a or _b.
Upon reboot, your tablet will be rooted with the latest Magisk systemless root strategy. If you do not see the Magisk app or the placeholder stub in your app drawer, go ahead and download the latest version from the link below and install the APK on your tablet. Open the Magisk app, grant the prompted permissions, and follow any prompts to complete setting up the root environment.
B. Gen 2 QLink Scepter 8Android 12 (Go Edition)
NOTE: If your tablet is running Android 11 Go Edition, you're in the wrong place. Go back to the previous section. .
1.Download the Gen 2 patched boot image that matches your S/N variant and the empty vbmeta.img using the links below, and save the files on your PC/laptop in the ADB/Fastboot directory. Note that the boot image file is named patched_boot.img, and the vbmeta image is named vbmeta.img. The flashing commands below assume that you leave these file names unchanged;
2. Go to device Settings>About tablet and tap Build number 7 times or until Developer Options are enabled. (This step is necessary if you unlocked your bootloader using the previous section, due to the factory data reset.) Enable USB Debugging in the Developer Options menu;
3. Power your tablet off. Hold the Power and Volume Down keys simultaneously until the QLink logo appears, at which time you release Power but continue holding Volume Down. The green Android will appear on the display to indicate fastboot mode;
4. Connect your tablet to your PC or laptop using a quality data sync cable. Verify your connection using the instructions in Step 4 of the bootloader unlocking section above;;
5. Once a solid connection is verified, execute this command:
Code:
fastboot flash boot patched_boot.img
Now, continuing in fastboot mode, you will need to disable dm-verity/Android Verified Boot (AVB) by flashing an empty vbmeta.img via executing the following command:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Next, execute this command to reboot your device:
Code:
fastboot reboot
Upon reboot, your tablet should now be rooted with the Magisk systemless root strategy. If you do not see the Magisk app or the stub placeholder in your app drawer, go ahead and download the latest version from the link below and install it on your tablet. Open the Magisk app, grant the prompted permissions, and follow any prompts to update Magisk and/or complete setting up the root environment.
IMPORTANT NOTE:
In the unfortunate event you have a mishap with rooting your tablet and get stuck in a boot loop, or if your tablet will not otherwise boot into the Android OS, have no worries. My tutorial on firmware restoration for the QLink Scepter 8 will revert your device back to its original stock factory state. You can then return here and give it another try.
QLink Scepter 8 Firmware Restoration Guide
DOWNLOADS:
• 15-Second ADB Installer
• Gen 1 (CF) Patched Boot Image
• Gen 1 (MD) Patched Boot Image
• Gen 2 (CF) Patched Boot Image
• Gen 2 (MD) Patched Boot Image
• Empty vbmeta.img
• Official Magisk Releases / GitHub Repo
THANKS & MENTIONS:
Thanks goes out to Hot Pepper Mobile CEO Shawn Sun and Support Specialist Joshua G for providing stock firmware images for this device.
Also, I wish to recognize and thank @13lack13ox for being a huge help to thread members at times when I was not able.
For some reason, I'm stuck on the part where you have to use the fastboot option. So basically, I got my tablet in fastboot mode (the secondary one with the green android graphic), but when I tried to use the adb function, it doesn't detect my tablet. And also, the command, "fastboot devices" doesn't do anything, and when I try to use "fastboot device" it just says waiting for any device and just... stays there, not detecting my tablet. I tried multiple computers, tried both PowerShell and the command prompt with admin privileges, to no avail. For information, it worked when my tablet was on my tablet is the V9 firmware, but it slightly newer since I just updated to V9_20220224... so maybe that might have something to do with it...
64Star said:
For some reason, I'm stuck on the part where you have to use the fastboot option. So basically, I got my tablet in fastboot mode (the secondary one with the green android graphic), but when I tried to use the adb function, it doesn't detect my tablet. And also, the command, "fastboot devices" doesn't do anything, and when I try to use "fastboot device" it just says waiting for any device and just... stays there, not detecting my tablet. I tried multiple computers, tried both PowerShell and the command prompt with admin privileges, to no avail. For information, it worked when my tablet was on my tablet is the V9 firmware, but it slightly newer since I just updated to V9_20220224... so maybe that might have something to do with it...
Click to expand...
Click to collapse
Sounds like you have a common driver issue. Do this: with your device connected to your PC in fastboot mode, right click your Windows start button and open Device Manager. What is your tablet showing up as? We will need to update your driver. I can walk you through it. Did you install the Google driver from the 15-Second ADB Installer? I am nearly finished writing a guide on properly installing the device drivers. I will link it here when posted. It will give you a detailed step-by,-step outline. I don't think it's an issue with the firmware builds. Fastboot detection issues are common with this tablet due to some type of instability with driver persistence. For example, I often need to update my driver every time I use fastboot mode because, for some odd reason, the updated driver doesn't persist once the tablet is disconnected from the PC and then reconnected.
i dont have this tablet but another hot pepper device called the poblano. with that i was able to boot into ffbm from the bootloader and have root adb access. then i ran dd on my boot partition and patched it with magisk and flashed it back
wondering if hot pepper still makes their devices like that or they patched it. either way props to you for getting the fw straight from the oem
luridphantom said:
i dont have this tablet but another hot pepper device called the poblano. with that i was able to boot into ffbm from the bootloader and have root adb access. then i ran dd on my boot partition and patched it with magisk and flashed it back
wondering if hot pepper still makes their devices like that or they patched it. either way props to you for getting the fw straight from the oem
Click to expand...
Click to collapse
The Scepter 8 does not ship with adb root shell (adbd) enabled. In fact, the bootloader was not even intended to be unlocked. The unlock command is disabled in standard fastboot mode. Luckily, the Scepter 8 is integrated with a second fallback fastboot mode, which we were able to use to to the oem unlock.
Many AllWinner tablets and other Chinese devices do, as you pointed out on your Hot Pepper device. When the Scepter 8 was first released I was able to pull a boot image using a Phoenix Suite tool that had been reverse engineered and modded. As luck would have it, I got rid of the tablet and lost my files along with access to the Phoenix Suite tool. So I've been weeks quarreling with Hot Pepper Mobile to provide firmware and the kernel source code. To their credit, the Hot Pepper CEO and support team were very helpful once they understood what I needed. Hot Pepper's software developers are in China, so a language translation issue hindered my request for some time.
Anyway thank you for your kind words and it is a pleasure making your acquaintance.
@64Star I have updated the thread above with some detailed instructions on updating your device drivers. Hope this helps.
Viva La Android said:
@64Star I have updated the thread above with some detailed instructions on updating your device drivers. Hope this helps.
Click to expand...
Click to collapse
It does, I've unlocked the bootloader and now i'm gonna go root it. Thanks for your help!
I have an unfortunate update: When I went to turn on my tablet, I've noticed there was a noticeable crack on the top left corner of the screen... and then when I tried to use it... the touchscreen no longer functions. I have no clue where that crack came from, cause that wasn't there yesterday, and I've kept it safe in a drawer until now, so I have no clue how it's possible. Guess the software isn't the only thing that's cheap, cause my 2020 Moto G Power survived way worse without even a single crack.
TL,DR: Touch screen somehow broke overnight, meaning I can't get past the setup screen, so GG no re, this $10 qlink tablet ****ing sucks.
64Star said:
I have an unfortunate update: When I went to turn on my tablet, I've noticed there was a noticeable crack on the top left corner of the screen... and then when I tried to use it... the touchscreen no longer functions. I have no clue where that crack came from, cause that wasn't there yesterday, and I've kept it safe in a drawer until now, so I have no clue how it's possible. Guess the software isn't the only thing that's cheap, cause my 2020 Moto G Power survived way worse without even a single crack.
TL,DR: Touch screen somehow broke overnight, meaning I can't get past the setup screen, so GG no re, this $10 qlink tablet ****ing sucks.
Click to expand...
Click to collapse
@64Star I hate to hear that but I know exactly how it goes. I've cracked many a screen in my day. But, on a positive note, if you have the extra funds, there are a ton of these tablets available on eBay within the $35 to $40 price range.
Viva La Android said:
@64Star I hate to hear that but I know exactly how it goes. I've cracked many a screen in my day. But, on a positive note, if you have the extra funds, there are a ton of these tablets available on eBay within the $35 to $40 price range.
Click to expand...
Click to collapse
LOL really turning a profit!
13lack13ox said:
LOL really turning a profit!
Click to expand...
Click to collapse
Haha. No doubt
Sorry about the delay on TWRP guys. My mounting issues are actually encryption issues. TWRP isn't decrypting the /userdata or /vendor partitions with the default key. I'm going to chat with one of my friends over at TeamWin and see if I can get a little guidance.
Viva La Android said:
@64Star I hate to hear that but I know exactly how it goes. I've cracked many a screen in my day. But, on a positive note, if you have the extra funds, there are a ton of these tablets available on eBay within the $35 to $40 price range.
Click to expand...
Click to collapse
You really expect me to shell out around 35$ to 40$ on a slow, laggy 10$ tablet just to experiment on? Hahahahahaha....
Spoiler
Perhaps
64Star said:
You really expect me to shell out around 35$ to 40$ on a slow, laggy 10$ tablet just to experiment on? Hahahahahaha....
Spoiler
Perhaps
Click to expand...
Click to collapse
Not really. I was only providing you info as to where they were available. I found one for $19 which is more than I really wanted to give.
As it stands now,.all the lag is gone in mine. I debloated everything that wasn't essential for normal operations. Then I edited the system/build.prop to increase responsiveness and I limited background apps & processes. Finally, I installed a kernel tuner and set the LMK to very aggressive, tweaked the I/o scheduler parameters, and increased entropy from the available pool. And set SELinux to permissive mode. I'm using Nova Launcher Premium with the launcher locked into memory. Believe it or not, the tablet is now very responsive considering the specs. I'm looking into overclocking the CPU a bit, but 1.46 GHz seems to suffice once RAM is optimized. It's a difference in night and day. It's good for a project tablet but that's about it.
There's another government tablet floating around called the Maxwest Nitro 7Q. 4G/LTE supported with a lot better specs. I think I have one located to buy for cheap.
Lots of tweaks it doesnt run too bad just removing bloatware. Would be cool to get your params on your tweaks etc. If you ever got time could you post it up? Maybe the rom you were talking about in another post has all that included? Anyways if not no biggie, this thing is just for playing around on.
13lack13ox said:
Lots of tweaks it doesnt run too bad just removing bloatware. Would be cool to get your params on your tweaks etc. If you ever got time could you post it up? Maybe the rom you were talking about in another post has all that included? Anyways if not no biggie, this thing is just for playing around on.
Click to expand...
Click to collapse
Absolutely. I'll list those for you here in just a little bit. I have a pure stock ROM built with a TWRP installer, but my TWRP has run into a snag. I've reached out to TeamWin for guidance on that.
All in good time, man. Just glad someone with knowledge is doing all this. Wish I could help more. My ability to program and compile is equivalent to stick poking. I've done it once with aosp 6 that was awhile ago.
13lack13ox said:
All in good time, man. Just glad someone with knowledge is doing all this. Wish I could help more. My ability to program and compile is equivalent to stick poking. I've done it once with aosp 6 that was awhile ago.
Click to expand...
Click to collapse
You seem to know your way around the Android OS pretty well. I'm a developer in training myself. Learning every day. Yeah AOSP 6, I still love working with the Marshmallow builds.
Ok first things first. I notice a huge performance boost from some kernel level mods. Here is a link to Kernel Toolkit. Install both APKs. https://mega.nz/folder/QYwA0QTA#O_Zg3h_iVkHOdeyU_yOmLw
First go to the CPU heading and change the scaling governor to Ondemand. Under CPU Governor Params, tap on Performance Profile and select Maximum Performance (you may personally want to scale back to Aggressive or Balanced, depending on your need for battery life). Now, close Kernel Toolkit and restart the app. Next go to the I/O heading. Choose kyber as the I/o scheduler and set the read ahead buffer to 512 KB. Go down to ZRAM and increase to the maximum of 1000 MB. Set Swappiness to 100. Go over to the Profiles heading, create a profile will all settings and give it a name recommended from the list. When complete, tap on the profile, select save settings and then apply settings.
Now go to the menu button in the upper left of the app. Go down and enable Apply Settings on Boot. Select All and set a 5 second delay.
Next, download a build.prop editor from Play Store. There are tons of free ones and any will suffice. Make a backup of your system/build.prop before you tweak anything. Open the editor and grant root permission.
For build.prop edits, locking your launcher into memory helps a lot with responsiveness. Add this line to system/build.prop
ro.HOME_APP_ADJ=1
This basically prevents the launcher from being killed by Android's native LMK.
To increase touch responsiveness, add these lines as well.
debug.performance.tuning=1
video.accelerate.hw=1
Disable the boot animation for faster boot time.
debug.sf.nobootanimation=1
Reboot to enable the tweaks.
Give these a try and let me know your feedback. I'm working on a few more mods to optimize this tablet and I'll keep you posted on those as well.
Thx great changes so far. Yeah more "snappyness" for sure. I'll have to play around and open up as much as i can swap around.
I can't change I/O scheduler though, I get a contact developer message.
13lack13ox said:
Thx great changes so far.
Click to expand...
Click to collapse
Yw. Do you notice a decent improvement?
This post records how I combine many tutorials online and finally enable VOLTE and VoWifi on my Realme GT Neo 2 while the toggles are not available at the beginning.
TLDR: Most Realme devices support VOLTE and VoWifi, but the toggles may not be available in countries where Realme is not sold officially. However, they could be enabled by editing the build.prop file. Root and Magisk are necessary. Using Magisk, services like Google Pay can still work properly (price is potentially less security).
As we all know, most Realme devices support VOLTE and VoWifi, and usually you can find and activate them easily in Settings->Mobile network->SIM-> SIM info & settings. There are many tutorials on the website. However, in countries where Realme is not sold officially, you may not find these 2 toggles. I'm not sure about the exact reason but some are saying that local operators have strict whitelist policy (like ATT and TMobile), and of course a device sold only overseas won't be on it.
My situationI bought a Chinese version Realme GT Neo 2 and the bands are compatible with Tmobile 4G (link). After getting the phone, I refer to this post to flash the global version firmware. My operator is Mint, a mvno of Tmobile and I cannot find VOLTE or VoWifi toggles. After reading this post and using an app called ForceLTE, I'm able to use 4G data. But whenever I make a phone call, the signal jumps back to 3G and data becomes H+(HSDPA). Recently Mint sent me a message, saying that they are retiring 3G soon and my device is not compatible. After a certain date, my phone will not be able to make/receive phone calls if still relying on 3G.
IMEM check fails on Tmobile, Mint, and ATT websites.
On Xiaomi devices there's a code used to activate VOLTE directly, on Oneplus devices you can use log app, but no similar way can be found for Realme devices.
This method I find could be applied to other Realme devices in other countries when the toggles are not available in SIM info & settings.
DisclaimerPlease try the posts I mentioned first.
This method requires root. Take your own risk for any of your behaviors.
I'm not responsible for any of your losses (including, but not limited to device, finance, data, personal info)
Device infoRealme GT Neo 2 chinese version
Global version firmware (RMX3370_11_C.02) via TWRP
Bootloader locked after flashing the firmware
Steps1. Unlock the bootloader (refer to this post). Attention: unlock will get all data wiped!
2. Install TWRP (refer to this post) and Magisk (refer to this post).
Attention: even after you flash TWRP.img to the recovery partition, if you keep using stock firmware (no matter what region/version), recovery will go back to stock one after the first time you boot to the system. You'll have to install Magisk (or use 3rd party firmware) to keep TWRP
3. Install MagiskHide props config (refer to this post) to allow us to edit the build.prop file. It is in system partition (ext4, read-only), and can no longer be edited directly (even if you try to remount it in TWRP or ZArchiver with -rw).
4. Install a terminal emulator from google playstore. Android is a linux system, imagine this app as a window you can open on your PC with linux to input commands.
5. In the emulator,
5.1 type "su" and enter
5.2 type "props" and enter
{
"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"
}
5.3 type "5" and enter (Add/edit custom props)
5.4 type "n" and enter (New custom prop)
5.5 type "persist.dbg.ims_volte_enable" and enter (the prop we want to add)
5.6 type "1" and enter (enter your desired option)
5.7 type "y" and enter (Enter y(es), n(o), e(xit) or an option from above)
5.8 type "n" and enter (do you want to reboot now)
5.9 repeat step 5.3-5.8 for the following props:
persist.dbg.ims_volte_enable, type "1" in step 5.6
persist.dbg.volte_avail_ovr, type "1" in step 5.6
persist.dbg.vt_avail_ovr, type "1" in step 5.6
persist.dbg.wfc_avail_ovr, type "1" in step 5.6
persist.radio.rat_on, type "combine" in step 5.6
persist.radio.data_ltd_sys_ind, type "1" in step 5.6
persist.radio.data_con_rprt, type "1" in step 5.6
persist.radio.calls.on.ims, type "1" in step 5.6
In step 5.8 after you finish entering the last prop, type "y" and enter (reboot now)
6. After reboot, check whether 2 toggles are there in Settings->Mobile network->SIM-> SIM info & settings
7. If you still want to properly use apps like Google Pay after root, refer to this post
Test if VOLTE and 4G network work1. In settings->Notifications & status bar->Status icons, make sure you turn on VoLTE, VoWiFi and Mobile network
2. If you are connected to a wifi and VoWifi works, you should see a small wifi sign above telephone sign in status bar, like this
In addition, for Tmobile, in Settings->Mobile network->SIM1, the Carrier is shown as T-Mobile Wi-Fi Calling (for mvno like mint, don't forget to turn it on on mint website->personal settings first).
3. Disconnect the wifi, you should see "4G" above the network sign, as well as VoLTE sign in the status bar. Turn on data, make a phone call (such as voicemail), minimize the window, check if "4G" sign is still there. Finally, with the call going on, try openning a website like Google. If "4G" sign is there during the whole process, congratulations!
Let me know if this works for you, or if you have any questions/suggestions. Thanks!
Worked for me thanks. Couldn't get volte registered on network. But I now have my toggles.
andrew202 said:
Worked for me thanks. Couldn't get volte registered on network. But I now have my toggles.
Click to expand...
Click to collapse
Hi, thanks for the reply and it's good to hear that. I just updated the steps to check VoWifi and VoLTE, do they work for you? If not, try this post (developer options + ForceLTE) and reboot.
darkhunter9 said:
Hi, thanks for the reply and it's good to hear that. I just updated the steps to check VoWifi and VoLTE, do they work for you? If not, try this post (developer options + ForceLTE) and reboot.
Click to expand...
Click to collapse
No my ims status is not registered. I spoke with my isp telus. Basically device not on list I won't get volte to work. So guessing the only option is some sort of spoofing.
andrew202 said:
No my ims status is not registered. I spoke with my isp telus. Basically device not on list I won't get volte to work. So guessing the only option is some sort of spoofing.
Click to expand...
Click to collapse
Please do not give up hope. Using MagiskHide props you can even change your device name (RMX3370). Probably one plus device would be a good choice to fake.
GOOD JOB! I have a rmx3366, Realme GT Explorer Master Edition with the original chinese version firmware(RMX3366_11_A.16), realme UI v2.0. Do you think I can follow your steps without flashing the global version firmware?
I will be ready to go with Tmobile 2g for voice/text otherwise.
piapiapia said:
GOOD JOB! I have a rmx3366, Realme GT Explorer Master Edition with the original chinese version firmware(RMX3366_11_A.16), realme UI v2.0. Do you think I can follow your steps without flashing the global version firmware?
I will be ready to go with Tmobile 2g for voice/text otherwise.
Click to expand...
Click to collapse
Yes I believe the method should work for most Realme devices, even with UI 2.0.
If you have your bootloader unlocked, feel free to give it a try without flashing global firmware. All properties you set in MagiskHide props config are reversible. Start from step 2.
If your bootloader is still locked, the unlocking process will wipe all data anyway (for personal info security). For a better chance, I suggest to flash the global firmware. I'm not sure whether Chinese version firmware has any restriction (software side) on specific 4G bands used by carrier in US/other countries.
darkhunter9 said:
Yes I believe the method should work for most Realme devices, even with UI 2.0.
If you have your bootloader unlocked, feel free to give it a try without flashing global firmware. All properties you set in MagiskHide props config are reversible. Start from step 2.
If your bootloader is still locked, the unlocking process will wipe all data anyway (for personal info security). For a better chance, I suggest to flash the global firmware. I'm not sure whether Chinese version firmware has any restriction (software side) on specific 4G bands used by carrier in US/other countries.
Click to expand...
Click to collapse
It is helpful! Thank you! My phone does not have a global version, but it works well with Tmobile so far except the volte part. I will try on the Chinese stock firmware.
piapiapia said:
It is helpful! Thank you! My phone does not have a global version, but it works well with Tmobile so far except the volte part. I will try on the Chinese stock firmware.
Click to expand...
Click to collapse
Did a little bit search and it seems what you said is a sad truth. Good luck bro!
help me i have followed you but its not successful
Phan Đức Nam said:
help me i have followed you but its not successful
Click to expand...
Click to collapse
Sorry can you please provide some more info or description?
darkhunter9 said:
Xin lỗi, bạn có thể vui lòng cung cấp thêm một số thông tin hoặc mô tả được không?
Click to expand...
Click to collapse
my neo2 bought in china, i have moved my rom to russia (a.02) and some other versions are not working
Phan Đức Nam said:
my neo2 bought in china, i have moved my rom to russia (a.02) and some other versions are not working
Click to expand...
Click to collapse
Did you do step 5? I didn't see "(active)" behind your "5 - Add/edit custom props". So basically, these props are not added to magisk successfully. In addition, in your screenshot I see 5G signal available. If that's the case there's really no need to worry about 4G VOLTE.
darkhunter9 said:
Did you do step 5? I didn't see "(active)" behind your "5 - Add/edit custom props". So basically, these props are not added to magisk successfully. In addition, in your screenshot I see 5G signal available. If that's the case there's really no need to worry about 4G VOLTE.
Click to expand...
Click to collapse
I did step 5 it didn't work so it failed, my 5G icon is Theme only
Phan Đức Nam said:
I did step 5 it didn't work so it failed, my 5G icon is Theme only
Click to expand...
Click to collapse
Maybe check firmware starting with C and RUI3 then. Sorry I cannot provide a solid solution.
darkhunter9 said:
Maybe check firmware starting with C and RUI3 then. Sorry I cannot provide a solid solution.
Click to expand...
Click to collapse
I am in RUI 3 C.06 RU region but still not working
Phan Đức Nam said:
I am in RUI 3 C.06 RU region but still not working
Click to expand...
Click to collapse
As I said, somehow these custom props are not added to your Magisk successfully, as 5 is not active in your screenshot.
I haven't done any of the steps, but the weird thing is, is VoLTE enabled by default?
I use Google Phone instead of built-in call app, and it shows HD next to the numbers. Does it mean VoLTE is enabled?
My model is RMX3370, Chinese version, running Realme UI 3.0, RMX3370_11_C.08
JohnVo said:
I haven't done any of the steps, but the weird thing is, is VoLTE enabled by default?
I use Google Phone instead of built-in call app, and it shows HD next to the numbers. Does it mean VoLTE is enabled?
My model is RMX3370, Chinese version, running Realme UI 3.0, RMX3370_11_C.08
View attachment 5666647
Click to expand...
Click to collapse
Not necessarily. The best way to check is if you are on a call check if you can still access the internet using mobile data. Without VoLTE, the modem shifts to 3G/2G, and you can't use mobile data simultaneously.
Hey XDA,
I felt obliged to contribute since the following steps worked for me and I got VoLTE and WiFi Calling switches in settings in my Realme GT Neo 2 global version RMX3370 that is on Freedom Mobile in Canada.
All factory, no root required, no bootloader unlock required.
May work on other Realme models.
Source: https://realme-gadgetlife.net/how-to-enable-volte/ (in Japanese, I used Google Translate). I can't remember where I found this link, all credits go to where they are due.
Steps, check pictures in the above link:
1. Enable Developers Options and USB Debugging (search online if needed)
2. Connect your phone to a Windows laptop
3. On the phone choose connection type Transfer files / Android Auto
(first time you will be prompted on your phone if you want to allow USB connection from this PC, choose Yes)
4. On the laptop install platform tools, open a command prompt and change directory to where they are installed
5. Enter command "adb devices"
6. The output should say:
List of devices attached
<your realme serial number> device
7. Enter command: "adb reboot fastboot"
8. The phone will enter the fastboot mode and display language selector. No need to do anything on the phone.
9. Enter command: "fastboot reboot recovery"
10. Nothing changes on the phone, no need to touch it this time either
11. Enter command: "adb devices"
12. The output will be:
List of devices attached
<your realme serial number> recovery
Here I installed realme Software&Driver Update tool from
Software Update - realme (India)
Update the latest software version on your realme phone.
www.realme.com
This may help if you're having issues at this step.
13. Enter the commands listed below ONE BY ONE. For some reason they didn't work when I entered them all together.
adb shell setprop persist.data.iwlan.enable true
adb shell setprop persist.dbg.ims_volte_enable 1
adb shell setprop persist.dbg.volte_avail_ovr 1
adb shell setprop persist.dbg.vt_avail_ovr 1
adb shell setprop persist.dbg.wfc_avail_ovr 1
adb shell setprop persist.radio.rat_on combine
adb shell setprop persist.radio.data_ltd_sys_ind 1
adb shell setprop persist.radio.data_con_rprt 1
adb shell setprop persist.radio.calls.on.ims 1
adb shell setprop persist.data.iwlan 1
adb shell setprop persist.data.iwlan.ipsec.ap 1
adb shell setprop persist.radio.volte.dan_support true
adb shell setprop persist.radio.VT_ENABLE 1
adb shell setprop persist.sys.cust.lte_config true
adb shell setprop persist.rcs.supported 1
adb reboot
14. The phone reboots and the VoLTE and WiFi Calling switches are there in Settings - Mobile Networks - <SIM> !
Note that I am not saying that your phone will display VoLTE or VoWiFi in the notification area but at least the switches (options) become available in settings
Thanks to the authors of the page above!