Related
Went to root with his one-click method instead of the usual way and i'm running into a problem.
I first had to downgrade to rc29, then update to cupcake. No problems. Then I had to put his flashrec.apk and Amon on my phone. Did that no problems. I used flashrec-1.1.3-20091107-2.apk from his link and also Amon 1.5.2. It seemed like all that went fine. I checked my radio and it was 2.22.19.26I so that's fine. But I wanted to upgrade to dangerspl.
I got dangerspl, put it on my card, renamed to update and booted up into recovery. Did a wipe, and applied update, did a reboot and it's getting stuck at the g1 splash screen. I pulled the battery and can boot back up into recovery or fastboot.
I also tried to do a nanbackup and it's giving me the error "error: Run nandroid-mobile.sh via console"
My options are a little different in recovery than his as well. I only have USB-MS toggle, backup/restore, flash zip from sdcard, wipe, partition sdcard, other Not sure where I went wrong, any ideas?
Sounds like you are all good, just don't have a rom flashed. The SPL probably wiped what you had. Download a rom and flash it like you have the other parts. Some roms take some extra effort. Cyanogen is a complicated mess so maybe you should try Super D or WG first. You will have to rename it to update.zip if you don't have the "flash any zip" option in recovery.
Yeah Danger SPL formats the NAND, so you everything is wiped including the ROM...
ah ...ok that explains it.
So basically, i'll take my card out, put it in the comp and i'll put super D 1.8 on it that way, rename to update and boot into recovery then flash it?
Should I partition for a2sd before or after I flash the rom?
If you have the latest Amon Ra Recovery then you dont have to rename it to update.zip but yeah thats basically it.
Dont know bout the A2sd though.
Thanks, i'm up and running. I partitioned before I flashed super D.
Last night I was freaking out, I thought I bricked my phone again Thanks for the help
lol thats happened to me so many times I almost had a heart attack haha.
I searched before I posted this question since I know it is a common question but I can't seem to figure out the problem with my phone.
I recently just bought it and I decided to root it. I following the instructions from wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_Nexus_One_Firmware_to_CyanogenMod When I went through the instructions, everything went through smoothly. No errors, all were complete installs but my Nexus One is stuck at the boot screen now. I waited for over 20 minutes but it wouldn't budge at all. I've done the procedure after "fastboot oem unlock" and "Flash CyanogenMod" already but it doesn't seem to make a difference. The flash that I'm currently using is the update-cm-5.0.5.1-N1-signed and gapps-passion-ERE36B-2-signed. Do you have any idea what could be wrong with it or what do you suggest any steps I should take to fixing it?
I don't think my phone is bricked since I'm able to go into Bootloader mode and Recovery.
Try a wipe and if not reflash and re wipe.
Mine is doing this too and i did exactly what OP did
Even after a wipe. Im reflashing right now
5.0.5.2 has just been released. Apparently fixes this bug. get it while it's hot.
Its still taking forever to boot. Im still watching it. What exactly do i do to do a "Wipe"?
Damn I don't have a microSD reader. =\
Is there any way to put the ROM on the microSD via Nexus One?
I'm having the same problem. This is on the recently released ATT compatible N1. I am able to go into Amon_Ra's 1.7 recovery and successfully install the V5.0.5.2 and gapps-passion-EPE54B-signed.zip but still have the same problem. Stuck on the X with the lock. I keep putting the original Rom back and doing it again after a full wipe and still have the same problem.
you dont have your usb cable? I was thinking about that too. Cause i know the nexus has its own memory internally but it doesn't show up under my computer. maybe you can push files through command prompt or something. or on linux
If you have the Amon_Ra's recovery you can do a wipe once you're in recovery.
If you made a backup of the original rom you can just put that back and boot into the original rom. once there, you can mount the usb and download it to the sdcard
you can also download the cyanogen updater from the android market and download the rom to your sdcard to install.
What did the trick for me was fresh install of Cyanogen 5.0.5 which i got to boot succesfully AND THEN use cyanogen updater to get to 5.0.5.2
jekyoo_style said:
Damn I don't have a microSD reader. =\
Is there any way to put the ROM on the microSD via Nexus One?
Click to expand...
Click to collapse
2 ways, either plug it in via usb and mount it from your notification bar on the phone, or download the rom via the web browser on your phone, then use Astro file browser(free) to move it from downloads to the root folder of your SD card, then flash from recovery.
dropshipinc said:
If you have the Amon_Ra's recovery you can do a wipe once you're in recovery.
If you made a backup of the original rom you can just put that back and boot into the original rom. once there, you can mount the usb and download it to the sdcard
you can also download the cyanogen updater from the android market and download the rom to your sdcard to install.
Click to expand...
Click to collapse
How long does it usually take to restore? I have about 18 lines of dots. Should it be taking this long?
5.0.5 first then update
Install the base 5.0.5 first then the google add on if you want the apps. After you boot like that update to the latest CM. I saw this some other place and this worked for me, don't wanna take anyone's credit.
Thanks everyone. 5.0.5.2 worked flawlessly once I was able to put it on my microSD.
If you guys don't have a MicroSD Reader, and have the AmonRA recovery, just boot to the recovery and chose I think the 3rd option (Toggle MS USB). You'll be able to see the phone as a mass storage device.
Please delete this post
Smallsmx3 said:
flashed back to jf6 via one click twice now. master cleared..... everytime i try to boot into recovery i get into 2e. dont flame me just help. anyone else have this issue before?
Click to expand...
Click to collapse
Did you put the update.zip on your internal SD card? If not I have attached it to this post. Please be careful in the future where you post though. There are a few bad apples that will rip you apart.
More info is needed to help you out. What setup where you running before?? Do you have the correct update.zip for CWM on the root of your sd and are you reinstalling packages x2 in 2e recovery and its not working or what?? Pretty vague in the OP.
EDIT: If you master cleared it wiped your sd and you need to put the update.zip that adamholden posted back on your sd.
whats the update.zip file? root access? I have root. everyone knows if you post in general you dont get replies.....
The update.zip that he posted is not root. Its for CWM and you should always keep it on your internal sd to always have CWM available. Just move the zip to your SD and select reinstall packages two times for the green txt CWM recovery.
was on eugenes gingerbread themed rom... going from r2 to r3....failed at line 2 so I one clicked....master cleared and everytime i try to get into CWM recovery 2e boots up instead.....i have root
silverslotcar said:
The update.zip that he posted is not root. Its for CWM and you should always keep it on your internal sd to always have CWM available. Just move the zip to your SD and select reinstall packages two times for the green txt CWM recovery.
Click to expand...
Click to collapse
i didnt know this existed....thanks...ill try it out
Smallsmx3 said:
whats the update.zip file? root access? I have root. everyone knows if you post in general you dont get replies.....
Click to expand...
Click to collapse
CWM is an update.zip file on your sdcard (assuming your not using a kernel with it baked in). What happens when you hit reinstall packages, is that it takes the CWM update.zip and flashes it, replacing 2e with CWM. If you don't have that update.zip on your sdcard, then you won't be able to get to CWM.
Yea, have you ever been in rom manager and had to "Flash Clockwork Recovery." Well thats what it is doing. Its putting CWM recovery as an update.zip on your sd. You should be good to go once you do that.
I had the same thing happen to me. I will list what I did step by step as best as I can remember not because all of it is necessarily relevant, just for a frame of reference:
i. Odin 1 clicked to stock
ii. one click root
iii. installed CWM from market
1. Opened CWM, selected install rom from SD card, did not check backup rom or wipe data.
2. Phone rebooted into stock recovery screen, selected reinstall packages, rebooted phone.
3. Repeated step 1 and 2 about 10 times with nothing happening. (Normally, the second time I go through this process, it installs the rom)
4. I tried selecting "Reboot into Recovery" (the manual option) but still nothing happened, it was taking me to the 2e stock recovery.
5. I went back into CWM and selected "All CWM Recoveries" and flashed the older version 2.5.1.1
5. Selected "Reboot into Recovery" again and the CWM recovery window came up and I was able to manually select my ROM from there.
Thanks for Clockwork Mod save
Thank you!!!! Like the previous poster I couldn't get into Clockwork to flash a new ROM altho' I went into recovery at least a dozen times - your fix worked! I downloaded an earlier Clockwork and that instantly took me to the correct screen. A million thanks, I thought I would be stuck in 2.1 for the life of the phone since it wouldn't flash.
dslsurfer said:
Thank you!!!! Like the previous poster I couldn't get into Clockwork to flash a new ROM altho' I went into recovery at least a dozen times - your fix worked! I downloaded an earlier Clockwork and that instantly took me to the correct screen. A million thanks, I thought I would be stuck in 2.1 for the life of the phone since it wouldn't flash.
Click to expand...
Click to collapse
Glad that you found a fix haha
So if I goto ROM Manager, I can successfully install CWM. I goto "Reboot into CWM" and I get a install error when it tries to boot. I am able to boot into CWM via MicroSD card but NOT from just my Nook device. I had some issues a few days ago where I accidentally whiped the /system and /data. I've since fixed it (i thought) but I cant help but think this issue is related.
Any ideas...?
DroidHam said:
So if I goto ROM Manager, I can successfully install CWM. I goto "Reboot into CWM" and I get a install error when it tries to boot. I am able to boot into CWM via MicroSD card but NOT from just my Nook device. I had some issues a few days ago where I accidentally whiped the /system and /data. I've since fixed it (i thought) but I cant help but think this issue is related.
Any ideas...?
Click to expand...
Click to collapse
I had this problem too. It happened to me, because I had screwed up the boot partition. I had to restore to stock, and then re-nooter to fix it.
I have the same problem running nookie froyo from emmc. I've tried a bunch of different things but have never been successful.
I was able to get it working on stock rooted fine thouhh. Has anyone successfully gotten clockwork running with nookie froyo without using the clockwork sd boot?
philburkhardt said:
I had this problem too. It happened to me, because I had screwed up the boot partition. I had to restore to stock, and then re-nooter to fix it.
Click to expand...
Click to collapse
Was it easy to restore to stock?
I would download the repartition boot from http://forum.xda-developers.com/showthread.php?t=929670 , put it on the micro sd along with CWR and flash. This should fix your boot partition, which you then can reinstall CWR if you so desire.
If that doesnt fix boot then use http://forum.xda-developers.com/showthread.php?t=931720
volwrath said:
I would download the repartition boot from http://forum.xda-developers.com/showthread.php?t=929670 , put it on the micro sd along with CWR and flash. This should fix your boot partition, which you then can reinstall CWR if you so desire.
If that doesnt fix boot then use http://forum.xda-developers.com/showthread.php?t=931720
Click to expand...
Click to collapse
will this work on my Nookie froyo on emmc?? without wiping my data?
I am struggling with the exact same issue. I used the Monster Root Pack to restore my messed up NC 1.1 this weekend. After i got everything back to 1.0.1, I have been unable to do a nandroid from CWM. It kept failing. After some searching on this forum, I found that the CWM zip that is included in Monster Root Pack isn't working. So I tried to flash the zip from CWM thread. That errored out, too! I'm glad I found this thread.
So, what does the repartitioning boot do? How would that fix the issue of CWM not flashing? Also, does flashing the repartition force me to have to go back to stock?
Anyone have any success with this?
Preston
Is there a way to get rid of the clockwork mod boot on the nook color
As per onstuctions on this site, I got a 1.1 pre roote version and installed it
from the sd card with the clockwork menu which informed me that the
"NookColor" install complete.
when I reboot, it starts with the welcome message,but then only reboots into the same recovery menu.
At this point I would just like to go back to a stock rom, but cannot boot anything but the recovery.
By the way, I can boot froyo from the sd card
Please help me
I've moved your thread to the correct forum.
So you dont have the CWR sdcard in? Because if you did, you would need to remove that first. Sorry if this dumb, but thats all I can think of right now. Maybe reflash the 1.1 pre rooted rom? Or follow the instructions in Samuelhalff's "Easily restore to stock" thread located here in the Nook forums.
The "Easily restore to stock" saved the day. I am now up and running.
Thanks
How did you do that? I have CWR on mine and I went to buy a book from the shop on the Nook and it downloaded and installed 1.1... Now when I try to go back and restore from backup CWR doesn't respond... All it does is sit there and if I select something from the menu it goes to the background image (the circle with the top hat) and sits there. I would like to remove this so I can reroot my Nook...
Thanks for any help.
Bob
See the other thread or sticky that's labeled "How to Restore to Stock easiliy." I believe you can also use the power down and on 8 times trick to restore to stock as well.
Same thing happened to me. I used Clockwork to flash the CWR-removal.zip on the restore thread mentioned above and it fixed my boot, everything else was OK.
porear said:
Same thing happened to me. I used Clockwork to flash the CWR-removal.zip on the restore thread mentioned above and it fixed my boot, everything else was OK.
Click to expand...
Click to collapse
Ditto that. I reinstalled CW and everything seems to be working fine. Has anyone else had issues with using Rom Manager on the NC? I've had to go back to stock twice whenever I've used it.
I had a problem when trying to roll my 1.1 rooted NC back to stock because I futzed it up that I ended up in a CWR loop. 8 resets didn't get me a reflash, it got a recovery. Took me finally getting the NC flashed and rerooted at 1.1 a second time when I reinstalled ROM Manager and ended up with the problem again. Took me this wasted effort to realize that CWR runs in lieu of the reflash if CWR is installed and that's an obvious problem when I wanted a reflash and not restore a different backup.
There is a thread with a zip that CWR can run that blasts CWR off and reflashs stock and getting that done put me back both times I messed up above.
Seems to me that perhaps the whole "can never brick" response when people ask for help needs to have an addendum about how CWR gets in the way of an 8 reboot reflash and provide guidance on how to get that update file and use it instead to get back to square one. (Plus some advice on when to clear caches and data partitions to avoid weirdness later).
Now rerooted on 1.1 with no ROM Manager running but I'm missing the nandroid bacjup capability, so maybe I reinstall but stay away from the recovery option until I need it?
I reinstalled CW after I rerooted 1.1 and have had no problems with it so far, but I also haven't tried to backup or anything since the first time (which initially got me into this mess).
I do think you're right about having some sort of addendum thrown in. I was running circles around the XDA forums for a few hours trying to find some sort of fix the first time my Nook started acting weird. The 8-reboot trick just wouldn't work, and my battery was more or less drained because CW was interfering. Maybe this is just understood by most, but it certainly would have saved me some time (and some gray hairs) if someone had mentioned it earlier.
So what is the conclusion of this thread? I have a new NC, updated to 1.1 and installed AutoNooker 3.0, immediately installed Clockwork and did a NAND backup... bad thing is that it won't boot off the eMMC anymore, only CW.
I can boot roms off of the SD card (ie Honeycomb) but this isn't want I want. I've downloaded and flashed several roms but its looped at CW. So the rom isn't the problem.
If we can't install Clockwork Recovery, then how can we flash new roms to the eMMC?
[UPDATE]
Found a flashable file which removes Clockwork Recovery.
http://www.etoile-laconnex.com/CWR-removal-rootsafe.zip
After I flashed that I am now booting off the eMMC froyo rom. Nice! Saved me from Restoring it, updating it, and reRooting it.
[UPDATE 2]
Well while it worked initially, it loaded the homescreen and reset. Now it is stuck at the "Touch the Future of Reading" screen with no Recovery... which worse off. Now I have to make a CWM bootable SD, flash the restore, and start over. Nice.
[UPDATE 3]
Finally got it back to stock after hours. I found a "MonsterPack" here:
http://forum.xda-developers.com/showthread.php?t=922870
Even this was more complicated then it needed. I had to download the 128mb RootPack image, and get it going so I can grab the needed root files. Then download the right size Clockwork image for my memory card and get it going. The end result ended in a Clockwork SD card. Then I made a "sdcard" folder from where I added the rootpack files and the stock image 1.0.1 flashable zip file.
Format the system and boot partitions, then flash the stock zip.
I just upgraded stock to 1.1, then will proceed to boot off the microsd and root, install GAPPS, etc.
I wish I knew of a great custom rom to flash. I flashed Nookie Froyo 0.6.8 and it powers down immediately (several complaints about this). Maybe CM7?
Ditto
I'm having this problem as well, but I can't seem to do anything to fix it. I was running 1.1, and auto-nootered using v3.0. Everything was hunky dory until I installed CWR. I flashed, shutdown, restarted, then chose to perform a backup which brought me down into CWR and I was never able to get out. I used the Monster pack zip to remove CWR, and now I boot to the "n" screen and sit forever. I tried the 8 hard resets and it said it installed on two different occasions, but still I sit on the "n" screen during boot. I tried the 1.0.1 restore zip as well, but to no avail. What do I need to do to get back up and running?
CW Recovery only
So I flashed my NC with both the pre-dualboot and the dual-honeycomb rom, but every time I reboot with the SD card inserted, it only boots to CW recovery. When I take it out..it boots to NC stock OS.
Am I suppose to remove clockwork recovery with the CW-removal zip? I tried that.. once it rebooted it went right back to CW. Should I be using two different SD cards? One for CW recovery and one to load the eMMc?
So confused...
What I need to know is what should be on the SD card after everything is flashed.
Mw : you could use a bootable cwr sdcard and flash 'emmc recovery repair', then format data and restore your backup.
Ehamonn: you have to remove cwr from the sdcard. Format should do the trick. But you'll loose the data on it..
Sent from my Desire HD using XDA App
Do I need to keep a boot image on the card after I format?
Well, if you only want to boot from internal memory, no.