okay, so i am trying to boot into my recovery (im wanting to run through jonsuh's recommended stuff)
but i get to a screen that says:
(highlighted) HBOOT
<send> fastboot mode
<vol up> recovery
and then i hit recovery but it goes immediately to a black screen with the phone and a triangle with an exclamation point in it and will just sit there.
can anyone direct me to a thread to tell me what im being an idiot about or just help me out!? thanks!
Recovery failure...bricked...return for replacement
I had the same problem with my daughters Eris. Verizon had to replace it with a refurbished phone.
That sucks. I JUST got it refurbished from verizon...
Sent from my DROIDX using XDA App
The question is.. what are you trying to do? What are you trying to flash?
If you just want to go flash a signed rom from an RUU, you can rename it pb00img.zip and flash it from hboot.
It's just sitting there because there's nothing for it to do. It's behaving perfectly normal for an unrooted Eris.
Actually, I figured it out. It may seem trivial, but when I would hit the vol down + power, and then hit vol up I was pressing vol up not holding vol up. Now I have two droid eris' running kaosfroyo
Does that make any sense?
Sent from my DROIDX using XDA App
frankawesome said:
Actually, I figured it out. It may seem trivial, but when I would hit the vol down + power, and then hit vol up I was pressing vol up not holding vol up. Now I have two droid eris' running kaosfroyo
Does that make any sense?
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Actually, no - it doesn't make sense. You can't use the stock recovery to install a dev ROM, because it won't pass the signing checks.
The only known ".zip" files that will pass signing checks using the stock recovery are the OTAs (renamed to "update.zip")
For the record, the behavior you noticed (with the dark screen w/ the triangle, exclamation point, and phone graphic) is normal - to get the "Recovery <2e>" menu to appear, you press Vol-Up+End a second time after that image appears. (Or possibly just Vol-Up).
bftb0
Related
I am not sure how to really search for this?
Anyways I am assuming its a combo of buttons pressed to enable... but when I power on my Atrix now I no longer get the "Moto Dual Core" screen, I now instead get the system menu to pick the various ways to start the phone up.
Does anyone know how to revert to the Dual Core screen, and not have it open the menu?
EDIT: as an update, I just went ahead and trashed the whole phone and flashed the pudding sbf with RSD and the phone is back to normal. I would still like to know what happened? I was in CWM and then it rebooted and gave me the magic value mismatch thing when going into CWM, and instead of the moto dual core screen I got the menu with all the boot options.
weird.
Are u sure that you are not on recovery mode?
Stop pressing vol down button
Sent from my MB860 using Tapatalk
mraxido said:
Are u sure that you are not on recovery mode?
Stop pressing vol down button
Sent from my MB860 using Tapatalk
Click to expand...
Click to collapse
Positive, its the full "engineering" prompt so to speak... it was even outputting every single thing the phone was doing at boot.
Maybe it was something the phone had triggered when you got that error? I've never seen/heard of this issue before, but computers can do something similar to show you what is booting and what everything is doing on start up. Maybe a "safe mode" kind of boot up? Safe Mode on a computer usually does that when it boots up, but I had that "Magic" error once before and I never had that happen to me.
I was wondering if there was a way of going back to the stock recovery from CWM? I have rooted my prime and unlocked the boot loader. Was wondering if I needed to return the tab if someone noticed CWM that they may give me a problem returning.
if you mean returning to a store, they will never check the recovery, probably would only check that it boots at all if even that
scook9 said:
if you mean returning to a store, they will never check the recovery, probably would only check that it boots at all if even that
Click to expand...
Click to collapse
I was thing that also, but is there a way to go back to the stock recovery?
grneyez said:
I was thing that also, but is there a way to go back to the stock recovery?
Click to expand...
Click to collapse
No.
Sent from my ADR6425LVW using XDA Premium.
Ok, thanks
Wrong actually. Use the method to downgrade to any of the Asus releases - using dd on the blob file, that overwrites the recovery with the stock one
I have to do this when going back to stock from CM9 since the kernel doesn't flash. I have to re-root and re-flash CWM each time since the blob method overwrites system, boot, recovery, and maybe one or two other things
scook9 said:
Wrong actually. Use the method to downgrade to any of the Asus releases - using dd on the blob file, that overwrites the recovery with the stock one
I have to do this when going back to stock from CM9 since the kernel doesn't flash. I have to re-root and re-flash CWM each time since the blob method overwrites system, boot, recovery, and maybe one or two other things
Click to expand...
Click to collapse
Huh, interesting. I never knew that. Thanks for pointing that out to me!
Sent from my ADR6425LVW using XDA Premium.
scook9 said:
Wrong actually. Use the method to downgrade to any of the Asus releases - using dd on the blob file, that overwrites the recovery with the stock one
I have to do this when going back to stock from CM9 since the kernel doesn't flash. I have to re-root and re-flash CWM each time since the blob method overwrites system, boot, recovery, and maybe one or two other things
Click to expand...
Click to collapse
Is this something that can be done fairly easily? And how would I be able to do this?
Sent from my Transformer Prime TF201 using Tapatalk
grneyez said:
Is this something that can be done fairly easily? And how would I be able to do this?
Sent from my Transformer Prime TF201 using Tapatalk
Click to expand...
Click to collapse
I am not sure of the full ramifications of doing the blob thing over anything other than the stock rom. You will want to find the thread in the dev section that talks about loading any version of the stock rom that you want.
i believe applying a official blob file after being unlocked/cwm'ed will get you a bricked Prime. i hope none of you have a brick these days.
Hey guys.. I'm trying not to start a new thread if I can help it as I'm sure my answer is here somewhere.. but ...
Can't seem to boot into recovery. I installed CWM using the viper tool and got successful messages but button combo doesn't work to enter recovery. Nor does Rom Manager work to reboot recovery. I've also tried flashing recovery via RM and got successful but still unable to boot into CWM. Tried installing touch recovery via RM.. got succesfull, and it even says what my current recovery is but no matter what I try I am unable to boot into CWM.
I feel like its not installed but according to RM my current recovery is 5.8.x.x
Any help would be GREATLY appreciated!
Sent from my SGH-I777 using Tapatalk 2 Beta-5
Coreym said:
Hey guys.. I'm trying not to start a new thread if I can help it as I'm sure my answer is here somewhere.. but ...
Can't seem to boot into recovery. I installed CWM using the viper tool and got successful messages but button combo doesn't work to enter recovery. Nor does Rom Manager work to reboot recovery. I've also tried flashing recovery via RM and got successful but still unable to boot into CWM. Tried installing touch recovery via RM.. got succesfull, and it even says what my current recovery is but no matter what I try I am unable to boot into CWM.
I feel like its not installed but according to RM my current recovery is 5.8.x.x
Any help would be GREATLY appreciated!
Sent from my SGH-I777 using Tapatalk 2 Beta-5
Click to expand...
Click to collapse
I had a lot of problems when I was on the non-touch version of CWM. It would do the button combo correctly but it would only boot to recovery about one time in five. Very frustrating, but it got a lot better when I chanced to touch CWM for some reason.
Gotta ask this but are you doing the button combo correctly? When you press power + vol down do you see the white text telling you that you have bot 5 sec to press vol up? When you press vol up, what happens? When I was having problems with this I would see the white text, press vol up then the screen would go black for about 10 sec then it would reboot.
paddycr said:
I had a lot of problems when I was on the non-touch version of CWM. It would do the button combo correctly but it would only boot to recovery about one time in five. Very frustrating, but it got a lot better when I chanced to touch CWM for some reason.
Gotta ask this but are you doing the button combo correctly? When you press power + vol down do you see the white text telling you that you have bot 5 sec to press vol up? When you press vol up, what happens? When I was having problems with this I would see the white text, press vol up then the screen would go black for about 10 sec then it would reboot.
Click to expand...
Click to collapse
That's part of the problem.. I have no idea if I'm doing the button combo right because nothing is happening. I've tried pressing power button and vol down until I see text.. never shows though. I feel a buzz or vibrate but no text so i continue holding down buttons until eventually i realize I've been holding the buttons down for a really long time and it's time to accept its not working so I let go. Ive also tried just pressing volume down..(thought I read that somewhere).. nothing ever happens but a buzz or vibrate. No text ever appear.
btw, thank you for the reply! you have no idea how many times I tried yesterday/last night. I'm up an atom, and back at it.. beats me though..
Sent from my Transformer Prime TF201 using Tapatalk 2 Beta-5
Coreym said:
That's part of the problem.. I have no idea if I'm doing the button combo right because nothing is happening. I've tried pressing power button and vol down until I see text.. never shows though. I feel a buzz or vibrate but no text so i continue holding down buttons until eventually i realize I've been holding the buttons down for a really long time and it's time to accept its not working so I let go. Ive also tried just pressing volume down..(thought I read that somewhere).. nothing ever happens but a buzz or vibrate. No text ever appear.
btw, thank you for the reply! you have no idea how many times I tried yesterday/last night. I'm up an atom, and back at it.. beats me though..
Sent from my Transformer Prime TF201 using Tapatalk 2 Beta-5
Click to expand...
Click to collapse
Unfortunately I don't have my Prime in front of me since I am at work so I'll see if I can remember . From power off press the power button until it vibrates, release it then quickly press and hold power and vol down. When you are on the Eee Pad splash screen you should some text at the top left saying that you have 5 sec to press vol up to enter RCK (or something...). Release and press vol up and you should be in.
Hit my thanks button if it works. If not, this is beyond my limited capabilities and you should find someone more knowledgeable Good luck!
paddycr said:
Unfortunately I don't have my Prime in front of me since I am at work so I'll see if I can remember . From power off press the power button until it vibrates, release it then quickly press and hold power and vol down. When you are on the Eee Pad splash screen you should some text at the top left saying that you have 5 sec to press vol up to enter RCK (or something...). Release and press vol up and you should be in.
Hit my thanks button if it works. If not, this is beyond my limited capabilities and you should find someone more knowledgeable Good luck!
Click to expand...
Click to collapse
Nope.. no dice. I hit your thanks because I appreciate the reply.. thank you. I started a thread in q&a addressing my problem.. hopefully get more help over there! Thanks again!
Sent from my SGH-I777 using Tapatalk 2 Beta-5
Hi guys,
Late last year i sold my GS2 to a guy at work. Rooted and with a custom ROM installed (Cognition V1.5.1 - yes i know its old but its not my phone )
I've attempted to install RC1 for CM9 this morning however, I'm falling at the first hurdle. I've booted into Clockwork recovery (4.0.0.2). The menu buttons work fine i.e, up/down and power as enter but when i select anything it goes to a black screen with the ROM Manager logo on it (the gog and the hat) - but no options.
Do i need to install a newer version of Clockwork on the device? If i do whats the best way to do it? Do i use ROM Manager to update it as i cant access any of the menus in recovery (other than the top menu)
I've not seen this problem before as normally people are kept in boot loops or cant get passed a splash screen.
EDIT - i've just managed to get the phone to boot and its now running as normal. I'm just concerned that if i go back into recovery i might not get it back up again.
Many thanks
Splash
You're pressing the wrong button lol... use the power button to confirm and the volume buttons to move up and down. The home button does nothing.
leijonasisu said:
You're pressing the wrong button lol... use the power button to confirm and the volume buttons to move up and down. The home button does nothing.
Click to expand...
Click to collapse
I am pressing power.. What I'm saying is that when I do I only get a blank screen with the rom manager logo on it.
Sent from my GT-N7000 using Tapatalk 2
old cwm did use home button, power button use to show a pic like you say, update cwm
Sent from my GT-I9100 using xda app-developers app
markie32 said:
old cwm did use home button, power button use to show a pic like you say, update cwm
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
I'm still trying to work out where I mentioned pressing the home button.
Splash
Sent from my GT-N7000 using Tapatalk 2
Captain Splash said:
Hi guys,
Late last year i sold my GS2 to a guy at work. Rooted and with a custom ROM installed (Cognition V1.5.1 - yes i know its old but its not my phone )
I've attempted to install RC1 for CM9 this morning however, I'm falling at the first hurdle. I've booted into Clockwork recovery (4.0.0.2). The menu buttons work fine i.e, up/down and power as enter but when i select anything it goes to a black screen with the ROM Manager logo on it (the gog and the hat) - but no options.
Do i need to install a newer version of Clockwork on the device? If i do whats the best way to do it? Do i use ROM Manager to update it as i cant access any of the menus in recovery (other than the top menu)
I've not seen this problem before as normally people are kept in boot loops or cant get passed a splash screen.
EDIT - i've just managed to get the phone to boot and its now running as normal. I'm just concerned that if i go back into recovery i might not get it back up again.
Many thanks
Splash
Click to expand...
Click to collapse
Try to update cwm recovery to the latest version
Sent from my GT-I9100 using xda premium
So, I installed safestrap and rebooted. Everything was fine, I let it boot normally and then rebooted again to get into recovery. In the recovery menu I tried installing a zip, and it told me I had to enable the safe system, so I did so. Now when I reboot the phone, I get a pure black screen and the phone is completely non-responsive. Trying to power it on does nothing, what should I do?
edit: OK, if I hold down power & the volume key, the screen will flash. If I hold down power again I can get back into recovery. I'm trying to disable safe system now, hopefully that'll work.
edit 2: Yep, that worked
Just curious in the safe side, did you actually flash any custom ROM?
Sent from my DROID RAZR using xda app-developers app
Alright, so I literally just received a replacement phone after having my Galaxy s4 broken for about 3 months. So naturally the first thing I do it is try to root it so I can get CM on it, but the factory the updated my phone to the VRUEMJ7 build, which apparently you can't actually hard root... so whatever, I do the saferoot, and use Hashcode's Safestrap recovery. But, for some reason I always feel the need to test **** that I don't understand, so in his recovery I switched the active ROM to the stock rom, then tried to reset to factory default, deleting all the data and whatnot, thinking I would be able to get more space for my CM partition. Welp, now my phone is stuck at the Samsung/Custom lock spash screen, and I don't think I can boot into Odin (it's still volume rocker up + power button, right?)
So, is my phone now hard bricked, or it there anything I can do about it? I'm downloading the image from this thread as I type this, but I'm not sure I can use it considering when I try to boot into Odin the blue text flashes in the upper right corner like normal, but then the screen goes black while I continue holding the buttons, and doesn't do anything until I release them, which causes it to just go back to the bricked splash screen.
Halp!!!
Nihilife said:
Alright, so I literally just received a replacement phone after having my Galaxy s4 broken for about 3 months. So naturally the first thing I do it is try to root it so I can get CM on it, but the factory the updated my phone to the VRUEMJ7 build, which apparently you can't actually hard root... so whatever, I do the saferoot, and use Hashcode's Safestrap recovery. But, for some reason I always feel the need to test **** that I don't understand, so in his recovery I switched the active ROM to the stock rom, then tried to reset to factory default, deleting all the data and whatnot, thinking I would be able to get more space for my CM partition. Welp, now my phone is stuck at the Samsung/Custom lock spash screen, and I don't think I can boot into Odin (it's still volume rocker up + power button, right?)
So, is my phone now hard bricked, or it there anything I can do about it? I'm downloading the image from this thread as I type this, but I'm not sure I can use it considering when I try to boot into Odin the blue text flashes in the upper right corner like normal, but then the screen goes black while I continue holding the buttons, and doesn't do anything until I release them, which causes it to just go back to the bricked splash screen.
Halp!!!
Click to expand...
Click to collapse
You reset your stock rom My advice is to read up on what you can and can't flash, and if you have even the slightest doubt, ask someone on the forums for, help. That saved me loads of time and stress.
ODIN/Download Mode
Make sure your device is completely off
Key(s): Volume Down
While holding this key down simultaneously press the Power button until you see a disclaimer on the screen
Then let go of both buttons and press Volume Up to accept the disclaimer
Once the green robot is visible on the screen this indicates that handset is in now ODIN/Download mode
Recovery Mode
Make sure your device is completely off
Key(s): Volume Up
While holding this key down simultaneously press the Power button
As soon as the phone vibrates, let go of the Power button but keep holding Volume Up
When you see the "Samsung Galaxy S4" logo (not just the word "Samsung"), right after that, the next screen you should see is your recovery
Don't let go of Volume Up until you see your recovery
ickray said:
You reset your stock rom My advice is to read up on what you can and can't flash, and if you have even the slightest doubt, ask someone on the forums for, help. That saved me loads of time and stress.
Click to expand...
Click to collapse
I know, I'm an idiot. :/
When I try to boot into Odin the android doesn't pop up though, the screen goes black while I have the buttons held, and just goes back to the boot screen after I let them go.
Nihilife said:
Alright, so I literally just received a replacement phone after having my Galaxy s4 broken for about 3 months. So naturally the first thing I do it is try to root it so I can get CM on it, but the factory the updated my phone to the VRUEMJ7 build, which apparently you can't actually hard root... so whatever, I do the saferoot, and use Hashcode's Safestrap recovery. But, for some reason I always feel the need to test **** that I don't understand, so in his recovery I switched the active ROM to the stock rom, then tried to reset to factory default, deleting all the data and whatnot, thinking I would be able to get more space for my CM partition. Welp, now my phone is stuck at the Samsung/Custom lock spash screen, and I don't think I can boot into Odin (it's still volume rocker up + power button, right?)
So, is my phone now hard bricked, or it there anything I can do about it? I'm downloading the image from this thread as I type this, but I'm not sure I can use it considering when I try to boot into Odin the blue text flashes in the upper right corner like normal, but then the screen goes black while I continue holding the buttons, and doesn't do anything until I release them, which causes it to just go back to the bricked splash screen.
Halp!!!
Click to expand...
Click to collapse
Nihilife said:
I know, I'm an idiot. :/
When I try to boot into Odin the android doesn't pop up though, the screen goes black while I have the buttons held, and just goes back to the boot screen after I let them go.
Click to expand...
Click to collapse
If worse comes to worst, try this: http://forum.xda-developers.com/showthread.php?t=2507253
ickray said:
If worse comes to worst, try this: http://forum.xda-developers.com/showthread.php?t=2507253
Click to expand...
Click to collapse
Sorry, not to sound ungrateful for the help, but I feel like you're not reading what I'm saying :/. I would love to be able to do that, but as of right now I'm unable to get into Odin. Unless you can get into Odin using ADB or something of the sort that won't help me.
Nihilife said:
Sorry, not to sound ungrateful for the help, but I feel like you're not reading what I'm saying :/. I would love to be able to do that, but as of right now I'm unable to get into Odin. Unless you can get into Odin using ADB or something of the sort that won't help me.
Click to expand...
Click to collapse
ah my fault
You can always enter download/Odin mode. Hold the HOME button and the volume down button when powering on until the screen turns on.
Sent from my SCH-I545 using xda app-developers app
Take the battery out and wait ten mins then put it back then try to boot in download mode. If you didnt flash over sbl 1-3 and aboot you should still be able to get into download mode. If not boot into recovery mode then clear cache and then try to boot to download mode. And what blue text in the upper right corner are you talking about? Download mode doesnt display that and recovery displays blue text in the upper left.
Sent from my SCH-I545 using XDA Premium 4 mobile app
I posted in the Safestrap thread asking for help too, and someone pointed out that you need to hold the buttons for Odin and release them when the phone vibrates, and I was keeping them help. Thanks so much for the help guys, I should be able to flash the recovery image and save my phone now.