Hi there,
Currently my phone has no ROM and a disfunctioning ClockworkMod Recovery. (It cannot install zips or take updates).
Therefore I'm using ADB to flash a new recovery and ROM into the phone.
Code:
mount data
Results in:
Code:
mount: can't find /etc/fstab: No such file or directory
So I copied my file into the /data/ folder with
Code:
adb push c:\rom.zip /data/
This was done successful.
After that I tried to install the rom.zip using
Code:
adb shell
recovery --update_package=DATA:rom.zip
Unfortunately this results in:
Code:
sh: /sbin/postrecoveryboot.sh: not found
Also tried to replace the recovery.img but this also resulted in:
Code:
sh: /sbin/postrecoveryboot.sh: not found
In short:
Can't mount USB in ClockWorkMod
Can't access phone files with Windows Explorer
Can't use Kies to recover phone.
Can't use ClockWorkMod to install a zip or update.
Can't do normal boot.
Can't mount data using ADB.
Can't install recovery ROM using ADB.
I can't think of any way to fix this, hope someone else can help me with this.
Simple Use Odin
Sent from my GT-I9100 using XDA
Can you get in to Download mode?
As the 2 people stated above:
If you are able to get into the download mode, then you should be able to install a stock rom via Odin.
Have a good day and good luck with your phone.
Sorry to mention. The first thing I tried was Odin, but I'm not able to get into download mode.
Magiciano said:
Sorry to mention. The first thing I tried was Odin, but I'm not able to get into download mode.
Click to expand...
Click to collapse
what happens when you try and get into download mode? is it just blank? when you plug it in to charge do you get the battery charging animation?
nutmegy said:
what happens when you try and get into download mode? is it just blank? when you plug it in to charge do you get the battery charging animation?
Click to expand...
Click to collapse
The download mode button combination has no effect, it won't even try to load.
I get a frozen image of a empty battery with the spinning wheel inside, the battery is more than half full tho.
Magiciano said:
Sorry to mention. The first thing I tried was Odin, but I'm not able to get into download mode.
Click to expand...
Click to collapse
USB recovery jig would be the next step before it all becomes expensive .
jje
I would say try using a USB jig to get into download mode. If that doesn't work, I think the only thing left to do would be to take it to Samsung.
Edit: Damn, I never saw JJE's post above. Sorry.
Jtag might be cheaper than taking it to samsung
Sent from my sgs2 running cm9 using xda app
Sounds annoying..
Tryed this?
http://forum.xda-developers.com/showthread.php?t=1449771
fastboot erase cache ( if failed ignore it)
fastboot oem rebootRUU ( not shure if RUU is htc dependent or not )
fastboot flash zip your_recover.zip
fastboot reboot-bootloader
it's worked for me, its basically change your recovery, so you can install a properly working clockwork
I've found my friend's sgs2 last few days ago as yours..
Couldn't go 2 download mode w/ buttons combination
..
Randomly as a noob (sorry4that.. ) I tried adb shell :
adb reboot download
N it worked ready2 next step flashing progress via Odin 1.85 (just try this ver!)
If yours don't: try USB Jig neither to JTaG or SSC @ last opt
Hope this may help & sorry about 'tittles'
Related
Hey guys.
I am assuming my phone is not "bricked" because I can still get to the clockworkmod interface and mount usb and things like that, but I cant get any roms to load. I followed all the instructions and multiple videos to make sure I did my 1.5 right. Seems to be find as far as root. When I logged in to my old backup i had superuser and all.
I tried to install the WARM rom, but didnt work, so i restored my backup and bought Flash Image GUI which then I loaded the WARM zip and it said it found the Kernel and went to install it. It then asked me to reboot, which I did, and then proceeded to install the rest of the ROM via clockwork install ZIP, after doing that I can no longer even restore my backup.
If i try to load WARM, it just sits at white HTC screen and never changes. If I try to load MIUI, it loads to HTC screen, makes a sound and then goes black forever with backlight on but black and buttons lit.
That is all I can currently do. My backup no longer loads or works.
Is my phone bricked? I dont think so since I can get to clockworkmod, but what can I do to try to get it back up and running?
Thanks,
M374llic4.
Your kernel is most likely the problem. When using the the flash image GUI, dont accept when it asks you to reboot, manually hold down the power button and reboot yourself. Hook up your phone to the computer and boot into fastboot usb and fastboot boot recovery.img then install the warm rom. This will ensure you have access to flash the kernel.
JayDaKissEP said:
Your kernel is most likely the problem. When using the the flash image GUI, dont accept when it asks you to reboot, manually hold down the power button and reboot yourself. Hook up your phone to the computer and boot into fastboot usb and fastboot boot recovery.img then install the warm rom. This will ensure you have access to flash the kernel.
Click to expand...
Click to collapse
Hey man, I am following most of what you said, but when yo said boot in to fastboot usb, I know how to do that, but how do i fastboot recovery.img, where is that?
m374llic4 said:
Hey man, I am following most of what you said, but when yo said boot in to fastboot usb, I know how to do that, but how do i fastboot recovery.img, where is that?
Click to expand...
Click to collapse
A friend kinda having a similiar issue with this.. but I tried this all on his computer and not sure if it's driver issues or not.. but I can't get adb to communicate with this phone.. when I use " adb device's " it doesn't show up.. but If i plug my phone it - it picks it up.. Same issue as the guy above it seems.. but when I go into the boot loader - click fastboot and it picks up the usb.. i still can't get them to talk.. any idea's?
m374llic4 said:
Hey man, I am following most of what you said, but when yo said boot in to fastboot usb, I know how to do that, but how do i fastboot recovery.img, where is that?
Click to expand...
Click to collapse
When you rooted your phone, you should have downloaded a folder called newevo3droot or something like that. There's adb files, fastboot..etc and this is how you would have flashed clockworl recovery. Since you are on hboot 1.5, you need to go into fastboot and connect usb so that it says fastboot-usb, then you need to run the command fastboot boot recovery.img. Recovery.img is the name of the recovery image file in that folder. I think it's something like cwm******.img
I did download that, and had some help from someone in the IRC channel and he got me back up up and running! Turns out you have to use USB fastboot on the phone along with fastboot.exe via cmd prompt on the pc with the CWM.exe to load the kernel, then once you do that, you use the phone cwm load from zip to load the rest of the rom and you are good to go!
JayDaKissEP said:
When you rooted your phone, you should have downloaded a folder called newevo3droot or something like that. There's adb files, fastboot..etc and this is how you would have flashed clockworl recovery. Since you are on hboot 1.5, you need to go into fastboot and connect usb so that it says fastboot-usb, then you need to run the command fastboot boot recovery.img. Recovery.img is the name of the recovery image file in that folder. I think it's something like cwm******.img
Click to expand...
Click to collapse
Yeah, thats what I did with some help from a fellow XDA member via IRC and it worked perfect! I was trying to do it all via the CWM on the phone side only, not via command prompt which was my issue.
Well, I have to ask for help right here because Goole/Yahoo/Wiki DIDN'T help. Although it's a bit long but please read it
Here's my problem:
At the last time that my phone is still being functional, I was playing the game "Contract Killer" and "Facebook", "Internet" were running in the background.
Suddenly, it shut off with showing "power off...(Sth like that). This is obviously a normal situation when the battery is out of power. I took it to charge as usual and went to sleep.
Next day, I waked up and tried to boot up my HTC EVO 3D...
First time: Stuck in the startup screen without playing the HTC opening sound track( The phone used to be in Silent Mode)
Second time: I pulled out the battery and put it back and boot again. Still stuck in the startup screen but this time it play the HTC opening sound track...
I've got a lot data in the internal memory and I've never BACKUP before.....
Is there anyway that can boot up my phone without losing the data???
Oh...my phone has never been rooted.
Anyone know the problem??? (
I dunno, kinda sounds like a Hard Reset/Factory Reset is in order. Did you take the battery out for a while and then try to reboot?
There's no way unless u can take to service provider an have them extract it
Sent from my PG86100 using XDA App
i had that kind of a problem once but i was on a CUSTOM ROM so i'm not sure it will work for you and I'M NOT SAYING this method is THE SAFEST.
so 1st thing i did was.. i panic'd... 2nd, i started googling and when all the signs pointed me to a boot up problem i opened the zipped rom, i extracted the boot.img, connected the phone to the pc in fastboot mode and flashed the boot image. after that it started with no problems, all my data was there. what do anyone else suggest? would it be okay to flash boot.img (stock one) on a stock rom?
I would suggest the following:
If rooted with custom recovery:
1. Pull out the battery
2. Replace the battery, and access recovery and do nandroid backup, you will only need the user data.
3. wipe, wipe, wipe
4. install the ROM you had and let it boot
5. reboot in to recovery and restore you DATA ONLY
If not rooted:
1. Install custom recovery
2. go to rooted instructions
IF this doesn't work you can get the .img files from the forums of the ROM you had or stock if that was what you had and only install the boot.img and system.img and try to see if you get the phone to boot with your data in there.
let me know if anything helps.
PS. There is a great risk that you won't be able to recovery your apps data but lets try and hope for the best.
This sounds like a battery, cable, or AC adapter problem to me. You can get a cheap replacement battery on eBay for a few bucks and see how that works out. Also try different wall pieces, micro USB cables, and power outlets.
If none of that has worked, then you more than likely have a corrupted boot image. You can mount the EMMC (internal flash storage) onto a Linux distribution (like Ubuntu or Fedora) via usb and copy your data to a safe place like a flash drive or HDD. Then do an RUU (there are tutorials on this in the development thread) to restore the phone to stock, then of course pull whatever is needed from the data you saved.
Now if absolutely none of this has worked at all, you have malfunctioning hardware. Your only option at this point is to go to a Sprint store to have your data transferred over to a new replacement phone.
Hope this helped mate.
Sent from a Shooter running Android 4.0.3 via XDA Premium.
megabiteg said:
I would suggest the following:
If rooted with custom recovery:
1. Pull out the battery
2. Replace the battery, and access recovery and do nandroid backup, you will only need the user data.
3. wipe, wipe, wipe
4. install the ROM you had and let it boot
5. reboot in to recovery and restore you DATA ONLY
If not rooted:
1. Install custom recovery
2. go to rooted instructions
IF this doesn't work you can get the .img files from the forums of the ROM you had or stock if that was what you had and only install the boot.img and system.img and try to see if you get the phone to boot with your data in there.
let me know if anything helps.
PS. There is a great risk that you won't be able to recovery your apps data but lets try and hope for the best.
Click to expand...
Click to collapse
First of all, thanks for helping~ I would like to know that will my data lose if install the custom recovery? Seems like a huge risk...
Besides, I am a little confused about using the .img to boot my phone.......
MikeyCriggz said:
This sounds like a battery, cable, or AC adapter problem to me. You can get a cheap replacement battery on eBay for a few bucks and see how that works out. Also try different wall pieces, micro USB cables, and power outlets.
If none of that has worked, then you more than likely have a corrupted boot image. You can mount the EMMC (internal flash storage) onto a Linux distribution (like Ubuntu or Fedora) via usb and copy your data to a safe place like a flash drive or HDD. Then do an RUU (there are tutorials on this in the development thread) to restore the phone to stock, then of course pull whatever is needed from the data you saved.
Hope this helped mate.
Sent from a Shooter running Android 4.0.3 via XDA Premium.
Click to expand...
Click to collapse
I was once using Nokia N900, and it is very easy to flash the rom meanwhile i can keep everything in the emmc remain unchanged! Since ANDROID is based on Linux, I am sure your way will be damn work! Any software or environment would i need to do these stuffs? Thx at all!!
:
All in all, I do care the messages in the phone only. That is what i really want.
Nokiawithandroid said:
All in all, I do care the messages in the phone only. That is what i really want.
Click to expand...
Click to collapse
Well if you can somehow get ADB access to your phone you can try to backup the following file:
/data/data/com.android.providers.telephony/databases/mmssms.db
This is there database that contains all your messages (SMS / MMS).
Flashing the boot.img file is easy, if you have the phone in fastboot (and it indicates the usb connection on the phone too) then you can just flash this way:
fastboot flash boot [location of boot.img]\boot.img
You will not loose any personal data, there that the partition affected by the boot.img is not the same as the one affected by /data. This also apply to the recovery section of the phone, in case you want to load a custom recovery:
fastboot flash recovery [location of recovery.img]\recovery.img
Hope this helps, if you need any more help let us know.
HELLO?
megabiteg said:
Well if you can somehow get ADB access to your phone you can try to backup the following file:
/data/data/com.android.providers.telephony/databases/mmssms.db
This is there database that contains all your messages (SMS / MMS).
Flashing the boot.img file is easy, if you have the phone in fastboot (and it indicates the usb connection on the phone too) then you can just flash this way:
fastboot flash boot [location of boot.img]\boot.img
You will not loose any personal data, there that the partition affected by the boot.img is not the same as the one affected by /data. This also apply to the recovery section of the phone, in case you want to load a custom recovery:
fastboot flash recovery [location of recovery.img]\recovery.img
Hope this helps, if you need any more help let us know.
Click to expand...
Click to collapse
How can i get to access my phone by ADB?
I am totally new for all these...
Nokiawithandroid said:
How can i get to access my phone by ADB?
I am totally new for all these...
Click to expand...
Click to collapse
This can get you acquainted with ADB
http://forum.xda-developers.com/showthread.php?t=1241935
Props to Droidzone for putting it all together.
If not rooted:
1. Install custom recovery
2. go to rooted instructions
IF this doesn't work you can get the .img files from the forums of the ROM you had or stock if that was what you had and only install the boot.img and system.img and try to see if you get the phone to boot with your data in there.
Can i do the above things while i can't get connect USB with my phone - -?
Nokiawithandroid said:
If not rooted:
1. Install custom recovery
2. go to rooted instructions
IF this doesn't work you can get the .img files from the forums of the ROM you had or stock if that was what you had and only install the boot.img and system.img and try to see if you get the phone to boot with your data in there.
Can i do the above things while i can't get connect USB with my phone - -?
Click to expand...
Click to collapse
If you remove the battery off your phone and then you reinsert it back, press PWR+Vol UP to access the bootloader.
While in the Bootloader access fastboot and ensure to have the USB connected. from there, you can run any fastboot command you need, like loading custom recoveries or anything else.
WOW! I am approaching the target. To be clear, fastboot command stands for using ADB access?
AND:"While in the Bootloader access fastboot and ensure to have the USB connected. from there, you can run any fastboot command you need, like loading custom recoveries or anything else." means my phone can connect the computer by using "press PWR+Vol UP to access the bootloader"??? The bloody bootoader??
I am sure i'm almost there!!!!! THANKSSWSSSS
Nokiawithandroid said:
WOW! I am approaching the target. To be clear, fastboot command stands for using ADB access?
AND:"While in the Bootloader access fastboot and ensure to have the USB connected. from there, you can run any fastboot command you need, like loading custom recoveries or anything else." means my phone can connect the computer by using "press PWR+Vol UP to access the bootloader"??? The bloody bootoader??
I am sure i'm almost there!!!!! THANKSSWSSSS
Click to expand...
Click to collapse
Fastboot is a different command center from it counterpart adb. From fastboot you use only commands related to the flashing img files and more.
Just use fastboot /? From the command prompt to see a quick help of all what fastboot can do for you, but the main thing you'll need from this command is the ability yo flash a new boot, and maybe system image to get your phone back up and running.
Sent from my PG86100 using Tapatalk
megabiteg said:
Fastboot is a different command center from it counterpart adb. From fastboot you use only commands related to the flashing img files and more.
Just use fastboot /? From the command prompt to see a quick help of all what fastboot can do for you, but the main thing you'll need from this command is the ability yo flash a new boot, and maybe system image to get your phone back up and running.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
Oh..damn.....the voyage is lengthy
What equipment/environment do i need?
My target: 1)Back up the Message Database 2) Run this bloody phone.
Difficulties: 1)S-ON 2)command 3) environment 4) Flashing a new (boot?image?)
megabiteg said:
Fastboot is a different command center from it counterpart adb. From fastboot you use only commands related to the flashing img files and more.
Just use fastboot /? From the command prompt to see a quick help of all what fastboot can do for you, but the main thing you'll need from this command is the ability yo flash a new boot, and maybe system image to get your phone back up and running.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
Any thread for that?
So I dont have my nanadroid backup...thats not my concern because i can just flash the stock rom...but anyways i dont have an os installed i have twrp recovery...im tryin to adb sideload the rom.zip so i can then flash the rom. Could someone please enlighten me how to do this or a detailed tutorial ive searched but im having no luck thanks in advance!!!
2phonejones said:
So I dont have my nanadroid backup...thats not my concern because i can just flash the stock rom...but anyways i dont have an os installed i have twrp recovery...im tryin to adb sideload the rom.zip so i can then flash the rom. Could someone please enlighten me how to do this or a detailed tutorial ive searched but im having no luck thanks in advance!!!
Click to expand...
Click to collapse
If never gotten sideload to work, but you can try adb push. this is where I learned it http://forum.xda-developers.com/showthread.php?t=1667929
joshyy_rey said:
If never gotten sideload to work, but you can try adb push. this is where I learned it http://forum.xda-developers.com/showthread.php?t=1667929
Click to expand...
Click to collapse
It working as far as connecting to fastboot but when i goto recovery like the tutorial states and then goto mount and run the commands it doesnt push the file even though it says device is being read.
joshyy_rey said:
If never gotten sideload to work, but you can try adb push. this is where I learned it http://forum.xda-developers.com/showthread.php?t=1667929
Click to expand...
Click to collapse
Im using twrp btw idk if that is the issue but if so do you know how i can flash the cwm recovery or is that not possible urrghhh im so close i just have to get this adb to push the file!
if you have an OTG cable you can load from a USB stick..Just mount OTG
2phonejones said:
Im using twrp btw idk if that is the issue but if so do you know how i can flash the cwm recovery or is that not possible urrghhh im so close i just have to get this adb to push the file!
Click to expand...
Click to collapse
You can flash cwm through adb. Adb might be buggy through recovery it was at first. I'd post on the twrp thread to see if a someone has an idea
Sent from my HTC One using xda premium
I had this problem myself today and started freaking out. After a brief 15 second panic attack I realized I could side load. I have twrp and sideloaded very easily.
I used the all in on toolkit listed in the android dev section and cleanrom 1.5. I put cleanrom on my desktop and renamed it to Rom.zip. I started the aio tool which has a button for sideloading a Rom. Boot the phone into recovery and plug it into your pc. (I am assuming you have the HTC drivers installed) From TWRP click on advance and the adb sideload. Then click the side load button on the aio tool. This will attempt to reboot your phone first but since you're already there just close the command prompt that comes up. A new window will come up for you to chose the zip. Navigate to your desktop and pick the zip you put on the desktop (longer paths seem to cause issue with sideloading). Then it will push the zip to your phone. The command prompt on your pc will have a percentage progress. Once done just flash that zip like normal.
I had to reboot my phone using the volume down power button method before I could get back to twrp and the install froze once in Aroma. But I just flashed it again and it worked. Once I got it back I just put my backup back on the phone, booted back to twrp, and restored my backup.
Sorry if this seems unorganized, had two toddlers crawling all over me while. typing. Using the AIO should work
AIO found herehttp://forum.xda-developers.com/showthread.php?t=2242635
Sent from my HTC One using xda app-developers app
I was trying to create more space. I saw the apps folder and moved it to somewhere else. Then my phone started crashing, so i turned it off. When i turned it back on i got a bootloop. My phone is rooted and i have an alacatel one touch 983. It keeps showing the o2 logo. I think this is because there is no launcher. Help please
If you have adb set up then pull the app folder from where you put it and push it to system/app. I presume you don't have a custom recovery or nandroid backup.
sinkster said:
If you have adb set up then pull the app folder from where you put it and push it to system/app. I presume you don't have a custom recovery or nandroid backup.
Click to expand...
Click to collapse
I think i put it in custect (or a something like that) but not sure, can i just push a folder called app and then add the launcher?
Bump - Please help. CMD says error: device not found, but i have sdk. Im trying to change the driver but it keeps saying its up to date.
If you're not sure where you put the folder then using adb could be pretty tedious anyway... You'd need the whole file, the bootloop probably won't be caused solely by having no launcher. If you've got a custom recovery then flash the Aroma file manager to find/move the folder, or find a CWM/TWRP flashable home launcher. If not, then your best bet is probably to use One touch support to update your rom, i,e, reflash back to stock.
sinkster said:
If you're not sure where you put the folder then using adb could be pretty tedious anyway... You'd need the whole file, the bootloop probably won't be caused solely by having no launcher. If you've got a custom recovery then flash the Aroma file manager to find/move the folder, or find a CWM/TWRP flashable home launcher. If not, then your best bet is probably to use One touch support to update your rom, i,e, reflash back to stock.
Click to expand...
Click to collapse
Well, i have a system.img that i want to flash with fastboot. i also found an o2 rom for my phone. So if i could get adb or recovery mode to work i could restore it. I have a rough idea of where it is, so i could get it, but adb and fastboot don't recognise my device. I tried hard resetting it by holding the volume up button but im still stuck at the o2 screen. I have tried the alcatel driver but that doesn't work. It doesn't recognise it when i try to put it into recovery mode. If you know the combination for the alcatel 983 please say. Maybe it is because hard resetting it disabled usb debugging, but my pc recognises it fine. (cannot open sd card), but it recognises it and it's name. So i do not know why adb doesn't recognise it.
I'm not familiar with Alcatel phones, but it should be volume down while turning on for fastboot. If you can get into fastboot you should be able to flash a custom recovery.
sinkster said:
I'm not familiar with Alcatel phones, but it should be volume down while turning on for fastboot. If you can get into fastboot you should be able to flash a custom recovery.
Click to expand...
Click to collapse
Holding up while turning on makes it to hard reset and holding down does makes it freeze. So how can i make it work with adb on my pc. Should i try a different pc? There are no other buttons, it is touch screen.
Actually holding down while it says waiting for device works, testing some stuff out now thanks. will show my resuslts
When you switch on/press down, the freeze is the phone in fastboot (apparently), so try that, connect to your pc, open cmd window where you'd normally open adb and try 'fastboot erase cache' and see if you get a response. should return a message saying cache erased, or similar. If so, you're in fastboot and you can use it to flash a custom recovery (obviously one for your phone)
This post seems to be a similar issue/resolution. There's no custom recovery yet for the phone.
sinkster said:
When you switch on/press down, the freeze is the phone in fastboot (apparently), so try that, connect to your pc, open cmd window where you'd normally open adb and try 'fastboot erase cache' and see if you get a response. should return a message saying cache erased, or similar. If so, you're in fastboot and you can use it to flash a custom recovery (obviously one for your phone)
Click to expand...
Click to collapse
ok ill try thanks.
Well i done that, but now it is frozen at the o2 screen. I flashed boot, recovery and system img. Lower buttons work but its stuck at o2 screen. What do i do next?
Can you connect with adb yet?
sinkster said:
Can you connect with adb yet?
Click to expand...
Click to collapse
Nope still no adb, still saying device not found. Is there an adb mode that i can get to?
Adb needs the system to respond, out may be borked due to the move of the system/app folder. What commands did you use in fastboot? Fastboot flash system xxx.img?
sinkster said:
Adb needs the system to respond, out may be borked due to the move of the system/app folder. What commands did you use in fastboot? Fastboot flash system xxx.img?
Click to expand...
Click to collapse
Yes i did fastboot flash system/boot/recovery for each their img's. Well i am trying the alcatel one touch update now. Ill see if that fixes it. Ill report back when its done
ok, good luck.
sinkster said:
ok, good luck.
Click to expand...
Click to collapse
Well, that didn't work. Got any other tips? Im still stuck at o2 screen. Thanks
supernovakid said:
Well, that didn't work. Got any other tips? Im still stuck at o2 screen. Thanks
Click to expand...
Click to collapse
It has worked, thanks a lot for your help! You are a great person thanks!
No probs.
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