Database Develop

Stuck on bootloader screen.

So I had root access. (i.e. when I first booted my G1 up it said something about a developer phone) and I tried flashing the dreaimg.nbh file to go back down to RC29. It fails every time won't let me do anything else. It just stays srtuck on the bootloader screen when I try to reboot. I've tried about everything I could think of and I'm at wits end. I really hope this problem can be fixed. Does anyone have any suggestions or know what went wrong? Thanks.

Re-download dreaimg.nbh file again. The one you're using may be corrupted.
Why do you want to go RC29 if you have root access? You should be able to flash anything on your phone as is, RC29 is only needed to gain the root.

It won't let me do anything. I'm unable to do anything to the SD card. Although, while typing this I just thought of something. If I got a card reader I could erase the file from my card since I can't do anything to the phone. Maybe that would work. But who knows because I've tried removing the card and booting up and it remains stuck on the bootloader screen. I literally can not do anything else, it's just permanently stuck like that. So I can't mess with anything. And the reason I was trying to downgrade is because I was trying to start all over again but I think I might have ended up screwing myself instead...

I am may be wrong, and please forgive me if I am, but from your post count I am getting the picture that you're pretty new to this.
Tell me if what you did is any different from these steps
You booted phone into h-boot mode holding power and camera buttons
Your phone found dreaimg.nbh and ran it on it's own.
You restarted the phone and got stuck in the boot loop.
Confirm that this is what happened

No, your assumption is not wrong at all. I am pretty new to this.
Yes, I did reboot my phone while holding down the camera button.
It found dreaimg.nbh and ran it but it failed so now I'm stuck in the boot loop with it constantly trying, and failing, to load dreaimg.
Thanks so much for your quick responses.

When it says "failed to load dreaimg.nbh" it means that it does not see it. I have a feeling that a file that you had was zipped.
Let's do this
Boot into recovery by holding power and home buttons
select wipe/factory reset or something along those lines and try booting up a your phone again. I'll be lurking around so just post what you find.
Take a note of which recovery you're running while you're at it too.

No, the file I had was not zipped I don't think cause it sees it and tries to update. It says update in progress then I get the progress bar but when it's finished it tells me: Update Terminate. Update Fail. Then it just goes back to the multi-colored bootloader screen and won't shut off. I can reset it by pressing call+menu+end but then it just starts all over again. So, I can't boot into recovery mode. Matter of fact, the only way to turn the phone off is to remove the battery. Otherwise, it just starts in bootloader mode and continues this viscous cycle.
At this point I don't even care about installing a ROM or anything, I just want a working phone.

I see. Yep.. you're S.O.L.
Just to make sure... when your phone is off and you hold power and home buttons it just goes to h-boot screen, right if so then unfortunately there's only one thing to do: get a card reader, re-download .nbh file and start over. At this point you have no working recovery or rom on your phone. Once you get that going you should be on your way to secure a root and flash whatever rom you need to.

Is it even fat32?

Damn. That's what I thought. I should have just left well enough alone until I did more research and knew exactly what I was doing but I get ADD when I'm hungover. Oh well. Thanks for your help.

This will happen from time to time.. it's always desirable to have a card reader handy. Also.. since you have nothing to loose, this would be a great time to re-format and re-partition your sdcard so you can start squiky clean.
Good luck.... let us know when this is worked out by adding [SOLVED] to the title of this thread.

G1 will not recover ??

I have G1 sitting around that I never messed with until last night, so if it's bricked, it's not a big deal. The phone will turn on, and loop through the splash screen. The only way it will boot is in safe mode. When trying to do ANYTHING in safe mode (aside from power down), everything will FC. If i go into the recovery menu with the Home plus End key sequence, I get the "can't open cache recovery command". I've tried to install RC33 in that screen, and get "installation interrupted".
The phone was given to me, so I really don't know if it was rooted or what was on it before. I do remember it worked, and just one day stopped working. When it was working I never saw a superuser icon or any other apps you usually see with a root. Thanks in advance for any help.

No one? Is there just a full update I can throw on the SD card and get it running?

Try formatting the sd card fat32, putting dreaimg.nbh(search) on it. Then, put it in the phone and boot with camera+power. Follow the onscreen instructions, and hopefully it'll work.
If it doesn't, not my fault. Good luck!

Thanks Michael, but I did that already and it really didnt change anything. I noticed the recovery menu looks a bit different, and when I go to safemode, the "android" looks different, but thats it. Still cant boot, and still shows there is no recovery in the recovery menu.

[Q] Urgent: Nexus failing to boot

Hi all,
I have had my N1 for 1year and two weeks now (yes, warranty just expired). I was charging the device and it seemed to overheat and reboot. I unplugged it, took the battery out, let it rest for a bit and tried to boot it again. The phone now gets stuck on the X logo (not moving) and never boots.
I'm currently abroad (in the UK) and can't have it sent back for repair (I'd have to pay the repair too).
Will rooting the phone and installing an alternate OS fix my phone?
Is there any way to get HTC to honor the warranty after two weeks of expiration (I've been getting this problem for a while now, but that was only an issue if I made extensive use of the device while charging, which I almost never do so I didn't bother.)
Is there any way to fix this issue without messing with rooting? I'm abroad right now and all I want is my phone to work.
Any suggestions are welcome.

Try booting into bootloader from power off (vol- pwr) if that doesn't work then try the 3 figure salute (pwr vol- tb) your phone should boot into fastboot then just select bootloader.
If either of these work the your good you can get the static x fixed all you need to do is passimg (search wiki if you don't know what it is) as for the charging problem passimg will factory reset the phone so if that doesn't fix it then no you'll need to try rooting or it might be hardware.

Yes, I'm able to go into the bootloader.
I tried clearing the storage, choosing fastboot, etc. The phone seems to be working, just won't boot past the static X.
From your last reply, you're saying passimg has good chances to fix my phone. What does that involve? Do you have a link to a how-to that I could follow (it would really be a bad time for me to brick my phone, a good how-to would be really appreciated).
Cheers!

Yes passimg is used for many things it just reflashes a shipment ROM to the phone through bootloader. Like I said you can visit the wiki to have a how to here is a link http://forum.xda-developers.com/wiki/index.php?title=Nexus_One/Guides_%26_Tutorials scroll down to "Unroot / Restore your Nexus" then follow the instructions. This should restore you to frg33 then you just need to update back to 2.3.4.
NOTE: this will wipe your data.

Ahh there's a way to unroot the nexus one now!
I had no idea! This is good to know (last time I checked was in December I think).
I will give that passimg a try as soon as I get home.
Can anyone confirm that this ("Attention: Latest stock ROMs don't flash using PASSIMG.ZIP method. Use the provided latest Froyo PASSIMG, and upgrade it after flashing.") means I can still reflash using this if I have the latest ROM (2.3.4) but will simply have to update again after (which I might not do given the issues I'm facing).
Cheers!

Confirmed - Dude is giving you good info... xD

Just to verify, unrooting is not the same as relocking. If you unlocked your bootloader (have a little lock symbol under the X screen), there is no way to relock it.
But the passimg is a good option. It will take you back to an older version of Android, and then you just let the system update itself.
Since you are out of your warranty, I can highly suggest looking into custom firmwares. These give you a lot more features and in many cases, perform better. CyanogenMod is probably the most popular one. These will fully replace your Android OS. CyanogenMod really doesn't even differ in look from stock all that much. Most people probably wouldn't even have a clue they are running something different, except for the stability and performance increases.
You can read up about this stuff in the wiki as well.

Oh, I see, thanks for the info.
I'm actually trying to get the FRG83 passimg file but the link is dead. Does anyone have an alternate one?

Use the FRG33 image

Alright,
I unlocked the device, used fastboot to write the recovery "Amon_Ra's Recovery".
Then I rebooted, went to the bootloader (trackball + power), went to "recovery" but the phone still gets stucked on the X (with the unlocked padlock logo).
Any advices?

Try the passimg, but it's possible that you are looking at hardware failure...

ldiamond2 said:
Alright,
I unlocked the device, used fastboot to write the recovery "Amon_Ra's Recovery".
Then I rebooted, went to the bootloader (trackball + power), went to "recovery" but the phone still gets stucked on the X (with the unlocked padlock logo).
Any advices?
Click to expand...
Click to collapse
If you are still running stock Android, you can't reboot between installing the recovery and getting into it. Stock Android will replace it. Try to go back to the bootloader and select recovery then, or fastboot to load the recovery, and then use fastboot to boot off of it.
Code:
fastboot flash recovery "c:\location to\recovery.img"
fastboot boot recovery "c:\location to\recovery.img"
Hopefully this will get you into Amon_RA so you can try again.
But the passimg method is used in the bootloader, not in recovery. You don't need a custom recovery to use the passimg method.

Amazing, thanks for pointing out my mistake, that give me a little bit of hope now . (I was at the point where I'd open the thing and look for a broken solder joint.)
I will try this as soon as I get home!
**Edit** I actually am not sure if I really rebooted or went straight to recovery. I'll update this thread tonight.

According to some other people, this would be a common issue with the internal memory dieing.
Is there a utility I can use to check the state of the memory?

None that I know of. Our phone internal memory uses the yaffs2 (Yet Another Flash File System v2) file system. I haven't heard of any programs that can check it.

Same situation
Hello, all. I haven't signed in on here in ages just because I've been so happy with how my Nexus has been running.
I ran into the same problem as OP stated.
I think I have some sort of hardware issue because my phone used to randomly freeze and couldn't be restarted unless I pulled the battery. Now it's at the point where I can't even turn it on because nothing happens when I press the power button or if I try to boot into recovery. This is really frustrating.
Is there any way to check for hardware damage? My warranty is over as well so I'd have to pay for any repairs to my phone if I sent it in.

If it's running, you can try to pull a log, and see what error reports you get?

andythefan said:
Now it's at the point where I can't even turn it on because nothing happens when I press the power button or if I try to boot into recovery. This is really frustrating.
Click to expand...
Click to collapse
Your power button might just be dead. Try having the phone plugged into a power source and removing and reinserting the battery. While you are doing that, hold the Volume Down button. This will get you into the bootloader which would allow a passimg to be performed. Hopefully your reboots aren't a hardware problem.

So , after pulling my battery, pulling the sim and the sd card, it finally turned on and went to recovery without freezing. I was able to wipe and reflash cyan 7. It's working well for now, but I'm really afraid this is going to happen again because this isn't the first time that it's just froze repeatedly.
Does anyone know what the problem could be?

Alright,
I did "fastboot flash recovery MYIMG" then "fastboot boot MYIMG", didn't work.
Then I tried "fastboot flash recovery MYIMG" then go to bootloader (without rebooting) and selected recovery.
Still no luck.
It always freezes on the static X logo. What else can I do? Will using passimg be any different (I don't have any way to put the file on the micro SD card but I can manage to do it if it's worth the shot).
Thanks

[Q] Nexus One Stuck on Boot X

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?

Massive problem with the tablet

I have spent about 10 hours sitting here, with over 200 tab open trying to find a solution to my problems but I could not find one. My last option is to post here and hope someone can help me out.
I recently bought the tf701t which came with Android 4.2.2. Everything worked fine. A few days ago, I got pushed an update to android 4.3 but it was .1.7 not .1.18 (the newest apparently). With that update, my problems came. When I light up the device by pressing the power button, the lock screen was unresponsive. I pressed my pin numbers in but there was no response and it was as if the touchscreen was broken. However, the home and back button were all working fine. I had to randomly keep pressing until it finally started becoming responsive. When I got in, the quick management window (the one you get by swiping down), kept popping up the moment i press the screen. Because of this, I couldnt do anything. I couldn't even turn off the tablet as the power off option was unable to be pressed by me (When i did press, the window came up again).
After a while, i managed to get around this by again randomly pressing stuff. I got really frustrated and decided maybe if I install a custom rom, this problem might be fixed.
I read around a bit and found that the CROMix rom required firmware 1.18, which I did not have. Because of this, i decided to try install 1.18. First i used the asus unlock tool. Next I tried booting into recovery but here I met my problem. I have guides telling me to first boot using power button + volume down key. This worked. It then told me to choose the RCK option and press the volume up key. This however, did not work. When I selected the RCK option, the android figure appeared lying down with a red triangle and exclamation mark over it.
Unsure of what to do in this situation, i read one of the guides on this forum which said simply place the 1.18 zip file (yes i unziped the zip file from the file i downloaded), in the root folder then reboot and it would automatically update. This didnt happen.
I then tried using the adb thing but it said no devices were connected even when my tf701t was connected to the PC. I guessed that I needed to be in the recovery mode that I could not get into, before it would work.
I then read around and they said I had to first get Rom manager + the CMR recovery thing but Rom Manager said it needed root access. In order to get root access, I needed to get into the recovery mode yet again.
So now I am stuck. Whenever I try the RCK option, the error pops up and I can't get any further.
WIll someone please help me? I have no idea what to do anymore except throw the tablet out.

zhuang281 said:
I have spent about 10 hours sitting here, with over 200 tab open trying to find a solution to my problems but I could not find one. My last option is to post here and hope someone can help me out.
I recently bought the tf701t which came with Android 4.2.2. Everything worked fine. A few days ago, I got pushed an update to android 4.3 but it was .1.7 not .1.18 (the newest apparently). With that update, my problems came. When I light up the device by pressing the power button, the lock screen was unresponsive. I pressed my pin numbers in but there was no response and it was as if the touchscreen was broken. However, the home and back button were all working fine. I had to randomly keep pressing until it finally started becoming responsive. When I got in, the quick management window (the one you get by swiping down), kept popping up the moment i press the screen. Because of this, I couldnt do anything. I couldn't even turn off the tablet as the power off option was unable to be pressed by me (When i did press, the window came up again).
After a while, i managed to get around this by again randomly pressing stuff. I got really frustrated and decided maybe if I install a custom rom, this problem might be fixed.
I read around a bit and found that the CROMix rom required firmware 1.18, which I did not have. Because of this, i decided to try install 1.18. First i used the asus unlock tool. Next I tried booting into recovery but here I met my problem. I have guides telling me to first boot using power button + volume down key. This worked. It then told me to choose the RCK option and press the volume up key. This however, did not work. When I selected the RCK option, the android figure appeared lying down with a red triangle and exclamation mark over it.
Unsure of what to do in this situation, i read one of the guides on this forum which said simply place the 1.18 zip file (yes i unziped the zip file from the file i downloaded), in the root folder then reboot and it would automatically update. This didnt happen.
I then tried using the adb thing but it said no devices were connected even when my tf701t was connected to the PC. I guessed that I needed to be in the recovery mode that I could not get into, before it would work.
I then read around and they said I had to first get Rom manager + the CMR recovery thing but Rom Manager said it needed root access. In order to get root access, I needed to get into the recovery mode yet again.
So now I am stuck. Whenever I try the RCK option, the error pops up and I can't get any further.
WIll someone please help me? I have no idea what to do anymore except throw the tablet out.
Click to expand...
Click to collapse
Did you try to put the update on the external sd card? Not sure if that would make a difference but i remember i used to put it there...
You could also flash a custom recovery and flash the update that way. You can find more info in this thread:
http://forum.xda-developers.com/showthread.php?t=2636093

You should safely be able to update your factory firmware first by putting it at /sdcard location.. Then just reboot. It automatic. I Thought there was also an update available in settings after that. Don't unlock til you are at 4.3.
To unlock with Asus unlock tool make sure Google 2 Step verification is disabled.
Then I used fastboot to flash CWM recovery from a computer. I think you flash with fastboot from the newly unlocked bootloader. Power + Vol DOWN.
After you have flash recovery then you can enter it. No scary man lying down.

YayYouFixedIt said:
You should safely be able to update your factory firmware first by putting it at /sdcard location.. Then just reboot. It automatic. I Thought there was also an update available in settings after that. Don't unlock til you are at 4.3.
Click to expand...
Click to collapse
I forgot to mention one thing at the start. I don't actually have on hand a external microSD card. Which I think might be why placing the zip file in the root of the internal storage did not work.
Should it work? Is there any way to get around it? I've been trying to use sideload with cwm (finally got cwm working), but it comes up with "failed to write data protocol fault no status"
EDIT: Through cwm, I chose "choose zip from /sdcard" then select the "0" file directory then i found my zip at the location. I selected it and confirmed install. However, it then comes up with "Error in data/media/0/(name of update here).zip status 6"
Thanks for the help so far but anyone have an idea about this?

Not sure. After googling I see this
http://forum.xda-developers.com/showthread.php?t=1535546
---------- Post added at 09:54 AM ---------- Previous post was at 09:45 AM ----------
You can put the zips anywhere when your recovery is installed.

Okay so I finally managed to get the custom rom installed and working. However, this did not fix my problem with the touchscreen. I think it is because it only changed the firmware but not the android version (still 4.3).
Is there any place I could find android 4.2.2 rom? This was the one the tablet was on before the update that screwed everything up. If I could downgrade to that version, it may work again.
Thanks
I gave up and just put on the android 4.3 ota from droidbasement. Now the tablet randomly restarts and is stick in reboot loop. It wont even allow me to boot into cwm recovery to delete the cache. But i accept that I now have a $600 piece of **** on my hands. Going to bed. Night.

Ya i dont like the whole void your warranty for "using it" idea. If it responds to fastboot you might be ok.

You should be able to download a 4.2.2 rom from Asus' website (.47 was the last build for 4.2.2). You can use fastboot to install it.

Alta1r said:
You should be able to download a 4.2.2 rom from Asus' website (.47 was the last build for 4.2.2). You can use fastboot to install it.
Click to expand...
Click to collapse
I tried that before but it stated "update aborted" immediately after i pressed confirm, in CWM.
But all that is in the past now. I am pretty sure that the tablet is hard bricked since it no longer even opens bootloader. I accidentally pressed the wipe data option and I read that irreversibly damages the tablet. When I hold pwr+vl down, nothing happens anymore, it keeps on its reboot loop.