<deleted >
In your case, repartitioning boot will have no effect: your NC is booting fine.
Your problem is most certainly due to some errors in either /data or /system.
Search for 1.1.0 clockwork recovery image in dev forum. Download the image, burn it to your SD. Boot, format system and data, flash the 1.1.0 file.
Then boot.
See the mentioned thread for further info. It's all in there, just take time to read.
Sam
<deleted >
No. That's not the file. There are a lot of threads about this. A quick search should give you plenty of answers..
Sent from my HTC Desire using XDA App
<deleted >
<deleted >
Related
Hi Everyone,
Sorry for this long-winded post. I've spent hours reading posts here, AndroidCentral and AndroidTablets.net forums, but have not found answers that work for me.
I hope someone can sort out the mess I've created on my rooted 1.1 Nook. Everything worked for 4-5 weeks after I rooted with Decad3nce method until...
A few days ago I decided to try 1.1G kernel. Read many threads about issues with Root Manager/ CWM; 3.0.0.5/3.0.0.6/SD CWM/EMMC CWM/Nook/Nook (old). When I booted into CWM, the version was 3.0.0.5. If I tried flashing CWM through Rom Manager, it said it 'flashed' 3.0.0.6 (tried both "Nook" and "Nook(old)"), but it never changed version of CWM I booted into. I also tried nemiths' "[RECOVERY] Official CWM 3.0.0.6 Update [BROKEN] (new fix soon!)" method to flash 3.0.0.6, but "adb shell busybox" always gave a 'can't get root' type error, so I gave up on that. I ended up using my current CWM to flash 1.1G kernel, and it worked very well. So I ignored the the CWM issues.
Then, I decided to try rookie1's dual-boot method so I could try out Honeycomb. I could never get 'prep_dualboot' zip to flash. It always gave an 'error in zip (status 0)'. His thread showed a few others getting same error, but none of the fixes given worked for me. I re-flashed that zip and ran the 'un-dualboot' zip many times with same result. I then found a "EMMC_CWM_3.0.0.6" zip and flashed that with my CWM. That actually gave me 3.0.0.6 CWM, but flashing dualboot still didn't work. I also again un-dualbooted, wipe cache partition, wipe dalvik cache, fix permissions with same result. So I gave up on that for now.
Then this morning, I found Market updates and downloads don't work anymore. It says 'about to download', then shows the arrows in status bar and nothing else happens. Saw threads regarding this issue and tried clearing Market cache and wiping whatever I could in CWM. Nothing I've found has helped so far.
As a side note in Rom Manager, "Recovery" section now shows 3.0.0.5 (before it wanted to flash 3.0.0.6). Tried flashing 3.0.0.5 there, but it doesn't seem to do anything (same as when it tried to flash 3.0.0.6). I can't understand the logic in Rom Manager. I also have Fascinate phone and RM has issues on that phone also.
I do have CWM backups and Titanium backups of all my stuff, so at worst I can do those. Looking for possibly easier way to get back to 'normal' so Market works and I can download the 'dual boot' zip and be happy again.
Some additional questions I have:
1) I saw in Decad3nce post that he left out 'root' for busybox in an early release, so that may be why mine won't work. I know I had used busybox before, but that may have been on earlier rooted 1.0.1. Is there a way to fix my current busybox without re-rooting?
2) What is the correct CWM I should use for 1.1 and will let me flash dual-boot zip? Also, where can I download it from and how can I replace the one I have?
3) I have saved my SD card to my computer many times and then re-formated it on the Nook. Is there some partition on it that format isn't cleaning that may contain some CWM image(s) causing at least some of my headaches?
Thanks in advance to anyone that can help with these issues. I may have tried a few other 'fixes' that I've since forgotten in the 5 hours last night trying to setup dual boot and quick hour this morning before work trying to sort out Market. Sorry (in advance) if you suggest something and I then say I tried it already. Possibly, just doing all the fixes I've tried previously in the correct sequence is what I need.
I seem to back to where I was before 'bad' versions of CWM skewered Market on me.
1) busybox: found that I just had to 'chmod 755' on my /system/xbin/busybox.
2) Saw that nemith posted a 3.0.0.9 version of CWM. Flashed that using his manual method. Didn't flash his kernel. Rebooted.
3) Tried clearing Market cache and didn't help. Wiped partition cache in CWM (or possibly Dalvik cache, not sure now...was going to do both but rebooted by mistake). After reboot, Market is working again.
Not sure if any of these affected Market, but I also unchecked/checked "Allow Non-Market Apps" and Unchecked/Checked "USB Debugging" and Unchecked "Auto Mount" in Settings.
Can't post in Dev area, so hope some there having same issue as me Market see this.
Now, gonna try the dual-boot again.
Alas, still getting (status 0) error flashing dual boot prep zip. Project for another night.
Sent from my LogicPD Zoom2 using XDA App
I'm getting that same error trying to flash the dual boot prep zip on my rooted Nook. Very frustrating.
jhoward88 said:
I'm getting that same error trying to flash the dual boot prep zip on my rooted Nook. Very frustrating.
Click to expand...
Click to collapse
From error logs it appears the sizes used in re-partitions may be the problem. Over weekend I'm going to try to find values that work. Could be the size differences reflect how NC was originally configured or how many re-roots/updates it has gone through and affect whether the prep works or not. Errors do occur on the 'remove dual boot' ZIP also.
vinal said:
From error logs it appears the sizes used in re-partitions may be the problem. Over weekend I'm going to try to find values that work. Could be the size differences reflect how NC was originally configured or how many re-roots/updates it has gone through and affect whether the prep works or not. Errors do occur on the 'remove dual boot' ZIP also.
Click to expand...
Click to collapse
No luck getting this to work
vinal said:
No luck getting this to work
Click to expand...
Click to collapse
Got a suggestion from Rookie1 to reformat my media partition. Prep now succeeded!
newfs_msdos -F 32 -L media /dev/block/mmcblk0p8
Sorry about making a new post under this forum, but i didnt have permission to reply in the dev forum.
To ask Questions about developing your device, installing ROMs, software and themes you must go to the Q&A or General Forum.
noticed the LG screwed up - bad - here's why your UI is jerky! link, and decided to give it a try.
Code:
cat /system/build.prop | grep build
shows:
ro.build.lge.version.release=LGP990-V10b
ro.build.date=2011. 03. 15. (í) 14:14:22 KST
ro.build.date.utc=1300166062
So i go for the V10b (date 1300166062) linked on http://forum.xda-developers.com/showthread.php?t=1023354
did a nanodroid backup and tried to install the rom(zipfile) with clockworkmod from my SDcard.
Select the "Wipe Dalvik Cache" but leave the others unchecked.
Phone reboots and enter CLockwork recovery and attempts to install but it fails at the beginning of the installation and reboots the phone before I get time to read the error message.
What am I doing wrong?
I didnt wipe cache over V10B and it worked smooth. But i am on V10C now which is much better!
Sent from my LG-P990 using XDA App
upgrading to v10c, does that require any wipe, or can you just write it over your current version. Also, do you have a link to the package?
edit> found it here. http://forum.xda-developers.com/showthread.php?t=1035041
I upgraded via Lg updater. I cant give you links and yes just apply over it.
Sent from my LG-P990 using XDA App
zereke said:
What am I doing wrong?
Click to expand...
Click to collapse
Sounds like you use ROM Manager to boot into recovery?
Try booting to recovery manually by holding Power+Vol- while booting (until you see the yellowish A N D R O I D letters) and go from there.
If I remember right CWM Recovery and ROM Manager swap the internal and external SD card around or fails to mount the latter when booting directly to recovery from ROM Manager.
I posted a while back about the different recovery images here and have since been using Darch_RA-1.7 for everything (Firerat, GB ROMS, etc.).
When I change my custom partitions, there are two times when I need to ADB (one is arguable). I have to reboot into recovery during one point of modifying mtd partitions with Firerat Recovery, which can be accomplished by pulling the battery and just booting with HOME+POWER keys. It would be super handy though if there was a reboot into recovery command in my recovery image. I know this is in CW 3.x.
Secondly, and more important, is that to limit hickups in google restoring my settings when I load a new ROM, I need to apply s0be's fix before my first boot, which essentially is just making a dir /cache/download and then fixing the permissions for it.
I would love it if these commands could be apart of Darch's 1.7 recovery so that I could re-flash on the go without a computer for ADB shell. I am not completely sure how to do this (modifying the recovery binary), and moreover if I need to find the original source or just unpack and use the binaries. This little conversation was somewhat helpful.
Thoughts? Help?
Replying to my own post, but I had an idea that to address s0be's fix, I could possibly make it into a signed zip, of course assuming that would work (permissions?). Just a thought.
If your using Ra1.7 you don't have to pull the battery when using fr. Just choose the power off option and reboot with home+power. I know its off your op topic but I'd figure I'd post incase you were still using fr.
#Root/Hack-Mod_Always*
And as for the s0be market fix, it is no longer necessary if you use firerat v1.5.8 and set your cache partition to 18
Sent from my HERO200 using XDA Premium App
So that's why people have an 18mb cache.
The Fer-Shiz-Nizzle said:
And as for the s0be market fix, it is no longer necessary if you use firerat v1.5.8 and set your cache partition to 18
Sent from my HERO200 using XDA Premium App
Click to expand...
Click to collapse
Well that explains why I see a bunch of folks using 18 as the cache size, but didn't see that in the thread. My most recent repart with with 128 and 18, which although is a bit excessive for the cache (only using 4 of 18), will eliminate the need for s0be's fix.
For the record, I went ahead and did it anyways. Also, you can definitely just use the power off function (or battery pull) in Darch's 1.7 to get reboot to recovery.
Bottomline: I would say this is solved for my specific issues with Firerat MTD. Also, Darch's 1.7 is perfectly capable of installing GB ROMs.
I own a captivate phone but didn't bother to buy an external SD card and am cheap so I didn't bother to buy one since I'm happy with the amount of internal storage. The thing is I wasn't happy with the out of the box performance of the phone or lack of customization available. So I began to look for my options of flashing ROMs.
I searched and googled myself tired with no luck on how to do this WITHOUT an SD card, so I gave up and vaguely followed most of the wiki's I did find. I'll give you a breif overview of my process which I have been able to successfully flash Cyanogenmod 7RC1 without trouble, (I suspect you can do the same with other ROMs too)
Things you need
Root (superoneclick)
If you're running stock 2.2 3e signature failure fix script + update.zip(found it here in XDA)
Clockwork ROMmanager
Phone.
Process
Open Clockwork > Flash Clock Recover using Captivate MTD(Yes to the popups) > Download ROM(I picked Cyanogen 7 RC1 + Gapps.
DO NOT ATTEMPT INSTALL YET
Cancel out of the popup that appears after the ROM is done downloading.
Back to Clock choose >Install ROM from SD Card and find and select the .zip file the default location is clockworkmod/download/download.cyanogenmod.com/get/update-cm-7.1.0-RC1-Captivate.zip
After you choose that leave the default settings, and your phone should reboot into Recover mode with the green text indicating you're in Clockwork.
Once you're in Clockwork choose > Install zip from sdcard > choose zip from sdcard > find your update-cm-7blahblahblah.zip file. The next step your phone will begin the flashing process.
On your next reboot you'll notice a new boot screen indicating it's flashed to your choosen ROM. On your first boot open Clockwork again and choose to install ROM from sdcard again. This time find your gapps.zip file and go thru the same process to install your gapps.
Finally...
you're done.
Sorry for the poor formatting but I hope you can follow this and maybe it will help somebody else as cheap as me..
Yeah, that's how you flash any Rom. And you can flash gapps before your first reboot.
Don't know why you thought you needed an sd card to flash roms on this phone
Sent from my HTC Desire HD
sliverworm said:
I own a captivate phone but didn't bother to buy an external SD card and am cheap so I didn't bother to buy one since I'm happy with the amount of internal storage. The thing is I wasn't happy with the out of the box performance of the phone or lack of customization available. So I began to look for my options of flashing ROMs.
I searched and googled myself tired with no luck on how to do this WITHOUT an SD card, so I gave up and vaguely followed most of the wiki's I did find. I'll give you a breif overview of my process which I have been able to successfully flash Cyanogenmod 7RC1 without trouble, (I suspect you can do the same with other ROMs too)
Things you need
Root (superoneclick)
If you're running stock 2.2 3e signature failure fix script + update.zip(found it here in XDA)
Clockwork ROMmanager
Phone.
Process
Open Clockwork > Flash Clock Recover using Captivate MTD(Yes to the popups) > Download ROM(I picked Cyanogen 7 RC1 + Gapps.
DO NOT ATTEMPT INSTALL YET
Cancel out of the popup that appears after the ROM is done downloading.
Back to Clock choose >Install ROM from SD Card and find and select the .zip file the default location is clockworkmod/download/download.cyanogenmod.com/get/update-cm-7.1.0-RC1-Captivate.zip
After you choose that leave the default settings, and your phone should reboot into Recover mode with the green text indicating you're in Clockwork.
Once you're in Clockwork choose > Install zip from sdcard > choose zip from sdcard > find your update-cm-7blahblahblah.zip file. The next step your phone will begin the flashing process.
On your next reboot you'll notice a new boot screen indicating it's flashed to your choosen ROM. On your first boot open Clockwork again and choose to install ROM from sdcard again. This time find your gapps.zip file and go thru the same process to install your gapps.
Finally...
you're done.
Sorry for the poor formatting but I hope you can follow this and maybe it will help somebody else as cheap as me..
Click to expand...
Click to collapse
Thx for the ... incite?
Sent from my Fusion II powered Captivate
Umm...ok? Lol
Sent from my SAMSUNG-SGH-I897 using XDA App
bulletproof1013 said:
Umm...ok? Lol
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Lol. Dunno man, just smile and nod
Sent from my HTC Desire HD
Welcome to xda silverworm¡
Sent from my SAMSUNG-SGH-I897 using XDA App
Good advice pirateghost
:nod:
Pirateghost said:
Lol. Dunno man, just smile and nod
Sent from my HTC Desire HD
Click to expand...
Click to collapse
I agree just smile and nod. It has served me well thru my life. Sometimes when you do things will randomly appear in the house but that is for a different forum
Sent from my SGH-I897 using XDA App
grabbed root-stock.zip and cwm just below it (first 2 links on this page http://forum.xda-developers.com/showthread.php?t=1686384 ) carefully followed instructions, even watched videos on youtube and everything went swimmingly except after system reboot following root-stock.zip install. i must have grabbed the wrong file (dont know how, it was recommended by everyone on every other thread regarding the rooting of the t679) anyway now i need assistance, which root.zip file should i use? how do i get it onto the phone's internal "usb storage" folder? or can i use another device to grab file, transfer to ext. sd, then put ext. sd card into t679? i understand its critical at this point to make no mistakes, i believe i can recover, assuming i get competent advice...
please advise...
- zCHEMDAWGz
p.s. i am attempting to repair wifi and bluetooth errors (assuming its the drivers not loaded properly following system update 2.3.6) though im not certain of the culprit of these errors as i am the 4th owner of this device. assuming an internal battery has NOT leaked onto circuit board causing corrosion, pretty sure its software not hardware issue. phone/sms/network WAS connecting just no wifi/bluetooth. gotta have wifi cuz im out in the woods on the "EDGE" network, home network is fast as can be.
In cwm wipe cache, under advanced try wipe dalvik, then fix permissions then reboot. Please report results.
Sent from my GT-P3113 using xda app-developers app
Dvarl said:
In cwm wipe cache, under advanced try wipe dalvik, then fix permissions then reboot. Please report results.
Sent from my GT-P3113 using xda app-developers app
Click to expand...
Click to collapse
hey thanks for helping me i really appreciate it. so i tried your advice, in every order possible. fix permissions, wipe (everything), load rom, reboot... wipe, load, fix, reboot... to no avail though. all results in same loop... im getting good at wiping and loading =)
also the location of the rom and cwm files prior to transferring to "usb storage" folder was "downloads" on my windows 7 pc... does this make a difference? i have noticed people saving these types of files to their desktop... just trying to find out where i went wrong... thanks again.
- zCHEMDAWGz
SIDE NOTE: i tried loading different rom "t679-root-v1.8.zip" with exact same results... however i noticed that when i load either version of the new rom when cwm begins installation, and when the progress bar at the lower part of the screen shows about 2-3% complete it is then all of the sudden finished with "complete" confirmation at the end. total time less than 5 seconds. according to instructional videos this process should take minutes, instead of seconds.... just an observation.
- zCHEMDAWGz
That's just root not a ROM. If your willing to start fresh you can try this.
Wipe everything x3
Under mounts and storage mound system and data then format both x3
Flash rooted community rom
Reboot
It should work. If you flash any recent ROM make sure you have the latest cwm or you will get status 7 error.
Sent from my SGH-T679 using XDA Free mobile app
success!! wifi/bluetooth still getting error though... tried *#*#526#*#* (wlantest engineering mode) reports "Notset Driver Loaded [NG]"
any ideas?
a-thousand thank yous
- zCHEMDAWGz