Related
My recovery image seems to be messed up since I can't boot into it. My phone will boot but everytime it does ADW crashes over and over not allowing me to do anything. What can I do to go about getting the recovery fixed again and reflashing to try to smooth everything out?
*Edit*.I think I may have thought of a work around. I emailed my self the launcherpro.apk and installed it through gmail. Now I can access my phone. Now I just need to flash a working recovery..
I do appreciate your help though Riley.
You can try downloading ADW Launcher, putting it on your SD card and boot from recovery, then flash the launcher. It is a far shot, but if launcher is the only problem, maybe reflashing it will do the trick.
** EDIT ** My apologies. I misunderstood. I thought you were referring to a corrupted recovery image that you had made of your ROM!
You say you can't boot into recovery/ what's your phone do or say when trying to boo4 in recovery? You may have to push new recovery image via fastboot.
CGriffiths86 said:
My recovery image seems to be messed up since I can't boot into it. My phone will boot but everytime it does ADW crashes over and over not allowing me to do anything. What can I do to go about getting the recovery fixed again and reflashing to try to smooth everything out?
Click to expand...
Click to collapse
If you have USB debugging turned on you can flash Amon_RA via an adb shell using the flash_image tool - exactly the way the original Eris rooting process worked. With your phone looping, it will run very slowly, but will still succeed.
If you have the S-OFF bootloader installed, you can flash the recovery with fastboot.
I'll have an XDA admin move this thread to the Q&A forum.
Ok guys..I got launcher pro installed so I can actually access my phone now. I attempted to Flash a recovery with Rom Manager and it says it succeeds but it will never boot into it. I do have the bootloader with the "off". Is there a market app or something that can easily flash the recovery? I only ask because I am not at my PC with the android sdk stuff.
CGriffiths86 said:
Ok guys..I got launcher pro installed so I can actually access my phone now. I attempted to Flash a recovery with Rom Manager and it says it succeeds but it will never boot into it. I do have the bootloader with the "off". Is there a market app or something that can easily flash the recovery? I only ask because I am not at my PC with the android sdk stuff.
Click to expand...
Click to collapse
If you can't get to a PC to use adb, you could use a root shell in a terminal emulator to flash recovery using flash_image. That's kind of painful/tedious though - almost enough so to make it worth your while to just wait until you get back to your PC.
It is technically feasible to put together a flashable ROM to re-flash the recovery, but I'm not aware of anyone having done so for the Eris.
Oh ok..well I have RA Eris 1.6.2 recovery on my sd card. So I can just flash it via the termninal emulator, right?
** I tried to install via terminal and it says "header is the same, not flashing recovery". Do you think I could install the stock Eris recovery and reflash Amon's?
UPDATE!!: I got a recovery to flash..YAY..thanks guys
CGriffiths86 said:
Oh ok..well I have RA Eris 1.6.2 recovery on my sd card. So I can just flash it via the termninal emulator, right?
** I tried to install via terminal and it says "header is the same, not flashing recovery". Do you think I could install the stock Eris recovery and reflash Amon's?
Click to expand...
Click to collapse
are you using "flash_image"? If so, where is it from? To my knowledge (the statically linked version from Amon_RA - /sbin/flash_image) is a pretty simplistic program - it performs no checks, and will let you flash total garbage to any named partition on your phone. (Which is why you should verify the md5 of the recovery image before you flash it, BTW; you can use the AFV app for that)
Hello! Sorry for posting this here, Idk if this is the right area for this kind of thing but anyways lets get started!!
Im sorry if this had already been posted, I have searched the forums before to see If someone had found a solution while I was having the error!
Sorry for this, but I posted this already here: http://forum.xda-developers.com/showthread.php?t=1370478 So moderators will you please delete the above post! Thanks so much!
This has happened to me so many times, I got frustrated, then I tried this out of the blue and it seemed to work..
Some examples of ROMS that froze on boot on my HTC EVO 3D HBOOT 1.5
All Infected ROMS
MIUI
Synergy
Senseless ROM
CleanRom
and some others..
These are the steps I took to fix the issue!
1. Flash ROM and see if it freezes on boot, if it does start below
2. After flashing rom and confirming that it does freeze.. Boot into bootloader (Power+volume down key) and press the power button while highlighted over fastboot.
3. Plug in your device into PC or MAC
4. Make sure you have the latest android SDK, im pretty sure you do if you have been flashing roms!
5. EXTRACT the .zip file of the ROM that you are using that freezes.
6. Open the folder and copy the boot.img from that ROM
7. Paste that .img into the folder that has your adb and fastboot files for the Android SDK!
8. in terminal navigate to that folder, and do the following commands
PC:
Code:
fastboot flash boot boot.img
Ive done it on the PC and most of the time I have issues.. like failing of transferring over of the boot.img.. So far I don't know a way around this besides to keep trying!!
MAC:
Code:
./fastboot flash boot boot.img
Ive done it on my mac as well, and so far I have had no errors! It works everytime.
9. After that reboot your phone..
10. Watch in awe as your phone should reboot and not freeze!
Thank you for reading this!!
~Bairdog35
Bairdog35 said:
Hello! Sorry for posting this here, Idk if this is the right area for this kind of thing but anyways lets get started!!
Im sorry if this had already been posted, I have searched the forums before to see If someone had found a solution while I was having the error!
Sorry for this, but I posted this already here: http://forum.xda-developers.com/showthread.php?t=1370478 So moderators will you please delete the above post! Thanks so much!
This has happened to me so many times, I got frustrated, then I tried this out of the blue and it seemed to work..
Some examples of ROMS that froze on boot on my HTC EVO 3D HBOOT 1.5
All Infected ROMS
MIUI
Synergy
Senseless ROM
CleanRom
and some others..
These are the steps I took to fix the issue!
1. Flash ROM and see if it freezes on boot, if it does start below
2. After flashing rom and confirming that it does freeze.. Boot into bootloader (Power+volume down key) and press the power button while highlighted over fastboot.
3. Plug in your device into PC or MAC
4. Make sure you have the latest android SDK, im pretty sure you do if you have been flashing roms!
5. EXTRACT the .zip file of the ROM that you are using that freezes.
6. Open the folder and copy the boot.img from that ROM
7. Paste that .img into the folder that has your adb and fastboot files for the Android SDK!
8. in terminal navigate to that folder, and do the following commands
PC:
Code:
fastboot flash boot boot.img
Ive done it on the PC and most of the time I have issues.. like failing of transferring over of the boot.img.. So far I don't know a way around this besides to keep trying!!
MAC:
Code:
./fastboot flash boot boot.img
Ive done it on my mac as well, and so far I have had no errors! It works everytime.
9. After that reboot your phone..
10. Watch in awe as your phone should reboot and not freeze!
Thank you for reading this!!
~Bairdog35
Click to expand...
Click to collapse
Your problem lies in your HBOOT 1.5.... you need to flash the kernel separately, either the way you described it, or I think theres an app called FlashGUI
or just access recovery from fastboot & flash like normal.
This should be moved
Lulz. 10 char.
Sent from my PG86100 using xda premium
SketchyStunts said:
or just access recovery from fastboot & flash like normal.
This should be moved
Click to expand...
Click to collapse
This.
Maybe OP doesn't know about it so I'll guide him.
OP, we appreciate you trying to help but if you follow the steps below you should have no problem.
1. Download the Rom you want and place it on your sd card.
2. Plug your phone in to your computer and open a cmd file where 'adb' is located and type "adb reboot bootloader".
3. Your phone will now restart and boot into bootloader. Now type in "fastboot boot recovery.img". Your phone will now boot into your recovery.
(At this point, you can unplug your phone.)
4. Use the recovery as how you normally would and wipe/flash, etc.
Enjoy.
arozer said:
This.
Maybe OP doesn't know about it so I'll guide him.
OP, we appreciate you trying to help but if you follow the steps below you should have no problem.
1. Download the Rom you want and place it on your sd card.
2. Plug your phone in to your computer and open a cmd file where 'adb' is located and type "adb reboot bootloader".
3. Your phone will now restart and boot into bootloader. Now type in "fastboot boot recovery.img". Your phone will now boot into your recovery.
(At this point, you can unplug your phone.)
4. Use the recovery as how you normally would and wipe/flash, etc.
Enjoy.
Click to expand...
Click to collapse
Yes I do this, and I still have to do what I provided up above. Idk what is wrong with my phone.
Your recovery can't flash kernels. Hence the boot loop.
There is a program in the evo3d theme and apps forum for us 1.5 boot loader users to flash the kernel using an app in android then you reboot to recovery and flash rom.
The app is called flash image GUI
http://forum.xda-developers.com/showthread.php?t=1192527
[APP] Flash Image GUI - Flash Kernels and Recoveries from normal Android mode!
Sent from my PG86100 using xda premium
shadowmike said:
Your recovery can't flash kernels. Hence the boot loop.
There is a program in the evo3d theme and apps forum for us 1.5 boot loader users to flash the kernel using an app in android then you reboot to recovery and flash rom.
The app is called flash image GUI
http://forum.xda-developers.com/showthread.php?t=1192527
[APP] Flash Image GUI - Flash Kernels and Recoveries from normal Android mode!
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
If you use that app and flash the boot.img from the rom and then go into recovery and flash the rom it should work
Sent from my HTC Evo 3D using XDA App
bairdog35 said:
hello! Sorry for posting this here, idk if this is the right area for this kind of thing but anyways lets get started!!
Im sorry if this had already been posted, i have searched the forums before to see if someone had found a solution while i was having the error!
Sorry for this, but i posted this already here: http://forum.xda-developers.com/showthread.php?t=1370478 so moderators will you please delete the above post! Thanks so much!
this has happened to me so many times, i got frustrated, then i tried this out of the blue and it seemed to work..
Some examples of roms that froze on boot on my htc evo 3d hboot 1.5
all infected roms
miui
synergy
senseless rom
cleanrom
and some others..
these are the steps i took to fix the issue!
1. Flash rom and see if it freezes on boot, if it does start below
2. After flashing rom and confirming that it does freeze.. Boot into bootloader (power+volume down key) and press the power button while highlighted over fastboot.
3. Plug in your device into pc or mac
4. Make sure you have the latest android sdk, im pretty sure you do if you have been flashing roms!
5. Extract the .zip file of the rom that you are using that freezes.
6. Open the folder and copy the boot.img from that rom
7. Paste that .img into the folder that has your adb and fastboot files for the android sdk!
8. In terminal navigate to that folder, and do the following commands
pc:
Code:
fastboot flash boot boot.img
ive done it on the pc and most of the time i have issues.. Like failing of transferring over of the boot.img.. So far i don't know a way around this besides to keep trying!!
mac:
Code:
./fastboot flash boot boot.img
ive done it on my mac as well, and so far i have had no errors! It works everytime.
9. After that reboot your phone..
10. Watch in awe as your phone should reboot and not freeze!
Thank you for reading this!!
~bairdog35
Click to expand...
Click to collapse
this worked for me it was hanging at the htc white logo screen did this steps and the phone passed the first boot logo and it turned on fine!!!
That's due to not flashin a kernel right or you skipped a part of the wipe.
Virus has this guide for flashing the kernel on his page
The problem with using this "Flash Image GUI" is the FACT that if an individual can't boot a ROM, they obviously can't run the apk.
Individuals with HBOOT 1.5 have two choices in this situation (bootloop)...
Either
1. "adb reboot bootloader" after which you run "fastboot boot recovery.img" (recovery.img must be placed in fastboot directory), then you flash the ROM/kernel in question...
Or
2. Flash boot.img through fastboot (which is what the above "should" do in the fist place).
BTW: If you always have a problem with bootloops, you aren't loading recovery the way you should...
You can either run the commands mentioned earlier in this post, or go to
forum.xda-developers.com/showthread.pho?t=1403148
and download the batch in the second post "jthein1989_batch.zip" (you will still need to download and copy the recovery.img to the folder).
Just download twrp or clockwork and copy it as "recovery.img" to the directory that you unzipped the batch to... Then, just follow the OP of my thread...
Sent from my PG86100 using XDA App
Maybe I'm a noob,
But you mean you can't select Recorery from Hboot menu? Even if you installed twrp? I don't know much of what I'm doing only had 3d for week. but its locks up at white HTC screen all the time.
Or you could try...
Fastboot boot my kernel or ill kill you.img
Sent from my HTC EVO 3D using xda premium
jcfunk said:
Maybe I'm a noob,
But you mean you can't select Recorery from Hboot menu? Even if you installed twrp? I don't know much of what I'm doing only had 3d for week. but its locks up at white HTC screen all the time.
Click to expand...
Click to collapse
With HBOOT 1.5 you "can" start recovery without ABD, but "S-ON" will not allow you to properly flash to the BOOT partition (limitation of the HTC unlock method). Therefore, users with HBOOT 1.5 need to go to extra lengths to flash the BOOT partition.
Sent from my PG86100 using XDA App
Having HBOOT 1.5, I've ran into this very problem. I'm not sure if it's hardware or what, but my phone will not run any Sense 3.5 ROM's I've tried. The phone just won't boot! I gave up trying 3.5 ROM's. I used ABD to put a 3.0 kernel back on and restore the recovery and everything is fine again. This will probably be my last HTC phone. Hoping something better besides the S2 is coming soon.
OK so I have the Sprint EVO 4G LTE with 1.22.651.3 on it, rooted, S-ON. I have the Team Win Recovery Project v.2.1.8 on it as well with hboot 1.15. I tried loading the newest rooted software 2.13.651.1 710RD and voila.... paperweight. I tried reloading 1.22.651.3 and nothing. I can still boot to the bootloader and TWRP recovery, but nothing seems to work and now because sprint screwed up and removed my total equipment protection service from my plan, I don't have insurance on the phone. PLEASE HELP!!!
You just need to flash the kernel, extract it from the Rom (boot.img) and place it in adb folder, connect phone I'm bootloader and type fastboot flash boot boot.img
You can also flash meanrom, it has a working kernel installer, just let it sit because the kernel installer does take awhile 5-10 minutes
om4 said:
You just need to flash the kernel, extract it from the Rom (boot.img) and place it in adb folder, connect phone I'm bootloader and type fastboot flash boot boot.img
You can also flash meanrom, it has a working kernel installer, just let it sit because the kernel installer does take awhile 5-10 minutes
Click to expand...
Click to collapse
Can you explain how to do this in greater detail? I'm experienced only enough to be dangerous to myself lol
This program should install the kernel that you need. If not you are supposed to be able to swap boot.img files that it will install.
http://forum.xda-developers.com/showthread.php?t=1917106
http://forum.xda-developers.com/showthread.php?t=1752270
This is for the One S but it's the same process for our phones also.
Sorry I've been in a low coverage area and just got home. Open the Rom, extract the boot.img, open adb folder or SDK, hold shift and right click, select open command window here, connect phone in fastboot and type fastboot flash boot boot.img
So I tried to use that program to flash the boot.img from the fastboot screen but the computer wouldnt connect to the phone... now what?
Boot from system into hboot and fast boot while plugged in via USB. Helps your PC determine drivers.
Also, if you need a guide for setting up adb/fastboot, Google a YouTube vid by qbking77 on how to unlock galaxy nexus bootloader, it links to a great tutorial.
from my flying AOKP'd Evo LTE and xda premium
do you have SDK installed on your computer? If not install it. Go through the setup (set up your your environment variables) for fastboot.
Make a copy of the boot.img from a ROM of your choice. Place it in a folder on your desktop name the folder (android) leave the folder open.
Open cmd
Type cd Desktop press enter
Type cd android press enter
Type fastboot flash boot boot.img
After that it should say sending then OK
After that go into recovery then flash the ROM
you should be good to go then...
Sent from my EVO using xda app-developers app
The full SDK is not necessary, just the debug tools
ADB Tools
Also you can directly open the command prompt from within the folder by holding shift and opening the context menu (shift+right click) then select open command window here
i keep getting a message in windows "usb device not recognized" so i switched usb cables and finally got that program to load the boot.img file, then flashed a rom in bootloader but its still not booting... any ideas?
Did you make sure to wipe the phone first? What rom are you trying to flash?
wiped phone first and now trying to flash 2.13.651.1 after loading boot.img thru that program
you have to find a way to update your twrp to version 2.2.0 cause this is the culprit that gave you the issues. did you make a backup try doing a restore to get back up and running then download goomanager from the google play store and install the latest twrp here is a video to update to the latest twrp through goomanager.
twrp downloads I dont know if you have to be s-off to install in bootloader or not. maybe someone could clarify that
ok so i tried flashing twrp 2.2.2.0 and got a message saying "main verison is older" then it said "update failed!" which is weird since i had version 2.1.8.0 to begin with i think.
anyone? any ideas? I feel like my only resort is to have it replaced
You could fastboot flash the recovery image. Thats how I usually do it
So download the recovery image from twrp website and place it in your a dB folder. I don't have my PC but I think the command is fastboot flash recovery "recovery image"
Sent from my EVO using xda premium
corcgaigh said:
You could fastboot flash the recovery image. Thats how I usually do it
So download the recovery image from twrp website and place it in your a dB folder. I don't have my PC but I think the command is fastboot flash recovery "recovery image"
Sent from my EVO using xda premium
Click to expand...
Click to collapse
this should be the correct code to type
fastboot flash recovery openrecovery-twrp-2.1.8-jewel.img
Or
fastboot flash recovery openrecovery-twrp-2.2.2-jewel.img
Depending on how twrp names their recovery image
Sent from my EVO using xda app-developers app
Ok so i updated the twrp by changing the txt file to the proper software number.... then i flashed the lastest software version and NOW IT STARTS!!! WOOOHOOO!!!! Thanks everyone!!
Here is a simple, easy guide to install a custom recovery and root your device after achieving S-Off using the RevOne method.
**Moonshine installs all the SU/busybox binaries needed for root. So if you merely want a custom recovery you can follow this guide up to Step 7.**
Takes less than 5 minutes and is really easy. First, go to one of these threads and download either classic or touch CWM CWM Recovery or TWRP if you so prefer TWRP Recovery
Step 1. Rename recovery file recovery.img *Note: If using Win7 or 8 it hides known file extensions by default. Take care to not rename the file to "recovery.img.img"*
Step 2. Move file to your folder containing fastboot.exe on your computer
Step 3. Make sure phone is plugged in to USB port and USB debugging is turned on.
Step 4. Open a command prompt and type in: adb devices
Step 5. If device is listed type: adb reboot bootloader
Step 6. Using the command prompt, cd to the directory that has your fastboot.exe and recovery file *example: cd C:\sdk\
Step 7. Once in the bootloader type: fastboot flash recovery recovery.img
Step 8. If everything goes as it should, the recovery should be installed. On the bootloader screen you are currently on navigate to and select the BOOTLOADER option. Once it takes you to the new screen, navigate to and select RECOVERY
Step 9. Once it boots into recovery, select reboot now. It will prompt you to root the device. Select Yes.
Step 10. Phone will reboot. You now have a custom recovery and are rooted. Go to the play store and download either SuperUser or SuperSU. I prefer SuperSU, but it is entirely up to you.
Click to expand...
Click to collapse
Enjoy!!
Really nice guide. Thanks for writing this. It's also exactly the same steps one would use for TWRP, if someone is wondering about that. Just use the TWRP file and rename to recovery.img.
Sent from my HTC6435LVW using Tapatalk 4 Beta
I've done this a 100 times but for some reason I'm getting the error "error: cannot load 'recovery.img'".
What's going on?
I did the RevOne method yesterday.
Edit, it happened with both CWM and TWRP.
After the RevOne method, my phone says **UNLOCKED** and S-Off, however is it possible that I'm not Unlocked?
Edit 2, what's really weird is that last night, I used the "All-in-one Toolkit" to flash the TWRP recovery and it worked just fine. I'm actually in the TWRP recovery right now. And then once I rebooted from recovery, it did NOT ask me to root/install SU.
arozer said:
I've done this a 100 times but for some reason I'm getting the error "error: cannot load 'recovery.img'".
What's going on?
I did the RevOne method yesterday.
Edit, it happened with both CWM and TWRP.
After the RevOne method, my phone says **UNLOCKED** and S-Off, however is it possible that I'm not Unlocked?
Edit 2, what's really weird is that last night, I used the "All-in-one Toolkit" to flash the TWRP recovery and it worked just fine. I'm actually in the TWRP recovery right now. And then once I rebooted from recovery, it did NOT ask me to root/install SU.
Click to expand...
Click to collapse
Do you use Win7 or 8? By default it hides known file extensions. So if you renamed it to "recovery.img" it might actually be "recovery.img.img".
Also I believe the all in one kit installs the SU binaries for you... I wouldn't know as I don't use one clicks or kits.
Phaded said:
Do you use Win7 or 8? By default it hides known file extensions. So if you renamed it to "recovery.img" it might actually be "recovery.img.img".
Also I believe the all in one kit installs the SU binaries for you... I wouldn't know as I don't use one clicks or kits.
Click to expand...
Click to collapse
Wow!
Why didn't I think of this? (I guess the frustration from last night trying to figure out why RevOne wasn't working.)
Thank you. This worked!
Fixed broken link.
Does this method erase all data? Sorry, just got my DNA yesterday
It erases nothing
Phaded said:
It erases nothing
Click to expand...
Click to collapse
Thanks, I'm dumb. Didn't realise it needed S-Off first (of course) which (at least the methods i've found) require a wipe.
Recovery Worked Great!
Worked Great!
Thank you
Use Runrummer for s off does not wipe
miggy_2602 said:
Worked Great!
Thank you
Click to expand...
Click to collapse
nice write up, extremely useful for noob:laugh:
Ok I type in fastboot flash recovery recovery.img and it just says "waiting for device" Looking at my phone it says Tampered/Unlocked S-OFF. Am I missing something?
when I flash recovery through
fastboot flash recovery recovery.img
I get the attached error. Is something wrong ????
also attached bootloader screenshot
thanks
You're not s-off or unlocked...
Hi all. Before i start i want to say, i read a lot of threaths and comments before i started to booting recovery and i followed Tutorial that you can find somewhere here on XDA for MotoE.
I unlocked Bootloader correctly and everything was right. Then i downloaded latest version of TWRP and CWM if something will be wrong.
So i booted into bootloader, connected to PC (windows 8.1) and using adb i installed TWRP (by command window). After instalation was complete, i used comand: "fastboot reboot" to get my mobile start normally. Everything worked fine so i started last step. Turned off mobile, booted into bootloader(or maybe fastboot? idk...) and by volumebuttons i choosed "Recovery" . Then a black screen for a minute. After that mobile stuck on screen that i attached down below. So i tried this but with CWM (same process way). But nothing new... Someone said me i had to try "Minimal ADB and Fastboot" but again, nothing happend.
Can you help me guys?
The recovery isn't installed! Reinstall the recovery and follow correct steps!
I tried it one more time. I´m attaching image that is from command window showing that .img was booted ... Strange is, immediately after booting was completed, mobile restarted... and after i turned off mobile again, still i can´t reach recovery. Isn´t that problem in .img file? maybe it´s broken, isn´t it?
Tried once again
Ok last try didnt worked. So i complettly followed this guide http://forum.xda-developers.com/moto-e/general/guide-one-moto-e-beginners-guide-t2807891 STEP-BY STEP!
Command window screen attached, Fastboot screen attached.
After reboot, turn off i tried to open recovery and again that image that i posted in first coment. (android figure with words: no command)
By that guide i downloaded recovery from here: https://goo.im/devs/OpenRecovery/condor/
and i downloaded just "openrecovery-twrp-2.7.1.0-condor.img" as i have to do it (written in guide)
Well, your recovery is flashing fine from cmd but its not detected by your phone.
Try re-downloading the recovery and check md5 before flashing.
I'll look into it and see if the issue can be pinpointed.
Btw, you might need the flash the stock ROM back if nothing works.
Tapatalk with RAZR HD
neo.ank said:
Well, your recovery is flashing fine from cmd but its not detected by your phone.
Try re-downloading the recovery and check md5 before flashing.
I'll look into it and see if the issue can be pinpointed.
Btw, you might need the flash the stock ROM back if nothing works.
Tapatalk with RAZR HD
Click to expand...
Click to collapse
Ok i will re-download recovery, is that file that i downloaded ok? i mean should i dowload same file as before?
+ sorry for that but i completly dont know what the "md5" is. can you send me link from where i can learn what it is? you can explain that too but i dont want take your free time.
Mondop said:
Ok i will re-download recovery, is that file that i downloaded ok? i mean should i dowload same file as before?
+ sorry for that but i completly dont know what the "md5" is. can you send me link from where i can learn what it is? you can explain that too but i dont want take your free time.
Click to expand...
Click to collapse
Okay try this.
Flash CWM
If flashing fails or you get any error, then try booting into recovery.
Code:
fastboot boot recovery.img
If you boot into recovery, flash the SuperSU package.
Reboot and then flash the recovery.
See if it works.
neo.ank said:
Okay try this.
Flash CWM
If flashing fails or you get any error, then try booting into recovery.
Code:
fastboot boot recovery.img
If you boot into recovery, flash the SuperSU package.
Reboot and then flash the recovery.
See if it works.
Click to expand...
Click to collapse
no
flashed CWM from here http://forum.xda-developers.com/showthread.php?t=2793625
concretly from here http://www.mediafire.com/download/6odyyqgodw15f1b/recovery.img
then i flashed it, then i rebooted phone then i shuted it off (to boot into fastboot) in fastboot i selected recovery and again, that screen with android figure (no command) so i pressed power button for long. mobile rebooted. again i went into fastboot to write command you said me to boot into recovery. but i stucked at starting screen (that blue big M in "water" cycle)
this all means, files i downloaded was OK but my phone isnt :/
any idea :/
Mondop said:
no
flashed CWM from here http://forum.xda-developers.com/showthread.php?t=2793625
concretly from here http://www.mediafire.com/download/6odyyqgodw15f1b/recovery.img
then i flashed it, then i rebooted phone then i shuted it off (to boot into fastboot) in fastboot i selected recovery and again, that screen with android figure (no command) so i pressed power button for long. mobile rebooted. again i went into fastboot to write command you said me to boot into recovery. but i stucked at starting screen (that blue big M in "water" cycle)
this all means, files i downloaded was OK but my phone isnt :/
any idea :/
Click to expand...
Click to collapse
Do not flash CWM, just boot into it by the command I posted above.
Then try and flash SuperSU, (if you get a root prompt from CWM, select NO.)
Reboot device.
Then again boot into fastboot and now flash recovery (twrp).
neo.ank said:
Do not flash CWM, just boot into it by the command I posted above.
Then try and flash SuperSU, (if you get a root prompt from CWM, select NO.)
Reboot device.
Then again boot into fastboot and now flash recovery (twrp).
Click to expand...
Click to collapse
so now what if i flashed that CWM before?
Now i tried go to fastboot and used just command that you said(to boot into recovery) and as i said, i stucked on motorola starting logo
+ you said i have to flash cwm
Mondop said:
so now what if i flashed that CWM before?
Now i tried go to fastboot and used just command that you said(to boot into recovery) and as i said, i stucked on motorola starting logo
+ you said i have to flash cwm
Click to expand...
Click to collapse
I said if flash is not successful, then boot into it. So you can't boot into recovery either.
Here's last resort, extract the stock recovery from stock ROM and flash it. Then we'll try flashing TWRP again.
If you don't have stock ROM, download it. as you might need it to recover.
neo.ank said:
I said if flash is not successful, then boot into it. So you can't boot into recovery either.
Here's last resort, extract the stock recovery from stock ROM and flash it. Then we'll try flashing TWRP again.
If you don't have stock ROM, download it. as you might need it to recover.
Click to expand...
Click to collapse
Okay, can you give me link with tutorial? i found just this one which restores whole system (and its 4.4.3 and i have now 4.4.4, i mean this will be maybe problem, wouldn´t it?)
i mean this one (tutorial how to restore moto E)
http://forum.xda-developers.com/showthread.php?t=2759495
did you try updating / reinstalling USB-driver on your computer?
magicw said:
did you try updating / reinstalling USB-driver on your computer?
Click to expand...
Click to collapse
no i didnt, think you it will help? i mean if i can connect my mobile into pc without any problem in normal mode and in fastboot too... i will unninstal drivers, intall them again and them i will try unninstal motorola device manager and then again intall him.
(i had newest drivers i can update them)
LOL?
OK im in recovery i already flashed superSU...
What did i do?
As you said, i reinstalled all drivers...
then i downloaded same TWRP again (but with mirror source)
I downloaded attached md5 file ( still dont know what should i do with it )
moved recovery and .md5 files into minimal adb and fastboot (both files i renamed to "recovery")
turned off devices
started fastboot
connected to PC
started command window and entered command "fastboot flash recovery recovery.img"
then i didnt wrote sommand "fastboot reboot" as i done before
i just unpluged usb and navigate to recovery button and launched it
and VUALA im in recovery
hurraaa
just installed superSU and then rebooted.
everything works (superSU too)
i have one more question...
i downloaded twrp manager from google play
first start: asked for root permission a allowed it
then message appeard:
"The only compatible version of busybox we support is Stericson. All other cause havoc on all operations in this app. Please click yes to install Stericson busybox"
what the heck is busybox?
+Should i download it or not?
Do not use TWRP Manager, ROM Manager, CWM Manager or any other of these Tools. They often do not really work good together with "exotic" fones. Why the heck do you need TWRP manager? You have TWRP installed
Anyway - Busybox you also can download and install from Playstore. Busybox is a collection of executable terminal commands helpful for any kind of script. There are a couple of rooted apps who will ask for busybox support - so don't hesitate to install busybox - but do it directly with busybox app from playstore.
After you have installed the binaries you can de-install the busybox-app. Because all necessary binaries then are copied into /system/bin/ folder and the app itself only will become active once a new version would be available (but this is not the case very often).
ok then
magicw said:
Do not use TWRP Manager, ROM Manager, CWM Manager or any other of these Tools. They often do not really work good together with "exotic" fones. Why the heck do you need TWRP manager? You have TWRP installed
Anyway - Busybox you also can download and install from Playstore. Busybox is a collection of executable terminal commands helpful for any kind of script. There are a couple of rooted apps who will ask for busybox support - so don't hesitate to install busybox - but do it directly with busybox app from playstore.
After you have installed the binaries you can de-install the busybox-app. Because all necessary binaries then are copied into /system/bin/ folder and the app itself only will become active once a new version would be available (but this is not the case very often).
Click to expand...
Click to collapse
i have no reason to want twrp manager, i just wanted to look at this app, and i found that busybox there so i wanted to ask here
thx for answer, now i undertand