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.
Related
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.
Hi there.
This is not the first problem I have had with my G1 and Cyanogen cm5 or cm6. Yesterday my phone was working just fine, battery got low so I turned it off and out it on the charger. So I go to turn the phone on and I am stuck at the bootscreen.
I can get into fastboot use the cam/power button combo. But I can not get into recovery at all.
At the hboot/fastboot screen I have the following listed, BTW it's the screen with the 3 androids at the bottom on skateboards.
DREAM PVT 32B ENG S-OFF
HBOOT-1.33.2005 (Drea10000)
CPLD-4
RADIO-2.22.23.02
Apr 20 2009, 15:30:43
When I switch over to Fastboot then back to Hboot screen I get this.
SD checking.
Loading...[DREADIAG.zip]
No image!
Loading...[DREADIA2.nbh]
No image or wrong image!
Loading...[DREADIAG.nbh]
No image or wrong image!
SD Checking...
Loading...[DREADIAG.zip]
No image!
Loading...[DREADIA2.nbh]
No image or wrong image!
Click to expand...
Click to collapse
What can I do to get back in business? If I have to put it back to stock, that is fine. I plan on selling it and getting the new Samsung Vibrant.
I have to stock 1gb card in the G1 right now. I have the following files on it.
recovery.img
update.zip
DREAIMG.nbh
In fastboot I get this for device.
HT852GZ12970
UPDATE:
I have been able to flash recovery via fastboot, now just trying to get a good image on there to reflash.
Also curious about this.. friend's having the same problem with the same rom.
Well I am back up and running.
What I had to do was flash a new recovery image using fastboot. Once I did that I was able to boot into recovery; wipe everything and reflash a new ROM (went with SuperBad, since CM keeps messing me up).
If you need more details, let me know.
svtcontour said:
Well I am back up and running.
What I had to do was flash a new recovery image using fastboot. Once I did that I was able to boot into recovery; wipe everything and reflash a new ROM (went with SuperBad, since CM keeps messing me up).
If you need more details, let me know.
Click to expand...
Click to collapse
I was going to tell you to do just that until I read:
UPDATE:
I have been able to flash recovery via fastboot, now just trying to get a good image on there to reflash.
Click to expand...
Click to collapse
I thought you had figured it out already. I probably could have saved you some time. Sorry.
How did you flash recovery in fastboot? Right now I am going through the same thing that you did!
I have a G1/Cyanogen 5.0.8
mjybarr said:
How did you flash recovery in fastboot? Right now I am going through the same thing that you did!
I have a G1/Cyanogen 5.0.8
Click to expand...
Click to collapse
Code:
fastboot flash recovery recovery.img
The standard procedure is to power on the phone with camera/power button combo, be sure to get the phone into fasboot mode.
Open up the CMD window in windows, CD to the directory you have the recovery.img file in. Use the above command. Then you can wipe and reinstall the update.zip with another rom.
That should do it,l assuming you already installed all the USB and ADB drivers and software.
svtcontour said:
Code:
fastboot flash recovery recovery.img
The standard procedure is to power on the phone with camera/power button combo, be sure to get the phone into fasboot mode.
Open up the CMD window in windows, CD to the directory you have the recovery.img file in. Use the above command. Then you can wipe and reinstall the update.zip with another rom.
That should do it,l assuming you already installed all the USB and ADB drivers and software.
Click to expand...
Click to collapse
So what is CMD and what do you mean "CD to the directory you have the recovery.img file in." I did some research on xda-forums about adb, sdk, fasboot. Do I need to do that and install all those programs. As you can tell I am a new to this. So I need some thorough directions. Thank you so much for helping. I need to get back to Android, right now I am using an old blackberry......and it totally sucks!
CMD will bring up the DOS window in windows. Go to the START button and look for RUN, them type in CMD. A black window will pop up.
CD means change directory. Example: cd c:\temp\adb will bring you to that exact directory. Just make sure you remember where you put the recovery.img file and CD to that.
I would go to this post and follow the directions to install ADB and the USB drivers.
http://androidcommunity.com/forums/f10/adb-fastboot-for-rookies-18124/
I had the same problem in a rooted Hero, but i lost the recovery image as well as the ROM. I could not flash the new recovery image using fastboot because my SPL does not allow it.
Search in google for
Follow the instructions in
wiki.cyanogenmod.com/index.php?title=RE-recovery-img#Restoring_the_custom_recovery_image
to flash a recovery image (cyanogen or amon-ra, just check it to be the one for your model).
It solved my problem!
I have the same problem (with CM6)
adb works well, but fastboot is waiting for devices
G1 is on fastboot usb screen
DREAM PVT 32B ENG S-OFF
HBOOT-1.33.2005 (DREA20000)
CPLD-4
RADIO-2.22.19.261
Apr 20 2009,15:30:43
the command "fastboot devices" doesn't work : i don't even have a feedback like "list of devices attached"
does anyone know what I have failed ?
Update: miserable failure: I forgot to cd to C:\path\android-sdk-windows\tools\
sorry about it
Reinstalling recovery, then installing the latest nightlies did the trick for me. Did not need to wipe.
Hope this helps.
Hi,
I bought a faulty Nexus one from ebay, thought I can fix it, as I did buy a faulty desire from ebay and was able to fix it. This time im not so lucky I guess.
So here it is:
The phone is stuck at X when booting normally.
I can access HBoot (But not Hboot USB Plug, because USB debugging is not enabled) and Fastboot USB. I unlocked Hboot. Fastboot in PC recognizes the phone but ADB does not as usb debugging is not enabled.
The phone is not Rooted
Here are my ideas so far:
Get somehow debugging on with some commands (No luck from reshearching in google)
Reflash stock rom with PASSIMG.ZIP in sdcard, but my phone does not recognize the file from my sdcard (I'm pretty certain im doing something wrong or my idea is somehow wrong)
Flash new images through FASTBOOT, but every time Signature check fails (Shipped-roms.com).
Root with superboot, but signature check failed here too.
Flash a recovery, signature check fails.
I will reguraly update my tries
Please suggest correction to my ideas or suggest new ones!
Help will be much appreciated!
I admit it, the phone might be briked, but I want to make sure that I have tried everything before I abandon this project.
And ofcourse I have no Warranty.
What file are you using for passimg.zip? Make sure it's not a zip inside a zip.
What images are you using via the fastboot flash command?
Sent from my Nexus One
You didn't unlock the bootloader, it seems - because if you did, it wouldn't be checking signatures, and you'd be able to flash anything.
First of thanks to both of you for helping.
I'm pretty sure that i do not have zip inside zip and I downloaded them from shipped roms.com -> android -> Passion-> PASSIMG_Google .... .ZIP, (Then renamed it ofcourse) Is there a difference what version of android i use?
The issue with this is, it checks the SD CARD and does not find anything. I have seen from google that the most common issue is that it starts to check the .zip file but then aborts. Does the SDCARD have to be a goldcard (I do have a goldcard but it might be faulty, right?)
I tried fastboot flash PASSIMG_Google.... .ZIP; Fastboot Flashall ( With having boot, recovery, system in my fastboot folder)
Maybe I should try to flash everything the .zip has in it seperately because that succeded for boot, system and recovery but I was too afraid to flash every partitation (Like Radio which seems to be the scariest and the most easiest way to brick phone)
For the third answer, I have ***UNLOCKED*** in bootloader in purple and top on the screen.
Once again thanks and keep suggesting!
Unpack the ZIP and flash each image separately.
Leave the radio as is, if it's updated enough (5.08 or 5.12). In any case, fastboot won't allow you to flash bad radio - and the risk of bricking the phone using fastboot is near 0.
For passimg.zip, you need to download the FRG33 shipped ROM from shipped-roms.com then EXTRACT the zip file that is inside the zip that you downloaded. Rename that file to passimg.zip
For fastboot, flash boot and system seperately.
When you boot the device normally, do you see the lock icon below the four colored x?
Sent from my Nexus One
Okay,
Did it one by one (PASSIMG_Passion_Google_WWE_2.16.1700.1_FRG33_release_signed.zip):
Succeeded:
Boot, Recovery, System and Userdata (that was only 3Kb)
Failed with signature check (Remote:Signature check failed):
Splash1, spcustom,
Did not do:
Radio
I'm going to post more details:
When booting up, it displays the X normally with the unlocking badge on the bottom of the screen and vibrates once. Then it goes black for a second or even less, the same images comes on and then it vibrates 6-7 times.
now that you successfully flashed the stock recovery, cam you boot into it?
Sent from my Nexus One
Nope, it does that what I described on the previous post
Oh and what's more it randomly during no activity being in fastboot vibrates as well for 5 times or so. It does this rarely but it's there
http://forum.xda-developers.com/showthread.php?t=710937
Thanks, Well thats it then for now, just have to figure out what to do now
Sounds like you need to get the PASSIMG.zip method to work, or unlock and flash a new recovery like amon ra, and flash a full rom with sig checks off.
siimplangi said:
Nope, it does that what I described on the previous post
Oh and what's more it randomly during no activity being in fastboot vibrates as well for 5 times or so. It does this rarely but it's there
Click to expand...
Click to collapse
Ok, but can you boot into recovery? In other words, boot into the bootloader and select recovery.
any solution?
efrant said:
Ok, but can you boot into recovery? In other words, boot into the bootloader and select recovery.
Click to expand...
Click to collapse
hi guys.i have exactly same situation.
does anyone have a solution fir this?
kobi_eidelman said:
hi guys.i have exactly same situation.
does anyone have a solution fir this?
Click to expand...
Click to collapse
Did you try all the solutions suggested above (passimg, fastboot flash, etc)? If yes then no I don't think so.
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....
Hey guys, I am starting this thread in hopes of getting an answer to help anyone else who may be experiencing the same problem that I am.
For the past couple of days i have been trying to root my HTC One using the "fastboot flash recovery" method using both CWM Touch and Classic along with trying TWRP. It appears that the recovery flash works each time by giving me the OKAY message in cmd. I go into the bootloader and everything appears as it worked by saying **TAMPERED** and **UNLOCKED** at the top but when i try to boot into recovery, the phone shows the HTC entering recovery screen but then fails and shuts off the phone before going into the recovery image.
I know that all probably sounded confusing and if you have any other questions i will be glad to answer them. All i want is my phone rooted so i can take off the bloatware.
Any help is welcomed and thanks for your help!
.
[email protected] said:
Hey guys, I am starting this thread in hopes of getting an answer to help anyone else who may be experiencing the same problem that I am.
For the past couple of days i have been trying to root my HTC One using the "fastboot flash recovery" method using both CWM Touch and Classic along with trying TWRP. It appears that the recovery flash works each time by giving me the OKAY message in cmd. I go into the bootloader and everything appears as it worked by saying **TAMPERED** and **UNLOCKED** at the top but when i try to boot into recovery, the phone shows the HTC entering recovery screen but then fails and shuts off the phone before going into the recovery image.
I know that all probably sounded confusing and if you have any other questions i will be glad to answer them. All i want is my phone rooted so i can take off the bloatware.
Any help is welcomed and thanks for your help!
Click to expand...
Click to collapse
Same thing happend to me when I tried to flash a new rom. I ended up reinstalling the TWRP file in the fastboot CMD. "Fastboot flash recover "twrp file name that you put in fastboot.img"
What carrier are you?
Edit: sorry, misread your post I think - if you see recovery trying to open for a split-second, try commanding
'fastboot erase cache' (in fastboot usb, of course) and try again
Otherwise, depending what carrier you are, I think there is a issue with that, I'm not familiar though as I'm in the UK.
Sent from my HTC One using xda premium
redbull123 said:
What carrier are you?
Edit: sorry, misread your post I think - if you see recovery trying to open for a split-second, try commanding
'fastboot erase cache' (in fastboot usb, of course) and try again
Otherwise, depending what carrier you are, I think there is a issue with that, I'm not familiar though as I'm in the UK.
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
OK thanks I'll be sure to try that. I'm currently on Sprint (Us
[email protected] said:
OK thanks I'll be sure to try that. I'm currently on Sprint (Us
Click to expand...
Click to collapse
There's a Sprint version of TWRP, try flashing this and see if it makes a difference... http://techerrata.com/file/twrp2/m7wls/openrecovery-twrp-2.5.0.0-m7wls.img
do a 'fastboot erase cache' before 'fastboot flash recovery your_recovery.img'
redbull123 said:
There's a Sprint version of TWRP, try flashing this and see if it makes a difference... http://techerrata.com/file/twrp2/m7wls/openrecovery-twrp-2.5.0.0-m7wls.img
do a 'fastboot erase cache' before 'fastboot flash recovery your_recovery.img'
Click to expand...
Click to collapse
Big Thanks! This worked flawlessly
redbull123 said:
There's a Sprint version of TWRP, try flashing this and see if it makes a difference...
do a 'fastboot erase cache' before 'fastboot flash recovery your_recovery.img'
Click to expand...
Click to collapse
Wow! I spent 3 hours looking for a solution to the recovery issue, and the link to the sprint twrp image worked perfectly! Wish I had seen it sooner!
Thanks