Database Develop

[Q] So my phone is bricked...

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

[Q] Fastboot.

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

Custom recovery problem

Hey so I currently have an unlocked bootloader and I try to flash a custom recovery via fastboot yet it hangs on < waiting for device > every time.
I have followed the cyanogen mod wiki step by step. It hangs on clockwork and amon RA. USB debugging is enabled. When I boot into recovery it says fastboot I then connect it to my computer it says fastboot USB.
I'm sure it will be some little setting that's wrong. I am currently running 2.3.4 stock, no root so rom manager is a no go.
I guess what I'm asking is does anyone know what I can do to flash a custom recovery?

Have you tried "fastboot devices" to make sure you have a connection?
What kind of computer are you using (Win/Mac/Linux)?

Fastboot devices gives an empty line the a new terminal line.
Also I'm running win 7.

My initial suggestion would be to update your drivers for fastboot. I have had this happen a couple times and a driver update resolved it for me.
Sent from my Nexus One using XDA Premium App

CapStone said:
Fastboot devices gives an empty line the a new terminal line.
Also I'm running win 7.
Click to expand...
Click to collapse
That means your phone is not connected. Update the drivers, as suggested above...

Much appreciated I will try this when I get home tonight.

Nexus One recovery won't start, stuck on bootloader

Hello,
ok so the problem is I tired to update to Jelly beam, i read about it here and i follow the steps. I make it to recovery and when i wanted to install files from zip it gave me error - Installation Aborted. I read somewhere that i have to update my Clockwork recovery so i tried and since then i can't do anything. When i press the power button i go to bootloader, from there if i chose Recovery the phone reboots and stucks on the colored X. When i type "adb devices" in cmd so i can try to apply some method list of devices is empty. I think it can be fixed if i make it to recovery but i can't. I looked a lot and maybe its because im mad or something but i can't find a solution, so if anyone can help me i will be very happy. I don't bother if im back to stock.

Use fastboot in bootloader, adb is only available in os and recovery
fastboot flash recovery recovery.img
Sent from my Nexus One using xda app-developers app

demkantor said:
Use fastboot in bootloader, adb is only available in os and recovery
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Tried that, stuck on : <waiting for device>
EDIT: I tried on my brother laptop and it worked but when i exucute the command, it says FAILED(remote: image update error)
EDIT2: Thanks i fixed it its working now. WOOHO!

when in bootloader have phone in fastboot mode, connect to pc via usb, make sure you have the proper drivers
HERE, THIS SHOULD HELP this is for a different phone so dont use the files but the concept is the same

[Q] Htc One BRICKED.

After only four day of having this phone i managed to brick it. I would really like to know if its fixable or if i have a really nice paper weight. Im stuck on a boot loop, I was half way through flashing a rom when it suddenly shut off. Now it will not boot up. I can load into the bootlader but when i try to go into recovery it just sends me to fastboot. When i restart the phone i can see the old recovery (TWRP)for just an instant but then the screen goes completely black. If i plug in to my pc, nothing happens my computer detects it but it says y device is damaged nd it cant identify it. PLEASE HELP Am i out of luck?
Ive looked around but i couldnt seem to find anyone with the same problem as me (Sprint Variant)

Good news it's not bricked i would put this question on the rom thread someonethere sshould be able to help

There's a Sprint One forum as well, so hopefully you found a ROM on there!
http://forum.xda-developers.com/forumdisplay.php?f=2215

jaythenut said:
Good news it's not bricked i would put this question on the rom thread someonethere sshould be able to help
Click to expand...
Click to collapse
I really hope so because on a college budget i cant afford another phone D:

Seen this in a couple of other places. Seems certain recoveries are possibly becoming currupted during flashing a new ROM.
What you need to do it get back into fastbboot, and....
fastboot erase recovery
fastboot erase cache
the re-flash your recovery, boot into recovery, full wipe and reflash your ROM.

wnp_79 said:
Seen this in a couple of other places. Seems certain recoveries are possibly becoming currupted during flashing a new ROM.
What you need to do it get back into fastbboot, and....
fastboot erase recovery
fastboot erase cache
the re-flash your recovery, boot into recovery, full wipe and reflash your ROM.
Click to expand...
Click to collapse
When i go back into fastboot my only options are
-Bootloader
-Reboot
-Reboot bootleader
-Power down.
I appriciate the help!

i suggest you contact with HTC customservices to repair this problem.

Muquita said:
When i go back into fastboot my only options are
-Bootloader
-Reboot
-Reboot bootleader
-Power down.
I appriciate the help!
Click to expand...
Click to collapse
Can you flash recovery in fastboot ?
the safest thing to do is relock and use a matching RUU to get back to stock

Muquita said:
When i go back into fastboot my only options are
-Bootloader
-Reboot
-Reboot bootleader
-Power down.
I appriciate the help!
Click to expand...
Click to collapse
Your phone isn't bricked. There are two tools in this forum that can help you. One is made by hasoon2000(I think that's his user name), and the other is jwtool(I think). Use them to help to flash a recovery if you don't know how to use fastboot.

DynamicRam said:
Can you flash recovery in fastboot ?
the safest thing to do is relock and use a matching RUU to get back to stock
Click to expand...
Click to collapse
I cannot. My computer wont recognize it. I re-installed the driver and it Says my device malfunctioned.
Im giving up hope here.

Muquita said:
I cannot. My computer wont recognize it. I re-installed the driver and it Says my device malfunctioned.
Im giving up hope here.
Click to expand...
Click to collapse
dont give up
Sent from my HTC One

Muquita said:
I cannot. My computer wont recognize it. I re-installed the driver and it Says my device malfunctioned.
Im giving up hope here.
Click to expand...
Click to collapse
Edit: Just got done typing the stuff below and saw you can't connect to your device in fastboot? What do you mean by re-installed driver?
Don’t worry, as long as you can still get into hboot your phone is not completely bricked!
The fastboot commands I referred to need to be carried out on your laptop/pc when you phone is connected in fastboot.
Can I assume that as you have already unlocked bootloader and flashed a custom recovery you are already familiar with this and have your computer set up for fastboot commands?
(Apologies if you already know some of this, best not to skip parts out though!)
I’d start with downloading a fresh version of your chosen recovery, and place it in your fastboot directory ready. I’d also do the same with your ROM.
Like you have already done, boot into fastboot. Connect your phone to your pc, and the red text should change to ‘Fastboot USB’.
Then open up command prompt and get to your fastboot directory. (On Windows 7 you just find that folder in Explorer, hold shift and right-click, then choose ‘Open command window here’.)
To check your pc is talking to your phone, type ‘fastboot devices’. You should get a device serial number back if all is well.
Then type ‘fastboot erase cache’ and hit enter.
Then type ‘fastboot erase recovery’ and hit enter.
Then type ‘fastboot flash recovery [name of recovery].img’ and hit enter.
Then type ‘fastboot reboot recovery’ and hit enter.
Hope fully you should successfully boot into recovery now. Once in recovery, mount USB storage and copy over your fresh ROM. Choose to do a full wipe including cache and dalvik, then reflash your ROM.
Reboot.
Let me know how this goes.

cronus101 said:
Your phone isn't bricked. There are two tools in this forum that can help you. One is made by hasoon2000(I think that's his user name), and the other is jwtool(I think). Use them to help to flash a recovery if you don't know how to use fastboot.
Click to expand...
Click to collapse
I used the hasoon2000 to flash TWRP earlier, but my problems is that my pc wont recognize my phone. When i plug it in it and try to re-flash it it cant find it. When i check my devices it shows up as an android device but it says the drivers are damaged. if i could get it to read it i think i should be eable to reflash somethint.
I APPRICIATE ALL THIS HELP. i really am trying to be as specific as possible :fingers-crossed:

Hey so just a thought and experience I have had with all my HTC phones is when you see that quick glimpse of the TWRP recovery screen then it disappears to an empty black screen......you are sometimes still in a form of recovery but during your Rom flash something (i don't know for sure) changed and it doesn't show the screen only black. So with that long explanation out of the way....have you tried once the screen goes black the
"adb devices "
Mine whenever in this situation would return the output of serial number and recovery so then you can push or sideload the Rom and boot into the system at which point your fastboot drivers will finally be recogniZed.....
Hope this helps a little
Sent from my HTC EVARE_UL using xda app-developers app

Muquita said:
I used the hasoon2000 to flash TWRP earlier, but my problems is that my pc wont recognize my phone. When i plug it in it and try to re-flash it it cant find it. When i check my devices it shows up as an android device but it says the drivers are damaged. if i could get it to read it i think i should be eable to reflash somethint.
I APPRICIATE ALL THIS HELP. i really am trying to be as specific as possible :fingers-crossed:
Click to expand...
Click to collapse
I'd say the next step is to re-install your drivers in the SDK. Open up your Android SDK and reinstall them. In Windows Device Manager, find your connected device (probably now with an exclamation mark on it) and right click on it and select 'Update Driver'.
(Assuming you are using Windows 7 here?)
http://developer.android.com/tools/extras/oem-usb.html

Muquita said:
When i go back into fastboot my only options are
-Bootloader
-Reboot
-Reboot bootleader
-Power down.
I appriciate the help!
Click to expand...
Click to collapse
when you are in fastboot, connect your phone using the usb cable, and when you see "fastboot" written in red turned into "fastboot usb" or something like this, do the commands below using cmd window of course :
1) fastboot erase recovery
2) fastboot erase cache
3) fastboot flash recovery recoveryname.img
4) fastboot erase cache
Let us know when you fix it
Good Luck

wnp_79 said:
I'd say the next step is to re-install your drivers in the SDK. Open up your Android SDK and reinstall them. In Windows Device Manager, find your connected device (probably now with an exclamation mark on it) and right click on it and select 'Update Driver'.
(Assuming you are using Windows 7 here?)
http://developer.android.com/tools/extras/oem-usb.html
Click to expand...
Click to collapse
(Win8 but the procces is identical.) All my drivers are up to date. Still no love.

On the dev forum is a thread that includes all the latest drivers (including an app to remove older drivers.)
Find that thread, download the drivers and bmp and driver removal tool. Remove drivers with tool, install the new drivers, reboot, connect phone and see if 'adb devices' finds anything.
Also make sure you're using the latest adb.
Sent from my HTC One using xda app-developers app

thneed said:
Hey so just a thought and experience I have had with all my HTC phones is when you see that quick glimpse of the TWRP recovery screen then it disappears to an empty black screen......you are sometimes still in a form of recovery but during your Rom flash something (i don't know for sure) changed and it doesn't show the screen only black. So with that long explanation out of the way....have you tried once the screen goes black the
"adb devices "
Mine whenever in this situation would return the output of serial number and recovery so then you can push or sideload the Rom and boot into the system at which point your fastboot drivers will finally be recogniZed.....
Hope this helps a little
Sent from my HTC EVARE_UL using xda app-developers app
Click to expand...
Click to collapse
This actually sounds really similar to my situation.. Would you care to be a little more specific on the procedure? noob here.

Tabtoub said:
when you are in fastboot, connect your phone using the usb cable, and when you see "fastboot" written in red turned into "fastboot usb" or something like this, do the commands below using cmd window of course :
1) fastboot erase recovery
2) fastboot erase cache
3) fastboot flash recovery recoveryname.img
4) fastboot erase cache
Let us know when you fix it
Good Luck
Click to expand...
Click to collapse
My pc will not recognize my phone. The drivers are up to date but when i plug it in it says something malfunctioned ?