Database Develop

UNroot issue

Hi all
was unrooting my g1 to return for warranty repair but hav e hit a sng
am stuck on rainbow screen trying to flash dreaimg.nbh
message says
loading.....
checking......
0028002
not allow
and then flicks back mto rainbow
have searched a fair bit but i cant find what this error means or what to do
please help
cheers
j
edit.. nevermind - i am an idiot - was using us version (RC29) of dreaimg - worked fine with uk (RC7) - apologies for unnecessary thread

I have the same issue, tried to downgrade so that I can get data back on rogers network, now stuck at rainbow:
DREA210 PVT 32B RUUNBH
HBOOT-0.95.0000
CPLD-4
RADIO-1.22.12.29
Sep 2 2008
Serial0
When I turn on my Dream (now nightmare) it automatically goes to what is supposed to be fastboot, but I can't access fastboot, computer doesn't recognize it, and I can't flash any NBH files. I've tried deleting the drivers using USBDeview, different computers, pressing the Back button on the device to try to get Fastboot, but nothing works.
Only the Rogers NBH files get past the:
00028002
Not Allow
error, but then they stop with the following:
DREAIMG.nbh - FAIL
RADIO_V2 -
BOOTLOADER -
SPLASH1 -
RECOVERY -
BOOT -
SYSTEM -
USERDATA
Update Terminate
Update Fail
I am also missing the recovery image, when I try to hold Home+Pwr it still goes to fastboot & the 3 finger saluat (call+menu+pwr) doesn't work.
I really just need to get fastboot working again so that I can get everything running again. Anyone with any advice?

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

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.

[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!

[Q] Stuck in HBOOT/FASTBOOT Menu

Hey guys,
So randomly my phone decided to just turn off (it was just idle on the home screen) and when I booted it back up it was in the Fastboot Menu.
I've tried reboot and even factory reset but neither work they just bring the phone right back to this when I turn it on anyone got any tips for me I'm hoping there's a really simple solution I have naively overlooked.
The screen says
***LOCKED*****
***Security Warning*******
VIVO PVT SHIP S-ON RL
HBOOT-2.03.0000
RADIO-3831.19.00.19_M
eMMC-boot
A few months back I used a RUU to manually update to ICS and everything went fine and I had been running it fine for a long time so I'm not sure if that impacted on this in any way at all.
Anyway since this happened I've tried the old turning it off and on, battery out for an hour, sim out/sd out etc
Also the following:
I've tried running the RUU again but I get error 170 as it gets stuck at "waiting for bootloader" after it reboots the phone at the start of the process
(Tried in all my USB ports, reinstalling drivers/HTC Sync, using original cable)
I tried flashing from my SD card, it reads the zip and asks would you like to update but after I click yes it goes for a few seconds and then says "Partition Update Failed" and prompts me to reboot. (Tried multiple sd's)
I tried to unlock the phone using the HTCDev unlock, however once I get my token and use it to get to the unlock screen on the phone I am unable to select yes my phone simply does not acknowledge the option when I press the power button it instead vibrates a few times and then inevitably I end up selecting the No option after much frustration.
I should probably mention that fastboot lists my device under devices but adb does not.
I would have tried making a goldcard but I currently cannot obtain my CID through adb nor by using readcid.exe with my laptop card reader.
So if anyone could help me out that would be much appreciated as I don't have a warranty on this or anything and HTC support were of exceedingly little help.

Nick960 said:
Hey guys,
So randomly my phone decided to just turn off (it was just idle on the home screen) and when I booted it back up it was in the Fastboot Menu.
I've tried reboot and even factory reset but neither work they just bring the phone right back to this when I turn it on anyone got any tips for me I'm hoping there's a really simple solution I have naively overlooked.
The screen says
***LOCKED*****
***Security Warning*******
VIVO PVT SHIP S-ON RL
HBOOT-2.03.0000
RADIO-3831.19.00.19_M
eMMC-boot
A few months back I used a RUU to manually update to ICS and everything went fine and I had been running it fine for a long time so I'm not sure if that impacted on this in any way at all.
Anyway since this happened I've tried the old turning it off and on, battery out for an hour, sim out/sd out etc
Also the following:
I've tried running the RUU again but I get error 170 as it gets stuck at "waiting for bootloader" after it reboots the phone at the start of the process
(Tried in all my USB ports, reinstalling drivers/HTC Sync, using original cable)
I tried flashing from my SD card, it reads the zip and asks would you like to update but after I click yes it goes for a few seconds and then says "Partition Update Failed" and prompts me to reboot. (Tried multiple sd's)
I tried to unlock the phone using the HTCDev unlock, however once I get my token and use it to get to the unlock screen on the phone I am unable to select yes my phone simply does not acknowledge the option when I press the power button it instead vibrates a few times and then inevitably I end up selecting the No option after much frustration.
I should probably mention that fastboot lists my device under devices but adb does not.
I would have tried making a goldcard but I currently cannot obtain my CID through adb nor by using readcid.exe with my laptop card reader.
So if anyone could help me out that would be much appreciated as I don't have a warranty on this or anything and HTC support were of exceedingly little help.
Click to expand...
Click to collapse
Try to use search.
For example in this thread were this:
Originally Posted by Addiso View Post
Did you get the HTC token again that you used to unlock the first time? If not, not go back into htcdev.com and follow all of directions. After you have it all in fastboot type in
Fastboot flash unlocktoken unlock_code.bin
http://forum.xda-developers.com/showthread.php?t=2236527

egorlins said:
Try to use search.
For example in this thread were this:
Originally Posted by Addiso View Post
Did you get the HTC token again that you used to unlock the first time? If not, not go back into htcdev.com and follow all of directions. After you have it all in fastboot type in
Fastboot flash unlocktoken unlock_code.bin
http://forum.xda-developers.com/showthread.php?t=2236527
Click to expand...
Click to collapse
Yeah I had a look at that before, I hadn't unlocked my phone before with htcdev but even then when I did try I was able to get my token and run the command and everything perfectly fine and even it takes me to the "Would you like to unlock your phone?" screen on my phone but I am unable to select the yes option and complete the final step which is the frustrating part.

Nick960 said:
Hey guys,
So randomly my phone decided to just turn off (it was just idle on the home screen) and when I booted it back up it was in the Fastboot Menu.
I've tried reboot and even factory reset but neither work they just bring the phone right back to this when I turn it on anyone got any tips for me I'm hoping there's a really simple solution I have naively overlooked.
The screen says
***LOCKED*****
***Security Warning*******
VIVO PVT SHIP S-ON RL
HBOOT-2.03.0000
RADIO-3831.19.00.19_M
eMMC-boot
A few months back I used a RUU to manually update to ICS and everything went fine and I had been running it fine for a long time so I'm not sure if that impacted on this in any way at all.
Anyway since this happened I've tried the old turning it off and on, battery out for an hour, sim out/sd out etc
Also the following:
I've tried running the RUU again but I get error 170 as it gets stuck at "waiting for bootloader" after it reboots the phone at the start of the process
(Tried in all my USB ports, reinstalling drivers/HTC Sync, using original cable)
I tried flashing from my SD card, it reads the zip and asks would you like to update but after I click yes it goes for a few seconds and then says "Partition Update Failed" and prompts me to reboot. (Tried multiple sd's)
I tried to unlock the phone using the HTCDev unlock, however once I get my token and use it to get to the unlock screen on the phone I am unable to select yes my phone simply does not acknowledge the option when I press the power button it instead vibrates a few times and then inevitably I end up selecting the No option after much frustration.
I should probably mention that fastboot lists my device under devices but adb does not.
I would have tried making a goldcard but I currently cannot obtain my CID through adb nor by using readcid.exe with my laptop card reader.
So if anyone could help me out that would be much appreciated as I don't have a warranty on this or anything and HTC support were of exceedingly little help.
Click to expand...
Click to collapse
U will need to Downgrade your device from ICS to GB or anything else ...At times it can be Windows 8 ,8.1 issue also ...The driver are still messed up search the forum u will find working way to get driver's work ..Error(170) which means your phone is blank to flash image to boot from or Os for starters..Can u boot in bootloader (Y) then simply working your way via CMD (windows 7 if u can access). It says RELOCKED on your device(Security warning can you paste a screen snap) .
1:- Flash a recovery(if yes skip this)
2:- boot into boot bloader (install any rom via recovery)
3:- flash boot.img manually (fastboot flash boot boot.img)
If it does not work REunlock ur device via htcdev.com
If you were trying to downgrade is HBoot Version (the same issue might happen)
Take stuff's real slow (make sure u do have correct driver installed on your pc )