I'm not a total noob to rooting as I've already rooted my G1 and am running cyanogen's mods for months now. My problem is on a different phone.
This dream was dropped in water months ago (that's when I purchased my 2nd on craigslist). The touchscreen wouldn't work so I was stuck at the setup screen. I read on many forums, xda included that it might eventually dry out and today I found that it was indeed working fine.
It works fine on stock 1.5 ota update crc1 but now that I rooted one I want this one rooted as well. This is where my problem starts. I'm trying to rollback using the dreaim.nbh found inthe latest "how to root" thread in the dev forum. Problem is I can't load the image. I powe up holding camera and power button, get to the multicolored bootloader, insstructions on the grey/whitish screen say press power button to load, and then I am stuck.
Power button does nothing and the phone is stuck on that screen until I pull the battery. Been through this process 5+ times, with redownloaded image (file is not corrupt) My concern is Ill end up bricking but I really want root. I'm think their might be water damage on the phone but everything else works fine.
Any suggestions for a workaround or a way to troubleshoot the problem? Thanks in advance!
-Air
nbh
heres a link to where you can get the nbh dwnload this one nd try agian.
http://coolpstuts.blogspot.com/2009/07/all-download-links.html
no dice
pistol thanks for the try but it didn't work. same 87.3mb file, rc29, same result.
the greyish white screen loads, but the update (rollback) never starts. Does anyone know of another way to load the dreaim.nbh image? or heard a similar issue?
are you sure you grabbed the t-mo image?? go to the original how to root your phone thread and grab the t-mo image, nothing has changed so there is no reason for us to have an updated thread other than to confuse people even more
my problem is not the rc29 image
tubaking, my problem is not the rc29 dreaim.nbh image. I have consistently found the same image in many threads on xda. my problem is that i cant get it to load. this thread was not created for general rollback issues and def not to confuse people with another how to.... i am trying to figure out why my US G1 (with a noted history of physical abuse) won't load the image.
Was not implying that this thread would be a how-to and confuse people, merely that we have so many and people are constantly asking how to do something even though the steps didn't change. The physical abuse your phone has sustained "should" have no effect on the image flashing. I would suggest you format your card again(not in windows as windows seems to screw up a lot), so long as you are using the correct image and a fat32 formatted card you shouldn't have any problems, does the screen pop up and say "no image found"
airmaxx said:
tubaking, my problem is not the rc29 dreaim.nbh image. I have consistently found the same image in many threads on xda. my problem is that i cant get it to load. this thread was not created for general rollback issues and def not to confuse people with another how to.... i am trying to figure out why my US G1 (with a noted history of physical abuse) won't load the image.
Click to expand...
Click to collapse
hmmm, have you tried re-formatting your card?
trying it now
reformatted at home using gparted but I'll try paragon now that I'm at the office.
tubaking, thanks for the advice and willingness to help. it does not say no image found. It actually shows the steps that it needs to install including, radio_vz, and a few other things i cant recall right now...
hopefully the reformat will do the trick. I will try to format the entire card fat32 for now and then add my ext3 after. reporting back shortly....
still not working
so reformatted again to fat32, used paragon, gparted, and built in format on the G1 still the same result
grey white screen, reads the image.... then stuck at:
Code:
DREAIMG.nbh -
BOOTLOADER -
RECOVERY -
BOOT -
SPLASH1 -
SYSTEM -
USERDATA -
RADIO_VZ -
Press power button
to start update image
Press action button
to cancel update image
and then I'm stuck
So even after you press the power button to start the update, it just stays at that one screen and never gives any "ok"s next to any of the listings?
exactly
no oks, just hangs there
I've been letting it sit since before my last post, about 45 mins so far and still nothing. I may have imagined it but when i did this process last week it felt like it was getting hotter, but still nothing happened
also I remember doing this on my other G1 that is already rooted, so I know how easy this step should be
Stupid question, but are you making sure not to rename the original DREAIMG.nbh to anything else other than what it is? Some people make the mistake of thinking they have to rename it to update.zip or make the mistake of not leaving it in capital letters (although I don't know if that matters). You have said you have downloaded the file multiple times so I doubt this is the case but I'm just spitballing here
no rename
In my desperation I had considered that really stupid idea for a moment but thought better of it. I don't want to end up with a brick i haven't renamed it, consistently used dreaimg.nbh
airmaxx said:
In my desperation I had considered that really stupid idea for a moment but thought better of it. I don't want to end up with a brick i haven't renamed it, consistently used dreaimg.nbh
Click to expand...
Click to collapse
I wasn't suggesting to rename it, I just wanted to make sure that you never had renamed it to anything but the original filename DREAIMG.nbh
its all good
directmatrix, I understood your post. I was just saying i had considered renaming it to update.zip in an effort to get something going. I appreciate the spitballing, maybe we'll hit something that I missed!
airmaxx said:
directmatrix, I understood your post. I was just saying i had considered renaming it to update.zip in an effort to get something going. I appreciate the spitballing, maybe we'll hit something that I missed!
Click to expand...
Click to collapse
I re-read your original post and was curious as to whether the power button could be the culprit considering that its needed to flash the image. Perhaps the water may have damaged the power button interface. I can't imagine that it would be the problem considering your able to get into the rainbow screen via power+camera. Have you tried pushing it harder, many times, on the side etc?
i did, tried holding it for a 10 count, multiple presses, long press. I'm pretty sure the problem is not with the button itself because it works fine when I have the phone booted up and press power to turn it off.
When I first posted I was hoping someone might know of an alternative button combo that might have the same effect of loading the image from that greyish white screen
there is no way to write the image through adb right?
Related
Fisrt let me start by saying hello to one and all great forum.
Right, to my problem i have had my g1 a month now and love it
have not rooted it yet as i have been reading over and over so that when
i do come to do it i wont f**k it up.
I was downloading and installing app from the market and i think i have installed one that is for a rooted phone only(well thats what the discriptive said) i didnt realise this until i had installed it and so i was testing the apps last nite then turned off my phone as usual when i went to bed, Well so turned it on this morning and it wont load past the Android Screen, i tryed to go into bootloader and itsjust a color screen with serial10 on it.
please tell me i havnt bricked my phone i didnt do anything to it
anyone help me please
You did not brick your phone, if worst comes to worst you can go ahead with the rooting steps and download the dreaimg.nbh from your rc package that is meant for your area and boot it through the bootloader
thanks whats happened to it, the serial 10 has now gone and its just the 4 coulours on screen with some text at top, i havnt taken out the battery i thought i might damage it is it ok to remove it
The multi color screen you are describing is the stock bootloader, I prefer people do not pull the battery out if at all possible, your phone is quite similar to a computer, would you unplug your computer when it crashes
no, your right i wouldnt, so really i have not a clue here what should i do now, i actually need this up and running its my only phone thanks
not bieng lazy either dude, trying to search but like i say i dont kow what i have done wrong so dont bnow solution to seach for
Find a thread on rooting your phone, there you can find your rc, and go from there, go ahead and root your phone while you are at it
not bieng funny mate but i dont want to root my phone until i am confident enought to do it, i upgraded this from 1.0 to 1.5 when i got it can i just not do that again with the 1.5 firmware, thanks
Sure, use the steps to downgrade for rooting, then just leave it go and within the next 72 hours you will get the cupcake ota update, so to recap, downgrade, wait for updates
ok, and thanks alot for the advice mate, i will root it but like i said when i understand exactly what i am doing, cheers
No problem, and thank you for taking your time to learn the system and getting familiar with what needs to be done, instead of rushing in and asking common questions
cheers mate, its the only way to learn, thanks again
sorry mate to bother agian, i just tryed to downgrade with 1.0 and white screen comes up it just says "not allowed" really stuck now
Did you do it in the bootloader(tri color screen) did you put the dreaimg.nbh on the root of your sd card and not change it to update.zip
What part of the world are you in so I can make sure you are using the right rc or it is a possiblity that you might have to make a gold card(which is a pain in the ass.....so I hear)
just realised now have to change it to update.zip
I am in Ireland
P.S. just changed the DREAMIMG-RC7.zip to update.zip and it didnt work
do i change the .NBH to update.zip
Nope,do not change it to update.zip, download rc7, extract the .nbh from inside and put it on the root of your sd, then use it through the bootloader
no. did that mate put the nbh on card into bootloader just said "not allowed" sorry for keeping you up man
does it make any difference that i deleted everything of the memory card by the way
i just thought of something this phone was bought in the U.S.A. would this make a difference when i iupdated it
it was with a U.K. 1.5 O/S
Hmmm, is your sdcard formated to fat32, it's the only filesystem that it will read in the bootloader, walk me through what it is doing
yes i formatted it, then copied the files back onto it that i had backed up, then i deleted them all again, so just putting the nbh onto a blank card
then start up the phone and bootloader, white screen comes up with "checking" then comes up "not allowed"
Hmmm....... I wonder why it is not allowing, maybe you are one of the unlucky ones who need a gold card, or maybe we can get a stock cupcake build to work in the recovery since it will be signed by your provider, let me look around a little bit and see if I can dig anything up
OK this is the deal, i bought a phone off someone from craigslist. i have no idea what this person has done on the phone it came as stock donut. no root or anything of the sort. and there is no way to contact the person to ask what or if they tried to do anything. i have been trying every which way and yes the search bar is my friend. and nothing. ive done this before MULTIPLE times i am not new to rooting and flashing. Everytime ive tried to load something it always says no signature(#), number sign for random file numbers, i have tried to downgrade everything spl, radio and down to rc29, and trying to figure out if i could downgrade the recovery to the original recovery not the 2 (e). ive stumbled upon the idea that i might be missing files. maybe the otacerts i believe. i searched that also and found someone only saying to reinstall rc29 THATS MY PROBLEM I CANT IT WONT LET ME. Please someone help before i bust my head open on my desk.
and sorry about the punctuation typing super fast and avoiding my boss.
No signature usually means the update isnt signed.... and you probably got the update.zip thats corrupt...
Ive tried 3 different downloads of every file aka different dev for each thing. Anything i try and put as Update or even left as Original such as the .nbh it all comes up no sig. is everything online corrupt?
You don't have a root hence no luck on roms.
.nbh is not flashed thru recovery. Put it on your sd, power down your phone and power up holding power and camera buttons. Phone should find DREAIMG.nbh and restore your device to RC29. From there, secure your root and it's business as usual. Good luck.
borodin1 said:
You don't have a root hence no luck on roms.
.nbh is not flashed thru recovery. Put it on your sd, power down your phone and power up holding power and camera buttons. Phone should find DREAIMG.nbh and restore your device to RC29. From there, secure your root and it's business as usual. Good luck.
Click to expand...
Click to collapse
going to try this again
Hi guys, my first post here (although have done some reading in the past year) and in dire need of some help. Last night I tried to root my phone. I followed instructions from a sticky post on here, and from another sticky post on another forum.
Before going through how I got there, I'll state what condition my phone is right now, as this may be more reader friendly. I turn on the phone and get the fastboot screen (tricolour). I can reset with call+menu+power. Goes back to bootscreen. Only way to turn off the phone is to remove the battery. If I press trackball+power, a blue LED comes on, the screen stays black. Turning on the phone with camera+power doesn't make a difference. Turning on the phone with home+power doesn't make a difference.
The screen, on turning on, says the following:
'DREA110 PVT 32B RUUNBH
HBOOT-0.95.0000
CPLD-4
RADIO-1.22.12.29
Sep 2 2000
Serial0'
Before it gets to the screen, the screen briefly flashes white and says
'Loading...
No image file!'
I'll try to decribe what exactly I did leading up to this in as much detail as possible, however it took place from 11pm to 4 30 am, and not fully understanding the whys behind what I did, I may not be able to recall it perfectly. Please ask if I haven't provided enough details. I installed the earliest android software and did the telnet commands through telnet, downloaded on the market. I downloaded an app called root.apk and followed the instructions. I got to 'Step 3 - Protect Root' and it said 'Root Protected'. I then got JesusFreke's 1.5 EU rom and renamed it 'update'(.zip) and placed it in my root SD card directory. I loaded the software on. I THINK the mistake I made was not having the radio image (I don't even know what it is or why I need it) before trying to load it. I've since put it on and it hasn't made a difference.
Anyway, I turned on the phone after the install, and it became stuck on the android screen. At this point, home and power and camera and power both worked to provide me with different boot screens when turning on the phone. I did a hard reset. This brings me to where I am now.
Is my phone bricked? I read on a guide here the difference between soft and hard bricking - from what I understood, this seems to be somewhere in between - hopefully if it's a brick it's a soft brick! Any help would be much appreciated, as we all hate to live without our G1's, lol! Looks like I'll be going back to my Nokia 6210 and trying to send this thing for replacement back to T-mobile. Please help guys!
Many thanks
Michael
search around the forums, as far as i know, if you can get to the fastboot, your g1 isn't bricked
Yep, agreed.
In my old G1 days I had the same problem and it was because I didn't have an image file on my SDcard.
You're not bricked but I've since gone from G1 to Hero to Nexus so I'm not what you need to do but it is SIMPLE, I remember kicking myself when I sorted it.
HTH.
thanks for the prompt response guys. Very relieved to hear that it might not be bricked.
I just tried adding two separate image files (one at a time) to the root directory, but it hasn't made a difference. These are the details of what I added:
First I put in all three of these:
Android 1.5
Radio Image ota-radio-2_22_19_26I.zip 9181622 aeecdb49b74a0d4bb67f9d8af70c1889
System Image signed-dream_devphone_userdebug-img-150275.zip 38027127
5ca85a135ff1ddd41643237577cb8ec4
Recovery Image signed-dream_devphone_userdebug-ota-150275.zip 46907411 01c19785eef97b06409f52fed568feff
and then the system image for 1.6 just in case. Is this a noob mistake? I'm very unfamilar with system images, would be really great if someone could link me to the file I should try and put there for the image file!
Thanks again guys
well since it goes into fastboot, is there a way you can flash the recovery in fastboot, and try from there?
sakumaxp said:
well since it goes into fastboot, is there a way you can flash the recovery in fastboot, and try from there?
Click to expand...
Click to collapse
I'd certainly love to try any ideas how I'd do that? If you let me know i'll do it now. atm i'm not aware of any buttoms/commands which work in fastboot, but I've never used it tbh.
yeah to be honest, im not sure how to do that either, i just remember i was lurking around this forum and i saw a previous thread, that had a similar problem and someone mentioned the tip i gave you, so if any senior members or anyone know how to do this, please explain
Tranquility__89 said:
thanks for the prompt response guys. Very relieved to hear that it might not be bricked.
I just tried adding two separate image files (one at a time) to the root directory, but it hasn't made a difference. These are the details of what I added:
First I put in all three of these:
Android 1.5
Radio Image ota-radio-2_22_19_26I.zip 9181622 aeecdb49b74a0d4bb67f9d8af70c1889
System Image signed-dream_devphone_userdebug-img-150275.zip 38027127
5ca85a135ff1ddd41643237577cb8ec4
Recovery Image signed-dream_devphone_userdebug-ota-150275.zip 46907411 01c19785eef97b06409f52fed568feff
and then the system image for 1.6 just in case. Is this a noob mistake? I'm very unfamilar with system images, would be really great if someone could link me to the file I should try and put there for the image file!
Thanks again guys
Click to expand...
Click to collapse
I may be wrong here (if I am come round and strangle the cat).
But I don't see any .img files?
They are all zips? you need to have the image files UNZIPPED an as .img IRC.
OK, I unzipped the folder and put a folder in the root which had the .img files in them.. still didnt work. because i was trying to put them on to the sdcard through my girlfriends old nokia, it was very slow and kept crashing so the only thing is, i didnt manage to get all 3 unzipped folders on there. would that make a difference?
edit: hope I can still work towards fixing it - i need to check if i have a compatible micro sd card reader when i get back from work! please keep any ideas coming
You need the DREAIMG.nbh on your sdcard. Download the DREAIMG-RC29.zip file, unzip, place DREAIMG.nbh in /sdcard, boot into bootloader, and flash.
i did what cloverdale described on a bricked G1 and it worked just fine , now i need to figure out how to get donut on the mobile
anybody? pm if you can help and TIA
cloverdale said:
You need the DREAIMG.nbh on your sdcard. Download the DREAIMG-RC29.zip file, unzip, place DREAIMG.nbh in /sdcard, boot into bootloader, and flash.
Click to expand...
Click to collapse
Thanks for your reply. I'm downloading this one DREAIMG-RC29.zip
I'll then extract on my computer, isolate the DREAIMG.nbh file and copy it into root of SD card.
Is that correct so far
How do I flash?
Many thanks
Hmm, been doing as much research as I can in the time I have, and it appears I need to type command prompts into the fastboot screen? If someone could tell me exactly what to do, that would be a lifesaver, because I am really missing my G1
I didn't think I was this much of a n00b, but apparently so, heh.
bump.. been doing as much research as possible, but most of my net access atm is from work which has many sides blocked (incl XDA!) and im not entirely sure how to do these things that have been suggested.. if someone could just go into a little bit more detail id be really grateful.
Tranquility__89 said:
Thanks for your reply. I'm downloading this one DREAIMG-RC29.zip
I'll then extract on my computer, isolate the DREAIMG.nbh file and copy it into root of SD card.
Is that correct so far
How do I flash?
Many thanks
Click to expand...
Click to collapse
Once you have extracted DREAIMG.nbh and placed it on the sdcard, all you need to do is power on while holding camera, and the installation should begin (or perhaps it asks you to confirm), and not console is needed. Let it do its work, and when it tells you to reboot, press and hold call+menu+end and you will reboot to RC29.
cloverdale said:
You need the DREAIMG.nbh on your sdcard. Download the DREAIMG-RC29.zip file, unzip, place DREAIMG.nbh in /sdcard, boot into bootloader, and flash.
Click to expand...
Click to collapse
And if that doesn't work I would see if your sdcard is fat32
Thanks guys!!!!!!!!!!! it worked! Much thanks indeed.
There is another problem now though, if anyone can help: I'm doing a manual update to 1.5 (rc8) from 1.0 (rc7) and its getting stuck on the G1 screen and not loading.. not hard bricked or anything, can still access recovery and bootloader.. This thread has more information: http://forum.xda-developers.com/showthread.php?t=625677
thanks again
help please
Hi, my g1 is stuck at the seria10 fastboot screen. It is a US g1 that I purchased rooted. I know enough about these sort of things to get myself into trouble. I removed an app (card game) and my phone then got stuck so I did a battery pull. Now all it will do is either spin on the g1 screen or I can get the three skateboards fastboot screen. I am unsure as to what to do now. I downloaded the rc29 build and put it onto my sd card. I am on a mac so I do not think I use FAT32. I thought putting the rc29 on my sd card and holding the power/send/menu key would tell the device to reboot with the rc29 build. Should I have deleted all the stuff of the sd card? I just want my phone to work - I didn't know the phone was rooted until after I had purchased it from a dude off craigslist. any help is appreciated.
sd card is formatted to fat 16 not 32 according to my diskimage. Help?
brian
bcp0809 said:
Hi, my g1 is stuck at the seria10 fastboot screen. It is a US g1 that I purchased rooted. I know enough about these sort of things to get myself into trouble. I removed an app (card game) and my phone then got stuck so I did a battery pull. Now all it will do is either spin on the g1 screen or I can get the three skateboards fastboot screen. I am unsure as to what to do now. I downloaded the rc29 build and put it onto my sd card. I am on a mac so I do not think I use FAT32. I thought putting the rc29 on my sd card and holding the power/send/menu key would tell the device to reboot with the rc29 build. Should I have deleted all the stuff of the sd card? I just want my phone to work - I didn't know the phone was rooted until after I had purchased it from a dude off craigslist. any help is appreciated.
sd card is formatted to fat 16 not 32 according to my diskimage. Help?
brian
Click to expand...
Click to collapse
Disk utility on a Mac will allow you to format to fat32, you must do this. What happens when you power on the phone while holding down home?
I was able to do the home power thing and wiped the handset then rebooted it. Not sure why it worked this time over any previous times...oh well at least it works. Thank you for your prompt reply.
Hey guys its been a while since I've even tried to fix my phone cause everyone was saying its dead. But I've been reading stories of people coming back from the G1 logo. So i could really use your help.
Heres the problem, A while back I dropped my old G1 and had to get a new one. Upon looking for the video I used last time to root my phone, I couldn't find it. I searched high and low but to no avail. I figured any video would work as long as it rooted me. So I started up the video. however once i was "done" with it i noticed nothing had changed. So i figured the video was garbage and found another one and started it up. I know, STUPID. Well when i booted my phone after wiping and flashing. It stayed on the G1 logo. I knew the worst had happened. So now i don't know what to do. There have been one or two occasions that I've gotten it to boot loader. So i know i can get there. but what do i do when I get it?
Also, no, I never got to flashing raido's or anything like that. I thought I wasn't rooted so i didn't move on.
I know it was long but I'm getting all the info out there. Please help, I think its possible, and if it is I want my phone back!!!
What were you installing by the way?
EDIT: Made a mistake, thought you were able to boot into recovery.
He does not get to recovery, but into bootloader mode (cam + power on). This is good, as there is a good chance to recover from that.
Try the first section of this guide:
http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_G1/Dream_Firmware_to_CyanogenMod
You have to flash the correct dreamimg.nbh via bootloader. You might need a Goldcard to do so, in certain countries, but lets just hope that is not the case (would be more work...)
€: Some more Info on Bricking your device with Radio/SPL updates, so take care: http://forum.xda-developers.com/showthread.php?t=655097
The guide on cyanogens wiki is considered dangerous at the optional update to HardSPL
First off I would like to say that this is one of the best forums I have ever seen as the amount of support and helpful users and creativity put into these phones are staggering. I was going to go to Windows mobile for my next phone but I now doub it with this site or at least maybe I will dual boot.
So I am sure I am asking questions that have already been answered but my problems with the phone (USA G1) are many and the answers to some of the problems are so fragmented that I had at one point 14 tabs open for reference to solve just a few issues. I am 70% noob with the G1. I have had the phone for a year with no major issues just the annoying Force Close that seemed unecessary for the commonality of the app that had problems. Texts were annoying because I could not tell if they had been sent the previous day or recently as service at my home is come and go and my older Verizon phone had envelope information and even said if the person had read it or not so no annoying duplication. However, otherwise it was stable and would last about a day and a half with the double size battery.
Recently, however I had rebooted from the power button prompt and it got stuck (I can't remember on what screen) and figured installing a different ROM and other files would fix the problem. By the way, I had bought the phone rooted and I believe it was using JF 1.42 and a Cyagen mod (forgive my spelling). So I followed step by step from this forum the wiki on the lastest stable Cy ROM. I followed the instructions to the T.
Being new to the software, it was a slow process with a lot of repeating of steps discovering little details that were not mentioned like naming something update instead of update.zip like instructed or adding the .img as an extension. So I had nearly made it and then I came to the DangerSPL and other files to be loaded on the phone in order via fastboot. Despite, several attempts I could not get the skateboarding droids or the rainbow screen to come up so I finally decided to just continue as I had been using Amon-RAs 1.7 update zip feature to follow the instrucions and install the software in order. All was well until I got to flashing the actual ROM which said something about how it said the E: [insert file name here] was not correct so it aborted everytime but it did show some progress on the yellow bar.
Next came the issue of the G1 screen hanging up after the above problem and for some reason I could get to the 1.7 screen but only by holding the button required to access Amon RA longer than usual other wise it would say the build of Amon RA at th ebottom with no commands and the reboot itself or hold it longer and finally get to the Amon RA but it would not load my recovery files as I had made many along the way.
I nearly gave up but then came across this solution which worked by using method 1 at well I am not allowed to pu the websit in here but I am not allowed by the mods. but it is the 4th one down if you google "how to fix a soft brick g1" and the link is titled Unbrick - android-roms - How To: Recover your G1 from a bring ...However, it did get stuck at the rainbow screen as it finally let me do the fastboot and I saw the Androids skateboardig but it hung at the rainbow screen. It was here I noticed that my 32A phone was now a 32B. I took the battery out and powered it up and lo and behold it was asking me to put in my google information and I finally made it to the home screen.
I thought "Yes!". Now, I can try again since it will fastboot now which was what was recommended at the final steps but I was mistaken. I could not searc the market for common apps like wave secure and it frequently said it does not exist. I saw that my terminal app was gone and when I was finally able to download it from the market and my superuser app was gone and the termina would not respond as before to the input of SU.
Then, I noticed my phone's screen would randomly come on and only sometimes go off. When I pressed menu it was as if it the call button was stuck and it would either repeatedly bring up voice dial or call someone. The buton does not appear to be stuck otherwise. When it would briefly stop, acting like the call button was in turbo mode it would give me the option to mount the SD card as I had lost my micro sd card reader but never give me a chance to mount it before the call button interrupted with google dial or calling some number.
I do not believe this to be a hardware issue because as far as I remember the call button worked normally during the steps as it was requently used. So my questions, at the moment, are these:
1. How do I tell if the call button problem is a hardware or software issue?
2. Once I find my card reader and will I be able to use the factory bootloader to go through the updates.
3. Obviously I have derooted my phone (or maybe I can delete the diag from sd card and it will operate as it is derooted), will I be able to reroot my phone by using my backups of nandroid basically leaving me at whatever step I was on to the road of recovery?
4. How do I use my nandroid backup to recover especially if I am stuck with the factory bootloader?
5. I copied my SD card before I did the wipe originally so will I be able to find a .xml from handcent with my texts? (I text myself my mileage for work as with my hours, it is easier than using an app plus it saves space for other apps)? Should I load that backup nandroid first and start over?
6. Is there a quicker way to root like...a program?
7. What is your advice for the future other tha obviously backing up my texts more?
8. When did wave secure start costing money? I think I might have backed up everything a few days before the crash but I have no access to it now.
9. What other key combinations can I later use for the fast boot?
10. When formating the card to fat32 what allocation do you use and do you use quick format?
11. What is lost dir. and why is it empty?
12. In Amon RA 1.7 there are several caches which I cleard all of them when asked to clear the the cache in the wiki directions? Should I clear all of them and what are the seperate caches, espicially the davik one?
I am sure I am missing some question but I will post more as I try to follow your directions or attempt other methods. I apologize for the long, long story but I wanted make sure I did not leave out any detail so this can be resolved ASAP because I am sure I am receiving texts and calls and people are probably thinking I am ignoring them (no one leaves voicemails anymore so how can I know if they called or texted during the phone's sickness). I also apologize if I have broken any forum rules or posted in the wrong section or violated some. Thanks guys in advance. I miss the fat little thing so much.
Oh My god! Sorry but that's too long for me to read, my attention span isn't all that great =p
I will try to help with your questions but I didn't read the whole intro so my answers might be a little redundant.
1.Run "adb logcat" from a cmd prompt on your computer and see if pushing the button registers on the computer
2. um ok??? not a question
3. you will have to re-root but your backups will still be usable after you gain back root
4. boot to recovery (home+power), scroll down to backup and restore, select restore, and select the file
5. I'm not familiar with handcaent so can't offer help there.
6. It's not hard. Downgrade with DREAIMG.nbh to RC29, use update.zip to upgrade to 1.5, install one click root, use it, flash a recovery, and flash a rom.
7. You should write shorter paragraphs =p
8. Again, not familiar with it.
9. HOME + POWER, and BACK + POWER
10. No clue....
11. It's a folder automatically created when you don't unmount your phone before disconectiong the usb. It's useless and you can delete it.
12. When installing a new rom, just wipe everything. It saves you trouble later on.
Hope I helped...
Thanks I will give it a try later today and probably come back with more questions and longer paragraphs