Database Develop

[Q] Stuck at Fastboot usb screen

I installed the new zen2.2 rom today and had a working clockwork recovery. Here is where I went stupid, I downloaded the kernel update but rather than running it via update.zip I flashed it using flash_image recovery via adb shell.
Now my phone comes up to fastboot usb and never goes any further, been waiting hours! I have tried booting into fastboot/hboot and it does nothing. I have booted to hboot before successfully but now nothing.
If I run adb devices it shows no devices. If I run fastboot devices it does show my device.
Whats next?

If you cant get into fastboot and you cant get into recovery then you m ight have bricked your phone. Did you try a hard reset?

How do you do a hard reset?
Here is a little more info. I believe it does actually get to fastboot usb as it says so on the top left of the screen and I can run fastboot commands but most commands say error. If I do fastboot devices it shows the device connected.
Little more info - when I try doing a back to basics RUU update it connects, shows the rom version, starts the update and then at about 88% every time, it goes right to a error [171] usb connection error. So its communicating but never finishes. Tried with the sprint RUU stock rom, another that was built by one of the devs in the Hero community and still both do the same.

I'm pretty sure you can flash a custom recovery from fastboot. Using something like fastboot flash xxx dont quote me on this but it sounds like you have a soft brick and you just need to get a recovery back on the phone. From there you can then flash and rom back on the phone. Do some research on flash a recovery from fastboot.

ASimmons said:
I'm pretty sure you can flash a custom recovery from fastboot. Using something like fastboot flash xxx dont quote me on this but it sounds like you have a soft brick and you just need to get a recovery back on the phone. From there you can then flash and rom back on the phone. Do some research on flash a recovery from fastboot.
Click to expand...
Click to collapse
Right, I also believe that if I could get a recovery back on the phone I would be good as gold! Here is the problem though. I have tried running "fastboot flash recovery [recovery.img]" but it gives me the below error. I have tried multiple key combination's to get into hboot but nothing works. If anyone has any other key combination's I could try please let me know!
Code:
D:\android-sdk-windows\tools>fastboot flash recovery recovery.img
sending 'recovery' (3720 KB)... FAILED (remote: not allow)
finished. total time: 0.001s

1st:The ONLY time you use flash_image recovery is when you are installing a recovery console, NOT a kernel
If you notice the kernel is in a signed .zip folder. When you use flash_image command it needs to be .img file
2nd: Put the recovery image on your sdcard
Put it in the tools folder of AndroidSDK and do
Code:
adb push recovery.img /sdcard
Now type in
Code:
$ adb shell
$ su
# flash_image recovery /sdcard/recovery.img

unCoRrUpTeD said:
1st:The ONLY time you use flash_image recovery is when you are installing a recovery console, NOT a kernel
If you notice the kernel is in a signed .zip folder. When you use flash_image command it needs to be .img file
2nd: Put the recovery image on your sdcard
Put it in the tools folder of AndroidSDK and do
Code:
adb push recovery.img /sdcard
Now type in
Code:
$ adb shell
$ su
# flash_image recovery /sdcard/recovery.img
Click to expand...
Click to collapse
Yeah I think he knows now not to flash kernels... atleast I hope so. +1 for your post.

unCoRrUpTeD said:
1st:The ONLY time you use flash_image recovery is when you are installing a recovery console, NOT a kernel
If you notice the kernel is in a signed .zip folder. When you use flash_image command it needs to be .img file
2nd: Put the recovery image on your sdcard
Put it in the tools folder of AndroidSDK and do
Code:
adb push recovery.img /sdcard
Click to expand...
Click to collapse
I am fully aware of how the how-to's and what not to do's. Like I said, it was a mistake, call it a bit of anxiety due to the new 2.2 rom that I was trying to get installed. I did it too quick and without much common sense .
Now type in
Code:
$ adb shell
$ su
# flash_image recovery /sdcard/recovery.img
Click to expand...
Click to collapse
For the second part, I am unable to do anything with adb as my computer does not see the phone. When running adb devices it is not listed. Only command that sees my phone is fastboot devices, but again I am unable to run anything aside from that due to previous error.

casualonejp said:
I am fully aware of how the how-to's and what not to do's. Like I said, it was a mistake, call it a bit of anxiety due to the new 2.2 rom that I was trying to get installed. I did it too quick and without much common sense .
For the second part, I am unable to do anything with adb as my computer does not see the phone. When running adb devices it is not listed. Only command that sees my phone is fastboot devices, but again I am unable to run anything aside from that due to previous error.
Click to expand...
Click to collapse
First do you have the eng spl, does your hoot say s (on)
Have you tried that command but point it to the sdcard? Also do you have any files on your sdcard like say a recovery.img or an update zip. If you don't you might need to manually move the file to it and try some of these commands
fastboot update /sdcard/<imagepackage>.zip [-w] -w will wipe the cache and the user/data
or your previous flash recovery but with the file pointing to the file on the sdcard
edit: sorry i dont think fastboot will see the sdcard but try anyways.

ASimmons said:
First do you have the eng spl, does your hoot say s (on)
Have you tried that command but point it to the sdcard? Also do you have any files on your sdcard like say a recovery.img or an update zip. If you don't you might need to manually move the file to it and try some of these commands
fastboot update /sdcard/<imagepackage>.zip [-w] -w will wipe the cache and the user/data
or your previous flash recovery but with the file pointing to the file on the sdcard
Click to expand...
Click to collapse
I will try the fastboot command right now. I am unable to get to hboot with any of the key combination I have tried, before I was able to. Only thing that always comes up is the HTC white screen with fastboot usb at the top left. Can't see what hboot version or anything else I have due to that limitation.

casualonejp said:
I will try the fastboot command right now. I am unable to get to hboot with any of the key combination I have tried, before I was able to. Only thing that always comes up is the HTC white screen with fastboot usb at the top left. Can't see what hboot version or anything else I have due to that limitation.
Click to expand...
Click to collapse
After reading a bit you should be able to do something like i described
- copy amon_ra image to yor sd
- flash_image recovery /sdcard/name-of-recovery.img
hopefully you have a way to copy the files to your sd card like say a microsd card converter and stick it in your comp. Or I have had to use a freaking camera once for my g1 after being in a similar situation.
edit: ok so maybe you wont be able to if you spl is in s-off mode.
if you can access your card and see if you have nadroids you could also try this
fastboot flash system /path/to/nandroid/system.img
fastboot flash boot /path/to/nandroid/boot.img
fastboot flash userdata /path/to/nandroid/userdata.img
fastboot reboot
hopefully you have these backed up on your puter to.

ASimmons said:
After reading a bit you should be able to do something like i described
- copy amon_ra image to yor sd
- flash_image recovery /sdcard/name-of-recovery.img
hopefully you have a way to copy the files to your sd card like say a microsd card converter and stick it in your comp. Or I have had to use a freaking camera once for my g1 after being in a similar situation.
edit: ok so maybe you wont be able to if you spl is in s-off mode.
if you can access your card and see if you have nadroids you could also try this
fastboot flash system /path/to/nandroid/system.fimg
fastboot flash boot /path/to/nandroid/boot.img
fastboot flash userdata /path/to/nandroid/userdata.img
fastboot reboot
hopefully you have these backed up on your puter to.
Click to expand...
Click to collapse
Negative on the fastboot commands. Also did have a nandroid but on old sdcard which died. I read that I could use anothers nandroid backup but I am currently trying to find one to test.
Tried doing the RUU method with stock/custom roms and it gets as far as seeing the image but when I click on "ok" to start the recovery, it goes to "waiting on bootloader" and then at 88% it errors to a 171 error stating usb connection error.

I would do some research its my understanding that you can't be bricked since you can get into spl. You should be able to put an .img file on your sd card and flash it. Sorry I can give you any more input.

ASimmons said:
I would do some research its my understanding that you can't be bricked since you can get into spl. You should be able to put an .img file on your sd card and flash it. Sorry I can give you any more input.
Click to expand...
Click to collapse
Ya I have been researching non stop all yesterday evening and today so far all day. I just cant get it to do anything. I will keep researching though. Thanks

Did you fix this yet?

Anyone figure this out yet...I have the same issue and haven't been able to resolve it yet. Still with a brick at this point!

Hey guys,if your stuck at fastboot(As I just was tonight), try in your CMD(if running Windows) fastboot reboot-bootloader or fastboot reboot to reboot as normal,I'll try to keep you updated to get through all this. I am at a loss right now but searching for answers first before i go about asking.
Answer to MY problem(maybe not yours): OK,I have come to the conclusion here tonight that I had a soft brick. What I did was remove the battery,put the battery back in,restarted the phone normally,then I ran the HTC Sprint Hero MR 2.27.651.6 on my computer(essentially restoring back to unrooted factory settings). This worked for me. I am totally refreshed and happy that my phone is ok and all. Yes I may have to go back and re-root but this only take me bout 20 minutes most to root and re-flash a CyanMod7 Nightly Rom. Hope my info can help out somebody!

[Q] Help flashing Rom (I think i've gone wrong...)

Right, can someone give me a quick set-by-set of what to do from my position.
I can access HBOOT fine (HBOOT-1.33.2005 / RADIO-2.22.23.02) and i can access my System Recovery fine (RA-dream-v1.7.0), but i can't boot to my Rom.
I have the following on my desktop:
HBOOT-1.33.0013d
RADIO-2.22.27.08
gapps-tiny-112010 (that the right one?)
froyobylaszlo-5.1 (from: http://forum.xda-developers.com/showthread.php?t=929678)
If my thinking is right, i need to:
- Delete the rom etc. that i installed wrong
- Move the files from my desktop onto my SD
- Install everything
- Boot
However, i'm not sure how to go about that... So this is where i need the simple instructions and advice.
**There was a serial0 question before, so ignore the first few posts.

Seems it's because i was using RC29 instead of RC7...
Soon as my phone has charged, i'll flash the rom

New issue:
Need some help people. Rooted my G1, worked. Got it back to 1.5, then updated it all. Installed the Recovery.img and that worked. Now, i want to install this:
http://forum.xda-developers.com/showthread.php?t=929678
But im not sure what radio, SPL and gapps to use. I followed this video:
http://www.youtube.com/watch?v=DR0HpUVv-BY
Then when he installed Cyanogen, i installed Gingerbread. Now im stuck on the boot screen and have been for 2 hours... ideas?
I'm thinking the files i used, from the video, ain't compatible. So, anyone have links to "SPL: 1.33.0013d (hboot)" and "RADIO: 2.22.27.08 / 28.25"? Then, what do i do from the Recovery screen to delete all i did and install Gingerbread?

wow you are in a rush to take the G1 all the way to the hilt arent ya?
What roms have you successfully run on it prior (if at all) to trying to flash Lazlo? Did Eclair work?

I ran Cyanogen6 for a long while till it developed a slight lag. In all i've ran:
Cyan6, then 1.6, then Cyan6, then 1.6 again, now im trying this.

I created the 3 - 4 Partition, THEN the 2 - 3 Partition.
Think that could be the issue?
If so, how do i go back and try again?
**NEW QUESTION FROM HERE

dmreall said:
Right, can someone give me a quick set-by-set of what to do from my position.
I can access HBOOT fine (HBOOT-1.33.2005 / RADIO-2.22.23.02) and i can access my System Recovery fine (RA-dream-v1.7.0), but i can't boot to my Rom.
I have the following on my desktop:
HBOOT-1.33.0013d
RADIO-2.22.27.08
gapps-tiny-112010 (that the right one?)
froyobylaszlo-5.1 (from: http://forum.xda-developers.com/showthread.php?t=929678)
If my thinking is right, i need to:
- Delete the rom etc. that i installed wrong
- Move the files from my desktop onto my SD
- Install everything
- Boot
However, i'm not sure how to go about that... So this is where i need the simple instructions and advice.
**There was a serial0 question before, so ignore the first few posts.
Click to expand...
Click to collapse
froyobylaszlo-5.1 needs radio 2.22.27.08/2.22.28.25,spl 1.33.0013d,flash your radio&spl first

Got Cyanogen6 working on it now.
I downloaded HBOOT-1.33.0013d and RADIO-2.22.27.08, zipped them, then moved them onto my SD card and when i try flash them on my G1, it's says invalid file.

dmreall said:
Got Cyanogen6 working on it now.
I downloaded HBOOT-1.33.0013d and RADIO-2.22.27.08, zipped them, then moved them onto my SD card and when i try flash them on my G1, it's says invalid file.
Click to expand...
Click to collapse
have u tried the guide from here to update your radio and spl
(p/s u need to follow it properly and understand most of the jargons such as spl perfect or engineered and etc)
http://forum.xda-developers.com/showthread.php?t=831139

Ok, so going by that i need to:
- Put them files onto my SD (not zipped, just as they are downloaded and into the root)
- Boot into fastboot
- Enter Console and type:
Code:
fastboot flash recovery recovery-RA-dream-v1.7.0-cyan.img
fastboot flash radio radio-2.22.27.08.img
fastboot flash hboot hboot-1.33.0013d.img
fastboot reboot-bootloader
- Check it says "1.33.0013d" as its version
- Enter console again and type:
Code:
fastboot erase system -w
fastboot erase boot
- Restart
- Boot to Recovery
- Go to "Flash"
- Select "Froyo by Laszlo"
- Reboot

Am i right with that method?
Need to know before i risk it

Just install yoshi ginger its so smooth (gingerbreab 2.3)
sent from my gingerdream

dmreall said:
Am i right with that method?
Need to know before i risk it
Click to expand...
Click to collapse
In theory it is already right. Maybe some small litte details.
After fastboot erase(before flashing rom), u should partition your sdcard so that it has the ext4 partition ( from recovery, partition sd, follow steps, upgrade from ext2 to ext3, upgrade ext3 to ext4 )
After that try using the wipe and reset all data to factory.
Now maybe u are good to go with flashing roms.
For the radio/hboot guide, just follow step by step from the thread.

This better then? I just want to make a guide for the future.
- Put "Recovery", "Radio" and "HBOOT" files onto SD (not zipped and into the root)
- Boot into fastboot
- Enter Console and type:
Code:
fastboot flash recovery recovery-RA-dream-v1.7.0-cyan.img
fastboot flash radio radio-2.22.27.08.img
fastboot flash hboot hboot-1.33.0013d.img
fastboot reboot-bootloader
- Check it says the Hboot that was just flashed as its version
- Enter console again and type:
Code:
fastboot erase system -w
fastboot erase boot
- Restart
- Boot to Recovery
- Go to "Partion SD"
- Partition SD with "Swapsize = 96" and "Ext2 = 1024" then "Ext2 to Ext3" then "Ext3 to Ext4"
- Go to "USB MS Toggle"
- Move Rom onto SD
- Go to "Flash"
- Select the ROM to flash
- Reboot
Click to expand...
Click to collapse

looks quite good, do u want to make a guide for the forum or just for urself?
If for the forum, maybe just add some small details as example :
boot into recovery ( hold power + home together )
Just for the new people without experiences in flashing.

No, this is for myself. Just trying to get a solid method i can reference to whenever im stuck.

Fastboot is "Power + Camera" yes? If so, i don't see a console.

Still need that one answered.
Also, should i put the files as .img or .zips in the root of my SD?

Fastboot can be accessed with camera and power or back and power.
You would move the files as zips.
A couple of notes. I wouldn't upgrade to ext4 as not all roms work with 4 (most do but not all) just go to ext3 and you will be good. If it supports ext4 then it will 3 also.
Also most of your guide is really only needed for the first time. if you are just switching roms you don't need to do half of that.
If just switching roms you only need to boot to recovery, wipe/factory reset, flash/install zip (depending on what the recovery calls it its the same thing). Reboot and enjoy.

Android G1 mobile software required (urgent)
Hi,
I have Htc G1 android mobile set.
The problem is my mobile phone only goes till G1 logo and does not proceed forward.
I think i have to flash my mobile set using micro SD card.
Can anyone plz share with me android G1 software and the method to do that.
I shall be grateful.
Regards,
Khurram

[q] need simple step by step guide .... Links please...

guys i've a g1.. its rooted .. when i go to About phone it shows:
firmware version: 1.5
model no: htc magic
baseband: 62.33.20.080. 1.22.12.29
build no. PLAT RC 33
i've recovery 1.7.0 installed, i even installed new radio & SPL through recovery...in fastboot mode it shows :
Dream PVT 32b Eng s-off
hboot- 1.33.2003
radio- 2.22.19i
ok... so now i want radio 2.22.28.25, spl 1.33.0013d (hboot) & froyo by lazlo 5.2 on my g1... last night i upgraded both radio & SPL but it didnt boot so i reverted through recovery, please give me simple steps to flash to this rom... also note that if there anything that i should be careful of can be mentioned... any other help or suggestion is welcomed... thanks in advance...
P:S: sorry guys i meant to say no links please... only simple instructions will do... i get more confused with links ....

well youll need links for the file you need
the best way is to flash through fastboot, have you used adb or fastboot before?
if not you should learn but this can be done from recovery. dont recommended it though
what i do recommended is looking at all the great guides throughout xda on how to do this (root and upgrade) but if you need your hand held i dont mind.
so read up, if your still confused let me know and i or another helpful soul here will help

thanks for the quick reply... i've the files allready... i've ADB in my pc... my sd is in fat32 format ... so please tell me how to flash through fastboot...

so power on while holding back or camera and plug your phone into your pc, if this is the first time a driver or two should pop up (android 1.0 or something)
no you will be on hboot screen and phone will say in red fastbootusb
with me so far?
now open the folder where all files are, here you need recovery (yes i know you have it but you still need it) radio, spl
also have the orange.nbh file handy in case you have trouble
(also best to have all these files in your platform-tools folder along with adb in case you havent changed the environmental variables and added a path for adb)
hold shift and right click choose open command window here
now type <fastboot>
hopefully a list of commands pops up this will tell you fastboot is working
now type fatboot devices
should show phone id here
if all is good lets proceed
type <fastboot flash recovery recovery.img>
(or whatever the file name is for your recovery)
you should get a notification it worked
now <fastboot flash radio 2.2....img>
(replace the 2... with the name of your radio image)
now fastboot flash hboot 1.33..img>
(replace 1.33... with the name of your spl image)
here is a sample of what this would look like in fastboot for me
fastboot flash recovery recovery-RA-dream-v1.7.0-cyan.img
fastboot flash radio radio-2.22.27.08.img
fastboot flash hboot hboot-1.33.0013d.img
so if you name your files the same as above you can just copy and past these commands
oh and if i didnt mention before you must extract the zip folders into the same location as adb unless you change environmental variables on your pc
been drinking a little so hope this is good! let me know how you fair

okk bro... but do i flash the new rom ??? i have lazlo 5.2.zip ....

When your done with the recovery,radio,spl you will type fastboot reboot recovery
Now flash fbl from recoveery
You can't do anything in flashboot except -w now because you will be quasi s-on
But fastboot wipe is the cleanest wipe so do this inbetween flashing roms, and superwipe cause wiping is fun
So yes flash roms only in recovery after this update
Sent from my HTC Vision using xda premium

srry to bother you bro... but can you please elaborate the last process with commands ?? like i have the rom in .zip format so wht should i type in console & what should i do after that ??? srry man i am a total noob !!!! BTW what is FBL ???

Fbl froyobylazslo
The rom has to stay a .zip to flash it from recovery, the radio,spl and recovery has to be extracted from the .zip to be flashed in fastboot
Sent from my HTC Vision using xda premium

sousaptak said:
srry to bother you bro... but can you please elaborate the last process with commands ?? like i have the rom in .zip format so wht should i type in console & what should i do after that ??? srry man i am a total noob !!!! BTW what is FBL ???
Click to expand...
Click to collapse
If, and only if, you already have 1.33.0013d and the 27.08 radio, copy the Froyobylaszlo zip onto the sd card. Just that one zip. Nothing else. Boot into recovery by pressing power+home. Go to flash zip and choose the zip, flash it, and reboot and enjoy

Hey frankdrey, long time no see!
Sent from my HTC Vision using xda premium

demkantor said:
Hey frankdrey, long time no see!
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Hey demkantor
I quit most of the internet for a while, but I'm back now.
(Offtopicness xD)
Anyway, um. To OP. Do you have an ext partition on your sd card? I'm pretty sure FBL requires one.
Sent from my HTC Dream using Tapatalk

no bro... i dont ... how to do that ???

sousaptak said:
no bro... i dont ... how to do that ???
Click to expand...
Click to collapse
In recovery. Find the partition sd card option. What size is your sd card and how many apps do you expect to have? Ill give you a suggestion.
Sent from my HTC Dream using Tapatalk

you have amonra1.7 now right?
boot into recovery and scroll down to partition sd card
if you want sawp (more than likely you do) choose around 96mb
then choose about 512 for ext
(this will be good choices for a card that is 2gb or more)
then after it runs its course i suggest scrolling down to ext2 - ext3
after that runs its course do the ext3 - ext4
(there are pluses and minuses to ext4 but i feel the speed out ways the life expectancy)
i assume you have finished all the fastboot commands from earlier?
so if you hold camera and power phone reads .28 (or whatever .25) for radio
and .13d for hboot?
if yes than do this and then flash fbl, when you reboot let the phone idle 5-10min
then yeah! your golden!

demkantor said:
you have amonra1.7 now right?
boot into recovery and scroll down to partition sd card
if you want sawp (more than likely you do) choose around 96mb
then choose about 512 for ext
(this will be good choices for a card that is 2gb or more)
then after it runs its course i suggest scrolling down to ext2 - ext3
after that runs its course do the ext3 - ext4
(there are pluses and minuses to ext4 but i feel the speed out ways the life expectancy)
i assume you have finished all the fastboot commands from earlier?
so if you hold camera and power phone reads .28 (or whatever .25) for radio
and .13d for hboot?
if yes than do this and then flash fbl, when you reboot let the phone idle 5-10min
then yeah! your golden!
Click to expand...
Click to collapse
One importatnt thing: MAKE A BACKUP!!!!!!!!!!!111

demkantor said:
you have amonra1.7 now right?
boot into recovery and scroll down to partition sd card
if you want sawp (more than likely you do) choose around 96mb
then choose about 512 for ext
(this will be good choices for a card that is 2gb or more)
then after it runs its course i suggest scrolling down to ext2 - ext3
after that runs its course do the ext3 - ext4
(there are pluses and minuses to ext4 but i feel the speed out ways the life expectancy)
i assume you have finished all the fastboot commands from earlier?
so if you hold camera and power phone reads .28 (or whatever .25) for radio
and .13d for hboot?
if yes than do this and then flash fbl, when you reboot let the phone idle 5-10min
then yeah! your golden!
Click to expand...
Click to collapse
@ demkantor & frankdrey .... thanks to you both ... now i've got what i wanted...thanks again you guys made my day

No problem, and shortybro need make a good point, as soon as you set up the rom just how you like it, reboot into recovery and scroll down to backup, and do a nandroid. This is like a restore point in case you mess something up. Also do it before you flash another rom, if you don't like that rom it a quick step back to have it just the way you like it. Just remember to wipe!
Sent from my HTC Desire Z using xda premium

yup... i did...

[Q] Flashing CM7

Hi all!
Last week I bought a used but still good-looking T-Mobile G1 (HTC Dream). The previous owner has rootet it (Android 1.6 is installed) and this are the infos:
Firmware-version: 1.6
Baseband-version: 62.50S.20.17U_2.22.19.26I
Kernel-version: 2.6.29-00479-g3c7df37
[email protected] #19
Build-number: DRC92
Click to expand...
Click to collapse
I looked through the forums here on XDA and found a laggy ICS-port, so I want to flash Gingerbread (CM7).
I've already flashed my Galaxy S, a friend's Galaxy R and my Asus Transformer tab, without any problems.
But flashing HTC-devices seems a little bit more complicated.
So what do I need to do? In the CyanogenWiki there's 'Danger_SPL' mentioned, guess I'll need it?
I don't need a looooong step-by-step-guide the correct threads or pages would be enough.
Thanks,
Lunch

need to know more about your phone, boot into bootloader mode (hold power + camera)
write down everything on this screen

DREA110 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-2.22.19.26I
Sep 2 2008
Serial 0
Click to expand...
Click to collapse
(at the moment it's connected with my PC for chrarging, this should explain Serial 0, right?)
Hope this helps.

ok so even if it is rooted the radio and spl need to be updated, which recovery is on there. (power on holding home button)

Ok, I bought it like this and didn't change anything...
Recovery: Android system recovery <2e>
(blue font)

ok you want amonra's recovery found here
http://wiki.cyanogenmod.com/wiki/HTC_Dream:_Rooting
this guide will help you root and update your phone, being your phone is rooted do not flash the dreaming.nbh or you will be reverted back to android 1.0 and loose root
you want to skip that step and go to flash amonra via terminal emulator
then update radio via recovery
then update to danger spl (must have radio updated first or you will brick!)
then i recommended flashing cm5 + gapps found in this link
once you finished this and confirmed all is working you want to update radio and spl further to be able to flash the newest roms, info here:
http://forum.xda-developers.com/showthread.php?t=831139
good luck and let me know if you get stuck (also the search function in xda is great and most of your question will have been answered, peek around a bit its more rewarding than having your hand held)

Thanks a lot for your help, I'll try it!

One quick question about the Telnet-app: do I have to write flash_image recovery /sdcard/recovery.img into the left text field and 23 in the right?
Error while connecting to server: localhost/127.0.0.1:23 - Connection refused
What do I do wrong? With Terminal Emulator the command isn't found...

telnet may not work thats ok
in terminal emulator you need to give yourself superuser permissions first
type su
then say yes to prompt
you are rooted right? do you have superuser.apk in app drawer?

Yes, I'm rooted and I'm su in Terminal Emulator.
Then there's this message: flash_image: not found
But the file is on the root of the sdcard, named recovery.img ...
And when navigating to /sdcard via Terminal Emulator and typing ls I see the recovery.img-file...

if you use windows it will auto add extentions, ie if you name it recovery.img it will read recovery.img.img
try naming it just recovery
also if it came in a .zip make sure you extract it so its a .img
Sent from my HTC Vision using xda premium

No, it's definetely named recovery.img ...
Is there another possibility to flash the recovery-file (via ADB for example)?

yes adb should work fine. i cant remember the command to type when you in adb but just by typing adb into the cmd you will get a list of commands including how to push the file/image you need.
Sent from my HTC Vision using xda premium

cd <adb-folder>
adb devices
adb shell
su
adb flash_image recovery /sdcard/recovery.img
Click to expand...
Click to collapse
Would this be possible (I can't test it now, phone is charging atm).
Thanks

that might just be perfect, but you said that didnt work from terminal emulator and a shell is nearly the same,
its worth a shot. being you are rooted you can try the orange.nbh and you will have an engineering spl where fastboot commands work and i can easly explain those (i dont use adb much but have used fastboot many time) so if adb dosent work for you check out one of the many guides out there or try ornage.nbh and fastboot
Sent from my HTC Vision using xda premium

Same message: flash_image: not found, but with ls I can see it...
Ok, my phone is rooted, I have the Superuser-app in my app drawer, I'm root when accessing the sdcard, I see the file when typing ls. What do I do wrong?
I've never run in trouble when rooting my Galaxy S or my Transformer tab. But my G1 seems quite defiant.

well not being there its hard to say, now try the ornage.nbh
youll find this file in the development section under ezterry's thread under 2708+ update 14mb ram hack. rename the image dreaming.nbh and put it on sdcard. now boot into hboot (power+ camera) and say yes to the prompt. this will allow you to use fastboot and allow you to flash recovery, radio and spl. when/if this all works then boot into recovery (home + power) and flash rom
Sent from my HTC Vision using xda premium

Ok, I'll try, thanks!
Just to go sure:
- I download orange-1.58......nbh from here: http://forum.xda-developers.com/showthread.php?t=831139 , rename it and put it onto my sdcard
- Flash it in fastboot (fastboot = hboot?)
- Flash Amon_Ra-recovery from cyanogenwiki
- flash spl (radio needed too?)
- ?

Don't want to mix in, but just some few stuff you should know:
Fastboot is a sort of recovery on your pc, although this has much more safety measures.
That .nbh file is a file that is a fresh new start to your phone: Like you have a new phone
From Fastboot you can flash a recovery, that you can take with you everywhere
The SPL/RADIO are BOTH needed to succeed. Cheers and if I made any mistakes, please point me to them

fastboot is within the bootloader. it is a .exe program in your sdk package and works similar to adb. the orange.nbh needs to be renamed dreaming.nbh and when you boot into your bootloader it will rewrite your recovery, radio, system, spl etc
the new hboot you get will have a fastboot option in it. connect the phone via usb and when in fastboot mode you will see fastboot usb in red on your phone. you will open a cmd in the same way as adb and will type fastboot devices just live adb to make sure you are attached.
the rest is explained in the op of that thread
Sent from my HTC Vision using xda premium

[Q] Flashing Custom Recovery

I'm having hard time flash custom recovery. I installed ROM Manager, when I tried to go to recovery I got stuck at android logo with EXCLAMATORY POINT. I already followed this instructions http://forum.xda-developers.com/showpost.php?p=10467058&postcount=1638 (deleted these files /system/etc/install-recovery.sh and /system/recovery-from-boot.p)
Followed these instructions:
via fastboot
Code:
Copy recovery-RA-passion-v2.2.1.img to a location where fastboot can find it.
Boot your phone into fastboot mode (power on while holding the trackball)
Connect your phone via usb to your pc/mac/...
fastboot devices (to make sure that fastboot "sees" your phone)
fastboot flash recovery recovery-RA-passion-v2.2.1.img
Click to expand...
Click to collapse
via terminal app
Code:
Copy recovery-RA-passion-v2.2.1.img to the root of your sdcard
start the terminal app
su(press enter)
flash_image recovery /sdcard/recovery-RA-passion-v2.2.1.img(press enter)
reboot recovery(press enter)
Click to expand...
Click to collapse
I also installed 4Ext Touch Recovery, but I think it need a wifi to connect to server, but I can't access a wife connection as of now.
What am I missing? I'm about to flash a ROM, my problem is just the recovery.. Anyone can help me with this? :crying:

i dont think you are missing anything just boot into recovery and flash your rom.
dont use rom manager to flash recovery, dont use 4ext recovery control app.
if you used one of the two methods you mentioned above (terminal or fastboot) and it was successful
then you have a recovery on your phone, boot into it and install your rom of choice, of course some roms will need custom mtd partitions whcih can be managed through blackrose, but for now just flash one within your parameters so you can begin
happy flashing!

demkantor said:
i dont think you are missing anything just boot into recovery and flash your rom.
dont use rom manager to flash recovery, dont use 4ext recovery control app.
if you used one of the two methods you mentioned above (terminal or fastboot) and it was successful
then you have a recovery on your phone, boot into it and install your rom of choice, of course some roms will need custom mtd partitions whcih can be managed through blackrose, but for now just flash one within your parameters so you can begin
happy flashing!
Click to expand...
Click to collapse
I really dont know what is happening. Still I can't go to recovery. Btw, does locking/unlocking bootloader affects in flashing custom recovery. But I think I already unlock mine, how would I know if unlock or lock my bootloader?

... Yea very much so, and I believe I misread you first post, I take it you didn't root your phone properly. First of all check what boot loader you have by booting into your hboot. There are a few ways to get there but for now just power off and then power back on holding your volume down key, here will be a screen with some words and androids skateboarding, write down everything from that screen here.
Sent from my Nexus 7 using xda premium

demkantor said:
... Yea very much so, and I believe I misread you first post, I take it you didn't root your phone properly. First of all check what boot loader you have by booting into your hboot. There are a few ways to get there but for now just power off and then power back on holding your volume down key, here will be a screen with some words and androids skateboarding, write down everything from that screen here.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
*BlackRose - Made by Lecabel(dla5244) *
jb-260/10/166
NEXUSONE PVT ENG S-OFF
HBOOT-7.35.5017 (PB9911000)
MICROP-0b15
TOUCH PANEL-SYNT0103
RADIO-5.08.00.04
Apr 21 2012, 04:53:16
HBOOT
VOL UP
VOL DOWN
TRACKBALL
FASTBOOT
RECOVERY - when I select this, I will be stuck at android logo with !
REBOOT
POWERDOWN

Well you are better off than just an unlocked bootloader, you have black rose installed which essentially is an engineering bootloader that allows custom mtd partitions.
Right now you have 260 for system, 10 cache and 166 for data, this should be fine for any chance ROM but may consider changing later on depending on ROM you want to run
For now you need these things
ROM of choice and anything else the dev thinks you need (gapps etc)
Put that on root of sdcard, make sure it is partitioned to fat32 and not in any folder
Also need to have fastboot working, I'm assuming you are using windows.
You will need fastboot.exe usually found in the android SDK and elsewhere.
Proper drivers installed, and although not necessary its nice to add fastboot and adb into path in environmental variables.
If all this is done great. If not go do it now.
Now get recovery, let's say amonra. Open cmd in the same directory as the recovery image, make sure you name it recovery.img (if you don't change command to fit)
Boot into hboot, and put phone into fastboot mode and connect to computer
In cmd type
fastboot devices
If you see your serial # good, if not then you missed something earlier
Now type
fastboot flash recovery recovery.img
If the output say done then you are good, select recovery from within hboot menu and reboot there, once in recovery do a nandrpoid backup (good practice) then do a full wipe, (yes wipe everything you possibly can - side note fastboot -w is cleaner for future reference) then flash ROM, gapps, whatever you need
Let me know if you get stuck
Sent from my Nexus 7 using xda premium

demkantor said:
Well you are better off than just an unlocked bootloader, you have black rose installed which essentially is an engineering bootloader that allows custom mtd partitions.
Right now you have 260 for system, 10 cache and 166 for data, this should be fine for any chance ROM but may consider changing later on depending on ROM you want to run
For now you need these things
ROM of choice and anything else the dev thinks you need (gapps etc)
Put that on root of sdcard, make sure it is partitioned to fat32 and not in any folder
Also need to have fastboot working, I'm assuming you are using windows.
You will need fastboot.exe usually found in the android SDK and elsewhere.
Proper drivers installed, and although not necessary its nice to add fastboot and adb into path in environmental variables.
If all this is done great. If not go do it now.
Now get recovery, let's say amonra. Open cmd in the same directory as the recovery image, make sure you name it recovery.img (if you don't change command to fit)
Boot into hboot, and put phone into fastboot mode and connect to computer
In cmd type
fastboot devices
If you see your serial # good, if not then you missed something earlier
Now type
fastboot flash recovery recovery.img
If the output say done then you are good, select recovery from within hboot menu and reboot there, once in recovery do a nandrpoid backup (good practice) then do a full wipe, (yes wipe everything you possibly can - side note fastboot -w is cleaner for future reference) then flash ROM, gapps, whatever you need
Let me know if you get stuck
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Finally.. Thank you so much.. I can now go to custom recovery.. Now I will backup and wipe then flash.. :good::good: Will press THANK button now, maybe a million times.. hehe

No problem, fastboot is a key skill to learn with any android device that supports it
Here is a guide I made a while back
http://forum.xda-developers.com/showthread.php?p=27796375
Its meant for a different phone but the basics are the same, I would suggest to read up on it a bit and you will have a much easier android experience
Happy flashing!
Sent from my Nexus 7 using xda premium

demkantor said:
No problem, fastboot is a key skill to learn with any android device that supports it
Here is a guide I made a while back
http://forum.xda-developers.com/showthread.php?p=27796375
Its meant for a different phone but the basics are the same, I would suggest to read up on it a bit and you will have a much easier android experience
Happy flashing!
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Okay. I will try to read my left time for this day. Thanks a lot..

demkantor said:
No problem, fastboot is a key skill to learn with any android device that supports it
Here is a guide I made a while back
http://forum.xda-developers.com/showthread.php?p=27796375
Its meant for a different phone but the basics are the same, I would suggest to read up on it a bit and you will have a much easier android experience
Happy flashing!
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Hi, I have a follow up question regarding sd partition, I will just raise my question here than making another thread. I have 4GB SD card but I forgot how much ext partition I made before but my total space in my SD card is 3.21GB. I want to partition my sd card again and increase it maybe to 1gb. If I will increase my partition should I flash again my ROM (VJ CM10.1 | Jelly Bean 4.2.2 - v6.0) and execute a2sd command in terminal emulator? or it's okay to partition my sd card without flashing the ROM again?

You can partition SD without fllashing rom again
On this phone the easiest way to check what you have is in 4ext recovery under info, or if you have a Linux distro run gparted
You could also run df through adb shell or if not by a computer, open a terminal and type
such
df
But being it sounds like you want too repartition I would just flash 4ext recovery and do everything from there
Sent from my Nexus One using xda app-developers app

demkantor said:
You can partition SD without fllashing rom again
On this phone the easiest way to check what you have is in 4ext recovery under info, or if you have a Linux distro run gparted
You could also run df through adb shell or if not by a computer, open a terminal and type
such
df
But being it sounds like you want too repartition I would just flash 4ext recovery and do everything from there
Sent from my Nexus One using xda app-developers app
Click to expand...
Click to collapse
I think a2sd is not working in my device. When I tried to install a2sd or reinstall it there was a line written in termenal emulator (/dev/block/mmcblkop2) I think that the reason why I easily having internal memory full, even I already partition my sd card, with 1024 ext partition using 4ext touch recovery. Check my screenshot in titanium backup showing my memory status..
Sent from my Nexus One using xda app-developers app

It looks like its working, just need to move what you want from data to ext partition shown by titanium as a2sd. What ROM are you running? It does support having apps on ext correct?
Sent from my Nexus 7 using xda premium

demkantor said:
It looks like its working, just need to move what you want from data to ext partition shown by titanium as a2sd. What ROM are you running? It does support having apps on ext correct?
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thanks for the reply. Im using VJ CM10.1 | JB 4.2.2 V 6.0. How to move data to ext partition? I will post screenshot in my internal storage too.
Sent from my Nexus One using xda app-developers app

if the rom doesnt have the feature built in then use an app from the market to do it, ive never used this rom so i dont know what options it has
also if you want an easy to see graph style layout of you partitions download Disk Usage from the market, you can easily see what is stored in which partition

demkantor said:
if the rom doesnt have the feature built in then use an app from the market to do it, ive never used this rom so i dont know what options it has
also if you want an easy to see graph style layout of you partitions download Disk Usage from the market, you can easily see what is stored in which partition
Click to expand...
Click to collapse
Thanks. Btw what rom are you using?
Sent from my Nexus One using xda app-developers app

Cyanmobile
Yes it has apps2ext built in, go into settings to activate
Sent from my Nexus One using xda app-developers app

demkantor said:
Cyanmobile
Yes it has apps2ext built in, go into settings to activate
Sent from my Nexus One using xda app-developers app
Click to expand...
Click to collapse
Thanks, Btw, what if I wanted to change my ROM, what procedure should I follow? Should I go back to Stock ROM before flashing a new ROM?

Nope, boot to recovery, do a nandroid backup, wipe everything, wipe twice even, hell fastboot wipe (most issues people have when flashing a new ROM is not clean wiping)
Then flash ROM like you did first time, and being you have a huge partition for system right now I would suggest to shrink it a bit first, maybe around 170 if your going to use cyan mobile. If you do this you propably should be prepared to flash recovery again as well
Sent from my Nexus 7 using xda premium

demkantor said:
Nope, boot to recovery, do a nandroid backup, wipe everything, wipe twice even, hell fastboot wipe (most issues people have when flashing a new ROM is not clean wiping)
Then flash ROM like you did first time, and being you have a huge partition for system right now I would suggest to shrink it a bit first, maybe around 170 if your going to use cyan mobile. If you do this you propably should be prepared to flash recovery again as well
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thanks for the quick reply. So, you're saying that I should partition my system first and flash recovery just like what you taught me in our previous posts? Just to be sure and making all things clear to my self.