I have a Vibrant T959. I just flashed from the latest official Cyanogenmod (android 4.2), to the latest unofficial cyanogenmod (Android 4.4.4).
However the phone is crashing in the setup process. I need to get back into clockworkmod, however I have tried the hold vol+, vol-, and power technique tons of times, and it does not work. I had trouble with that method before but would always just use rom manager to reboot to recovery, but needless to say, can't do that this time.
I'm currently attempting to use the ADB to reboot to recovery (which I've never used). I installed the latest JRE, and downloaded ADB, however currently I am unable to get the drivers for my phone. I understand I'm supposed to launch SDK manager to download them, however SDK manager does nothing, just pops up an empty command window for a split second and quits. Did some searching to see if I can download the ADB drivers seperate, but just found many dead, or untrustworthy looking links.
Been reading for hours, but i'm stumped now. All I need to do is just get back to clockworkmod recovery. Is there any way to do so?
Well just an update, by sheer luck I found a roundabout way to get back into recovery. Apparently from all the web searching lots of people are having the same problem with the 3 button combo not working. Supposedly it might be hardware locked.
Here is what worked for me.
Hold volume down and power, and after a couple seconds plug in a usb cord (other end was attached to pc, but no software or anything running)
Keep holding those 2 buttons for about 30 seconds, you'll see the battery icon flash a number of times, along with a little round loading cursor type thing which will also be flashing.
After about 30 seconds, release the power button but keep holding the volume down button for awhile.
After about 10 seconds, clockworkmod recovery pops right up.
Tags (for anyone else who may have this problem: Samsung vibrant T959 how to enter recovery. recovery fix. recovery not working. can't get to clockworkmod.
Try this!
servohead said:
I have a Vibrant T959. I just flashed from the latest official Cyanogenmod (android 4.2), to the latest unofficial cyanogenmod (Android 4.4.4).
However the phone is crashing in the setup process. I need to get back into clockworkmod, however I have tried the hold vol+, vol-, and power technique tons of times, and it does not work. I had trouble with that method before but would always just use rom manager to reboot to recovery, but needless to say, can't do that this time.
I'm currently attempting to use the ADB to reboot to recovery (which I've never used). I installed the latest JRE, and downloaded ADB, however currently I am unable to get the drivers for my phone. I understand I'm supposed to launch SDK manager to download them, however SDK manager does nothing, just pops up an empty command window for a split second and quits. Did some searching to see if I can download the ADB drivers seperate, but just found many dead, or untrustworthy looking links.
Been reading for hours, but i'm stumped now. All I need to do is just get back to clockworkmod recovery. Is there any way to do so?
Click to expand...
Click to collapse
ADB will work. Use the process given below and let me know if it works
1. Install stand alone SDK tools from here, they should work. (h ttp://dl .google.com/android/ins taller_r23-windows.ex e)(Delete all spaces in between.)
2.Note the folder where you have installed SDK tools.
3. Move all the ADB driver files ( Probably 2 .exe and 2 .dll files, or just copy all the files from the ADB driver folder in which you installed the ADB drivers ) to the SDK tools folder.
4.Make sure all usb drivers for your phone have been installed. ( If not just google it, you will find them in the first or second link)
5. Connect your phone and make sure it is recognized by your PC.
6.Navigate to the SDK folder where you have also copied the ADB files. Hold down SHIFT and right click, Select Open Command Window Here.
7. Type adb devices .It should show you all the connected devices, mainly numbers. If not, the ADB drivers have not been installed correctly.
8. If Step 8 works, to reboot into recovery just type " adb reboot recovery " without quotes.
9. Your phone will reboot into recovery .
(If the steps above don't work, you will have to install the latest custom CWM recovery for your device and then boot into recovery from Step 5. And if you get errors while flashing the rom or the custom recovery then you may have to check if signature verification toggle is enabled and disabled,it SHOULD be disabled.And then repeat the flashing process.)
Hope this works . Happy Flashing!:good:
Glad to know it works for you, for people who can't gain access to recovery any other way, ^ This is the way
Related
I'm very new to the whole flashing rom thing. I've tried an unknown amount of times to access clockwork recovery however continued to come to either stock recovery or black screen. I am becoming very frustrated with this whole process. Someone please help me with this.
The Streak overwrites custom recovery files, and that is why you're not seeing the custom recovery you installed. There is a way to stop this which involves renaming etc\install-recovery.sh to etc\install-recovery.sh.bak. I used SuperManager from the Market to do the job, since it can write to the system.
I can provide a more detailed how-to later, but in short, I installed streakmod recovery, rebooted, installed and ran SuperManager to change the file mentioned above, then installed streakmod recovery a second time in case I wanted to flash custom updates to files.
downloaded supermanager however still not entirely sure as what to do. if you are able further help me it would be greatly appreciated. this has become a significantly long process. thank you
http://forum.xda-developers.com/showpost.php?p=13603833&postcount=200
completed the task listed above. thank you for the required steps. however... using clockwork brings me to a black screen. you mentioned using streakmod? that will require fastboot right? I don't know how to use fastboot, like I can get to fastboot just not sure what to do from there. and on top of that no driver will properly install on my computer from the device for some reason, including android 1.0 and dell streak driver. what should I do now? thanks again for everything.
Flashing Streakmod will require getting into fastboot, yes. However you do not install drivers from the Streak. They areinstalled from the computer.
1a. Download ADB Tethering Drivers from here.
1b. Download Superuser and copy it to the root of the MicroSD card.
2. Download multirecovery flasher from here and extract the files to a directory, C:\Streak for example.
3. Run multirecovery flasher after reading up on how to use it, and select Streakmod Recovery.
4. Enter Fastboot mode on the Streak by holding down the camera button while turning the Streak on.
5. On the white screen that shows up following step 4, tap "Fastboot".
7. Wait for the response screen, which should say "Wait for USB FastBoot detect...".
8. Plug the data cable into the Streak, and watch the screen change to "FASTBOOT_MODE" in response.
9. The recovery image will very quickly load.
10. Hold down the volume up and down buttons then unplug the data cable. Continue holding down the buttons until you successfully get into Streakmod Recovery. From there you should be able to root the phone by installing Superuser from the "Install Update.zip" option in Streakmod Recovery.
11. Reboot.
12. If you want Streakmod Recovery to stick around, you'll need to follow the how to I provided earlier in the thread, then repeat steps 3-9 in this how to so Streakmod Recovery is reinstalled, since it was overwritten when you rebooted in step 11.
Now, you may encounter a problem at step 8, where the Streak does not show "FASTBOOT_MODE" but is stuck at "Wait for USB FastBoot detect...". This is where the ADB Tethering Driver I provided a link to comes into play.
1. Unzip the ADB Tethering Drivers into a directory.
2a. If running Windows XP, select "Run" and in the dialog box that pops up type "devmgmt.msc".
2b. If running windows Vista or Windows 7, in the search bar at the bottom of the Start Menu, type "device manager" and hit enter.
3. In the device manager should be an item labeled "Android 1.0".
4. Right click "Android 1.0" and select "Update Driver Software".
5. Select "Browse my computer for driver software".
6. Click on "Browse" and navigate to the directory where the ADB Tethering Driver is located.
7. Click "Next" to install the driver.
8. If a prompt comes up saying the driver is not digitally signed, ignore the prompt and install the driver anyway.
9. Re-run the how-to above.
Hopefully this helps, because this is exactly how I had to do it myself, including installing the driver.
Followed to a T and still have the same results. Black screen when I try to get into Streakmod. You get into SR by doing double volume and then selecting update.pkg right?
EDIT: fixed. I was trying to flash from 1.6 O2 recovery. Needed to update to 2.1 O2 to make it work. Thanks
Since this thread is here I hope someone can solve my similar problem. I am trying to install a zip file.
I want to run Clockwork mod recovery mode but when I try it just reboots as normal. I have tried following the instructions by renaming the recovery-install file. But nothing has happened. I am on o2 stock 2.2 is there another option available to me or will I have to go down the Fastboot method?( Which I don't fancy trying to get my head round!)
You need to go into fastboot in order to flash the recovery from your computer. Did you do that?
Turn phone off, hold camera button, turn phone off, wait 20 seconds, connect phone, run multi recovery flasher to install streakmod, reboot. Hold volume buttons when phone restarts, then press power on the blank screen to bring up streakmod.
Maybe I'm misunderstanding something?
Sent from my Dell Streak using XDA App
eSZee said:
You need to go into fastboot in order to flash the recovery from your computer. Did you do that?
Turn phone off, hold camera button, turn phone off, wait 20 seconds, connect phone, run multi recovery flasher to install streakmod, reboot. Hold volume buttons when phone restarts, then press power on the blank screen to bring up streakmod.
Maybe I'm misunderstanding something?
Sent from my Dell Streak using XDA App
Click to expand...
Click to collapse
Hmm...I didn't want to hear that but I guess I'll have to give it a go.
I was hoping that I could just do it from running Recovery Mode from Rom Manager without the fuss of messing with Fastboot mode. I've read too many scary stories of things going wrong. If everything goes to plan then I may as well consider trying to install 2.2.2.
Thanks mate.Have a +1 on me!
this was very simple to do once figured it out. streakdroid is running very well. I would like to thank everyone here for the help.
first off, i just wanted to state, before i get ripped into, i have spend the last 1.5 days reading everything i can find on any forum that comes back with search results for my issue. i've tried numerous drivers, different PC's, even a Linux Live CD system.
I cannot get my PC (win 7, 32 bit) to see my TF201 via ADB.
It is installed in the device manager with the "universal naked driver 0.7", and shows up as "Asus Transformer Prime ADB Interface". But whenever i try to connect via ADB to run the fix in this thread - http://forum.xda-developers.com/showthread.php?t=1514088 - i cannot see the device.
I have tried all of the mount/unmount options in CWM. nothing is working for me.
is there anyone that has run into this? And if so, have you found a resolution?
sorry if i'm coming off as the typical noob here, but i really have put in time researching the issue and attempting other fix-it routes before posting up a help thread.
Thanks!!
perch_44 said:
first off, i just wanted to state, before i get ripped into, i have spend the last 1.5 days reading everything i can find on any forum that comes back with search results for my issue. i've tried numerous drivers, different PC's, even a Linux Live CD system.
I cannot get my PC (win 7, 32 bit) to see my TF201 via ADB.
It is installed in the device manager with the "universal naked driver 0.7", and shows up as "Asus Transformer Prime ADB Interface". But whenever i try to connect via ADB to run the fix in this thread - http://forum.xda-developers.com/showthread.php?t=1514088 - i cannot see the device.
I have tried all of the mount/unmount options in CWM. nothing is working for me.
is there anyone that has run into this? And if so, have you found a resolution?
sorry if i'm coming off as the typical noob here, but i really have put in time researching the issue and attempting other fix-it routes before posting up a help thread.
Thanks!!
Click to expand...
Click to collapse
Update****
I was able to get it out of the boot loop, so that it will boot to the splash screen. well following instructions i've found online, when in CWM, i connected through ADB and pushed a copy of cm9.zip up to the internal storage.
yet, whenever i choose "install from zip" in CWM, it never finds the zip file.
i have done it a few times now and it says it copies up completely, but never actually shows up.
syntax i'm using: adb push cm9filename.zip "/sdcard/cm9filename.zip"
it takes about two minutes and gives me confirmation that it pushed x amount of bytes of data for the file, and says its done. I then go back to the tablet in CWM and choose install from sdcard, and it says there are no files.
I'm about ready to throw this thing in the trash and be done with it......
First of all make a small text file and zip it up for a test file that wont take long to push.
Now type adb push test.zip /data/media/
look if the file is showing where you go to install a rom.
If it is showing then push the rom to the same place then install it
flumpster said:
First of all make a small text file and zip it up for a test file that wont take long to push.
Now type adb push test.zip /data/media/
look if the file is showing where you go to install a rom.
If it is showing then push the rom to the same place then install it
Click to expand...
Click to collapse
If that fails, I had the same issue with cwm, I installed twrp via fastboot and haven't had the problem of the file not showing up after adb push. Fustrating I know.... I tired everything I could think of in cwm multiple reboots different usb ports... on an on......
Please HELP CWM Roocovery Loop!!!
perch_44 said:
Update****
I was able to get it out of the boot loop, so that it will boot to the splash screen. well following instructions i've found online, when in CWM, i connected through ADB and pushed a copy of cm9.zip up to the internal storage.
yet, whenever i choose "install from zip" in CWM, it never finds the zip file.
i have done it a few times now and it says it copies up completely, but never actually shows up.
syntax i'm using: adb push cm9filename.zip "/sdcard/cm9filename.zip"
it takes about two minutes and gives me confirmation that it pushed x amount of bytes of data for the file, and says its done. I then go back to the tablet in CWM and choose install from sdcard, and it says there are no files.
I'm about ready to throw this thing in the trash and be done with it......
Click to expand...
Click to collapse
I am having the same exact problem. It started when I tried to restore my stock backup that I made using CWM 5.8.2.0 coming from the CM rom. I am stuck in the CWM recovery screen and cant get ADB to see the TF Prime. I just get error: device not found. How did you manage to push a zip if ADB wasn't seeing your device? I have been looking for a fix for the last week now.
Forget CWM fastboot flash TWRP then load your rom via microsd.....
Danny80y said:
Forget CWM fastboot flash TWRP then load your rom via microsd.....
Click to expand...
Click to collapse
How do I flash TWRP when Im stuck CWM?
hellshavoc said:
How do I flash TWRP when Im stuck CWM?
Click to expand...
Click to collapse
The answer is in the post you quote, did you read it? Fastboot, see on twrp site.
Striatum_bdr said:
The answer is in the post you quote, did you read it? Fastboot, see on twrp site.
Click to expand...
Click to collapse
the problem is whenever it try to fastboot it just keeps saying waiting for device. I can put my TF prime in fastoot mode when I power on while holding down on vol it just goes right to CWM recovery and any adb command gives me no device found and I tried APX mode (holding vol up during power on) and tried to use NVFlash but that just gives me an error device not recognized. I have all the drivers installed. I used the naked drivers .7 and have cleared out all the old drivers too.
hellshavoc said:
the problem is whenever it try to fastboot it just keeps saying waiting for device. I can put my TF prime in fastoot mode when I power on while holding down on vol it just goes right to CWM recovery and any adb command gives me no device found and I tried APX mode (holding vol up during power on) and tried to use NVFlash but that just gives me an error device not recognized. I have all the drivers installed. I used the naked drivers .7 and have cleared out all the old drivers too.
Click to expand...
Click to collapse
you hold the volume down until the screen starts, then you let go and wait
whycali said:
you hold the volume down until the screen starts, then you let go and wait
Click to expand...
Click to collapse
As I stated above holding down Val down while turning on does not bring up the menu it still just boots right into CWM recovery. i have no option for fastboot or anything.
hellshavoc said:
As I stated above holding down Val down while turning on does not bring up the menu it still just boots right into CWM recovery. i have no option for fastboot or anything.
Click to expand...
Click to collapse
No, you hold Vol down + power then when the first screen with sentences appears you release everything DON'T touch anything, after 5 secondes you will end in a screen with three icons, with volume down youu select the usb icon in the middle, then volume up.
This procedure works even on locked devices except that in this case you don't have the usb icon, only the factory reset and cold reboot ones. So it's impossible you don't obtai this screen, it's hardware coded.
It is confusing but just keep trying till you get it!! Once there go to the TWRP site they have the file and the fastboot commands all set in a guide.
I have exactly the same problem than you.
I had the fastboot/adb connection (I used to push the rom by adb), but i tried to install a wrong version on gapps. Since then, I'm stock in the recovery mode without adb/fastboot connection.
If you find a solution for that, pleaze post it !!
Striatum_bdr said:
No, you hold Vol down + power then when the first screen with sentences appears you release everything DON'T touch anything, after 5 secondes you will end in a screen with three icons, with volume down youu select the usb icon in the middle, then volume up.
This procedure works even on locked devices except that in this case you don't have the usb icon, only the factory reset and cold reboot ones. So it's impossible you don't obtai this screen, it's hardware coded.
Click to expand...
Click to collapse
I have searched a lot on google and xda and havn't found an answer to my issue. Either I'm searching for the wrong thing or I have a very unique problem.
My basic problem is on two Nabi 2's I can't access the bootloader in order to be able to fastboot TWRP (or any other recovery). It just perpetually hangs.
Both tablets boot just fine. Both tablets are on 1.9.37. Both tablets can be factory wiped via the stock recovery.
Both tablets were rooted via TWRP 2.3.3.0 a few years ago in order to install gapps. I wanted to be able to upgrade the tablets to JB when it came out so I used Nabilablite to "return to stock". I followed all of the prompts and it appeared as though everything worked as desired. I downloaded the OTA update told it to install and never looked at the version again...I just assumed it installed. Handed the tablets back to the kids and everyone was happy. Apparently all I did was flash the stock recovery because they are still rooted and have gapps after several factory resets.
Now (a year later) I have realized I was a dufas and didn't actually effect the change I wanted.
If I hold Vol+ & Pwr buttons it loads to the recovery/boot menu with "boot normally" "fastboot protocol" "recovery kernal" and "forced recovery". If I boot normal, the tablet works fine but I can't update via OTA.
If I choose fastboot protocol it just hangs...for ever...HOW DO I FIX THIS!?!?!
If I choose recovery kernal it loads the stock recovery but still wont install any update OTA or otherwise, even from the sd card.
If I choose forced recovery nothing happens, it also appears to just hang.
If I hold Vol- & Pwr button the nabi logo flashes then the device turns off.
If I hold Vol+ & Vol- & Pwr buttons it appears to be the same as just Vol+ & Pwr.
With the tablet on and fully booted I can see it via ADB. I tried using the adb restart bootloader. The tablet reboots but then just hangs never actually loading the boot loader...
I found http://forum.xda-developers.com/showthread.php?t=2587543. But aicjofs mentions seeing a bootloader issue once before.
Usually when it hangs at the Nabi logo it means you don't have the USB cable plugged in or that the fastboot driver is not installed.(Check device manager and see if fastboot driver is installed/no exclimation point). If that's not the issue then it's the bootloader which I have only seen one person have that issue. Depending on which OTA's you have ran there was an update to a Jellybean bootloader so it's possible. That can be fixed with nvflash or placing the bootloader blob in the staging partition.
Also you can always get recovery back without fastboot in Android by dd'ing the recovery over.
For example if the recovery image is on the internal SD
dd if=/data/media/recovery.img of=/dev/block/platform/sdhci-tegra.3/by-name/SOS
Click to expand...
Click to collapse
I have NO idea what dd'ing the recover over is...
Thank you for any help fixing this.
P.S. I have a 3rd tablet that I also used TWRP 2.3.3.0 on to root and install gapps with. I did NOT use nabilablite on that tablet to return to stock. Yesturday I used fastboot to flash TWRP 2.6(something) to flash a JB OTA update which worked fine. It was also able to download and install every other OTA update all the way to the most recent KK with no problems...
najman9 said:
I have searched a lot on google and xda and havn't found an answer to my issue. Either I'm searching for the wrong thing or I have a very unique problem.
My basic problem is on two Nabi 2's I can't access the bootloader in order to be able to fastboot TWRP (or any other recovery). It just perpetually hangs.
Both tablets boot just fine. Both tablets are on 1.9.37. Both tablets can be factory wiped via the stock recovery.
Both tablets were rooted via TWRP 2.3.3.0 a few years ago in order to install gapps. I wanted to be able to upgrade the tablets to JB when it came out so I used Nabilablite to "return to stock". I followed all of the prompts and it appeared as though everything worked as desired. I downloaded the OTA update told it to install and never looked at the version again...I just assumed it installed. Handed the tablets back to the kids and everyone was happy. Apparently all I did was flash the stock recovery because they are still rooted and have gapps after several factory resets.
Now (a year later) I have realized I was a dufas and didn't actually effect the change I wanted.
If I hold Vol+ & Pwr buttons it loads to the recovery/boot menu with "boot normally" "fastboot protocol" "recovery kernal" and "forced recovery". If I boot normal, the tablet works fine but I can't update via OTA.
If I choose fastboot protocol it just hangs...for ever...HOW DO I FIX THIS!?!?!
If I choose recovery kernal it loads the stock recovery but still wont install any update OTA or otherwise, even from the sd card.
If I choose forced recovery nothing happens, it also appears to just hang.
If I hold Vol- & Pwr button the nabi logo flashes then the device turns off.
If I hold Vol+ & Vol- & Pwr buttons it appears to be the same as just Vol+ & Pwr.
With the tablet on and fully booted I can see it via ADB. I tried using the adb restart bootloader. The tablet reboots but then just hangs never actually loading the boot loader...
I found http://forum.xda-developers.com/showthread.php?t=2587543. But aicjofs mentions seeing a bootloader issue once before.
I have NO idea what dd'ing the recover over is...
Thank you for any help fixing this.
P.S. I have a 3rd tablet that I also used TWRP 2.3.3.0 on to root and install gapps with. I did NOT use nabilablite on that tablet to return to stock. Yesturday I used fastboot to flash TWRP 2.6(something) to flash a JB OTA update which worked fine. It was also able to download and install every other OTA update all the way to the most recent KK with no problems...
Click to expand...
Click to collapse
EDIT: OOOPPS. I didn't see this was in the XDA Assist section. I'm not suppose to answer questions(I was just searching for Nabi questions and didn't notice this was XDA assist), dedicated XDAers just point you in the right direction in this section. Please ask the question again in the Nabi2 section and I'l come help you. http://forum.xda-developers.com/nabi-2
This might help answer some questions http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119
If it just hangs at fastboot protocol then the USB connection isn't good or fastboot driver isn't installed most of the time. Can you verify fastboot shows up in device manager?(I know the 3rd tabet worked OK) .
Nabilabite doesn't do anything that should change the bootloader, and fastboot should still work as it did before.
dd'ing recovery over means that you use the root access you have in Android to flash the recovery partition instead of using fastboot. IT's just another way of getting the TWRP recovery on the tablet.
The stock recovery won't install the OTA because when you added Gapps it changed some fies and the OTA sees those files as invalid and will fail.
Forced recovery always looks blank screen. It's waiting for you to give it a bootloader to run(beyond the scope here).
You should be able to get back on track once you have TWRP loaded. It's one of 3 things. Bad USB connection, fastboot driver not installed right, bootloader damage. Check the first 2 issues despite the fact the 3rd tablet had no such problems.
One of the XDA smart guys fixed my error of posting this in the wrong section.
I'm running Windows 7 Ultimate and have installed and re-installed the drivers several times. When the tablet's are fully booted ADB has a good connection and sucessfully sends the command to reboot. So I don't believe there is a driver or USB cable error...
When the tablets hang on the fastboot protocol my computer makes the usb connecting noise but fails to install the drivers...
When I hit forced recovery I hear the unrecognized USB device sound...
These two things make me think I don't have the proper drivers installed...but I don't understand how the driver's work when the tablet is booted but not when trying to access the boot loader.
It appears as though I'm going to have to try the dd method if you are able to point me in that direction please.
EDIT: Now I'm thinking I really DON'T have the fastboot drivers installed. I just plugged the 2nd tablet that hands on the fastboot menu and fastboot failed. I also booted the tablet completly, the adb driver's installed correctly but the fastboot driver's did not...I have installed the 64 bit driver's included with nabilablite. I can't find any actual other downloads. The 15 second ADB installer didn't change anything...
najman9 said:
One of the XDA smart guys fixed my error of posting this in the wrong section.
I'm running Windows 7 Ultimate and have installed and re-installed the drivers several times. When the tablet's are fully booted ADB has a good connection and sucessfully sends the command to reboot. So I don't believe there is a driver or USB cable error...
When the tablets hang on the fastboot protocol my computer makes the usb connecting noise but fails to install the drivers...
When I hit forced recovery I hear the unrecognized USB device sound...
These two things make me think I don't have the proper drivers installed...but I don't understand how the driver's work when the tablet is booted but not when trying to access the boot loader.
It appears as though I'm going to have to try the dd method if you are able to point me in that direction please.
EDIT: Now I'm thinking I really DON'T have the fastboot drivers installed. I just plugged the 2nd tablet that hands on the fastboot menu and fastboot failed. I also booted the tablet completly, the adb driver's installed correctly but the fastboot driver's did not...I have installed the 64 bit driver's included with nabilablite. I can't find any actual other downloads. The 15 second ADB installer didn't change anything...
Click to expand...
Click to collapse
Uninstall those nablablite and try this one. http://forum.xda-developers.com/showpost.php?p=62826514&postcount=2639
Or look at the other options in section 4 here http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119
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.
Hi,
I have encountered a suddenly dead old device. It was working long time without an issue, but one day it does not start and just a logo is displayed. It was possible to turn off the device or enter the recovery menu. I have found more posts about repairing with some unofficial flash tools or using unofficial ROMs.
I was able to revive the device finally with success and using official tools only, so I would like to share the steps I have used, basically it is about downloading the official ROM from Acer site and flashing it with ADB:
1. You will need Windows computer, I was not able to make the Mac recognise the phone properly, but maybe it is somehow possible.
2. Download official Android 4.4.2 ROM from ACER site: https://www.acer.com/ac/en/GB/content/drivers
enter SNID (check the phone under cover), look in OS category and download, the ZIP file is ~700MB large, do not unzip.
Download also the Drivers and extract it.
No need to download unofficial ROMs or drivers for this phone I think.
3. Download android platform tools from https://developer.android.com/studio/releases/platform-tools and unpack to some directory
4. Install phone Drivers manually from Device manager, use Action/Add device command and navigate to INF in the driver folder.
5. Turn on the phone and star recovery mode (Vol down+Power).
6. Connect the charged device with USB cable.
7. Start cmd.exe and navigate to platform-tools directory, start "adb devices" command, your device should be listed.
If no device is listed, return to driver installation step.
8. start "adb reboot bootloader", phone will reboot, hint about flashing the ROM appears
9. start "adb sideload yourpathto/officialROM.zip
10. wait few minutes until the installation is finished, phone reboots and should work.
11. you are happy
Hey,
2 Years ago my E700 dropped down, since then it does not work anymore. It shows no reaction if i want to start the device.
Could something be broken?
Do you have an idea to fix it?