Forgive me if this has been answered somewhere but I have searched and have given up out of frustration. I just downgraded from RC30 to RC29 and, no matter what I do, it won't show up under my computer or anything.
I've uninstalled the drivers through device manager, tried updating the drivers various times and used USBDeview to uninstall. After every uninstall, when I plug my phone back in via USB, windows will automatically install drivers for me. I check under device manager, and the only new device is a non-descript USB Mass Storage device.
Under USBDeview, I only found and uninstalled one driver with HTC Android in the description instead of the recommended three. I have the SDK and have tried various drivers, possibly the same. Nothing I do seems to work. I just want to get ADB running so I can register my phone over wifi.
Thank you in advance for any help, I know that XDA always pulls through and is a great forum and community.
Woah slow down, the phone should be detected as a Mass storage assuming you have a SD in the phone.What are you using Fastboot?
Fastboot needs Haykuro SPL or HARD SPL.
It's not really being detected at all, as in nothing appears in My Computer in Windows Explorer. Just the hard drives and cd-rom drive. I have a 4gb SD class 2. Works fine when I plug it into my SD card reader (Micro SD to SD adapter).
I have done nothing to my phone besides downgrading and am largely unfamiliar with SPL's but I'm fairly certain you have to install them yourself?
You have to install them yourself...if you are going to do it, INSTALL RADIO FIRST AND THEN THE SPL, otherwise you are going to brick you phone.
So are you recommending me to use fastboot to detect my phone as a Mass Storage device? but before using fastboot, to install a radio and then an SPL?
If I remember correctly didn't RC29 have that nasty thing where you had to go into settings to mount your sdcard? I may be completely wrong but...
That may be true. I've read a lot of posts of users saying they had to check USB Debug mode or something.
Excuse my noobishness, but what is the difference between the RC# releases and HTC's Android ADP 1.5 image builds? Would it be possible to load JesusFreke's 1.5 onto my phone since it includes the option to skip the registration screen completely, allowing me to register over wifi at a later time?
I'm completely new to the whole android experience and really only have experience in PSP's, iPhones and a bit of WinMo.
crzyaznkdxd said:
That may be true. I've read a lot of posts of users saying they had to check USB Debug mode or something.
Excuse my noobishness, but what is the difference between the RC# releases and HTC's Android ADP 1.5 image builds? Would it be possible to load JesusFreke's 1.5 onto my phone since it includes the option to skip the registration screen completely, allowing me to register over wifi at a later time?
I'm completely new to the whole android experience and really only have experience in PSP's, iPhones and a bit of WinMo.
Click to expand...
Click to collapse
The RC# (this also includes CRB# & DRC#) are the shipping versions of the system for updates. The Htc ADP releases were made for the Android Developer phones, or the phones you buy through Google that come unlocked (and rooted?).
So one is a consumer version/build of Android and one is for developers/people who are willing to pay more for an unsubsidized phone? It seems like I'd want to ultimately want to end up with the ADP release anyways so is there a way to install it through SD card?
Related
hi
I tried to upgrade my pda2k to 2005, but I get hang
then when I tried again it show this message
http://www.600kb.com/uploads/20aac64ad6.jpg
can i get help please
sarab
Strategies for dealing with radio ROM update 114 errors
I had this problem last week and recovered from it. At first it looked pretty bad, nothing seemed to work. I looked the Internet up and down and in most forums, including this one, people agreed that nothing could be done about error 114, the mainboard of the BA needed replacement, etc.
When I finally did fully recover from this situation, it was from a combination of measures that I took and as I don't really know which one actually did the trick, I'll try to describe all of them even though not all will probably apply to others. Another problem is that I probably won't be able to remember them all, but anyway, here goes:
1) I downloaded the latest full official ROM update from site of the carrier this phone was branded for, in this case T-Mobile. It included a radio ROM, albeit version 1.13.0, not 1.15.0 which is the one I had been trying to flash. I decided it would be best to go back to that official version first.
2) I had been trying to do the radio ROM upgrade from a Macintosh (OSX) under Virtual PC. I have since done several ROM installations (without the radio part) from the Mac/VPC which worked fine, but since people had observed that radio ROM updates seem to be more sensitive than fiddling with the normal ROM, I decided to fire up my "real" PC, which runs WIndows XP, SP2, with Active Sync 4.5.
3) As others had suggested, I made sure that I had my cradle connected directly to a USB port on the computer; before I had been trying to go trough a hub. I also made sure the cradle was connected to the power adapter.
4) I had unlocked my device before to work with a non-T-mobile SIM card, but since I wasn't sure wether or not SIM/Net lock problems might still interfere with radio upgrades, I took my SIM card out of the unit, as well as the SD card -- trying to eliminate as many potential sources of screw-up as possible.
5) I think I tried to set my BA into as much of a defined state as I could by hard-resetting it and THEN invoking boot loader mode. I don't remember whether or not this was possible as the device was not reacting much to anything at the time.
6) On the Windows PC, I opened Active Sync, then went to Connection Settings and explicitly disabled the USB connection. I then quit Active Sync and invoked the Windows task manager (Ctrl-Alt-Del) to check that no other processes were running. Trying to cut out interference as much as poosible ...
7) I then proceeded to flash the official ROM version, which went flawlessly including the Radio ROM, took less than fifteen minutes in all. To be honest, I don't remember which ROM upgrade utility (BaUpgradeUt/MaUpgradeUt_noID) I used ... sorry. I know I tried whatever was included with the T-Mobile download first.
After that, I verified that everything was working again, then immediately flashed Radio ROM 1.15.0 as I had originally intended. This time it went uneventfully.
Hope some of this helps, I know how frustrated you must be at this point.
Good luck!
thanks a lot
i'm going to follow your instruction today.
regards to all
[email protected] said:
thanks a lot i'm going to follow your instruction today.
Click to expand...
Click to collapse
So did you have any luck?
Hey there everyone, I am pretty new to this forum so I must apologize for throwing you all into the deep end. I recently purchased an o2 XDA mini S second hand from a guy on boards.ie here in Ireland. I got the phone and really liked it because it allowed me to get rid of my Dell Axim X3i and mp3 player and keep it all in one device.
After a little bit of more research I discovered that I could remove some of the bloatware from the o2 xda mini S by just hard resetting and choosing the basic option which I than did. Still not satisfied with the overall performance of the XDA I decided to try a rom upgrade. Not wanting to do a totall overhaul I decided to just do a radio upgrade first.
My device is sim unlocked, it was like that when I bought it. I used the latest wizard service tool to CID unlock the device before I even flashed the phone. I also used the wizard service tool to change the nk.nbf file within the o2 mini S radio update into 96000000-GSM.nb. I then used this file to write to the GSM radio code (Bdk 1) according to the wizard service tool in the hopes that it would upgrade my radio version.
Well when I restarted, nothing of the sort happened, on the boot screen I noticed I was now missing my GSM version and when the phone finally got into windows mobile, it did not pick up any signal even though beforehand it could. The phone also became super slow to the point where it was unusable.
I have gone into bootloader mode subsequently after reading on this forum and tried to reflash with a number of updates with active sync disabled and nothing else running with the phone connected via usb to the pc. None of the updates would even pick up the phone or allow me to flash it.
My phone is pretty much screwed, I have a spare so it is not that big of an issue but I would like to make this usable again if at all possible. So my question is how do I flash a rom while the phone is in bootloader mode?
P.S I forgot to include the Current boot screen details:
IPL - 1.05
SPL - 1.05
OS - 1.5.4.2
Hi,
You can use the Wizard Love Rom from here http://rapidshare.com/files/17792050/Wizard_Love_2.26.10.2_WWE_Novii_CF2.rar
Hey there, thanks for the advice, I did download that ROM but like I said before, none of the roms manage to flash my XDA because they all cannot seem to connect to it. Activesync does not even pick it up in windows mode, and even when I have it connected in bootloader mode via usb and I double click on the love rom, it goes through the motions but never managed to "verify the information with the pda"
Try a stock Tmobile ROM but not from bootloader. Also, I would check the activesync app on the device. Make sure it's set to use USB as the default connection method.
A few other steps to try...
Uninstall ActiveSync and install an older version. If still no go, try a newer version.
Try a different USB cable and/or USB port.
Try a different computer with XP, not Vista.
Try flashing it without the SIM card or any memory cards.
If all else fails, you can try the SD card flashing method. There are instructions in the Wiki on how to do it, but always a stock ROM.
Try this one... http://forum.xda-developers.com/showthread.php?t=311027
Updated IPL/SPL and radio 2.69
Hey Devis, I think I have come one step closer, I tried all the suggestions that you made. Except well now my phone will not even go into the operating system when I switch it on. It will boot and the version numbers show but then it just resets itself.
I tried a different usb cable and I am not using vista, tried a different pc and the same result. The one place I did have some marginal success was the sd card method.
Basically what happened is that It backed up the OS from my phone and then reloaded it, not exactly what I wanted since the OS and rom are both screwed on the phone so my question at this point is, is there anyway using the SD card method to load one of the stock roms onto my phone?
I searched around the net and found the opposite to the "r2sd all" function, would be the "s2d" function, would that allow me to flash the phone with a stock rom?
Thanks for your time, I am going to call it a night here in ireland and head to bed.
Ok, if the phone resets then you probbably have a dead/dying battery. Charge it for about an hour or so using the wall charger, not the USB cable. Try to restart it and see if you can get in the OS. I was looking in the SD card method thread and some guy was successful at restoring the image from the SD even though his OS had died. He then had a fully functional phone.
The other thing to do would be to get the image file from someone that has a living and breathing wizard, preferably one with a stock ROM. Since this method is the equivalent of making an image of a PC using Ghost, the restoration of such an image to your Wizard should work just fine.
Just make sure that the other Wizard is SIM and CID unlocked. Or just go buy a Wizard from the store, unlock SIM and CID, copy the image on the SD and flash your device. Or... since u've got a new Wizard in your hands, just take the freaking thing appart and swap the guts return the store bought wizard to the store saying that the thing just doesnt freaking work!
As for the AT commands... it is possible that s2d would workfor you, it doesn't work in my wizard. from what i have been reading it appears that the bootloader is password protected and that password is randomly generated. I haven't played long enough with it to figure out how to get the password.
It looks like you've got some "trial and error" processes ahead of you. There is a wealth of info on bootloader AT commands on Wiki, nothing for the Wizard though. But something may work... not sure.
I could try to get you a ROM dump from my Wizard but I already am on SPL/IPL 3.08 and running WM6. the SPL/IPL version alone wouldn't allow you to restore from my backup.
Hey Devis, thanks for your time, just woke up here, will work some more on the phone today and let you know what is going on
Hey Devis, I did not even get a chance to fiddle around with the phone today, from being able to switch on less than 24 hours ago, it does not even want to switch on now so I am going to officially declared it a brick and move on. Will see if anyone can fix it for me, spent way too much time already when I should be working on my dissertation, thanks alot anyway
Sorry to hear that...
I have bricked one phone myself in the past... my old Pana GD87 and I absolutely loved that phone. I know how you feel.
Good luck with your dissertation.
oh damn. i failed to follow the steps for rom flashing (didn't delete the partnership) and hurt my poor phone. it works just fine. turns on makes calls etc, but when plugged in to the usb cable the pc pops up a little message that say " usb device not recognized" and it tells me that it's malfunctioning. it pops up in the device manager as unknown device with no drivers. i hard reset, entered bootloader, and checked the wiki and saw no help that didn't require me to connect the device to the pc which i can't do. i do have an old tool for my wallaby (first htc) that used to be able to copy a rom to an sd so you could flash it from the card din the bootloader, but alas, it only works for wallaby roms.
so is there an analog to this that will work with the wizard or is there a tool i can import via .cab file to restore the drivers to the wizard? i would love to get this fixed before my fiance finds out cause i was just bragging about how i had all this totally licked
ok so it seems all i need, i hope, is a back up rom image that i can flash from my sd card
any help?
ok, so anyone fallowing the story arch here, prepare for the surprise conclusion. in an m knight shamalayn type twist all of my assumptions were wrong, and the problem was totally resolved by reinstalling activesynch. apparently i hashed the drivers on the pc. thank you for joining me on this ridiculous stream of conscious little crisis.
Need some help in getting a stock rom to work and flashing a custom rom once thats' fixed.
I decided to go back to a basic HD2 and reload my custom rom on a fresh system. I downloaded and installed a stock rom, went to install my custom rom (Elegancia v2) and a couple things happened. First the flash failed with an error that there was a communication problem, though I could see the device on Active Sync. Now it's stuck at the white HTC page when I turn it on so something is wrong with the stock rom is some way to prevent it from booting through. It did that yesterday but not today. All I"ve done is continue to try to flash the custom rom and fail.
A magic bullet would be nice here.
Ok sense you posted this in the T-Mobile Development section I assume you have a TMOUS HD2 and I also am going to assume you got your stock ROM via the official T-Mobile HTC HD2 upgrade. You can try to reflash the ROM by manually putting your HD2 into bootloader (muticolor screen). Turn your HD2 off and then turn it back on but hold down the volume down button as it is booting it will bring up bootloader. Connect your HD2 via USB cable to your computer and wait until the Serial in the white bar of bootloader changes to USB and your computer regonizes your HD2 (this should happen simultaneously). Right click on the update utility and click on run as adminastrator.
But if you keep getting the communication error you can try flashing via a SD card. You will need a SD card formated Fat 32 it is recommended to use a smaller GB card but if you format your 16GB SD card it should work. Make sure you make a back up copy of your SD card on your computer before you reformat it. To learn more abput how to do this go to this thread. It can tell you all you need to know to flash via SD card. Also when you rename the Ruu_signed.nbh file it is not case sensative so you can name it LEOIMG.nbh or leoimg.nbh it does not matter. Be advised though no matter wich method you use to flash you will have to reflash HSPL to your HD2 before you can flash your custom ROM.
T-Macgnolia said:
Ok sense you posted this in the T-Mobile Development section I assume you have a TMOUS HD2 and I also am going to assume you got your stock ROM via the official T-Mobile HTC HD2 upgrade. You can try to reflash the ROM by manually putting your HD2 into bootloader (muticolor screen). Turn your HD2 off and then turn it back on but hold down the volume down button as it is booting it will bring up bootloader. Connect your HD2 via USB cable to your computer and wait until the Serial in the white bar of bootloader changes to USB and your computer regonizes your HD2 (this should happen simultaneously). Right click on the update utility and click on run as adminastrator.
But if you keep getting the communication error you can try flashing via a SD card. You will need a SD card formated Fat 32 it is recommended to use a smaller GB card but if you format your 16GB SD card it should work. Make sure you make a back up copy of your SD card on your computer before you reformat it. To learn more abput how to do this go to this thread. It can tell you all you need to know to flash via SD card. Also when you rename the Ruu_signed.nbh file it is not case sensative so you can name it LEOIMG.nbh or leoimg.nbh it does not matter. Be advised though no matter wich method you use to flash you will have to reflash HSPL to your HD2 before you can flash your custom ROM.
Click to expand...
Click to collapse
Tried that and no joy. I can get to the bootloader and see USB at the bottom of the screen but it won't go beyond that. Such is life. I worked it out with TMobil to exchange the phone with no penalty (hopefully that sticks0 but I'd still like to get my old one working. Not idea how I got stuck on the white page nor why this is happening at all but I want to try to prevent it in the future.
rogerperk said:
Tried that and no joy. I can get to the bootloader and see USB at the bottom of the screen but it won't go beyond that. Such is life. I worked it out with TMobil to exchange the phone with no penalty (hopefully that sticks0 but I'd still like to get my old one working. Not idea how I got stuck on the white page nor why this is happening at all but I want to try to prevent it in the future.
Click to expand...
Click to collapse
Hmmmm when you have your HD2 plugged into the computer while in bootloader and it says USB in the white bar of bootloader. Go down to the bottom right of your task bar and click on the little icon to safely remove a device. See if it lists your phone as "HTC USB Sync". If it does not list it as this you need to either try another USB port or update your USB drivers. Try updating the drivers while your HD2 is connected to your computer and in bootloader.
rogerperk said:
Tried that and no joy. I can get to the bootloader and see USB at the bottom of the screen but it won't go beyond that. Such is life. I worked it out with TMobil to exchange the phone with no penalty (hopefully that sticks0 but I'd still like to get my old one working. Not idea how I got stuck on the white page nor why this is happening at all but I want to try to prevent it in the future.
Click to expand...
Click to collapse
I had the same problem. I was in the bootloader screen with USB showing at the bottom. But when I tried to flash something I'd get a connection error. I just unplugged the usb from my pc and plugged it into a different usb slot, and walaa it started installing the htc drivers. Also in active sync, check the connection settings and make sure allow usb connections is checked.
Thank you for sharing, like very much
After looking through the varying questions concerning the same topic and, subsequently, not seeing the right answers - within the right timeframe (e.g. within the past month or so), I decided that a new thread was needed. So here's it is:
A branded G1 (mine, T-mobile, Germany) is what I want to downgrade so that it may be rooted and upgraded with a custom ROM. The problem, I am finding, is not that the instructions aren't correct. Rather, it's that a piece of the instruction set doesn't exist. Namely, the revskills.de website. I mention this because I have tried, repeatedly, to boot with the DREAIMG.nbh in order to downgrade and have consisitently (after numerous downloads from different sites) received the same error - 00028002 (or something like that) while trying to load it. I eventually learned that some phones needed a "goldcard" so I set about trying to do that. Got the CID, reversed it, etc. but the part about going to psas.revskills.de is the killer. The site is down and apparently, no other method of changing the carrier ID exists (or, if it does, the method is too ugly to mention, let alone comprehensible by someone like me, a not-so-good-programmer). Worse yet, all the instructions involving the generation of a goldcard also involve this website and consequently, because of the aforementioned down-status of the site, renders all instructions moot (Grade: D for relying on unreliable sources). So, back to the question: does a method exist outside of what I have mentioned? Where can I find it? Does it have a cost attached to it?
If you've read this far it means that full words and sentences don't confuse you (in light of so-called "l337sp33k") and I applaud you. I will applaud you even more when a well thought out and not-so-glib answer unriddled with blog cliches and platitudes can be found as a reply to this post...
Seriously, if you don't know an answer, a link to check out or someone I can refer to, don't waste your time (or mine) with a the standard "you need to read this and that rules before asking a question" reply. I have trolled through this forum and a few others for the past 2 days looking for the answers to the question of downgrading and finding not the right answers that are specific to this problem (yes, I've read thropugh cyanogenmod wiki, read through the wiki here for dream/g1 phones, gsm programmer's sites, android dedicated sites, etc...ALL of them point to revskills for the goldcard gen (except for one which allows dowloading a perl prog to compile yourself to make the goldcard - I'm not so good with perl yet)
If you need to check the website go here:
psas.revskills.de/?q=goldcard
it's not working for me, whether through proxies in the US, netherlands, britain, frnace, or germany. My only conclusion is that it has been shut down.
Thanks for you attention and I really appreciate some advice from one of you that may be able to shed more light on this.
Incidentally:
SD Card: Hama 2GB Micro SD(formatted fat32)
Droid/HTC G1 phone has been factory reset to:
Firmware: 1.6
Kernel: 2.6.29-00479-g3c7df37 [email protected] #19
Baseband ver.: 62.50S.20.17U_2.22.19.26I
Build No.: DRC 92
are you going on that non exiatent site to download the qmat thing? maybe try looking for it as a torrent file... use bittorrent or something and see if it's out there... i wish i knew how to help more, but i never needed to do anything like that...
stupid question but did you try both dreaimg files? rc29 and rc7?
both img files
Yes, I tried both. The US version gave me the same response as the European one. Tried qmat 5.0.2 and got nowhere with it (i ran out of time before I could figure out everything it could do - apart from simply reversing the cid). The only way to create a gold card seems to be through revskills...kind of a raw deal for the rest of us, if you ask me.
yeahh haha this sucks im not sure what you can do... hopefully someone sees this who can help you. sorry
I am currently trying out the alternate root method from your guide. Something's working...the build version is now CRB43 and I have cupcake (1.5) installed - I think. I shoudl be able to go through the guide in order now, right?
yeah if you have 1.5 than all you need is a custom recovery installed and you have root access... i prefer amonra recovery.. than you can flash radio and spl and go even further by flashing the newer 2825 radio and 0013d hboot
I just have to update my phone account with a data plan (forgot I didnt have one and cant sign in to google without it). Fortunately, it's cheap and takes only a day to update.
OK, so i worked the alt recovery method, but I can't sign in to google. (I used the AMON_RA recovery img.) I can't do anything now. The phone is (for all intents and purposes, bricked. I then tried to do the work around to get the wireless turned on at the touch me screen. It doesn't work. Still no root access. trying to go back to stock rom, no go. Still get the "Not Allow" 00028002 error. Haven't seen the fast boot screen lately. I try the back arrow from the boot loader screen...nothing. Even went so far as to try the HTC site boot unlocker method. HTC Sync installed, android sdk installed, etc. got the drivers in win7 x64 to acknowledge the phone being plugged in...it even recognozed (once) as the HTC Dream/G1, after that never again. This is nuts! It's funny as well as highly annoying. I'm running out of ideas and could use some suggestions...
Thanks
incidentally, the link to "DREAIMG.nbh" in the unrooting section connects to a download of the update.zip file. So, the link is misplaced or something...
good news, the gold card gen sit is back up, however, I can't connect to the phone with adb...I have tried the workaround but I guess the image on this thing is still not rooted. I'm out of ideas what to do, I cannot sign in to google (registration work around) and I can't connect with adb to all the other work to change things. This phone is hosed (and I will absolutely not go to T-mobile (in germany) they're even worse here than in the US...
Here is the link that I found for dreaming.nbh file.
http://www.megaupload.com/?d=NAAS5VBS
See if that works.
So, I am resigning myself to never getting this fixed. I have a rom I cannot access because the data plan on my sim card is for Maxxim, while the rom sets everything up as T-Mobile. Maxxim support will not give out the APN info and, to top it off, the wireless work around does not work because the cupcake dreaimg.nbh and amon_ra recovery image still do not allow root access. I'm lost, got a "working brick" phone, and I'll be damned if I go crawling back to t-mobile whether here in Europe or the US! Thanks for the help anyway...
yeah sorry bout that will fix the link, but its the same one you use to 'downgrade' on the Root method.. just brings you to 1.0, then flash the update.zip to 1.5 or 1.6...
so you cant flash the DREAIMG.nbh file? and you cant do anything via recovery?
but your device works if you had a data plan.. lol wow all i can think of is trying to flash the orange.nbh or get the DREAIMG.nbh to work..
Yeah, tried the orange.nbh as well and I get the same error for every nbh I try:
"00028002 Not Allow". It's really weird that all the nbh do not work...it's almost deliberate. The only root that worked was the alternate root, but wouldn't that have let me flash other roms? Interesting that it didn't.
Good that this G1 is a spare, but I would still like to get it working. I've found a use for it at work but it needs to be rooted. Will post back shortly with results from the DREAIMG.nbh and orange.nbh (if need be).
Incidentally:
Bootloader screen:
DREA110 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-2.22.19.26I
SEP 2 2008
Does this give you any ideas? I can get to the recovery console but it does not necessarily mean I have root (as far as I've seen to this point). I mean, if I were able to register the phone without a data plan (using the wireless connection) I think I would be ok. I did have a point when I was able to connect to the phone via adb (but the phone was registered).
I know I don't have root because I am unable to do the <enter>reboot<enter> thing in the reg bypass method. How did that happen? -I've got no idea...
Another thought, Is there another way to install drivers on my windows machine so that the phone is recognised by adb (even though it's not regitered and I have no way of turning on debugging)? Is there a way to alter the build manifest so that USB debugging is on by default thereby allowing me to connect via windows?
Its painful to read threads like this..
Do you still have your sdcards CID from the OP?
If so using the sdcard you have the CID to make the goldcard on your computer, tben takethe orange nbh rename it to DREAIMG.nbh and place it onthe root of the sdcard.
Then flash the orage nbh and use fastboot to install the 2708+ radio/spl/custom recovery (ra or clockwork)
If you dont have the CID find a device (likely a friends phone) that can read the CID and pick up from there. (notice no adb, and only fastboot after flashing an nbh with an engenering spl)
(I didn'tsay it earlier as the goldcard site was down...)
How to I go about reading the CID on another phone? I am not too familiar with the process. I have a nokia X2. Will that work through a bluetooth connection? (it's my wife's phone and I don't want to try anything with that one until I am absolutely sure.
If you could point me at something I could read on how to do this, I would be exteremely grateful...
Thanks
the site http://psas.revskills.de/?q=goldcard is odwn for me, so I can´t create my gold card.
Any other way to access the site?
I'm following the CM guide for my inspore 4g, but when I searched this forum, this thread came up
So here's my final result:
* Followed steps in the guide for alt root method (nothing else worked but that) - gained root.
* Restarted in order to follow thorugh with the radio upgrade
* No root
* Reflash the ROM
* still no root
* Cannot connect adb to device
* Windows sees it only as USB (even after uninstalling and pointing the hardware to the Android SDK USB Drivers
So I've come into an infinite loop:
* Can't gain root without a goldcard (or some ability to take the NBH apart and modify the kernel - DEFINITELY not my strongest skill...
* Can't get a goldcard without being able to read the CID
* Can't read the CID without connecting with adb
* Can't connect with adb without USB Debugging on
* Can't turn on usb debugging without a) registering phone (no data plan) or b) having root access to type in the commands at reg screen (with SIM Card in) or initial screen (without SIM card)
I've tried every ROM I could find, used the Android Kitchen tool (to modify the ROMs I've found, adding root access), I've read every guide I could get my hands on, as well as trying to extract the nb files from the NBH (in hopes of spotting what I needed to change in order to enable the phone to come on with wireless ON). I have been unsucessful. Is the phone now a paperweight?
I appreciate and respect any suggestions (I've already thought of buying a new phone - so that suggestion is out ;-) ).
Thanks