I'm trying to root my G1 from scratch. I downloaded the DREAMIG file to my freshly formatted SD card. After I shut my phone down and reboot using (CAMERA + POWER) I get the multicolored screen that says Serial0, but it doesn't give me any fastboot options for applying the new image. I hit back and the screen reloads, but Serial0 still shows up with no options for applying the new image. I hit back again and now the Serialno screen is frozen, it won't reload. I've repeated these steps multiple times, but still I can't get into fastboot.
Any ideas?
Wrong section dude, this is Development, not Q&A...
There are TONS of guides for rooting a phone, check this one:
http://forum.xda-developers.com/showthread.php?t=563679
I'm using the CyanogenMod wiki instructions. They don't address the issue that I'm having. They assume that I'll see a grey bootloader screen where I would then hit the Action key to apply the image file, but I don't see that gray screen just the multicolored one and I can't get out of it. Any help would be appreciated!!
You don't have a fastboot enabled bootloader, you have a stock one. At this point it shouldn't matter. You can get out of bootloader by pressing menu+talk+power, aka 3 finger salute.
If your phone, in bootloader mode, doesn't find DREAIMG.nbh that means you named it wrong: are you on windows machine? Make sure that it's not hiding extensions and you did not name your file DREAIMG.nbh.hbh. Make sure that you have the right file and it's not corrupted (MD5 sum), make sure your card is formated in FAT32 format. Once your nbh file is right format/name, your phone will find it automaticaly.
Once can apply the image (DREAIMG.nbh) you're fine. Just reboot after it's done and continue with your rooting process.
I got it to work. It now recognizes my NBH file. The only thing I did differently was to do a regular format of my SD card instead of a quick format. Weird.
Thanks for the replies!
http://forum.xda-developers.com/showthread.php?t=485364 check first post, i ran into something like that when i rooted my g1, try using qmat and also you need a wm based device to get it work
All questions go into the Questions and Answers forum. Next time, please post in the correct forum. Moved.
here i was hoping we could have a weekend of people searching and posting in the correct section
same problem
scrappyabs2 said:
I'm using the CyanogenMod wiki instructions. They don't address the issue that I'm having. They assume that I'll see a grey bootloader screen where I would then hit the Action key to apply the image file, but I don't see that gray screen just the multicolored one and I can't get out of it. Any help would be appreciated!!
Click to expand...
Click to collapse
I have the exact same problem
you must have gotten ahead of your self, the multicolored bootloader screen is stock and has little to no fastboot commands available to you. maybe you can explain in more detail where you are at in your rooting process and what guide your following
Related
Edit: ****, ok so my phone isn't booting up now..the phone just freezes at the g1 splash logo.
I can still get into recovery console/bootloader, can I save my phone? Help!
I do have other theme's in /sdcard/themes/
I don't know if I can delete the current update.zip in my root and move one of them to the root and rename it, then flash that on? Someone please help!
-Ok so, I have the sdk...
-I'm in fastboot mode
-I have the correct driver for the phone, windows picks it up
but when adb doesn't pick up the devices, is there something I need to do to "get started" so to say? I'm trying to install some themes and push the browser.apk into the phone but, im stumped
tehseano said:
Edit: ****, ok so my phone isn't booting up now..the phone just freezes at the g1 splash logo.
I can still get into recovery console/bootloader, can I save my phone? Help!
I do have other theme's in /sdcard/themes/
I don't know if I can delete the current update.zip in my root and move one of them to the root and rename it, then flash that on? Someone please help!
-Ok so, I have the sdk...
-I'm in fastboot mode
-I have the correct driver for the phone, windows picks it up
but when adb doesn't pick up the devices, is there something I need to do to "get started" so to say? I'm trying to install some themes and push the browser.apk into the phone but, im stumped
Click to expand...
Click to collapse
First, you are at the wrong screen. You should not be in fastboot mode in the bootloader for updating themes, you should be in recovery mode.
I suggest you perform a wipe to possibly bring your phone back to normal at least. It can be done by turning off the phone, then pressing and holding the back and home button until you enter recovery mode.
From there press alt + w to wipe the phone.
Then restart by pressing back + home.
Next, before installing the theme, make sure its the correct one for your phone. Check with the author if it was made for RC30 or RC8, and if it is a non-wipe theme, because if it is not, you will be stuck at the Tmobile G1 splash screen (aka be in an indefinite loop) like your current situation.
If you are trying to install browser.apk (im assuming the multitouch browser - please correct me if im wrong) you will need to install JF 1.41 first. By default it will include the multitouch version of browser.apk
Please provide more information about your situation, and keep us posted.
andonnguyen said:
First, you are at the wrong screen. You should not be in fastboot mode in the bootloader for updating themes, you should be in recovery mode.
I suggest you perform a wipe to possibly bring your phone back to normal at least. It can be done by turning off the phone, then pressing and holding the back and home button until you enter recovery mode.
From there press alt + w to wipe the phone.
Then restart by pressing back + home.
Next, before installing the theme, make sure its the correct one for your phone. Check with the author if it was made for RC30 or RC8, and if it is a non-wipe theme, because if it is not, you will be stuck at the Tmobile G1 splash screen (aka be in an indefinite loop) like your current situation.
If you are trying to install browser.apk (im assuming the multitouch browser - please correct me if im wrong) you will need to install JF 1.41 first. By default it will include the multitouch version of browser.apk
Please provide more information about your situation, and keep us posted.
Click to expand...
Click to collapse
Sorry, I should have provided more information, and explained that the 2nd half of this post was my original post, which was just me asking how to correctly use ADB. I do already have JF 1.41, I upgraded yesterday. It wasn't my first theme I installed either. I was using Vintage War (for the Dream), but it hadn't been updated for 1.41, so I was trying the standalone apk adb push method found in this forum, which is where this post first oriented.
I was in recovery mode for installing themes, I'm using JF 1.41 RC30, with the HardSPL bootloader. Initially after installing the theme it would go blank after the g1 splash, so I had tried to install it again hoping it would fix it, unfortunately my thumb is a bit to fat and I hit alt W instead of S, anyways that is what put me into this infinite loop.
But like I said this wasn't my first time trying to mod the phone, I've had it rooted for a month or so now, and have been keeping up-to-date.
Any more information I can provide, please let me know. My phone is my livelyhood, I need it. So if anyone can help, the sooner would be better. Either way I am entirely greatful for any help anyone can provide. Thanks in advance!
tehseano said:
I was in recovery mode for installing themes, I'm using JF 1.41 RC30, with the HardSPL bootloader. Initially after installing the theme it would go blank after the g1 splash, so I had tried to install it again hoping it would fix it, unfortunately my thumb is a bit to fat and I hit alt W instead of S, anyways that is what put me into this infinite loop.
Click to expand...
Click to collapse
It is weird how a wipe caused you to go into an infinite loop. Which apk's did you try to push to your phone?
I would suggest to go without using the theme for now. JesusFreke had pointed out that some themes were causing problems for the new 1.41. update. You should check with the author of the theme to see if its compatible with the new 1.41 (which it should be since RC30 1.3, RC30 1.31, and RC30 1.41 are all compatible)
andonnguyen said:
It is weird how a wipe caused you to go into an infinite loop. Which apk's did you try to push to your phone?
I would suggest to go without using the theme for now. JesusFreke had pointed out that some themes were causing problems for the new 1.41. update. You should check with the author of the theme to see if its compatible with the new 1.41 (which it should be since RC30 1.3, RC30 1.31, and RC30 1.41 are all compatible)
Click to expand...
Click to collapse
....How do I get out of the loop. My phone doesn't get passed it. There has to be something I can do in console or recovery or something. I'm really sorry if I'm coming off as rude or demanding but I really need a phone, and I need it right now. I don't know what more I can tell you before someone can finally give me a solution (sorry)
1. Download RC29
2. Copy it onto your sdcard
3. Reboot your phone into the SPL with Power+Camera
4. When prompted, press the end key to start the reflash.
Note: this will completely wipe the flash chip on your phone and revert everything back to factory. You will need to re-root your phone and update to JF1.41
Next time, use nandroid to backup before installing themes, etc.
Datruesurfer said:
1. Download RC29
2. Copy it onto your sdcard
3. Reboot your phone into the SPL with Power+Camera
4. When prompted, press the end key to start the reflash.
Note: this will completely wipe the flash chip on your phone and revert everything back to factory. You will need to re-root your phone and update to JF1.41
Next time, use nandroid to backup before installing themes, etc.
Click to expand...
Click to collapse
Alright, I'm doing it now. And I did use nandroid and make a backup, no one said anything about how to restore it. Regardless thank you so very much, you are my Savior right now!
tehseano said:
Alright, I'm doing it now. And I did use nandroid and make a backup, no one said anything about how to restore it.
Click to expand...
Click to collapse
That's easy. Just grab a copy of the fastboot utility and the images off your sdcard in the 'nandroid' directory and boot your phone into the SPL. Plug your phone in via usb and press the back button once and you should see "Serial0" change to "FASTBOOT" Then open up a windows command prompt in the location of the exe you downloaded and run:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata data.img
fastboot reboot
Your phone will come back up with all of your applications, settings etc from when you did the backup. Keep in mind you need the HardSPL to do this though(look for three androids on skateboards in SPL). The G1 factory bootloader does not support fastboot, only NBH images that come from the factory.
Hi, my situation is a bit worse:
I have a Dev Phone, upgraded to JFv1.41.
Today, I got the pop up message telling me to do a "system holiday update 2 of 2". I press "Update now" and the phone got reboot. Since then... I could not get through the first screen that has the word "Android" at all, not even to the screen where Android icon is flashing. It just freezes right there.
The only way to turn off is to take out battery. I could not enter recovery mode through pressing Home+Power. One time, the screen actually turned into weird color patterns. Is there anything I can do? consider that I don't have any nandroid back up image at all?
I tried to download the DREAIMG-RC29.zip, unzip and copy to the sdcard, then reboot into the SPL with Power+Camera but nothing happens, just a 4 color screen said "serial0".
Thanks in advance.
Isn't the 4 color screen the standard bootloader that ships with retail G1's (not a dev phone bootloader)?
lugiamx said:
Hi, my situation is a bit worse:
I have a Dev Phone, upgraded to JFv1.41.
Today, I got the pop up message telling me to do a "system holiday update 2 of 2". I press "Update now" and the phone got reboot. Since then... I could not get through the first screen that has the word "Android" at all, not even to the screen where Android icon is flashing. It just freezes right there.
The only way to turn off is to take out battery. I could not enter recovery mode through pressing Home+Power. One time, the screen actually turned into weird color patterns. Is there anything I can do? consider that I don't have any nandroid back up image at all?
I tried to download the DREAIMG-RC29.zip, unzip and copy to the sdcard, then reboot into the SPL with Power+Camera but nothing happens, just a 4 color screen said "serial0".
Thanks in advance.
Click to expand...
Click to collapse
I had the same problem, almost verbatim. ADP1.1, JFv1.41, ran the Holiday update 1 of 2, no problems, did the 2 of 2 update, got stuck at the flashing Android boot screen. Pulled the battery, rebooted, same thing, waited 2-3 minutes at the flashing screen and was just about to pull the battery again and then all of a sudden the damn thing came to life, the OS loaded up and now everything's working fine. Gave me quite a scare.
ummm actually the fastboot utility wont work for my computer soo what shoud i do.... if anything i need a really good reply something long cause im new to this and my fone wont get off the android sign.
chinoman said:
ummm actually the fastboot utility wont work for my computer soo what shoud i do.... if anything i need a really good reply something long cause im new to this and my fone wont get off the android sign.
Click to expand...
Click to collapse
Why have you just hijacked a 5 month old thread? You haven't given use any details either. Fastboot is available for all OS's, it will work on your computer, you just probably don't know how to use it. Please make a new thread in the Q&A section where we can help you out there.
This should be closed or moved to Q&A.
hey man just unroot ur phone and root it again u soft bricked ur phone its ok
hey just try to unroot k
hey if u want me to fix it for u just email me at [email protected] and ill help u
So usually I've read this is a matter of the wrong spl, or unsigned files, or other things that don't seem to be my problem. I've searched for days now and would LOVE some help.
I'm downgrading for a warranty return because my touchscreen doesn't work. I try to follow the directions found in several threads but I get hung up at the same spot.
When flashing the dreaimg.nbh file in the stock bootloader, bootloader starts, checks, then I get to the screen that asks you to press power to flash, or action to cancel. No buttons on this screen do anything. Not the "3 finger solute" to reboot, not power, not action, nothing. Just no response. And yes, I waited, and waited.
I think I've tried about every combination of everything I can think of, but please, your suggestions mean a lot to me.
The only thing I can think of, is that maybe the updated radio isn't compatible with RC29, and the phone knows this somehow and won't let me flash RC29 with my current radio? Does that make any sense? Do I need to flash an old radio, then the dreaimg.nbh?
Thanks!
(anybody wanna tell me how to get a screenshot from the bootloader and I'd be glad to show it, but it's just the standard screen)
I say try! ahaha
Same thing happened to me with the touchscreen lol.
I just flashed the old image didn't even bother to update or anything and just sent it in.
And I didn't get charged for voiding the warranty.
And no the new radio is compatible with RC29 I've used my friends phone when we were rooting it and he had the new radio.
Thanks for that, if I can't figure it out, I guess I'll try the warranty. I'm still going to work on it though, I can't imagine that someone hasn't had an unresponsive bootloader before though, and know how to fix it.
I've always done things the retard way, but I've spent the last week learning ALOT. I've got adb and fastboot setup, is there a way to flash the nbh file via fastboot or adb, bypassing the bootloader?
And FYI for others, with the nonworking touchscreen you can't "press the droid" after a factory reset. SDK, and androidscreencast fixed that, you can see your screen on your computer and use your mouse to click!
http://code.google.com/p/androidscreencast/
I also just got droid explorer, which lets you do lots of things with a GUI, including invoke androidscreencast, man that would've been easier a week ago! At least now I am able to use the phone as I had to disable the wipe unlock, and touch the droid to recover from a wipe!
I imagine this would be perfect for people with broken screens as well!
the .NBH includes EVERYTHING but an SPL... it rewrites Radio, splash1 system and usrdata...... if you cant press the action button, first try re-flashing the SPL, then try cleaning out your trackball
the action button is the trackball BTW...
Thanks for those tips. But I've done that and it still doesn't work. Even tried downloading the spl from a variety of sources, and doing a checksum to make sure it's not corrupted. And the trackball works in every other application. Basically, the stock bootloader just won't respond to any command (action to cancel, power to update, 3 buttons to reboot, nothing). It DOES recognize the .nbh, which is a step further than most bootloader fail threads I see.
Is it possible to flash an nbh file using fastboot or adb? I've figured out how to do update.zips this way, but not .nbh. I'd still have a custom bootloader, but everything else would be stock.
Thanks again everyone!
So if anybody can help, maybe this bit is useful too, I get no response from the hard spl either. Example, it is my understanding that the standard hard spl screen (with no .nbh file on card it dislplays phone radio info at top, serial0/10, 3 android skaters at bottom) that screen I should be able to press call+power+menu to reboot, right? I get nothing, and thought I should. This spl won't flash the nbh either, I guess because it won't register the "press power to contine".
1. Any ideas? My keys work when in standard usage and in recovery, why won't they work in any of the spls?
2. still wondering if/how I can fastboot the dreaimg.nbh file?
Make it unbootable (don't brick it - just wipe your current ROM and recovery partition) and restore to stock G1 SPL and if they say anything about "It won't boot" blame it on shipping.
Have you tried updating with a engineering SPL? I don't know if that would have any difference. Also, is your sdcard still partitioned? I think it has to be all fat32 or a goldcard (no idea where a goldcard actually come in on G1).
Brilliant! I bet it is the partitioning! I now remember that I thought about that for a minute, but tried other things. I'll try a fresh, all fat32 partitioning and give that a shot. Otherwise, good call on just deleting the partitions.
(actually excited to have something hopeful to try for a change!)
Solved!
Cheers to you R3s!
If anybody else finds themselves with an unresponsive bootloader, make sure your sdcard is not partitioned.
For the step by step folks who may be wanted to return a G1 to stock, in my case for a warranty return because the touchscreen doesn't work:
put the stock 1 G card in a card reader, popped it in the usb drive of a winxp system, my computer, right click on drive, format (not quick) fat32.
copied over stock spl renamed as update.zip
copied over DREAIMG.nbh
unmount sd card
pop into g1
home+power to get into recovery
apply update.zip
reboot
wipe
reboot + hold camera button
power button to apply
wait, this time I got the status bar immediately
action button to restart when prompted
reboots to spl
3 finger salute to reboot (call+end+menu)
BAM, back to the android to press the button to start
(and fully stuck there now since I don't have a touchscreen, my daughter called me crazy for being so happy, she asked if I fixed it and I said no I broke it!)
So there ya go, anybody else has this problem, reformatting the sdcard isn't enough, you have to remove the partitions.
Hi
I have been using Clockwork recovery for months and tonight was flashing ROM/zips as usual, and all of a sudden when I try to get into recovery my Nexus just sits on the colored X. When I pull the battery it reboots fine with the ROM I currently have installed. Then I go back into ROM manager, re-flash clockwork recovery: it says flash was successful, so then I choose to boot into recovery, and again it just sits at the blue, red, green and yellow X.
So then I tried a round-about way by going into ROM manager and choosing to restore a backup. Again, when I choose to restore backup it just boots to the colored X again and freezes there.
I've also tried the regular method of holding power button and trackball and get the same results.
Does anyone know why this might be happening? Right now I'm stuck with a ROM I was just playing with and didn't necessarily want to use permanently....I'm afraid I might be stuck with it forever now
Thanks for any help!!!
I've been searching and I should add that my bootloader is not unlocked
Try to flash your recovery manually, using the guide from my signature. Try Amon_RA's.
Jack_R1 said:
Try to flash your recovery manually, using the guide from my signature. Try Amon_RA's.
Click to expand...
Click to collapse
Well I ended up wiping all user data in fastboot and now I get nothing but an X nomatter what I do, won't boot at all.
All I can do is hold down the power button and trackball and get the page that says
bootloader
reboot
reboot bootloader
power down
the only way I'm going to get this fixed is to use my computer and I've never done it that way...I've always used ROM manager
I'll read the links but I think I'm screwed because a lot of this is over my head
Thanks for the links !
1) Try to follow "Unroot/restore" guide first, see if you can restore functionality using PASSIMG method. Once you have functional FRG33 with recovery, you can root it, replace the recovery and install custom ROM of your choice / update to FRG83G.
2) If nothing helps - consider a) replacing your phone, b) unlocking the bootloader and flashing recovery through fastboot.
Getting in over your head is sometimes a good way to expand your horizons
Hi Jack
Thanks for the help
I'll do some reading and see what I can do....got two feet of snow here so I guess I have the time
worst comes to worst I'm still under warranty.
Well I tried the instructions but nothing happens..it just sits on the screen with the androids skateboarding. I renamed the zip and moved it to my SD card but it doesn't seem to even search for it, let alone find it. Really wish I had not deleted storage. At least I had a working ROM at that point.
Which instructions did you try? Did you download FRG33, rename it to PASSIMG.ZIP (and not PASSIMG.ZIP.ZIP !), put it on the root of SD card and reboot to bootloader?
Jack_R1 said:
Which instructions did you try? Did you download FRG33, rename it to PASSIMG.ZIP (and not PASSIMG.ZIP.ZIP !), put it on the root of SD card and reboot to bootloader?
Click to expand...
Click to collapse
Hey Jack...
Sorry for taking so long to respond...I finally had to crash for awhile, my brain was frying.
Yes I did what you describe: downloaded FRG33, renamed it PASSIMG.ZIP(not ZIP.ZIP) moved it to SD card just like any ROM and held down volume and power button and came to the screen with the three androids. Then it just stayed there, nothing happened.
The only thing is I had to use my backup Nexus One(EDGE only on ATT model) to move it to the SD card as I don't know how to access the SD card with the device acting like this. If I connect the device to my computer while the three androids are on the screen, I hear it connect to the computer, but nothing pops up allowing me to access the SD card....
Like I said I'm a noob at this I appreciate you trying to help me here
About 3 seconds after the 3 androids skating appears, you should see some text flash up?
It does say you're in HBOOT and not FASTBOOT right? If in fastboot, pick the bootloader option and then it should find the file.
Rusty! said:
About 3 seconds after the 3 androids skating appears, you should see some text flash up?
It does say you're in HBOOT and not FASTBOOT right? If in fastboot, pick the bootloader option and then it should find the file.
Click to expand...
Click to collapse
Hi Rusty
Sorry I somehow missed your post here. Yes I see some text flash up...takes a little longer than 3 seconds...maybe 8 seconds...
At first it says I'm in Fastboot, but then I press the power button and then it says HBOOT at the top.....that's when the text flashes on the screen. It flashes too fast for me to read it though....but nothing happens after the text flashes on the screen.
I'll be damned guys....I got it working! After responding to Rusty's post above, I decided to give the whole thing another try. Well I went thru the whole process of putting the file on the SD card and realized I had in fact renamed it zip.zip....it LOOKED like it was only ZIP, but when I clicked on the file while it was still on my PC, it said it was zip.zip...that's when I knew what the problem was.
My problem now is getting it re-rooted. Originally I used the Universal Androot application..the true one-click method...I just tried it again and it didn't work.
Is there a way to downgrade to a version where this app will work again?
Thanks guys you really helped me out here!!
Please read the guide in Wiki, and follow one of the zillion SuperOneClick threads that are around. It's really as simple as it gets - and if you happen to have Windows 7, it's even more simple - you won't need to install the drivers.
Jack_R1 said:
Please read the guide in Wiki, and follow one of the zillion SuperOneClick threads that are around. It's really as simple as it gets - and if you happen to have Windows 7, it's even more simple - you won't need to install the drivers.
Click to expand...
Click to collapse
Yup I'm already rooted!!! Thanks man!!!! Took 12 minutes!!
Okay I'm having another issue: SuperOneClick said I was rooted,I have the superuser icon in my app drawer, but ROM manager will not flash Clockwork mod recovery and Titanium Backup says I do not have root rights??
well I rebooted and now have root rights but am still getting an error when I try and flash clockwork mod: it says: "an error occurred while flashing your recovery"
Do you have Busybox installed?
Jack_R1 said:
Do you have Busybox installed?
Click to expand...
Click to collapse
You're going to think I'm a dip**** but I don't even know what busybox is?
Let's just say it's an app that the system needs Go to Market, download and install it, try again. If it doesn't work - you can try to install custom recovery manually, using another guide from Wiki. Look in "Installing Recovery" for "For locked bootloader - flash_image using Terminal" guide. If you don't know what Terminal is - download "Android Terminal" by Jack Palevich from the Market.
Use the fix problems button in Titanium Backup to install it, long story short is it lets you use a bunch of native Linux commands that as missing from Android.
Hello
I can't boot on my n1.
Every time I turn on my phone it gets stuck on the screen fastboot.
The worst is that no button works, nor volume, nor power, nor the trackball.
I searched the forum and found no solution.
I appreciate the help
This is the screen
imageshack.us /photo/my-images/843/imag0652g.jpg/
One of the buttons (trackball? volume?) is stuck.
That's what all the forum searches should have told you.
Nothing to do but physically repair it.
If it is getting stuck in Fastboot mode, it would be your trackball button that is stuck.
res
It was really a physical problem at first, the trackball was stuck and now I can move the volume and power buttons.
However when I select the bootloader i go to another screen and selecting fastboot back to the previous screen and the system does not load.
When I select reboot or reboot bootloader, go to the same screen and the system will not boot.
When I select recovery appears a triangle with an exclamation and not leave it, I have to take the battery out.
I've made clear storage and nothing changed.
That is, still can not get the phone working.
Any suggestions?
Thank you very much
If you are looking at keeping the phone stock, I would recommend looking into the PASSIMG method (method can be found in the Nexus One Wiki link in Jack_R1's signature under Unroot/Restore). This will put your phone back to the way it was when it first came out of the box.
If you are wanting to load a 3rd-party firmware, the easiest way is to unlock the bootloader using fastboot and then load a custom recovery like ClockworkMod or Amon_RA. This will allow you to install a custom ROM.
I made a video, hope it helps.
youtube
watch?v=GBvtiB2n3zM&feature=youtu.be
You have a link explaining how to do this method?
Thanks
For which method? Either way, I am sure both are well documented in the wiki in Jack_R1's signature.
Hello everybody
Unfortunately I could not solve my problem.
I tried the method passimg but not worked. The phone does not leave the bootloader screen.
My sd card is formatted, the file passmig put it, the file is installed, but then back to the same screen and the system will not boot.
Can anyone help?
I lost my phone?
Hey I'm having the same issue, I'm still with the phone like if the trackball is stuck, but I feel button ok, I press it normal. I think it could be the flex, what do you think guys?
Hi,
Just yesterday my phone died and appears to be in boot loop. The X is stuck on the screen. I've been reading through some forums and heard trying to reboot with the SD card, but that didn't do anything. Unfortunately my main problem is that my power button is also broken, so I can't do a system restore or fastboot. My phone isn't rooted and I'm new to the technical stuff of phones so if someone could give me some help or advice I would greatly appreciate it.
in a smiliar boat
I dont mean to step on the OP but maybe my situation could help shed some light. My N1 is displaying the same symptoms but my power button works fine. If I power up while holding the trackball, the only thing that shows up as selectable items are:
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
Way back when I rooted my G1, it seems to me there was a much more extensive menu available at this stage. I'm willing to root and flash at this point if needed--I just need this to work as a phone for my non-data using wife. Any suggestions appreciated.
dclaryjr said:
I dont mean to step on the OP but maybe my situation could help shed some light. My N1 is displaying the same symptoms but my power button works fine. If I power up while holding the trackball, the only thing that shows up as selectable items are:
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
Way back when I rooted my G1, it seems to me there was a much more extensive menu available at this stage. I'm willing to root and flash at this point if needed--I just need this to work as a phone for my non-data using wife. Any suggestions appreciated.
Click to expand...
Click to collapse
I suggest you should do some reading first to get familiar with the procedures and then work on your N1. Here is the Nexus One Wiki on this thread which has extensive information http://forum.xda-developers.com/wiki/index.php?title=Nexus_One
I've been reading the wiki for two days but I keep running into roadblocks. I just now realized the fastboot was highlighted by default (duh). It's coming back to me now. I'll just keep plugging. Thanks!
I had your exact problem at one point. Broken power button, locked bootloader, stuck at the boot up screen, only difference was that my phone was rooted. What I did to fix it was the PASSIMG.ZIP method which can be found on the wiki here.
You're going to need an alternative method to putting the ZIP file on your SDcard since you can't boot into Android to mount it. If you have one, use an SDcard adaptor to plug the card directly into your computer, or use another phone and mount it from there.
Good luck!
(Not sure if this is what you did and meant when you said "reboot with the SD card," hopefully it's not)
I've tried the ZIPIMG method but when the phone reads the file it just says 'No Image or Old Image' and goes back to Fastboot menu
magma9495 said:
I had your exact problem at one point. Broken power button, locked bootloader, stuck at the boot up screen, only difference was that my phone was rooted. What I did to fix it was the PASSIMG.ZIP method which can be found on the wiki here.
You're going to need an alternative method to putting the ZIP file on your SDcard since you can't boot into Android to mount it. If you have one, use an SDcard adaptor to plug the card directly into your computer, or use another phone and mount it from there.
Good luck!
(Not sure if this is what you did and meant when you said "reboot with the SD card," hopefully it's not)
Click to expand...
Click to collapse
magma9495 said:
I had your exact problem at one point. Broken power button, locked bootloader, stuck at the boot up screen, only difference was that my phone was rooted. What I did to fix it was the PASSIMG.ZIP method which can be found on the wiki here.
You're going to need an alternative method to putting the ZIP file on your SDcard since you can't boot into Android to mount it. If you have one, use an SDcard adaptor to plug the card directly into your computer, or use another phone and mount it from there.
Good luck!
(Not sure if this is what you did and meant when you said "reboot with the SD card," hopefully it's not)
Click to expand...
Click to collapse
I have the same problem and following your instruction, I have copied the PASSIMG.zip to the SD card, but how can I mount it when the power button is broken?