Hi everyone,
My N1 is stuck on the X, but my problem seems to be different to the other "my nexus is stuck on X" threads, as I've tried everything that was suggested and am still stuck...here is as much info as I can give.
My phone is rooted (has been since day 1 when it first came out) but I had not used it in a while.
The last rom I had on there was Cyangenmod 5.0.5 (or something like that.)
I booted into recovery (amon_ra from back in the days) and tried to flash Cyanogenmod 7.
The phone booted up, got passed the X but got stuck on the android on the CM circle with the rotating arrow...only the arrow was not rotating.
Anyway, I went back into recovery, and tried again...same thing...so I tried 5.0.5 and that worked.
Happy with my success I tried to install clockwork and try again...
this time, the phone got stuck on X...
tried going back to 5.0.5 but again, phone stuck on X.
So I tried to go back to stock.
fastboot flash boot boot.img and user data.img worked fine but system would fail.
I tried the PASSIMG.zip, but 7) system was fail-PU
read some more and some people said that with hboot 0.35 this was not possible, so I managed to downgrade to 0.33, but that didn't help either.
I've tried Clockwork and Amon
older roms and newer ones
PASSIMG.zip from different sources...nothing has worked.
In hboot now i have 0.35 and underneath I have a B (which I think is for amolded)
I've can't seem to get ADB to work either...I have done in the past, but for some reason this is not working for me this time...fastboot yes.
Could anyone PLEASE help me...
Thanks,
Lou
Fail-PU means Failed Partition Update, means your internal memory on /system partition couldn't be written, means a dead NAND, means your phone is really bad.
You could try to recover from it by using Blackrose hboot, and repartitioning the device.
Blackrose it is...I'll try that..thanks
L
So I got blackrose on, but that didn't help...still the same thing...
I've given up on the phone, but I'd still like to solve this, now that I've devoted som much time into it
L
You don't need to just load Blackrose, it won't solve a thing. You need to repartition your phone, making sure that the /system partition isn't sitting on the bad block. Try to move /system partition forward, making /data smaller.
I partitioned it as per the blackrose thread...are you saying i should use different values? could you recommend some to try?
L
I can't, because I don't know where the failure might be on the /system partition.
Try to change values between /system and /data, for example (move /system into /data). Just for testing. You'll need to find some position for it that won't cause write failures, and there's nothing I can suggest but to try and see at what address the failure seems to be, and repartition in such way as to exclude this address.
Related
i have a class 6 adata 8gb 2gb ext4 64mb swap rest fat32
im running cyanogen 4.0.2 or 4.0.4 whichever one i load up from sd at the time, but both are stable. i have newest radio and spl also. the issue is simple. i can get into recovery mode and bootloader menu. everytime i reboot it goes to bootloader menu(3 skateboards). camera button is not held down either or stuck. the only way to get past this screen is to evertime i reboot to factory wipe and install new rom which is a pain. i was wondering if by having the original image DREAIMG file in a folder on my sd is whats causing this. but now that i cant get past this screen i cant remove it from sd. i also already tried mounting sd to comp from console using: "ums_enable" it does nothing(tried it on 3 computers). im tired of reseting and reflashing. pls some assistance.
Have you tried to reflash the SPL? You could just redo the entire root process and replace everything.
New Isuue, Same Problem
Sorry it took so long to get back here. No I haven't tried that. How could it be the SPL? Im asking it in a meaningful way, like why and/or how could it be?
I will reflash the SPL tonight and edit post if it works.
I also erased my sd card and re partioned in in "parted" it booted fine. The battery died today and i rebooted it and BAM! bootloader screen again. So i factory reset and flashed a new ROM image. then it worked fine. now only problem is the private apps i have installed wont work and they get stuck on uninstalling....Whats the fix for that?
Thanks XDA!!
You need to start over and replace everything. It sounds like you have multiple problems. Use THIS guide starting with the downgrade bacause it will reflash EVERYTHING on your phone. If the problem persist then it's hardware issues. Redownload everything, don't use anything you already downloaded because these files might be bad too.
Hello, I recently updated to the latest cyanogen. After several times of it loading and working (although not completely as the home button did not seem to work), the device failed to boot. I can get to the recovery section (in which the home key works). I have since tried everything thing I can think of, wipe/factory reset, reload cm rom, load old version of cm, reflash recovery image, fsck (automatic and manual), take the sd card out, repartition sd card, reflash radio image. The device will still not boot beyond the g1 screen. However I can get to the adb shell when it is at the g1 screen. Here is the logcat from that point: http://clarkehackworth.com/logcat.txt and the dmesg: http://clarkehackworth.com/dmesg.txt
at the bottom of the logcat it says:
"I/vold ( 127): Aborting start of /sdcard (bootstrap = 1)
I/vold ( 127): Volmgr not ready to handle device"
I am not sure why it is aborting loading the first partition (vfat) and/or why the volume manager is not ready to handle the device.
btw, I followed this guide to partition the sd card (http://androidandme.com/2009/08/news/how-to-manually-partition-your-sd-card-for-android-apps2sd/)
So maybe this is a problem with my sd card, but I have not seen any read/write errors, and I have completely repartitioned the sd card with still no luck.
I have tried booting with out the sd and I get basically the same thing. I know that cyanogen will not work right with out the sd card because of apps 2 sd, but I think it should get farther than it does (let me know if I am wrong). Here are the log files with no sd card. http://clarkehackworth.com/logcat-nosd.txt
http://clarkehackworth.com/dmesg-nosd.txt
Does anyone any any ideas of what could be going wrong?
p.s.
And before people start yelling about this problem is common and I should google it, I have and I have not found many others with the exact problem (at least as far as I can tell) and definitely not a solution.
Thanks
First of all u r in wrong section this belong in Q&S
Second what SPL & Radio u r on and did u flash OTA recovery b4 u flashed cy?
Sorry for posting in the wrong section.
I did not realize I had to install the OTA recovery image (which is different from the cm recovery image), as I had not had to do so before with cm 4.2.8. I went to HTCs site (http://developer.htc.com/adp.html) and tried to get it, however I think they no longer have the download links there. I did a google search for it and found another site that had it (and made sure the md5 was correct). I installed the OTA recovery and then reinstalled the latest cm. This seemed to work for me. Thanks for your help.
HTC Dream 1.6 Image
There you go
clarke.hackworth said:
Sorry for posting in the wrong section.
I did not realize I had to install the OTA recovery image (which is different from the cm recovery image), as I had not had to do so before with cm 4.2.8. I went to HTCs site (http://developer.htc.com/adp.html) and tried to get it, however I think they no longer have the download links there. I did a google search for it and found another site that had it (and made sure the md5 was correct). I installed the OTA recovery and then reinstalled the latest cm. This seemed to work for me. Thanks for your help.
Click to expand...
Click to collapse
Well if this help u here its the link how to do everything step by step with cyan wiki
http://wiki.cyanogenmod.com/index.php/Main_Page#How_do_I_upgrade_to_the_latest_CyanogenMod.3F
i hope this can help u i had that problem long time ago and i know how it feels to find the answer by ur self
First of all, I have checked around quite a bit on this forum as well as others to try and avoid having to ask a question that's already been answered. Here's my problem/ what happened. I was rooted (one-click with locked bootloader) and had tried out several roms for a couple of months now. A few days ago I reverted back to an old stock 2.2 backup. My phone received two ota updates and I'm pretty sure I lost root. I had just went on using the phone for about two days when I ran into a problem today. After shutting the phone off I have now become "stuck" at the initial "X" screen (not animated). I pulled the battery and tried again several times. I then tried to reboot into recovery from the bootloader/ 3 skateboards screen with no luck. Any time I hit recovery it simply takes me back to my stuck "X" screen. I have an entire backup of my SD card from earlier as well as at least 4 nandroid backups (one of which was the stock 2.2 before the latest ota). I am thinking I need to somehow put clockwork recovery back on my phone so I can restore to one of my backups. I do not know how to do this. Sorry for the lengthy post but I want to provide as much information as possible. Any help at all would be greatly appreciated.
Just like you restore to stock 2.2. You should have used recovery.img. use adb fastboot to put the stock or anom recovery. I am not am expert but I have had the same problem few times. Always use adb commands
Sent from my Nexus One using Tapatalk
Does my n1 have to be in usb debugging mode because it's acting like it's not connected or something. I get the message "error: device not found." I'm on the fastboot screen on my n1 and using terminal on a mac. I usually didn't leave debugging mode on
No it doesn't but you have to have the drivers installed as well as the SDK with dependencies.
Whew! Thank God! I ended up getting a FRG33 stock rom onto the sd card and the bootloader detected it. I'm not sure what happened but when I tried recovery after that it took me to the android with an "!" point (meaning no recovery?) and then back to the X. This time however it loaded on through and went right back to the way it was before it was stuck. Again, not sure what happened but thanks for the replies and help.
fastbook oem unlock
install Amon RA recovery
flash new rom.
Caseyp789 said:
Whew! Thank God! I ended up getting a FRG33 stock rom onto the sd card and the bootloader detected it. I'm not sure what happened but when I tried recovery after that it took me to the android with an "!" point (meaning no recovery?) and then back to the X. This time however it loaded on through and went right back to the way it was before it was stuck. Again, not sure what happened but thanks for the replies and help.
Click to expand...
Click to collapse
The exclamation mark is just the stock Android recovery - it was re-installed when you loaded the stock FRG33 ROM.
Performing OTA updates requires you to have the stock recovery installed. Simply reverting to a stock 2.2 nandroid isn't sufficient, so trying to install those OTAs (which should have failed without stock recovery) may have broken something there.
GldRush98 said:
fastbook oem unlock
install Amon RA recovery
flash new rom.
Click to expand...
Click to collapse
This is by far the easiest (and safest) way. Google/HTC provided us an easy and safe method for gaining full access to our phones.... Why so many people refuse to use it is beyond me. If you root it the proper way (with fastboot oem unlock), it will make recovery from any further issues a lot more simple.
From what I can tell, I am having the same symptoms as the topic creator. I believe the problems started during a failed flash of cyanogenmod 6, but I am not sure by what means the flashing took place.
I can't boot the phone normally, it hangs on the X splash screen and the same occurs when trying to enter recovery mode.
I have tried the passimg approach to fix this, it either doesn't recognize my zip or starts loading it and freezes on a loading bar.
Fastboot flashing recovery completes, but doesn't fix the issue.
I can fastboot flash every image partition except system or radio, both hang.
As danger rat and dude random both know, I have posted this problem on the nexus one forums but I thought I'd post here to have some more minds look at it.
The Story:
I bought a new Nexus one.
Got the OTA updates and updated the phone (first 2.1 then 2.2 and 2.2.1)
Since then the phone is not rebooting properly. usוally it just reboot and reboot and reboot.
After I formated the SD card the phone booted succeussfully but crashed again after a minute back to the endless loops.
can someone please help?
I tried to unlock the bootloader, root the device and flash Amon's recovery but although the cmd windows said that it ewent alright besides of the open lock sign nothing seems to change.
Please Please Please Help, It's a brand new phone...
p.s.
if there is any way to just erase everything (already tried earse cache and userdata from the recovery...) and get a "new" phone - please tell me how.
I know how to use adb/fastboot, I'm not a noob...
Thanks a lot!!!
Where is my question...?
I can't find it...
It's right here.
Anyway, I suspect your problem after flashing recovery is you're rebooting, and the OS is reverting to stock. Go straight into it first, take a backup and wipe it.
Failing that you'll need to grab FRG83 image from http://developer.HTC.com and use fastboot to flash over system.img and boot.img
You'll be able to format every partition on your Nexus One by using Clockwork Recovery.
By Amon's recovery you can do similar thing but it doesn't offer ability to format System partition (it's not quite useful to format System partition anyway..)
You mentioned that your phone could boot successfully with a formatted SD card and then ran into problem, my guess is that your SD card has bad block(s), please verify this by take your SD card out and use your phone for few hours, is there any stability issue?
so... an update:
I downloaded the original files and flashed them all in fastboot (recovery.img, userdata, boot and system).
The phone is on the "nexus-one sign" screen for over then half an hour now and nothing seem to change.
a. Is there somthing else that I should do? how long it should take...?
b. what are the odds that it's a hardware problem...?
c. could it be a problem related to incompatible radio?
Thanks...
and other update...
even after reflashing the original files I can't enter recovery (original) so I guess the problem lies within it.
with this information and the other messages - does anyone has an idea...? please...?
did you try another SD card?
try this and let me know if it works
kuldrivedotcom/host/n1/Back2Stock.zip
just unzip the file and follow the instructions.
let me know if it worked
nexus @ kuldrive dot com
PCNemy said:
try this and let me know if it works
kuldrivedotcom/host/n1/Back2Stock.zip
just unzip the file and follow the instructions.
let me know if it worked
nexus @ kuldrive dot com
Click to expand...
Click to collapse
Thank you, but the problem solved.
It was a big HARDWARE problem.
HTC knew right away what the problem is.
Sent the phone to HTC, got it back in 3 days, everything work just fine since.
Thanks anyway...
I have a Verizon Galaxy tablet 7 inch the original one. I have had many custom roms on it in the past. Recently I had AOKP on it...I am not sure what build. For some reason my kids were playing with it and it would not boot up. I went into recovery and tried flashing AOKP and it would stay locked up on the boot screen. I eventually tried flashing all ICS roms with no success. I eventually ended up trying to go back to stock. I can get into download mode with and communicate with Heimdall and/or Odin. The problem is that every thing I flash goes into a boot loop. when I go into recovery I get an unable to mount error like E: unable to mount cache and one for kernel and about 6 more. I figure that there is something wrong with the file system so I have used a pit file when I flashed with no success. I am not sure if there is an issue with the file system being the wrong type or if I have to many partitions now. I know that the mount error in recovery is where the problem has to be. If someone could please point me in the right direction. I have been all over these forums.
Thanks,
Leroy
In order to determine if it is file related. Try to do a full wipe right after the Odin.
That is all 3 Wipes (Cache,Dalvik,Data)
Also check all the boxes on the right side of the Odin screen to flash the stock rom.
Well I got a little further now it boots up after 5 minutes and states encryption unsuccessful and asks to reset tablet. There is some threads on this so I will get to trying to resolve this. In fact I just realized this is how everything started off I didn't read the message and powered it down. So it must have started on its own or from the kids playing on the tablet.
Is there any way to determine if your internal memory is shot. It seems like there is a problem mounting my internal memory > emmc?