Okay so I'm new to Android. I have been trying to update to a new rom but have pretty much got stuck at the first hurdle. I have been trying to follow http://forum.xda-developers.com/showthread.php?t=552591
MoDaCo Custom ROM is here (2 versions based on the 'new update')!
As stated in the first thing to do for a newbie is to Download the patched recovery image linked above and install as detailed in that post.
I have not been able to get pasted this stage
Please please please can someone write an idiots guide for this as by the end of tonight I’m going to be bald as I’m pulling my hair out.
robboy said:
Okay so I'm new to Android. I have been trying to update to a new rom but have pretty much got stuck at the first hurdle. I have been trying to follow http://forum.xda-developers.com/showthread.php?t=552591
MoDaCo Custom ROM is here (2 versions based on the 'new update')!
As stated in the first thing to do for a newbie is to Download the patched recovery image linked above and install as detailed in that post.
I have not been able to get pasted this stage
Please please please can someone write an idiots guide for this as by the end of tonight I’m going to be bald as I’m pulling my hair out.
Click to expand...
Click to collapse
1. make a full nandroid backup
2.download the recovery image
3.turn off your phone and turn on by pressing the on button+the back key (to get into bootloader)
4.open a terminal from the folder which contains the recovery image.
5. type 'fastboot boot cm-hero-recovery.img'
6.type 'adb shell mount /sdcard'
7.type 'adb push cm-hero-recovery.img /sdcard/cm-hero-recovery.img'
8.type 'adb shell flash_image recovery /sdcard/cm-hero-recovery.img'
now whenever you want to access the recovery console, you just have to switch your phone on+home key and u'll enter.
To install the rom,
9. download the radio and rom from modaco
10. plug in ur usb and mount sd card
11. copy radio into sd card and rename to update.zip.
12. switch off phone and enter recovery console
13.if you never upgraded the phn , then a wipe is necessary
14. then, select update.zip..
15. u repeat the steps from step9 onwards the same way to update the rom.
hope ie helped.
i mentioned nandroid backup as from step 1 itself.
just came to realise that maybe u have never accessed recovery image from pc.
well dont worry, u can ignore step one but be sure to make the backup after step 8 ..... before installing the new rom
cheers and good luck
Okay so number 4 is my problem. Do o do this from the phone or pc?
robboy said:
Okay so number 4 is my problem. Do o do this from the phone or pc?
Click to expand...
Click to collapse
From the pc. A DOS terminal, if you are on windows.
should I allready have partitioned my sd card before i do this?
This is the error message i get
robboy said:
This is the error message i get
Click to expand...
Click to collapse
As far as I can see, you opened the command-line in the system32 dir from youre PC?! You should open the commandline in the dir where the image-file is. Should look like C:\SDK\tools
See this post to guide you further.
http://forum.xda-developers.com/showpost.php?p=4257045&postcount=38
robboy said:
This is the error message i get
Click to expand...
Click to collapse
To open a terminal( command prompt) from a folder,
1.go to accesories in Windows, copy the command prompt.
2. Go to your folder and paste it there.
3.right click on the command prompt, go on prope
rties.
4. U will find a line containing ' start in : %homedrive%%homepath....'
5. Delete that line so that 'start in' remains blank
6. Apply. And u r good to go
By the way. I supposed u already installed HTC sync right.
okay I thought HTC sync might be causing me problems so i removed it
robboy said:
okay I thought HTC sync might be causing me problems so i removed it
Click to expand...
Click to collapse
You will need to install HTC sync cause it contains the drivers for you phone.
Okay so I have put HTC sync back on. My hero connects to the sync in normal mode as an android USB devices - My HTC . What I'm unsure of now is when I press 'on and back buttons to go into bootloader' should the hero still sync as My HTC or should it be syncing to a different driver. I have been going round in circles all day. I have also removed the android development software as before the hero was syncing as and adb device??
When going to the cdm I now get the error device not found. USB debugging is selected on my device.
I think I’m on the brink of giving up.
okay so now when I'm in the bootloader my device connects as a ADB Interface - HTC Bootloader.
BTW I'm on Vista and i selected the driver that was in x86 folder that I was advised to download. However still no device found
robboy said:
Okay so I have put HTC sync back on. My hero connects to the sync in normal mode as an android USB devices - My HTC . What I'm unsure of now is when I press 'on and back buttons to go into bootloader' should the hero still sync as My HTC or should it be syncing to a different driver. I have been going round in circles all day. I have also removed the android development software as before the hero was syncing as and adb device??
When going to the cdm I now get the error device not found. USB debugging is selected on my device.
I think I’m on the brink of giving up.
Click to expand...
Click to collapse
Yes if your device is recognised as adb ... it's good.
That's how it should be.
Try installing HTC sync before plugging ur phone, then enter bootloader on the phn, plug it in, and then perform the command from the prompt.
P.s try entering bootloader first and only afterwards u plug in ur phone
Try to get the latest driver HTC sync from HTC site. If that doesnt work, try downloading the latest sdk plus drivers. U can find it somewhere on the forum . I think that there is a link on the rooting guide by daysee
I'm a total noob at Android too but theunlockr.com was the easiest and fastest way for me to install the custom Modacco ROM. Check out their site; it'll show you step by step with videos :]
Related
I have a blind N10 on bootloader that is it doesnt show anything on fastboot mode but it does go there. I researched and found other people with similar problem http://rootzwiki.com/topic/37629-bootloader-fastboot-weirdness/ . However they managed to unlock the device by clicking the vol+ once and then power key as I also saw on youtube videos. IT WORKED. and then it went downhill. it got stuck on bootloop. SO i tried to go into fastboot again and it went and then pressed vol+ twice to go into recovery and there was a android with "!" red sign on middle.
and of course it won't boot. So I tried to use the Wugs toolkit, put it on back to stock with bootloop option. and it started to do its work, but got stuck at the sending bootloader (1280KB) sign for more than 10-15 mins. I pressed the power button and it failed that step saying too many links and wugs kit continued the process got stuck again and then completed and my device still goes to fastboot, but cant go into recovery anymore I think as it shows blank screen. Please mind that I am still blind on the screen and nothing comes. my only way of knowing it goes to fastboot is through cmd line. PLEASE HELP, dont wanna brick this.
Is there any way to ODIN it. I cant find online any ODIN insturctions? help help
I cant even turn it off now! Its always going to fastboot. Please help
mustafansu said:
I cant even turn it off now! Its always going to fastboot. Please help
Click to expand...
Click to collapse
I think that's a good thing, if you can get to Fastboot then I would say to forget about the toolkits and just download the latest Google MantaRay image from here https://dl.google.com/dl/android/aosp/mantaray-jwr66y-factory-3d8252dd.tgz
Make sure your Android SDK is updated, unzip the downloaded file once and copy the contents to your Fastboot folder, shift/right click inside your fastboot folder and select "open command window here" then type "fastboot devices" and make sure your device id is shown, after that just type in your cmd window "flash-all.bat" and let it do its magic. If everything goes well by the time it completes you will have a factory restored Nexus10 and then you can start the hacking all over again.
Good Luck! and remember when in doubt, just ask.
Erik
ricco333 said:
I think that's a good thing, if you can get to Fastboot then I would say to forget about the toolkits and just download the latest Google MantaRay image from here https://dl.google.com/dl/android/aosp/mantaray-jwr66y-factory-3d8252dd.tgz
Make sure your Android SDK is updated, unzip the downloaded file once and copy the contents to your Fastboot folder, shift/right click inside your fastboot folder and select "open command window here" then type "fastboot devices" and make sure your device id is shown, after that just type in your cmd window "flash-all.bat" and let it do its magic. If everything goes well by the time it completes you will have a factory restored Nexus10 and then you can start the hacking all over again.
Good Luck! and remember when in doubt, just ask.
Erik
Click to expand...
Click to collapse
Hi ricco333
thanks for the reply. I have updated the SDK and tried to run the command as you mentioned. However it is the same thing. Its getting stuck at sending bootloader. I am attaching a screenshot here. it stays there until i press ctrl+c. then it tries to continue and gets stuck again at sending boot. which is the second screenshot.
Is there any other way to restore factory image. i thought samsung devices had ODIN system. Thanks again for the reply.
Try connecting the Nexus to a different USB port, also try another USB cable, as a last resort I will go as far as using a different PC, based on your screenshots it is being recognized but my guess is that it is having a problem writing the new partitions.
Erik
Also try re downloading the stock images...
Maybe you have a corrupted file.
Have you tried using the Nexus 10 Toolkit?
http://forum.xda-developers.com/showthread.php?t=2001868
IT WORKED!!
ricco333 said:
Try connecting the Nexus to a different USB port, also try another USB cable, as a last resort I will go as far as using a different PC, based on your screenshots it is being recognized but my guess is that it is having a problem writing the new partitions.
Erik
Click to expand...
Click to collapse
Thanks so much guys.After trying 2 different cables and a new computer, a fresh installation of ADB and samsung drivers it finally worked. Thanks again. HUGE SIGH of RELIEF
Hello there
My name is Kareem and I'm using a Sony Xperia U 4.0.4 and build number 6.1.1.B.1.10.
So the thing is that I want to update my phone to 4.4 Kitkat and I'm following this thread.
I rooted my device, and I'm now trying to unlock bootloader. My devices says that I'm able to bootload but I still need to unlock it. So I googled around and came across this video which shows me how to unlock bootloader. First I had problems with installing the drivers because I am using windows 8.1 64-bit, but after I disabled “Driver Signature Enforcement” I managed to install the drivers.
And here the problem starts... I have to press the up volume button while plugging in so I can start fastboot. As what I was told, I did and the blue led on the left side turned on. But when I look on my desktop I get a notification that my usb device is not recognized.
Can anyone tell what causes this issue? Otherwise, is there another and maybe an easier way to unlock bootloader?
Kind regards
Kareem
P.s. I'm using that flashtool software to unlock bootloader. It's called "Sony Mobile Flasher by Androxyde".
I prefer to use this.
Is the official method for unlocking the bootloader, includes the drivers and stuff, just follow that tutorial and you're good to go.
Also you have to make sure that your phone can have unlocked bootloader first, if not, then, you have to stick to locked bootloader ROM's.
Now, sorry for saying like this but Windows 8.1 is such a pain in the a**, it always gives error because the drivers isn't signed, if you get problems with that again use this.
USB not recognized, well the solutions for that problem can be:
Use other USB port, if still doesn't work on any of the ports, then can be the slots or bad placement of pins in the motherboard, almost never is a problem of internal dust in the computer but you can try these.
Try other USB cable, may be the cable is failing, try other from another Android phone to complete the process.
Try using other computer with WIndows 7 or Ubuntu.
If you were not able to get working, then tell me.
Thanks for your reply. Both links are the ones I came across too, I used the first one but not the second one. So I'm trying the 2nd link, but I'm troubling with
browse from disk and select "android_winusb.inf" from "...\android-sdk\extras\google\usb_driver" and select "android bootloader interface.
Click to expand...
Click to collapse
There is no android bootloader interface in my usb_driver folder. Do I need to get it from somewhere like the SDK manager or a website?
Kareem
Kareem_XperiaU said:
Thanks for your reply. Both links are the ones I came across too, I used the first one but not the second one. So I'm trying the 2nd link, but I'm troubling with There is no android bootloader interface in my usb_driver folder. Do I need to get it from somewhere like the SDK manager or a website?
Kareem
Click to expand...
Click to collapse
Windows key + R, write devmgmt.msc, enter.
Plug your phone and look if some device is recognized in the list, it may appear as Android or something like that, if you got it, then follow me.
Right click to it, Update driver, select from computer, use a list from the PC, and "Use disk", see if there's something that says like that because I got Windows 7 in spanish so it's different.
In that browse for the folder that has the .inf file and open it, it returns a list that you have to select the interface, next and your driver may be installed.
Understand? I can explain more but I have Windows in spanish so I don't know how is in english.
Okay.
So I got to Device Manager and when I plug my phone when going in fastboot mode it first appeared as Android but then later on it appeared as Other Device(s) and after a split seconds it goes away. That's because the fastboot doesn't last long since fastbood isn't unlocked yet (and yest bootunlocker:yes is stated on my phone when dialing a code).
Secondly to your explanation. So when I still try to update the driver I can choose to let windows find a driver a use my own software to update it. So I clicked on use my own software, chose the path where the usb_driver is located. But only the folders appear, I can't see the ini or inf. files.
Edit: I'm actually going to downgrade back to windows 7. Since I went to 8.1 it gave a lot of troubles like unsupported screen resolutions and this.
Update: I managed to borrow my sister's laptop for one time, her laptop contains windows 7. So I got on her laptop and took my usb with flash-tool on it and a kernel. I connected my phone with cable while holding the buttons to get in fastboot mode, voila it got recognized by flashtool. I'm one step closer to unlocking bootloader with only one trouble a head. So when I try to unlock my bootloader with a kernel I get an error that my phone needs to be rooted first. The thing is that my phone has been rooted already, plus I just test if it is rooted and the test said that it's rooted. What can be the problem? Not having the right kernel? Not having pc companion on that pc?
Kareem_XperiaU said:
Okay.
So I got to Device Manager and when I plug my phone when going in fastboot mode it first appeared as Android but then later on it appeared as Other Device(s) and after a split seconds it goes away. That's because the fastboot doesn't last long since fastbood isn't unlocked yet (and yest bootunlocker:yes is stated on my phone when dialing a code).
Secondly to your explanation. So when I still try to update the driver I can choose to let windows find a driver a use my own software to update it. So I clicked on use my own software, chose the path where the usb_driver is located. But only the folders appear, I can't see the ini or inf. files.
Edit: I'm actually going to downgrade back to windows 7. Since I went to 8.1 it gave a lot of troubles like unsupported screen resolutions and this.
Update: I managed to borrow my sister's laptop for one time, her laptop contains windows 7. So I got on her laptop and took my usb with flash-tool on it and a kernel. I connected my phone with cable while holding the buttons to get in fastboot mode, voila it got recognized by flashtool. I'm one step closer to unlocking bootloader with only one trouble a head. So when I try to unlock my bootloader with a kernel I get an error that my phone needs to be rooted first. The thing is that my phone has been rooted already, plus I just test if it is rooted and the test said that it's rooted. What can be the problem? Not having the right kernel? Not having pc companion on that pc?
Click to expand...
Click to collapse
Tried to unlock the bootloader with the Sony method?
manudo said:
Tried to unlock the bootloader with the Sony method?
Click to expand...
Click to collapse
Okay I'm going to try it right now, at least I want to but there are some steps very confusing for me.
Sony website said:
9. Download and unzip this file. This is the standard android_winusb.inf-file, with a few lines of code added to enable Fastboot to support Sony and Sony Ericsson devices. Make sure you are running Google USB Driver package revision 4 or higher in your Android SDK. You can see current Google USB Driver package revision in the SDK Manager.
10. Place the unzipped file in the usb_driver folder, located in the Android SDK > extras > google folder on your computer. Accept to replace the old android_winusb.inf-file with the new file. If you can't find the usb_driver folder, please install the Google USB Driver Packager using the Android SDK manager.
11. Turn off your device.
12. On your device, push and hold the Fastboot button at the same time as you connect the device to the computer with a USB-cable. The Fastboot button may differ between different device models. See the Fastboot buttons page for more information on what button use on your device.
13. On your computer, you will be asked for drivers. Point to the usb_driver folder where you placed the android_winusb.inf-file, and select the Android Boot loader Interface-file.
14. Open a command window and go to the tools folder within the Android SDK folder.
15. Enter fastboot.exe -i 0x0fce getvar version, and verify that you get a response back (for example "0.3"). This means your device is connected properly.
Click to expand...
Click to collapse
13. Well when I connect my phone in fastboot mode it doesn't ask for driver installation, it happens automatic i guess. No problem, right?
14. Do I have to do it like the screenshot?
i1362.photobucket. com/albums/r682/klaskareem/Untitled_zps296a1291.jpg (website protocol needs to be placed in front + remove space between . &com
Kind regards
Kareem_XperiaU said:
Okay I'm going to try it right now, at least I want to but there are some steps very confusing for me.
13. Well when I connect my phone in fastboot mode it doesn't ask for driver installation, it happens automatic i guess. No problem, right?
14. Do I have to do it like the screenshot?
i1362.photobucket. com/albums/r682/klaskareem/Untitled_zps296a1291.jpg (website protocol needs to be placed in front + remove space between . &com
Kind regards
Click to expand...
Click to collapse
13. If your phone is recognized in fastboot mode then continue, if not, update the driver.
14. Know the command "cd"? Is for accesing directories, you can use "dir" to see whats in the folder. Example, you downloaded the Android SDK bundle in the Desktop, then "cd" to the "tools" directory, that contains the binary to unlock the bootloader. That's in cmd.
Like:
Code:
cd /SDK/adt-bundle-blah-blah/sdk/tools
And, you're using Windows 8, again, your device is recognized in fastboot mode?
Thank you for the clear explanation, makes sense now ( already knew that cd thing, wasn't sure though).
Uhm don't mind me using windows 8 atm. I'm downloading 32-bit sdk so I can use it on my sisters laptop.
Kareem_XperiaU said:
Thank you for the clear explanation, makes sense now ( already knew that cd thing, wasn't sure though).
Uhm don't mind me using windows 8 atm. I'm downloading 32-bit sdk so I can use it on my sisters laptop.
Click to expand...
Click to collapse
Right, if anything goes wrong, feel free to ask!
By the way. Do I need to make a copy my ROM I already have? Like when something goes wrong I can still go back to my original android 4.0.4
Kareem_XperiaU said:
By the way. Do I need to make a copy my ROM I already have? Like when something goes wrong I can still go back to my original android 4.0.4
Click to expand...
Click to collapse
It's recommended to keep the stock ROM or any other ROM if anything goes wrong.
Sent from my Xperia Sola using XDA Premium 4 mobile app
manudo said:
It's recommended to keep the stock ROM or any other ROM if anything goes wrong.
Sent from my Xperia Sola using XDA Premium 4 mobile app
Click to expand...
Click to collapse
And how can I do that to be honest?
Kareem_XperiaU said:
And how can I do that to be honest?
Click to expand...
Click to collapse
In this post, there are a list with all stock and custom ROM's available in XDA forum, you should download stock and if anything goes wrong then flash the stock ROM with flashtool. You know, flashmode, select kernel, connect to green led, let it boot, and you have stock.
By now, try to unlock the bootloader, if you need help with the flashing then you can ask by here or create another thread.
`Dear Admin,
Hi my Name is Zaki.... i am using HTC Rezound which i purchased in U.A.E
After installing whatsapp i got continious restart problem so i downloaded stock firmware of ICS version. all was good but by mistake i clear internal storage in fastboot mode. and after that i am unable to get into TWRP Recovery mode, it is showing phone with with arrow circle and after few second it converted into phone with triangle (attached screens 2 and 3) please explain me with links how to get TWRP again. and the links for TWRP versions i am not sure which is ok.
Please Reply.
syedzakiabidi said:
`Dear Admin,
Hi my Name is Zaki.... i am using HTC Rezound which i purchased in U.A.E
After installing whatsapp i got continious restart problem so i downloaded stock firmware of ICS version. all was good but by mistake i clear internal storage in fastboot mode. and after that i am unable to get into TWRP Recovery mode, it is showing phone with with arrow circle and after few second it converted into phone with triangle (attached screens 2 and 3) please explain me with links how to get TWRP again. and the links for TWRP versions i am not sure which is ok.
Please Reply.
Click to expand...
Click to collapse
You can't access TWRP because you over-wrote it with the factory RUU firmware image, it isn't there anymore...
Download TWRP image from TWRP official site at https://dl.twrp.me/vigor/ or Flyhalf's build at http://forum.xda-developers.com/showthread.php?t=1902381
Either one is good... then start fastboot, connect usb and flash recovery with the command:
fastboot flash recovery <path/filename of TWRP IMG file>
give it a minute or so, reboot into Hboot and start TWRP.
im having a similar issue but my computer always says waiting for device in command prompt. I have all the drivers installed and the phone says "usb fastboot" or "fastboot usb" (cant recall what order those 2 words are in LoL)
youdoofus said:
im having a similar issue but my computer always says waiting for device in command prompt. I have all the drivers installed and the phone says "usb fastboot" or "fastboot usb" (cant recall what order those 2 words are in LoL)
Click to expand...
Click to collapse
You probably have a driver issue then... Install HTC Sync, connect the phone, then disconnect it, remove HTC Sync and it should work. If that doesn't work, try a different USB port.
Honestly, I switched to Linux a long time ago... I don't have driver issues. If you were running Linux, even a live or USB key distro, you would access it easily.
acejavelin said:
You probably have a driver issue then... Install HTC Sync, connect the phone, then disconnect it, remove HTC Sync and it should work. If that doesn't work, try a different USB port.
Honestly, I switched to Linux a long time ago... I don't have driver issues. If you were running Linux, even a live or USB key distro, you would access it easily.
Click to expand...
Click to collapse
fair point, and i do have ubuntu (of differing flavor dates) on 3 of my machines, so i might just do that. Thanks!! Ill also try the goofy htcsynch (which i forgot about, as im a Sammy guy now) Thanks again!!
Edit: I'm running Windows 8.1 and that is probably the problem. I need find some universal drivers that work for win8.1 with the moto e.
Hi,
I decided to try to root a recently acquired Moto E (XT1526/5.1) and got it unlocked easily enough by following directions online. I have downloaded the motorola usb drivers, TWRP, Android SDK, SuperSU, and tried different versions.
After following the unlock guide, it says DEVICE IS UNLOCKED. STATUS: CODE 3
I open the command prompt in platform-tools and enter fastboot flash recovery recovery.img (file was renamed), and it shows it's sending recovery OK, writing recovery OK, and finished.
After that things don't progress, and there are options that I can scroll through:
Restart Bootloader...
Power off...
Factory Mode - resets it to fac settings I think
Bar Codes...
BP Tools?
QCOM?
Bootloader Logs...
Start - does the warning that it's unlocked and then starts the phone.
Reocvery Mode - flashes the unlocked warning and nothing else. It goes back to fastboot flash screen.
Guides show it going to TWRP screen after running the command prompt, and then options to load up files.
Am I missing something?
TIA
Download mfastboot and redownload the recovery img
hetor99 said:
Download mfastboot and redownload the recovery img
Click to expand...
Click to collapse
Thanks.
Decided to install it on my desktop. While trying various files, my laptop accidentally got hit with Chromium virus. It looked like all required files were there, but kept having problems with a couple of those sdk files (tools/platform tools).
I'm still getting the following error:
( bootloader) has-slot :recovery: not found
And once again the Android SDK Tools and Android SKD Platform-tools that are under Tools (preview channel) are unchecked. Not sure if they are needed.
Follow the instructions of how to install on the general section
hetor99 said:
Follow the instructions of how to install on the general section
Click to expand...
Click to collapse
thanks lol.
I believe I have downloaded and installed/reinstalled everything 2 or 3 times. I have followed the guide here while reading and watching the video. I googled for other guides to fill in any information I didn't understand or see clearly. That was before I made this thread. I was hoping there might be something that is commonly overlooked. Phone seems to be ready, so I am assuming it's on the pc side. I read there is a way to do it with just the phone, but I'll try one more time on my laptop since that's what I have to work on today.
L8Show said:
thanks lol.
I believe I have downloaded and installed/reinstalled everything 2 or 3 times. I have followed the guide here while reading and watching the video. I googled for other guides to fill in any information I didn't understand or see clearly. That was before I made this thread. I was hoping there might be something that is commonly overlooked. Phone seems to be ready, so I am assuming it's on the pc side. I read there is a way to do it with just the phone, but I'll try one more time on my laptop since that's what I have to work on today.
Click to expand...
Click to collapse
How to Install TWRP Recovery and Root MOTO E
https://www.youtube.com/watch?v=9Jh-O2LGL3Y
OK, it is done.
Took a couple days with several hours of clicking, and checking settings, and reading and researching, and watching videos, and downloading, and installing/uninstalling, and restarting, but it's now rooted! Way too much time wasted even though it was raining and the gf and I were just watching movies for a lot of it. She kept asking me why I'd waste so much time and remind me I had a perfectly fine iphone nearby. Today I finally got to the point where I had given up. I figured something was screwed up with the phone after that reset on my computer.
Some highlights that may or may not be helpful for the next moto e rooter:
USB debugging was somehow switched to off a few times after I turned it on. Might have been after resetting phone, but who knows exactly.
I set screen to stay while connected via USB.
I removed all the apps I could and took out the sd card.
Kingoroot stuck at 66% many, many times, and then phone would restart. Research showed it may be accessing the wrong ADB instance or something. So I uninstalled SDK, fastboot, Minimal, etc. Anywhere it could have been hiding. Even did a system restore to last week the day I reinstalled windows. Didn't help one bit. Which is to also say... there are a half dozen or more legit options. Try different ones if you are relatively confident you followed directions the 1st 10 times.
Ministro didn't have moto e in their data base.
Finally back to XDA after checking a dozen videos (I have to admit I was completely dumbfounded and was mad at the whole process). I found XDA Kingroot and right away it worked, but it needed permission to allow apps that were not certified or some thing. I can see how people would think this is so easy. If I had started with this, I'd never have had to ask for help here. Btw, was this my problem all along? Did I miss that in the instructions or was it something else possibly? I don't remember if I did that before since it was 3 days ago.
So far I am thoroughly impressed with the this moto e. I paid $40 for it on a whim and now that I can remove a bunch of bloatware and customize it a bit, I think it may be a good gateway into android devices.
Thanks for looking and all your suggestions.
I've been in the same boat for weeks, thank you. I thought I had already tried KingRoot, but must have not, as it's working now and I have root and twrp installed, http://www.kingroot.net/ . Thanks again !
XT-1526 Sprint Prepaid Moto E 2nd gen.
faheyd said:
I've been in the same boat for weeks, thank you. I thought I had already tried KingRoot, but must have not, as it's working now and I have root and twrp installed, http://www.kingroot.net/ . Thanks again !
XT-1526 Sprint Prepaid Moto E 2nd gen.
Click to expand...
Click to collapse
Glad it helped.
So I decided that I try and get TWRP to run on this phone. After researching, I followed a guide using stock firmware and a modified batch file. Phone is working, but wifi/4G/data isn't. I did all the basic trouble shooting and nothing works so I decided to just try install TWRP/supersu. The problem is that ADB isn't working again. It works when phone is on and shows up in adb devices, but not boot mode. Fastboot shows the device. But ADB doesn't show the device while in boot mode and it's not working.
I updated the drivers in the device manager.
I tried minimal fastboot and 15 second adb.
Reinstalled motorola drivers.
Anyone have any ideas?
Thx!
L8Show said:
Glad it helped.
So I decided that I try and get TWRP to run on this phone. After researching, I followed a guide using stock firmware and a modified batch file. Phone is working, but wifi/4G/data isn't. I did all the basic trouble shooting and nothing works so I decided to just try install TWRP/supersu. The problem is that ADB isn't working again. It works when phone is on and shows up in adb devices, but not boot mode. Fastboot shows the device. But ADB doesn't show the device while in boot mode and it's not working.
I updated the drivers in the device manager.
I tried minimal fastboot and 15 second adb.
Reinstalled motorola drivers.
Anyone have any ideas?
Thx!
Click to expand...
Click to collapse
First of all adb doesn't work in fastboot mode. It only works when the phone is up and running.
Try
fastboot devices
If it shows up your device's serial no. then you're good to go, everything's working fine.
I didn't got what's you're exact problem is. Pardon me
Will you explain what you did before your wifi stopped working.
-z3r0- said:
First of all adb doesn't work in fastboot mode. It only works when the phone is up and running.
Try
fastboot devices
If it shows up your device's serial no. then you're good to go, everything's working fine.
I didn't got what's you're exact problem is. Pardon me
Will you explain what you did before your wifi stopped working.
Click to expand...
Click to collapse
Thanks for that information. I thought I saw adb devices command working in fastboot mode in one of the videos so I thought that was the problem. I thought adb needed to root the phone.
In order of what I've done with the phone so far:
Sent/got codes and unlocked moto e.
Turned on developer options and USB debugging.
Was then unable to get TWRP or the other cw something to work using the command fastboot flash recovery (file name) or fastboot boot... commands.
Gave up and installed Kingroot and everything worked fine.
Decided to try to install TWRP and superSU since kingroot had worked. I read that the phone needed to be flashed back to stock to do this and watched/read a couple of guides. http://forum.xda-developers.com/showthread.php?t=2759495
I used the following named file:
SURNIA_ACG_LTE_5.1_LPI23.29-30_cid9_subsidy-DEFAULT_CFC
The phone was changed back, but data doesn't work. I can't access wifi because as soon as I switch it on, it switches back off. 4G, etc is not working either. So after trying to figure that out I decided to just proceed and put TWRP/superSU on the phone.
I powered off the phone. Powered into fastboot mode connected the phone to my computer.
I opened Minimal fastboot folder and shift/right click to bring up the command prompt.
In the command promt i typed fastboot devices and it shows my phone.
I then type fastboot flash recovery (file name or renamed to recovery or renamed to TWRP or I click the actual file and drag it to the command prompt) and then hit enter.
It says it's doing stuff in so many seconds, but after nothing happens. The phone doesn't reset like some of the videos. If I reset it, it powers on, but not into the TWRP screen.
After that I did more reading and found out that adb doesn't always play nice with windows 8.1 and that you might need to force other drivers to make it work right. I did this next and was going to try all the available options from universal naked driver later, but there were no motorola drivers.
Then I came here and learned something new. ADB devices command doesn't work when the phone is in fastboot mode so that has no effect on installing twrp...
Right now I am considering trying to install the other stock files I have access to:
SURNIA_ACG_LTE_5.1_LPI23.29-20_cid9_subsidy-DEFAULT_CFC (20 instead of 30).
After that I am out of ideas if it's not the adb problem. Might kingroot again and go from there.
Ok after researching, it seems that LTE file may not work on sprint and there was success using the boost file from
http://www.filefactory.com/file/6be...XI22.50-14.8_cid9_subsidy-DEFAULT_CFC.xml.zip
(2 hour dl make that 5+ lol)
http://forum.xda-developers.com/moto-e-2015/help/sprint-backup-moto-e-2nd-xt1526-cdma-t3099670
I'll try that next to get the wifi working and then figure out why it won't root.
Thx!
L8Show said:
Edit: I'm running Windows 8.1 and that is probably the problem. I need find some universal drivers that work for win8.1 with the moto e.
Hi,
I decided to try to root a recently acquired Moto E (XT1526/5.1) and got it unlocked easily enough by following directions online. I have downloaded the motorola usb drivers, TWRP, Android SDK, SuperSU, and tried different versions.
After following the unlock guide, it says DEVICE IS UNLOCKED. STATUS: CODE 3
I open the command prompt in platform-tools and enter fastboot flash recovery recovery.img (file was renamed), and it shows it's sending recovery OK, writing recovery OK, and finished.
After that things don't progress, and there are options that I can scroll through:
Restart Bootloader...
Power off...
Factory Mode - resets it to fac settings I think
Bar Codes...
BP Tools?
QCOM?
Bootloader Logs...
Start - does the warning that it's unlocked and then starts the phone.
Reocvery Mode - flashes the unlocked warning and nothing else. It goes back to fastboot flash screen.
Guides show it going to TWRP screen after running the command prompt, and then options to load up files.
Am I missing something?
TIA
Click to expand...
Click to collapse
Copy the twrp file in the sdk root file(right click the desktop icon and open file loaction ) and rename it as recovery
next step on that folder press shift button and right click and choose option open command window here. and type follwiong command without quotes and press enter "fastboot flash recovery recovery.img" this will flash the twrp onto ur moto e
---------- Post added at 05:30 AM ---------- Previous post was at 05:29 AM ----------
rakeshwipr said:
Copy the twrp file in the sdk root file(right click the desktop icon and open file loaction ) and rename it as recovery
next step on that folder press shift button and right click and choose option open command window here. and type follwiong command without quotes and press enter "fastboot flash recovery recovery.img" this will flash the twrp onto ur moto e
Click to expand...
Click to collapse
and open the command prompt with admin rights
Okay dude first of all get rid of those videos (no offense to youtubers).
Check if your device shows up in adb devices. (When phone is on)
Check if your device shows up in fastboot devices (When phone is in fastboot mode)
If both of them shows positive then your setup is fine. Now move on to next part.
Get the right stock image for your device.
Go to your about phone in settings and match with your build/build number. (or give me a screenshot of your about phone and I'll find it for you)
Avoid using any kind of batch file(If you don't know what's there inside) and try to flash manually one by one.
After that flash your twrp recovery.
When this is completed use volume buttons on your phone to get to "Recovery" options in fastboot mode then press power button to boot into recovery.
You'll successfully boot into recovery then from there flash SuperSU. Avoid using kingroot.
The reason your wifi/data stopped working is because of the wrong boot.img(kernel). Since you've flashed the boot.img of same phone but different variant, you were able to turn on your phone. If it had any wrong boot.img your phone wouldn't have turned on anyway.
-z3r0- said:
Okay dude first of all get rid of those videos (no offense to youtubers).
Check if your device shows up in adb devices. (When phone is on)
Check if your device shows up in fastboot devices (When phone is in fastboot mode)
If both of them shows positive then your setup is fine. Now move on to next part.
Get the right stock image for your device.
Go to your about phone in settings and match with your build/build number. (or give me a screenshot of your about phone and I'll find it for you)
Avoid using any kind of batch file(If you don't know what's there inside) and try to flash manually one by one.
After that flash your twrp recovery.
When this is completed use volume buttons on your phone to get to "Recovery" options in fastboot mode then press power button to boot into recovery.
You'll successfully boot into recovery then from there flash SuperSU. Avoid using kingroot.
The reason your wifi/data stopped working is because of the wrong boot.img(kernel). Since you've flashed the boot.img of same phone but different variant, you were able to turn on your phone. If it had any wrong boot.img your phone wouldn't have turned on anyway.
Click to expand...
Click to collapse
d
Thanks! The devices shows up when on as ADB and in fastboot too. I had to take a break when the kernel download took 8 hours, but I think I got the file that will work to fix the wifi issue. I can't mess with it til I get home tomorrow, but I will read and follow all advice.
For the previous poster, I did do the admin rights and did rename TWRP file to recovery... I aslo tried many other combinations, but will keep it in mind for all further attempts.
Appreciate the help so far. I almost left it with the kingroot, but it was bugging me that I couldn't get it to go. Hopefully I'll have good new tomorrow.
-z3r0- said:
Okay dude first of all get rid of those videos (no offense to youtubers).
Check if your device shows up in adb devices. (When phone is on)
Check if your device shows up in fastboot devices (When phone is in fastboot mode)
If both of them shows positive then your setup is fine. Now move on to next part.
Get the right stock image for your device.
Go to your about phone in settings and match with your build/build number. (or give me a screenshot of your about phone and I'll find it for you)
Avoid using any kind of batch file(If you don't know what's there inside) and try to flash manually one by one.
After that flash your twrp recovery.
When this is completed use volume buttons on your phone to get to "Recovery" options in fastboot mode then press power button to boot into recovery.
You'll successfully boot into recovery then from there flash SuperSU. Avoid using kingroot.
The reason your wifi/data stopped working is because of the wrong boot.img(kernel). Since you've flashed the boot.img of same phone but different variant, you were able to turn on your phone. If it had any wrong boot.img your phone wouldn't have turned on anyway.
Click to expand...
Click to collapse
Device shows up in both instances.
It's stock now and the wifi works. Flashed it back to stock by following Mdkcheatz guide here:
http://forum.xda-developers.com/moto-e-2015/help/sprint-backup-moto-e-2nd-xt1526-cdma-t3099670
I'm stuck where I was when I first started this thread. I've set my account up as administrator. Developer is enabled and so is USB debugging. I downloaded 2 different TWRP Condor files (3.0 and 2.7). I tried both and renamed them recovery just in case.
I confirmed the connection:
fastboot devices
I try to flash it with the:
fastboot flash recovery recovery.img
It says:
target reported max download size of 268435456 bytes
sending 'recovery' (6928 KB)...
OKAY [ 0.359s]
writing 'recovery'...
OKAY [ 0.359s]
finished total time: 0.578s
C: |Program Files (x86)\Minial ADB and Fastboot>
I'm running windows 8.1 (64 bit). I read that some people had had problems with windows 8. Kingroot worked through the app store. It has been flashed with various stock kernels and that usually takes a few minutes so I don't think it's doing much in half a second. I'll research a bit more, but I think it just a bad combination of this version phone and windows 8.1.
I started the phone after this last attempt. Are there any files in internal storage that I should look for?
L8Show said:
I downloaded 2 different TWRP Condor files (3.0 and 2.7). I tried both and renamed them recovery just in case.
Click to expand...
Click to collapse
Flashed the wrong recovery dude. You're flashing twrp of condor.
Here's this might work for you : http://forum.xda-developers.com/devdb/project/?id=10398#downloads
After done flashing. Open recovery mode and flash SuperSU.
Also I don't think there's any problem with windows 8.1
As long as you're opening cmd with admin rights and adb/fastboot commands are working for you everything's fine.
-z3r0- said:
Flashed the wrong recovery dude. You're flashing twrp of condor.
Here's this might work for you : http://forum.xda-developers.com/devdb/project/?id=10398#downloads
After done flashing. Open recovery mode and flash SuperSU.
Also I don't think there's any problem with windows 8.1
As long as you're opening cmd with admin rights and adb/fastboot commands are working for you everything's fine.
Click to expand...
Click to collapse
Just in time for Easter! You are correct. TYVM! I'm in TWRP and have to see about read only option again (read about it a week ago, I think it said to leave initially). SuperSU is next and then off to the races.
L8Show said:
Just in time for Easter! You are correct. TYVM! I'm in TWRP and have to see about read only option again (read about it a week ago, I think it said to leave initially). SuperSU is next and then off to the races.
Click to expand...
Click to collapse
Be sure to flash the latest SuperSU (the systemless one).
Here's the direct link:
http://download.chainfire.eu/supersu
-z3r0- said:
Be sure to flash the latest SuperSU (the systemless one).
Here's the direct link:
http://download.chainfire.eu/supersu
Click to expand...
Click to collapse
I am on v2.65. Should I use this version? I checked root and it's rooted, but I needed to use no bloat app (instead of free titanium) to remove some apps. Is that normal? I thought once rooted and set up, I would have complete control. Some apps seem very invasive so I haven't grabbed many yet. I have some questions about apps, etc., but will probably research and ask in another forum if needed.
Thx again for all the help and pointing out my mistake.
When I try to uppgrade with cm12.1 and others, I always
get "signature can't veryfy....", and then reboots.
What iis wrong? I'm new at this so I need some
guide please.
vespa70 said:
When I try to uppgrade with cm12.1 and others, I always
get "signature can't veryfy....", and then reboots.
What iis wrong? I'm new at this so I need some
guide please.
Click to expand...
Click to collapse
Welcome to the Android comuntiy!
I will try to guide you step by step on how to get your phone rocking cyanogenmod 11 (cm11 is kitkat but it is the same procedure for any other ROM, just replace the cm11 file cm12)
What you'll need;
The CyanogenMod ROM
A custom recovery, otherwise you'll get the signiture verification error
ROOT!
Adb and fastboot
adb drivers
Google Apps
-------------------------
We are going to use The custom recovery I provided in this post and not the one provided in the description of the video. The steps below is assuming that you have succesfully rooted your device and have enabled usb debugging and authorized your pc.
-------------------------
1. Connect your phone to your pc, wait for the drivers to install and once they have installed continue on.
2. Click start and open devices and printers, you should see your device, right-click it and hit properties and then you should see different "devices", choose the one who has a type from SAMSUNG and then up next to the corners you should see 2 options, general and one more, hit the second one and hit properties at the bottom right.
3. It should open a new window, in that window there is and option to change setting, click it then select drivers at the top and hit update.
4. Click choose an update already availible on the computer, then click let me pick and wait.
5. Then there is an option to choose compatible drivers or something like that and make sure it is not ticked! Find a driver from ClockworkMod and to the right you should see android adb interface, click it and hit install after that is complete you should have the adb drivers.
6. Open minimal adb and fastboot that you downloaded and type "adb devices" and wait, it should show your device and you might get a popup window on your phone saying to authorize the pc, hit always trust and hit allow and your device should be seen in adb and it should say device next to the serial number.
7 Turn off your phone.
8. Boot into recovery by pressing power + volume up + home button.
9. Click advanced
10. Click adb sideload and make sure that when you type adb devices in minimal adb and fastboot you should see your device and it should say sideload next to the serial number. If you don't, repeat the steps for installing the drivers just this time do it in adb sideload mode.
11. Once you got the driver working in adb sideload you should press the home button and click wipe, then select advanced wipe and select, dalvik, system, data, internal storage, cache and preload. This will wipe your data!
12. Once that is done go to adb sideload and connect your phone to the pc.
13. Move the downloaded ROM to the minimal adb and fastboot folder adn then in the command line type adb sideload <filename>. DON'T REBOOT!!!
14. Once flash is done it is time to move the google apps to the minimal adb and fastboot, remember, DON'T REBOOT!!
15. Type adb sideload <googelappsfilename>. Wait till it is done and now you can finally reboot.
--------------------
It should boot perfectly, remember, the first time boot might take a lot of time and the device might overheat but just leave it there for a couple of mnutes until it boots.
All credits to the cyangenmod development team and that guy from youtube!
If I helped you, hit thanks!
If you encounter any problems (ROM Not booting or device won't show up in adb), please post them here!
RAZERZDAHACKER said:
Welcome to the Android comuntiy!
I will try to guide you step by step on how to get your phone rocking cyanogenmod 11 (cm11 is kitkat but it is the same procedure for any other ROM, just replace the cm11 file cm12)
What you'll need;
The CyanogenMod ROM
A custom recovery, otherwise you'll get the signiture verification error
ROOT!
Adb and fastboot
adb drivers
Google Apps
-------------------------
We are going to use The custom recovery I provided in this post and not the one provided in the description of the video. The steps below is assuming that you have succesfully rooted your device and have enabled usb debugging and authorized your pc.
-------------------------
1. Connect your phone to your pc, wait for the drivers to install and once they have installed continue on.
2. Click start and open devices and printers, you should see your device, right-click it and hit properties and then you should see different "devices", choose the one who has a type from SAMSUNG and then up next to the corners you should see 2 options, general and one more, hit the second one and hit properties at the bottom right.
3. It should open a new window, in that window there is and option to change setting, click it then select drivers at the top and hit update.
4. Click choose an update already availible on the computer, then click let me pick and wait.
5. Then there is an option to choose compatible drivers or something like that and make sure it is not ticked! Find a driver from ClockworkMod and to the right you should see android adb interface, click it and hit install after that is complete you should have the adb drivers.
6. Open minimal adb and fastboot that you downloaded and type "adb devices" and wait, it should show your device and you might get a popup window on your phone saying to authorize the pc, hit always trust and hit allow and your device should be seen in adb and it should say device next to the serial number.
7 Turn off your phone.
8. Boot into recovery by pressing power + volume up + home button.
9. Click advanced
10. Click adb sideload and make sure that when you type adb devices in minimal adb and fastboot you should see your device and it should say sideload next to the serial number. If you don't, repeat the steps for installing the drivers just this time do it in adb sideload mode.
11. Once you got the driver working in adb sideload you should press the home button and click wipe, then select advanced wipe and select, dalvik, system, data, internal storage, cache and preload. This will wipe your data!
12. Once that is done go to adb sideload and connect your phone to the pc.
13. Move the downloaded ROM to the minimal adb and fastboot folder adn then in the command line type adb sideload <filename>. DON'T REBOOT!!!
14. Once flash is done it is time to move the google apps to the minimal adb and fastboot, remember, DON'T REBOOT!!
15. Type adb sideload <googelappsfilename>. Wait till it is done and now you can finally reboot.
--------------------
It should boot perfectly, remember, the first time boot might take a lot of time and the device might overheat but just leave it there for a couple of mnutes until it boots.
All credits to the cyangenmod development team and that guy from youtube!
If I helped you, hit thanks!
If you encounter any problems (ROM Not booting or device won't show up in adb), please post them here!
Click to expand...
Click to collapse
Hello! Thank's for your help! But I'm stuck at item nbr 9. There is no "advanced" .
Right now I can't go anny further.
vespa70 said:
Hello! Thank's for your help! But I'm stuck at item nbr 9. There is no "advanced" .
Right now I can't go anny further.
Click to expand...
Click to collapse
I wrote that we are not going to use the recovery the guy in the video used, replace it with the recovery I provided, remember to read the whole post.
RAZERZDAHACKER said:
I wrote that we are not going to use the recovery the guy in the video used, replace it with the recovery I provided, remember to read the whole post.
Click to expand...
Click to collapse
Hi! Shall I first install "TWRP...md5" with Odin?
The phone is rooted, I used Kingroot.
Item 5, can't find "ClockworkMod".
vespa70 said:
Hi! Shall I first install "TWRP...md5" with Odin?
The phone is rooted, I used Kingroot.
Item 5, can't find "ClockworkMod".
Click to expand...
Click to collapse
Yea, twrp and you should see the clockworkmod in the list, make sure the box is not ticked if you downloaded and installed the .exe driver file that I provided.
RAZERZDAHACKER said:
Yea, twrp and you should see the clockworkmod in the list, make sure the box is not ticked if you downloaded and installed the .exe driver file that I provided.
Click to expand...
Click to collapse
yes, ther is 5 in the list and i looked at all of them.
There is a lot of manufacturers but not Clockwork.
vespa70 said:
yes, ther is 5 in the list and i looked at all of them.
There is a lot of manufacturers but not Clockwork.
Click to expand...
Click to collapse
If you have an sdcard you can put the files on there and flash via sdcard.
RAZERZDAHACKER said:
If you have an sdcard you can put the files on there and flash via sdcard.
Click to expand...
Click to collapse
Yes I have a sdcard. If I copy all the files from you to
the card, how do I procid from there?
The cam is rooted so how do I go on?
vespa70 said:
Yes I have a sdcard. If I copy all the files from you to
the card, how do I procid from there?
The cam is rooted so how do I go on?
Click to expand...
Click to collapse
Put the cyanogenmod rom on the sdcard and the google apps. Assuming you have the recovery I provided here boot into it. Hit install then select storage then select your sdcard. Make sure the files are there and exit out and wipe as I said in the instructions. Make sure not to wipe the micro sdcard. Then install the rom then the google apps.
RAZERZDAHACKER said:
Put the cyanogenmod rom on the sdcard and the google apps. Assuming you have the recovery I provided here boot into it. Hit install then select storage then select your sdcard. Make sure the files are there and exit out and wipe as I said in the instructions. Make sure not to wipe the micro sdcard. Then install the rom then the google apps.
Click to expand...
Click to collapse
I am a little confused about this. This is what I have on the sdcard:
cm-11-20160603-UNOFFICIAL-kylepro.zip, TWRP.S7580.tar.md5, HDPI_gapps-kk-20160526-signed.zip.
I have done TWRP.. with Odin, is that what you mean "boot into it"??
"Hit install", where?? Wipe: Shall I "wipe cache partition"??
There is "wipe data/factory reset", but then everything is gone.
Please, can you show me point by point what to do, so I don't brick it all.
You know what, I stumbled across this video and it is basically a full tutorial! Lycka till med ditt flashande!
vespa70 said:
Hi!!!! It''s working now 4.4.4 kitkat is up
and running!! I don't belive it, but it's true.
I had to,in Odin, untick "autoreboot and F.Reset time". That maked the the damn thing not to reboot.
After that it worked.
Anyway, Many thank's for your hep!!
Bye
Click to expand...
Click to collapse
vespa70 said:
Hi!!!! It''s working now 4.4.4 kitkat is up
and running!! I don't belive it, but it's true.
I had to,in Odin, untick "autoreboot and F.Reset time". That maked the the damn thing not to reboot.
After that it worked.
Anyway, Many thank's for your hep!!
Bye
Click to expand...
Click to collapse
Ha, jag visste det från alla utropstecken , hoppas att allt funkar bra och om du får några bugg eller så rapportera det här.