[FAQ] Frequently Asked Questions For Moto E (2015) [UPDATED-3/7/2015] - E 2015 Q&A, Help & Troubleshooting

Frequently Asked Questions
Motorola Moto E
{
"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"
}
Hello Guys this is a FAQ for Moto E(2015) . Please read this here before posting it in the developmental section or creating a thread anywhere.
I am sure it will help.
Thank You
A big thanks goes to @matmutant for providing FAQ templates and his own FAQ from I have copied some things.Here is the original guide

[SIZE=+1]Q1: How to access Fastboot?[/SIZE]Hold PowerButton and VolDown during boot.​
[SIZE=+1]Q2: How to unlock Bootloader?[/SIZE]Boot to Fastboot and
follow my guide
Motorola guide on Motorola's website
[SIZE=+1]Q2: How to relock Bootloader?[/SIZE]Boot to Fastboot and give the command "fastboot oem lock"​
[SIZE=+1]Q3: 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]Q4: How to flash Stock Firmware?[/SIZE]Please Follow My Guidehere.​
[SIZE=+1]Q5: How to Root my device ?[/SIZE]First you'll need to unlock your bootloader,
then follow this guide
​
[SIZE=+1]Q6: Where can i find a Custom recovery ?[/SIZE]Yet to be uploaded​
[SIZE=+1]Q7: 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]Q8: 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)
[SIZE=+1]Q9: 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]Q10: 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]Q11: 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.
For Indian customers, The warranty is void if you unlock/root your device. Motorola also reserves the right to maintain the records of unlocked bootloader devices. So you may not even get the warranty by relocking the device
[source]​
[SIZE=+1]Q12: What to do if my battery is fully discharged and not re-charging?[/SIZE][source]​
[SIZE=+1]Q13: 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]Q14: 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)
Follow this FAQ​
[SIZE=+1]Q15: How to remove the 'unlocked warning' message?[/SIZE]Follow my guide here and default Motorola logo will be back .​
[SIZE=+1]Q16: 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]Q17: What are the Moto E tech specs[/SIZE]
XT1527, XT1511 - for USA
XT1505 - Global model
[SIZE=+1]Q18: How to get OTA updates even after Rooting and Flashing a custom Recovery[/SIZE]
Use the full unroot option from the Super Su
Flash the stock recovery Use Code : mfastboot flash recovery recovery.img
Now you'll be able to get OTA updates as before
[SIZE=+1]Q19: How to Unlock Advanced Camera Settings?[/SIZE]
Refer to this thread​

some usefull lines of commands for any user wanting to know what's going on:
requirements :
On Windows : install Moto E 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:
#motoe normal mode
SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", ATTR{idProduct}==”2e82″, MODE="0666"
#motoe debug mode
SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", ATTR{idProduct}==”2e76″, MODE="0666"
#motoe 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 E 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

Reserved

This is a WIP for now. Thread will be updated soon

My only question about this phone is if it has the autofocus feature or not (as was happened with 1st gen of it)

Lucas Eugene said:
This is a WIP for now. Thread will be updated soon
Click to expand...
Click to collapse
Lucas, have you tested the root method on the 2015 Moto E yet?

qbking77 said:
Lucas, have you tested the root method on the 2015 Moto E yet?
Click to expand...
Click to collapse
Updated thread now. You can visit the root thread

Lucas Eugene said:
This is a WIP for now. Thread will be updated soon
Click to expand...
Click to collapse
Bro,U tested moto e 2015 before it's arrival in the market.that's good
---------- Post added at 01:31 PM ---------- Previous post was at 01:25 PM ----------
Antonio Li said:
My only question about this phone is if it has the autofocus feature or not (as was happened with 1st gen of it)
Click to expand...
Click to collapse
Me too have the same doubt that it has auto focus cam or not.because I had moto e gen1 which has an average cam with manual exposure

Antonio Li said:
My only question about this phone is if it has the autofocus feature or not (as was happened with 1st gen of it)
Click to expand...
Click to collapse
suryaz124 said:
Bro,U tested moto e 2015 before it's arrival in the market.that's good
---------- Post added at 01:31 PM ---------- Previous post was at 01:25 PM ----------
Me too have the same doubt that it has auto focus cam or not.because I had moto e gen1 which has an average cam with manual exposure
Click to expand...
Click to collapse
Yes I suppose it has
confirmed

changing default install location
I am having trouble changing the default install location. I've used the command "adb shell pm set-install-location 2" and I received an error "error: java.lang.SecurityException: Package android does not belong to 2000." Anybody else getting this error? How do I go about fixing this issue? I am running stock 5.02 and getting this error before and after I unlocked the bootloader. Thank you.

Can't unlock bootloader
I have Cricket and my phone is not eligible to unlock the boot loader. Is there a workaround for this yet?

can i buy this phone .. is good ?? please help me ..
Sent from my 7236 2G using Tapatalk

Are the guides here the same for the 3G variant vs the LTE one? I'm thinking they are.
I scored a free Moto E 3G version for free when the wife ordered her Moto X from Motorola.com. Figured I'd just play with it. Thanks

apristel said:
Are the guides here the same for the 3G variant vs the LTE one? I'm thinking they are.
I scored a free Moto E 3G version for free when the wife ordered her Moto X from Motorola.com. Figured I'd just play with it. Thanks
Click to expand...
Click to collapse
The guides for unlocking bootloader etc. should be the same. Just don't flash LTE images on the 3G model, as they have completely different processors.
The CPU in the 3G model is actually rather similar to the first gen E, but beefed up with more cores. It may be possible to port Moto E 1st gen stuff to the 3G version fairly easily. I was thinking of getting a 3G model to tinker with, but unfortunately they are not available in Canada and I can't justify the cost of importing one myself.
It's a shame that Motorola hasn't released stock firmware images for this model. There is a leak for the European LTE model (that might work on North American ones with an unlocked bootloader). There are no stock images for the 3G out there yet.

squid2 said:
The guides for unlocking bootloader etc. should be the same. Just don't flash LTE images on the 3G model, as they have completely different processors.
The CPU in the 3G model is actually rather similar to the first gen E, but beefed up with more cores. It may be possible to port Moto E 1st gen stuff to the 3G version fairly easily. I was thinking of getting a 3G model to tinker with, but unfortunately they are not available in Canada and I can't justify the cost of importing one myself.
It's a shame that Motorola hasn't released stock firmware images for this model. There is a leak for the European LTE model (that might work on North American ones with an unlocked bootloader). There are no stock images for the 3G out there yet.
Click to expand...
Click to collapse
OK thanks! Funny you are in Canada. I ended up selling it to my friend in Canada. Its on its way there now.

WiFi tether
Has anyone managed to get WiFi tether working on their moto e 2015

Please update the thread
The recovery and root method for 3g version are working. @Lucas Eugene.
By the way this device is lagging like hell sometimes. Is it the memory leak problem.
How to solve it.

Ravx said:
Please update the thread
The recovery and root method for 3g version are working. @Lucas Eugene.
By the way this device is lagging like hell sometimes. Is it the memory leak problem.
How to solve it.
Click to expand...
Click to collapse
I'll update it asap with a lot of other things.
Don't if it works for you but you can try clearing cache/art cache and then compare

mdewii23 said:
I have Cricket and my phone is not eligible to unlock the boot loader. Is there a workaround for this yet?
Click to expand...
Click to collapse
No, much like the VZW variant I have. No root for us.

Related

[FAQ] Frequently Asked Questions For Moto E [UPDATED-05/10/14]

Frequently Asked Questions
Motorola Moto E
{
"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"
}
Hello Guys this is a FAQ for Moto E. Please read this here before posting it in the developmental section or creating a thread anywhere.
I am sure it will help.
Thank You
A big thanks goes to @matmutant for providing FAQ templates and his own FAQ from I have copied some things.Here is the original guide
[SIZE=+1]Q1: How to access Fastboot?[/SIZE]Hold PowerButton and VolDown during boot.​
[SIZE=+1]Q2: How to unlock Bootloader?[/SIZE]Boot to Fastboot and
follow my guide
Motorola guide on Motorola's website
@matmutant Speed Run Guide
[SIZE=+1]Q2: How to relock Bootloader?[/SIZE]Boot to Fastboot and give the command "fastboot oem lock"​
[SIZE=+1]Q3: 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]Q4: How to flash Stock Firmware?[/SIZE]Please Follow My Guidehere.​
[SIZE=+1]Q5: How to Root my device ?[/SIZE]First you'll need to unlock your bootloader,
then follow this guide
OR this guide(User Friendly)
​
[SIZE=+1]Q6: Where can i find a Custom recovery ?[/SIZE]TWRP 2.7.2.0​
[SIZE=+1]Q7: 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]Q8: 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)
[SIZE=+1]Q9: 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]Q10: 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]Q11: 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.
For Indian customers, The warranty is void if you unlock/root your device. Motorola also reserves the right to maintain the records of unlocked bootloader devices. So you may not even get the warranty by relocking the device
[source]​
[SIZE=+1]Q12: What to do if my battery is fully discharged and not re-charging?[/SIZE][source]​
[SIZE=+1]Q13: 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]Q14: 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)
Follow this FAQ​
[SIZE=+1]Q15: How to remove the 'unlocked warning' message?[/SIZE]Follow @cschmitt method and default Motorola logo will be back .​
[SIZE=+1]Q16: 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]Q17: What are the Moto E tech specs[/SIZE]
XT1021 (Single Sim)
XT1022 (Dual Sim)
XT1025 (Dual Sim With TV Digital)
[SIZE=+1]Q18: How to get OTA updates even after Rooting and Flashing a custom Recovery[/SIZE]
Use the full unroot option from the Super Su
Flash the stock recovery Use Code : mfastboot flash recovery recovery.img
Now you'll be able to get OTA updates as before
[SIZE=+1]Q19: How to Unlock Advanced Camera Settings?[/SIZE]
Refer to this thread​
some usefull lines of commands for any user wanting to know what's going on:
requirements :
On Windows : install Moto E 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:
#motoe normal mode
SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", ATTR{idProduct}==”2e82″, MODE="0666"
#motoe debug mode
SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", ATTR{idProduct}==”2e76″, MODE="0666"
#motoe 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 E 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
reserved---3
reserved----4
last one
Let me reserve a post here
I've updated the thread a bit. Have to leave soon so didn't did much updates.
More Updates Coming Soon
Reserved:victory:
Updated Thread with Model No's
Thanks to @deej_roamer
Like to add an input regarding Q11
For Indian customers, The warranty is void if you unlock/root your device. Maybe OP can add this too.
Hello guys
I switched to moto e from a phone which had a pretty versatile memory system in which i could transfer apps to sd card and use link2sd to partition sd card and use it as internal memory.
in moto e moving the preinstalled apps like maps and music and chrome etc through link2sd causes them to FC.
apart from that i cannot move my whatsapp data to SD card even if i transfer the actual app to sd card partition through link2sd. also, apps do not catch their data from the sd card. everything should be on the internal memory to work and that forces me to not install apps. my whatsapp has important databases which cannot be deleted and they take up 700+MB of internal SD space which cannot be freed to the ext SD since whatsapp doesnt restore from ext card. what to do???
TacTieTee said:
Hello guys
I switched to moto e from a phone which had a pretty versatile memory system in which i could transfer apps to sd card and use link2sd to partition sd card and use it as internal memory.
in moto e moving the preinstalled apps like maps and music and chrome etc through link2sd causes them to FC.
apart from that i cannot move my whatsapp data to SD card even if i transfer the actual app to sd card partition through link2sd. also, apps do not catch their data from the sd card. everything should be on the internal memory to work and that forces me to not install apps. my whatsapp has important databases which cannot be deleted and they take up 700+MB of internal SD space which cannot be freed to the ext SD since whatsapp doesnt restore from ext card. what to do???
Click to expand...
Click to collapse
Thats how KK is designed. App should store their data on internal memory. Sdcard is treated as another partition. Apparently,this is so that on uninstall there's no residual data.
To change that, you need root.
Sent from my XT1022 using Tapatalk
Falcon G said:
[SIZE=+1]Q5: How to Root my device ?[/SIZE]First you'll need to unlock your bootloader,
then follow this guide​
Click to expand...
Click to collapse
There are confirmed rooting methods here and here!​
neo.ank said:
Thats how KK is designed. App should store their data on internal memory. Sdcard is treated as another partition. Apparently,this is so that on uninstall there's no residual data.
To change that, you need root.
Sent from my XT1022 using Tapatalk
Click to expand...
Click to collapse
deej_roamer said:
There are confirmed rooting methods here and here!
Click to expand...
Click to collapse
my device is already rooted guys. trying to keep data in ext but app does not recognise tht data. for example my whatsapp - it only recognises data on internal. and it takes up anywhere between 1 GB to 1.5 GB...even if i mnage to shiftthe app to the ntfs partition through link2sd which i already have, i cant keep the data in ext since itdoesnt recognise
TacTieTee said:
my device is already rooted guys. trying to keep data in ext but app does not recognise tht data. for example my whatsapp - it only recognises data on internal. and it takes up anywhere between 1 GB to 1.5 GB...even if i mnage to shiftthe app to the ntfs partition through link2sd which i already have, i cant keep the data in ext since itdoesnt recognise
Click to expand...
Click to collapse
That needs modification at system level. As I said it is in the design of the OS.
Best bet for now is to wait for Custom ROMs.
Sent from my XT1022 using Tapatalk
TacTieTee said:
my device is already rooted guys. trying to keep data in ext but app does not recognise tht data. for example my whatsapp - it only recognises data on internal. and it takes up anywhere between 1 GB to 1.5 GB...even if i mnage to shiftthe app to the ntfs partition through link2sd which i already have, i cant keep the data in ext since itdoesnt recognise
Click to expand...
Click to collapse
Why was i quoted in this reply?
Sorry I thought u were guiding me to root guides since the poster above yours told me to have my come rooted.
neo.ank said:
Like to add an input regarding Q11
For Indian customers, The warranty is void if you unlock/root your device. Maybe OP can add this too.
Click to expand...
Click to collapse
deej_roamer said:
There are confirmed rooting methods here and here!
Click to expand...
Click to collapse
Added to the OP
Hope it helps
For Q15, you may use this:
http://forum.xda-developers.com/showpost.php?p=52804779&postcount=12

Unofficial TWRP Padfone X

Introduction:
The padfone X was released last friday and I wanted TWRP. As you may know; @Dees_Troy is on vacation. So, I hacked together this "repack" version which should have all features in order. One caveat with this version though, when launching recovery after it's installed, the screen must time out (2-minutes) before you can push power and see it.
Warning:
Even though you may simply be using your device and just running apps, you are modifying your device. There is no 100% back to stock. You can find a fastboot flashable stock recovery here, but there is no stock system. While this mod did not trigger a "modified status" on my device, I cannot guarantee the same for you. This is a very new device and unless you're one of the few, brave and anxious, it may be in your best interest to wait until a stock firmware update, back-to-stock flash, or even an official XDA-Developers forum has been created for this device.
you will need:
1.The Unofficial TWRP recovery image
2.SuperSU installed on your device
3.TowelRoot installed on your device. You will need to enable third-party sources.
4.Terminal access (pick the one you're more comfortable with)
4a.ADB
4b.Terminal emulator
installation:
If you chose to use ADB, then use these ADB Instructions. Otherwise skip down to Terminal Emulator Instructions.
ADB Instructions
Ensure you have installed SuperSU and TowelRoot.
Launch the TowelRoot app, follow instructions, and let it reboot your device.
navigate to the folder you downloaded ADB (and dll's if you're on windows) and execute the following command.
Code:
adb shell "curl 'https://builds.casual-dev.com/files/Asus/Padfone%20X/TWRP-Nexus5repack-AO1.img'>/sdcard/recovery.img; su -c 'dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery' bs=4096; sync; reboot recovery;"
check your device for any pop-ups and grant root access to shell.
wait 2 minutes after the screen is black, and then press power button. This is due to a difference between Nexus5 and PadfoneX which will be fixed in an official version later.
Terminal Emulator Instructions
Ensure you have installed SuperSU and TowelRoot.
Launch the TowelRoot app, follow instructions, and let it reboot your device.
Launch Terminal Emulator and copy-pasta the following into it.
Code:
curl 'https://builds.casual-dev.com/files/Asus/Padfone%20X/TWRP-Nexus5repack-AO1.img'>/sdcard/TWRPrecovery.img; su -c 'dd if=/sdcard/TWRPrecovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery' bs=4096; sync; reboot recovery;
check your device for any pop-ups and grant root access to shell.
wait 2 minutes after the screen is black, and then press power button. This is due to a difference between Nexus5 and PadfoneX which will be fixed in an official version later.
Conclusion
Congratulations, you've got TWRP installed on your device. Now you can back up, restore, and install TWRP Flashable Zips. Please leave a comment and tell others how it worked. This worked great for me, Image below.
{
"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"
}
@Dees_Troy has a helpful suggestion:
Might be worth mentioning Settings -> Screen and lower the screen timeout to help get the screen up and running sooner
Whatever you do, don't turn off the screen timeout though
Click to expand...
Click to collapse
By turning down the screen timeout you only need to wait for two minutes, one time. Turn it down to 30 seconds to reduce the wait time.
Again, this is temporary for this unofficial build. I will update these instructions later when we have a proper solution to perform the needed hardware reset.
I can't wait to see development for this phone!!!! Thank you for all your hard work.
This is great, now all we need is a device thread.
What do we need to do , in order to get that going ? this device has great potential !!!
Adam have you put on the screen protector i saw you bought from ATT? i can't figure out how to properly place it because very time i go into tablet mode and i pull the phone out the phone protector always has a bubble or two from sticking to the tablet ... not sure if that makes sense lol
AdamOutler said:
Introduction:
The padfone X was released last friday and I wanted TWRP. As you may know; @Dees_Troy is on vacation. So, I hacked together this "repack" version which should have all features in order. One caveat with this version though, when launching recovery after it's installed, the screen must time out (2-minutes) before you can push power and see it.
Warning:
Even though you may simply be using your device and just running apps, you are modifying your device. There is no 100% back to stock. You can find a fastboot flashable stock recovery here, but there is no stock system. While this mod did not trigger a "modified status" on my device, I cannot guarantee the same for you. This is a very new device and unless you're one of the few, brave and anxious, it may be in your best interest to wait until a stock firmware update, back-to-stock flash, or even an official XDA-Developers forum has been created for this device.
you will need:
1.The Unofficial TWRP recovery image
2.SuperSU installed on your device
3.TowelRoot installed on your device. You will need to enable third-party sources.
4.Terminal access (pick the one you're more comfortable with)
4a.ADB
4b.Terminal emulator
installation:
If you chose to use ADB, then use these ADB Instructions. Otherwise skip down to Terminal Emulator Instructions.
ADB Instructions
Ensure you have installed SuperSU and TowelRoot.
Launch the TowelRoot app, follow instructions, and let it reboot your device.
navigate to the folder you downloaded ADB (and dll's if you're on windows) and execute the following command.
Code:
adb shell "curl 'http://builds.casual-dev.com/files/Asus/Padfone%20X/TWRP-Nexus5repack-AO1.img'>/sdcard/recovery.img; su -c 'dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery' bs=4096; sync; reboot recovery;"
check your device for any pop-ups and grant root access to shell.
wait 2 minutes after the screen is black, and then press power button. This is due to a difference between Nexus5 and PadfoneX which will be fixed in an official version later.
Terminal Emulator Instructions
Ensure you have installed SuperSU and TowelRoot.
Launch the TowelRoot app, follow instructions, and let it reboot your device.
Launch Terminal Emulator and copy-pasta the following into it.
Code:
curl 'http://builds.casual-dev.com/files/Asus/Padfone%20X/TWRP-Nexus5repack-AO1.img'>/sdcard/TWRPrecovery.img; su -c 'dd if=/sdcard/TWRPrecovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery' bs=4096; sync; reboot recovery;
check your device for any pop-ups and grant root access to shell.
wait 2 minutes after the screen is black, and then press power button. This is due to a difference between Nexus5 and PadfoneX which will be fixed in an official version later.
Click to expand...
Click to collapse
Didn't work for me. Just look like in TE it kept looking for a response back from the server. I tried to download the img manually and looks like the server is down or something.
FUZER384 said:
Didn't work for me. Just look like in TE it kept looking for a response back from the server. I tried to download the img manually and looks like the server is down or something.
Click to expand...
Click to collapse
It's working now. Server was, in-fact down earlier.
As they (nearly) share the same hardware, do you think it would be possible to compile a working recovery from Asus PadFone Infinity 2 (A86) sources?
Here is a link: http://www.asus.com/Tablets_Mobile/The_new_PadFone_Infinity/HelpDesk_Download/
(or: http://dlcdnet.asus.com/pub/ASUS/Mo...dFone_Infinity/PadFoneT004-1012394-kernel.zip for a direct link)
As Asus has not released PFX kernel sources on their site, I think it could be useful.
Demazda said:
As they (nearly) share the same hardware, do you think it would be possible to compile a working recovery from Asus PadFone Infinity 2 (A86) sources?
Here is a link: http://www.asus.com/Tablets_Mobile/The_new_PadFone_Infinity/HelpDesk_Download/
(or: http://dlcdnet.asus.com/pub/ASUS/Mo...dFone_Infinity/PadFoneT004-1012394-kernel.zip for a direct link)
As Asus has not released PFX kernel sources on their site, I think it could be useful.
Click to expand...
Click to collapse
Not without a device in-hand. I won't try to troubleshoot without it.
However, I use mkbootimg_tools and it requires a Linux system, not windows.
to get reccovery.img
Code:
adb shell su -C dd if=/dev/block/platform/*/by-name/recovery of=/sdcard/recovery.img
adb pull /sdcard/recovery.img
to uncompile original boot.img
Code:
mkboot recovery.img oringialoutput
this opens recovery.img and creates a ramdisk from it which you can freely edit. Now, do the same with TWRPRecovery.img
you will copy the following folders from the TWRP ramdisk to the originaloutput ramdisk. but heed the notes here.
/sbin -- replace only recovery, but copy all files over to the new device.
/res and /etc -- do not replace files, but add in TWRP files to this and its subdirectories.
/supersu -- this does not exist on the new ramdisk, so just copy it.
you will have to navigate to originalrecovery/ramdisk/system, then copy /system/bin into /sbin, then delete /system/bin, finally link /system/bin to /sbin. the positioning is important and you cannot use fully qualified paths to link the files here. it must be linked to ../sbin, specifying one folder up, a folder called "sbin", not /home/username/whatever...
Code:
cd originalramdisk/system/
cp ./bin/* ..//sbin
rm -rf ./bin
ln -s ../sbin
And then you're ready to repack.
Code:
mkboot originalramdisk myNewRecovery.img[code]
now you can copy myNewRecovery.img to your SDCard and flash it using the DD method I showed in the OP.
Oh, I thought you had the device, my bad.
Also, sorry, this may be off-topic (but still related to PadFone and development), but how hard do you think it would be to port CyanogenMod to a PadFone? Not for the PadFone X but for another one, knowing that I managed to build a recovery from source and that it's working, but that I've never managed to make the compiled rom itself boot?
Demazda said:
Oh, I thought you had the device, my bad.
Also, sorry, this may be off-topic (but still related to PadFone and development), but how hard do you think it would be to port CyanogenMod to a PadFone? Not for the PadFone X but for another one, knowing that I managed to build a recovery from source and that it's working, but that I've never managed to make the compiled rom itself boot?
Click to expand...
Click to collapse
This is a Padfone X forum. I can't help you any more than I have. Locate a developer with a Padfone 2 and ask him questions. I gave you instructions to try to create your own. I cannot do more.
AdamOutler said:
This is a Padfone X forum. I can't help you any more than I have. Locate a developer with a Padfone 2 and ask him questions. I gave you instructions to try to create your own. I cannot do more.
Click to expand...
Click to collapse
It's for the PadFone Infinity and I already have a CWM working, my question was about building a ROM. Also it seems that no developer has this device, as it's never beed released in the US.
But no problem, thanks anyway.
Also, sorry but I might not have said it properly in my first post: I did not ask you to build a recovery PadFone Infinity 2 (I don't have this device), I just gave you the kernel source because I thought it could help you build a PadFone X recovery from those sources, as they are both similar in hardware and from the same manufacturer.
Can anyone tell me how to build a cwm recovery for Asus Zenfone 5 ?
I cant take the recovery.img from my system ...
So I seem to have really screwed something up with a few features by trying to save space by integrating various GApps updates to the ROM. I cannot get a keyboard at all during boot-up for any purpose (eg encryption, which my employer requires to use this on their networks).
I don't suppose anyone has a stock nandroid of /system on hand I could download?
EDIT: I see there isn't one yet, but if you make one, anyone, I'd be willing to host it on my Mediafire account.
EDIT 2: Where might I find this flashable stock recovery? I must be overlooking it.
EDIT 3: I see. The link to the unofficial TWRP points to the stock DD pull. I already have a DD pull I just did so ignore that question aboug stock recoveries.
Anyone else having SERIOUS device issues after flashing this?
EDIT: Not demanding updates/etc, just asking/inquiring.
I have ADB installed but running "adb devices" does not show any device connected. My windows 7 shows the storage (internal and external SD card) but windows does not recognize the "ASUS Android Composite ADB Interface".
Any advice where to find drivers for windows 7 for my Padfone X ?
Thanks !
JD
dorj1234 said:
I have ADB installed but running "adb devices" does not show any device connected. My windows 7 shows the storage (internal and external SD card) but windows does not recognize the "ASUS Android Composite ADB Interface".
Any advice where to find drivers for windows 7 for my Padfone X ?
Thanks !
JD
Click to expand...
Click to collapse
LOL! did you ever plug it into the computer? It has the drivers on it.
AdamOutler said:
LOL! did you ever plug it into the computer? It has the drivers on it.
Click to expand...
Click to collapse
For me they installed automatically
Sent from my ASUS PadFone X using XDA Free mobile app
Does anyone have new download link for twrp recovery , link is dead

[ROM] [SFOS] [OFFICIAL] Sailfish OS 2.0.5.6 for Redmi 2[wt88047][Android App Support]

{
"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"
}
Sailfish OS was originally developed for Nokia phones and was named Meego OS. The project was joint collaboration between Nokia and Intel. The project was later dropped by Nokia but Meego enthusiasts picked up the project and continued the Meego project under Sailfish OS and INTEX was the first ever company to officially tie it's phone to Sailfish OS ROM. For further info checkout : https://en.wikipedia.org/wiki/Sailfish_OS and https://sailfishos.org/
This is the Alpha stable release still has many bugs so don't complain about it. Enjoy your newly built SFOS 2.0.5.6 for Xiaomi Redmi 2 device. This is not Android, this is pure Linux similar to Ubuntu based upon libraries from Android.
For Newbies who don't know the difference between Sailfish OS and Android OS respectively a here is a compact difference list:
1. Pure Linux vs Modified Linux kernel
2. A real multitasker vs Naah not so much of multi-tasking.
3. Store sucks vs Tons of Apps
4.Android apps support too. vs Only Android app is supported.
Change LOG (Compact):
1. Kernel Patched for faster bootup.
2. Wlan, BT, MultiSIM, PulseAudio,GPS fixed.
3. Jolla Store is enabled
4. Multi ROM support
Steps:
1. Go to TWRP recovery mode.
2. Wipe All data except media.
3. Flash CM-12.1 for Redmi 2
4. Flash SailfishOS ROM.
5. Reboot the system after wiping Cache/Dalvik Cache.
There you go. Your SFOS 2.0.5.6 is now loaded. To skip the tutorial touch upper left corner of the screen and clockwise till bottom left corner.
To debug and report error open terminal in Linux and type "telnet 192.168.2.15 2323". For Windows probably install telnet related services and libraries and use the same command in cmd prompt.
Bugs:
1. Front Camera doesn't work. Instead switching between them might lead to camera app crash, to resolve it switch back again to front or back cam.(Temporary soln).
2. Media Player will not play song, to resolve it do the following
3. 4G won't work (as of now). My 4G signal is too weak so it didn't work, my bad.(For JIO users : Go to Settings>Cellular Networks>Data Access point : Change Access point name from "jionet" to "www".)
4. Android Apps won't work (as of now)
5. Battery drain leads to bootloop
SFDROID (Android App Support):
How to install (For Linux Users only):
1. Download the RPM files mentoioned here
SFDROID:https://drive.google.com/open?id=0B8I9RnxIQmQea0xxU3puYnc4Ymc
2. Create a folder for these files separately.
3. In your device goto Settings>Developer Settings and set your password and note down the I.P. address for USB if you are using USB for file transfer or Wifi for Wifi file transfer.
4. Now go to the folder where RPM files are located and right click to open terminal
5. Enter scp *.rpm [email protected]"I.P. address for USB/Wifi": (Add colon ":" sign after the I.P. address, also if you are using USB for file transfer, use the USB I.P. Address mentioned in your developer settings and similarly for Wifi)
6. Enter your password you have set previously and file transfer would begin.
7. Now for USB connected phone open a new terminal and type telnet 192.168.2.15 2323 (If this is not the I.P. address for USB you can see the relevant I.P. address as shown in the Developer Settings of your phone and enter the same after telnet except for 2323(port number))
8. Type su
9. Now type cd /home/nemo
10. Type ls to confirm that all files have been transferred successfully.
11. Type rpm -i --force *.rpm
12. Now type reboot
13. After reboot again in the terminal type telnet 192.168.2.15 2323 and type killall surfaceflinger zygote system_server main servicemanager
14. Now run SFDROID and wait for sometime your Android will load.
15. For Wifi connected phone (Make a Wifi Hotspot on your computer and connect to the hotspot for the mobile device, don't use Wireless router, use direct connection b/w computer and mobile) open a new terminal and type ssh [email protected] (Your I.P. address for Wifi as shown in the Developer setiings of your phone)
16. Now type devel-su
17. Now type in your password
18. Now type cd /home/nemo
19. Now type rpm -i --force *.rpm
20. Now type reboot
21. After reboot again type ssh [email protected]
22 Type killall surfaceflinger zygote system_server main servicemanager
Note: Android is bit sluggish and not perfect as a native Android, but hey at least you got your Android running.
Thanks especially to @saidinesh5 for debugging SFDROID and ofcourse other members of #sfdroid on IRC freenode channel
Bootanimation(default):
https://forum.xda-developers.com/redmi-2/themes/mod-sailfish-os-t3561208 thanks to @taalojarvi
Thanks to adeen-s (www.github.com/adeen-s) @saidinesh5, @mal-, @m4r0v3r, sledges and other member of #sailfish-porters IRC channel.
The CyanogenMod and Kernel isn't my proprietary it is the proprietary of CyanogeMod team and @ketut.kumajaya respectively. However the kernel has some changes made in accordance to SFOS and also I have patched it to decrease the boot up time delay.
Download Link:
https://drive.google.com/open?id=0B8I9RnxIQmQeV3VMM1FFU0RzazQ
https://www.androidfilehost.com/?w=files&flid=153058
SFDROID:https://drive.google.com/open?id=0B8I9RnxIQmQea0xxU3puYnc4Ymc
Edit: Now Lollipop bootloader is supported. Tested it and SFOS was able to boot up.
Github : https://github.com/nrdnandan
Wiki-MER: https://wiki.merproject.org/wiki/Adaptations/libhybris/porters
Name : Sailfish OS
Version : 2.0.5.6 (latest)
Kernel : 3.10.49
Release type: User-Release
Build : Stable
Boolader : Lollipop (Here is the link : http://en.miui.com/thread-386154-1-1.html)
CM/Android base: 12.1(wt88047)/5.1.1
GG! Here's an upvote
Great job
nrdnandan said:
This Alpha release still has many bugs so don't complain about it. Enjoy your newly built SFOS 2.0.5.6 for Xiaomi Redmi2 device. This is not Android, this is pure Linux similar to CentOS based upon libraries from Android.
Change LOG (Compact):
1. Kernel Patched for faster bootup.
2. Wlan, BT, MultiSIM, PulseAudio fixed.
3. Jolla Store is enabled
Steps:
1. Go to TWRP recovery mode.
2. Wipe All data except media.
3. Flash CM-12.1 for Redmi 2
4. Flash SailfishOS ROM.
5. Reboot the system without wiping Cache/Dalvik Cache.
There you go. Your SFOS 2.0.5.6 is now loaded. To skip the tutorial touch upper left corner of the screen and clockwise till bottom left corner.
To debug and report error open terminal in Linux and type "telnet 192.168.2.15 2323". For Windows probably install telnet related services and libraries and use the same command in cmd prompt.
Bugs:
1. Front Camera doesn't work.
2. Media Player will not play song, to resolve it do the following:
i). rm -rf /etc/audio_platform_info.xml (similarly for media_codecs_google_video_le.xml,flp.conf, firmware,mixer_paths_qrd_skui.xml)
ii). ln -s /system/etc/audio_platform_info.xml /etc/audio_platform_info.xml (similarly for media_codecs_google_video_le.xml,flp.conf, firmware,mixer_paths_qrd_skui.xml)
Thanks to @saidinesh5sh5, mal, ghosalmartin, Nexit and other member of #sailfish-porters IRC channel.
Download Link:
https://drive.google.com/open?id=0B8I9RnxIQmQeV3VMM1FFU0RzazQ
Click to expand...
Click to collapse
Thanks for the build. Please hide your imei in the screenshot.
Is it multirom bootable as secondary or primary ROM.
Downloading.....
does this support 4g mobile data,i found a phone named intex aqua has sailos with jio 4g support can u port that to enable data
---------- Post added at 12:57 PM ---------- Previous post was at 12:54 PM ----------
2. Media Player will not play song, to resolve it do the following:
i). rm -rf /etc/audio_platform_info.xml (similarly for media_codecs_google_video_le.xml,flp.conf, firmware,mixer_paths_qrd_skui.xml)
ii). ln -s /system/etc/audio_platform_info.xml /etc/audio_platform_info.xml (similarly for media_codecs_google_video_le.xml,flp.conf, firmware,mixer_paths_qrd_skui.xml)
plz tell how to do this
Please reply.
*4G working?
*Android apps working?
ROCKY_ME said:
Is it multirom bootable as secondary or primary ROM.
Downloading.....
Click to expand...
Click to collapse
I have not checked. I will report back to you later
Superraju said:
Please reply.
*4G working?
*Android apps working?
Click to expand...
Click to collapse
they already mentioned this is not andriod rom,so no andriod apps ok
suresh001 said:
they already mentioned this is not andriod rom,so no andriod apps ok
Click to expand...
Click to collapse
It is not true, 4G won't work because ROM doesn't support VOLTE, and as far as JIO goes, it requires 4G and VOLTE for full activation.
Android Apps will work. That is what SFDROID is for.
suresh001 said:
does this support 4g mobile data,i found a phone named intex aqua has sailos with jio 4g support can u port that to enable data
---------- Post added at 12:57 PM ---------- Previous post was at 12:54 PM ----------
2. Media Player will not play song, to resolve it do the following:
i). rm -rf /etc/audio_platform_info.xml (similarly for media_codecs_google_video_le.xml,flp.conf, firmware,mixer_paths_qrd_skui.xml)
ii). ln -s /system/etc/audio_platform_info.xml /etc/audio_platform_info.xml (similarly for media_codecs_google_video_le.xml,flp.conf, firmware,mixer_paths_qrd_skui.xml)
plz tell how to do this
Click to expand...
Click to collapse
I will upload a new version soon, so don't worry about that.
suresh001 said:
they already mentioned this is not andriod rom,so no andriod apps ok
Click to expand...
Click to collapse
Dont comment without any proper informations dude
@nrdnandan @ROCKY_ME
Here's the process for booting SailfishOS as a secondary ROM in MultiROM. Please put appropriate CM zip name and everything else is the same.
https://forum.xda-developers.com/redmi-2/how-to/guide-how-to-boot-sailfish-os-secondary-t3434696
Good news, Lollipop bootloader is supported.
Superraju said:
Dont comment without any proper informations dude
Click to expand...
Click to collapse
The developer mentions in the OP that android apps are not working!
part 1994 said:
The developer mentions in the OP that android apps are not working!
Click to expand...
Click to collapse
Read it again my friend, it is a bug or I may say a non-availability now. Ported phones don't support Android apps straight away, I will make sure in later builds Android apps work.
nrdnandan said:
Read it again my friend, it is a bug or I may say a non-availability now. Ported phones don't support Android apps straight away, I will make sure in later builds Android apps work.
Click to expand...
Click to collapse
I got that from the OP.
Was just responding to that person's query whether android apps are working that is all.
Also the ROM does not seem to boot for me
Wonderful I was waiting for this, had good times with SFOS , but one provided by adeen-s was not booting from LP bootlader. Good to know that this does boot. I will wait for some time.. Let it get a bit stable. (Its still Alpha)
part 1994 said:
I got that from the OP.
Was just responding to that person's query whether android apps are working that is all.
Also the ROM does not seem to boot for me
Click to expand...
Click to collapse
dmesg
part 1994 said:
I got that from the OP.
Was just responding to that person's query whether android apps are working that is all.
Also the ROM does not seem to boot for me
Click to expand...
Click to collapse
i guess you are using Lolipop bootloader?

How To Guide Converting Japanese Pixel 6 to Global version

I live in a country with no Pixel availability and end up purchasing one in Japan.
Limitations(mostly forced shutter and screenshot sound) on Japan phones can be pretty annoying, so I researched a bit on how to remove those.
Search leads me to this reply by @ziand for same trick but on Pixel 5. Turns out Pixel 6 is different but similar. So I'll summarize what I've done here.
At the same time @ziand may also work on a magisk module or something when possible, doing the same thing but in a much safer way. Once his work is done please switch to his method.
Disclaimer
I'm not familiar with law in every country but doing this could have risk. Research before acting.
The instructions requires basic Linux/Android knowledge. You could brick your phone if not knowing what you're doing. You can always wait for ziand's work for more safety.
I confirm this works on my phone. But I'm not responsible for anything happens on yours. Use at your own risk.
Click to expand...
Click to collapse
Spoiler: steps
1. Root your phone
2.
adb shell
su
dd if=/dev/block/by-name/devinfo of=/sdcard/devinfo.img
Click to expand...
Click to collapse
3. Quit adb shell, then
adb pull /sdcard/devinfo.img
Click to expand...
Click to collapse
Keep this file as backup
4. Use a hex editor, open the "devinfo.img" pulled in step 3, find "GR1YH", it should be in 0x000000F7, edit it to "GB7N6", save as "devinfo_modified.img"
{
"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.
adb push ./devinfo_modified.img /sdcard/
adb shell
su
dd if=/sdcard/devinfo_modified.img of=/dev/block/by-name/devinfo
Click to expand...
Click to collapse
6. Reboot and enjoy
This should be permanent, you can also revert root if you want.
Thank you HarryShan. It's confirmed work for me. Much appreciated for your share.
Do I need to unlock bootloader to root sir?
norman00037 said:
Do I need to unlock bootloader to root sir?
Click to expand...
Click to collapse
Yes. Please refer to the rooting guide I've linked to
Thank you HarryShan! It's worked for me)
Hi,
Someone tried this on pixel 5a?
I dealing with the same anoying japanese problem.
Curious if this would adversely affect NFC function as the Japanese model is NFC-F.
you did it with non rooted phone, right? and how did you do it without TWRP?
HarryShan said:
At the same time @ziand may also work on a magisk module or something when possible, doing the same thing but in a much safer way. Once his work is done please switch to his method.
Click to expand...
Click to collapse
Here is below a script to convert the device to another version.
About versions of Google Pixel 6, Product ID oriole :
Model IDs:
G9S9B - Verizon and AT&T US carriers
GB7N6 - US Unlocked, US Google Fi, US TMO, Canada, Taiwan, Australia, Europe countries and carriers
GR1YH - Japan and carriers
Script for changing Model ID
for devices: Google Pixel 5, 6/pro, 6a, 7/pro​Prerequisites
TWRP or Magisk 20.4+
Downloads
Magisk module: MID_Changer_v2.10-MAGISK-TWRP.zip
Change log
-v2.10 : Pixel 7 added
- v2.09 : Pixel 7pro added
- v2.08 : Pixel 6a added
Example running image:
To apple changing, flash global Factory Image with erasing data. You can use Android Flash Tool with locked bootloader option.
ziand said:
Here is below a script to convert the device to another version.
About versions of Google Pixel 6, Product ID oriole :
Model IDs:
G9S9B - Verizon and AT&T US carriers
GB7N6 - US Unlocked, US Google Fi, US TMO, Canada, Taiwan, Australia, Europe countries and carriers
GR1YH - Japan and carriers
Script for changing Model ID on Pixel 6​Prerequisites
Your phone has to be rooted
Downloads
Magisk module: MID_Changer_v2.04-MAGISK.zip
Installation instruction
Download and install Magisk module above.
Running instruction
Variant 1 with commands from PC:
Code:
adb shell
su
MID_Changer.sh
Example image:
View attachment 5471525
Shorter Variant 1 with commands for PC:
Code:
adb shell
su -c MID_Changer.sh
Variant 2 with commands without PC.
Also you can use for example Android Terminal Emulator with commands:
Code:
su
MID_Changer.sh
To apple changing, flash global Factory Image with erasing data.
Recommendations
If someone wouldn't like to use root in the future, he can lock bootloader by the command at bootloader mode:
Code:
fastboot flashing lock
or use parameter "Lock bootloader" at flashing Factory Image via Android Flash Tool.
Click to expand...
Click to collapse
thank you very much. I tried and succeeded. my pixel 6 can mute the shutter sound. but after inserting the Japan sim, the sound comes back. so sad. I don't know is there any other solution?
h281994 said:
thank you very much. I tried and succeeded. my pixel 6 can mute the shutter sound. but after inserting the Japan sim, the sound comes back. so sad. I don't know is there any other solution?
Click to expand...
Click to collapse
Did you flash Factory Image with erasing data, factory reset ?
The converting is success if you have:
- new Model ID in bootloader - Barcode -SKU;
- new Model ID in Settings - About phone - Regulatory Labels;
- appeared option to switch off the sound in settings of stock Camera app.
Do you have all of them ? Show some pictures.
ziand said:
Did you flash Factory Image with erasing data, factory reset ?
The converting is success if you have:
- new Model ID in bootloader - Barcode -SKU;
- new Model ID in Settings - About phone - Regulatory Labels;
- appeared option to switch off the sound in settings of stock Camera app.
Do you have all of them ? Show some pictures.
Click to expand...
Click to collapse
@h281994, are you in Japan ?
I think to necessary to check how is with it on original non-Japanese phone with any sim there ?
ziand said:
@h281994, are you in Japan ?
I think to necessary to check how is with it on original non-Japanese phone with any sim there ?
Click to expand...
Click to collapse
Yes i am working in japan, i tried inserting softbank sim, sadly the camera sound is back again and the setting to turn off shutter sound is gone.I tried removing the sim and restarting the device ...the setting to turn off camera sound appeared again. very happy
Do you have possibility to insert another sim not softbank and maybe not Japanese carrier at all ? it is interesting how with this sound on other pixels 6 not Japanese versions there in Japan.
h281994 said:
Yes i am working in japan, i tried inserting softbank sim, sadly the camera sound is back again and the setting to turn off shutter sound is gone.I tried removing the sim and restarting the device ...the setting to turn off camera sound appeared again. very happy
Click to expand...
Click to collapse
This is known issue as even global Pixel do have forced shutter and screenshot sound when a Japanese carrier SIM is inserted, no matter where you use it. In this case MID changing method can't help you.
The module from the other thread may work though as it's directly modifying system UI APK:
GitHub - AndroPlus-org/magisk-module-pixel6: Google Pixel 6シリーズ以降向けのMagiskモジュールです。
Google Pixel 6シリーズ以降向けのMagiskモジュールです。. Contribute to AndroPlus-org/magisk-module-pixel6 development by creating an account on GitHub.
github.com
Downside would be you'll always need Magisk installed. You can have a try.
ziand said:
Here is below a script to convert the device to another version.
About versions of Google Pixel 6, Product ID oriole :
Model IDs:
G9S9B - Verizon and AT&T US carriers
GB7N6 - US Unlocked, US Google Fi, US TMO, Canada, Taiwan, Australia, Europe countries and carriers
GR1YH - Japan and carriers
Script for changing Model ID on Pixel 6​Prerequisites
Your phone has to be rooted
Downloads
Magisk module: MID_Changer_v2.05-MAGISK.zip
Installation instruction
Download and install Magisk module above.
Running instruction
Variant 1 with commands from PC:
Code:
adb shell
su
MID_Changer.sh
Example image:
View attachment 5471525
Shorter Variant 1 with commands for PC:
Code:
adb shell
su -c MID_Changer.sh
Variant 2 with commands without PC.
Also you can use for example Android Terminal Emulator with commands:
Code:
su
MID_Changer.sh
To apple changing, flash global Factory Image with erasing data.
Recommendations
If someone wouldn't like to use root in the future, he can lock bootloader by the command at bootloader mode:
Code:
fastboot flashing lock
or use parameter "Lock bootloader" at flashing Factory Image via Android Flash Tool.
Click to expand...
Click to collapse
I can't use this module for my Pixel 6 pro Japan. How can I use .
Thank you!
khoanx said:
I can't use this module for my Pixel 6 pro Japan. How can I use .
Thank you!
Click to expand...
Click to collapse
Of course, because Pixel 6 and Pixel 6 pro are different devices.
Pixel 6 is Product ID "oriole" and Pixel 6 pro Product ID "raven". For now the module v2.05 and less is for Pixel 6 only.
Send me to PM some info from your device to upgrade this for Pixel 6 pro too. No problem, I will add everything into the script for converting.
I use HarryShan's guide. And change GF5KQ to GLU0G for my Pixel 6 Pro. It worked. My phone don't have sound when capture sceen and take photo.
Thank you.
HarryShan said:
This is known issue as even global Pixel do have forced shutter and screenshot sound when a Japanese carrier SIM is inserted, no matter where you use it. In this case MID changing method can't help you.
The module from the other thread may work though as it's directly modifying system UI APK:
GitHub - AndroPlus-org/magisk-module-pixel6: Google Pixel 6シリーズ以降向けのMagiskモジュールです。
Google Pixel 6シリーズ以降向けのMagiskモジュールです。. Contribute to AndroPlus-org/magisk-module-pixel6 development by creating an account on GitHub.
github.com
Downside would be you'll always need Magisk installed. You can have a try.
Click to expand...
Click to collapse
You can also use a gcam mod camera for silent shutter . There used to be a workaround for the silent camera by simswapping in Japan but it was removed or patched in android 12. A Japanese sim will always enable sounds

How To Guide [EU model] Unlock bootloader of European model

As you may know, at the time of writing it's not possible to unlock the bootloader of the European model. Fortunately there's a workaround. To know how it works, scroll to the end of the post.
First of all, this is only for the European RMX3301, but you can try on any other global model that doesn't allow the unlocking of the bootloader. I'm not talking about temporary errors, but of the infamous This phone model does not support deep testing error message.
Before starting I would like to thank polygraphene for their implementation of the Dirty Pipe vulnerability on Android. Without that, this would not have been possible.
Requirements:​
The phone with a decent charge. Do not attempt this procedure with the phone at 10% and then cry if something goes wrong
A compatible build, read below
A Windows or Linux PC with adb and fastboot drivers installed
Check if your build is compatible:​
Go to Settings -> About device -> Version and check Build number:
If your build is between RMX3301_11_A.14 and RMX3301_11_A.21, go to the procedure below
If your build is lower than RMX3301_11_A.14, or higher than RMX3301_11_A.21, install this OTA package to downgrade (or upgrade) to RMX3301_11_A.14
Procedure:​
Make sure under Developer options you have OEM unlocking and USB debugging enabled
Download and extract the attached gt2pro_eu_unlock_dirtypipe_v0.2.zip file
Open a terminal in the folder of the extracted files
Connect the phone to the PC and select the File transfer option
Run the script:
On Windows, type run.bat and press enter
On Linux, type ./run.sh and press enter
Now the phone is temporarily rooted and the phone model is changed to RMX3301. Do not reboot or you will lose this status.
At this point you can follow the procedure on the official forum to unlock the bootloader of the global model. If you already have the Deeptesting app installed, clear its data to make sure it will update.
Changelog:​v0.2:
Show more info about device for better debug
Show the model at the end to check if it worked
For technical people: how does it work?​The script abuses a vulnerability of the Linux kernel called Dirty Pipe (or CVE-2022-0847). For further details, you can visit the official website. This allows us to gain temporary root and overwrite the ro.product.name property, the only one checked by the Deeptesting app. The vulnerability is present in Android and it has been fixed, at least for the Pixel 6, in the May 2022 security update. On the GT 2 Pro, the vulnerability has been fixed with the Android 13 update, while the latest Android 12 build (RMX3301_11_A.21) is still vulnerable. I have tested the procedure personally up to build RMX3301_11_A.16. If you're on a newer build and it doesn't work, please report it in the comments.
Will it work on device X?​If the following conditions are met:
it is a Realme device;
the kernel version is 5.10.66;
there's a global model with a different ro.product.name that can be unlocked;
then you can edit the startup-root file and replace RMX3301 (near the end) with the ro.product.name of the global model and try if it works. If it doesn't, it could be for a lot of reasons. Unfortunately, I can't help you without physically having the device in hand.
If you have further questions about the procedure, please post them below.
woowww... thanks for you aport
I wonder if we can use this temporary root to do some modifications on system.
criszz said:
I wonder if we can use this temporary root to do some modifications on system.
criszz said:
I wonder if we can use this temporary root to do some modifications on system.
Click to expand...
Click to collapse
Excellent question... for example try modific the build regist
Click to expand...
Click to collapse
Rapper_skull said:
As you may know, at the time of writing it's not possible to unlock the bootloader of the European model. Fortunately there's a workaround. To know how it works, scroll to the end of the post.
First of all, this is only for the European RMX3301, but you can try on any other global model that doesn't allow the unlocking of the bootloader. I'm not talking about temporary errors, but of the infamous This phone model does not support deep testing error message.
Before starting I would like to thankpolygraphene for their implementation of the Dirty Pipe vulnerability on Android. Without that, this would not have been possible.
Requirements:
The phone with a decent charge. Do not attempt this procedure with the phone at 10% and then cry if something goes wrong
A compatible build, read below
A Windows or Linux PC with adb and fastboot drivers installed
Check if your build is compatible:
Go to Settings -> About device -> Version and check Build number:
If your build is RMX3301_11_A.14, RMX3301_11_A.15 or RMX3301_11_A.16, go to the procedure below
If your build is lower than RMX3301_11_A.14, or higher than RMX3301_11_A.16, install this OTA package to downgrade (or upgrade) to RMX3301_11_A.14
Procedure:
Make sure under Developer options you have OEM unlocking and USB debugging enabled
Download and extract the attached gt2pro_eu_unlock_dirtypipe.zip file
Open a terminal in the folder of the extracted files
Connect the phone to the PC and select the File transfer option
Run the script:
On Windows, type run.bat and press enter
On Linux, type ./run.sh and press enter
Now the phone is temporarily rooted and the phone model is changed to RMX3301. Do not reboot or you will lose this status.
At this point you can follow the procedure on the official forum to unlock the bootloader of the global model. If you already have the Deeptesting app installed, clear its data to make sure it will update.
For technical people: how does it work?
The script abuses a vulnerability of the Linux kernel called Dirty Pipe (or CVE-2022-0847). For further details, you can visit the official website. This allows us to gain temporary root and overwrite the ro.product.name property, the only one checked by the Deeptesting app. The vulnerability is present in Android and it has been fixed, at least for the Pixel 6, in the may 2022 security update. At the time of writing, the latest build for the GT2 Pro is RMX3301_11_A.16, and it's still vulnerable.
If you have further questions about the procedure, please post them below.
Click to expand...
Click to collapse
When you try the procedure... delete al date of phone? whe finish---- type run.bat and press enter ---- erase all?
criszz said:
I wonder if we can use this temporary root to do some modifications on system.
Click to expand...
Click to collapse
Theoretically you can do everything you can do on a rooted phone (Magisk, but without modules and Zygisk). In practice I never got Magisk to work properly, so I just limited myself to change the property. My goal was to unlock the bootloader, so I did it and installed Magisk.
manu81cba said:
When you try the procedure... delete al date of phone? whe finish---- type run.bat and press enter ---- erase all?
Click to expand...
Click to collapse
My procedure will not delete any data, but after that you have to follow the official procedure to unlock the bootloader, and that will factory reset your phone.
{
"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"
}
I have this error... why?
manu81cba said:
View attachment 5634133
I have this error... why?
Click to expand...
Click to collapse
Can you post the output of adb devices?
Rapper_skull said:
Can you post the output of adb devices?
Click to expand...
Click to collapse
You can explain? no understand.. what do you say?
manu81cba said:
You can explain? no understand.. what do you say?
Click to expand...
Click to collapse
In the terminal, where you are, type adb devices and press enter, then post the output.
Rapper_skull said:
In the terminal, where you are, type adb devices and press enter, then post the output.
Click to expand...
Click to collapse
manu81cba said:
View attachment 5634133
I have this error... why?
Click to expand...
Click to collapse
Yes i have same output on A.16 installed.
manu81cba said:
View attachment 5634153
Click to expand...
Click to collapse
I can see that you have two different versions of adb, one inside the platform-tools folder and one installed elsewhere. Please confirm that by running adb version inside platform-tools and then outside.
Rapper_skull said:
In the terminal, where you are, type adb devices and press enter, then post the output.
Click to expand...
Click to collapse
now put all file decripted to plataform adb... and this result... all ok?
manu81cba said:
now put all file decripted to plataform adb... and this result... all ok?
View attachment 5634159
Click to expand...
Click to collapse
Yes. To make sure, run adb getprop ro.product.name and confirm it's RMX3301.
manu81cba said:
now put all file decripted to plataform adb... and this result... all ok?
View attachment 5634159
Click to expand...
Click to collapse
Working now?
Is rooting temporary? i can modific build.pro? or this process is only for change the model propety?
manu81cba said:
Working now?
Is rooting temporary? i can modific build.pro? or this process is only for change the model propety?
Click to expand...
Click to collapse
No, you can't modify any files, since /system is read-only. Even if you manage to do it, you will brick your device since the bootloader is still locked. If you want to unlock your bootloader, follow the official guide I've linked.
Rapper_skull said:
Yes. To make sure, run adb getprop ro.product.name and confirm it's RMX3301.
Click to expand...
Click to collapse
manu81cba said:
View attachment 5634169
Click to expand...
Click to collapse
Sorry, adb shell getprop ro.product.name

Categories

Resources