hey guy's
After a faild attempt ot install CM10 on my phone
Im getting "this build is for development bla bla bla..." massage,
now, Im trying to go back to recovery mood but(!) there's this horrifying triangle with exclamation mark that take's me right back to the
"this build etc..." massage.
is there anything that i can do?
or I should just toss my device into the toilet?
I'm not 100% sure but somehow u deleted your recovery (twrp or cwm) if this is the problem Cuz I don't know 100% if it is this u need to flash the recovery again there are some ways u can do this
Go into the bootloader and try flashing recovery again using ur pc like u did before
Fastboot flash recovery (name of file). Img
That should install the recovery again then if that works u can Adb push a rom onto the phone or mount usb storage and put a rom into the phone and boot up again
Sent from a man, using a mobile phone
10X my friend,i tried what you said and it didn't worked very well for me.
iv'e written "flastboot flash recovery boot.img"
and it said that the recovery was successfully recovered but the circle of the massage is still exist :/
although there is no red triangle anymore
thank you for trying to help me.
Vijence said:
iv'e written "flastboot flash recovery boot.img"
Click to expand...
Click to collapse
boot.img is not a recovery image.
It should be something like recovery-twrp.img or recovery-cwm.touch.img or something similar.
Do a quick google search and download cwm touch and flash how I told u above file name should be something like member posted above
Sent from a man, using a mobile phone
Related
Hi guys,
A little help would be appreciated here as I think i've bricked my SNS just now..
I was following this guide here: http://forum.xda-developers.com/showthread.php?t=878446 in an attempt to flash clockworkmod to then flash something else however:
I get to step 14 after booting into recovery and a whole bunch of e:/ errors are shown, mainly around the Cache when in the cwm recovery screen.
I attempted to flash the stock ROM as per this thread: http://forum.xda-developers.com/showthread.php?t=1063664 (Android 2.3.6/GRK39F/XXKF1 Radio/KA3 Bootloader)
However this error'd and went back to the cwm screen with the e:/ errors.
The phone will now not boot past the Google logo with the unlocked padlock on the screen.
Any ideas atall? I've tried factory wipe/cache/devlik wipe ect but the errors are still showing?
Thanks in advanced!
i had experienced same problem " E:/ errors"
try use newer or older version of recovery , that's how i solved it ...
can you still be able to enter fastboot ? if so , you can flash new recovery img via adb
if you can't ,that's gonna be kinda problem , i suggest you try Odin ...although it could be little more complicated then recovery
qtwrk said:
i had experienced same problem " E:/ errors"
try use newer or older version of recovery , that's how i solved it ...
can you still be able to enter fastboot ? if so , you can flash new recovery img via adb
if you can't ,that's gonna be kinda problem , i suggest you try Odin ...although it could be little more complicated then recovery
Click to expand...
Click to collapse
Thanks for replying.. How do I get into Fastboot if it doesn't boot though? + what command do I use to get there from a Mac?
I've used odin before so am aware of how it works, but wouldn't know which files to flash if you know what I mean?
Edit: Im using cwm 3.0.0 by the way, not sure if that helps?
adaimespechip said:
Thanks for replying.. How do I get into Fastboot if it doesn't boot though? + what command do I use to get there from a Mac?
I've used odin before so am aware of how it works, but wouldn't know which files to flash if you know what I mean?
Edit: Im using cwm 3.0.0 by the way, not sure if that helps?
Click to expand...
Click to collapse
To enter fastboot when phone is off just hold the volume up button and the power button at the same time
Sent from my Google Nexus S using xda premium
smok3thekid said:
To enter fastboot when phone is off just hold the volume up button and the power button at the same time
Sent from my Google Nexus S using xda premium
Click to expand...
Click to collapse
Oh! Yes sorry, I can do that indeed..
Hey everyone,
Basically I was trying to flash a new ROM onto an old Nexus S of mine and when I tried to boot into recovery there was just a black screen. I pressed the power button and a single line saying "Clockwork mod Recovery" and the version number popped up. I assumed that the recovery must've been corrupted so I erased it and installed the latest version using fastboot which seemed to work fine.
Now whenever I try to boot into recovery I just get a blank screen with nothing else. I've tried using other recovery images such as twrp but the same problem happened, I just get the background wallpaper/image and nothing else.
I searched the forums and apparently people were having this issue earlier on when the i9023 was first released but now most custom recoveries are supposed to work with both i9020 and i9023.
Also the touch buttons light up and vibrate whenever I touch them when I'm in recovery mode.
Any help to this problem would be greatly appreciated as atm I have an old ROM which is buggy as hell and I need to get rid of it.
Cheers!
I had the same Issue. If you can boot into the rom, you can try to download the rommanager-app and install the recovery from there.
Hey I tried that already that and instead of booting into recovery it just went into the bootloader and said "No Recovery or Bootloader found".
Any other ideas?
Did you clicked the first point in rommanager? Install recovery, or you only hit the second button reboot into recovery?
Sent from my Full Android on Crespo using XDA App
Hey
I have the i9023 and I install rom manager. install CWM and if I reboot into recovery it works and I get in to CWM recovery.. but after reboot into os.. if I go into Rom manager and reboot to recovery it dont work? I just get the android figur and a "!".. then I just can Power + vol up and I'm in bootloader recovery..
Do I have to install CWM every time i want to use it? and can't I access CWM on boot op ?
sorry for my bad English
Normaly you have to flash the recovery only once.
Try to flash the newer clockwork-recovery with fastboot.
http://forum.xda-developers.com/showthread.php?t=988686
Alfiedk: You need to get rid of this file:
/system/etc/install-recovery.sh
As it re-installs the stock recovery every boot.
I think you can download any custom ROM for your phone, and flash it in CWM recovery, this will also solve the problem
Edit: Did you unlock the phone? Have you tried fastboot oem unlock?
Sent from my SNES
bedalus said:
Alfiedk: You need to get rid of this file:
/system/etc/install-recovery.sh
As it re-installs the stock recovery every boot.
I think you can download any custom ROM for your phone, and flash it in CWM recovery, this will also solve the problem
Edit: Did you unlock the phone? Have you tried fastboot oem unlock?
Sent from my SNES
Click to expand...
Click to collapse
I havent unlock my phone, but I can get in to bootloader is it then necessary to unlock ?
I try to delete the /install-recovery.sh
Yes you need to unlock your bootloader, if you dont want to reflash it all the time.
Sent from my Full Android on Crespo using XDA App
Xziped said:
Yes you need to unlock your bootloader, if you dont want to reflash it all the time.
Sent from my Full Android on Crespo using XDA App
Click to expand...
Click to collapse
Then it must be unlock as default.. I havent unlock it.. just delete the install install-recovery.sh and it works every time now.
now I just have to find a ROM to try..
Xziped said:
Did you clicked the first point in rommanager? Install recovery, or you only hit the second button reboot into recovery?
Sent from my Full Android on Crespo using XDA App
Click to expand...
Click to collapse
Yes I made sure I selected install clockwork mod. Like I said the problem isn't the same when I do this, instead of a blank screen, when I boot into recovery it goes straight to fastboot and tells me that I don't have a recovery image installed at all...
Simultaneity said:
Yes I made sure I selected install clockwork mod. Like I said the problem isn't the same when I do this, instead of a blank screen, when I boot into recovery it goes straight to fastboot and tells me that I don't have a recovery image installed at all...
Click to expand...
Click to collapse
what happens when you try to temporary boot into the recovery?
instead of "fastboot flash recovery recovery.img", try to "fastboot boot recovery.img"
Just look for an recovery.img that works temporary and then try to flash it permanently.
I'll try it and get back to you Xziped. If anyone else can think of any other ideas please just throw'em at me, I'm willing to try anything!
Yeah no help there either. It does the exact same thing temporarily booting into a recovery that it did when I actually had it installed on the phone :\.
I updated ROM manager to the latest and tried installing CWM with that but to no avail. It still says that there is no recovery installed when I do that.
Simultaneity said:
Yeah no help there either. It does the exact same thing temporarily booting into a recovery that it did when I actually had it installed on the phone :\.
I updated ROM manager to the latest and tried installing CWM with that but to no avail. It still says that there is no recovery installed when I do that.
Click to expand...
Click to collapse
Sorry but if not even the temporary recovery boots up, i dont know what else we can do
did you try some of the older recoverys? is your bootloader unlocked?
I haven't tried an older recovery and my bootloader is unlocked.
could it be a problem with my computer as opposed to the phone itself? As in my computer is messing up when trying to flash the recovery?
I've also noticed now that when I boot into fastboot mode the menu just locks up and doesn't respond to anything. Sometimes I have to pull the battery and other times it'll start responding after randomly pressing the power key a lot of times...
I'll try an older recovery next
Simultaneity said:
I haven't tried an older recovery and my bootloader is unlocked.
could it be a problem with my computer as opposed to the phone itself? As in my computer is messing up when trying to flash the recovery?
I've also noticed now that when I boot into fastboot mode the menu just locks up and doesn't respond to anything. Sometimes I have to pull the battery and other times it'll start responding after randomly pressing the power key a lot of times...
I'll try an older recovery next
Click to expand...
Click to collapse
Use Odin, that might solve your problems. Search for the Nexus S version of Odin in the Dev section here.
khartaras said:
Use Odin, that might solve your problems. Search for the Nexus S version of Odin in the Dev section here.
Click to expand...
Click to collapse
There's a version of Odin for the Nexus S!?!? I'll look into that straight away thanks!
Simultaneity said:
There's a version of Odin for the Nexus S!?!? I'll look into that straight away thanks!
Click to expand...
Click to collapse
Just look @ http://www.samfirmware.com/ .
There you should find all you need
Sent from my Full Android on Crespo using XDA App
I had switched off my phone for some days and switched it on today. the phone wont boot, gets stuck at htc logo. I CAN go into bootloader but when i try to get into recovery, i get a blank screen. please help
Sandesh7 said:
I had switched off my phone for some days and switched it on today. the phone wont boot, gets stuck at htc logo. I CAN go into bootloader but when i try to get into recovery, i get a blank screen. please help
Click to expand...
Click to collapse
same problem here
Fellas try flashing another recovery. Or download again this one that you currently have and flash this again
Which recovery?? Twrp 2.5??
ғг๏๓ ҭђє ғเรђ™
no cwm.
tried flashing both twrp and cwm. still giving me a blank screen when i try to boot into recovery
ok im going to try to go back to ruu and flash recovery again. can some1 give me the link to the thread containing all the ruu?
No need to flash the RUU.. Just reflash the recovery using
Code:
fastboot flash recovery recovery.img
yeah, when i tried that and it says fastboot is not recognized as internal or external command. :\
Sandesh7 said:
yeah, when i tried that and it says fastboot is not recognized as internal or external command. :\
Click to expand...
Click to collapse
That means fastboot is not installed... Or is not recognized..
Go to the original android development section, and download fastboot for windows from the twrp recovery thread..
And also download twrp 2.5.0.0 from the same thread(bith links are in the 1st post)..
Extract both zips in a folder, then from cmd prompt, navigate to that folder, and from there, run
Code:
fastboot devices
fastboot flash recovery recovery.img
If you have the android sdk installed, run an update, to get the newest version of fastboot(not needed) and then run the "fastboot flash.." command..
ғг๏๓ ҭђє ғเรђ™
oh I really appreciate the response will try this and report by tomorrow.
yeah did what you said. but it gets stuck at the teamwin logo
nothing seems to work. please help!
Sandesh7 said:
nothing seems to work. please help!
Click to expand...
Click to collapse
Try again if it doesnt work ... Sometimes after a freshly flashing the recovery it gets stuck at teamwin splashscreen.. then just remove battery and by using the power and vol button combo boot into bootloader and then into recovery. If its still getting stuck at teamwin logo.. try redownloading the recovery.img.. this time from the thread..and flash it again.. if it still doesnt work .. then go to the Rooting tutorial by jaggyjags and flash the A310e recovery using the bat file.. That must do the trick.
when i reflashed and tried to go into recovery, first it goes to splashscreen then suddenly goes blank and then comes back to splashscreen and gets stuck there. when i tried the jaggyjags recovery it goes blank. how could have something gone so wrong just coz i switched off my phone for a few days? i was running cm9 build 14 and yannou cwm5. now nothing seems to work. any other suggestions?
Sandesh7 said:
when i reflashed and tried to go into recovery, first it goes to splashscreen then suddenly goes blank and then comes back to splashscreen and gets stuck there. when i tried the jaggyjags recovery it goes blank. how could have something gone so wrong just coz i switched off my phone for a few days? i was running cm9 build 14 and yannou cwm5. now nothing seems to work. any other suggestions?
Click to expand...
Click to collapse
Try removing SD card and booting into recovery. If it enters into recovery fully , electrocute your SDcard by putting it back in,while inside recovery ,then do what you have to.
If all doesn't work ,could be a burnt recovery ..You May try this.. not sure about exact code.
Code:
fastboot boot recovery /sdcard/recovery.img
You need twrp 2 5 recovery.img in /SDcard
Complete cute prince recovery procedure and try booting your Rom. You will not be able Flash any other recovery if you've actually burnt it. Only way is by the above code.. If your Rom boots,read twrp thread fully.
Sent from my HTC Explorer A310e using xda app-developers app
Yeah thanks guys. It got fixed after I tried flashing recovery in jaggyjags tutorial n then flashing twrp
Sent from my HTC Explorer A310e using xda premium
Hi,
My wife just got a new phone and gave up her old XT925 so I thought I would try to put CM or SlimKat on it and let my daughter play around with it. But I'm having trouble putting a custom recovery on it. I've unlocked the bootloader. I've used fastboot to write the recovery image...but when I try to reboot directly into recovery so the binary update can complete, it pauses for a couple of minutes and then reboots the OS normally. If I try entering reovery after that, I end up with the dead android with a red exclamation point in him and "no command" written below.
The phone currently has 4.4.2 and System 181.46.3.XT925.RCI.en.CA. Am I out of luck with this device and stuck on 4.4.2?
Thanks!
What recovery did you try to flash ?
Use this one, it worked for me :
http://forum.xda-developers.com/showthread.php?t=2747535
Thanks. That one worked. I wonder why I had trouble with twrp.
Orionbell37 said:
What recovery did you try to flash ?
Use this one, it worked for me :
http://forum.xda-developers.com/showthread.php?t=2747535
Click to expand...
Click to collapse
pls update the link pls
Pausky said:
pls update the link pls
Click to expand...
Click to collapse
Its because you need to rename the stock recovery to .bak at the end of the file name. The stock recovery is getting in the way of you rebooting to TWRP or what ever custom recovery you are trying to use.
If you cant figure out how to do that or don't know where in system the stock recovery is just hit me up and ill give you the path to the file. After you rename the file just go back into fastboot and reflash the custom recovery and you should be able to reboot into TWRP or what ever custom recovery you want.
I am having some issues trying to flash Recovery (TWRP). When ever I try to boot to Recovery after flashing it, it says "No command." even after I did everything correctly.
My Nexus 5s bootloader is unlocked and I am currently running Marshmallow 6.0.1 if that matters.
CableStone said:
I am having some issues trying to flash Recovery (TWRP). When ever I try to boot to Recovery after flashing it, it says "No command." even after I did everything correctly.
My Nexus 5s bootloader is unlocked and I am currently running Marshmallow 6.0.1 if that matters.
Click to expand...
Click to collapse
What do u mean it says no command, do u mean u still end up in stock recovery, the one with the android and triangle? If that's what's happening then u aren't flashing twrp correctly, or ur not booting strait to recovery after flashing it, how are u flashing it, via command line? If so do this:
fastboot flash recovery "recovery name here".zip
fastboot reboot recovery
That should fix your issue, if u don't boot straight to recovery after u flash it, or if u use something like flashify, when the device reboots it overwrites recovery with the stock recovery, which is what ur seeing
Sent from my XT1526 using Tapatalk
CableStone said:
I am having some issues trying to flash Recovery (TWRP). When ever I try to boot to Recovery after flashing it, it says "No command." even after I did everything correctly.
My Nexus 5s bootloader is unlocked and I am currently running Marshmallow 6.0.1 if that matters.
Click to expand...
Click to collapse
And after flashing the custom recovery again, do not unplug the USB cable or let the device boot. After flashing the recovery, the display should go back to the bootloader, use the volume rocker to highlight recovery, press the power to get into recovery. This will make sure that you flashed right this time. The TWRP logo should be display if everything goes right.
Recovery is flashed with the fastboot command "fastboot flash recovery name-of-file.img".
soupysoup said:
What do u mean it says no command, do u mean u still end up in stock recovery, the one with the android and triangle? If that's what's happening then u aren't flashing twrp correctly, or ur not booting strait to recovery after flashing it, how are u flashing it, via command line? If so do this:
fastboot flash recovery "recovery name here".zip
fastboot reboot recovery
That should fix your issue, if u don't boot straight to recovery after u flash it, or if u use something like flashify, when the device reboots it overwrites recovery with the stock recovery, which is what ur seeing
Sent from my XT1526 using Tapatalk
Click to expand...
Click to collapse
Yeah, sorry for missing that.. And do you need a rooted device in order to flash a TWRP?
Root is not required to flash a custom recovery or a custom rom.
soupysoup said:
fastboot flash recovery "recovery name here".zip
fastboot reboot recovery
That should fix your issue, if u don't boot straight to recovery after u flash it, or if u use something like flashify, when the device reboots it overwrites recovery with the stock recovery, which is what ur seeing
Click to expand...
Click to collapse
It seems to me that this is only required with TWRP 3.0.0 while 2.8.7.1 will happily survive a normal system boot. I've tried right now, just one phone, back to back tests, no other changes.
How come the phone overwrites 3.0.0 with stock but leaves 2.8.7.1 untouched? This is weird.
Am I missing something, perhaps?