Hello all,
I think I may have bricked my nexus one. It is completely my fault for attempting things that I knew little about, so flame away But after the flaming, if anyone is willing to help I would be sooooo thankfull...
I successfully rooted my phone following the instructions on this page: (all links edited with a double asterisk as I don't believe I can post links)
h**p://theunlockr.com/2010/01/02/how-to-root-the-nexus-one/
Then successfully installed cyanogenmod (which is awesome!) following this page:
h**p://theunlockr.com/2010/01/08/how-to-load-a-custom-rom-on-the-nexus-one/
All was well, I even got the modaco desire rom up and running, and was happily switching back and forth using the recovery screen. I had nand backups for specific setups, etc.
Then I decided it would be good to know how to go back to stock, and found this page:
h**p://**w.androidspin.com/2010/05/06/guide-unrooting-your-nexus-one-its-like-it-never-happened-almost/
I followed the instructions to the letter (I think) except for erasing userdata (it said "failed: remote not allowed"). I thought that things would be ok, since I'd recently wiped, so I followed the page till the end.
The phone rebooted, and I got the original nexus boot animation - but it's in an endless loop! What's worse, it that now when I try to go to the bootloader or recovery mode, I get the exclamation triangle with the little android.
Is there any way through a command prompt (or other method) that I can fix this? I tried to re-flash the RA recovery image through the command prompt, but the response was, "waiting for device."
ANYTHING that anyone can suggest to help, I would be so thankful! I've been loving the nexus, and hate to think that I crippled it
Thanks in advance,
Randy
I doubt its bricked.
Noticed you didnt mention that fast boot doesnt work? (power button+trackball) try it.
Once you get to fastboot you can flash any ROM back. (fastboot flash **** commands from a command shell)
Did you ever perform a Nand Backup from Recovery?
It's not bricked, the only way to brick is to interrupt power when flashing a Radio image
Connect phone to PC. Open command prompt.
adb reboot recovery
Wipe, reflash.
So far, nobody has managed to brick a Nexus. There is no way as the fastboot mode can restore the whole phone and can't be messed with. Make sure you have the latest version of the SDK with correct USB drivers and fastboot. Then try and reflash the recovery image.
-------------------------------------
Sent from my Nexus One
nexus5894 said:
So far, nobody has managed to brick a Nexus. There is no way as the fastboot mode can restore the whole phone and can't be messed with. Make sure you have the latest version of the SDK with correct USB drivers and fastboot. Then try and reflash the recovery image.
-------------------------------------
Sent from my Nexus One
Click to expand...
Click to collapse
Actually...
http://forum.xda-developers.com/showpost.php?p=6320068&postcount=404
Paul22000 said:
Actually...
http://forum.xda-developers.com/showpost.php?p=6320068&postcount=404
Click to expand...
Click to collapse
............................
It worked!!!!!
It worked!!
britoso, thank you soooooo much! The only way that I knew to get into bootloader/recovery was via power button/volume down, but power/trackball brought up the bootloader screen, and I clicked on fastboot. I was able to flash the RA recover image through the command terminal via fastboot, then able to get into recovery. I had cyan and modaco sense on the sd, and was able to flash one of them on.
I never thought I'd be so happy to see "quietly brilliant"!!! I WILL buy you a beer, a case in fact as soon as money clears my paypal account.
I have learned my lesson, research research research. (I did do some, but not enough to feel comfortable with what I was doing - hence my cry for help!)
Other than the phone and OS itself, the thing I like most about the nexus is the fact that one CAN root, and then customize (sold a Telus moto droid because I could not do that very thing).
I digress... thanks again so much!
And Paul, thanks for your sense ROM; I've had HTC phones from the Touch to the the diamond to the Hero, and missed the UI!
Randy Malkoski said:
It worked!!
britoso, thank you soooooo much! The only way that I knew to get into bootloader/recovery was via power button/volume down, but power/trackball brought up the bootloader screen, and I clicked on fastboot. I was able to flash the RA recover image through the command terminal via fastboot, then able to get into recovery. I had cyan and modaco sense on the sd, and was able to flash one of them on.
I never thought I'd be so happy to see "quietly brilliant"!!! I WILL buy you a beer, a case in fact as soon as money clears my paypal account.
I have learned my lesson, research research research. (I did do some, but not enough to feel comfortable with what I was doing - hence my cry for help!)
Other than the phone and OS itself, the thing I like most about the nexus is the fact that one CAN root, and then customize (sold a Telus moto droid because I could not do that very thing).
I digress... thanks again so much!
And Paul, thanks for your sense ROM; I've had HTC phones from the Touch to the the diamond to the Hero, and missed the UI!
Click to expand...
Click to collapse
Glad to hear it. You learn the most by trial and error.
I think i got the same problem. i tried to Unlock Bootloader and Root Google Nexus One which was successful but then i tried to superboot it and when it came to the part where you "double click the ‘install-superboot-windows.bat’ file" i clicked it but it did not go to the nnext screen where the superboot completes it just stayed at the "bootloader screen". i must hve not done something or done something wrong i dont know.
So then i unplugged the phone from the pc and rebooted it. when it reeboted i wasnt getting any network, the phone was slow and the notification bar would not slide down...also i noticed the phone restarting on itself...
/i tried all kinds of "restore to factory settings" but not solved. Can anyone tell me what to do tht will work. I coud not understand what was said in the above thread as i am new to this android n my first time rooting n stuff n i believe that solution would work for me too..if some one could please explain in simple tirms the steps i need to take would be good...
Really appreciate it....
revonomics said:
I think i got the same problem. i tried to Unlock Bootloader and Root Google Nexus One which was successful but then i tried to superboot it and when it came to the part where you "double click the ‘install-superboot-windows.bat’ file" i clicked it but it did not go to the nnext screen where the superboot completes it just stayed at the "bootloader screen". i must hve not done something or done something wrong i dont know.
So then i unplugged the phone from the pc and rebooted it. when it reeboted i wasnt getting any network, the phone was slow and the notification bar would not slide down...also i noticed the phone restarting on itself...
/i tried all kinds of "restore to factory settings" but not solved. Can anyone tell me what to do tht will work. I coud not understand what was said in the above thread as i am new to this android n my first time rooting n stuff n i believe that solution would work for me too..if some one could please explain in simple tirms the steps i need to take would be good...
Really appreciate it....
Click to expand...
Click to collapse
Tell me what i need to download again and how to go about it...i really need my phone working again ((((
Related
I just tried flashing the Gingerbreadime.zip and followed the directions to the letter and I experienced my first soft brick. The phone went into a boot loop at the mytouch screen. Luckily I was able to go into Recovery and restored the backup I had made after rooting and turning s=off. It appears to have restored okay as I still have root etc. Does anyone have any idea how or why this happened ? This zip was posted in Droid-Life and was advertised as good for all android 2.2 devices. I have never used adb but have it set up on my phone so I guess I had better get more familiar with it. I have flashed my Vibrant numerous times using Odin and Rom manager but I don't believe that there is a similar program for the Mt4g (Odin that is) I guess I have been spoiled by my Vibrant as it seems to have more options to recover with and are easier to use from what I can tell. I do love this MT4g though It is probably the best all around phone I have ever owned. Any and all info and help is greatly appreciated.:
to my knowledge there has been no gingerbread port for our device yet. Your lucky you didn't brick your device.
tenbeau said:
I just tried flashing the Gingerbreadime.zip and followed the directions to the letter and I experienced my first soft brick. The phone went into a boot loop at the mytouch screen. Luckily I was able to go into Recovery and restored the backup I had made after rooting and turning s=off. It appears to have restored okay as I still have root etc. Does anyone have any idea how or why this happened ? This zip was posted in Droid-Life and was advertised as good for all android 2.2 devices. I have never used adb but have it set up on my phone so I guess I had better get more familiar with it. I have flashed my Vibrant numerous times using Odin and Rom manager but I don't believe that there is a similar program for the Mt4g (Odin that is) I guess I have been spoiled by my Vibrant as it seems to have more options to recover with and are easier to use from what I can tell. I do love this MT4g though It is probably the best all around phone I have ever owned. Any and all info and help is greatly appreciated.:
Click to expand...
Click to collapse
There are people experiencing the same thing in the Nexus forum. Personally I would stay away from anything that is not specifically built for this phone as its a completely different OS than Vanilla or Moto Droid or etc. etc.
bobsbbq said:
to my knowledge there has been no gingerbread port for our device yet. Your lucky you didn't brick your device.
Click to expand...
Click to collapse
yes I a sure am. I trusted the Dorid-Life site and should not have. Thanks for the swift response...
setzer715 said:
There are people experiencing the same thing in the Nexus forum. Personally I would stay away from anything that is not specifically built for this phone as its a completely different OS than Vanilla or Moto Droid or etc. etc.
Click to expand...
Click to collapse
I sure intend to and I should have got on this forum before I even attempted to flash it. Right now everything seems fine except I cannot get into recovery only clockworkimode recovery. I am holding down the volume down button and pressing the power button at the same time and the device just reboots. Any ideas and what could be causing that? I am embarassed to say that my ignorance that pushed me to flash that zip is probably at the root of it. Any steps that I can take to enable me to get into stock recovery to check and make sure S=off?
Edit: Just pulled battery and sim card and than put them back in and the device went into stock recovery and s=off so I hope that all is okay and I did not create some ghosts that will show up when I attempt to flash a rom later on.
Please post questions in Q&A section.
I did the same thing. I flashed the .zip file from droid life forum and got a success message when I installed it through recovery and mine never bootlooped. I didn't get the gingerbread keyboard but it didn't bootloop either
Sent from my HTC Glacier using XDA App
tenbeau said:
I sure intend to and I should have got on this forum before I even attempted to flash it. Right now everything seems fine except I cannot get into recovery only clockworkimode recovery. I am holding down the volume down button and pressing the power button at the same time and the device just reboots. Any ideas and what could be causing that? I am embarassed to say that my ignorance that pushed me to flash that zip is probably at the root of it. Any steps that I can take to enable me to get into stock recovery to check and make sure S=off?
Edit: Just pulled battery and sim card and than put them back in and the device went into stock recovery and s=off so I hope that all is okay and I did not create some ghosts that will show up when I attempt to flash a rom later on.
Click to expand...
Click to collapse
I think you mean bootloader? You only have 1 recovery. If you flashed clockwork you no longer have stock recovery. Vol Down + Pwr gets you to bootloader or SPL where it shows S=off.
I did not flash the zip (sounds like an overkill to flash a zip for new KB). I ADB pushed both files and got a FC on multi-touch KB... oh well, I like HTC_IME better anyway
tenbeau said:
I sure intend to and I should have got on this forum before I even attempted to flash it. Right now everything seems fine except I cannot get into recovery only clockworkimode recovery. I am holding down the volume down button and pressing the power button at the same time and the device just reboots. Any ideas and what could be causing that? I am embarassed to say that my ignorance that pushed me to flash that zip is probably at the root of it. Any steps that I can take to enable me to get into stock recovery to check and make sure S=off?
Edit: Just pulled battery and sim card and than put them back in and the device went into stock recovery and s=off so I hope that all is okay and I did not create some ghosts that will show up when I attempt to flash a rom later on.
Click to expand...
Click to collapse
make sure fastboot is checked off otherwise you cant get into the bootloader. to make sure it is off go to: menu, settings, applications and uncheck fastboot. you're good to go then. to get into recovery, you can do it thru bootloader or by opening up rom manager and clicking on the "reboot to recovery" option
setzer715 said:
There are people experiencing the same thing in the Nexus forum. Personally I would stay away from anything that is not specifically built for this phone as its a completely different OS than Vanilla or Moto Droid or etc. etc.
Click to expand...
Click to collapse
the website was not specific enough. the port at the current moment is for motorola droid devices. they should have been more specific instead of saying any rooted 2.2 android phone. even if you do get it on your phone, its only going to force close every time you try and type something. thats what happened to me, so after about 24 hours i said **** it and removed it. swype in my opinion is better anyway. im trying to port the g2 swype to our phone so we can have a swype with a mic on the keyboard. oddly, ours didnt come with one.
Hi all!
Seriously in need of some expert help from your kind selves. Basically my phone is rooted with custom roms. I'm needing to try to get it back to normal as it has developed a hardware fault in the way that the volume key doesn't work, more so the down volume. Sometimes the up volume works when it feels like it. The camera itself has also been playing up and not working at times (not sure if this would be hardware related). As you can guess I'm wanting to get the phone repaired under warranty. The major headache comes when I need to get into the bootloader and I can't with the down button not working. Earlier I flashed a different kernel and when the phone went to reboot all hell broke loose. I'm currently stuck on the white screen with HTC logo. So without getting into the bootloader to try to recover I'm in serious bother! I tried this link and followed all the steps but in the end it just kept giving me an unknown error message
http://forum.xda-developers.com/showthread.php?t=841890
I'm just trying to get the phone back up and running and then will take it from there to return it back to stock if possible. One thing I didn't try was the fact I have a 1.84 rom on and tried to flash with 1.72. May well try a 1.84 later on when I get the chance.
I hope you basically understand what I've done and what I'm trying to achieve and the problems I've got.
Thanks in advance if you can provide any solutions or ideas to try.
oooo boi thats gota hurt... but dont worry.. download "quickboot" from the market with it u can go to bootloader and cmw recovery .. about the rest.. i didnt get it.. u have 1.72 stock ruu and u want to get 1.84 ? why not just use 1.32 old rom and send it back repair guys ?
Find the downgrade thread in the Dev section, download the PD98IMG.zip from that thread. Put that on your SDcard.
Now you want to boot into bootloader which maybe difficult given your button predicament. I am sure there must be a fastboot/adb command to do this, possibly
fastboot reboot-bootloader
The bootloader should read and flash the PD98IMG.zip automatically, returning you to stock.
Hi mate. I had same problem my volume buttons don't work at all but i managed to flash latest recovery witch let's you scroll with home button don't no if this helps but try it
Thanks guys for trying to help. Leatherface I'm stuck on the white boot screen with htc logo and it won't go any further so can't get into market to download any apps. Or is the program you're talking about available for pc? I have custom roms on and not stock but want to put stock back on to send in for repair.
AndyHarney I will try your advice later but obviously as soon as I turn phone on it goes straight to the boot screen so I really can't see how I could get into the bootloader any other way but I may be wrong. Hopefully I am!!
Biggy I did flash with the latest CWM right before it went beserk but still no way of getting into bootloader.
I'm off for an Easter drink now to take my mind off it coz it's stressing me out and will return soon to butcher my phone a little more lol
Happy Easter
Of course, to use fastboot you need to be in fastboot in the bootloader.
Using the app Leather|Face mentioned, is there an option to boot into bootloader?
Anyways, enjoy your bank holiday.
thegeordiehunk said:
Thanks guys for trying to help. Leatherface I'm stuck on the white boot screen with htc logo and it won't go any further so can't get into market to download any apps. Or is the program you're talking about available for pc? I have custom roms on and not stock but want to put stock back on to send in for repair.
AndyHarney I will try your advice later but obviously as soon as I turn phone on it goes straight to the boot screen so I really can't see how I could get into the bootloader any other way but I may be wrong. Hopefully I am!!
Biggy I did flash with the latest CWM right before it went beserk but still no way of getting into bootloader.
I'm off for an Easter drink now to take my mind off it coz it's stressing me out and will return soon to butcher my phone a little more lol
Happy Easter
Click to expand...
Click to collapse
as long as the rom ur using is not cynogenmod7... ur warranty isnt void my friend
did u try to re-flash a rom ? trying flashing a fresh rom.. full wipe ur phone before.. bellow in atttachment is full wipe.. download it extact it and put "full wipe 1.3" in ur sd card.. and put a rom there too.. then boot into recovery.. 1st do a full wipe.. then flash the rom.. see if that solves ur problem doode..
Edit : aaa crap.. i forgot u cant go into bootloader.. :|
Edit 2 : the guy 2 posts above said that u can use ur home key to navigate thro recovery... maybe u could use it for booting it to boot loader too.. donno lemme try if that can happen
Edit 3 : no that didnt work... btw abt 6 months back... on my samsung galaxy s... volume keys wudnt work so i couldnt get into recovery to get make to stock rom because i was using custom roms... i cudnt do anything and i was still under warrantly. so i perposly bricked ma phone to the extent that no matter wat u do with it, it wudnt switch on.. and i was sent a new one
If you are trying to get into bootloader another way worked for me but maybe not every. Body is to flash a new splash with android flasher then pull cable at correct moment when it boots into fastboot briefly. He'll it works for me LOL
biggy81168 said:
If you are trying to get into bootloader another way worked for me but maybe not every. Body is to flash a new splash with android flasher then pull cable at correct moment when it boots into fastboot briefly. He'll it works for me LOL
Click to expand...
Click to collapse
thanks for letting me knw man... i cud use that if nothing else is possible lol
my down volume key does not work either, and i have had difficulty with this.
i have just tried to install a theme, and reboot and it was stuck on white htc screen.
plugged phone into computer, use adb reboot bootloader and load up recovery from there..
I flashed a full wipe zip by mistake and with no volume buttons i thought i was screwed but after two days trying i found i could only go back to stock 132 every thing else would fail?
For anyone who is in this predicament, if you can't or are unwilling to use adb, then if you download and install Droid Explorer, there is the option to boot into bootloader, flash other ROMs and loads more besides.
Nope... u just need. To. Root and eng s off and s off again...then ur back in business
Sent from my Desire HD using XDA Premium App
like someone said before, you can access the phone with adb and forget about touching the controls on the actual phone, it can go into bootloader, and from there i guess you can reflash or recover your stock rom
adb is more simple than it sounds, it's just sort of like remote control via the computer
I've tried adb fastboot as suggested but all it says is <waiting for device>. I've tried plugging device in and turning it on both before and after entering this command but the phone just immediately goes to the white HTC screen. Also tried Droid Explorer as suggested but I can't even get that to install as it throws up an error message during install!! I'm not having a good time with this phone at the moment lol
If you downloaded the PD98IMG.zip from the downgrade thread, and download Quick Boot from the market.
Put the zip on your SDcard and use Quick Boot to get to the bootloader. From there is should be an automated process, and your phone will be restored to HTC stock.
I'm unable to get into the market to download anything since the phone doesn't boot
Ok I'm back in business. Just managed to flash a clean rom. Some nice chappy on another thread was also having the exact same problems as me and he managed to sort it out and helped me. The commands are ADB REBOOT RECOVERY or ADB REBOOT-BOOTLOADER. I was typing FASTBOOT REBOOT-BOOTLOADER as mentioned in an earlier post and wasn't getting anywhere.
However I'd like to thank you all for your efforts and now I should be able to return the phone to stock and get it shipped off for repair with peace of mind that they won't whinge that the warranty is null and void.
Leather|Face said:
Edit 3 : no that didnt work... btw abt 6 months back... on my samsung galaxy s... volume keys wudnt work so i couldnt get into recovery to get make to stock rom because i was using custom roms... i cudnt do anything and i was still under warrantly. so i perposly bricked ma phone to the extent that no matter wat u do with it, it wudnt switch on.. and i was sent a new one
Click to expand...
Click to collapse
Luckly you didnt do above method..lol
Sent from my Desire HD using XDA App
naimmkassim said:
Luckly you didnt do above method..lol
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
ROFLMAO !
Followed these instuctions:
http://nexusshacks.com/nexus-s-hacks/how-to-root-nexus-s/
My phone is now stuck at the google logo and will not go past. After rooting and clockwork i was not able to load anything else but i would not boot.
Please help.. Thank You
seriously? there is like 4 threads on how to root it, and you go with one that you shouldnt.. lol
it had pictures.. lol
all the threads on here talk about specific phone models and i wasnt sure so i just went with it... Bad choice on my part..
hopefully someone can help
load up fastboot and try to get to recovery if you can then awesome.. try wiping everything and see if that fixes anything
Pull the battery, hold volume up and power and follow this post to get into recovery. Then like shabby penguin said, when you get into recovery wipe everything and you should be good to go. Again, the post I linked you to is the proper way to root the 4g...
http://forum.xda-developers.com/showpost.php?p=13570498&postcount=5
i can get into recovery and i wiped the phone, but still doesnt help.
opie2l said:
i can get into recovery and i wiped the phone, but still doesnt help.
Click to expand...
Click to collapse
Oh, guess I didnt catch that.
ok your best bet it to go into fastboot and flash the clockworkmod 3.0.2.4
did you do the oem unlock command?
yeah i did the oem unlock.
ok well assuming you followed the directions from this guy, then you have a diff bootimg on there i can toss a few files that may fix it, but no garuntees...
seriously tho
(You should see that “LOCK STATE” says “UNLOCKED”, meaning your Nexus S is rooted.)
Click to expand...
Click to collapse
is posted on his site.. that would be a good indicator to me to stop listening to anything he said.. he then later in the comments was trying to help someone and told them if usb wasnt working then use a microsd adapter to put the files on..
yeah i am kicking my self in the a$$. Is there anyway do just get it back to stock?
well have you tried flashing a kernel? if it gets to bootani then its usually rom erros, freezing at spalsh screens is generally kernel images
is it possible to load a kernel when i cant see the phones memory from the computer???
someone has to have some idea of to fix this...
just got me to stock unrooted phone.. please
yes, download this
boot into fastboot and type in fastboot flash boot /path/to/natarchy.img
replace /path/to with where its located.. this should get you rollin again
thank you... thank you... thank you!!!!!!!!
i have learned my lesson and i wont stray from the xda forum next time.
Again thank you
I have a similiar issue as OP...I tried to flash netarchy kernel with kernal manager and then phone rebooted and got stuck at google logo.
I have installed SDK...google drivers, but when I try to flash the kernel I get waiting for device in command prompt. Same error when I type "fastboot oem unlock"
Any ideas?
Skillz1318 said:
I have a similiar issue as OP...I tried to flash netarchy kernel with kernal manager and then phone rebooted and got stuck at google logo.
I have installed SDK...google drivers, but when I try to flash the kernel I get waiting for device in command prompt. Same error when I type "fastboot oem unlock"
Any ideas?
Click to expand...
Click to collapse
Waiting for device means Windows does not recognize phone. Reinstall drivers.
ok sounds like a driver issue, i used pdanet to install the drivers i needed. try fastboot devices, if it doesnt show anything then your phone isnt connected
Ok used my mac and was able to get cwm recovery on device. I could mount it. Now how can I flash back to stock. I9020A att 3G version. Booting now I see google and a lock.
Thanks everyone!
Hello All,
I have run into a problem with my Heroc not wanting to boot. Some background:
ROM: CM7
Kernal: Jaybob's recent Kernal
Mods: Firerats
All was fine and dandy until yesterday, when I decided to reboot the phone (with a full battery charge). The phone shutoff and when restarted was stuck at the HTC screen. I've tried several times to get into recovery but it hangs at the HTC Screen.
I can enter Fastboot/Hboot. I did some digging and tried to unroot by using this method: http://forum.xda-developers.com/showthread.php?t=988741
Method 1, loading the imaging on the sd root and loading. Everything loaded fine but when I reboot it still hangs at the HTC screen. I have not tried to RUU being that I am on a Mac and don't have access to a PC at the moment. So RUU will be done later tonight hopefully, but I don't expect different results.
It seems like I have some messed up memory and its not allowing me to boot. Does anyone know of a fix? I'm not desperate because its time for an upgrade. I just wanted to hold off on using it until January when Sprint holds their press conference, assuming its an Android device. I'd like to see what I could get versus the phones on the market now.
Any help is appreciated, thanks in advance
srkmagnus said:
Hello All,
I have run into a problem with my Heroc not wanting to boot. Some background:
ROM: CM7
Kernal: Jaybob's recent Kernal
Mods: Firerats
All was fine and dandy until yesterday, when I decided to reboot the phone (with a full battery charge). The phone shutoff and when restarted was stuck at the HTC screen. I've tried several times to get into recovery but it hangs at the HTC Screen.
I can enter Fastboot/Hboot. I did some digging and tried to unroot by using this method: http://forum.xda-developers.com/showthread.php?t=988741
Method 1, loading the imaging on the sd root and loading. Everything loaded fine but when I reboot it still hangs at the HTC screen. I have not tried to RUU being that I am on a Mac and don't have access to a PC at the moment. So RUU will be done later tonight hopefully, but I don't expect different results.
It seems like I have some messed up memory and its not allowing me to boot. Does anyone know of a fix? I'm not desperate because its time for an upgrade. I just wanted to hold off on using it until January when Sprint holds their press conference, assuming its an Android device. I'd like to see what I could get versus the phones on the market now.
Any help is appreciated, thanks in advance
Click to expand...
Click to collapse
You definitely need to do an RUU. No way around it. know it sucks starting fresh again but it'll solve all these problems you have. If your s-off you can also do the RUU from Hboot but it's better to do it from PC as I have learned. Good luck man.
thanks a lot! om going to give it a try later tonight when i have access to a pc. Im not so much worried about starting fresh than I am losing the phone and using my upgrade now... I have a curve laying around and started to thing about using that for a while until I see something I like.
i will report back tonight or tomorrow when i am up and running again.
I had the same problem awhile back and it took me forever to get it fixed but I finally got it fixed. Search the forum for " stuck at HTC screen and look for the threads I started for as possible fix. I will try to find it and post the link here.
http://forum.xda-developers.com/showthread.php?t=1305479&page=3
My last post describes how I finally fixed my Hero, but you should read the whole thread.
williams1978 said:
I had the same problem awhile back and it took me forever to get it fixed but I finally got it fixed. Search the forum for " stuck at HTC screen and look for the threads I started for as possible fix. I will try to find it and post the link here.
http://forum.xda-developers.com/showthread.php?t=1305479&page=3
My last post describes how I finally fixed my Hero, but you should read the whole thread.
Click to expand...
Click to collapse
Thanks. I will give it a look.
I read through the thread and it looks like you passed the black htc screen and got to the white one. I can't get passed the black and adb doesn't pick up the phone at this point. I'm still waiting to try the RUU and see if HTC sync picks up the device.
Very resourceful thread and I'll be sure to give all the suggestions a try before giving up.
HTC sync won't pick up the device and I don't think any other option will work since I don't have ADB access. I'm just gonna bite the bullet and look into a replacement.
Ok to verify your phone does boot at least to the bootloader? If so I have a doffeemr approach for you to take
私のEVO 3Dから送信される。
dastin1015 said:
Ok to verify your phone does boot at least to the bootloader? If so I have a doffeemr approach for you to take
私のEVO 3Dから送信される。
Click to expand...
Click to collapse
yeah. I can get into bootloader and fastboot. whatcha got?
I have a new phone on the way. Amazon has ET4G for $79, too good to pass up so I used my upgrade. Ill still be curious to know how I can get the Hero up and running.
srkmagnus said:
yeah. I can get into bootloader and fastboot. whatcha got?
I have a new phone on the way. Amazon has ET4G for $79, too good to pass up so I used my upgrade. Ill still be curious to know how I can get the Hero up and running.
Click to expand...
Click to collapse
Follow these instructions: http://forum.xda-developers.com/showthread.php?t=804692
I used a flashable RUU based off Flipz source and still no luck. I will give your RUU a try later tonight... Thanks
No luck. The phone freezes at the HTC screen and fails to go any further. :-(
srkmagnus said:
No luck. The phone freezes at the HTC screen and fails to go any further. :-(
Click to expand...
Click to collapse
i had same kinda deal from a bad radio flash
if you still have fastboot do
"fastboot erase system -w"
"fastboot oem boot heroc.hboot-1.46.2000.zip"
you may need to rename the file to HBOOT.
if that dose not work unzip the file take the hboot img and place on sdcard and place where your fastboot files are like in android/platform-tools.
this made a deference for me.
then try fastboot flash img hboot.img
this is what i went through here
http://forum.xda-developers.com/showthread.php?t=1086125
good luck if i can help let me know.
Thanks for the help oostah. I haven't been able to get ADB to recognize the device. When I get home I'll try it again and remove the hboot as suggested and give that a try.
Now that ICS is in beta for the Heroc my phone decides to crap out on me and I can't enjoy the hard work put in by the developers. Nonetheless, I am much appreciative of all the support put into the Heroc and have learned a lot from this community
I'll report back tonight with my results.
srkmagnus said:
Thanks for the help oostah. I haven't been able to get ADB to recognize the device. When I get home I'll try it again and remove the hboot as suggested and give that a try.
Now that ICS is in beta for the Heroc my phone decides to crap out on me and I can't enjoy the hard work put in by the developers. Nonetheless, I am much appreciative of all the support put into the Heroc and have learned a lot from this community
I'll report back tonight with my results.
Click to expand...
Click to collapse
you are welcome i have been there before.
your phone may not recognize ADB but it may still take fastboot commands. that was one thing that drove me crazy is that i could fastboot but not adb. let us all know how it goes.
I did "fastboot-mac devices" and got my device to show up, so it registered. however, when I go to erase system I get an error, "remote: not allowed". The same occurred when trying to flash the .zip and img files separately as suggested . At one point the devices started vibrating like crazy and shut off, the led started to blink green. I did get it back into Fastboot, but now it won't turn on.
Thanks for the help though It was already replaced and the new phone should be here tomorrow. I'm just going to miss the Hero since it was my first Android device and I learned a lot in this forum.
Thanks!
srkmagnus said:
I did "fastboot-mac devices" and got my device to show up, so it registered. however, when I go to erase system I get an error, "remote: not allowed". The same occurred when trying to flash the .zip and img files separately as suggested . At one point the devices started vibrating like crazy and shut off, the led started to blink green. I did get it back into Fastboot, but now it won't turn on.
Thanks for the help though It was already replaced and the new phone should be here tomorrow. I'm just going to miss the Hero since it was my first Android device and I learned a lot in this forum.
Thanks!
Click to expand...
Click to collapse
i still have one of my hero's that i let people play with when the come over. it still runs off wifi so they can play games yous gtalk what ever be nice to get it up and running for experience and fun lol now that your not in a have to mode.
do you have a nan back up from a sd card any place like on your pc if so look for your clockworkmod folder look for backups and you should see your backups open one of them you will see
boot
system
data
recovery
sd-ext
cache
they will be img files you can place them on your sd card and fastboot them back to the phone
"fastboot flash img boot.img"
"fastboot flash img system.img"
and so on
or
"fastboot boot img boot.img"
"fastboot boot img system.img"
and so on
or you can let it RIP
good to know. I'll give that a try if I can get it booted. I'm thinking its dead and needs a charge to get back into fastboot. I'd love to get it back up and running as a learning experience more than anything. I wont have time until tomorrow or Thursday . I will report back when I give it a try.
srkmagnus said:
good to know. I'll give that a try if I can get it booted. I'm thinking its dead and needs a charge to get back into fastboot. I'd love to get it back up and running as a learning experience more than anything. I wont have time until tomorrow or Thursday . I will report back when I give it a try.
Click to expand...
Click to collapse
will the charge light come on when plugged in if not there is a trick take a old usb cable cut one end off on the battery there are
= and - becare full connect the red wire to + and black to - tap them down so they dont move. let it set for 2 1/2 hrs should be good to go.
I flashed the Eclipse ROM via safestrap and then restored the Eclipse ROM onto the stock ROM slot. For some stupid reason, instead of restoring the stock ROM slot before resetting the phone back to stock, I opted to use RSD Lite 6.1.4 and tried to flash the JB firmware (yes, I got into fastboot). When I tried to do this, the phone reboots past the Motorola M insignia, to the droid startup screen (with the flashing red light/circle), but does not get past the startup screen (yes, I gave it 30+ minutes to no avail). I also tried to reflash the JB firmware, but no matter what, I ended up stuck at the bootup screen.
For this reason, I tried to flash the ICS firmware instead (per instructions on XDA and other websites, I removed the lines in the XML file that had the word var, getvar, and oem). This did work! However, after RSD flashed the firmware, rather than restarting into the OS, the phone reboots into a black screen w/ the phrase "Fastboot Reason: Sticky bit factory_fastboot" at the very bottom. Anytime I try to restart the phone, it automatically boots into this screen. If I hold the volume up and down buttons, together w/ the power button, I am able to get back to the option to start normally.
When I tried to do the OTA JB update, the phone downloads the necessary files, but when the phone tries to reboot to install the OS update, it goes back into that black screen and does not install the update. Also, when I finally do get back into the OS, the phone then constantly reboots as if it were trying to install the OTA JB update.
Does anyone know what "Fastboot Reason: Sticky bit factory_fastboot" means? Also, if anyone knows how to "fix" this issue, I'd greatly appreciate it. If the fix requires command line work (like in this thread), I'd greatly appreciate if someone could walk me through it step-by-step, as I am not familiar w/ the command line process.
Thanks!
Edit 1: The next step I will try is to get root back on my phone, install Safestrap, and see whether I can flash a backup that I previously had.
Edit 2: In some threads for other Moto phones, there is some discussion regarding using ADB to fastboot/flash the stock ROM. Anyone know how this is different from using RSD? Also, can anyone walk me through HOW to ADB? I have zero knowledge in this regard.
Have you tried holding the buttons down to enter fast boot again and reflash? Worth a shot if you haven't. You could also attempt a factory reset from the boot menu. Maybe the corrupt file would correct itself.
You should definitely take the time to learn some ADB; at least a working understanding. It helps down the road.
Here's a good tutorial on ADB commands. http://mobile.tutsplus.com/tutorials/android/android-adb-quick-guide/
And to install ADB without Android SDK (app production software) http://mobilecon.info/install-adb-in-windows.html
Sent from my Nexus 7 using xda app-developers app
skippid said:
Have you tried holding the buttons down to enter fast boot again and reflash? Worth a shot if you haven't. You could also attempt a factory reset from the boot menu. Maybe the corrupt file would correct itself.
You should definitely take the time to learn some ADB; at least a working understanding. It helps down the road.
Here's a good tutorial on ADB commands. http://mobile.tutsplus.com/tutorials/android/android-adb-quick-guide/
And to install ADB without Android SDK (app production software) http://mobilecon.info/install-adb-in-windows.html
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Yes, I attempted to reflash on multiple occasions, both using the stock ICS and the stock JB roms. I must have reflashed close to 10x at this point. In any case, no matter how often I have reflahsed (including after doing a factory reset from within the OS as well as from within recovery), I still get the error. The good news is that I was successfully able to flash the JB ROM and have the phone OS actually start up, whereas, a few days ago, it would be stuck at the red circle/eye thing.
Furthermore, I attempted the command fastboot flash system [system.img], and I got the error:
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
error: cannot load '[system.img]': no error
I saved the system.img in both c:\android, as well as the internal SD card of the phone.
The other good news is that I am still able to use the phone if I get into the boot menu and ask the phone to boot normally. However, I am now unable to get root, and anytime I need to restart the phone, it gives me that error message.
I have also tried the command fastboot reboot bootloader but continue to get the same error message.
OK. Find a JB leak zip or current stock JB zip, access the screen where it asks for AP Fast boot and recovery, choose recovery, then volume up I believe when the phone shows the android with the red exclamation point.. Then choose update with zip. Search your SD card and install. It's worth a try in this manner in case you haven't already.
That's odd that your phone didn't respond well with RSD.
Sent from my XT907 using xda app-developers app
You need to use an updated fastboot binary for the new larger images in these devices.
http://db.tt/AveMC40y
skippid said:
OK. Find a JB leak zip or current stock JB zip, access the screen where it asks for AP Fast boot and recovery, choose recovery, then volume up I believe when the phone shows the android with the red exclamation point.. Then choose update with zip. Search your SD card and install. It's worth a try in this manner in case you haven't already.
That's odd that your phone didn't respond well with RSD.
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
Skippid, thanks for the suggestions. I tried your method as well. Went into recovery, selected to update from external SD (or something to that effect), selected the JB zip file, and let it flash that way. Unfortunately, I still received the same error message regarding the sticky bit factory_fastboot.
cellzealot said:
You need to use an updated fastboot binary for the new larger images in these devices.
http://db.tt/AveMC40y
Click to expand...
Click to collapse
cellzealot, thank you for the link. I've downloaded the file that you linked to. Could you be so kind as to now give me a step-by-step on how to re-attempt the flashing process?
Quick update - I was able to get root back, installed safestrap, and flashed the nandroid that I had made back when I first flashed Eclipse. However, I am still having the same issue:
Whenever I restart the phone, I get the sticky bit factory_fastboot error. If I use the command fastboot continue, the phone boots up as normal; however, it would be great to not have to do this each and every time I reboot the phone. Any help would be greatly appreciated. Thanks!
More updates (still not fixed):
After getting root, I reflashed my nandroid, factory reset (both within the OS and in recovery), and then tried flashing both the ICS and JB stock ROMs. I tried flashing both using mfastboot, as well RSD Lite. The files flash successfully; however, whenever I restart the phone, I continue to get the stick bit factory_fastboot error.
Also, when I get into recovery, I try to flash via "update from external SD". When I do so, recovery simply restarts without flashing the stock ROM.
Here's my last update as to this issue:
After trying all of the methods that I could think of (RSD Lite, flashing via fastboot and mfastboot, flashing from external), the problem did not correct itself.
I brought my phone into a Verizon store, where they told me that they had never seen that problem before. They agreed to replace my phone pursuant to the one-year warranty (I received my phone in December), which I received today. I've again rooted my phone, but have opted to not screw around w/ safestrap and custom ROMs this time around, as I find the stock JB experience to actually be quite good.
Found the soultion!!!!!!
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful
Thank you!
cerafio said:
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful
Click to expand...
Click to collapse
Thank you! This was the answer I needed after searching and searching trying all the different things for over 3 hours, this 2 second fix worked!
Namanati said:
Thank you! This was the answer I needed after searching and searching trying all the different things for over 3 hours, this 2 second fix worked!
Click to expand...
Click to collapse
#8 > http://forum.xda-developers.com/droid-razr-m/general/guide-faq-how-to-root-boot-unlock-t2869432
ATTACK said:
#8 > http://forum.xda-developers.com/droid-razr-m/general/guide-faq-how-to-root-boot-unlock-t2869432
Click to expand...
Click to collapse
Thanks, but that didn't come up when I googled AP Fastboot: flash failed, and since I didn't get it from rooting or unlocking my phone I didn't think to look for that.
cerafio said:
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful
Click to expand...
Click to collapse
Oh my god dude thank you so much. That fixed my bootloader issue that was plaguing me for weeks
Thanks again!!!
cerafio said:
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful
Click to expand...
Click to collapse
Thanks Man You really saved my razr.:good:
Edit : Sorry I asked stupid question!
Pierro29 said:
Edit : Sorry I asked stupid question!
Click to expand...
Click to collapse
there are no stupid questions if you question its because you dont know something and would like to fulfill the empty space where a reasonable answer could go. and s thanks for the solution to this error.
Okay, I have a "stupid"/newbie question. I flashed an image and I am getting the sticky boot thing. How to a get to a window to type the lines in?
Thanks!
cerafio said:
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful
Click to expand...
Click to collapse
Hey dude ! You save my life
Awesome trick