Related
I have a Streak 7 (unlocked WiFi + 3G/4G) with Stock Honeycomb. I previously Rooted it and had CWM Recovery installed (not sure which version, but I think it was 5.something). Somehow, I seem to have reverted to the stock recovery. I don't know how this happened, but I noticed it first when I tried to make a backup last week. I have tried several times to flash CWM recovery (both versions 5.0.2.7 and 5.0.2.8) but I keep getting the stock recovery when I boot to recovery. Otherwise, everything seems to operate normally.
I use fastboot to flash recovery and get the following:
C:\Android ADB Streak\Streak\Win32>fastboot flash recovery recovery.img
sending 'recovery' (4402 KB)...
OKAY [ 0.507s]
writing 'recovery'...
OKAY [ 1.355s]
finished. total time: 1.863s
On the Streak screen, I see:
Starting Fastboot USB Download Protocol
Flashing StorMgr partition recovery
Read after write partition recovery
then I reboot the Streak:
C:\Android ADB Streak\Streak\Win32>fastboot reboot
rebooting...
finished. total time: 0.002s
But when I boot into recovery, I get the stock recovery. Am I doing something wrong?
wdwray said:
I have a Streak 7 (unlocked WiFi + 3G/4G) with Stock Honeycomb. I previously Rooted it and had CWM Recovery installed (not sure which version, but I think it was 5.something). Somehow, I seem to have reverted to the stock recovery. I don't know how this happened, but I noticed it first when I tried to make a backup last week. I have tried several times to flash CWM recovery (both versions 5.0.2.7 and 5.0.2.8) but I keep getting the stock recovery when I boot to recovery. Otherwise, everything seems to operate normally.
I use fastboot to flash recovery and get the following:
C:\Android ADB Streak\Streak\Win32>fastboot flash recovery recovery.img
sending 'recovery' (4402 KB)...
OKAY [ 0.507s]
writing 'recovery'...
OKAY [ 1.355s]
finished. total time: 1.863s
On the Streak screen, I see:
Starting Fastboot USB Download Protocol
Flashing StorMgr partition recovery
Read after write partition recovery
then I reboot the Streak:
C:\Android ADB Streak\Streak\Win32>fastboot reboot
rebooting...
finished. total time: 0.002s
But when I boot into recovery, I get the stock recovery. Am I doing something wrong?
Click to expand...
Click to collapse
You press/hold +Vol button, press/hold the power button till the menu comes up. You then select option #2 and press the power button. That will take into CWM.
Thanks. I feel like a clone:cyclops:; I forgot about selecting option 2. Although it would be helpful if each Android device didn't have a different way of getting to Recovery.
Thank you very much .... But when I select option 2 "install update .... " my device freeeze on boot !!!!!!!!!!
Can you give me a solution please .. thanks
kdultimate said:
Thank you very much .... But when I select option 2 "install update .... " my device freeeze on boot !!!!!!!!!!
Can you give me a solution please .. thanks
Click to expand...
Click to collapse
You've flashed the CWM via Fastboot and your trying to boot into it now?
I would make sure you are at least 60% charge first.
Yes .... Exactly i flashed cwm via fastboot ... Writing recovery ok ... But when i tried to enter " the device freeze on install update package and i cannot make anything... Thanks
kdultimate said:
Yes .... Exactly i flashed cwm via fastboot ... Writing recovery ok ... But when i tried to enter " the device freeze on install update package and i cannot make anything... Thanks
Click to expand...
Click to collapse
There are a few different CWM versions, so it's possible that you used a version not compatiable with your ROM.
The same was happening to my streak but i installed version 3.0.x.x and it worked with that one
Sent from my LG-P999 using xda app-developers app
I'm on the T-Mobile variant and have followed the steps on the motorola website to unlock the bootloader. When I boot into fastboot, it says the device is unlocked with at status code 3. When I run 'fastboot flash recovery recovery.img' everything seems to run fine:
fastboot flash recovery recovery.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.827s]
writing 'recovery'...
OKAY [ 1.102s]
finished. total time: 1.930sWhen I try to reboot into recovery mode it just shows me the warning that my bootloader is unlocked, then boots as normal. I don't know what to do. I've tried both the twrp and cwm recovery images. Any help?
what recovery did you flash?
waiflih said:
what recovery did you flash?
Click to expand...
Click to collapse
I've tried both the twrp and cwm recoveries that are available in the android development section.
You are replacing recovery.img with the actual file name right?
Sent from my Moto X.
mentose457 said:
You are replacing recovery.img with the actual file name right?
Sent from my Moto X.
Click to expand...
Click to collapse
Yup. From reading around it seems like there's a script in /system that flashes the stock recovery upon booting up. I tried to get the PwnMyMoto apk onto my device to get root and remove the recovery script file but now I'm getting an unexpected exception when trying to install the apk through adb. I have both USB debugging and Unknown Sources allowed. Any ideas?
Edit:
By the way I am T-Mobile, post OTA. If that changes anything.
elijahah said:
Yup. From reading around it seems like there's a script in /system that flashes the stock recovery upon booting up. I tried to get the PwnMyMoto apk onto my device to get root and remove the recovery script file but now I'm getting an unexpected exception when trying to install the apk through adb. I have both USB debugging and Unknown Sources allowed. Any ideas?
Edit:
By the way I am T-Mobile, post OTA. If that changes anything.
Click to expand...
Click to collapse
This might be a long way to do it but can't you downgrade back to 4.2.2 then get root with that then follow the instructions found in the general section for maintaining root through taking the ota? This should fix your problem. Also the instructions there might give you a different idea of how to work around this issue. You might just be able to flash the boot image and install the hidden su yourself.
Sent from my XT1060 using xda app-developers app
jayboyyyy said:
This might be a long way to do it but can't you downgrade back to 4.2.2 then get root with that then follow the instructions found in the general section for maintaining root through taking the ota? This should fix your problem. Also the instructions there might give you a different idea of how to work around this issue. You might just be able to flash the boot image and install the hidden su yourself.
Sent from my XT1060 using xda app-developers app
Click to expand...
Click to collapse
I'm already on 4.2.2. I'm guessing you mean to undo the recent OTA? How would I do that without a custom recovery or root?
Twrp has a built on file explorer, can you boot directly into recovery from the fastboot screen and delete the file that way?
Sent on my Moto X
flashallthetime said:
Twrp has a built on file explorer, can you boot directly into recovery from the fastboot screen and delete the file that way?
Sent on my Moto X
Click to expand...
Click to collapse
Unfortunately I can't I flash the recovery via fastboot then try to boot into recovery and it just shows me the warning that my bootloader is unlocked and boots normally.
elijahah said:
Unfortunately I can't I flash the recovery via fastboot then try to boot into recovery and it just shows me the warning that my bootloader is unlocked and boots normally.
Click to expand...
Click to collapse
One more clarification: After you flash recovery, you are using the volume down key to highlight recovery and then you are using the up arrow to select it correct? You do not press the power button to make the selection as on nexus devices.
elijahah said:
Unfortunately I can't I flash the recovery via fastboot then try to boot into recovery and it just shows me the warning that my bootloader is unlocked and boots normally.
Click to expand...
Click to collapse
Don't flash it, boot it. Fastboot boot recovery recovery.IMG. if that works maybe you can delete that file.
Sent from my Nexus 7
mentose457 said:
One more clarification: After you flash recovery, you are using the volume down key to highlight recovery and then you are using the up arrow to select it correct? You do not press the power button to make the selection as on nexus devices.
Click to expand...
Click to collapse
Oops I didn't know that! Still no avail. I get a screen with the green android that says 'no command'
phositadc said:
Don't flash it, boot it. Fastboot boot recovery recovery.IMG. if that works maybe you can delete that file.
Sent from my Nexus 7
Click to expand...
Click to collapse
Ah man I thought this would work but this is the response I got:
fastboot boot twrp263.img
downloading 'boot.img'...
OKAY [ 0.811s]
booting...
(bootloader) Command restricted
FAILED (remote failure)
finished. total time: 0.881s
Thanks for all your help though guys.
elijahah said:
Oops I didn't know that! Still no avail. I get a screen with the green android that says 'no command'
Ah man I thought this would work but this is the response I got:
fastboot boot twrp263.img
downloading 'boot.img'...
OKAY [ 0.811s]
booting...
(bootloader) Command restricted
FAILED (remote failure)
finished. total time: 0.881s
Thanks for all your help though guys.
Click to expand...
Click to collapse
Did you leave a word out? I think it's fastboot boot recovery recovery. IMG.
Sent from my Nexus 7
elijahah said:
Oops I didn't know that! Still no avail. I get a screen with the green android that says 'no command'
Thanks for all your help though guys.
Click to expand...
Click to collapse
Erase the recovery partition. Then try flashing twrp.
fastboot erase recovery
fastboot flash recovery twrp26XX.img
Sent from my Moto X.
mentose457 said:
Erase the recovery partition. Then try flashing twrp.
fastboot erase recovery
fastboot flash recovery twrp26XX.img
Sent from my Moto X.
Click to expand...
Click to collapse
I get this:
fastboot erase recovery
(bootloader) Variable not supported!
erasing 'recovery'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.071s
Actually it works now. I just tired fastboot flash recovery twrp263.img then pressed vol down to get to recovery and pressed vol up to select it and it worked! Thanks for sticking with me guys.
elijahah said:
Actually it works now. I just tired fastboot flash recovery twrp263.img then pressed vol down to get to recovery and pressed vol up to select it and it worked! Thanks for sticking with me guys.
Click to expand...
Click to collapse
Excellent. Glad you got it working.
elijahah said:
Actually it works now. I just tired fastboot flash recovery twrp263.img then pressed vol down to get to recovery and pressed vol up to select it and it worked! Thanks for sticking with me guys.
Click to expand...
Click to collapse
PS you had recovery the first time you hit the up volume and it sent you to a screen that said "no command" from that screen if you press the up volume and power button together it sends you to the recovery screen. It may be down volume and power together to get passed that "no command" screen but its one of the two. I saw people having that same problem in the forum about maintaining root through the OTA.
phositadc said:
Did you leave a word out? I think it's fastboot boot recovery recovery. IMG.
Sent from my Nexus 7
Click to expand...
Click to collapse
elijahah said:
Oops I didn't know that! Still no avail. I get a screen with the green android that says 'no command'
Ah man I thought this would work but this is the response I got:
fastboot boot twrp263.img
downloading 'boot.img'...
OKAY [ 0.811s]
booting...
(bootloader) Command restricted
FAILED (remote failure)
finished. total time: 0.881s
Thanks for all your help though guys.
Click to expand...
Click to collapse
Probably your battery isnt charged enough to proceed with operation.
Check your battery and make sure it is charged at least 50% and try again.
leonardoafa said:
Probably your battery isnt charged enough to proceed with operation.
Check your battery and make sure it is charged at least 50% and try again.
Click to expand...
Click to collapse
Will charge up a bit over 50% and see. I still get permission denied. Plus when I try to get into recovery, I can't. The Motorola log shows up for a while, then restarts and boots normally into Android.
Hello, my MB886 is runing a stock ROM 4.1.1 (OTA updated)
Rooted
Unlocked Bootloader
I've tried to flash CWM via Fastboot to install a CM ROM, and I get this:
C:\Fastboot>adb reboot bootloader
C:\Fastboot>fastboot devices
TA30004B86 fastboot
C:\Fastboot>fastboot flash recovery cwm.img
sending 'recovery' (7892 KB)... OKAY [ 1.159s]
writing 'recovery'... OKAY [ 1.914s]
C:\Fastboot>fastboot boot cwm.img
downloading 'boot.img'... OKAY [ 1.039s]
booting... INFOCommand restricted
FAILED (remote failure)
When boot in recovery appears Andy laying down with a red triangle with excalmation and no more , can anyone help me to get recovery running fine, please? Thanks a lot.
yurifabricio said:
Hello, my MB886 is runing a stock ROM 4.1.1 (OTA updated)
Rooted
Unlocked Bootloader
I've tried to flash CWM via Fastboot to install a CM ROM, and I get this:
C:\Fastboot>adb reboot bootloader
C:\Fastboot>fastboot devices
TA30004B86 fastboot
C:\Fastboot>fastboot flash recovery cwm.img
sending 'recovery' (7892 KB)... OKAY [ 1.159s]
writing 'recovery'... OKAY [ 1.914s]
C:\Fastboot>fastboot boot cwm.img
downloading 'boot.img'... OKAY [ 1.039s]
booting... INFOCommand restricted
FAILED (remote failure)
When boot in recovery appears Andy laying down with a red triangle with excalmation and no more , can anyone help me to get recovery running fine, please? Thanks a lot.
Click to expand...
Click to collapse
Why are you trying to boot directly into the recovery IMG that way? Just boot up into system and use "adb reboot recovery" or hold volume up as you turn the phone on.
Sent from my MB886 using Tapatalk
penser said:
Why are you trying to boot directly into the recovery IMG that way? Just boot up into system and use "adb reboot recovery" or hold volume up as you turn the phone on.
Sent from my MB886 using Tapatalk
Click to expand...
Click to collapse
Thanks for you replied, I've tried your tip, and I get a Andy laying down with a red triangle too (but even using key combination, logically)
yurifabricio said:
Thanks for you replied, I've tried your tip, and I get a Andy laying down with a red triangle too (but even using key combination, logically)
Click to expand...
Click to collapse
You'll need to rename /system/etc/install-recovery.sh to install-recovery.sh.bak then re-flash CWM by fast boot.
Sent from my MB886 using Tapatalk
penser said:
You'll need to rename /system/etc/install-recovery.sh to install-recovery.sh.bak then re-flash CWM by fast boot.
Sent from my MB886 using Tapatalk
Click to expand...
Click to collapse
I did what you advised me, but still the same. I do not know if that step what I should have done before flashing the first time? I followed the instructions from CyanogenMod for BM886.
several fastboot and adb commands are restricted on this phone. Anything pertaining to rebooting to recovery doesn't work.
Papahyooie said:
several fastboot and adb commands are restricted on this phone. Anything pertaining to rebooting to recovery doesn't work.
Click to expand...
Click to collapse
All the adb commands I've used [sideload, install, reboot recovery/bootloader] work just fine. Same with fastboot commands, they all work except OEM lock/unlock.
Sent from my MB886 using Tapatalk
read skevydudes guide it will tell you all you need to know
http://forum.xda-developers.com/showthread.php?t=2226527
error unlock bootloader
hola tengo un problema con mi atrix mb886
trate de desbloquear elm bootloader y me aparecio error
dice : flash failure y no enciende
jessesanmart said:
hola tengo un problema con mi atrix mb886
trate de desbloquear elm bootloader y me aparecio error
dice : flash failure y no enciende
Click to expand...
Click to collapse
Thats known as the failure to follow xda rules error. It requires you to try that again, but in english
Sent from my ATRIX-RAZR HD using XDA Free mobile app
unlock bootloader error
hello I have a problem with my atrix MB886 try to unlock bootloader and I appeared Error fastboot reazon: flash failure can I do?
Hi Everyone,
Don't know what I did wrong but at the moment i stucked with a bootloop. I was trying to flash a 4.4 Rom on a Cyanogenmod 4.2.2
Now I can enter in bootloader but not into the recovery. When I try to boot into recovery it simply tries to boot the phone.
Bootloader i unlocked (it says tampered) but S-ON.
Tried to fastboot the recovery of clockworkmod but still can't enter in it.
How I can restore the phone to its original factory image?
Thnaks
It's seems you are not the only one.
Enter bootloader and choose fastboot.
Then run a command prompt in your PC, cd to the fastboot folder and write fastboot flash recovery filename.img
I suggest you download and flash twrp 2.6.3.0
Then check if the recovery has been installed successfully.If yes, go into recovery and type in the command prompt in your PC the following:
Adb push filename.Rom /data/media/0
Filename.zip stands for the Rom you wanna flash. After its done you can flash that file with twrp
Sent from my HTC One using Tapatalk
I think the cache just needs wiping with the command:
fastboot erase cache
Worked for me once or twice
Sent from my HTC One using XDA Premium 4 mobile app
thanks guys,
as i said i already tried to flash the recovery with the fastboot flash command.
I tried CMW and TWRP... but still can't enter into the recovery.
I have to try the erase cache command....
will let you know!
Did you find a solution? I am in the same boat and it is actually quite annoying.
gerazzo said:
thanks guys,
as i said i already tried to flash the recovery with the fastboot flash command.
I tried CMW and TWRP... but still can't enter into the recovery.
I have to try the erase cache command....
will let you know!
Click to expand...
Click to collapse
The_Doctor_Who said:
Did you find a solution? I am in the same boat and it is actually quite annoying.
Click to expand...
Click to collapse
Yes solved for me with the erase cache command and fastboot recovery the latest TRWP
Than i flashed the AR ROM...
bye
gerazzo said:
Yes solved for me with the erase cache command and fastboot recovery the latest TRWP
Than i flashed the AR ROM...
bye
Click to expand...
Click to collapse
Thanks. Unfortunately I cannot boot in to the custom recovery. It skips the recovery and jumps directly to the google screen.
The_Doctor_Who said:
Thanks. Unfortunately I cannot boot in to the custom recovery. It skips the recovery and jumps directly to the google screen.
Click to expand...
Click to collapse
^^^^ fastboot erase cache will solve that
nkk71 said:
^^^^ fastboot erase cache will solve that
Click to expand...
Click to collapse
Unfortunately I've typed fastboot erase cache until I'm blue in the face and it still will not boot into the custom recovery. Trust me, I wish I could get it to work for me.
The_Doctor_Who said:
Unfortunately I've typed fastboot erase cache until I'm blue in the face and it still will not boot into the custom recovery. Trust me, I wish I could get it to work for me.
Click to expand...
Click to collapse
okay, i trust you, can i have a little info on your state:
hboot version
which recovery are you using (name and version please )
and you are unlocked right?
nkk71 said:
okay, i trust you, can i have a little info on your state:
hboot version
which recovery are you using (name and version please )
and you are unlocked right?
Click to expand...
Click to collapse
Sure! H-boot 1.54, s -On, I have tried both locked and unlocked (via fasboot oem lock and unlock). I originally tried CWM touch, then gave TWRP a try. No luck booting to either. I get success on the cmd with loading, but cannot get it into recovery. I select recovery from the fastboot menu and the phone vibrates, then a second later "Google" appears.
Version of recovery:
CWM 6.0.3.1 and and 6.0.4.3
TWRP: 2.6.6.3 m7
The_Doctor_Who said:
Sure! H-boot 1.54, s -On, I have tried both locked and unlocked (via fasboot oem lock and unlock). I originally tried CWM touch, then gave TWRP a try. No luck booting to either. I get success on the cmd with loading, but cannot get it into recovery. I select recovery from the fastboot menu and the phone vibrates, then a second later "Google" appears.
Click to expand...
Click to collapse
make sure bootloader is unlocked, reboot to booloader/FASTBOOT USB (again make sure the top line or 2nd says UNLOCKED), then get latest CWM (just for this exercise) from here: http://forum.xda-developers.com/showthread.php?t=2173863
fastboot erase cache
fastboot flash recovery recovery-clockwork-touch-6.0.4.5-m7ul.img
fastboot erase cache
fastboot reboot-bootloader
copy/paste command prompt output (all of it pls)
---> and try to enter recovery.
let me know what happens.
nkk71 said:
make sure bootloader is unlocked, reboot to booloader/FASTBOOT USB (again make sure the top line or 2nd says UNLOCKED), then get latest CWM (just for this exercise) from here: http://forum.xda-developers.com/showthread.php?t=2173863
fastboot erase cache
fastboot flash recovery recovery-clockwork-touch-6.0.4.5-m7ul.img
fastboot erase cache
fastboot reboot-bootloader
copy/paste command prompt output (all of it pls)
---> and try to enter recovery.
let me know what happens.
Click to expand...
Click to collapse
Sure. Thank you!
Here is my output:
c:\And>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.055s]
finished. total time: 0.056s
c:\And>fastboot flash recovery recovery-clockwork-touch-6.0.4.5-m7ul.img
target reported max download size of 1526722560 bytes
sending 'recovery' (8746 KB)...
OKAY [ 1.175s]
writing 'recovery'...
OKAY [ 0.675s]
finished. total time: 1.852s
c:\And>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.051s]
finished. total time: 0.051s
c:\And>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.042s]
finished. total time: 0.042s
Tried entering recovery. Black screen for a moment, vibration and then "Google"
The_Doctor_Who said:
Sure. Thank you!
Here is my output:
c:\And>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.055s]
finished. total time: 0.056s
c:\And>fastboot flash recovery recovery-clockwork-touch-6.0.4.5-m7ul.img
target reported max download size of 1526722560 bytes
sending 'recovery' (8746 KB)...
OKAY [ 1.175s]
writing 'recovery'...
OKAY [ 0.675s]
finished. total time: 1.852s
c:\And>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.051s]
finished. total time: 0.051s
c:\And>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.042s]
finished. total time: 0.042s
Tried entering recovery. Black screen for a moment, vibration and then "Google"
Click to expand...
Click to collapse
what is "******** Did you mean to fastboot format this partition?" how come I never get that
is your adb sdk newer or older than mine? I'm still using:
Code:
C:\ADB2>adb
Android Debug Bridge version 1.0.29
Question, are you on GPE hboot (the black one) or normal (the white one)?
nkk71 said:
what is "******** Did you mean to fastboot format this partition?" how come I never get that
is your adb sdk newer or older than mine? I'm still using:
Code:
C:\ADB2>adb
Android Debug Bridge version 1.0.29
Question, are you on GPE hboot (the black one) or normal (the white one)?
Click to expand...
Click to collapse
That's interesting. Here is mine:
c:\adb>adb
Android Debug Bridge version 1.0.26
I'm on the GPE black screen.
The_Doctor_Who said:
That's interesting. Here is mine:
c:\adb>adb
Android Debug Bridge version 1.0.26
I'm on the GPE black screen.
Click to expand...
Click to collapse
1- recommend updating adb sdk, mine isnt even the latest, i think latest is something like 1.0.3xx
2- don't know if this will work in GPE hboot, but try "fastboot boot <recovery>.img", it used to work on 1.44, but stopped on 1.54+, maybe on GPE it still works.
nkk71 said:
1- recommend updating adb sdk, mine isnt even the latest, i think latest is something like 1.0.3xx
2- don't know if this will work in GPE hboot, but try "fastboot boot <recovery>.img", it used to work on 1.44, but stopped on 1.54+, maybe on GPE it still works.[/QUOT
I'm updating now. I tried fastboot boot recovery yesterday and it froze the phone.
Click to expand...
Click to collapse
The_Doctor_Who said:
I'm updating now. I tried fastboot boot recovery yesterday and it froze the phone.
Click to expand...
Click to collapse
yeah, it was crapped in 1.54
i'm gonna have to sign off soon, but will check back tomorrow....
BTW: i wouldn't mind if you hit the thanks button on my posts (the useful ones!)
Cheers.
nkk71 said:
yeah, it was crapped in 1.54
i'm gonna have to sign off soon, but will check back tomorrow....
BTW: i wouldn't mind if you hit the thanks button on my posts (the useful ones!)
Cheers.
Click to expand...
Click to collapse
Of course! I appreciate your time today!
nkk71 said:
1- recommend updating adb sdk, mine isnt even the latest, i think latest is something like 1.0.3xx
2- don't know if this will work in GPE hboot, but try "fastboot boot <recovery>.img", it used to work on 1.44, but stopped on 1.54+, maybe on GPE it still works.
Click to expand...
Click to collapse
I think his recovery partition might be corrupt.. @mike1986. wrote an article about corrupt data partitions(http://android-revolution-hd.blogspot.ch/2013/10/fix-data-htc-one.html) I think it was you who sent me that link.. well.. do you know if it is possible to use some of this commands? But we'd have to get into a state where we can use adb..
hi
i just flashed twrp on my phone with fastboot and when i go into recovery the screen is black !!
so i thought may be cwm will work but unfortunately samething happened again !! my phone battery charge is 100% so i don't why is this happening
any help !!
farooq88 said:
hi
i just flashed twrp on my phone with fastboot and when i go into recovery the screen is black !!
so i thought may be cwm will work but unfortunately samething happened again !! my phone battery charge is 100% so i don't why is this happening
any help !!
Click to expand...
Click to collapse
Did you run fastboot erase cache after you flashed the recovery?
@majmoz I did but still on 1st time i flash recovery nothing happened !
farooq88 said:
@majmoz I did but still on 1st time i flash recovery nothing happened !
Click to expand...
Click to collapse
Are you S-ON and is your bootloader unlocked?
Does the black screen have a triangle in it? If so, then you are in stock recovery.
What version of TWRP are you using?
What version of your PC (Win, Mac, Linux) OS are you using?
Could you post the output of the command window with the steps for flashing the recovery?
majmoz said:
Are you S-ON and is your bootloader unlocked?
Click to expand...
Click to collapse
yes its s-on but bootloader is unlocked
majmoz said:
Does the black screen have a triangle in it? If so, then you are in stock recovery.
Click to expand...
Click to collapse
no just clear black screen but when i touch the screen i feel some vibrations
majmoz said:
What version of TWRP are you using?
Click to expand...
Click to collapse
latest version not sure the number
majmoz said:
What version of your PC (Win, Mac, Linux) OS are you using?
Click to expand...
Click to collapse
windows 7
majmoz said:
Could you post the output of the command window with the steps for flashing the recovery?
Click to expand...
Click to collapse
fastboot flash recovery openrecovery-twrp-2.8.0.2-m7.img
farooq88 said:
fastboot flash recovery openrecovery-twrp-2.8.0.2-m7.img
Click to expand...
Click to collapse
Did you output look similar to this?
Code:
C:\ADB3>[COLOR="Blue"]fastboot flash recovery openrecovery-twrp-2.8.0.2-m7.img[/COLOR]
target reported max download size of 1514139648 bytes
sending 'recovery' (9184 KB)...
OKAY [ 1.209s]
writing 'recovery'...
OKAY [ 1.144s]
finished. total time: 2.354s
C:\ADB3>[COLOR="Blue"]fastboot erase cache[/COLOR]
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.120s]
finished. total time: 0.120s
C:\ADB3>[COLOR="Blue"]fastboot reboot-bootloader[/COLOR]
rebooting into bootloader...
OKAY [ 0.160s]
finished. total time: 0.160s
@majmoz they are same
farooq88 said:
@majmoz they are same
Click to expand...
Click to collapse
Here are a couple of options:
Try TWRP 2.6.3.3
Connect your PC to the phone while the phone is in Recovery (Black screen) then type: adb reboot recovery
Try a different computer or Linux
Save your files off of the phone;
-- Lock the bootloader
-- Flash stock firmware
-- Enter stock recovery and perform a factory reset
-- Reboot phone a couple of times
-- Unlock bootloader
-- Flash TWRP
majmoz said:
Here are a couple of options:
Try TWRP 2.6.3.3
Connect your PC to the phone while the phone is in Recovery (Black screen) then type: adb reboot recovery
Try a different computer or Linux
Save your files off of the phone;
-- Lock the bootloader
-- Flash stock firmware
-- Enter stock recovery and perform a factory reset
-- Reboot phone a couple of times
-- Unlock bootloader
-- Flash TWRP
Click to expand...
Click to collapse
@majmoz i used 2.8.0.0 and erased cache cuople times and reboot it and now it entere recovery.
thank you very much and i'm sorry to bothered you for so long my friend.
tbh this is strange never happened for me i opened bootloaders for a lot of friends but this is 1st time i see this problem what do you think is cause of it ??
farooq88 said:
@majmoz i used 2.8.0.0 and erased cache cuople times and reboot it and now it entere recovery.
thank you very much and i'm sorry to bothered you for so long my friend.
tbh this is strange never happened for me i opened bootloaders for a lot of friends but this is 1st time i see this problem what do you think is cause of it ??
Click to expand...
Click to collapse
Gremlins?? Sometimes the programs don't clean up after themselves and they leave corrupted files/bits. That is why you want to erase cache to make it clean. Glad you are back up!!!