Database Develop

[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

Help! Stuck at HBOOT, need ideas/help!

Hi,
I bought a faulty Nexus one from ebay, thought I can fix it, as I did buy a faulty desire from ebay and was able to fix it. This time im not so lucky I guess.
So here it is:
The phone is stuck at X when booting normally.
I can access HBoot (But not Hboot USB Plug, because USB debugging is not enabled) and Fastboot USB. I unlocked Hboot. Fastboot in PC recognizes the phone but ADB does not as usb debugging is not enabled.
The phone is not Rooted
Here are my ideas so far:
Get somehow debugging on with some commands (No luck from reshearching in google)
Reflash stock rom with PASSIMG.ZIP in sdcard, but my phone does not recognize the file from my sdcard (I'm pretty certain im doing something wrong or my idea is somehow wrong)
Flash new images through FASTBOOT, but every time Signature check fails (Shipped-roms.com).
Root with superboot, but signature check failed here too.
Flash a recovery, signature check fails.
I will reguraly update my tries
Please suggest correction to my ideas or suggest new ones!
Help will be much appreciated!
I admit it, the phone might be briked, but I want to make sure that I have tried everything before I abandon this project.
And ofcourse I have no Warranty.

What file are you using for passimg.zip? Make sure it's not a zip inside a zip.
What images are you using via the fastboot flash command?
Sent from my Nexus One

You didn't unlock the bootloader, it seems - because if you did, it wouldn't be checking signatures, and you'd be able to flash anything.

First of thanks to both of you for helping.
I'm pretty sure that i do not have zip inside zip and I downloaded them from shipped roms.com -> android -> Passion-> PASSIMG_Google .... .ZIP, (Then renamed it ofcourse) Is there a difference what version of android i use?
The issue with this is, it checks the SD CARD and does not find anything. I have seen from google that the most common issue is that it starts to check the .zip file but then aborts. Does the SDCARD have to be a goldcard (I do have a goldcard but it might be faulty, right?)
I tried fastboot flash PASSIMG_Google.... .ZIP; Fastboot Flashall ( With having boot, recovery, system in my fastboot folder)
Maybe I should try to flash everything the .zip has in it seperately because that succeded for boot, system and recovery but I was too afraid to flash every partitation (Like Radio which seems to be the scariest and the most easiest way to brick phone)
For the third answer, I have ***UNLOCKED*** in bootloader in purple and top on the screen.
Once again thanks and keep suggesting!

Unpack the ZIP and flash each image separately.
Leave the radio as is, if it's updated enough (5.08 or 5.12). In any case, fastboot won't allow you to flash bad radio - and the risk of bricking the phone using fastboot is near 0.

For passimg.zip, you need to download the FRG33 shipped ROM from shipped-roms.com then EXTRACT the zip file that is inside the zip that you downloaded. Rename that file to passimg.zip
For fastboot, flash boot and system seperately.
When you boot the device normally, do you see the lock icon below the four colored x?
Sent from my Nexus One

Okay,
Did it one by one (PASSIMG_Passion_Google_WWE_2.16.1700.1_FRG33_release_signed.zip):
Succeeded:
Boot, Recovery, System and Userdata (that was only 3Kb)
Failed with signature check (Remote:Signature check failed):
Splash1, spcustom,
Did not do:
Radio
I'm going to post more details:
When booting up, it displays the X normally with the unlocking badge on the bottom of the screen and vibrates once. Then it goes black for a second or even less, the same images comes on and then it vibrates 6-7 times.

now that you successfully flashed the stock recovery, cam you boot into it?
Sent from my Nexus One

Nope, it does that what I described on the previous post
Oh and what's more it randomly during no activity being in fastboot vibrates as well for 5 times or so. It does this rarely but it's there

http://forum.xda-developers.com/showthread.php?t=710937

Thanks, Well thats it then for now, just have to figure out what to do now

Sounds like you need to get the PASSIMG.zip method to work, or unlock and flash a new recovery like amon ra, and flash a full rom with sig checks off.

siimplangi said:
Nope, it does that what I described on the previous post
Oh and what's more it randomly during no activity being in fastboot vibrates as well for 5 times or so. It does this rarely but it's there
Click to expand...
Click to collapse
Ok, but can you boot into recovery? In other words, boot into the bootloader and select recovery.

any solution?
efrant said:
Ok, but can you boot into recovery? In other words, boot into the bootloader and select recovery.
Click to expand...
Click to collapse
hi guys.i have exactly same situation.
does anyone have a solution fir this?

kobi_eidelman said:
hi guys.i have exactly same situation.
does anyone have a solution fir this?
Click to expand...
Click to collapse
Did you try all the solutions suggested above (passimg, fastboot flash, etc)? If yes then no I don't think so.

[Q] S7 won't boot into recovery

I have a S7 that is an X rev and it only has one camera on it and it has a different ID than the current streak 7s, so I can't apply the update that tmobile put out.
So I rooted the S7 and ran ROM MANAGER and it insists that the clockworkmod is installed correctly, but I can't reboot into recovery from that program (I don't think it works on s7 anyway) nor can I do it with the volume+ and power. (All that does is to boot into android)
The fastboot seems to work fine, so is there a way that I can push one of the .ZIP file ROMs using fastboot? I was thinking the "Dell Streak 2.2.2 update with FULL ROOT" would be a good one to try, but there are many .img files in the zip file and when I try fastboot update, I get the following errors:
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
I know that the following lines will work, but there isn't a system.img in the .zip file.
$fastboot flash boot boot.img
$fastboot flash recovery recovery.img
$fastboot flash system system.img
Thanks
Maj

You cant use regular fastboot commands its something like "fastboot -l 0413e blah blah search my threads for "how to flash stock img. " at the bottom of first post you will see fastboot help link
Sent from my Dell Streak 7 using XDA Premium App

http://forum.xda-developers.com/showpost.php?p=11929063&postcount=23
Sent from my Dell Streak 7 using XDA Premium App

Hey thatruth I've never used fastboot -iowhatever. All my fastboot cmds are fastboot (cmd) (dir) (file). Op so when holding +volume and power it doesn't put you in the bootloader? Your device may not work with cwr. Being a X device. And op are you using ubuntu/linux?
Sent from a signal

to get into cwr you have to hold vol and power. Then at the android menu select option 2 update.pkg. it will then boot into recovery
you can also reboot into recovery via adb
adb reboot recovery

graffixnyc said:
to get into cwr you have to hold vol and power. Then at the android menu select option 2 update.pkg. it will then boot into recovery
you can also reboot into recovery via adb
adb reboot recovery
Click to expand...
Click to collapse
I have not found a way to get into recovery. Using adb, fastboot, reboot into recovery options, and attempting vol+ and power, just boots straight into android. It says "cold-booting linux" and boots into android. It seems as if there isn't a real partition to do that, so I somehow need to dump an image onto the s7 so that it will have all of these partitions.
I have a Droid Incredible in which I've hacked to death, so I know how to get into the other menus, they just don't appear to be there or accessible for some reason.

Hellzya said:
Hey thatruth I've never used fastboot -iowhatever. All my fastboot cmds are fastboot (cmd) (dir) (file). Op so when holding +volume and power it doesn't put you in the bootloader? Your device may not work with cwr. Being a X device. And op are you using ubuntu/linux?
Sent from a signal
Click to expand...
Click to collapse
Yah, the +volume and power just boots the phone right into android. ROM Manager tells me that my rooted s7 installs cwr just fine. (in fact I've tried every different version it offers) I use w7 x64.

MajikUF said:
Yah, the +volume and power just boots the phone right into android. ROM Manager tells me that my rooted s7 installs cwr just fine. (in fact I've tried every different version it offers) I use w7 x64.
Click to expand...
Click to collapse
did you try flash cwm through fastboot yet?
http://www.4shared.com/file/l2JpliG6/recovery-clockwork-3019-streak.html
use this to download cwm recovery img

jiwengang said:
did you try flash cwm through fastboot yet?
http://www.4shared.com/file/l2JpliG6/recovery-clockwork-3019-streak.html
use this to download cwm recovery img
Click to expand...
Click to collapse
Assuming that's the same cwm that I got in the streaksmart forum, yah. I flashed that using fastboot as the recovery and then issued the reboot into recovery command and it just booted up android.
At this point, I am assuming the build/version I have isn't a standard build and I will have to do something outside the normal channels to get it to work. I might just chuck this and get another. Especially since I heard that there will be a compatible version of honeycomb for devices with less than stellar resolutions like the s7.

I think the key here is to unplug usb from computer and hold down the power and Vol+ button to reboot into recovery mode.
I struggled with this for probably half a day figuring that out.

thx for your help and I finally figured out the fastboot and then recovery.img. So then I rebooted and seleted the software upgrade via update and it been stuck on that selection for awhile. is that normal?

by the way upper left hand it has in white lettering Booting recovery kernel image.

chavezop said:
thx for your help and I finally figured out the fastboot and then recovery.img. So then I rebooted and seleted the software upgrade via update and it been stuck on that selection for awhile. is that normal?
Click to expand...
Click to collapse
It should say Booting recovery kernel image and then take you straight into clock work recovery...

Mines doing the same thing just getting stuck when it says Booting recovery kernel image and the dell logo apears then when i press the power button it turns off if i boot the device up not plugged into my computer and hold the power and volume+ it will flash red the LED and turn off.

Resolved Yet???
I'm having the same issue... CWM says it's working fine but when I try to load ROM it reboots normally back into the menu... Red lights blinking and does nothing when trying to get into recovery mode. Fastboot is only thing that seems to work and that even doesn't work properly...
I'm stuck with a ROM that is constantly crashing. Every 10 min or so, it needs to go. Please anyone that may have a method I could try would be appricitated...
J

[Q] white triangle with yellow exclamation mark

Hello. I want to install the latest stable Cyanogenmod version 7.2.0 on my Nexus One which was up to now unlocked with stock software.
I followed instructions up to this point:
Installed Android SDK
Installed (downloaded) fastboot
Unlocked phone - bootloader now shows UNLOCKED, and the opened padlock symbol appears when powering up.
Downloaded and transferred recovery-RA-passion-v2.2.1.img
Up to this point all was ok. However when I select RECOVERY (from within BOOTLOADER) and press the POWER button, the phone reboots and I end up with a green android, a white triangle and yellow exclamation mark. The phone basically sticks there and I have to remove the battery. A photo is attached for your reference.
I also downloaded and transferred recovery-clockwork-5.0.2.0-passion.img However the same thing happens.
So basically I am stuck at this point. I can only remove the battery, and reboot the phone using the stock ROM.
What do you recommend?

hw did you transfer recovery.img? was it successfully flashed?
Sent from my Nexus One using Tapatalk

n1newbie said:
hw did you transfer recovery.img? was it successfully flashed?
Sent from my Nexus One using Tapatalk
Click to expand...
Click to collapse
Hi,
i transferred it using cmd prompt with command fastboot flash recovery recovery-RA-passion-v2.2.1.img and it was successful.
The same applies to when i transferred the recovery-clockwork-5.0.2.0-passion.img
What do you recommend?

White triangle and yellow exclamation mark means that you still have stock recovery, so the custom recovery flash did not work. When you see the triangle and exclamation mark you should push and hold both the Volume Up and Power Button (give it a few tries). Not that this will help you, but you don't have to pull the battery anymore
What do you see when you type fastboot devices in the command prompt when your phone is in fastboot mode?

tommert38 said:
White triangle and yellow exclamation mark means that you still have stock recovery, so the custom recovery flash did not work. When you see the triangle and exclamation mark you should push and hold both the Volume Up and Power Button (give it a few tries). Not that this will help you, but you don't have to pull the battery anymore
What do you see when you type fastboot devices in the command prompt when your phone is in fastboot mode?
Click to expand...
Click to collapse
Hi,
I run fastboot by starting a command prompt and changing to directory:
c:\users\xxxxxx\appdata\local\android\android-sdk\platform-tools
when I type fastboot devices i get the following reply:
HT05DP800931 fastboot
when I type fastboot flash recovery recovery-clockwork-5.0.2.0-passion.img i get the following reply:
sending recovery (3058 kb)
OKAY [ 0.499s]
writing 'recovery'....
OKAY [ 1.140s]
finished. total time 1.647s
So I assume the transfer is ok.
Is the path mentioned above correct?
Any idea what could be wrong?

All seems okay to me like that.. Could you try to flash 4EXT recovery? Make sure the recovery.img is in the same folder as fastboot (c:\users\xxxxxx\appdata\local\android\android-sdk\platform-tools). When it's finished, type fastboot reboot-bootloader and then navigate to recovery..

tommert38 said:
All seems okay to me like that.. Could you try to flash 4EXT recovery? Make sure the recovery.img is in the same folder as fastboot (c:\users\xxxxxx\appdata\local\android\android-sdk\platform-tools). When it's finished, type fastboot reboot-bootloader and then navigate to recovery..
Click to expand...
Click to collapse
Hello Tommert38,
Immediately after i sent my last post i tried again RECOVERY and to my surprise it worked! I proceeded with Backup, Wipe Factory and installed zip from SD card (first Cyanogenmod and then Google apps).
Everything seems to work, apart from MARKET. I can browse apps, however when i select any app and try to download it, I get error message "app name" could not be downloaded due to an error.
I googled for similar problems and found a post on xda developers:
http://forum.xda-developers.com/showthread.php?t=1724463
However i cannot find a solution.
Can you help?

can try different rom?
Sent from my Nexus One using Tapatalk

n1newbie said:
can try different rom?
Sent from my Nexus One using Tapatalk
Click to expand...
Click to collapse
Hello,
i tried 7.1 and it works great.
thanks for your help.

spannerj said:
Hello,
i tried 7.1 and it works great.
thanks for your help.
Click to expand...
Click to collapse
good . might be rom/gapps issue
Sent from my Nexus One using Tapatalk

I had similar problems with the white triangle/yellow exclamation mark.
Started with N1, never modified. Trying to run Recovery took me straight to triangle.
Unlocked bootloader, then tried to load ClockworkMod before rooting, as some tutorial told me to. File transferred without error, but still went straight to triangle when trying to run.
Rooted with SuperOneClick.
Went back and loaded CWM again with command line fastboot, again no error but still went to triangle when trying to run.
Downloaded Rom Manager (free) from app store, used it to install CWM. This actually worked for a few times, then it too started going directly to triangle when trying to run. It might have started failing when data was wiped, not sure.
Loaded the Amon Ra recovery tool using fastboot, it has worked reliably so far. Went on to load CGM 7.2 plus the apps, that was uneventful.
Some tutorial claimed you needed to load android-sdk directly under C:, not sure that's really required, but that's what I did.
Dave

That's happening most likely because all the participants of this thread are using stock ROM, and instead of booting to recovery directly from fastboot after flash, they first loaded the ROM and then tried to go to recovery.
Almost 3 years back, when actual developers with knowledge were all around this forum, it was a common knowledge that stock ROM overwrites the recovery on each boot, and to stop it from overwriting one should delete the stock recovery image that is used for that from the ROM. Also, booting to recovery directly after it was flashed and removing the stock recovery image from a ROM was a known way to avoid this kind of problems. I didn't try it, but I believe Google can still help finding these pieces of information, and Wiki definitely still holds them.
Well, I guess nobody reads the Wiki these days.
http://forum.xda-developers.com/wik...ages#For_unlocked_bootloader_-_using_fastboot
What really disturbs me is that the thread went to 2nd page without even a hint for this answer, while it's all that simple to get to - "Wiki -> Recovery", and here you have it.

yellow exclamation in white triangle
tommert38 said:
White triangle and yellow exclamation mark means that you still have stock recovery, so the custom recovery flash did not work. When you see the triangle and exclamation mark you should push and hold both the Volume Up and Power Button (give it a few tries). Not that this will help you, but you don't have to pull the battery anymore
What do you see when you type fastboot devices in the command prompt when your phone is in fastboot mode?
Click to expand...
Click to collapse
i also have the same problem but i did no flash i did hard reset on my galaxy spica(gt-i5700) and now stuck on that symbol my phone gets rebooted every time and get stuck on that symbol so plz help i also tried to flash with odin but my phone goes in download mode but is not detected by odin plzzz help and rply ass fast as possible i am using win 8 32 bit

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