[FAQ] Frequently Asked Questions For Moto E [UPDATED-05/10/14] - Moto E 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. 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

Related

[Tutorial] Root FRF91/FRF85B/FRF83/FRF72 (T-Mo/AT&T) Without Unlocking (100% Working)

[Tutorial] Root FRF91/FRF85B/FRF83/FRF72 (T-Mo/AT&T) Without Unlocking (100% Working)
Credits:
Booker-T
M9x3mos
th3fallen
juan413
_Sri_
Amon_RA
cyanogen
For your amazing works leading up to this guide
Notes:
- Donate if I've helped save your HTC warranty.
- This will work! If you can't figure something out, don't get discouraged. Ask here for help.
- After this process, you can flash whatever ROM you like in recovery. I just have the steps showing for CyanMod so you know you have a good, clean system to start off with.
[T-Mo & ATT] Prerequisites:
- Locked Nexus One flashed with FRF85B
(Stuck on FRF91? Use THIS to downgrade to EPE76. Then update back up to FRF85B.)
- Lastet SDK (Click)
- Working ADB (Info)
- The attached .zip "ROOT_FRF83.zip" (Attachment at bottom)
- Got Mac/Linux? (Click Thanks madj42)
Process:
1) Extract the files within "ROOT_FRF83.zip" into the "tools" directory of the extracted SDK package
2) Open a command prompt or terminal and change to the "tools" directory of the extracted SDK package
- Example: Type "cd C:\Users\Matt\Desktop\android-sdk-windows\tools" and hit Enter
3) Type "loop" and hit Enter
4) With phone attached through microUSB, enter Recovery with the battery cover OFF and the SDcard REMOVED.
- Tip: Be careful not to let the battery fall out during this process
- Tip: To enter recovery, boot while holding Volume down button. Then select the recovery option.
5) When you see the HTC devices attached in recovery mode, hit Ctrl+C, then "y", then Enter
6) Slide in SDcard (Make sure there is no update.zip on it at this point)
- Tip: It should slide in and click VERY easily if you trim the tab on the battery properly. A sharp razor blaze works well.
- Tip: I recommend this instead of other methods (paper slip) because it will work without error
- Tip: You only need to cut as far as the SDcard slot goes, you do not need to trim the entire tab
{
"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"
}
7) On your phone, press Power + Volume Up AFTER inserting SDcard
8) Choose "apply sdcard:update.zip"
- Tip: It will fail, but that is expected because there is no update.zip
- Tip: This is done to mount the SDcard after achieving adb while the SDcard was out
9) In your terminal type "adb push flash_image /sdcard/flash_image" and hit Enter
10) In your terminal type "adb push ota.zip /sdcard/update.zip" and hit Enter
11) In your terminal, type "adb push update.zip /sdcard/update.zip" and DO NOT yet hit Enter
12)Ready your finger near the Enter key of your keyboard so that you can quickly hit it once you complete the next step
13) Choose "apply sdcard:update.zip"
14) As soon as you see the yellow installation progress bar, hit Enter on your keyboard
- Tip: If completed properly, you should see a message about rooting adb
15) Choose "Reboot into system"
You now have root access(aka Admin rights) in your stock ROM, but with limited capabilities.
If you want to do any of the following, please continue:
- Flash a custom recovery
- Perform Nandroid backup
- Flash a Rooted Stock Froyo ROM with full capabilities
- Flash CyanogenMod
16) Download the following to the root of your SDcard
- recovery-RA-nexus-v1.7.0.1.img: http://rapidshare.com/files/393267368/recovery-RA-nexus-v1.7.0.1.img
- Note: UnMount your SDcard after copying these files, but keep your phone plugged in
17) In your terminal type "adb shell" and hit Enter
18) In your terminal type "su" and hit Enter
- Tip: At this point, it will hang until you choose "Allow" on your phone with the SuperUser app pop-up
- Tip: $ should now be replaced with #
19) In your terminal, type "mount -o rw,remount /dev/block/mtdblock4 /system" and hit Enter
20) In your terminal, type "cat /sdcard/flash_image > /system/bin/flash_image" and hit Enter
21) In your terminal, type "chmod 775 /system/bin/flash_image" and hit Enter
22) In your terminal, type "flash_image recovery /sdcard/recovery-RA-nexus-v1.7.0.1.img" and hit Enter
23) In your terminal, type "rm /system/etc/install-recovery.sh" and hit Enter
24) In your terminal, type "rm /system/recovery-from-boot.p" and hit Enter
You can now boot into your new Recovery by turning off your phone and turning back on while holding Volume Down.
If you want the latest CyanogenMod, please continue.
25) Download the following to the root of your SDcard
- update-CM-5.0.8-N1-signed.zip: http://cyanogen-updater.googlecode.com/files/update-cm-5.0.8-N1-signed.zip
- gapps-passion-EPF30-signed.zip: http://www.mediafire.com/download.php?mjzwozjojkh
26) Nandroid backup
- Tip: In Recovery, choose "Backup/Restore" then "Nand backup"
- Tip: This will give you an exact copy of your system's current state which you can revert back to at any time
27) Wipe your phone
- Tip: In Recovery, Choose "Wipe" then "Wipe data/factory reset"
28) Apply zip "update-CM-5.0.8-N1-signed.zip"
- Tip: In Recovery, Choose "Flash zip from sdcard"
29) Apply zip "gapps-passion-EPF30-signed.zip"
30) Reboot into your newly rooted phone!
thanks! is there any specific reason why it has to be FRF83 or FRF72 if you know? for us AT&T Nexus User stuck on EPE54B, shouldn't we be able to do the same? or the ota.zip is different in that sense? Please give us some insight. thanks!
Sorry, where is The attached .zip "ROOT_FRF83.zip" ?
where is the attached .zip "ROOT_FRF83.zip"
Oops!! Added link to the top!
Constrabus said:
Oops!! Added link to the top!
Click to expand...
Click to collapse
the link wont work
Link updated
Constrabus said:
4) With phone attached through microUSB, enter Recovery with the battery cover OFF and the SDcard REMOVED.
- Tip: Be careful not to let the battery fall out during this process
5) When you see the HTC devices attached in recovery mode, hit Ctrl+C
6) Slide in SDcard (Make sure there is no update.zip on it at this point)
- Tip: It should slide in and click VERY easily if you trimmed the tab on the battery properly
7) On your phone, press Power + Volume Up
8) Choose "Apply update.zip from SDcard"
- Tip: It will fail, but that is expected.
9) In your terminal type "adb push flash_image /sdcard/flash_image" and hit Enter
Click to expand...
Click to collapse
Still getting either adb with no sd, or sd with no adb.
When I follow your exact process, apply "sdcard:update.zip" returns
"-- Install from sdcard...
Finding update package...
E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
(No such file or directory)
E:Can't mount SDCARD:update.zip
Installation aborted."
and then "adb push flash_image /sdcard/flash_image" returns
"failed to copy 'ota.zip' to '/sdcard/flash_image'ermission denied".
These are the exact same returns I get when I tried the process without a card inserted, which is what leads me to believe the card is in but not mounted.
Is there a way to tell adb to (re)mount the SD card in recovery?
Or am I doing something wrong...
Can you walk me through just those particular steps? Like Cookbook-detailed instructions.
Make sure that you are inserting the sdcard BEFORE you press Power and Volume Up to reveal the recovery options and AFTER you get adb connected in recovery mode with loop.
Also make sure you can get adb working while in android to make sure the driver is installed properly.
lostinatlanta said:
Still getting either adb with no sd, or sd with no adb.
When I follow your exact process, apply "sdcard:update.zip" returns
"-- Install from sdcard...
Finding update package...
E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
(No such file or directory)
E:Can't mount SDCARD:update.zip
Installation aborted."
and then "adb push flash_image /sdcard/flash_image" returns
"failed to copy 'ota.zip' to '/sdcard/flash_image'ermission denied".
These are the exact same returns I get when I tried the process without a card inserted, which is what leads me to believe the card is in but not mounted.
Is there a way to tell adb to (re)mount the SD card in recovery?
Click to expand...
Click to collapse
weird thing is adb devices do not see my phone even without SD card...
guess froyo is a must to get this working?
i am on EPE54B, still...
I now have an unlocked, newly unrooted FRF83. Will this tutorial still work for me?
t mobile usa 3g network, stock recovery image. I think I am unrooted because there was a warning in the tutorial and my adb shell denies super user permissions.
kaiser_tytnii said:
weird thing is adb devices do not see my phone even without SD card...
guess froyo is a must to get this working?
i am on EPE54B, still...
Click to expand...
Click to collapse
This guide is for people stuck on FRF83 because you can't revert to the older build where other guides worked.
adambenjamin said:
I now have an unlocked, newly unrooted FRF83. Will this tutorial still work for me?
t mobile usa 3g network, stock recovery image. I think I am unrooted because there was a warning in the tutorial and my adb shell denies super user permissions.
Click to expand...
Click to collapse
If you are unlocked, this guide would be redundant for you. The purpose of this guide is to root without having to unlock, thus preserving your warranty.
Shell script version of loop.bat:
I assume this will work...
Code:
while true; do adb devices; done
Constrabus said:
If you are unlocked, this guide would be redundant for you. The purpose of this guide is to root without having to unlock, thus preserving your warranty.
Click to expand...
Click to collapse
I still would like to get my root back. Will that part of this tutorial work to get the root back?
EDIT: Got it rooted. wow that was easy.
Based on you providing links for recovery-RA-nexus-v.1.7.0.1.img, update-CM-5.0.8-N1-signed.zip, google addon EPF30; will the steps involving these install Cyanogen on my phone?
I was hoping to do this process without wiping my phone's memory and keeping my stock FRF83.
what25 said:
Based on you providing links for recovery-RA-nexus-v.1.7.0.1.img, update-CM-5.0.8-N1-signed.zip, google addon EPF30; will the steps involving these install Cyanogen on my phone?
I was hoping to do this process without wiping my phone's memory and keeping my stock FRF83.
Click to expand...
Click to collapse
If you don't want the Cyanogen ROM or RA recovery just skip step #22 and stop with step #24. I didn't follow this tutorial as I did Booker-T's method with some tweaks but if you do what I said you should be fine.
madj42 said:
If you don't want the Cyanogen ROM or RA recovery just skip step #22 and stop with step #24. I didn't follow this tutorial as I did Booker-T's method with some tweaks but if you do what I said you should be fine.
Click to expand...
Click to collapse
You dont have to use that rom, you can flash any other rom as long as you have root. Paul obrien offeres a rooted FRF83 rom
I was able to do this without taking out / putting the SD card in (and thus avoided filing down my battery. I didn't run "loop.bat" until I was highlighting the Recovery icon, the ran it, when into Recovery, and adb picked it up.
Worked perfect!
Just, when flashing recovery, the better terminal emulator was giving me an error, i used Rom Manager to flash the recovery, and back to terminal to rm /system/etc/ blah blah ....GREAT Tutorial!

[How-To] Root the Slide with any sw verision and flash cust rom

First I want to thank all the developers here and I take no credit for this all i did was put together a full set of steps
Big thanks to nbetcher with help from ChiefzReloaded who ultimatley go the steps for the exploit needed and to 743c who developed the exploit
Following these steps from beginging to end will allow you to full obtain root and flash a new rom from begining to end. Follow each step and you will be good.
Easy root guide for the MyTouch slide currently any version downloads at bottom
Make sure before starting that the device has atleast 50% battery charge.
Go to C drive on pc and make a new folder we will call root
Copy then all the files from the zip into that folder.
___________________________________________________________
not required but you should also copy a rom that you want to use the the root of the sdcard on the device too then I have included teamfenix 1.7.1 as is a stable 2.2 android rom but you can use anyone you want.
___________________________________________________________
First we will need to get some files to the device would be easiest with a following settings already done:
settings > applications > development > USB debugging (check mark here)
settings > connect to pc > charge only
settings > wireless & networks > wifi unchecked (important)
settings > sound & display > screen timeout > never
Now connect device
Then start the command prompt and uses these commands to move the files we will need
cd C:\root
myroot (just allow to continue we covered the steps in it already)
Will take a few minutes for that to copy everything over to the places on the phone where we need them. will look like is frozen on ESPRIMG.zip that is normal don't interupt it just let it go.
when done we are now ready to actually get root and allow phone to let us get a recovery on there we can use with a few more commands
commands_______ things in () don't run just memos
adb shell
(should now see a $)
cd /sqlite_stmt_journals
chmod 0755 exploid
./exploid
(will have initated the loop hole to get root)
(at this time go to settings and turn wifi on and then back off before continuing)
./exploid
---The password is : secretlol
(You should now have a # instead of a $)
cd /data/local
chmod 04755 *
/data/local/flash_image misc /data/local/mtd0.img
_______________________________________________________________
ok now we are set to apply the engineering build to get a custom rom
Turn off the device
Press and hold volume down and then power up and hold both
let go when see the 3 skateboarding androids
give the phone a minute then will read the moded file on card
when is ready press volume up to apply this update
--- This will take a while just let it run
WAIT - when done it will ask you to reboot DON'T
press volume down for no
then back on bootloader screen press volume down once to highlight recovery and select with power to boot recovery
on the recovery you will have a device with a triangle
hold volume up and power for a second together
volume down and power to select for apply update.zip
and you will then be loaded into the clockwork recovery and will beable to flash the rom of your choosing from sd card.
You can use touch pad not to scroll down and select install zip from sd
select choose zip from sdcard
find your rom and apply
You are now rooted enjoy
needed files - http://www.4shared.com/file/J6i52nwy/slideroot.html
rom i use - http://forum.xda-developers.com/showthread.php?t=749312
I keep getting permission denied when I try to run the chmod command its very frustrating.. the myroot runs perfect everything flashes but then it gives me permission denied any ideas? plz
where you able to cd into the proper directory. what chmod are you getting the error on.
just got it to work good job Artiszan everything is so much smoother then how it use to be.. I had to power off my phone and format my sdcard idk why but it worked and was able to chmod and do everything thanks bro
TheArtiszan said:
First I want to thank all the developers here and I take no credit for this all i did was put together a full set of steps
Big thanks to nbetcher with help from ChiefzReloaded who ultimatley go the steps for the exploit needed and to 743c who developed the exploit
Following these steps from beginging to end will allow you to full obtain root and flash a new rom from begining to end. Follow each step and you will be good.
Easy root guide for the MyTouch slide currently any version downloads at bottom
Make sure before starting that the device has atleast 50% battery charge.
Go to C drive on pc and make a new folder we will call root
Copy then all the files from the zip into that folder.
___________________________________________________________
not required but you should also copy a rom that you want to use the the root of the sdcard on the device too then I have included teamfenix 1.7.1 as is a stable 2.2 android rom but you can use anyone you want.
___________________________________________________________
First we will need to get some files to the device would be easiest with a following settings already done:
settings > applications > development > USB debugging (check mark here)
settings > connect to pc > charge only
settings > wireless & networks > wifi unchecked (important)
settings > sound & display > screen timeout > never
Now connect device
Then start the command prompt and uses these commands to move the files we will need
cd C:\root
myroot (just allow to continue we covered the steps in it already)
Will take a few minutes for that to copy everything over to the places on the phone where we need them. will look like is frozen on ESPRIMG.zip that is normal don't interupt it just let it go.
when done we are now ready to actually get root and allow phone to let us get a recovery on there we can use with a few more commands
commands_______ things in () don't run just memos
adb shell
(should now see a $)
cd /sqlite_stmt_journals
chmod 0755 exploid
./exploid
(will have initated the loop hole to get root)
(at this time go to settings and turn wifi on and then back off before continuing)
./exploid
---The password is : secretlol
(You should now have a # instead of a $)
cd /data/local
chmod 04755 *
/data/local/flash_image misc /data/local/mtd0.img
_______________________________________________________________
ok now we are set to apply the engineering build to get a custom rom
Turn off the device
Press and hold volume down and then power up and hold both
let go when see the 3 skateboarding androids
give the phone a minute then will read the moded file on card
when is ready press volume up to apply this update
--- This will take a while just let it run
WAIT - when done it will ask you to reboot DON'T
press volume down for no
then back on bootloader screen press volume down once to highlight recovery and select with power to boot recovery
on the recovery you will have a device with a triangle
hold volume up and power for a second together
volume down and power to select for apply update.zip
and you will then be loaded into the clockwork recovery and will beable to flash the rom of your choosing from sd card.
You can use touch pad not to scroll down and select install zip from sd
select choose zip from sdcard
find your rom and apply
You are now rooted enjoy
needed files - http://www.4shared.com/file/J6i52nwy/slideroot.html
rom i use - http://forum.xda-developers.com/showthread.php?t=749312
Click to expand...
Click to collapse
This worked so well and for lack of a better word well it is perfect. My friend watched me, and saw how easy it was and he did his new mt3gs as well. Many thanks to all the peeps who worked on this and thanks to TheArtiszan for making this into english. I'm not that tech savy yet. As they say if I can do it anyone can. Thanks again
Error, read only file system
If you get read only errors, you may want to check out Radu Motisan's thread about how to "Write on the Android Read-only file system" on PocketMagic.net (sorry, can't post outside links yet. Just search for the quoted phrase on the aforementioned webpage to read the original post) Thank you Radu Motisan.
A brief overview:
Most of Android partitions are mounted as read only.
For eg. /system where most of the libs and other system components are stored, including the permissions.xml file.
You can temporary re-mount the /system partition to read write and load your new files to that partition!
using adb shell or the android terminal with root privileges, do the following:
See the currently mounted partitions:
Code:
# mount
Then re-mount to read-write the partition you are interested in , eg. /system:
Code:
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3
.../...
You can also:
Code:
mount -o rw,remount -t rootfs /
Click to expand...
Click to collapse
CAVEAT! Please read.
On my MT3GS I had to enter the command to remount the rootfs as read/write a little differently to make it work with my #TEAMSLIDE Kanged CM6
The command was:
Code:
mount -o rw,remount rootfs /
My mount command didn't like the "-t" tag. Works just fine without it for me.
Why did you copy+paste nbetcher's root method?
{
"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"
}
Can anyone please tell me where to stop if I want to continue with the stock rom but just want phone to be rooted.??...with the steps outlined here doe I need to install another ROM? how do I maintain the stock ROM? and just apply only the root?
Churusaa said:
If you get read only errors, you may want to check out Radu Motisan's thread about how to "Write on the Android Read-only file system" on PocketMagic.net (sorry, can't post outside links yet. Just search for the quoted phrase on the aforementioned webpage to read the original post) Thank you Radu Motisan.
A brief overview:
CAVEAT! Please read.
On my MT3GS I had to enter the command to remount the rootfs as read/write a little differently to make it work with my #TEAMSLIDE Kanged CM6
The command was:
Code:
mount -o rw,remount rootfs /
My mount command didn't like the "-t" tag. Works just fine without it for me.
Click to expand...
Click to collapse
Does this work with a stock (unrooted) MTS3G? I don't have SU permissions, and even when using the aforementioned method you talked about, it still does not work
Keeps saying chmod /system :read only file system
TheArtiszan said:
First I want to thank all the developers here and I take no credit for this all i did was put together a full set of steps
Big thanks to nbetcher with help from ChiefzReloaded who ultimatley go the steps for the exploit needed and to 743c who developed the exploit
Following these steps from beginging to end will allow you to full obtain root and flash a new rom from begining to end. Follow each step and you will be good.
Easy root guide for the MyTouch slide currently any version downloads at bottom
Make sure before starting that the device has atleast 50% battery charge.
Go to C drive on pc and make a new folder we will call root
Copy then all the files from the zip into that folder.
___________________________________________________________
not required but you should also copy a rom that you want to use the the root of the sdcard on the device too then I have included teamfenix 1.7.1 as is a stable 2.2 android rom but you can use anyone you want.
___________________________________________________________
First we will need to get some files to the device would be easiest with a following settings already done:
settings > applications > development > USB debugging (check mark here)
settings > connect to pc > charge only
settings > wireless & networks > wifi unchecked (important)
settings > sound & display > screen timeout > never
Now connect device
Then start the command prompt and uses these commands to move the files we will need
cd C:\root
myroot (just allow to continue we covered the steps in it already)
Will take a few minutes for that to copy everything over to the places on the phone where we need them. will look like is frozen on ESPRIMG.zip that is normal don't interupt it just let it go.
when done we are now ready to actually get root and allow phone to let us get a recovery on there we can use with a few more commands
commands_______ things in () don't run just memos
adb shell
(should now see a $)
cd /sqlite_stmt_journals
chmod 0755 exploid
./exploid
(will have initated the loop hole to get root)
(at this time go to settings and turn wifi on and then back off before continuing)
./exploid
---The password is : secretlol
(You should now have a # instead of a $)
cd /data/local
chmod 04755 *
/data/local/flash_image misc /data/local/mtd0.img
_______________________________________________________________
ok now we are set to apply the engineering build to get a custom rom
Turn off the device
Press and hold volume down and then power up and hold both
let go when see the 3 skateboarding androids
give the phone a minute then will read the moded file on card
when is ready press volume up to apply this update
--- This will take a while just let it run
WAIT - when done it will ask you to reboot DON'T
press volume down for no
then back on bootloader screen press volume down once to highlight recovery and select with power to boot recovery
on the recovery you will have a device with a triangle
hold volume up and power for a second together
volume down and power to select for apply update.zip
and you will then be loaded into the clockwork recovery and will beable to flash the rom of your choosing from sd card.
You can use touch pad not to scroll down and select install zip from sd
select choose zip from sdcard
find your rom and apply
You are now rooted enjoy
needed files - http://www.4shared.com/file/J6i52nwy/slideroot.html
rom i use - http://forum.xda-developers.com/showthread.php?t=749312
Click to expand...
Click to collapse
Command promps aren't working. You say to follow these steps and it's easy, but the steps are incomplete, and you assume the reader knows what you mean. Please break it down a little more. For example in the command promp you say to type cd C:\root the it says myroot, what does that mean? It's not as easy as you think.
The whole thing falls apart around the time I try and flash ESPRIMG.zip. I get into bootloader and it just skips right on by ESPRIMG.zip with "no image found" and of course when flashing update.zip from the memory card in recovery it fails the signature and refuses to flash. I cannot get into clockwork for the life of me.
loganthered said:
The whole thing falls apart around the time I try and flash ESPRIMG.zip. I get into bootloader and it just skips right on by ESPRIMG.zip with "no image found" and of course when flashing update.zip from the memory card in recovery it fails the signature and refuses to flash. I cannot get into clockwork for the life of me.
Click to expand...
Click to collapse
Then you don't have the file ESPRIMG.zip on the root of your sdcard.
I've tried every root method for the slide and most of them worked but not without problems, this Root method is exactly down to the T, perfectly executed, no problems whatsoever. Thanks for everyone who helped make this happen and for the OP you made this super easy.
Did this on my first attempt, I was coming from stock with the OTA update and had no issues. Great job to everyone involved!
Sent from my rooted myTouch Slide using XDA app....
Video of the root...
Can someone please post a video of the rooting process? I'm deathly scared that I'm gonna mess something up and break my new phone. This is my first android phone and my first time rooting one. And in the video could you show how to get the Android SDK and how to get it ready to root? It would be soooo appreciated.
supermario12312 said:
Can someone please post a video of the rooting process? I'm deathly scared that I'm gonna mess something up and break my new phone. This is my first android phone and my first time rooting one. And in the video could you show how to get the Android SDK and how to get it ready to root? It would be soooo appreciated.
Click to expand...
Click to collapse
Perhaps you can try this guide which was written by a n00b, for n00bs. It consolidates a lot of details together and doesn't assume you already know about Android tools and hacking.
yea they should make a video....it would be a lot easier for us please!!!
is there anyway to get into clockwork and make a nandroid before applying the eng rom
i can't get my pc to find my mt3gs
c:\root>myroot
c:\root>clr
'clr' is not recognized as an internal or external command,
operable program or batch file.
"This is made for MyTouch 3G Slide with a combination of a few methods"
"Originally found at xda developers I did develop the exploit just made this sim
ple tutorial"
"At this point, your phone should be booted as normal and connected"
"Make sure of these things:"
"USB Debugging Enabled - Settings/Applications/Development"
"USB Connection Type - Charge Only (select on your notifications bar)"
"Wifi is currently turned off."
"Confirm that the screen on the device is set to never timeout."
"Press enter to begin the process"
c:\root>pause
Press any key to continue . . .
c:\root>clr
'clr' is not recognized as an internal or external command,
operable program or batch file.
"Please Wait...Initiating root setup to device and copying files this will take
a while"
c:\root>adb devices
List of devices attached
c:\root>adb push exploid /sqlite_stmt_journals
error: device not found
c:\root>adb push flash_image /data/local
error: device not found
c:\root>adb push mtd0.img /data/local
error: device not found
c:\root>adb push update.zip /sdcard
error: device not found
c:\root>adb push esprimg.zip /sdcard/ESPRIMG.zip
error: device not found
"follow the rest of the steps now"
c:\root>pause
Press any key to continue . . .
Your phone is not being recognized in adb mode. First try starting phone normally and go under settings to applications to development then check mark usb debugging pluf in device and give the pc a min
In c:/root run this
Adb devices
Should see device listed beneath. If not sounds like a driver is messed up. If this is the case I would first try and install pdanet on the computer as this should get us the right drivers. I assume you are running windows right?
Sent from my T-Mobile myTouch 3G Slide using XDA App

X10 Custom ROM AOSP 2.2.1 : How to for dummies

SINCE FREE X10 IS NOW BETA, THIS HOW TO IS NO LONGER VALID
Hello world !
I noticed there was nothing to explain simply how to install the increible X10 Free Rom in dual-boot with your regular 2.1 rom of Zdzihu.
** No responsability for anything, you are all responsible of what you're doing !! **
** Please follow ALL these steps. Don't try to be Indiana Jones by flashing your device without all the tools needed !!! **
INSTALL
(for 1st install)
Before attempting anything, make sure you have AT LEAST 50% of battery charge. Don't try anything with low battery, you can abort the flashing and brick your device !!!
Please make sure you're also running a 2.1 rom (Generic, nordic, official, custom...)​
- Download FreeX10 v0.0.1 file (NOT 002 yet !!!)
- Download Android SDK
You don't need to save the entire archive (but you can), you just need the Tools folder (because it contains ADB, the Android Debug Bridge we need to install files).
- On x10 :
Download and install Busybox (from Market), make sure it says "Done!".
Connect your x10 in USB, mount SD card, and copy files FreeX10.zip and install on the root of your SD Card.
Enable USB debugging (Parameters > Applications > Development).
- On your computer, go in the Tools folder, open a DOS prompt (for Windows 7 : hold CAPS + right click, you'll see Open a DOS prompt) and
type :
Code:
adb shell
(this will run ADB shell... You will get a "$")
- Type :
Code:
su
(this will make you super-user, you will get a "#")
- Type :
Code:
dd if=/sdcard/install of=/data/install && chmod 777 /data/install && /data/install
(It will display "11", "1+1", or "inflating:..." ...)
- Wait, have a beer, pray for your sins for your phone not to turn into a $600 brick
- One minute after, when it shows
Code:
All done, please reboot!
, reboot ! (But you can gently quit ADB by typing
Code:
exit
twice
)
Note : regarding me, I typed "exit" to quit ADB, I turned off ADB on phone and disconnected USB. You can do, it's even safer
- Wait up to 5 minutes for the phone to boot, it is NORMAL !!!! It looks stuck on Sony Ericsson logo and/or on Free X10 logo, it's NOT stuck !!! You MUST wait !!!!
- It will finally run normal, your phone is alive and 2.2-hearted !!
You are now eligible to install v0.0.2 (as it comes as an update).
Dual Boot usage
This rom comes with a great Dual Boot, which means the 2.2.1 is installed safely apart from your original 2.1 rom. This means you can switch back anytime to stock rom. To say it simply :
- Your Android 2.1 is here, and no changes are made to it (apps, version, etc etc). It is stored as it has to be, in the internal 1Gb phone memory storage (called the "NAND").
- FreeX10 (2.2.1) is running from image files (like .ISO files) stored in your SD Card. This means the two Android are living together peacefully, without affecting (theorically) each other.
FreeX10 mainly creates a bootloader, for you to choose whether to test 2.2.1, or go back to 2.1 for your daily use.
- To run 2.2.1 : do nothing (default boot)
- To run 2.1 : press any key at boot, when it shows "Sony Ericsson".
Notes when upgrading to v0.0.2 :
- As Android is stored into image files (.IMG), upgrading will wipe out all your content (it does a fresh "install"), make backup of what you need !
- to avoid future bugs, altough you're not forced to do, do the routines to make sure Wifi, root, packages install, ... work. This is because USB debug can break, so you won't be able to use ADB to fix these bugs
- Root is strongly recommended to work, because it's cool and because the CPU performance is set to highest : stuck at 998MHz all the time, it will drain your battery like hell ! You can switch it back to original power saving plan (ondemand plan) by using (ie) SetCPU. Root required !
If your Android goes instable, does not work anymore, or you want a fresh install after lots of tests, simply drag and drop the original v0.0.2 .img files on your SD card. This will make you boot into a fully fresh install.
For all bugs, commands, etc.. Please go first to this excellent (and very easy) thread !!
Nice..
How about one on AOSP 2.1
Perceval from Hyrule said:
Hello world !
I noticed there was nothing to explain simply how to install the increible X10 Free Rom in dual-boot with your regular 2.1 rom of Zdzihu.
Click to expand...
Click to collapse
nice dummies HOW TO
and ohhh my god there is dummies
all comands needed
INSTALLATION
1. Download the rom package (FreeX10_alpha-release_0.0.1.tar.bz2)
2. Unpack it to the root (main folder) of your SD Card
3. Connect your phone in USB Debugging mode
4. Open ADB shell, switch to root user (SU)
5. Issue the command
dd if=/sdcard/install of=/data/install && chmod 777 /data/install && ./data/install
6. Reboot when installation is finished
7. Enjoy
---------------------------------------------------------------------------------------------
CHANGE BOOT PRIORITY
Copy chargemon.txt file to
/system/bin
folder ON YOUR ORIGINAL 2.1 ROM, NOT FROYO!!!
---------------------------------------------------------------------------------------------
UPGRADE TO 0.0.2 VERSION
Boot into 2.1, unpack the content of FreeX10_alpha-release_0.0.2-UPDATE.tar.bz2 into
/sdcard/FreeX10
folder and reboot into updated 2.2!
NOTES:
1. SMS vibrate is disabled by default; open Messaging, press MENU button -> settings -> vibrate -> always
2. If you don't have radio (network) after 1st boot, please open ADB shell and issue this command:
killall servicemanager
3. If you don't have root access, please open ADB shell and issue this command:
chmod 4755 /system/bin/su
---------------------------------------------------------------------------------------------
hope it helps too
UPDATE TO v.0.0.2
Note : you can only update from 0.0.1 to 0.0.2. I mean you can't do a fresh install of 0.0.2, you MUST have 0.0.1 installed !
- Download v0.0.2 from main thread.
- Run your device on your regular 2.1 rom (while off, power on, and press any button when it displays Sony Ericsson logo)
- Mount the SD Card, then copy data.img and system.img from the archive into the folder /FreeX10. Replace the two .img files.
- Reboot into 2.2, have fun ^^
OmegaRED^ said:
Nice..
How about one on AOSP 2.1
Click to expand...
Click to collapse
I'll try to do one if I get time, but I need a fully working ROM as my phone is useful for my life (still waiting for 2.1 stable )
Thanks for your posts all, it will help everybody who want to try the 2.2
(as it is safe and running from SD card, very very very cool idea !)
Help followed your guide get adb shell not a internal command what am i doing wrong been trying this for hours now
I found drawing a pentagram in human blood and chanting a few words can do wonders too.
fastphil said:
Help followed your guide get adb shell not a internal command what am i doing wrong been trying this for hours now
Click to expand...
Click to collapse
root privileges do you have it?
unmount sdcard
OmegaRED^ said:
I found drawing a pentagram in human blood and chanting a few words can do wonders too.
Click to expand...
Click to collapse
sarcasm...love it
rendeiro2005 said:
root privileges do you have it?
unmount sdcard
Click to expand...
Click to collapse
yes mate i do have root access titanium etc works fine just cant get adb shell to run
When i installed 2.2, it rebooted and when to the sony ericsson logo for almost an hour, does this mean i have to reinstall 2.1, and if so, i would i accomplish this
fastphil said:
yes mate i do have root access titanium etc works fine just cant get adb shell to run
Click to expand...
Click to collapse
and what about sdcard?
uncheck nount/unmount
rendeiro2005 said:
and what about sdcard?
uncheck nount/unmount
Click to expand...
Click to collapse
done that too
fastphil said:
done that too
Click to expand...
Click to collapse
can you post a screenshot of cmd?
ok will do
I am still having problems also...
after I type the cmd...
dd if=/sdcard/install of=/data/install && chmod 777 /data/install && /data/install
it just says:
1+1 records in
1+1 records out
520 bytes transferred in 0.003 secs...
#
so, where am I going wrong?
fyi, I am trying to install v001, not the update, and the phone is rooted, busybox is installed. Sorry, but I have tried for a while now and I finally have to just ask for help. Thanks guys.
here pic off cmd
{
"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"
}
fastphil said:
Help followed your guide get adb shell not a internal command what am i doing wrong been trying this for hours now
Click to expand...
Click to collapse
Does it work when your run "adb" command only ?
It looks to me your error is because you're not in the folder where adb.exe is
It is in folder tools, if you try to run it from root directory (where is the android app with nice icon) it won't work for sure
Edit: didn't see your screenshot >> you are NOT in the correct folder !! (so Windows is searching for a registered command which does not exist, I think there's a thread somewhere on how to add it as a registered (I mean global) command)
You must download Android SDK (22mb... Lmao regarding 4gb for iOS ), extract the archive and go in the tools folder. Here is adb.exe.
when i try & run adb exe it does not open it just closes right away

[GUIDE] Recover FULL GT-I8160P if flashed to GT-I8160 (non-P)

{
"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"
}
UPDATED 2013-09-06 (NEW AND EASY WAY with links to GB/JB FULL 3-parted Firmwares)
UPDATED 2013-09-05 (I8160PXXMG2_I8160POXXMG2_624MB_MULTI_ROOT)
UPDATED 2013-07-26 (USB Debugging is not needed for working with ADB in Android System Recovery)
UPDATED 2013-07-24 (I8160POXXMF1_MULTI & I8160POXXMF1_MULTI_ROOT)
This GUIDE is for those who own an GT-I8160P and flashed it to an GT-I8160 (non-P) with one of the leaked JB FW MB2/MB4 and/or MC8 or mixed MC8/ME1 or GB RUS LK6 (3-Parted).
This will bring back your FULL GT-I8160P with incl. Baseband, Bootlogo, Model info in Recovery, etc!
Without any Counter increase or unofficial custom Binarys!
Old way (NOT recommended anymore because to difficult for some - but still working)
Whats needed:
- Your ROOTED GT-I8160P has an active and working IMEI currently! This is not a guide to bring back IMEI!
- USB-Debugging is activated! - Not needed for ADB
- You know how to ROOT your Phone! GB or JB having different methods! - Good rooting HOW-TO [http://forum.xda-developers.com/showpost.php?p=39799320]
- Installed ADB and basic knowledge in ADB (I recommend installation to C:\ADB>)
- Installed ODIN 3.07 and basic knowledge in flashing with ODIN 3.07
- Knowledge how to enter Android System Recovery and ODIN Download Mode
- External SD-Card (everyone should have one if you own a 8160P)
- Phone is connected with USB cable to PC
- some patience
Which Files are needed:
- I8160P_DBT.rar (Contains I8160P_DBT.bin) [http://d-h.st/Q4L]
- ANY FULL original GB or JB Firmware for GT-I8160P [http://www.sammobile.com/firmwares/1/?model=GT-I8160P&pcode=0#firmware]
Optional Files
- I recommend to use JB FW I8160PXXME1_I8160PDBTME1_DBT [http://www.hotfile.com/dl/222919379/f5c8dfe/I8160PXXME1_I8160PDBTME1_DBT.zip.html]
- 1st TIP: Made by me MULTI-CSC FW I8160PXXMF1_I8160POXXMF1_MULTI [http://d-h.st/TNo]
- 2nd TIP: Made by me MULTI-CSC Pre-Rooted FW I8160PXXMF1_I8160POXXMF1_MULTI_ROOT [http://d-h.st/MeA]
- 3rd TIP: Made by me MULTI-CSC Pre-Rooted FW I8160PXXMG2_I8160POXXMG2_624MB_MULTI_ROOT [http://d-h.st/TEA]
- FULL_NAND_BACKUP_ADB.rar (ADB with easy to handle FULL BACKUP and FULL RESTORE script) [http://d-h.st/Efj]
Further Information
- If you go back to GB and do rooting with Kernel than your Counter will be increased!
- If everything went well your Data remains untouched! (If you did not Wiping Data and Factory Reset)
- BUT: Wiping Data and Factory Reset is still recommended after you finished HOW-TO!
- Keep the Backup of CSPSA_FS and MODEM_FS + EFS save! This is your Serialnumber, IMEI and MAC adress!
- Use ALL ADB commands from your PCs CMD - Command Prompt (e.g. C:\ADB>) while your Phone is in (stock) Android System Recovery
- If you got ADB message: mount: Device or resource busy - Don't care about it! Your SD-Card is already mounted! Go ahead!
- Its sometimes needed to let the SAMSUNG Android ADB Interface install its driver new. That happens if you came from JB and go to GB and vice versa.
Delete old ADB Interfaces in System Control on PC [if needed "Show hidden devices"] but do NOT delete Drivers!
De- and Replug USB that PC can install new ADB Interface. Only do the driver reinstallation if during ADB commands your Phone is not recognized.
Disclaminar:
I'am not responsible if you brick your phone. Keep in mind that we do some critical commands for partition copy/write here.
If you are NOT familar with ADB or ODIN please don't try this at home!
Special thanks goes to:
avkiev @ xda (his very nice xls file of 8160/8160P partitions makes things easy to understand)
Szaby59 @ xda (for his findings that IMEI could be in partition CSPSA_FS)
matthias76 @ android-hilfe (for his hint to changed MAC adress -> solved)
Also thanks goes out to for thier general help
knipseringo @ xda and android-hilfe
KevinNash @ xda
angrybb @ xda
Optional
- Before you start I recommend to make a FULL (incl internal SDCard) Nand-Backup of 3,68 GB (3.959.422.976 Bytes) to external SD-Card
- This Will take 6-7 mins - could be more if your SD-Card is slow.
A) Enter stock Android System Recovery
B) Mount SD-Card
Code:
adb shell su -c "mount -t vfat -o rw /dev/block/mmcblk1p1 /sdcard"
C) FULL Backup:
Code:
adb shell su -c "dd if=/dev/block/mmcblk0 of=/sdcard/fullbackup.img bs=4096"
Option: FULL Restore - If you want to go back to old state of your Phone
Code:
adb shell su -c "dd if=/sdcard/fullbackup.img of=/dev/block/mmcblk0 bs=4096"
Here we go:
1.) Move File I8160P_DBT.bin from Archive to root of external SD-Card
2.) Enter stock Android System Recovery
3.) Open Command Promt (CMD) to you ADB folder (e.g. C:\ADB> )
Leave the CMD ADB Window open. We need it again.
4.) Mount external SD-Card
Code:
adb shell su -c "mount -t vfat -o rw /dev/block/mmcblk1p1 /sdcard"
5.) Backup CSPSA_FS and MODEM_FS + EFS to external SD-Card
Code:
adb shell su -c "dd if=/dev/block/mmcblk0 of=/sdcard/CSPSA_FS.img bs=4096 skip=384 count=384"
Code:
adb shell su -c "dd if=/dev/block/mmcblk0 of=/sdcard/MODEM_FS_EFS.img bs=4096 skip=1024 count=6656"
6.) Write I8160P_DBT.bin from external SD-Card to your Phone
Code:
adb shell su -c "dd if=/sdcard/I8160P_DBT.bin of=/dev/block/mmcblk0 bs=4096 count=17664"
7.) Go directly into ODIN Downloadmode (Hold the 3 Keys as long as needed directly out of Android System Recovery)
8.) Flash FULL original GT-I8160P Firmware with ODIN 3.07 (PDA)
9.) After ODIN rebooted let your Phone boot completely! activate USB Debugging
10.) Root your Phone! (Keep in mind: JB and GB having different methods!)
11.) Enter stock Android System Recovery
12.) Mount external SD-Card
Code:
adb shell su -c "mount -t vfat -o rw /dev/block/mmcblk1p1 /sdcard"
13.) Write saved CSPSA_FS and MODEM_FS + EFS from external SD-Card to Phone
Code:
adb shell su -c "dd if=/sdcard/CSPSA_FS.img of=/dev/block/mmcblk0 bs=4096 seek=384 count=384"
Code:
adb shell su -c "dd if=/sdcard/MODEM_FS_EFS.img of=/dev/block/mmcblk0 bs=4096 seek=1024 count=6656"
14.) Reboot and be Happy that the FULL GT-I8160P with working IMEI is back in Town!
Without any Counter increase or unofficial custom Binarys!
Optional
- Before you start I recommend to make a FULL (incl internal SDCard) Nand-Backup of 3,68 GB (3.959.422.976 Bytes) to external SD-Card
- This Will take 6-7 mins (on an SDHC 32GB Class 10) - could be more if your SD-Card is slow.
A) Enter stock Android System Recovery
B) Mount SD-Card
Code:
adb shell su -c "mount -t vfat -o rw /dev/block/mmcblk1p1 /sdcard"
C) FULL Backup:
Code:
adb shell su -c "dd if=/dev/block/mmcblk0 of=/sdcard/fullbackup.img bs=4096"
Option: FULL Restore - If you want to go back to old state of your Phone
Code:
adb shell su -c "dd if=/sdcard/fullbackup.img of=/dev/block/mmcblk0 bs=4096"
NEW WAY (recommended)
Whats needed:
- Your [email protected] has an active and working IMEI currently! This is not a guide to bring back IMEI!
- Installed ODIN 3.07 (and Samsung Drivers for flashing) and basic knowledge in flashing with ODIN 3.07
- CWM Recovery (Files are linked) for GB or JB (depends on which you are)
- Knowledge how to enter CWM Recovery and ODIN Download Mode
- Knowledge how to install ZIP files from external SD-Card with CWM Recovery
- External SD-Card (everyone should have one if you own a 8160P)
- some patience
Which files are needed:
- BACK_TO_THE_I8160P.zip (CWM installable zip file) [http://d-h.st/Vcn]
- CWM_Recovery_GB_JB.rar (archive with CWM for GB and JB - unpack it) [http://d-h.st/6Nv]
AND ONE OF THE FOLLOWING FIRMWARES
- FULL 3-parted GT-I8160P GB (2.3.6) Firmware DBT (Open Germany) CODE_GT-I8160P_I8160PXXLK2_CL1211774_REV00_user_SEC_KEY_XLK2_4G [http://d-h.st/fWn]
OR
- FULL 3-parted GT-I8160P JB (4.1.2) Firmware DBT (Open Germany) CODE_GT-I8160P_I8160PXXME1_DBT_1106830_REV00_user_low_ship [http://d-h.st/v6N]
OR
- FULL 3-parted GT-I8160P JB (4.1.2) Firmware OXA (Open Europe) CODE_GT-I8160P_I8160PXXME1_OXA_1106830_REV00_user_low_ship [http://d-h.st/Sux]
Whats NOT needed anymore:
- ROOT is not needed
- ADB is not needed
- no more copy&paste of the ADB commands
Disclaminar:
I'am not responsible if you brick your phone.
Special thanks goes to:
avkiev @ xda (his very nice xls file of 8160/8160P partitions makes things easy to understand)
Szaby59 @ xda (for his findings that IMEI is in partition CSPSA_FS - [HOW-TO] Backup/Restore NV Data (IMEI, Serial number, Baseband...))
Shaaan @ xda (for Temporary CWM Recovery - [JB] CWM Recovery 6)
matthias76 @ android-hilfe (for his hint to changed MAC adress -> solved)
unknown user - he want to stay anonymous (for the links to FULL 3-parted Firmwares)
Also thanks goes out to for thier general help
knipseringo @ xda and android-hilfe
KevinNash @ xda
angrybb @ xda
Here we go:
1.) Move File BACK_TO_THE_I8160P.zip to root of external SD-Card
2.) Install CWM Recovery
- For GB: Flash I8160XXLL2_CWM_5.0.2.6_ANT.tar.md5 from archive with ODIN as PDA (This is the CWM Kernel for GT-I8160)
- For JB: Install CWM_6.0.2.8.zip from Android System Recovery. Move this file before to root of external SD-Card (This is the temporary CWM Recovery for JB)
3.) Go into CWM Recovery
- For GB: Press following keys together (as long as needed): VOL UP + HOME + POWER
- For JB: CWM is available right after you installed it from Android System Recovery (Enter Android System Recovery also with VOL UP + HOME + POWER)
4.) Install from CWM Recovery the file BACK_TO_THE_I8160P.zip and follow the instructions on the display
- This will also save your EFS / MODEMFS / CSPSA partitions to folder BACKI8160P on external SD-Card - Keep those files save.
5.) Flash FULL 3-parted GB or JB Firmware (PIT as PIT / CODE as PDA / CSC as CSC)
- This is also instructed in the script - You do not need it twice of course.
- Set ODIN as mentioned here: [HOW-TO] Go back from JB to GB on GT-I8160P (ACE 2 NFC)
6.) OPTIONAL: Flash any GT-I8160P Firmware of your specific country
That was easy, isn't it?
If you are Happy with this please push Thanks! :highfive: - Or if you just like my "Back to the..." Image LoL
If you cannot post here use former Discussion Thread
http://forum.xda-developers.com/showthread.php?t=2279510
Success Stories
miyagi83 (http://forum.xda-developers.com/showpost.php?p=43297460&postcount=111)
ghostface (http://forum.xda-developers.com/showpost.php?p=43317243&postcount=12)
lasy (http://www.android-hilfe.de/samsung...android-4-1-2-fuers-ace2-199.html#post6047728)
Robin Fischer (http://www.android-hilfe.de/root-cu...-es-zum-i8160-geflasht-wurde.html#post6061538)
infinity4 (http://www.android-hilfe.de/root-cu...-es-zum-i8160-geflasht-wurde.html#post6064240)
Maxwel (http://www.android-hilfe.de/root-cu...s-zum-i8160-geflasht-wurde-2.html#post6064287)
Superarni (http://www.android-hilfe.de/root-cu...s-zum-ace2-geflasht-wurde-2.html?#post6072975)
primewell (http://forum.xda-developers.com/showpost.php?p=43494174&postcount=121)
Shadowcareful (http://forum.xda-developers.com/showpost.php?p=45363432&postcount=22)
Moonly (http://forum.xda-developers.com/showpost.php?p=45367023&postcount=34)
Can this be used to come from JB (the P version) back to GB? It would help a lot of people since many people who had official update through Kies (PHE and XEZ CSC) have only 482 MB of RAM. (I would try it if I wasn't such a *****... but I just got my phone back from service yesterday since it was hardbricked )
This will go over GB RUS FW (this will bring you 550MB) and then (after the other suff) we flash I8160PXXME1_I8160PDBTME1_DBT (you get also 550MB)
If you can use an GB FW of I8160P instead of JB could be possible - Logically it must work - BUT THIS IS NOT TESTED BY ME...
Personally I don't see any reason to go back to GB but I understand your wishes.
I think I'm the best choise to test this (because the RIFF Box is lying around here :good
I will test this with the latest GB 8160P DBT - I8160PXXLK2_I8160PDBTLK2_DBT and let you all know.
AGAIN: Success :victory:
Works also with GB I8160PXXLK2_I8160PDBTLK2_DBT
Be sure that you have Pre-Rooted Version of it or the rooted system_rooted.tar.md5 and csc.tar.md5 available....
I don't know if this will work with the Kernel-Root method - I do not test this.....
So it's also possible to go back to FULL I8160P with GB!
With this way we have an access error to DBT CSC - And Multi CSC will be installed. But this is not a problem!
This leads me to the opinion that this might work with any other original FW of JB or GB of 8160P
Feel free to test this and report please if you used another FW.... Please keep in mind that you need to root it to push CSPSA_FS back....
So in which step should I flash the GB DBT ROM? (step 2 or 9 according to your guide)?
Sent from my GT-I8160P using xda app-developers app
fifo171 said:
So in which step should I flash the GB DBT ROM? (step 2 or 9 according to your guide)?
Click to expand...
Click to collapse
Step 9 (of course)
Please read it again and try to understand what we are doing here...
Main Key is to save the CSPSA_FS from a working IMEI FW.
Then we push the first 70 MB of an 8160P DUMP (to get the 8160P back technically)
This is actually the most "risky" part. But you'll have access to Andriod recovery and Downloadmode anyway. So who cares :angel:
Then we flash the 8160P original FW.
After that we write saved CSPSA_FS back to get IMEI.
The Rest is Rooting, ADB Drivers installing and getting back 550MB (with 3 parted RUS FW)
If you like to have another FW combination (to have 482/550/624MB) feel free to test it.
I posted this HOW-TO for the most recommended way! 550MB with JB in my opinion.
BUT: If you want to stay with your current RAM configuration - and only get back the 8160P - Then you can leave 1 - 3 and start directly with Nr. 4.
It might also work if you save the CSPSA_FS before you do the DUMP and FW flashing (NOT tested). But I decided to write this HOW-TO that everyone has the same initial situation...
Okay, my last question
Lets say I'm on P-version JB and have 482 RAM. I want to have 550. The fact that I have only 482 is caused by the new SBL (normal.bin) from XEZ ME1 JB ROM. (the DBT JB Odin package doesn't contain the normal.bin and because of that it has 550 RAM if you flash it over GB) In order to get 550 I need to flash the GB SBL.(most probably ) Can I just do this?
1. backup CSPSA_FS
2. flash the I8160P_DBT.bin you posted
3. restore my CSPSA_FS
Is there a risk of bricking my phone? (Except typing wrong dd command.)
Sent from my GT-I8160P using xda app-developers app
fifo171 said:
1. backup CSPSA_FS
2. flash the I8160P_DBT.bin you posted
3. restore my CSPSA_FS
Click to expand...
Click to collapse
fifo, fifo, fifo... - If you what to have 550MB and JB why you didn't do it as written in the HOW-TO?
This I8160P_DBT.bin is from an GB Phone! Therefore I think the most secure way is to write this to an GB FW.
And in order to get back 550MB for all the best way was to use the GB RUS FW (3-parted).
I can't say exactly if your way will work. What I can say is that during the whole testings with this 70 MB BUMP (if you flash it completly) I got never got HardBrick...
But what do you what me to say? Your Phone will never be Bricked again? I can NOT promise this! I hope you understand this.
AND: Please do not type the commands! Use Copy&Paste. STRG-C for coping the command from the HOW-TO and right mouse button and insert to paste it to ADB window (I can't belive that I'm writing this here )
One question: After you flash the JB rom do you have valid imei without the 13th step (CSPSA restore) or you have to flash CSPSA to show the correct imei even if with LK6 was ok ?
Thanks for this great guide!
Just one question, whlie I am mounting the SD card, cmd writes that "mount: Device or resource busy", but when I do backup, I´ve got a 3,69GB fullbackup.img there, so what am I doing wrong if something..? Thanks in advance.
P.S.: SU rights are allowed for adb in phone.
Szaby59 said:
One question: After you flash the JB rom do you have valid imei without the 13th step (CSPSA restore) or you have to flash CSPSA to show the correct imei even if with LK6 was ok ?
Click to expand...
Click to collapse
No - After JB flash the IMEI is NOT there. If this would be so then we didn't have this whole trouble :laugh:
Only after CSPSA flash! And CSPSA of GB works on JB!
[EDIT] I konw this is strage because LK6 RUS has also an CSPSA. And the IMEI works after flshing this... Could be that this CSPSA of this LK6 has an emty part in it?! That is one of my next plans to check/compare unflashed CSPSA LK6 with flashed working CSPSA.
But it seams that the step over GB RUS is not needed (some futher tests to go) - Main Key is the to save CSPSA from an working IMEI phone, flash the DUMP of 8160P, flash complete FW and write CSPSA back.
After I did some furthr tests I will adapt the HOW-TO. But up to now this works like I've written it.
ghostface said:
Thanks for this great guide!
Just one question, whlie I am mounting the SD card, cmd writes that "mount: Device or resource busy", but when I do backup, I´ve got a 3,69GB fullbackup.img there, so what am I doing wrong if something..? Thanks in advance.
P.S.: SU rights are allowed for adb in phone.
Click to expand...
Click to collapse
If it say "mount: Device or resource busy" then your SD-Card is already mounted and its OK!
ARH! Its 3,68 GB (3.959.422.976 bytes) - You are right!!!! LOL Will correct HOW-TO! :good:
Thanks again mate, I´ve got a fully working i8160P with IMEI and everything :good:
Hi, pls check "uploaded.net" links... don't work
tnx
ChuckyIT said:
Hi, pls check "uploaded.net" links... don't work
Click to expand...
Click to collapse
Just checked it - works...
If you have local restrictions with uploaded.to please wait until Monday - After I updated the HOW-TO I will move the files to DEV-HOST. This seams to more stress-free for most Users.
fluffi444 said:
Just checked it - works...
If you have local restrictions with uploaded.to please wait until Monday - After I updated the HOW-TO I will move the files to DEV-HOST. This seams to more stress-free for most Users.
Click to expand...
Click to collapse
Worked with google DNS (8.8.8.8 and 8.8.4.4) tomorrow will try all and will let you know!
First Post Updated 2013-07-08
fluffi444 said:
Work in Progess - NO ETA - please don't ask
- GT-I8160P with 624MB RAM (out of I8160XXMF1 FW)
Click to expand...
Click to collapse
I'm not sure how but I managed to get 624MB RAM on my i8160P
I was running XEZ JB ROM with 482MB RAM but wanted to try CM10, so I backed up my ROM in CWM, changed some lines in build.prop (otherwise the CM won't install), went to CWM, full-wiped, formated /system, installed CM10 and GApps. The phone still had 482MB RAM with CM10 but it was fast and smooth. After few days I wanted to go back to stock Samsung ROM, so I went to CWM, restored my backup, booted up the phone and BANG - there was 624MB RAM.
I hope you'll find out why this happened.
BTW I was using this CM10 by dh.harald.
fifo171 said:
I'm not sure how but I managed to get 624MB RAM on my i8160P
I was running XEZ JB ROM with 482MB RAM but wanted to try CM10, so I backed up my ROM in CWM, changed some lines in build.prop (otherwise the CM won't install), went to CWM, full-wiped, formated /system, installed CM10 and GApps. The phone still had 482MB RAM with CM10 but it was fast and smooth. After few days I wanted to go back to stock Samsung ROM, so I went to CWM, restored my backup, booted up the phone and BANG - there was 624MB RAM.
I hope you'll find out why this happened.
BTW I was using this CM10 by dh.harald.
Click to expand...
Click to collapse
Thx for this info! Flashed recently (for testing purposes) the MF1 (from 8160) on my 8160P (as it was an still an 8160).
This gave me also 624MB. Without any repartionering.
Knisperingo had his 8160P at the Samsung Service (as it was HardBricked long time ago). They changed the complete PCB and now he has also 624MB with an 8160P! Never heard that before!
I really don't know what this RAM is all about But lets go back to Topic. There are many other threads which are talking about this never ending story of 482/550/624 RAM...
This for instance: http://forum.xda-developers.com/showthread.php?p=42075864
I'm triing to go back to GB but i have a black screen after the splash screen...
im installing the prerooted version of i8160pxxle6
i'm doing something wrong?? tnx
ChuckyIT said:
I'm triing to go back to GB but i have a black screen after the splash screen...
Click to expand...
Click to collapse
I would try to format system/data and wipe cache...In Recovery Mode... If not already done.
And flash the FW again...
If this did not help you could try to format the partitions with the temporary CWM 6.0.2.8
http://forum.xda-developers.com/showthread.php?t=2141395
Menu MOUNTS AND STORAGE
Format SYSTEM, DATA, CACHE, PRELOAD, EMMC
BUT NOT SDCARD!!!! :angel:
After this your phone will not start anymore properly. But this is normal because of formated partitions
Then flash via ODIN again.....
The next start will take longer than normal....

[FAQ] Frequently Asked Questions For Moto E (2015) [UPDATED-3/7/2015]

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.

Categories

Resources