Related
I had my phone rooted and working fine on CM5 but I had the CM/JF recovery.
I wanted to update to a new recovery so I downloaded Clockworkmod's ROM Manager. I flashed the recovery and rebooted into recovery. The phone will hang on the G1 screen if I try to go into recovery, but if I let it boot normally it will go into android.
How can I fix this?
If you have a SPL that allows FASTBOOT, you can FASTBOOT, connect to the PC, and flash the recovery image from there.
Everthing I read about fastboot is done over linux, is there a way to get it running in Windows?
Has nothing to do with linux. Is multiplatform.
http://forum.xda-developers.com/showthread.php?t=532719
Windows 7 is being a pain in the ass and not letting me install the USB drivers. I don't know what to do
Use google.
It has been asked already. I had Windows 7, and it worked.
The only thing I find is how to get the Hero to sync with W7. Should i follow those steps anyway?
I cant post links but I used a method on theunlockr
And Winblows 7 is still telling me it is unable to install my device.
.....
It is the same.
just go to amon ra's thread on his 1.7.0 version and there is instructions on how to flash his recovery from terminal on the phone its really simple that way
In his thread it says not to flash it from within CM5 :\
That's probably what happened in the first place, i flashed a recovery from within CM5 and this caused my problem.
EDIT: Tried it anyway and it didn't work.
EDIT EDIT: After messing with the HTC sync drivers I was able to install them and my computer reads my phone when I do 'fastboot devices'. However I have to go to school so I will have to flash the recovery after work. I hope this works
I was able to successfully flash the recovery with Fastboot. Thanks for the help
First some history with my G1:
I used the normal unrooted G1 for about a ear after i decided to root it. I rooted it succesfully to 5.something (old, because there wasnt ADW launcher yet). Soon after i wanted to go 2.2 or cyanogen 6.0.3. That too was a succes, but after short use it turned out quite slow. I did some research and found out that 5.0.8 is the way to go for a fast G1 phone ith use of apps. Short install but a few trial and errors (lots of factory resets etc.) i got it running smooth. I installed all my apps once again and thought to myself "i should do a Nandroid back-up before i have to wipe it all again...". So i remembered ROM Manager from 6.0.3 and installed it from market. I did a backup via there, but as i clicked i saw a message for a milisecond. It seemed like an error message, but after a split second my phone just rebooted.... Only this time it got stuck at the G1 boot logo....
After getting familiar with Cyanogen this was very new to me. I tried going into recovery obviousley, but that didnt boot. Only thing that did boot was Fast Boot. No idea what i can do there so i didnt touch it.
More research came i decided that i phone maybe bricked... I found out that you can try Terminal or something in fast boot to reflash something... This still isnt clear to me, and i was wondering if there is any guide that i couldnt find that gives me a noobie guide on how to use terminal on your computer to flash something on your phone?
Thanks very much in advanced!
Summary of things i use/did:
Computer: Macbook 1.0.6 OSX
Phone: G1 rooted to 5.0.8 Cyanogen (stable)
Possible cause: Using ROM Manager to make a Nandroid backup
Uh, did you remove the back cover and remove/replace the battery?
Glycerin50 said:
First some history with my G1:
I used the normal unrooted G1 for about a ear after i decided to root it. I rooted it succesfully to 5.something (old, because there wasnt ADW launcher yet). Soon after i wanted to go 2.2 or cyanogen 6.0.3. That too was a succes, but after short use it turned out quite slow. I did some research and found out that 5.0.8 is the way to go for a fast G1 phone ith use of apps. Short install but a few trial and errors (lots of factory resets etc.) i got it running smooth. I installed all my apps once again and thought to myself "i should do a Nandroid back-up before i have to wipe it all again...". So i remembered ROM Manager from 6.0.3 and installed it from market. I did a backup via there, but as i clicked i saw a message for a milisecond. It seemed like an error message, but after a split second my phone just rebooted.... Only this time it got stuck at the G1 boot logo....
After getting familiar with Cyanogen this was very new to me. I tried going into recovery obviousley, but that didnt boot. Only thing that did boot was Fast Boot. No idea what i can do there so i didnt touch it.
More research came i decided that i phone maybe bricked... I found out that you can try Terminal or something in fast boot to reflash something... This still isnt clear to me, and i was wondering if there is any guide that i couldnt find that gives me a noobie guide on how to use terminal on your computer to flash something on your phone?
Thanks very much in advanced!
Summary of things i use/did:
Computer: Macbook 1.0.6 OSX
Phone: G1 rooted to 5.0.8 Cyanogen (stable)
Possible cause: Using ROM Manager to make a Nandroid backup
Click to expand...
Click to collapse
Rom manager has a habit of breaking recoveries. If you can get into fastboot you can flash a new recovery from there. If you have an engineering spl that is. Need your info from fastboot. Do you have danger spl? Amonra has guides on how to flash from fastboot. Get his 1.7.0 and fastboot flash it. You dont sound bricked.
http://forum.xda-developers.com/showpost.php?p=4647751&postcount=1
Ok been a while ,sorry! I am still "bricked" (or at least i think i am). Yes i have taken out the battery and putting it back in.
@Johnson: Yes so i have read! A little to late, My info from fastboot:
DREAM PVT 32B ENG S-OFF
HBOOT-1.33.2005 (DREA11000)
CPLD-4
RADIO-2.22.19.26I
Apr 20 2009, 15:30:43
I'll go to that tutorial ,see if i can figure it out. Thanks for the help!
EDIT: So, ive read it... But its not clear to me. Do i need to open a terminal like program on my mac and just type in:
fastboot devices (to make sure that fastboot "sees" your device)
fastboot flash recovery recovery-RA-dream-v1.7.0.img
Or do i need to connect with my phone somehow (besides USB)
Yes, boot in to the SPl (you might need to enable fastboot in there, just poke stuff), then fire up Terminal.app, cd to the /tools directory where the SDK is installed, then issue the commands.
I havent heard of SPL boot yet, how do i do this? Or is this Camer+power on/off?
Also the part about Terminal.app is total abracadabra to mee, haha. ill try and figure it out using the tutorial and maybe some common sense. If i did figure it out, i'll let you guys know!
Otherwise, if u read this and feel like helping... Much appreciated! I can use all the help you can offer!
Thanks!
Tobias
Boot to fastboot mode. Should tell u how on amonra's page. Put recovery in tools folder of your sdk. Then open command prompt on PC and type: fastboot devices hit enter. Should get a serial number. CD to tools folder and type fastboot flash image command in thread
Sent from my HTC Magic SparksMod using XDA App
Glycerin50 said:
I havent heard of SPL boot yet, how do i do this? Or is this Camer+power on/off?
Also the part about Terminal.app is total abracadabra to mee, haha. ill try and figure it out using the tutorial and maybe some common sense. If i did figure it out, i'll let you guys know!
Otherwise, if u read this and feel like helping... Much appreciated! I can use all the help you can offer!
Thanks!
Tobias
Click to expand...
Click to collapse
Yes, the SPL is the bootloader (camera+power). To open the terminal, got to Applications > Utilities > Terminal.
ok, this is getting more and more understandable to me
Just where is this tools SDK folder. Will this apear on my pc when i plug my phone while i bootloader? or do i need to download some more stuff for this all to work on my pc...
U will need to look up how to install sdk on your computer. Its another program u need to control your phone with the PC. Called adb. Android debugging bridge
Sent from my HTC Magic SparksMod using XDA App
I don't think that fastboot comes with the SDK. There is fastboot-mac zip file somewhere out there... I can't remember where I got mine from, but there is one here http://developer.htc.com/adp.html
Put the file somewhere on your mac and use the terminal program in your applications/utilites folder to access it. You should be a little familiar with Linux to use it If you want to get fancy, put it in /usr/sbin or somewhere in your $path.
The SDK kit is good too, especially adb.
EDIT:
Here are a few good threads to get you headed down the path to flash-a-rama. Most of the commands are the same, regardless of platform, but the installation procedure will vary, i.e., fastboot erase system -w does the same thing on any platform.
http://forum.xda-developers.com/showthread.php?t=517874
http://forum.xda-developers.com/showthread.php?t=532719
Lastly this thread should be required reading... http://forum.xda-developers.com/showthread.php?t=655097
SUCCES! YEAH!!! Thank you guys so much! While reading your posts and all the guides i decided to get into bootcamp (windows on mac) and do it all there.
It was way easy to install and ive setup adb and SDK easy and used fastboot to flash Amon Ra's recovery!
It installed within seconds and from recovery i did a fresh wipe and installed my 5.0.8 cyanogen.
Right now it booting up for the first time as i typ and i think its going to boot.... Yes, it takes a long time the first time.
Yes, it works!
Thank you guys again!
Tobias
Tried to install Cyanogen 6.1... It failed.
From there the device booted up normally on a fresh start, but I tried to recover my backup and that is where everything got all messed up.
Im stuck on the G1 screen.
Ive gotten it to the fastboot mode and Im downloading what I think I need to get my phone working again. Ive downloaded the Andriod 1.6 image from the HTC website. Do I need the recovery? I just want 1.6 until I have time to try and get Cyanogen installed.
Im currently installing JDK for the Andriod SDK.
Am I headed in the right direction?
I was using ROM Manager with Clockwork Mod. My old ROM was Super E... Not sure what version, but it was Andriod 2.1
What radio/spl do u have?
johnson8cyl said:
What radio/spl do u have?
Click to expand...
Click to collapse
2.22.19.26I
Tbry said:
2.22.19.26I
Click to expand...
Click to collapse
And spl? Do u have and eng spl? (S-off). If so u could fastboot erase your system and try to flash the rom through recovery. And fastboot flash a recovery of your choice first. Have u tried going on ezterry's thread with the new radio/spl and going that route?
Not sure what the version of the SPL is, but I know it is off. I'll check his thread out and give it a try. I might end up finding someone who actually knows what they are doing, or buying the Nexus S.
Ok. If u follow his thread exactly and fastboot flash the radio/recovery/spl u should end up with everything as described in the thread and be able to move on with cm6 with appropriate kernel. Alternatively u could boot into fastboot and open up your terminal on your computer and type in code to fastboot recovery of your choice (after it's download and put in sdk/tools folder on your PC) he has amonra link in his thread for download . Then type fastboot erase system -w (hit enter). When it's done type fastboot erase boot (hit enter). Then power down. Power back into recovery with the rom on your sdcard and flash away.
That is actually what I'm trying to do. Its just about my only option at this point.
Im having problems getting everything set up correctly though.
What are u having problems setting up?
I installed Andriod SDK, seems to be working.
Downloaded the drivers, which seems to have stopped my computer from seeing the phone.
I downloaded the Fastboot.exe, tried to run it but it cannot find ADB.dll ( Pretty sure thats what it was.)
I was basically following the steps on the cyanogen wiki.
When I have some time, I will try the Fastboot for noobs guide.
I think I followed a guide in androiddevelopers.com or something like that. If I find it again ill post a link. I don't think I ran a fastboot exe file though. Just have it in my androidsdk/tools folder. Added the variable to my paths and was good to go. Not at my PC currently though.
Edit: developer.android.com/sdk/
I believe is what I followed
http://forum.xda-developers.com/showthread.php?t=532719
Following this for fastboot.
I cannot update anything. Home + power doesnt do anything.
Only thing I can access is fastboot mode.
Fortunately my radio is up to date, so I assume my SPL is as well.
Going to attempt to try the fastboot step, once I can get the SDK working correctly
edit: I knew if I spent enough time working at it that I'd get it working.
Only problem now is getting my device to be listed.
Edit2: at first when I entered fastboot mode, I would get the "Add new hardware" for the device "Andriod 1.0"
It now says "andriod bootloader interface"
I feel like I'm so close. I'm going to keep playing with it, but what can I do to get my device listed when I type the command "Fastboot devices"?
Edit 3: Awesome. I got fastboot to work and my phone is recognized. Only problem now is getting my SD card reader to work so I can put the proper files on
Final edit: MY phone is killing SD cards for some reason. Don't know what to do
Got the SD cards to work, for some reason though, some of the commands are not working. When I type fastboot shell, I just get the usage doc.
When I do fastboot update, I get the following: error: failed to load 'update.zip'
What are u trying to do in fastboot?
Sent from my T-Mobile myTouch 3G using XDA App
Well, I fixed my phone. Back to its original state.
I guess my only question at this point my only question is if I switch to Cyanogen 6.1, will it be less buggy than my Super E ROM?
For anyone wondering, Holding home + end for about 25 seconds is what I did. From there I just went to nandriod and tried to recover the same backup that gave me the problem.
I would say no. It will not be less buggy. U can always flash and try different roms though for experiment sake. Glad u got it back up
Sent from my T-Mobile myTouch 3G using XDA App
I have been searching all afternoon, here is my problem. I had issues with some radio and SPL files last night (won't verify), and someone pointed me to a newer version but they are *.img files...I've never loaded anything but the recovery partition as an image file.
I looked this up and it says it needs "fastboot"
90% of the searches tell you how to install the SDK (even though fastboot is in the title, it's never mentioned in the body of the post), thanks, I have the SDK since I got my phone, but I don't have or see fastboot anywhere in it.
So my newbie question is how do I fastboot the *.img files onto my G1, since I don't see fastboot on SDK or on my phone?
Second newbie question, when I see the directions for installing they list the fastboot commands serially...so do I have to reboot after each img load or can I just load one then the next without rebooting/power cycle?
Thanks.
GolfnWrx said:
I have been searching all afternoon, here is my problem. I had issues with some radio and SPL files last night (won't verify), and someone pointed me to a newer version but they are *.img files...I've never loaded anything but the recovery partition as an image file.
I looked this up and it says it needs "fastboot"
90% of the searches tell you how to install the SDK (even though fastboot is in the title, it's never mentioned in the body of the post), thanks, I have the SDK since I got my phone, but I don't have or see fastboot anywhere in it.
So my newbie question is how do I fastboot the *.img files onto my G1, since I don't see fastboot on SDK or on my phone?
Second newbie question, when I see the directions for installing they list the fastboot commands serially...so do I have to reboot after each img load or can I just load one then the next without rebooting/power cycle?
Thanks.
Click to expand...
Click to collapse
1.turn off the phone . open fastboot on the phone by holding back and power.
2.open up command prompt with admin priveliges. use the command "cd" for main android sdk directory, wherever you have it.
3. once found the directory, for me its X:/AndroidSDK/ , refer to the tools by adding the /tools like so: X:/AndroidSDK/tools
.
4. enable fastboot devices by typing the command fastboot devices
5. use the command fastboot flash *****.img.
if you are flahing new radio and hboot's. PLEASE flash the radio first!!!! and with the second question, you can flash the next img right after, just make sure you do the correct ones first.
I'm still missing something here
Back+power = rainbow screen, now I'm stuck because my ADB command fails here, no device detected (it works on normal power up, or even in recovery mode).
So my issue is with item #2, how can I "open up a command prompt" from the rainbow screen? gonna search on that though.
Is this a hack that I missed?
I DO see fastboot in my tools directory.
ooops androids on skateboards are gone
Think I found it....
"...you need to replace your bootloader with an unlocked G1 bootloader that has fastboot enabled..."
So my old build had it, and my new one (1.6 rooted) does not....so need a known good ROM with fastboot enabled.
haha, that only took me all day.
Help please, need a ROM that supports Fastboot
Yes, I'm an idiot...while there is tons of information here, even tutorials and walkthroughs, the amount of time I had to spend searching and reading to find what I wanted is phenomenal. I have been out of it for a while, and it's gotten much worse in many ways and better in some ways too.
What I don't understand is why so many ROM's fail to load still. The tools and processes are much better understood now but many ROM's fail at loading, at least that I tried.
There are also tons of dead links to ROM's, frustrating for someone not familiar with the site.
I want a simple fast ROM, FAST = 3.0 MFLOPS+ on LINPACK, that is reasonably stable...not having much luck so far.
THANKS! for all the help.
So, I have spent the last 4 hours trying to find information and trying to fix things and I have yet to get nowhere.
I tried to install SkyDragon (http://forum.xda-developers.com/showthread.php?t=2400161) on my HTC One. Having gotten an insurance replacement in the last month, I forgot that I hadn't gotten around to getting S-OFF on this replacement device. (I had S-OFF on my old one). Due to this, everything got messed up.
It was trying to boot, went to HTC screen, then tried to reboot to recovery. Clockwork mod would boot, but as soon as any graphics came on the screen, it would reboot back to the HTC screen. This looped.
I managed to flash TWRP on it, but the same thing was happening.
After using fastboot to clear the cache, I got into TWRP. Awesome. Now I just need to get a ROM on this sucker.
adb keeps telling me "adb server is out of date. killing..." In regards to this, I have gone to the Android SDK and installed the latest version. I also tried updating to the latest drivers on my computer as well.
To my understanding, you can't push whole .zip files with fastboot, but I tried to use the "fastboot update rom.zip" command, which won't work due to "archive does not contain 'android-info.txt'" and "archive does not contain 'android-product.txt'".
I tried to go into TWRP and mount the storage, but lo-and-behold it crashes and doesn't mount crap so I can't copy this rom over to flash it with TWRP.
Please. Does anyone have any suggestions? I am not the MOST android savvy, but I have tried everything I could think of. One last resort is I'm gonna try to flash clockwork and see if I can get it to mount. Please help me?
EDIT: Clockwork didn't work, and sideload won't work because "adb server is out of date. killing..."
EDIT 2: I've got an M7_UL with S-ON, HBOOT 1.44.0000. Fastboot works like a charm, adb tries to connect but fails every time.
What is your PC Operating system?
You may wish to try a Linux Live CD.
BenPope said:
What is your PC Operating system?
You may wish to try a Linux Live CD.
Click to expand...
Click to collapse
Both of my PCs are running Windows 7.
Using my roommates computer, I downloaded the Android SDK and I am now able to adb push. Here's to hoping just pushing a ROM and booting into recovery to flash it will work.
starlitjessi said:
Using my roommates computer, I downloaded the Android SDK and I am now able to adb push. Here's to hoping just pushing a ROM and booting into recovery to flash it will work.
Click to expand...
Click to collapse
It works now. I was able to push a stable ROM from my roommate's computer and got it running just fine. Thanks anyway!