Database Develop

Just can't install any ROM

hi,
after some theme ****ed up my CM 4.2.15.1 installation I tried to to a fresh new install, but it doesn't seem to work.
First of all some information that might be useful, dunno:
DREA110 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-1.22.12.29
I downgraded to RC7 (Kila_uk-user 1.0 TC5 RC7 112931 ota-rel-keys) again and did the telnet-thingy to install the recovery image, which works fine - but here's where the problem starts.
I wanted to install DRC83_base_defanged (as the CMWiki says) from the recovery mode but it simply says "Installation aborted".
Also wiping, recovery etc. doesn't work at all. No matter what update.zip I want to install, it's the same every time. I googled for like 5 hours now and can't find any solution, please don't flame me if I was simply too stupid for proper searching, trust me I did ^^
The same thing happens to me when using the CM recovery and the RA one. Am I right that this can't be because I have no root? Because if I can install the recovery images, I should have root, right? please help me I'm getting crazy, trying to make it work for the whole day now
thanks in advance and sorry for my bad english and newbiness ^^
mistkäfer

mistkäfer said:
hi,
after some theme ****ed up my CM 4.2.15.1 installation I tried to to a fresh new install, but it doesn't seem to work.
First of all some information that might be useful, dunno:
DREA110 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-1.22.12.29
I downgraded to RC7 (Kila_uk-user 1.0 TC5 RC7 112931 ota-rel-keys) again and did the telnet-thingy to install the recovery image, which works fine - but here's where the problem starts.
I wanted to install DRC83_base_defanged (as the CMWiki says) from the recovery mode but it simply says "Installation aborted".
Also wiping, recovery etc. doesn't work at all. No matter what update.zip I want to install, it's the same every time. I googled for like 5 hours now and can't find any solution, please don't flame me if I was simply too stupid for proper searching, trust me I did ^^
The same thing happens to me when using the CM recovery and the RA one. Am I right that this can't be because I have no root? Because if I can install the recovery images, I should have root, right? please help me I'm getting crazy, trying to make it work for the whole day now
thanks in advance and sorry for my bad english and newbiness ^^
mistkäfer
Click to expand...
Click to collapse
the only thing I can think of is one of your partitions has become corrupt
its happened to me before ( well truth be known I did a flash_image system /sdacard/nandriod....system.img , don't do that )
here is how to confirm
from RA Recovery go to console, and type
mount /system
then
mount /data
and then
mount /cache
if any of those complain, then we are closer to fixing it
you need to erase the problem partition with fastboot
fastboot is part of the android sdk, you can hopefully find install instructions somewhere on this forum or google.
once you have fastboot setup, you need to get into fastboot mode on the phone, do this by holding the camera button when turning your phone on, you should see skateboards
hook your phone up to pc via usb
select fastboot on the phone ( fastboot should be in a red block )
then on pc
fastboot erase < the broken partition >
e.g. if system failed to mount
fastboot erase system
Hope this helps

ok the cache seems to be broken, now i just have to get familiar with the android sdk and how that fastboot stuff works

http://forum.xda-developers.com/showthread.php?p=3083753
will help
and you can get to fastboot a little faster,
use back + power
but camera + power
and then back will work

Stuck G1 - but Not your typical

Okay.
I dont think my problem is typical, and Ive searched google and xda for answers. Some situations seem similar, but none exact.
Here is the story:
G1 was running wifi tether and on charge. No bumps or bruises, just sitting by itself. The tether stopped working, so I went over to look at the G1 and the phone was frozen. Display was lit up and working, just frozen. Had to pop the battery out to shut it down.
After powering back up, the sits at the splash screen indefinitely.
I can go into fastboot but I can NOT get into recovery.
I have going into fastboot usb mode and:
1) flash a recovery image (works)
2) flash a nandroid backup (works)
3) flash rc29 (see below)
4) flash hboot (always fails)
What I mean by works is the flash indicates it was good, but there is no change in functionality of the phone. Hboot gives me device errors.
Dream PVT 32B ENG S-OFF
HBOOT-1.33.2005 (DREA10000)
CPLD-4
Radio-2.22.19.26I
Apr 20 2009,15:30:43
I have also flashed a different splash image - and even though it says it succeeded the image doesnt change.
When I attempt to flash the original RC29 using the SD card mode or fastboot mode it indicated I need HBOOT 1.33.2004. 2004 *will not install* --- it gives an error (I think something to the effect of wrong device.)
I know my way around fastboot and adb, but I dont know what "hboot mode" is used for. For grins, I tried flashing the recovery in hboot mode and it says "waiting on device" forever.
It seems almost like this is a hardware problem that is presenting itself as a software issue.
Also - *sometime* when I hold home/power to try to boot into recover the phone will connect to ADB (listed in adb devices) but no commands seem to work.
Im an a loss. 10+ hours trying to fix this thing...
Any ideas?
Thanks.
Blade

Blade10 said:
When I attempt to flash the original RC29 using the SD card mode or fastboot mode it indicated I need HBOOT 1.33.2004. 2004 *will not install* --- it gives an error (I think something to the effect of wrong device.)
Click to expand...
Click to collapse
Tried with a goldcard?

No. Maybe I didnt read enough, but I thought the goldcard required a WM Device? All my machines are win xp, obvously I can use a live cd to boot linux.
BTW, the SDcard method of installing dream.nbh (RC29) gives me a checksum error, while fastboot finishes but doesnt make a difference. Yes, tried different SD cards and ran checksum after coipying to the card - checksum is correct.
Any other ideas, or maybe some links that make a goldcard easy?
Thanks,
Blade

Bricked? Can't get out of bootloader & "not allow" problem

I dug too greedily and too deep, and now I'm afraid my phone is bricked. Any help would mean the world to me!
Summarized: phone will only boot into bootloader, and not further. Installing images does not work because of a "not allow" error message.
Current device situation
Works: boot into bootloader with camera/power, boot into standard google recovery with home/power
Does not work: Boot to full OS. Powering the phone just starts the bootloader. Fastboot/ADB
Device info:
Dutch T-Mobile G1, 1.5 years old.
Bootloader screen:
DREA110 PVT 32B
HBOOT-0.95.0000
CPLD-5
RADIO-1.22.12.29
Sep 2 2008
Serial0
Installed ROM
No clue! See below.
What I did before the brick
I had a fully working, rooted, installation of OpenEclair 1.2.0.1. SPL (forgot, by this time, which one), newest radio, Cyanogen's recovery, and all that.
OpenEclair started refusing to boot after batteries had been drained once. Needing phone immediately, I hastily installed dream_devphone_userdebug-ota-14721.zip from my SD.
Noticed that phone was not rooted anymore. Fatal mistake.
Wanted to re-root. So, followed (to the letter) all steps under "Downgrade" on Cyanogen's Cyanogenmod full update guide for the g1/dream firmware. I.e. tried to install RC7 via DREAIMG.nbh (rightly spelled)
Rebooted.
What then happened
G1 finished installing RC7, then I rebooted. On subsequent boots, it would directly go to the bootloader and not the OS. I think somehow the install corrupted.
What I've tried since the brick
Searching forums: Could not find situations similar to mine with any answers.
ADB/Fastboot: I've tried both of these. For ADB, it seems you need to be able to get into full Android mode, so that's a no. Fastboot does not seem to be enabled on this bootloader (no mention of it to be found, logically, since it's a stock bootloader). In windows, USB device is not recognized, throws an error and allows no installation of drivers.
Nandroid: Useless without working ADB/fastboot? I do have several backups of old working installs.
Images: Tried if re-downloaded RC7 or RC29 worked. No dice. Gives 0028022 "not allow"
Installing dream_devphone_userdebug-ota-14721.zip using the recovery mode. Gives no signature/verification filed errors.
Goldcard: Have no winphone, or access to one. Terminal emulator method does not work without working Android OS...
I'm at a loss what to try anymore. Help much appreciated!

Sigh .. your mistake was flashing an nbh in the firstplace..
The ota image is for the android dev phone and had root access over adb.. there are even guides as to how to reinstall a custom recovery from the ota.
Also its most likely that you had danger or another fastboot enabled spl that could have been used to get yourself out of any firmware issue.
However now you have a half installed stock T-Mobile system.. and will need to reflash a nbh.
This will either require a goldcard (see if you can get your Linux PC to read the sd cards cid, or find someone in your area to make one for you)
Or a Dutch T-Mobile rru/nbh not sure I've heard of such a thing in the wild.

Need help, HTC DREAM

I was trying to do the post 911 rogers root on my htc phone, i got to the point where I Amon_ra's 1.7 recovery booted but then the home button wouldn't respone which is weird as it was used to boot into recovery.
after this I researched a bit and found that an eailer version of Amon_ra's recovery used the "Send" key instead of home, flashed that on and booted into it however it still asked me for "Home" to comfirm.
I then downloaded clockworks recovery and flashed it onto my phone but now the phone is stuck(waited 3 hours) at the ROGERS boot screen. I can boot into fastboot and my computer sees it as:
"list of device
HLXXXXXXXXXXXXXX fastboot"
x=numbers/letters
but whenever I try to do a fastboot command i get an error stating that remote is not allowed.
I am worried that this phone super derpped on me

What radio and SPL do you have? It will say in fastboot mode on the device. Also, can you still get into the ROM?

thanks for the reply the spl and radio are:
spl: 1.33.0010(?)
radio: 3.22.26.17
heres what it all says
"DREAM PVT 32B SHIP S-On d
HBOOT-1.33.0010 (DREA21000)
CPLD-4
RADIO-3.22.26.17
Jun 2 2009, 21:33:16"
no I can't get into the system rom, it is stuck at the bootspalsh screen.

You have a 3.xx (EBI1) radio but clockwork recovery only works with 2.xx (EBI0) radios.
I don't know if this will work but give it a shot:
1) Download: orange-1.58.73.2.nbh (MD5: aca4dee0c1ece7e9773f2ecbdfbba7c0) (mirror)
2) enter fastboot and run 'fastboot flash nbh orange-1.58.73.2.nbh'
3) wait for the entire nbh to flash
4) boot into the bootloader again (it will be an engineering SPL 1.42.2000)
5) You can now re-flash the radio/hboot/recovery via fastboot that you wish to have installed.
Click to expand...
Click to collapse

I downloaded the NBH file but I can't send the file to the phone it gives me this
nbh orange-1.58.73.2.nbh
sending 'nbh' (88683 KB)... FAILED (remote: not allow)
finished. total time: 0.005s
Click to expand...
Click to collapse
EDIT*: After following this guide http://wiki.cyanogenmod.com/index.php?title=Full_Downgrade_Guide_-_HTC_Dream I can now boot past the Rogers screen but its followed by a caution triangle. Recovery doesn't work "home"+power.
EDIT**: Further inspection i can get into recovery via atl+L at the triangle screen the load then rogers rom so I can make calls. The "home button" doesn't work so i can't flash or do anything in recovery mode as it ask for the "home" key to comfirm. Also home key is useless in normal boot(doesn't return me to home) which is wierd as my phone has never been dropped or water damaged, not even a scratch. Another thing since home key is now defucnt I can't reboot my phone or it will give me the error splash screen

Thats great news that you can get into recovery. You should try to get an unlocked spl before you do anything else. It looks like the home button not working is a hardware problem. If you feel comfortable doing it you could open the device because something might just not be contacting properly. You can find a service manual if you search for it.
You could try to use flash_image to flash img files in recovery through adb without the need for the home button.
http://wiki.cyanogenmod.com/index.php?title=Flash_image
Be sure to update to the latest radio before flashing your spl. This is very important!!!

[Q] HTC Dream update to Android2 (wow this is hard)

I've been trying for a long time reading all the guides following all instructions and I think I finally see how all the pieces work together, but for some reason, I get completely stuck by fastboot.
Here's what it says when I hold back and power:
DREA100 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-2.22.23.02
Sep 2 2008
Serial 0
this guide: http://wiki.cyanogenmod.com/index.php?title=Dream:DangerSPL
Says to root the G1 (based on the radio version, I think that's been done).
Next I'm supposed to install Amon Ra recovery
From this guide: http://forum.xda-developers.com/showthread.php?t=566669
It says that if I have the engineering SPL (which I seem to based on the numbers), I should be able to follow these directions:
Copy recovery-RA-dream-v1.7.0.img to a location where fastboot can find it.
Boot your G1 into fastboot mode (boot while holding BACK)
Connect your G1 via usb to your pc/mac/...
fastboot devices (to make sure that fastboot "sees" your device)
fastboot flash recovery recovery-RA-dream-v1.7.0.img
I've copied the img to somewhere on the phone (I forget where) and I've done the second and third steps, but fastboot never sees the device even though ADB can. What now?
Copy recovery-RA-dream-v1.7.0.img to a location where fastboot can find it.
Boot your G1 into fastboot mode (boot while holding BACK)
Connect your G1 via usb to your pc/mac/...
fastboot devices (to make sure that fastboot "sees" your device)
fastboot flash recovery recovery-RA-dream-v1.7.0.img

Something must have happened at some point because now the phone won't boot unless I do it into safe mode. This is pretty frustrating. All these guides and none work for me.

What is the status at this point? Are you able to get into Recovery, fastboot, etc...?

When you boot normally and you plug your phone in fastbooted, do you hear a sound/any indication from Windows that it's detected in any way at all? Have you checked device manager?
You need not bother with the further commands unless 'fastboot devices' picks up the phone in command prompt. Fastboot didn't find mine straight away either. I had to change to HTC Bootloader driver when connected to USB in bootloader -which shouldn't effect ADB or anything else as the phone is booted differently and loads as a different device to have ADB operational, hence why I believe you generally can't mix fastboot/adb ccommands.

BeenAndroidized said:
What is the status at this point? Are you able to get into Recovery, fastboot, etc...?
Click to expand...
Click to collapse
Sorry for the late reply. I don't often get a chance to work on the phone. I can boot to the four color boot screen that shows the hboot and radio information as follows:
DREA100 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-2.22.23.02
Sep 2 2008
Serial 0
For a second it flashes to a different screen and then says "no image" or something then goes back to the multi-color screen. When I plug the device into the computer during the multi-color screen, nothing happens. The computer makes no noises to indicate it knows a USB device is there.
If I exit colored screen mode (whatever it's called), and leave the cable plugged in, Windows says there's something attached but it malfunctioned. Both the phone and Windows respond when I plug in USB at any time other than the multicolor mode.

I'm trying to solve the "g1 looks like usb mass storage" issue and it's not working. If I follow directions to boot to fasboot mode first, it only goes to the four color screen and the USB isn't recognized. If I do it while it's on normally, Windows sees it, but won't let me update the drivers.
I tried picking them manually, but that's not working. Wait... all of a sudden I see HTC Android listed under "Disk Drives" I don't know what happened, but it seems to have worked (I just updated the GOOGLE USB drivers using the SDK third party installer so maybe that was it). Let me try from scratch again.

Still nothing. By the way, I've never been able to boot to Fastboot mode. I've never seen skateboarders. Do you install that?

Ok, I've tried a series of other guides online. I've spent the last 4 or 5 hours on this trying to root and then install various other things. Using three different rooting techniques, I still can't get super user access when using terminal emulator.
What is this? Some kind of practical joke?

Making progress... I think
I followed the directions here:
http://wiki.cyanogenmod.com/index.php?title=HTC_Dream:_Rooting
Which didn't use to make sense, but now are helping. I downgraded the Firmware per instructions, but used the SuperOneClickv1.7-ShortFuse to root the phone instead (which worked splendidly). Now I FINALLY can get root using ADB though installing Amon Ra recovery isn't going too smoothly yet.
Edit, spoke too soon: I didn't see anything in the SDCARD folder until I disconnected the cable and reconnected it. I was able to use the flash_image recovery recovery.img file now (recovery.img is a renamed amon ra cyan image).

After installing Amon Ra, upgrading the SPL to Danger was easy to do in recovery mode as was installing Cyanogen. I also installed a different mod (biffmod), but didn't like it.
Now everything seems to work other than clockwordmod still won't install (but I don't really care since I can do everything fine with Amon Ra if I move downloads into the root folder).
I hope this thread helps others!