Related
I have really been trying to research this on the forums...but can't really find the answers, at least not in the dumbed down version I seem to require.
I have my rezound unlocked, and rooted using zerg. I don't have a "recovery", I don't think anyway..and I can't install one, or any roms...which I really want to do.
My main problem right now is when I boot into recovery, I get to the red exclamation point, hit volume up and power, I get the message: E: Can't open/ cache/ recovery/ command...... Then when I navigate to install zip from sd card, and try to select it with the power button, I get the messages: Invalid operations. Success rebooting by reason oem-00....
I am really anxious to get this device set up the way I want it, I'm VERY excited by the potential for customization....that's the biggest reason I got it..and I will REALLY appreciate any help I can get! Thanks in advance! Scott
Con247 has a guide in the development section. I'm using the Amon Ra recovery which seems to be the only stable one right now. CWM seems to be a little quirky right now. Srosler has some good tools to use and clean rom is sense but with vz bloat removed. There are several other good ones from Nils, BAMF and others. Good luck.
sent from either NC running CM9 or Rez on Clean 1.5
I appreciate it sout....my problem now is I can't install amon ra...or anything else for that matter...because of my issues in recovery mode.
3oclockslop said:
I appreciate it sout....my problem now is I can't install amon ra...or anything else for that matter...because of my issues in recovery mode.
Click to expand...
Click to collapse
u need to install a recovery to so u can go into recover mode the most stable one i amon ra..after that is install then you be able to install roms..jus pm me ill i go thru the steps with u
Naisaelee21 said:
u need to install a recovery to so u can go into recover mode the most stable one i amon ra..after that is install then you be able to install roms..jus pm me ill i go thru the steps with u
Click to expand...
Click to collapse
How do you install the custom recovery image if i have S-on and get the same reboot by oem-00 message? i tried flashing back using H-boot and get a "Main Version is older!" message when running the update to flash back to stock n i cant boot up? i can use adb but it doesnt recognize device?!? Plz help =( i tried to reboot oem with adb and i just get .... then it sits forever till i unplug it and it says read failure wtf?!? Im not a complete idiot so what am i not seeing here?
IVXX said:
How do you install the custom recovery image if i have S-on and get the same reboot by oem-00 message? i tried flashing back using H-boot and get a "Main Version is older!" message when running the update to flash back to stock n i cant boot up? i can use adb but it doesnt recognize device?!? Plz help =( i tried to reboot oem with adb and i just get .... then it sits forever till i unplug it and it says read failure wtf?!? Im not a complete idiot so what am i not seeing here?
Click to expand...
Click to collapse
Have you put a custom recovery on this phone before? You say you are trying to flash back to stock so it sounds like you have flashed a ROM? And your message about "Main Version is older" makes me think you may have updated your mainver.... did you play with the ICS leak?
If you did try out the ICS leak check out this post for help:
http://forum.xda-developers.com/showpost.php?p=21442702&postcount=3
Its actually a friends so i dont know what happened exactly that messed it up but heres what i get when i boot into recovery,
E:Can't open /cache/recovery/command
E:set_bootloader_message_block: emmc_read_data_fail!
E:Can't mount /data/data/recovery/log
E:Can't open /data/data/recovery/log
E:set_bootloader_message_block: emmc_read_data_fail!
if i try to run anything from recovery i always get,
E:Can't mount /data/data/recovery/HTCFOTA/update_result.log
E:Can't mount /data/data/recovery/OMADM/update_result.log
E:Can't mount /data/data/recovery/log
E:Can't open /data/data/recovery/log
E:set_bootloader_message_block: emmc_read_data fail!
so i assume she had a bad update but im stumped for a way to fix it
Download Amon ra and place it on the root of your SD card. Power off the phone, remove the battery, and then replace the battery. After this is done, hold volume down and power until you boot in to fastboot. After that, it should install Amon Ra automatically.
htcdesirezgeorge said:
Download Amon ra and place it on the root of your SD card. Power off the phone, remove the battery, and then replace the battery. After this is done, hold volume down and power until you boot in to fastboot. After that, it should install Amon Ra automatically.
Click to expand...
Click to collapse
This.
Alternate directions.
Unzip the boot.img file. Reboot the phone using "adb reboot bootloader". Once in fastboot run "fastboot flash recovery recovery.img" then "fastboot reboot" and you're all done.
MrSmith317 said:
This.
Alternate directions.
Unzip the boot.img file. Reboot the phone using "adb reboot bootloader". Once in fastboot run "fastboot flash boot boot.img" then "fastboot reboot" and you're all done.
Click to expand...
Click to collapse
C:\AndroidSDK\tools\fastboot flash boot boot.img
error: cannot load 'boot.img'
I placed it on the root of my SD and and in C:\AndroidSDK\tools folder so why wont it load?
MrSmith317 said:
This.
Alternate directions.
Unzip the boot.img file. Reboot the phone using "adb reboot bootloader". Once in fastboot run "fastboot flash boot boot.img" then "fastboot reboot" and you're all done.
Click to expand...
Click to collapse
C:\AndroidSDK\tools\fastboot flash boot C:\AndroidSDK\tools\boot.
img
sending 'boot' (2560 KB)...
OKAY [ 0.436s]
writing 'boot'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.760s
IVXX said:
C:\AndroidSDK\tools\fastboot flash boot C:\AndroidSDK\tools\boot.
img
sending 'boot' (2560 KB)...
OKAY [ 0.436s]
writing 'boot'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.760s
Click to expand...
Click to collapse
That's my fault.. one too many kernel flashes. fastboot flash recovery <whatever recovery file>.img .
IVXX said:
C:\AndroidSDK\tools\fastboot flash boot boot.img
error: cannot load 'boot.img'
I placed it on the root of my SD and and in C:\AndroidSDK\tools folder so why wont it load?
Click to expand...
Click to collapse
You need to put the exact name of the Amon Ra recovery image in the line and it should be fastboot flash recovery "name of recovery.img" at least that's how I have flashed recovery and I have flashed the last 3 versions.
Oh , you don't place it at the root of the SD just in the same folder as fastboot unless you have a path in variables to use abd from anywhere.
I get the same signature verificationfailed message no matter what I seem to do ={ if I had the proper androidinfo.txt file could I run an update through fastboot without the signature failing? If so where can I get that info I tried to get the Cid but I got another error in fastboot.
Sent from my ADR6300 using XDA Premium App
OK so I got the phone to get passed the signature verification and got this message in recovery.
--Install /sdcard ...
E:set_boot loader_message_block: emmc_read_data fail!
Finding update package...
Opening update package...
Verifying update package...
Installing update...
file_getprop: failed to stat "/system/build.prop": No such file or directory
E:Error in /temp/sideload/package.zip
(Status 7)
Installation aborted.
E:Can't mount /data/data/recovery/HTCFOTA/update_result.log
E:Can't mount /data/data/recovery/OMADM/update_result.log
E:Can't mount /data/data/recovery/log
E:Can't open /data/data/recovery/log
E:set_bootloader_message_block: emmc_read_data fail!
Any thoughts how to properly correct this??
Sent from my ADR6300 using XDA Premium App
TWRP Recovery 2.3.0
~~~LazyPanda~~~
JEWEL PVT SHIP S-OFF RL
CID-SPCS_001
HBOOT-1.12.1111
RADIO-1.05.11.0606
OpenDSP-v25.1.0.32.0405
eMMC-boot
Apr 26 2012, 19:54:01
Error when I try to install ROM:
E:Error in /sdcard/MeanROM-ICS-v48-jewel-ltevo.zip
(Status 1)
Error flashin zip '/sdcard/MeanROM-ICS-v48-jewel-ltevo.zip'
Updating partition details...
E:Unable to mount '/data'
How do I get past this? Thank you!
There's an issue with the 2.3, try to downgrade to 2.2 and see if that works
TWRP 2.2.2.0
Thank you for the response, talk to me like a 2yr old - how do I downgrade at this point? All I can do right now is boot into recovery.
Thanks!
Assuming you don't have adb tools which you probably do have but humor me.
ADB Tools
Download and extract anywhere
Open folder and holding shift, right click
Select open command window here
Connect the phone to pc and make sure it says fastboot usb
In the terminal type fastboot devices to make sure
Type fastboot flash recovery openrecovery-twrp-2.2.2.0-jewel.img
Reboot phone (bootloader)
Select recovery
Wipe phone and flash rom
Here's what I get:
C:\Temp\HTC4GLTE_Root\ADB_TOOLS>fastboot flash recovery openrecovery-twrp-2.2.2.
0-jewel.img
sending 'recovery' (7356 KB)...
OKAY [ 1.076s]
writing 'recovery'...
FAILED (remote: partition is not allowed to be flushed!)
finished. total time: 1.123s
C:\Temp\HTC4GLTE_Root\ADB_TOOLS>
Thank you!
Ok, that's a new one for me, I see the path is in temp folder? Where did you unzip to?
Ah crud Any other ideas? Is there a bigger hammer?
I extracted it into that C:\Temp\HTC4GLTE_Root\ADB_TOOLS folder
The 5 minute NOOB post limitation is killing me
Thinking but I can't seem to come up with any solutions right now, sorry
Your S-off, why don't you use the PG75IMG.zip of the twrp 2.2.2. Put it on the root of your external sd card and boot into the bootloader let it install. After it installs, you have to remove the file from your sd card or it will keep on installing everytime you enter the bootloader. Here is the link to download it:
http://techerrata.com/file/twrp2/jewel/PJ75IMG-twrp-2.2.2.0-jewel.zip
TWRP website: http://www.teamw.in/project/twrp2/98
Remember, you have to rename it to PJ175IMG.zip before you install it.
Glad someone had the link for the update zip, I only have the img
Thanks everyone. I'm up and running again on the EVO LTE. I did use the bootloader method to flash the .zip. I also now think my primary issue was self inflicted - I was using a 32gb micro SD card and I don't think the phone liked that. When I used one of my 8GB cards everything seemed to work like a champ.
Again, I want say thank you for the super fast responses and great knowledge provided - THANK YOU!!
[SOLVED]
Hi,
I just unlocked my phone using HTCdev/bootloader, and installed TWRP 2.6.3.0 recovery flashing it from HTC ONE X + toolkit .( I first flashed it from fastboot cmd, but it wasnt loading on the recovery when i was selecting it on my bootloader, then it worked just fine from the toolkit ).
After this operations, i tried to flash the last CM custom rom, following their wiki, but when i flash the rom, i get this error :
Code:
c:\Fastboot>fastboot flash /sdcard cm-10.2.1-enrc2b.zip
sending '/sdcard' (208390 KB)... OKAY [ 15.600s]
writing '/sdcard'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 36.999s
I tried to flash the boot.img first, by extracting it appart and using command
Code:
fastboot flash boot boot.img
, then flashing the zip file, but it still doesn't work.
Last thing but not the coolest, I'm now, totally unable to boot on my previous rom.
I can use fastboot/bootloader and recovery perfectly though. Every single file i'm trying to flash into the /sdcard is failing due to signature verification. Please can someone help me ?
Thank you.
( sorry for my bad english writing )
EDIT :
My actual bootloader :
Code:
***TAMPERED***
***UNLOCKED***
EVITA PVT SHIP S-ON RL
HBOOT-2.15.0000
RADIO-1.31a.32.45.16_2
OPENDSP-v33.1.0.45.1128
eMMC-boot
Aug 22 2013, 11:48:30:-1
I tried to check my version for RUU reset
Code:
c:\Fastboot>fastboot getvar version-main
version-main: 5.08.163.2
finished. total time: 0.003s
Couldnt find any .exe RUU to help.
Thanks !
Bruwno said:
Hi,
I just unlocked my phone using HTCdev/bootloader, and installed TWRP 2.6.3.0 recovery flashing it from HTC ONE X + toolkit .( I first flashed it from fastboot cmd, but it wasnt loading on the recovery when i was selecting it on my bootloader, then it worked just fine from the toolkit ).
After this operations, i tried to flash the last CM custom rom, following their wiki, but when i flash the rom, i get this error :
Code:
c:\Fastboot>fastboot flash /sdcard cm-10.2.1-enrc2b.zip
sending '/sdcard' (208390 KB)... OKAY [ 15.600s]
writing '/sdcard'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 36.999s
I tried to flash the boot.img first, by extracting it appart and using command
Code:
fastboot flash boot boot.img
, then flashing the zip file, but it still doesn't work.
Last thing but not the coolest, I'm now, totally unable to boot on my previous rom.
I can use fastboot/bootloader and recovery perfectly though. Every single file i'm trying to flash into the /sdcard is failing due to signature verification. Please can someone help me ?
Thank you.
( sorry for my bad english writing )
Click to expand...
Click to collapse
Are you using the latest CM 4.4 nightlies ? If yes these rom wont install using TWRP , you need to install either Lloir or Philz CMW recovery to flash them. This is clearly mentioned on Lloir's Post.Again make sure you are Using the enrc2b version of the phone..
http://forum.xda-developers.com/showthread.php?t=2510836
ethanon said:
Are you using the latest CM 4.4 nightlies ? If yes these rom wont install using TWRP , you need to install either Lloir or Philz CMW recovery to flash them. This is clearly mentioned on Lloir's Post.Again make sure you are Using the enrc2b version of the phone..
http://forum.xda-developers.com/showthread.php?t=2510836
Click to expand...
Click to collapse
Thank You for your answer, but i've been using stable cm-10.2.1-enrc2b. So i'm not sure that is the problem, because i've been having the same signature verify fail with other custom roms...
EDIT : Apparently i can't send anything to the /sdcard , i tried to send the right original OTA RUU, for flashing it from the original recovery, still getting this verify signature failed
Bruwno said:
Hi,
I just unlocked my phone using HTCdev/bootloader, and installed TWRP 2.6.3.0 recovery flashing it from HTC ONE X + toolkit .( I first flashed it from fastboot cmd, but it wasnt loading on the recovery when i was selecting it on my bootloader, then it worked just fine from the toolkit ).
After this operations, i tried to flash the last CM custom rom, following their wiki, but when i flash the rom, i get this error :
Code:
c:\Fastboot>fastboot flash /sdcard cm-10.2.1-enrc2b.zip
sending '/sdcard' (208390 KB)... OKAY [ 15.600s]
writing '/sdcard'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 36.999s
I tried to flash the boot.img first, by extracting it appart and using command
Code:
fastboot flash boot boot.img
, then flashing the zip file, but it still doesn't work.
Last thing but not the coolest, I'm now, totally unable to boot on my previous rom.
I can use fastboot/bootloader and recovery perfectly though. Every single file i'm trying to flash into the /sdcard is failing due to signature verification. Please can someone help me ?
Thank you.
( sorry for my bad english writing )
EDIT :
My actual bootloader :
Code:
***TAMPERED***
***UNLOCKED***
EVITA PVT SHIP S-ON RL
HBOOT-2.15.0000
RADIO-1.31a.32.45.16_2
OPENDSP-v33.1.0.45.1128
eMMC-boot
Aug 22 2013, 11:48:30:-1
I tried to check my version for RUU reset
Code:
c:\Fastboot>fastboot getvar version-main
version-main: 5.08.163.2
finished. total time: 0.003s]/code]
Couldnt find any .exe RUU to help.
Thanks ![/QUOTE]
[QUOTE="Bruwno, post: 50774443, member: 5754687"]Thank You for your answer, but i've been using stable cm-10.2.1-enrc2b. So i'm not sure that is the problem, because i've been having the same signature verify fail with other custom roms...
EDIT : Apparently i can't send anything to the /sdcard , i tried to send the right original OTA RUU, for flashing it from the original recovery, still getting this verify signature failed[/QUOTE]
Sorry Missed that the phone that you are using is EVITA (TelUs vesion of the phone ) and not the enrc2b (International version), Since you are trying to install the cm-10.2.1-enrc2b (International) version of the ROM it is failing .. enrc2b and EVITA are two different phones internally .They have different roms so try installing ROMS meant for EVITA(At&t) and not enrc2b .. This is kinda risky ... might just brick your phone ..
You can try this CM version on your phone
http://forum.xda-developers.com/showthread.php?t=2547118
Click to expand...
Click to collapse
ethanon said:
Sorry Missed that the phone that you are using is EVITA (TelUs vesion of the phone ) and not the enrc2b (International version), Since you are trying to install the cm-10.2.1-enrc2b (International) version of the ROM it is failing .. enrc2b and EVITA are two different phones internally .They have different roms so try installing ROMS meant for EVITA(At&t) and not enrc2b .. This is kinda risky ... might just brick your phone ..
You can try this CM version on your phone
http://forum.xda-developers.com/showthread.php?t=2547118
Click to expand...
Click to collapse
Nope, still nothing able to be uploaded got this verify signature failed error again and again...
Bruwno said:
Nope, still nothing able to be uploaded got this verify signature failed error again and again...
Click to expand...
Click to collapse
which ROM are you installing? also try installing the correct Recovery which is meant for EVITA (HOX) version and try installing the correct rom again. TRY HOX ROMS NOT HOX+ ROMS.
ethanon said:
which ROM are you installing? also try installing the correct Recovery which is meant for EVITA (At&t) version and try installing the correct rom again.
Click to expand...
Click to collapse
Well well well, i see progress down there !
I just tried something. I used the TWRP mount option to mount the sdcard, as it poped on my computer i was able to paste directly the ROMS which was unable to transfer before. I'll try EVITA CM first, after wyping data/cache. I'll let you know. This is pretty encouraging. Thanks for the reading, the ideas !
Bruwno said:
Well well well, i see progress down there !
I just tried something. I used the TWRP mount option to mount the sdcard, as it poped on my computer i was able to paste directly the ROMS which was unable to transfer before. I'll try EVITA CM first, after wyping data/cache. I'll let you know. This is pretty encouraging. Thanks for the reading, the ideas !
Click to expand...
Click to collapse
Make sure you download the HOX Roms from Cyanogenmod website and also my bad I gave you a wrong link in the previous post..
SOLVED
ethanon said:
Make sure you download the HOX Roms from Cyanogenmod website and also my bad I gave you a wrong link in the previous post..
Click to expand...
Click to collapse
After fighting hours to solve the problem, i was able to use a custom recovery to mount the sdcard and transfert it from a graphic interface. Then install it from recovery on the phone.
I still doesn't know why it wasnt transfering before, and why i got the failed verify signature using flash command in fastboot.
I'll run some simulation in order to found out why it's going this way and try to find a solution. I saw a lot of post mentionning this problem but still no solutions.
Thank you though, everything is ok now.
Bruwno said:
After fighting hours to solve the problem, i was able to use a custom recovery to mount the sdcard and transfert it from a graphic interface. Then install it from recovery on the phone.
I still doesn't know why it wasnt transfering before, and why i got the failed verify signature using flash command in fastboot.
I'll run some simulation in order to found out why it's going this way and try to find a solution. I saw a lot of post mentionning this problem but still no solutions.
Thank you though, everything is ok now.
Click to expand...
Click to collapse
For your case in particular I think it has to do with the wrong ROM selection . as you were trying to install enrc2b ROM and Recovery meant for enrc2b.
Hello everyone,
I am trying to unbrick my Moto E XT1021 but so far nothing work. Here are the infos:
Status: Device is unlocked (Status Code: 3), rooted, and CWM Recovery (v6.0.4.9) is installed.
Initially, I installed Kitkat Rom from this link https://www.youtube.com/watch?v=w7S5WmlPgrI, but after finishing, OTA showed me an update to 5.0.2, which I did. Everything work fine for about a month until last week where my phone just stop working.
Problem: Device is stuck on the Motorola Logo, bootloader loop.
Tested Solutions so far:
1- I tried to restore the stock firmware from the bootloader mode, but I always failed. I am applying the procedure given in:
http://forum.xda-developers.com/showthread.php?t=2759495
but it always failed. The method is working and the phone's screen some instructions are appearing, but between them, I notice in red/pink color that the phone is saying:
....
hab check failed for boot
......
hab chck failed for recovery
2- I also tried to install zip from sdcard from the CWM Recovery, or even to simply wipe cache, .... but strangely I am getting error on CWM as following:
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
E: Can't mount /cache/recovery/last_install
E: Can't open/cache/recovery/last_install
and when I tried to install zip from sideload, I am also getting an error:
E:Error in /tmp/update.zip
(Status 7)
So.....basically, I do not know what to do or try more. Any idea. Please Help ?!!!
Thanks
First change ur recovery to twrp 2.5.8 using adb method and then try to install latest cm12.1 . maybe ur downloaded file is corrupted.
Hit thanks if helped. goodluck☺��
youwave111 said:
First change ur recovery to twrp 2.5.8 using adb method and then try to install latest cm12.1 . maybe ur downloaded file is corrupted.
Hit thanks if helped. goodluck☺��
Click to expand...
Click to collapse
Thanks for the infos. I tried to install TWRP but I am receiving an error "Mismatched partition size (recovery)". Any ideas ?!!!
moh19814 said:
Thanks for the infos. I tried to install TWRP but I am receiving an error "Mismatched partition size (recovery)". Any ideas ?!!!
Click to expand...
Click to collapse
I tried again using this time twrp-2.7.1.0-condor.img, but still I am getting on the phone's screen the same message:
"Mismatched partition size (recovery)",
and on the adb (CMD) window, I am getting:
<bootloader> Failed to erase partition
<bootloader> Failed to flash partition recovery
Failed <remote failure>
Any ideas ?!!!. Please Help !!!
Try ro use twrp 2.5.8 or above instead and write the following command in cmd
Fastboot boot recovery.img
In this way you're not owerwriting the recovery and if it boots up fine then install the stock firmware
Peace✌
Hit thanks pls
youwave111 said:
Try ro use twrp 2.5.8 or above instead and write the following command in cmd
Fastboot boot recovery.img
In this way you're not owerwriting the recovery and if it boots up fine then install the stock firmware
Peace✌
Hit thanks pls
Click to expand...
Click to collapse
Thanks again for the help. I tried that also.
On the CMD window, I got OK, but the phone reboot and stuck on the Motorola Logo page and nothing happen after. ?!!!
For info, I tried with both TWRP 2.7.1.0 and 2.8.6.0, and in both cases phone stuck on the Motorola Logo after reboot.
Any idea what is hapenning ?!!
Thanks
Can any one help me my moto e xt1022 was bricked whlie i update to 4.4.4 pls help me
IMTHI said:
Can any one help me my moto e xt1022 was bricked whlie i update to 4.4.4 pls help me
Click to expand...
Click to collapse
Can you get into the recovery mode ?
Sent from my Y541-U02 using Tapatalk
moh19814 said:
Hello everyone,
I am trying to unbrick my Moto E XT1021 but so far nothing work. Here are the infos:
Status: Device is unlocked (Status Code: 3), rooted, and CWM Recovery (v6.0.4.9) is installed.
Initially, I installed Kitkat Rom from this link https://www.youtube.com/watch?v=w7S5WmlPgrI, but after finishing, OTA showed me an update to 5.0.2, which I did. Everything work fine for about a month until last week where my phone just stop working.
Problem: Device is stuck on the Motorola Logo, bootloader loop.
Tested Solutions so far:
1- I tried to restore the stock firmware from the bootloader mode, but I always failed. I am applying the procedure given in:
http://forum.xda-developers.com/showthread.php?t=2759495
but it always failed. The method is working and the phone's screen some instructions are appearing, but between them, I notice in red/pink color that the phone is saying:
....
hab check failed for boot
......
hab chck failed for recovery
2- I also tried to install zip from sdcard from the CWM Recovery, or even to simply wipe cache, .... but strangely I am getting error on CWM as following:
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
E: Can't mount /cache/recovery/last_install
E: Can't open/cache/recovery/last_install
and when I tried to install zip from sideload, I am also getting an error:
E:Error in /tmp/update.zip
(Status 7)
So.....basically, I do not know what to do or try more. Any idea. Please Help ?!!!
Thanks
Click to expand...
Click to collapse
Ur internal storage is gone...consult ur nearby Motorola service centre
To confirm whether ur internal is working or not flash a boot logo via adb, if it fails to install then ur internal is gone!! :/
Sent from my falcon using Tapatalk
Try to flash the stock firmware
Press thanks if I helped you☺
Same problem with my moto e 1st gen...if u find any solution please tell me...
moh19814 said:
Thanks again for the help. I tried that also.
On the CMD window, I got OK, but the phone reboot and stuck on the Motorola Logo page and nothing happen after. ?!!!
Click to expand...
Click to collapse
Same problem with my moto e 1st gen, if u fond any solutions please tell me so that i can give a new life to my dead moto e.. Thanks a lot in advance..
My email id
[email protected]
phone is dead
ProudRed said:
Can you get into the recovery mode ?
Sent from my Y541-U02 using Tapatalk
Click to expand...
Click to collapse
No,phone is not starting,even not going into recovery or bootloader when I plug the charger led is blinking pls help my friend
Thanks in advance
moh19814 said:
Hello everyone,
I am trying to unbrick my Moto E XT1021 but so far nothing work. Here are the infos:
Status: Device is unlocked (Status Code: 3), rooted, and CWM Recovery (v6.0.4.9) is installed.
Initially, I installed Kitkat Rom from this link
, but after finishing, OTA showed me an update to 5.0.2, which I did. Everything work fine for about a month until last week where my phone just stop working.
Problem: Device is stuck on the Motorola Logo, bootloader loop.
Tested Solutions so far:
1- I tried to restore the stock firmware from the bootloader mode, but I always failed. I am applying the procedure given in:
http://forum.xda-developers.com/showthread.php?t=2759495
but it always failed. The method is working and the phone's screen some instructions are appearing, but between them, I notice in red/pink color that the phone is saying:
....
hab check failed for boot
......
hab chck failed for recovery
2- I also tried to install zip from sdcard from the CWM Recovery, or even to simply wipe cache, .... but strangely I am getting error on CWM as following:
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
E: Can't mount /cache/recovery/last_install
E: Can't open/cache/recovery/last_install
and when I tried to install zip from sideload, I am also getting an error:
E:Error in /tmp/update.zip
(Status 7)
So.....basically, I do not know what to do or try more. Any idea. Please Help ?!!!
Thanks
Click to expand...
Click to collapse
Try this:-
https://forum.xda-developers.com/moto-e/general/unbrick-hard-bricked-moto-e-t2974093/amp/
Hi all!
I recieved my new OPX yesterday, brand new from oneplus store.
The phone immediatly updated through the ota to:
OnePlusXOxygen_14_OTA_019_all_201611071506
After that i followed this guide:
https://forums.oneplus.net/threads/...om-recovery-root-take-efs-backup-more.401713/
I installed all the drivers and managed to unlock the bootloader without any problem.
(it said "device tampered: no, device unlocked: yes" using the command: fastboot oem device-info
The problem starts at twrp.
I have downloaded twrp-3.0.2-2_blu_spark.v41-onyx_by-engstk.img and i can flash it to recovery using
fastboot flash recovery recovery.img (after renaming it to recovery.img)
After that I use the command: fastboot boot recovery.img
I can enter TWRP, but I cannot do anything. It cannot mount anything and on all the storages there is 0mb.
After this I can reboot normal and the normal recovery is back, so my phone isnt bricked or anything like that
I did try to download OnePlusXOxygen_14_OTA_019_all_201611071506_03f73e21449d4d31.zip and flashed it but the twrp problem still persists.
I tried the other twrp for the new bootloader by Nachiket.Namjoshi, but with the same result.
I have no Idea what to do, can anyone help me? Why can´t I access files from twrp?
Does it have something to do with my phone being brand new?
/regards Bror David
brordavid said:
Hi all!
I recieved my new OPX yesterday, brand new from oneplus store.
The phone immediatly updated through the ota to:
OnePlusXOxygen_14_OTA_019_all_201611071506
After that i followed this guide:
https://forums.oneplus.net/threads/...om-recovery-root-take-efs-backup-more.401713/
I installed all the drivers and managed to unlock the bootloader without any problem.
(it said "device tampered: no, device unlocked: yes" using the command: fastboot oem device-info
The problem starts at twrp.
I have downloaded twrp-3.0.2-2_blu_spark.v41-onyx_by-engstk.img and i can flash it to recovery using
fastboot flash recovery recovery.img (after renaming it to recovery.img)
After that I use the command: fastboot boot recovery.img
I can enter TWRP, but I cannot do anything. It cannot mount anything and on all the storages there is 0mb.
After this I can reboot normal and the normal recovery is back,
so my phone isnt bricked or anything like that
I did try to download OnePlusXOxygen_14_OTA_019_all_201611071506_03f73e21449d4d31.zip and flashed it but the twrp problem still persists.
I tried the other twrp for the new bootloader by Nachiket.Namjoshi, but with the same result.
I have no Idea what to do, can anyone help me? Why can´t I access files from twrp?
Does it have something to do with my phone being brand new?
/regards Bror David
Click to expand...
Click to collapse
Hello, recieved your PM,
I'm guessing something wrong has been done on your part, however, its okay, no harm will be done
from the OP i could infer that your TWRP isnt getting flashed, as (if i understand it correctly) OnePlus Recovery is restored when you reboot
i would suggest you to follow this guide and my recovery.
and when you unlock, always let your phone boot completely before rushing to flashifying stuff.
follow this guide and postback with any info (if more than this)
also, the build number issue is what i cannot confirm, as I have only seen 1 OPX in my life (yes, believe me) and that was mine, since Im currently on a different ROM i cannot post my build number.... @Joshwin Aranha could maybe help you with build number.
Nachiket.Namjoshi said:
Hello, recieved your PM,
I'm guessing something wrong has been done on your part, however, its okay, no harm will be done
from the OP i could infer that your TWRP isnt getting flashed, as (if i understand it correctly) OnePlus Recovery is restored when you reboot
i would suggest you to follow this guide and my recovery.
and when you unlock, always let your phone boot completely before rushing to flashifying stuff.
follow this guide and postback with any info (if more than this)
also, the build number issue is what i cannot confirm, as I have only seen 1 OPX in my life (yes, believe me) and that was mine, since Im currently on a different ROM i cannot post my build number.... @Joshwin Aranha could maybe help you with build number.
Click to expand...
Click to collapse
Thanks for reply!
I believe that I manage to flash twrp. In fastboot I get this:
target reported max download size of 536870912 bytes
sending 'recovery' (15860 KB)...
OKAY [ 0.500s]
writing 'recovery'...
OKAY [ 0.223s]
finished. total time: 0.726s
I can boot into twrp, and I see the different options (backup, restore, etc), but when I choose backup I cannot choose any storage. All of the storages is listed as 0mb. I can see folders under install menu (boot, cache, data, dev, etc, external_sd.....), but no files appears. In the logs in TWRP I get a lot of errors regarding cannot mount storages.
My only option from here is rebooting into os again, and when I do that, twrp gets overwritten by oneplus recovery.
BTW, all the storages works as they should in OP:s recovery.
The errors im having in twrp are these:
Erimary block device 'dev/block/platform/msm_sdcc.1/by-name/userdata' for mount point '/data' is not present!
E:Unable to find partition size for 'boot'
E:Unable to find partition size for 'recovery'
E:Unable to find partition size for 'misc'
E:Unable to find partition size for 'efs1'
E:Unable to find partition size for 'efs2'
E:unable to set bootloader message.
Failed to mount '/data' (invalid argument)
Unable to recreate /data/media folder.
Updating partition details...
Failed to mount '/firmware' (invalid argument)
Failed to mount '/system' (invalid argument)
Failed to mount '/data' (invalid argument)
Failed to mount '/cache' (invalid argument)
Failed to mount '/persist' (invalid argument)
...done
Unable to mount storage
Failed to mount '/data' (invalid argument)
Failed to mount '/cache' (invalid argument)
Full SELinux support is present
Failed to mount '/cache' (invalid argument)
Failed to mount '/cache' (invalid argument)
Unable to mount /data/media/TWRP/.twrps
MTP enabled
As I wrote to Nachiket.Namjoshi, I have compared my phone with a co-workers OPX and there are differences in build numbers
My is:
ONE E1003_15_161107 and my co-worker: ONE E1003_14_161107.
brordavid said:
Thanks for reply!
I believe that I manage to flash twrp. In fastboot I get this:
target reported max download size of 536870912 bytes
sending 'recovery' (15860 KB)...
OKAY [ 0.500s]
writing 'recovery'...
OKAY [ 0.223s]
finished. total time: 0.726s
I can boot into twrp, and I see the different options (backup, restore, etc), but when I choose backup I cannot choose any storage. All of the storages is listed as 0mb. I can see folders under install menu (boot, cache, data, dev, etc, external_sd.....), but no files appears. In the logs in TWRP I get a lot of errors regarding cannot mount storages.
My only option from here is rebooting into os again, and when I do that, twrp gets overwritten by oneplus recovery.
BTW, all the storages works as they should in OP:s recovery.
The errors im having in twrp are these:
Erimary block device 'dev/block/platform/msm_sdcc.1/by-name/userdata' for mount point '/data' is not present!
E:Unable to find partition size for 'boot'
E:Unable to find partition size for 'recovery'
E:Unable to find partition size for 'misc'
E:Unable to find partition size for 'efs1'
E:Unable to find partition size for 'efs2'
E:unable to set bootloader message.
Failed to mount '/data' (invalid argument)
Unable to recreate /data/media folder.
Updating partition details...
Failed to mount '/firmware' (invalid argument)
Failed to mount '/system' (invalid argument)
Failed to mount '/data' (invalid argument)
Failed to mount '/cache' (invalid argument)
Failed to mount '/persist' (invalid argument)
...done
Unable to mount storage
Failed to mount '/data' (invalid argument)
Failed to mount '/cache' (invalid argument)
Full SELinux support is present
Failed to mount '/cache' (invalid argument)
Failed to mount '/cache' (invalid argument)
Unable to mount /data/media/TWRP/.twrps
MTP enabled
As I wrote to Nachiket.Namjoshi, I have compared my phone with a co-workers OPX and there are differences in build numbers
My is:
ONE E1003_15_161107 and my co-worker: ONE E1003_14_161107.
Click to expand...
Click to collapse
Hi there, sorry for joining late to the party
So about the TWRP, I'm not sure what is going on, because the command is correct, and the log you posted is over my head, its kinda mind boggling if the Recovery flashed correctly, which as I understand it did, then it should't throw those errors. @Nachiket.Namjoshi that's your thing bro.
Regarding build numbers, I'm confused, at the outset I'd anyway like you to post a screenshot of your About Phone section, and the other thing, you stated at the beginning of your thread that you OTA updated to OnePlusXOxygen_14_OTA_019_all_201611071506, but in your second reply you say that it say's ONE E1003_15_161107, can you clarify this ? Because as of now I'm still running OnePlusXOxygen_14_OTA_019_all_201611071506, i.e Oxygen OS (OOS) 3.1.4. And my build number is ONE E1003_14_161107.
Joshwin Aranha said:
Hi there, sorry for joining late to the party
So about the TWRP, I'm not sure what is going on, because the command is correct, and the log you posted is over my head, its kinda mind boggling if the Recovery flashed correctly, which as I understand it did, then it should't throw those errors. @Nachiket.Namjoshi that's your thing bro.
Regarding build numbers, I'm confused, at the outset I'd anyway like you to post a screenshot of your About Phone section, and the other thing, you stated at the beginning of your thread that you OTA updated to OnePlusXOxygen_14_OTA_019_all_201611071506, but in your second reply you say that it say's ONE E1003_15_161107, can you clarify this ? Because as of now I'm still running OnePlusXOxygen_14_OTA_019_all_201611071506, i.e Oxygen OS (OOS) 3.1.4. And my build number is ONE E1003_14_161107.
Click to expand...
Click to collapse
Welcome to the party. :laugh:
My co-worker suggested that I should erase recovery before flashing the twrp doing this:
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot boot recovery.img
I did this, but I have still problem with twrp.
At first boot after i bought OPX the phone updated itself (cant remember the actual name on that beacuse the system downloaded it, but it was 3.1.4), after that i unlocked bootloader and all the other stuff, usb debugging etc.
After I failed the first time with twrp, I flashed this one hoping that twrp would work after flashing:
OnePlusXOxygen_14_OTA_019_all_201611071506_03f73e21449d4d31.zip (from op:s download page)
Here is a screenshot of my "about phone section"
https://drive.google.com/open?id=0B9XjA60WaKGVSXZ4OHEtdVQ3X0k
Might there be problem with the fastboot/adb environment?
/regards Bror David
brordavid said:
Welcome to the party. :laugh:
My co-worker suggested that I should erase recovery before flashing the twrp doing this:
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot boot recovery.img
I did this, but I have still problem with twrp.
At first boot after i bought OPX the phone updated itself (cant remember the actual name on that beacuse the system downloaded it, but it was 3.1.4), after that i unlocked bootloader and all the other stuff, usb debugging etc.
After I failed the first time with twrp, I flashed this one hoping that twrp would work after flashing:
OnePlusXOxygen_14_OTA_019_all_201611071506_03f73e21449d4d31.zip (from op:s download page)
Here is a screenshot of my "about phone section"
https://drive.google.com/open?id=0B9XjA60WaKGVSXZ4OHEtdVQ3X0k
Might there be problem with the fastboot/adb environment?
/regards Bror David
Click to expand...
Click to collapse
no, most likely not.
one final question, as per OP you said you are back into Oxygen Recovery when you reboot to recovery after flashing, is that correct?
im going to leave a method here for you to try.... I'm not sure if it will work as I cannot get handson to your device.. but after reading your issue
only thing that pops up to my mind is: messed up partitions..
here is what you should try:
boot to fastboot mode
use following commands in same order
Code:
[LIST]
[*]fastboot flash recovery recovery.img
[*]fastboot format userdata - [B][COLOR=Red]NOTE: THIS WILL FORMAT YOUR ENTIRE INTERNAL DATA SO BACKUP FIRST[/COLOR][/B]
[*]fastboot boot recovery.img
[/LIST]
reboot to recovery again (to test)
Nachiket.Namjoshi said:
no, most likely not.
one final question, as per OP you said you are back into Oxygen Recovery when you reboot to recovery after flashing, is that correct?
im going to leave a method here for you to try.... I'm not sure if it will work as I cannot get handson to your device.. but after reading your issue
only thing that pops up to my mind is: messed up partitions..
here is what you should try:
boot to fastboot mode
use following commands in same order
Code:
[LIST]
[*]fastboot flash recovery recovery.img
[*]fastboot format userdata - [B][COLOR=Red]NOTE: THIS WILL FORMAT YOUR ENTIRE INTERNAL DATA SO BACKUP FIRST[/COLOR][/B]
[*]fastboot boot recovery.img
[/LIST]
reboot to recovery again (to test)
Click to expand...
Click to collapse
No, I can boot into TWRP, but I cannot flash/backup anything at all in TWRP as I cannot access the storages.
After I reboot from TWRP to OOS TWRP gets overwritten and Oxygen Recovery is back.
I cannot backup anything. I'm not rooted
Will the OS also disappear?
brordavid said:
No, I can boot into TWRP, but I cannot flash/backup anything at all in TWRP as I cannot access the storages.
After I reboot from TWRP to OOS TWRP gets overwritten and Oxygen Recovery is back.
I cannot backup anything. I'm not rooted
Will the OS also disappear?
Click to expand...
Click to collapse
well you can backup your data in internal storage, it gonna be gone if you use that command, but hopefully its worth it (90% chance)
EDIT: you should really try those steps. im 9-% positive that should solve the problem
Nachiket.Namjoshi said:
well you can backup your data in internal storage, it gonna be gone if you use that command, but hopefully its worth it (90% chance)
EDIT: you should really try those steps. im 9-% positive that should solve the problem
Click to expand...
Click to collapse
Sorry, it didnt work. All the steps seems fine (as you can see).
C:\Users\David\Downloads\Oneplus X (onyx)\twrp variant två ny bootloader>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (15860 KB)...
OKAY [ 0.499s]
writing 'recovery'...
OKAY [ 0.222s]
finished. total time: 0.727s
C:\Users\David\Downloads\Oneplus X (onyx)\twrp variant två ny bootloader>fastboot format userdata
Creating filesystem with parameters:
Size: 12611891200
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3079075
Block groups: 94
Reserved block group size: 751
Created filesystem with 11/770048 inodes and 88617/3079075 blocks
target reported max download size of 536870912 bytes
erasing 'userdata'...
OKAY [ 1.877s]
sending 'userdata' (136970 KB)...
OKAY [ 4.294s]
writing 'userdata'...
OKAY [ 1.809s]
finished. total time: 7.989s
C:\Users\David\Downloads\Oneplus X (onyx)\twrp variant två ny bootloader>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.500s]
booting...
OKAY [ 0.026s]
finished. total time: 0.531s
I can enter twrp, but all the errors are still there.
I also tried to reboot from twrp to twrp, and twrp is still there, but with all the errors.
TWRP takes a while to boot, but I guess thats beacuse of all the mounting errors.
(I tried all of your steps twice)
It's strange, because in oxygen recovery everything is mountable..
I'm really grateful that you are helping me. Any other suggestions?
I have exactly the same symptoms on my new OPX, got it last Thursday. mfg 13.11.2016
ONE E1003
/ Mattias
Mattias N said:
I have exactly the same symptoms on my new OPX, got it last Thursday. mfg 13.11.2016
ONE E1003
/ Mattias
Click to expand...
Click to collapse
Thank god I'm not alone.
It must be something hardware wise then?
A little update.
I had a remote session today with oneplus support (they are really helpful!) and I guess they did some kind of brick restore thingy. It didn't work. After the remote session the phone stops at the oneplus logo (but now I can't access storages in oxygen recovery either) , so I'm returning the phone and letting oneplus repair it.
I'll keep you updated when there are more news.
Thanks for your help here at xda, oneplus x has a great community here.
hello, here the same problem.... tried a few TWRP recovery versions but can't access the internal Storage. After the try to flash the phone with the MSMdownloadtool 2.0 (original OP Recovery Flash-Tool) the Oneplus X even boot anymore. No idea what happens with the newest Generation OPX
Date of Manufacture was November 2016?! Perhaps, the problem is the newer OOS 3.xxx. With OOS2.xxx i had no problems to Flash CM13 to a few OPX
Oneplus_X_Flasher said:
hello, here the same problem.... tried a few TWRP recovery versions but can't access the internal Storage. After the try to flash the phone with the MSMdownloadtool 2.0 (original OP Recovery Flash-Tool) the Oneplus X even boot anymore. No idea what happens with the newest Generation OPX
Date of Manufacture was November 2016?! Perhaps, the problem is the newer OOS 3.xxx. With OOS2.xxx i had no problems to Flash CM13 to a few OPX
Click to expand...
Click to collapse
Another with the same problem. There is something strange going on. Have you tried a remote session with oneplus or are you returning it?
I know I shouldn't think like this, but it feels good not being the only one with this problem. =)
hello, yes we tried a remote session with oneplus but the technican also can't help. Yes! something strange ist going on with the newer OPX Generation. Three OPX with DOM 2015 no problem to Flash CM13 and this one with DOM 2016 unable to Mount Partition in Recovery
in this thread, is perhaps the same problem...only already destroyed with the original Rescue Builder from OP http://forum.xda-developers.com/oneplus-x/help/bricked-oneplus-x-removable-drive-t3518620/page2
Same problem here
I received new onyx yesterday. I have exactly the same problem!!! tried the same things.
I didnt have these problems on my last onyx
do you have OOS 3 or OOS 2 on your new OnePlus X? I think the problem is a bug in OOS3/Android 6
Oneplus_X_Flasher said:
hello, yes we tried a remote session with oneplus but the technican also can't help. Yes! something strange ist going on with the newer OPX Generation. Three OPX with DOM 2015 no problem to Flash CM13 and this one with DOM 2016 unable to Mount Partition in Recovery
in this thread, is perhaps the same problem...only already destroyed with the original Rescue Builder from OP http://forum.xda-developers.com/oneplus-x/help/bricked-oneplus-x-removable-drive-t3518620/page2
Click to expand...
Click to collapse
I am one of the people who had a bricked device (black screen, white led) and was lucky (tricked them) to get my device/mainboard exchanged, see http://forum.xda-developers.com/oneplus-x/help/bricked-oneplus-x-removable-drive-t3518620/page2
I was on ONE E1003_14_161107 before and now with the new mainboard I also have ONE E1003_15_161107 and twrp can't find the partitions.
After I read your post I am sure ONE E1003_15_161107 is a build to stop twrp from working and so stop people rooting and messing with their phones.
i dont think so...oneplus has no problems with the rooter and flasher so why do that intentionally?^^ the support also dont know about the problem with the locked internal Storage.
where do i find the " ONE E1003_15_161107" ? is it on the sticker of the original Oneplus X Box?
you can find it in Settings --> about phone --> Build number
I have also ONE E1003_15_161107