twrp and cwm screen is black !! - One (M7) Q&A, Help & Troubleshooting

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!!!

Related

[Q] Can't boot into recovery HTC one

Hi -
Thanks for any help in advance. I'm a bit of a rookie round here, I've rooted and flashed my past 3 HTC phones but taken the easy route every time.
But today, I've used ADB commands to flash the revone binary and unlock and get s-off on my HTC one m7. It took me several tries, but it eventually worked (or at least said successful). So my HBOOT 1.44 says UNLOCKED & S-OFF.
So onto the next step. fastboot flash recovery recoverytwrp.img
...
Another success!
So, I reboot into bootloader and prompt recovery boot like I'm about to get HAM on twrp and flash some superuser files. It shows me a developer screen full of red print saying that it's booting into recovery, and then after a while, it just rebooted back into system.
It does this every time. I reflashed the image, I flashed the stock image, I tried the hansoon tool. each time I can't actually get into the recovery.
So this is where I'm stuck. Why can't I get anywhere with this?
EDIT & ANSWER;
Sprint phone needed Sprint TWRP image
Have you tried
fastboot erase cache
BenPope said:
Have you tried
fastboot erase cache
Click to expand...
Click to collapse
This.
Just do evrything again until you finish installing custom recoveries. Before rebooting, erase the cache with "fastboot erase cache"
ryryzz said:
This.
Just do evrything again until you finish installing custom recoveries. Before rebooting, erase the cache with "fastboot erase cache"
Click to expand...
Click to collapse
Gave that all a shot all over again. Still can't boot into recovery
Is fast boot off?
Use the original cable your One came with, go into bootloader power/vol - then open a cmd window
Now connect the One with your computer, don't use a USB 3.0 connection, and a different one then before.
In bootloader choose fastboot, that should change to fastboot USB
In cmd window point to your fastboot directory where you also copied the recovery to, I would try CWM touch for now.
Type cd c:\fastboot (or what your toolfolder is called)
fastboot erase cache
fastboot flash recovery recovery.img
fastboot erase cache
That installs the recovery, you can select it in bootloader abd boot into it.
Sent from my HTC One using xda premium
---------- Post added at 06:28 PM ---------- Previous post was at 06:23 PM ----------
BenPope said:
Is fast boot off?
Click to expand...
Click to collapse
You mean the fastboot option under Power Settings is unticked when booted up normally?
Sent from my HTC One using xda premium
hardstuffmuc said:
Use the original cable your One came with, go into bootloader power/vol - then open a cmd window
Now connect the One with your computer, don't use a USB 3.0 connection, and a different one then before.
In bootloader choose fastboot, that should change to fastboot USB
In cmd window point to your fastboot directory where you also copied the recovery to, I would try CWM touch for now.
Type cd c:\fastboot (or what your toolfolder is called)
fastboot erase cache
fastboot flash recovery recovery.img
fastboot erase cache
That installs the recovery, you can select it in bootloader abd boot into it.
Sent from my HTC One using xda premium
---------- Post added at 06:28 PM ---------- Previous post was at 06:23 PM ----------
You mean the fastboot option under Power Settings is unticked when booted up normally?
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Same deal. On it's way to booting into recovery it goes blank, resets and reboots into system
C:\adt\sdk\platform-tools>fastboot erase cache
erasing 'cache'...
OKAY [ 0.078s]
finished. total time: 0.078s
C:\adt\sdk\platform-tools>fastboot flash recovery recovery.img
sending 'recovery' (7422 KB)...
OKAY [ 1.139s]
writing 'recovery'...
OKAY [ 0.640s]
finished. total time: 1.778s
C:\adt\sdk\platform-tools>fastboot erase cache
erasing 'cache'...
OKAY [ 0.062s]
finished. total time: 0.062s
C:\adt\sdk\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.047s]
finished. total time: 0.047s
There's the last log - and then on it's way to recovery there's a red disclaimer and a pink text saying "Entering Recovery"...then after 20 seconds it resets
Did you try various recovery (versions) ? May be , you just have corrupted recovery image.
tash2013 said:
Did you try various recovery (versions) ? May be , you just have corrupted recovery image.
Click to expand...
Click to collapse
at this point I've tried stock, twrp and cwm. All with the same results
Jman12000 said:
at this point I've tried stock, twrp and cwm. All with the same results
Click to expand...
Click to collapse
Ok , I see mysterious problem ))
Try, remaining unlocked, go back to s-on (you can always take s-off again) and check your recovery (enter and flashing) under s-on.
tash2013 said:
Ok , I see mysterious problem ))
Try, remaining unlocked, go back to s-on (you can always take s-off again) and check your recovery (enter and flashing) under s-on.
Click to expand...
Click to collapse
Is that something I can do with the revone binary? To be honest, I have no idea how to turn security back on. I can relock it and that may be about it.
I stumbled upon another thread, shares a common theme as my issue, but with a different twist. Using a superboot.img as a rooting method instead of flashing it via recovery. It somewhere says that the boot.img needs to be flashed as well, however I can't find a decent boot.img to flash. The superboot tool seems like unproven territory right now.
Here's the other thread, I've leafed through it and found no determinable answer for my particular issue.
http://forum.xda-developers.com/showthread.php?p=39852757#post39852757
Do not apply revone to return s-on!
Use fastboot by "fastboot oem writesecureflag 3".
Be convinced that bootloader is unlocked before return to s-on.
Regarding your issue: I suspect that a certain code in HBOOT tries to install TAMPERED flag when sees custom recovery, but isn't able to do it correctly because s-off (bypassing security) and a certain mistake or exception conducts to reset phone.
Jman12000 said:
Hi -
Thanks for any help in advance. I'm a bit of a rookie round here, I've rooted and flashed my past 3 HTC phones but taken the easy route every time.
But today, I've used ADB commands to flash the revone binary and unlock and get s-off on my HTC one m7. It took me several tries, but it eventually worked (or at least said successful). So my HBOOT 1.44 says UNLOCKED & S-OFF.
So onto the next step. fastboot flash recovery recoverytwrp.img
...
Another success!
So, I reboot into bootloader and prompt recovery boot like I'm about to get HAM on twrp and flash some superuser files. It shows me a developer screen full of red print saying that it's booting into recovery, and then after a while, it just rebooted back into system.
It does this every time. I reflashed the image, I flashed the stock image, I tried the hansoon tool. each time I can't actually get into the recovery.
So this is where I'm stuck. Why can't I get anywhere with this?
Click to expand...
Click to collapse
try to install recovery again
you can download recovery from here
http://www.clockworkmod.com/rommanager
tash2013 said:
Do not apply revone to return s-on!
Use fastboot by "fastboot oem writesecureflag 3".
Be convinced that bootloader is unlocked before return to s-on.
Regarding your issue: I suspect that a certain code in HBOOT tries to install TAMPERED flag when sees custom recovery, but isn't able to do it correctly because s-off (bypassing security) and a certain mistake or exception conducts to reset phone.
Click to expand...
Click to collapse
Code:
C:\Users\Justin\Desktop\adt-bundle-windows-x86_64-20130522\sdk\platform-tools>ad
b reboot bootloader
C:\Users\Justin\Desktop\adt-bundle-windows-x86_64-20130522\sdk\platform-tools>fa
stboot oem writesecureflag 3
...
(bootloader) writesecureflag: partitions siganture pass
OKAY [ 1.665s]
finished. total time: 1.666s
C:\Users\Justin\Desktop\adt-bundle-windows-x86_64-20130522\sdk\platform-tools>fa
stboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.045s]
finished. total time: 0.046s
C:\Users\Justin\Desktop\adt-bundle-windows-x86_64-20130522\sdk\platform-tools>ad
b reboot bootloader
error: device not found
C:\Users\Justin\Desktop\adt-bundle-windows-x86_64-20130522\sdk\platform-tools>ad
b reboot bootloader
So here's where I'm at
Right now I've done all the above, I've got a *** TAMPERED *** and ***UNLOCKED*** and S-ON
I've been through 4 boots, 2 of them attempts to get to recovery. Now instead of recovery rebooting into system, it just shuts off now.
Where do you think I go from here?
I've just skimmed through the posts and didn't see this mentioned
If you are still able to boot into the system, download either GooManager (for TWRP) or RomManager (for CWM) and use either of those apps to install recovery. Once done, you can use the app to boot into recovery instead of the fancy ADB commands or button presses.
Jman12000 said:
So here's where I'm at
Right now I've done all the above, I've got a *** TAMPERED *** and ***UNLOCKED*** and S-ON
I've been through 4 boots, 2 of them attempts to get to recovery. Now instead of recovery rebooting into system, it just shuts off now.
Where do you think I go from here?
Click to expand...
Click to collapse
This topic seems like your problem :
http://forum.xda-developers.com/showthread.php?t=2328983&page=3
The man resolved this by flashing the same recovery many many times.
And more.. Please print here your recovery flashing process
tash2013 said:
This topic seems like your problem :
http://forum.xda-developers.com/showthread.php?t=2328983&page=3
The man resolved this by flashing the same recovery many many times.
And more.. Please print here your recovery flashing process
Click to expand...
Click to collapse
So both that method through ADB shell and GooManager require root. Every rooting method requires recovery, so I don't have perm root yet.
You quoted me, but answered not to me.
Read a post #26 from my link above
Possible Solution
Hello I have the same problem and the solution was:
1. Settings - Energy- Fastboot uncheked
2. Flash Recovery usin one all-in-one-kit
3. Erase Cache 3 times
4. Unplug to PC, and load into system normal
5. Turn off phone - via stock menu NOT FORCE TO OFF pressing the off button
6. Wait 2 minutes, and boot into HBOOT - Power + Volume(-) pressing
7. Choose recovery
Ready.. May these work for you! Let me know

Bootloop - Recovery not working

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..

Help htc butterfly s , iam an expert in android but i failed :(

hii ...
i have HTC butterfly s phone is boot looping ,,,
issue :
when entering OS i can see the lock screen for 3 seconds then reboot.
solutions tried :
1- tried to wipe from TWRP recovery when it reaches /data >>> reboot.
2- tried to install another ROM without wiping >>>> reboot
3- tried to install CWM recovery , it says completed in fastboot (CMD) but recovery is not changing.
4- tried to lock the boot loader again , it says no such file or directory .
5- tried to boot in safemode but i see the lock screen for 3 seconds then reboot
iam stuck ... please help
thank you
hello
it happened to me the same, I just download it stock rom that is here, you have to see the version of your phone to know which is for yours.
greetings and good luck
all credits to the creator of the post
http://forum.xda-developers.com/showthread.php?t=2663295
GAVANA said:
hello
it happened to me the same, I just download it stock rom that is here, you have to see the version of your phone to know which is for yours.
greetings and good luck
all credits to the creator of the post
http://forum.xda-developers.com/showthread.php?t=2663295
Click to expand...
Click to collapse
hi .. thanks for reply ,,,
i downloaded stock rom 2.21 and tried to flash it from recovery when it tries to install the rom when it reaches to writing /data phone reboots
you mean something else ?
thanks ...
i want to add one thing ,,,
i have TWRP recovery 2.6.0.0 and i want to change it to CWM , i try to install from fastboot and it says successful but when i go into recovery its not changed !!!!!!
recovery recovery.img
sending 'recovery' (12364 KB)... OKAY [ 1.794s]
writing 'recovery'... OKAY [ 0.983s]
finished. total time: 2.777s
hwoarang626 said:
i want to add one thing ,,,
hello
at first I was the same with the recovery, but install this and it worked well, and use that version of android stock for now
but if you want to upgrade later (OTAS), you would have to have stock recovery and unroot your device, saludos
http://forum.xda-developers.com/showthread.php?t=2730482 .
i have TWRP recovery 2.6.0.0 and i want to change it to CWM , i try to install from fastboot and it says successful but when i go into recovery its not changed !!!!!!
recovery recovery.img
sending 'recovery' (12364 KB)... OKAY [ 1.794s]
writing 'recovery'... OKAY [ 0.983s]
finished. total time: 2.777s
Click to expand...
Click to collapse
hello
at first I was the same with the recovery, but install this and it worked well, and use that version of android stock for now
but if you want to upgrade later (OTAS), you would have to have stock recovery and unroot your device
regards
http://forum.xda-developers.com/showthread.php?t=2730482
its the same ,,, i tried to install the recovery you gave me but it did not install the recovery , Iam still stuck with a recovery that is not doing anything .
thanks
one more point ,,, i noticed that my /system is empty ...
hwoarang626 said:
one more point ,,, i noticed that my /system is empty ...
Click to expand...
Click to collapse
Since no one else is really helping you I will.
So what I gathered is your Rom bootloops and you've tried installing stock Rom but still no luck so you want to switch recoveries but you can't get twrp to flash...?
1. Are you S-Off or S-On? If you are s-on you must flash boot.img with this command
Code:
fastboot flash boot boot.img
2. To flash a recovery made for your device you must place it in fastboot and enter this
Code:
fastboot flash recovery recovery.img
3. Place Rom on internel storage if you choose cwm because it doesn't support external sdcard like twrp. For latest twrp, message @kairi_zeroblade... If you can't place on internal with cwm then you must do a sideload with the Rom same goes for twrp.
Want to support InsertCoin? Just get our donate key
xXminiWHOOPERxX said:
Since no one else is really helping you I will.
So what I gathered is your Rom bootloops and you've tried installing stock Rom but still no luck so you want to switch recoveries but you can't get twrp to flash...?
1. Are you S-Off or S-On? If you are s-on you must flash boot.img with this command
Code:
fastboot flash boot boot.img
2. To flash a recovery made for your device you must place it in fastboot and enter this
Code:
fastboot flash recovery recovery.img
3. Place Rom on internel storage if you choose cwm because it doesn't support external sdcard like twrp. For latest twrp, message @kairi_zeroblade... If you can't place on internal with cwm then you must do a sideload with the Rom same goes for twrp.
Want to support InsertCoin? Just get our donate key
Click to expand...
Click to collapse
thank you for your help ,,,
im S-ON
fastboot flash boot boot
.img
< waiting for device >
sending 'boot' (6104 KB)...
OKAY [ 0.830s]
writing 'boot'...
OKAY [ 0.590s]
finished. total time: 1.420s.
fastboot flash recovery
cwm6.0.4.5.img
sending 'recovery' (12364 KB)...
OKAY [ 1.430s]
writing 'recovery'...
OKAY [ 0.990s]
finished. total time: 2.420s
i did what you said but nothing changed im still on TWRP recovery 2.6.0.0 and my room is boot looping
hwoarang626 said:
thank you for your help ,,,
im S-ON
fastboot flash boot boot
.img
< waiting for device >
sending 'boot' (6104 KB)...
OKAY [ 0.830s]
writing 'boot'...
OKAY [ 0.590s]
finished. total time: 1.420s.
fastboot flash recovery
cwm6.0.4.5.img
sending 'recovery' (12364 KB)...
OKAY [ 1.430s]
writing 'recovery'...
OKAY [ 0.990s]
finished. total time: 2.420s
i did what you said but nothing changed im still on TWRP recovery 2.6.0.0 and my room is boot looping
Click to expand...
Click to collapse
Not sure if you can enter this command without a-off but try
Code:
fastboot erase cache
Then repeat the previous post....
If that doesn't work I'd try firewaters universal s-off tool and obtain s-off and try that command or see if it fixes your issues with your device. if that fails your best bet would be to ruu.. if you can't do that either you got a useless device till s-off exploit Is found if that's the reason why it's messing up.... Or donate it to someone who could fix it (me)
Want to support InsertCoin? Just get our donate key
xXminiWHOOPERxX said:
Not sure if you can enter this command without a-off but try
Code:
fastboot erase cache
Then repeat the previous post....
If that doesn't work I'd try firewaters universal s-off tool and obtain s-off and try that command or see if it fixes your issues with your device. if that fails your best bet would be to ruu.. if you can't do that either you got a useless device till s-off exploit Is found if that's the reason why it's messing up.... Or donate it to someone who could fix it (me)
Want to support InsertCoin? Just get our donate key
Click to expand...
Click to collapse
i tried this and no luck ,,,
actually i tried every thing but the problem is that the data does not change in the phone ,, i even formated (real format fsck) to /data and it was showing its empty but after reboot everything went back ,,, iam fixing android phones since htc desire but never faced anything like this ,,,
thank you for your help ,, and what you mean by donate and get it fixed ?
hwoarang626 said:
i tried this and no luck ,,,
actually i tried every thing but the problem is that the data does not change in the phone ,, i even formated (real format fsck) to /data and it was showing its empty but after reboot everything went back ,,, iam fixing android phones since htc desire but never faced anything like this ,,,
thank you for your help ,, and what you mean by donate and get it fixed ?
Click to expand...
Click to collapse
Seem like you fried your "/data" partition from what you just mentioned above. The only way I could see you fix is ruu. Cause HTC won't fix it if you send it in with a custom recovery at which you can't change.
And what I meant is since the device is rendered completely useless, unless you can get a run to ruu. You'd donate it to me this way i could try and fix it...
Sent from my HTC0P4E1 using Tapatalk
xXminiWHOOPERxX said:
Seem like you fried your "/data" partition from what you just mentioned above. The only way I could see you fix is ruu. Cause HTC won't fix it if you send it in with a custom recovery at which you can't change.
And what I meant is since the device is rendered completely useless, unless you can get a run to ruu. You'd donate it to me this way i could try and fix it...
Sent from my HTC0P4E1 using Tapatalk
Click to expand...
Click to collapse
i think im facing the same problem here, do u know where we can find the RUU, I searched the whole internet and i could not find, im ready to donate if u fix my problem and provide me with the RUU.
Regards
mr_wehbe said:
i think im facing the same problem here, do u know where we can find the RUU, I searched the whole internet and i could not find, im ready to donate if u fix my problem and provide me with the RUU.
Regards
Click to expand...
Click to collapse
There is no RUU for this phone, as far as I know. The closest thing to RUU is flashing everything by hand, but this seems to have failed in this case, unfortunately.

[Q] TWRP Tries to load but fails

Hi, I have an htc one m7 verizon. I am currently running nusense 7.8. I wanted to update to v8.0. Anyway I go to recovery from the menu and the screen goes black like it is going to the team win logo but it goes back to the white screen that says entering recovery. It stays on that screen until I power plus volume down. I am confused because twrp loaded fine. I have tried cwm as well. no recovery software will load. The phone boots to nusense 7.8 fine. Anyone know what would cause recovery software not to load?
Try flashing the latest version of TWRP through Fastboot to see if the issue resolves. Make sure you use TWRP for the Verizon M7.
MarkBell said:
Try flashing the latest version of TWRP through Fastboot to see if the issue resolves. Make sure you use TWRP for the Verizon M7.
Click to expand...
Click to collapse
I agree re-flash TWRP for Verizon
http://techerrata.com/browse/twrp2/m7vzw
fastboot flash recovery openrecovery-twrp-2.8.0.1-m7wlv.img
fastboot erase cache
fastboot reboot-bootloader
Thanks for throwing up the link clsA. I was about to do that a minute ago when my phone died. Lol.
I will give twrp 2.8.0.1 a try. I have tried several versions but not that one.
fastboot flash recovery openrecovery-twrp-2.8.0.1-m7wlv.img
fastboot erase cache
fastboot reboot-bootloader[/QUOTE]
I tried the above and I am still getting stuck with the white screen green htc logo and entering recovery at the top. I am happy with nusense 7.8 except for youtube not working. I do have some backups that are useless when twrp will not load. Maybe it is time to ruu this phone.
I installed the ruu VZW.M7.5.28.605.2.PN0731IMG.zip. It installed ok. I am still s off and rooted. I used flashify to flash twrp 2.8.0.1. My phone still will not load a recovery app.......I wonder if this is a hardware issue?
Anybody have any ideas? everything on my phone works accept the ability to load the recovery software. Like I said I was able to install an RUU file with fastboot. I would really like to get twrp working so I can backup and restore again.
I think I found my issue. I am pretty sure my recovery partition is hosed. The command fastboot format recovery fails. I get this message:
Formatting is not supported for filesystem with type 'raw.
Anybody know how to rebuild a corrupted recovery partition?
vaping redhead said:
I think I found my issue. I am pretty sure my recovery partition is hosed. The command fastboot format recovery fails. I get this message:
Formatting is not supported for filesystem with type 'raw.
Anybody know how to rebuild a corrupted recovery partition?
Click to expand...
Click to collapse
recovery partition is a raw partition, the only EXT4 partitions are /system, /cache, and /data
can you copy/paste your command prompt output as you do the fastboot commands that clsA gave you.
nkk71 said:
recovery partition is a raw partition, the only EXT4 partitions are /system, /cache, and /data
can you copy/paste your command prompt output as you do the fastboot commands that clsA gave you.
Click to expand...
Click to collapse
Here you go.
c:\adb>fastboot flash recovery openrecovery-twrp-2.8.0.1-m7wlv.img
target reported max download size of 1514139648 bytes
sending 'recovery' (9596 KB)...
OKAY [ 1.071s]
writing 'recovery'...
OKAY [ 0.862s]
finished. total time: 1.935s
c:\adb>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.511s]
finished. total time: 0.512s
c:\adb>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.041s]
finished. total time: 0.041s
I have tried flashify, and also an ruu version of twrp. still no go.
Have you tried turning s on, relocking bootloader, running RUU, doing factory reset in Stock recovery and then unlocking and installing TWRP? It is worth a shot I assure you. I had problems with TWRP about a month back and this solved it for me.

Issues with flashing TWRP to tablet

I am trying to go through the process of flashing a custom recovery so that I can get off of stock and on to a custom rom. I have gone through the following steps:
1) downloaded the latest drivers
2) downloaded the latest version of fastboot
3) downloaded twrp 2.8.1.0 and checked the MD5 for the program
4) enabled the usb debugging, signed on as an administrator in my pc, and am using a 2.0 usb port
5) have verified the conenction between tablet and PC.
I get the following result:
C:\>fastboot devices
15C3E100910000000XXXXXXXX fastboot (I edited out a few numbers and replaced them with with x's, but got a pure result)
C:\>fastboot -i 0x0B05 flash recovery twrp.blob
target reported max download size of 643825664 bytes
sending 'recovery' (7024 KB)...
OKAY [ 0.964s]
writing 'recovery'...
OKAY [ 0.241s]
finished. total time: 1.213s
C:\>fastboot reboot
rebooting...
finished. total time: 0.021s
The recovery is not actually flashing over to the device. When I attempt the flash I do a fastboot reboot and power down afterwards, then try to boot back up to the recovery and instead I get the bried vision of the android and the blue bar underneath before it's promptly replaced by the dead android. The twrp.blob file is in the same directory as fastboot. I have tried deleting and re-downloading both the blob file and the drivers. I have tried using 2.8.0.1 and 2.8.1.0. Because TWRP wasn't working I tried flashing CWM and got exactly the same result. There doesn't seem to be an issue with the cable, since I can move other forms of data between the devices with no issue. I'm beating my head against the wall here, and am hoping that you guys might be able to provide me with some direction as to what else I might try/look for. Thanks all.
Are you sure you are using the correct recovery for your device? There is no version of TWRP that works with the TF701T.
Sleeepy2 said:
Are you sure you are using the correct recovery for your device? There is no version of TWRP that works with the TF701T.
Click to expand...
Click to collapse
I had been advised that the version for the TF700 would also work with the TF701T. However, I did use a CWM version specific to the TF701T with the same result you saw in the command window in my OP.
talion777 said:
I had been advised that the version for the TF700 would also work with the TF701T. However, I did use a CWM version specific to the TF701T with the same result you saw in the command window in my OP.
Click to expand...
Click to collapse
I am not sure who told you that but it is 100% wrong.
I am also not sure what the commands that you are sending are however you should just be doing
fastboot flash recovery recovery.img
Get the recovery from this link
http://droidbasement.com/asus/tf701t/recovery/
Sleeepy2 said:
I am not sure who told you that but it is 100% wrong.
I am also not sure what the commands that you are sending are however you should just be doing
fastboot flash recovery recovery.img
Get the recovery from this link
http://droidbasement.com/asus/tf701t/recovery/
Click to expand...
Click to collapse
Thanks Sleeepy, but as I mentioned in the OP I did the flash for the CWM recovery already, using exactly the link you sent me, with the exact same commands, and with the same results. No go.
P.P.S. - also tried juggling around the MTP and PTP modes (plug/unplug while on/off) to ensure recognition and it seems fine both ways. Someone else had said they freed up their drivers that way but it made no difference on my end.
P.S. - Here, just so that you see, here are the command window results for th CWM recovery, just for clarity's sake:
C:\adb 2>fastboot devices
15C3E100910000000XXXXXXXX fastboot
C:\adb 2>fastboot flash recovery recovery.img
target reported max download size of 643825664 bytes
sending 'recovery' (6646 KB)...
OKAY [ 0.910s]
writing 'recovery'...
OKAY [ 0.230s]
finished. total time: 1.140s
C:\adb 2>fastboot reboot
rebooting...
finished. total time: 0.020s
C:\adb 2>
That's really odd.
I just downloaded the most recent version and tried re-flashing just to make sure and I had no issues...
Can you boot the recovery without flashing it?
fastboot boot recovery.img
Sorry, this defiantly not strong point but I will try to help.
Sleeepy2 said:
That's really odd.
I just downloaded the most recent version and tried re-flashing just to make sure and I had no issues...
Can you boot the recovery without flashing it?
fastboot boot recovery.img
Sorry, this defiantly not strong point but I will try to help.
Click to expand...
Click to collapse
yes, I can boot the recovery. Am I able to use the temp image to install the recovery into the tablet, or to import the files I need to do so?
talion777 said:
yes, I can boot the recovery. Am I able to use the temp image to install the recovery into the tablet, or to import the files I need to do so?
Click to expand...
Click to collapse
The temp image will work just like normal.
Sleeepy2 said:
The temp image will work just like normal.
Click to expand...
Click to collapse
except that I will always need to be connected to my PC to use it. How do I actually make that the default recovery in my tablet? It just seems bizarre to me that I can boot the image but that I can't flash it. Also, assuming I used the image to flash a custom ROM what happens when the temp image is shut off and the recovery reverts to stock? Would the ROM work with a stock recovery?
Was able to use the CWM image to install SuperSU and root the tablet. Still can't get the recovery to flash over.
Wait... what version of bootloader do you have?
You are unlocked and updated to the most recent ASUS version right...
Sleeepy2 said:
Wait... what version of bootloader do you have?
You are unlocked and updated to the most recent ASUS version right...
Click to expand...
Click to collapse
I'm on 11.4.1.17, and yes I'm on the latest ASUS update.
Damn... that was my last guess. You need to get the attention of someone smarter than me like pershoot or berndblb
Sorry I can't help any better.
Thanks Sleeepy, you've already been a big help and I really appreciate the effort!
talion777 said:
Thanks Sleeepy, you've already been a big help and I really appreciate the effort!
Click to expand...
Click to collapse
Just for kicks try to flash the CWM image with this:
Code:
fastboot -i 0x0B05 flash recovery recovery.img
The vendor ID should not be necessary - but it certainly wouldn't hurt to try....
And post the exact output please.
berndblb said:
Just for kicks try to flash the CWM image with this:
Code:
fastboot -i 0x0B05 flash recovery recovery.img
The vendor ID should not be necessary - but it certainly wouldn't hurt to try....
And post the exact output please.
Click to expand...
Click to collapse
You sir, would appear to be a genius. CWN successfully flashed to the tab. Excellent! Thanks so very much to both you and Sleeepy for your help. This was driving me absolutely bananas!
berndblb said:
Just for kicks try to flash the CWM image with this:
Code:
fastboot -i 0x0B05 flash recovery recovery.img
The vendor ID should not be necessary - but it certainly wouldn't hurt to try....
And post the exact output please.
Click to expand...
Click to collapse
God damn it. You step in with one comment and boom, like magic it works
And @talion777 glad you've got it working now
Sleeepy2 said:
God damn it. You step in with one comment and boom, like magic it works
And @talion777 glad you've got it working now
Click to expand...
Click to collapse
A lucky guess.. LOL
Actually I worked with talion on the Transformer forums on his problem, so it was not quite as magical as it may sound. [emoji56]

Categories

Resources