renamed spl to update.zip and placed in root of SD
did alt+s, think i pressed alt+w accidentally, now when booting / rebooting
trying to get my home + power screen to reload, get "ROGERS" with the red "FASTBOOT USB" at the top, according to this
Rogers, heres your real root
http://forum.xda-developers.com/showthread.php?t=544654
"(if you don't boot into recovery or accidentally rebooted, just pull the battery [if you notice top left it should read "FASTBOOT" or "FASTBOOT USB" if it's plugged in] you're not bricked, you just need to access recovery, not standard boot ;P)"
then alt+s to load the rom, well the rom isn't on there becausei was following
installing the new spl
http://forum.xda-developers.com/showthread.php?t=532719
anyway to load the actual rom some other way, can't access the SD card with the fastboot skateboard screen or the rogers with the red "Fastboot usb" screen.
Confused, and frustrated, some help would be wonderful if you have the time, Thanks !
Did you flash the SPL before you flashed the radio?
xsnipuhx said:
Did you flash the SPL before you flashed the radio?
Click to expand...
Click to collapse
what i was trying to do
note: when attempting to flash
fastboot flash radio radio.img
Error: FAILED <remote: signature verify fail>
fastboot erase system -w
-okay
fastboot erase boot
-okay
fastboot erase recovery
-okay
fastboot flash recovery recovery.img
Error: FAILED <remote: signature verify fail>
Try redownloading the recovery.img There may have been a corrupted file somewhere.
xsnipuhx said:
Try redownloading the recovery.img There may have been a corrupted file somewhere.
Click to expand...
Click to collapse
Just did, receiving same error as before
"FAILED <remote: signature verify fail>
?
Check the original thread and see if anyone else is having the same problem.
xsnipuhx said:
Check the original thread and see if anyone else is having the same problem.
Click to expand...
Click to collapse
seems like a few are having a similar issue , more or less the "stuck at rogers screen for a long ass time"
this is a little frustrating =( haha
JsnLlnd said:
seems like a few are having a similar issue , more or less the "stuck at rogers screen for a long ass time"
this is a little frustrating =( haha
Click to expand...
Click to collapse
If you're just trying to load the ROM, try booting into recovery (home+power) then press alt+x and type ums_enable that will allow you to transfer things over to your sdcard like you normally would.
h.nocturna said:
If you're just trying to load the ROM, try booting into recovery (home+power) then press alt+x and type ums_enable that will allow you to transfer things over to your sdcard like you normally would.
Click to expand...
Click to collapse
Tried, won't go into recovery. stays at the Rogers start screen.
Anything else?
Quick update, was able to get into
fastboot boot recovery.img
and it loaded cyanogen cf 1.5? did alt+s and alt+w but theres no rom on the sd card right? hence its not doing anything?
am i figuring this out correctly here?
when i type in the fastboot boot recovery.img
downloading 'boot.img'...OKAY
booting...OKAY
where is this thing and how do i do this right im confusing myself blahhh
--------
rebooted, now i can't get into fastboot -_-
is this thing bricked now ?
use my fastboot boot recovery.img and it goes fastboot real quick, see a loading bar, then bam back to plain rogers screen. gonna try different recovery.
possibly adb push ? im learning this all just now more or less, so a direct path from my c:\android\sdk1.5_r3\tools: adb push ??? what goes here?
as far as the alt+x option goes , i can do it , but ums_enable isn't doing anything , any more details on that so i can get that rom on the SD card, think i will be good to go after that.
Related
Everything works fine. I can boot into 2.1 stock and bootloader but I can't enter recovery. Everytime I try I get the damn Triangle and Android. I even tried factory reset which didn't do the trick. Can anyone help me?
I recently reverted back to stock 2.1 with an old nandroid backup. Today I downloaded the 2.2 Froyo manual update, didn't even put it on SD yet. So I rebooted into bootloader and pressed recovery and that came up. I read from a different post that the exclamation point and android stands for stock recovery but I never went back to stock recovery mode, only back to stock ROM.
try pressing the power button with the volume up button at the same time. It might take a couple of times but you'll get somewhere. Try it out really quick and let me know
You might have done it on accident.
Go into the bootloader and fastboot flash your custom recovery again.
Im trying to flash the custom recovery again but for some reason when I try adb devices it will not show my serial number. It only shows if I boot the phone into the stock rom, but won't on FastBoot USB.
Where do I put the recovery.img in the directory of Android SDK?
can you power off and get into the bootloader? Sorry man, I'm confused.
Yes I can.
alright then, can you flash everything from fastboot?
What do you mean flash from Fastboot? You mean recovery?
My device isn't recognized in Fastboot USB
put the custom recovery.img where you have fastbot access on your pc. Open command prompt and start fastboot.
Boot into bootloader (white screen with 3 androids)
type "fastboot devices" in command prompt
the type "fastboot flash recovery recovery.img"
Do you know what I'm talking about?
Im not saying your an idiot by writing this out so don't take offense lol
Gave me an error.
cannot load 'recovery.img'
is the recovery.img in the same folder as the fastboot access?
ezeddiekun said:
Gave me an error.
cannot load 'recovery.img'
Click to expand...
Click to collapse
You have to replace recovery.img with the name of your recovery file. Download recovery-RA-nexus-v1.7.0.img from here:
http://forum.xda-developers.com/showthread.php?t=611829
and type:
fastboot flash recovery recovery-RA-nexus-v1.7.0.img
This is assuming you wish to return to a custom and not stock recovery menu.
Im an idiot when it comes to this. What do you mean fastboot access folder? The tools folder in AndroidSDK?
Problem solved guys.. Im a friggin idiot. I forgot to open the command prompt in the fastboot folder. omg -_-
ezeddiekun said:
Im an idiot when it comes to this. What do you mean fastboot access folder? The tools folder in AndroidSDK?
Problem solved guys.. Im a friggin idiot. I forgot to open the command prompt in the fastboot folder. omg -_-
Click to expand...
Click to collapse
Haha it's cool man, Just glad to got it
ezeddiekun said:
Im an idiot when it comes to this. What do you mean fastboot access folder? The tools folder in AndroidSDK?
Problem solved guys.. Im a friggin idiot. I forgot to open the command prompt in the fastboot folder. omg -_-
Click to expand...
Click to collapse
Yes, you are an idiot...
Scares the sh*t out of me sometimes doing this stuff as well. Like to live dangerously though!!
Glad you got it sorted.
So I did a full wipe and then installed Rodriguezstyle FroYo rom (http://forum.xda-developers.com/showthread.php?t=692609). It was fine but I missed too many CM features and NeXTheme.
I did a wipe, reflashed CM5.0.7.1 and then restored my nandroid (+ext). Now I cannot get the device to boot!
I can get into bootloader and thought I should replace the radio as I know the FroYo one is a problem in non-FroYo roms but while it copies ok, when installing it says FAILED (remote:image update error)
Please please help me. Give me steps to do to get back to a clean CM5.0.7.1 and I can sort the rest out!
Fastboot won't let me flash anything! I am unlocked though!
There's no need to post your question in multiple forums.
Someone will answer when they know how to help.
That said, all I can suggest is maybe trying a different radio image? Or maybe see if you can load up one of the 2.1 ROMs and deal with the radio issue once it's up and running?
Sorry, got a bit desperate
I have tried several radios, the problem is that I cannot flash anything for some reason. I cannot even flash Amon_Ra's recovery to try and get a different rom working
So even booting to fastboot (press and hold trackball during power-on) your computer is unable to connect via fastboot? So "fastboot devices" doesn't return anything?
Just booting normally, what happens? Does it get stuck on the Android bootloader screen or what? Any chance of connecting to it via adb?
I haven't broken my stuff hard yet, so I'm kinda guessing here lol. Trying to help though!
I appreciate the help, thanks.
I can get to fastboot and issue fastboot commands (fastboot devices returns the model number (?) as normal). It's just that if I try to fastboot flash recovery I get that "image update error"
I can't get as far as a recovery image to issue adb commands. When I try to boot normally, the phone vibrates once as the X comes up, then several quick vibrations which seem like some kind of error code.
Also, by way of some extra info in case it helps, the following is displayed on my bootloader:
NEXUSONE PVT SHIP S-ON
HBOOT_0.33.0012
MICROP-0b15
TOUCH PANEL-SYNT0103
Radio-4.02.02.14
Dec 17 2009,13:05:23
3Shirts said:
I appreciate the help, thanks.
I can get to fastboot and issue fastboot commands (fastboot devices returns the model number (?) as normal). It's just that if I try to fastboot flash recovery I get that "image update error"
I can't get as far as a recovery image to issue adb commands. When I try to boot normally, the phone vibrates once as the X comes up, then several quick vibrations which seem like some kind of error code.
Also, by way of some extra info in case it helps, the following is displayed on my bootloader:
NEXUSONE PVT SHIP S-ON
HBOOT_0.33.0012
MICROP-0b15
TOUCH PANEL-SYNT0103
Radio-4.02.02.14
Dec 17 2009,13:05:23
Click to expand...
Click to collapse
What is the EXACT command are you typing to flash recovery?
3Shirts said:
I appreciate the help, thanks.
I can get to fastboot and issue fastboot commands (fastboot devices returns the model number (?) as normal). It's just that if I try to fastboot flash recovery I get that "image update error"
Click to expand...
Click to collapse
Have you tried this --> http://forum.xda-developers.com/showthread.php?t=614850
It is a sticky..... Anyways, I would also try the official .zip image (PASSIMG.zip) if you can find a thread on that someplace. That loads through fastboot I believe so check it out.....
Also try "Fastboot boot recovery.img" (recovery.img being c:\PATHTOFILE) and see if it will boot into recovery that way......
martin0285 said:
Have you tried this --> http://forum.xda-developers.com/showthread.php?t=614850
It is a sticky..... Anyways, I would also try the official .zip image (PASSIMG.zip) if you can find a thread on that someplace. That loads through fastboot I believe so check it out.....
Also try "Fastboot boot recovery.img" (recovery.img being c:\PATHTOFILE) and see if it will boot into recovery that way......
Click to expand...
Click to collapse
The command I am typing is: fastboot flash recovery recovery.img <- this being the name of the Amon_Ra recovery image file located in the same folder I am in when issuing the command
I have tried that post's instructions but I get "remote: not allowed" when trying to erase userdata and I was getting "remote: image update error" when trying to do any of the flash commands. I say WAS becasue I have just tried sticking the original PASSIMG on sd card and updating that way and, while it gave me partition update errors on boot and system, it has changed something because now when I do the fastboot flash commands I get a different error: "remote: signature verify fail"
I know the files are not corrupt though as I have checked the md5s
EDIT: I also tried doing a fastboot boot to the recovery image but it loads to the X then I get prompted by windows to install a Qualcomm CDMA driver which it can't find?!!
the first case of semi-brick?
like on the G1
JKshowman said:
the first case of semi-brick?
like on the G1
Click to expand...
Click to collapse
Don't say that
Thread Moved.
3Shirts said:
Don't say that
Click to expand...
Click to collapse
no, its just i had a semi-brick problem on the G1 and i solved it quickly enough by reflashing a recovery, but in this case.........
try to see if other flashboot commands work
3Shirts said:
Don't say that
Click to expand...
Click to collapse
Try downloading the recovery image again. It could be corrupt. Also, I am assuming you unlocked your phone first.
No I have confirmed the MD5s on everything I downloaded including the recovery image. Yeah I've been unlocked and rooted from day one.
Does anyone have an hboot image I can try flashing
Well it looks like i'm f***ed then.
I can't adb and can't boot to any kind of terminal so with only fastboot available, and that not allowing me to flash much, I can't fix this
I guess it's off to HTC, see what hey can/will do and if that fails... no more Nexus One
EDIT: Booked it in with HTC for collection tomorrow afternoon (UK time). I'll update again to provide a definitive answer to the question: What is the price for effing up your Nexus One through your own stupidity
The command I am typing is: fastboot flash recovery recovery.img
Click to expand...
Click to collapse
I realize this, but fastboot BOOT recovery.Img is a different command to just "boot" the image and not "flash" permanently... worth a shot....
martin0285 said:
I realize this, but fastboot BOOT recovery.Img is a different command to just "boot" the image and not "flash" permanently... worth a shot....
Click to expand...
Click to collapse
I have tried that too. It just sits at the X. Doesn't get into recovery
3Shirts said:
I have tried that too. It just sits at the X. Doesn't get into recovery
Click to expand...
Click to collapse
****ty, well good luck with HTC.....
Just to update for anyone interested in the process:
I called HTC on 2nd June and booked collection for the following afternoon.
Picked up by courier (I packed it in original box and jiffy bag with battery but no SD or Sim cards) at 2pm on 3rd June
Received confirmation of arrival with HTC (Milton Keynes as I'm in the UK) at 1.43pm on 4th June
Next step is to wait for a call regarding the repair that can be done and associated cost.
I need some help here.
Power button broke on my n1 sometime ago. Recently I tried to flash a new kernel but forgot to wipe and it's basically stuck at the logo.
I'm able to get into the hboot screen via bqttry removal technique but cannot select any option because of bad power button.
Any ideas how to flash a new room? I tried connecting USB to pc but phone is not recognized while in hboot mode.
Any help would appreciated as it's my only phone
Thanks
Is your phone unlocked (ie do you have a lock symbol at the bottom of the 'X' screen)?
If so, I believe you can hold the trackball while booting up and that will take you into fastboot.
From there, I think you just issue the command
Code:
fastboot reboot recovery
If that doesn't work, you can just boot off a recovery file that is stored on your computer. Download either clockworkmod (I would recommend any v2.x as v3.x has some problems) or Amon_RA to a easy to type location on your computer. Then issue the command
Code:
fastboot boot recovery "c:\location to\recovery.img"
Ok, so I got it to boot in fastboot, but there's no option to
./fastboot-mac reboot recovery
Click to expand...
Click to collapse
also
./fastboot-mac boot recovery ../recovery-RA-passion-v2.2.1.img
Click to expand...
Click to collapse
I get:
cannot load 'recovery'
and I did this:
fastboot flash recovery /path/to/<recovery>.img
Click to expand...
Click to collapse
Is there a way reboot it into recovery?
Thanks!
Passimg back to stock, root, and try again...
jp2000 said:
I get:
cannot load 'recovery'
Click to expand...
Click to collapse
Is there any more into that error? Did you verify the md5sum to make sure the recovery isn't corrupted?
Also, if you have a recent nandroid backup saved on your sdcard, you can pull that off and flash the imgs directly
Code:
./fastboot-mac flash system /location/to/system.img
./fastboot-mac flash boot /location/to/boot.img
./fastboot-mac flash userdata /location/to/data.img
./fastboot-mac reboot
Where these files will be located depends on your recovery. I know with clockworkmod they are located in the backup folder under the clockworkmod folder on the sdcard. I don't know where they are stored for Amon_RA, but I would assume it would be similar.
Thanks to everyone for your suggestions.
Finally got my phone working!
Hi.
I have the same problem but whenever I try "fastboot flash" or "fastboot recovery" I end up with "FAILED (remote: signature verifiy fail)". I think this is due to that my bootloader is not unlocked, so I tried:
fastboot oem unlock
I got the option to unlock bootloader but I had to use my power button to select "unlock". My power button is broken so I don't know what to do.
Is there anything else I can do? Otherwise I think I have to open the phone and try to repair the button.
PASSIMG back to stock and root. Use "unroot/restore" section in Wiki.
If you're skilled enough with soldering tiny connectors - you can repair the button. There is a guide on this forum, showing the exact location to attach to.
Thanks. Now I can use the phone again!
Where is this repair guide...please let me know...
Sent from my Nexus One using xda premium
I've got a nexus one with a broken power button and a corrupt OS. It rarely successfully manages to boot. Since this is the case, I'm not able to turn on USB debugging to follow some of the tutorials here..
My next try was fastboot.. I downloaded these two files:
recovery-clockwork-5.0.2.0-passion.img
update-cm-7.1.0-N1-signed.zip
But it seems like I wont be able to flash a recovery file if I have "s-on" displayed on my hboot or fastboot screen..
How do I gain "s-off"? And is it possible to flash a stock rom via fastboot?
And yes, my phone's got stock gingerbread 2.3.4 rom.
HBOOT 0.35.0017
MICROP 0b15
Touch panel SYNT0103
Radio 5.08.00.04
Please help me with this matter as I have been trying to accomplish this task for over three months now..
Read Nexus One wiki, section "root", and section "recovery".
You don't need S-OFF to flash anything, if you unlock your bootloader. This is Nexus.
Boot into fastboot, plug into your PC, open command prompt wherever you have the fastboot command in Windows, most likely in android sdk under platform-tools, run "fastboot oem unlock" from command prompt, your bootloader is now unlocked. Attempt to flash your recovery now."
Sent from my Nexus One using XDA App
troby86 said:
Boot into fastboot, plug into your PC, open command prompt wherever you have the fastboot command in Windows, most likely in android sdk under platform-tools, run "fastboot oem unlock" from command prompt, your bootloader is now unlocked. Attempt to flash your recovery now."
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
My phone's power button is broken so I'm not able to select the recovery option
Jack_R1 said:
Read Nexus One wiki, section "root", and section "recovery".
You don't need S-OFF to flash anything, if you unlock your bootloader. This is Nexus.
Click to expand...
Click to collapse
It's already unlocked, as there is a small open lock displayed at the bottom of the boot screen.. and fastboot displayed it as already unlocked as well.. still.. i need a way to go to recovery without the power button
If you're in the bootloader - "fastboot reboot recovery".
If you're in the OS or while the OS is booting and ADB daemon is already running - "adb reboot recovery".
Jack_R1 said:
If you're in the bootloader - "fastboot reboot recovery".
If you're in the OS or while the OS is booting and ADB daemon is already running - "adb reboot recovery".
Click to expand...
Click to collapse
fastboot reboot recovery doesnt seem to boot the phone to recovery..
should the OS be completely booted up if I want to use the adb command? because it displays the error "error: device not found" when I try to "adb reboot recovery"
Might this be a problem with my computer? I checked and confirmed that the drivers for the phone are successfully installed...
knaphih said:
fastboot reboot recovery doesnt seem to boot the phone to recovery..
should the OS be completely booted up if I want to use the adb command? because it displays the error "error: device not found" when I try to "adb reboot recovery"
Might this be a problem with my computer? I checked and confirmed that the drivers for the phone are successfully installed...
Click to expand...
Click to collapse
Do you have the fastboot command on your computer?
troby86 said:
Do you have the fastboot command on your computer?
Click to expand...
Click to collapse
Yes, I can fastboot works ok because I can flash recovery image and reboot phone through fastboot. But since my power button is broken, I need to reboot to recovery through the computer...
knaphih said:
Yes, I can fastboot works ok because I can flash recovery image and reboot phone through fastboot. But since my power button is broken, I need to reboot to recovery through the computer...
Click to expand...
Click to collapse
First try: "adb reboot recovery" or "fastboot reboot-recovery"
If that doesn't work, give this a good read to see if it will help you:
http://wiki.cyanogenmod.com/index.php?title=Fastboot
If you are able to flash the recovery via fastboot, then I see no reason why you should not be able to reboot into recovery via fastboot or adb.
---------- Post added at 06:18 AM ---------- Previous post was at 06:11 AM ----------
knaphih said:
Yes, I can fastboot works ok because I can flash recovery image and reboot phone through fastboot. But since my power button is broken, I need to reboot to recovery through the computer...
Click to expand...
Click to collapse
And if none of that seems to work:
http://www.androidguys.com/2010/09/08/manage-nexus-broken-power-button/
OR
http://www.yamihoshi.nl/tech/tutorial-google-nexus-one-power-button-soft-fix
Both are the same, the second one is easier to follow.
OR
Put your recovery .img file into the same folder as your fastboot command, and run this: "fastboot boot recovery-clockwork-2.5.1.4-passion.img"
^^^^^USE YOUR RECOVERY NAME...NOT THE EXACT ONE ABOVE^^^^^
First try: "adb reboot recovery" or "fastboot reboot-recovery"
If that doesn't work, give this a good read to see if it will help you:
http://wiki.cyanogenmod.com/index.php?title=Fastboot
If you are able to flash the recovery via fastboot, then I see no reason why you should not be able to reboot into recovery via fastboot or adb.
Click to expand...
Click to collapse
I've attached an image showing proof that I've tried your method but still kept on failing to reboot to recovery..
When i try the command "fastboot boot recovery-clockwork-5.0.2.0-passion.img", the phone simply restarts and goes back to the 'X' boot screen and gets stuck there.
Could anyone please find me an genuine unedited gingerbread 2.3.4 ROM so I can PASSIMG it? ... I've downloaded several rooted ones.. but all seem to need the "android-info" file
fastboot reboot recovery
No "reboot-recovery".
And if you still get stuck on "X" when you reboot to recovery - it means that your recovery is corrupted/unusable too, and you need to PASSIMG everything.
Generally, booting the recovery through "fastboot boot" should have done enough - if your phone can't boot, it might probably be a HW problem preventing it from booting, and in that case - nothing will help.
fastboot reboot recovery
No "reboot-recovery".
And if you still get stuck on "X" when you reboot to recovery - it means that your recovery is corrupted/unusable too, and you need to PASSIMG everything.
Generally, booting the recovery through "fastboot boot" should have done enough - if your phone can't boot, it might probably be a HW problem preventing it from booting, and in that case - nothing will help.
Click to expand...
Click to collapse
I've attached an image trying out "fastboot reboot recovery" fastboot doesnt even seem to send that command to the phone..
Could anyone please provide me with a genuine stock gingerbread 2.3.4 or higher PASSIMG file? i've searched a lot but all i see are modded or rooted ones.
Yes, you're right. Fastboot can't reboot to recovery, only adb.
Oh well, in that case you're out of luck. You can't PASSIMG without power button, so if "fastboot boot some_boot_image" doesn't help - there's not much left to do.
You could always disassemble the phone and fix the power button...
knaphih said:
I've attached an image trying out "fastboot reboot recovery" fastboot doesnt even seem to send that command to the phone..
Could anyone please provide me with a genuine stock gingerbread 2.3.4 or higher PASSIMG file? i've searched a lot but all i see are modded or rooted ones.
Click to expand...
Click to collapse
Here's the 2.3.6 PASSIMG zip file link. Follow the directions. If you can get into BootLoader, your phone should automatically boot this if you have it named to PASSIMG.zip, and on the ROOT of your SD card:
http://forum.xda-developers.com/showthread.php?t=1312540
You guys are life savers troby86 and Jack_R1..
Yes, you're right. Fastboot can't reboot to recovery, only adb.
Oh well, in that case you're out of luck. You can't PASSIMG without power button, so if "fastboot boot some_boot_image" doesn't help - there's not much left to do.
You could always disassemble the phone and fix the power button...
Click to expand...
Click to collapse
I've seen an in depth video tutorial on youtube and attempted to repair the power button on my own.. however I failed since I cannot do such tiny soldering..
Here's the 2.3.6 PASSIMG zip file link. Follow the directions. If you can get into BootLoader, your phone should automatically boot this if you have it named to PASSIMG.zip, and on the ROOT of your SD card:
http://forum.xda-developers.com/show....php?t=1312540
Click to expand...
Click to collapse
Thankyou so much . This is what I've been searching for.. I'll let you guys know the outcome after I download and fix my phone (hopefully I will)
knaphih said:
You guys are life savers troby86 and Jack_R1..
I've seen an in depth video tutorial on youtube and attempted to repair the power button on my own.. however I failed since I cannot do such tiny soldering..
Thankyou so much . This is what I've been searching for.. I'll let you guys know the outcome after I download and fix my phone (hopefully I will)
Click to expand...
Click to collapse
Did the link I provided work? If not here is the actual file:
http://www.multiupload.com/KVY1MG1HGH
troby86 said:
Did the link I provided work? If not here is the actual file:
http://www.multiupload.com/KVY1MG1HGH
Click to expand...
Click to collapse
wow troby86
your still here
http://forum.xda-developers.com/showthread.php?t=1350288
atleast have the decency to refund my money you jackass
mally2 said:
wow troby86
your still here
http://forum.xda-developers.com/showthread.php?t=1350288
atleast have the decency to refund my money you jackass
Click to expand...
Click to collapse
I realize the situation you are in sucks, but please don't let your frustration carry over into these threads. We are here to help the original poster, not to try and get claims resolved and to sling mud. Try to keep this thread a helpful thread
Thanks
bassmadrigal said:
I realize the situation you are in sucks, but please don't let your frustration carry over into these threads. We are here to help the original poster, not to try and get claims resolved and to sling mud. Try to keep this thread a helpful thread
Thanks
Click to expand...
Click to collapse
well what do you know, he may just ask the OP to send him his nexus to get it fixed and you will never hear from him again.... just warning y'all thats all....
I'm afraid I may have bricked my phone but good this time.
I had gone through the unlock,flash recovery, etc process a few months ago. Today I downloaded and installed what I think is a rom that was not intended for my phone and everything went south.
I am still able to boot into bootloader, and I can select FASTBOOT and plug the phone in. It switches to FASTBOOT USB, so I type
fastboot erase cache
That seems to work fine so I next type
fastboot flash recovery openrecovery-twrp-2.5.0.0-m7.imp
I get sending 'recovery'
OKAY
writing 'recovery'
OKAY
finished.
Swell So I power down and reboot to fastboot, then select recovery. I get a flash of the TWRP screen, then it goes blank and it tries to boot to the OS. Since there isn't one I get stuck at the htc quietly brilliant logo screen. (I'm not feeling particularly brilliant at the moment).
I just flashed openrecovery-twrp-2.6.3.3-m7.img and the same thing happened. I went back to 2.5.0.0-m7 and the same thing.
Am I screwed beyond repair or is there a way to fix this? Perhaps I'm using the wrong recovery image? If so can someone point me to the right one and where I might be able to download it from? I like TWRP a lot but their website is not the best I've ever seen.
dlbarron said:
I'm afraid I may have bricked my phone but good this time.
I had gone through the unlock,flash recovery, etc process a few months ago. Today I downloaded and installed what I think is a rom that was not intended for my phone and everything went south.
I am still able to boot into bootloader, and I can select FASTBOOT and plug the phone in. It switches to FASTBOOT USB, so I type
fastboot erase cache
That seems to work fine so I next type
fastboot flash recovery openrecovery-twrp-2.5.0.0-m7.imp
I get sending 'recovery'
OKAY
writing 'recovery'
OKAY
finished.
Swell So I power down and reboot to fastboot, then select recovery. I get a flash of the TWRP screen, then it goes blank and it tries to boot to the OS. Since there isn't one I get stuck at the htc quietly brilliant logo screen. (I'm not feeling particularly brilliant at the moment).
I just flashed openrecovery-twrp-2.6.3.3-m7.img and the same thing happened. I went back to 2.5.0.0-m7 and the same thing.
Am I screwed beyond repair or is there a way to fix this? Perhaps I'm using the wrong recovery image? If so can someone point me to the right one and where I might be able to download it from? I like TWRP a lot but their website is not the best I've ever seen.
Click to expand...
Click to collapse
You could try downloading the dev edition RUU and running it to get your phone to a working stock. After that, you could flash your specific rom to get back to your native stock. There are other options as well.
Try flashing CWM as well and see what happens ...
dlbarron said:
I'm afraid I may have bricked my phone but good this time.
I had gone through the unlock,flash recovery, etc process a few months ago. Today I downloaded and installed what I think is a rom that was not intended for my phone and everything went south.
I am still able to boot into bootloader, and I can select FASTBOOT and plug the phone in. It switches to FASTBOOT USB, so I type
fastboot erase cache
That seems to work fine so I next type
fastboot flash recovery openrecovery-twrp-2.5.0.0-m7.imp
I get sending 'recovery'
OKAY
writing 'recovery'
OKAY
finished.
Swell So I power down and reboot to fastboot, then select recovery. I get a flash of the TWRP screen, then it goes blank and it tries to boot to the OS. Since there isn't one I get stuck at the htc quietly brilliant logo screen. (I'm not feeling particularly brilliant at the moment).
I just flashed openrecovery-twrp-2.6.3.3-m7.img and the same thing happened. I went back to 2.5.0.0-m7 and the same thing.
Am I screwed beyond repair or is there a way to fix this? Perhaps I'm using the wrong recovery image? If so can someone point me to the right one and where I might be able to download it from? I like TWRP a lot but their website is not the best I've ever seen.
Click to expand...
Click to collapse
Seen this happen before, it was because 'fast boot' was selected in Settings.
Settings -> Power -> make sure "fast boot" is unticked. Then power the phone off, then boot to fastboot and flash recovery again.
redbull123 said:
Seen this happen before, it was because 'fast boot' was selected in Settings.
Settings -> Power -> make sure "fast boot" is unticked. Then power the phone off, then boot to fastboot and flash recovery again.
Click to expand...
Click to collapse
I can't get to settings. It hangs at the HTC logo.
v-b-n said:
Try flashing CWM as well and see what happens ...
Click to expand...
Click to collapse
I did try that. It hangs at the "Entering Recovery..." screen.
dlbarron said:
I did try that. It hangs at the "Entering Recovery..." screen.
Click to expand...
Click to collapse
did u "fastboot erase cache" after flashing the recovery?
kibmikey1 said:
You could try downloading the dev edition RUU and running it to get your phone to a working stock. After that, you could flash your specific rom to get back to your native stock. There are other options as well.
Click to expand...
Click to collapse
Is that the right recovery?
Don't I have to be able to boot into recovery to run the RUU? Where can I get it?
What are some of the other options?
nkk71 said:
did u "fastboot erase cache" after flashing the recovery?
Click to expand...
Click to collapse
Yes, I tried erase cache before and after, no difference.
I think you screwed something up in your device's file system, partition table or your bootloader is somehow damaged. As you can run fastboot, I strongly suggest a RUU. To get the right RUU for your phone there are numerous guides such as:
http://forum.xda-developers.com/showthread.php?t=2428276
http://forum.xda-developers.com/showthread.php?t=2158151
xxmorph3u5xx said:
I think you screwed something up in your device's file system, partition table or your bootloader is somehow damaged. As you can run fastboot, I strongly suggest a RUU. To get the right RUU for your phone there are numerous guides such as:
http://forum.xda-developers.com/showthread.php?t=2428276
http://forum.xda-developers.com/showthread.php?t=2158151
Click to expand...
Click to collapse
I think so. I just tried flashing CWM and was able to boot into it. It's showing unable to mount messages.
Looks like I have no choice but to try the RUU. I have been hesitant because I have yet to find a good explanation and good downloads of all the parts I need. Is there something like that available?
all right, this will certainly add to the confusion.
I flashed recovery_m7_att_stock and was able to get into it a little. Then I went back to the bootloader and flashed openrecovery-twrp-2.5.0.0-m7 and actually get into it.
WHAT?
I pushed the CM nightly rom to it and it installed, although there were some errors about not being able to mount some things data and cache. But it did install and I was able to get into CM.
I'm almost afraid to try anything else at this point.
dlbarron said:
I think so. I just tried flashing CWM and was able to boot into it. It's showing unable to mount messages.
Click to expand...
Click to collapse
unable to mount /cache is OK (caused by fastboot erase cache)
unable to mount /data is not ok, could be a corrupt /data partition
nkk71 said:
unable to mount /cache is OK (caused by fastboot erase cache)
unable to mount /data is not ok, could be a corrupt /data partition
Click to expand...
Click to collapse
After rebooting I'm still able to get into TWRP. I've been able to flash a couple of ROMs (very carefully) and I'm no longer seeing any errors about not being able to mount.
Looks like what ever was wrong has been corrected. Now all we have to do is figure out what went wrong and what I did to fix it.
Thanks everyone.