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
Hello Nookers,
I myself and pndo1 of XDA have posted guides for dual booting CM7 and Stock 1.2. My first one was crappy, my second one was a little less crappy, and pndo1's was pretty good, but had too many steps. So yeah, I decided to clear this up once and for all. Alright, enough of that garbage, let's get on with the guide!
0. Make a CWM sd card using these instructions.
1. Download CM7 to your sd card. I recommend the latest version from here. Also, if you would like to overclock download this. Lastly, if you would like to remap Volume + and - to Menu and Back, download this too. Also, your gonna want (duh) have a copy of Nook Color Stock 1.2. This one is the best in my opinion. Also, if you would like to root Stock 1.2, get this. Now get gapps from here. Almost! Download thishere. And now the multiuboot! Grr... this is tiring... but lasties! Get it here. Put ALL the files you downloaded on your SD Card.
1. Boot into CWM. Go into Backup+Restore and create a backup. Then go into Mounts+Storage and unmount the sd card. Put in an MicroSD reader in your computer. Navigate to /sdcard/clockworkmod/ and find the backup. Copy it to your computer. You can now delete it from the SD Card. Put the SD Card back in the nook. Go into Mounts+Storage and hit "Mount sd card" Now from the same place, wipe system, data, and cache. Now go to the root menu (hit the power button once). Hit "Install zip from sd card" then "Choose zip from sd card" Select prep.dualboot.zip. Then redo the choose zip Select your downloaded 1.2 Zip. It should be called "update_nc_stock_1.2_keepcwm.zip" Flash that. Now wait for it to install. Reboot your Nook. It will boot and will ask you to setup the Nook. Set it up but if you don't have wifi, follow these instructions. After setting up, boot back into CWM using your sd card.
2. Now Choose the zip from sd again, but select ManualNooter. That will take one minute to flash. Reboot again. Make sure your root is setup. To confirm, download an app from the market. Any app.
3. Once that is done, boot back into CWM. Flash the zip "eclair-to-dualboot-0.2.zip" It will duplicate Stock 1.2 to the Second partition. Now go into Mounts+Storage, and wipe system+data+cache. Now choose zip again, but this time pick CM7. Then Choose again, pick GAPPS. Then anything else, like that KeysMod or OC kernel. Now flash Multi-Uboot-0.3.zip. Now reboot without holding anything. It should boot CM7. Reboot, but this time hold the home button. BAM! Stock 1.2. Hope it worked for ya!
To those whom it doesn't work:
yelloguy said:
I had the same problems as everyone else is reporting on this thread. I did this on Tuesday without the benefit of this guide but with the help of other two mentioned in the OP.
So after talking to iKingBlack via PM, I tried it again yesterday. And here is the exact sequence of events in case it helps anyone.
Install removal script for dual boot found in these forums
Install stock 1.2 from the link mentioned in OP
Boot 1.2 and register the device
Sleep 7.5 hours and then chat with iKingBlack
Install manual nooter, then the apk enabler
Boot 1.2 to check root access
(no boot from now on)
Install prep dual boot
Install eclair to dual boot
Format system, data and cache
Install CM7 nightly
Install gapps
Install multi boot
Reboot holding N and check stock works as it used to
Reboot normally, check CM7 works and set it up
Since then I have used both partitions successfully.
Click to expand...
Click to collapse
Credits:
@GirLuvsDroid for the feedback and testing
@GabrialDestruir for 1.2 Manual Nooter
@Koush for ROM Manager and CWM Flashes
@yellowguy for telling us to flash prep.dualboot
@Anyone else who helped but escapes my mind at the moment
@pndo1 (Who has moved on to better things than our little NC's... aka Flyer) for this orignal project
I've been wanting to dual boot my NC for a while now, but I've read several sets of instructions and kept getting twisted up in them. I was also concerned that having a dual boot would make it difficult to impossible to continue installing the CM7 nightlies and the latest Dal kernels.
These instructions look really clear and easy to follow and I thank you for that!
I just want to clarify my understanding: both CM7 and stock 1.2 are run from eMMC, correct? And, because stock 1.2 is on the second partition, it's just business as usual to install the nightlies and the latest kernel on the first partition, right?
Again, thanks for taking the time to rework your instructions again. Your contributions are much appreciated!
Why a special uboot? Stock cm7 uboot (based on bn 1.2) already does multiboot... (hold down n on boot for info) and dalingrin's nook tweaks lets you set up default options from prefs menu...
That said, I didn't read the instructions carefully so maybe there's a reason...
@GirLuvsDroid Your welcome, and yes both run from the emmc. Flash nightlies and kernel like anything. Just nothing to the dual boot partition.
@fattire For me the CM7 Alternate boot option hangs. But again, that's me.
I may have just missed it, but I didn't see where in the instructions to download the Multi-Boot-Uboot-0.3.zip file.
I found and downloaded v0.4 file from this thread
http://forum.xda-developers.com/showthread.php?t=947698
and it doesn't quite work right. It boots CM7 fine, but it hangs on the Nook 'N' screen when booting into stock 1.2. I'm not sure if that's because of the v0.4 multi-boot file, or because of something else I did wrong. (It did boot into stock 1.2 correctly at the point where you said it would in the instructions).
Any thoughts, or the link to the v0.3 multi-boot zip and I'll flash that to see if it corrects the problem.
MHotovec said:
I may have just missed it, but I didn't see where in the instructions to download the Multi-Boot-Uboot-0.3.zip file.
I found and downloaded v0.4 file from this thread
http://forum.xda-developers.com/showthread.php?t=947698
and it doesn't quite work right. It boots CM7 fine, but it hangs on the Nook 'N' screen when booting into stock 1.2. I'm not sure if that's because of the v0.4 multi-boot file, or because of something else I did wrong. (It did boot into stock 1.2 correctly at the point where you said it would in the instructions).
Any thoughts, or the link to the v0.3 multi-boot zip and I'll flash that to see if it corrects the problem.
Click to expand...
Click to collapse
MH, it's the link in the OP that says this: "Last one (yes, really!) here." It's not the Multi-Boot-Uboot-0.3.zip but the eclair-to-dualboot-0.2.zip.
Disgregard this post -- I'm an idiot and apparently blind, as well.
Thanks GLD.
I'll reflash that one (I flashed both, just like the directions said ) and see if that makes it behave better.
MHotovec said:
Thanks GLD.
I'll reflash that one (I flashed both, just like the directions said ) and see if that makes it behave better.
Click to expand...
Click to collapse
I must be blind -- I don't see where it says to flash both. I only see the eclair-to-dualboot in the instructions.
Nevermind -- I found it. It's the last step. I stand corrected and I'm glad I do because I'm planning to do this when I get home from work tonight. Thanks for setting me straight!
Reflashing the eclair to dualboot wasn't the answer, now is doesn't even TRY to boot the stock 1.2.
Now where did I leave that drawing board....
I found the download link for the Multi-Boot-Uboot-0.3.zip:
http://api.viglink.com/api/click?fo...dified u-boot.bin based on B&N 1.2 source
GLD, if anyone tells you that you're not a goddess, you tell them that I said you are.
Of course, that didn't solve the problem. (sigh)
I ran the entire routine again, and this time used the v.03 multi-boot that you found, same problem. It will boot into CM7 just fine, but it hangs up when booting into stock.
ahhhhhh, that's just so sweet, MH!
I just went through the whole process myself and everything went perfectly right up until I tried to boot into stock 1.2. Exactly like you, it hangs on the N and won't boot up. CM7 boots just fine, though.
Well, at least I know it's not just me.
By any chance, have you run the app that changes your Nooks RAM from 'new way' to 'old way'? (1gb data, 5gb apps).
I have, I wondering if that has something to do with it (just fishing of course, it's not like I actually KNOW anything).
Yes, I had a blue dot NC that I repartioned, but I did it using the custom partition (around 2GB data).
Well, multi-boot link added.
Oh, to those whom it doesn't work (stuck on N), try flashing 1.2 zip and manual nooter without rebooting and then eclair2dualboot then wipe system,data, and cache. Then flash cm7 and goodies. Not one reboot. Try it and only then say if it works or doesn't.
I'll try this no-boot method when I get a chance tomorrow. One question for you -- assuming I get this to work, is there any reason I can't restore /data from the CWM backup of my original setup that I made before I started the dual boot process?
I get the same result with the no boot method. CM7 boots fine, Nook stock hangs on the 'N' screen.
I had the same problems as everyone else is reporting on this thread. I did this on Tuesday without the benefit of this guide but with the help of other two mentioned in the OP.
So after talking to iKingBlack via PM, I tried it again yesterday. And here is the exact sequence of events in case it helps anyone.
Install removal script for dual boot found in these forums
Install stock 1.2 from the link mentioned in OP
Boot 1.2 and register the device
Sleep 7.5 hours and then chat with iKingBlack
Install manual nooter, then the apk enabler
Boot 1.2 to check root access
(no boot from now on)
Install prep dual boot
Install eclair to dual boot
Format system, data and cache
Install CM7 nightly
Install gapps
Install multi boot
Reboot holding N and check stock works as it used to
Reboot normally, check CM7 works and set it up
Since then I have used both partitions successfully.
@GLD Yes, I think you can restore safely.
@yellowguy You don't need prep dual boot because eclair2dualboot already takes care of that. And if my instructions didn't work, try yellowguys, a slightly refined method.
Just posting what happened to me yesterday since I forgot some details about installing CM9 roms through ACMEInstaller2.
I decided to try CN's "Butta" CM9 rom, so figured I'd be safe and use the ACMEInstaller2 script to upgrade from CM7. I downloaded ACMEInstaller2 and the butta .zip file and put them in the proper directories on the TP and on my PC.
When I ran the novacom command from my PC, the TP went into double penguin mode, and lots of text scrolled up on the screen, but the rom never installed - probably because I didn't rename it to match the CM9 alpha files.
So when the TP rebooted, I went into Clockworkmod recovery, cleared system data/cache/dalvic, and then flashed CM9.
Seems to have worked, and everything appears to work okay, but I'm just wondering if this could cause problems down the road.
mike-y said:
Just posting what happened to me yesterday since I forgot some details about installing CM9 roms through ACMEInstaller2.
I decided to try CN's "Butta" CM9 rom, so figured I'd be safe and use the ACMEInstaller2 script to upgrade from CM7. I downloaded ACMEInstaller2 and the butta .zip file and put them in the proper directories on the TP and on my PC.
When I ran the novacom command from my PC, the TP went into double penguin mode, and lots of text scrolled up on the screen, but the rom never installed - probably because I didn't rename it to match the CM9 alpha files.
So when the TP rebooted, I went into Clockworkmod recovery, cleared system data/cache/dalvic, and then flashed CM9.
Seems to have worked, and everything appears to work okay, but I'm just wondering if this could cause problems down the road.
Click to expand...
Click to collapse
ACME should just install all the zips in "cminstall" regardless of name...
Your alternative sounds fine, but you lost all your apps. The upgrade would have kept your apps from CM7.
Thanks for the response. looks like I'm okay then.
Losing the apps wasn't a big deal, I had everything backed up with TB anyway. After I installed gapps, I was able to DL the newest version of TB and restore my old apps.
Something similar happened to me last night when I ran novacom w/ ACMEInstaller2. I had to rename the newest KANG build to match the CM9 alpha build and it worked correctly the second time.
Hello
I have the problem that I cannot update my i9000 from CyanogenMod 10.1.3 to 10.2.0. After the update, Cyanogenmod doesn’t start anymore. It gets stuck at the boot animation: The blue CyanogenMod-mascot within the round rotating arrow. I waited 15min for it to start, then I left the phone for 2h and it still didn’t start.
I did the update as follows:
First, I tried to update with the automatic updater from CyanogenMod, but that didn’t work. It aborted and restarted CyanogenMod 10.1.3.
So I tried it manually with ClockworkMod (v6.0.3.6):
- wipe data / factory reset
- wipe cache partition
- advanced -> wipe dalvik cache
This message was shown: E:unknown volume for path [/sd-ext]
Dalvik cache wiped.
- install zip -> choose zip from sdcard -> cm-10.2.0-RC1-galaxysmtd.zip
It aborted and the following message was shown:
This ROM uses an incompatible partition layout
Your /data will be wiped upon installation
Run this update.zip again to confirm install
- Did it again: install zip -> choose zip from sdcard -> cm-10.2.0-RC1-galaxysmtd.zip
Now the zip-file was installed completely.
- reboot system now
The result was that the phone got stuck at the boot animation.
Remarks:
- I didn’t do a backup of apps and data, because I didn’t have important data on the phone.
- I didn’t have root-rights in CM 10.1.3.
I tried it again with the stable version of CM 10.2.0. I didn’t have to install the zip twice anymore, but the phone still gets stuck at the boot animation. Wiping cache and dalvik cache again didn’t make it start.
I can still boot into ClockworkMod and it was also possible to go back to CM 10.1.3. Just CM 10.2 doesn’t start up.
What do I have to do to make CM 10.2 start up?
Thank you very much for your help.
Best regards
Tomy
@Tomy_Delmar
Tomy, CyanogenMod is already custom ROM, there is always root access on it
Try it this way:
download Gapps for CM10.2x (Android 4.3.x) and paste them on your external SD card
put the card in your phone
run it in recovery mode
wipe cache and dalvik cache
flash Gapps for 4.3
wipe again cache and dalvik cache.
reboot
Post if it worked.
Tomy_Delmar said:
Hello
I have the problem that I cannot update my i9000 from CyanogenMod 10.1.3 to 10.2.0. After the update, Cyanogenmod doesn’t start anymore. It gets stuck at the boot animation: The blue CyanogenMod-mascot within the round rotating arrow. I waited 15min for it to start, then I left the phone for 2h and it still didn’t start.
I did the update as follows:
First, I tried to update with the automatic updater from CyanogenMod, but that didn’t work. It aborted and restarted CyanogenMod 10.1.3.
So I tried it manually with ClockworkMod (v6.0.3.6):
- wipe data / factory reset
- wipe cache partition
- advanced -> wipe dalvik cache
This message was shown: E:unknown volume for path [/sd-ext]
Dalvik cache wiped.
- install zip -> choose zip from sdcard -> cm-10.2.0-RC1-galaxysmtd.zip
It aborted and the following message was shown:
This ROM uses an incompatible partition layout
Your /data will be wiped upon installation
Run this update.zip again to confirm install
- Did it again: install zip -> choose zip from sdcard -> cm-10.2.0-RC1-galaxysmtd.zip
Now the zip-file was installed completely.
- reboot system now
The result was that the phone got stuck at the boot animation.
Remarks:
- I didn’t do a backup of apps and data, because I didn’t have important data on the phone.
- I didn’t have root-rights in CM 10.1.3.
I tried it again with the stable version of CM 10.2.0. I didn’t have to install the zip twice anymore, but the phone still gets stuck at the boot animation. Wiping cache and dalvik cache again didn’t make it start.
I can still boot into ClockworkMod and it was also possible to go back to CM 10.1.3. Just CM 10.2 doesn’t start up.
What do I have to do to make CM 10.2 start up?
Thank you very much for your help.
Best regards
Tomy
Click to expand...
Click to collapse
As the partition layout is different in cm10.2, you should flash it at least 2 times and wait for system to be stable for about 15-20 minutes
Tetakpatak and Rohitdahiya, thanks for the reply and advice!
In my previous post, I forgot to mention that I installed CyanogenMod without the Gapps. I’d like to try if an android-phone without the Gapps is still useful. Somehow I don’t like the data-collecting-mania of Google.
I tried again the update from CM 10.1.3 to 10.2:
- I downloaded cm-10.2.0-galaxysmtd.zip again and copied it to the internal SD-card of the phone.
- Restarted the phone into ClockworkMod recovery.
- wipe data / factory reset
- wipe cache partition
- wipe dalvik cache
- install zip -> choose zip from sdcard -> cm-10.2.0-galaxysmtd.zip
- install zip -> choose zip from sdcard -> cm-10.2.0-galaxysmtd.zip
(Did it twice. Don’t know if necessary.)
Didn’t install Gapps.
- wipe cache partition
- wipe dalvik cache
- reboot system now
Unfortunately CM still gets stuck at the boot animation. The arrow has been rotating for over an hour now.
To my knowledge the Gapps are not mandatorily required to install CM. I could install CM 10.1.3 without the Gapps without any problems.
Could a full-wipe solve my problem?
ClockworkMod -> mounts and storage -> format /system …?
I have never done this before.
Or is there something else I can do?
Regards
Tomy
Tomy_Delmar said:
Tetakpatak and Rohitdahiya, thanks for the reply and advice!
In my previous post, I forgot to mention that I installed CyanogenMod without the Gapps. I’d like to try if an android-phone without the Gapps is still useful. Somehow I don’t like the data-collecting-mania of Google.
I tried again the update from CM 10.1.3 to 10.2:
- I downloaded cm-10.2.0-galaxysmtd.zip again and copied it to the internal SD-card of the phone.
- Restarted the phone into ClockworkMod recovery.
- wipe data / factory reset
- wipe cache partition
- wipe dalvik cache
- install zip -> choose zip from sdcard -> cm-10.2.0-galaxysmtd.zip
- install zip -> choose zip from sdcard -> cm-10.2.0-galaxysmtd.zip
(Did it twice. Don’t know if necessary.)
Didn’t install Gapps.
- wipe cache partition
- wipe dalvik cache
- reboot system now
Unfortunately CM still gets stuck at the boot animation. The arrow has been rotating for over an hour now.
To my knowledge the Gapps are not mandatorily required to install CM. I could install CM 10.1.3 without the Gapps without any problems.
Could a full-wipe solve my problem?
ClockworkMod -> mounts and storage -> format /system …?
I have never done this before.
Or is there something else I can do?
Regards
Tomy
Click to expand...
Click to collapse
First of all, don't forget to quote the user whom you want to contact, because he don't get any notification until you quote. I was just checking around the questions and thus I saw this.
Sometimes, there is requirement of g-apps for the core system to be working ( Not sure in case of cm10.2). Try with g-apps (you may choose light package).
In my opinion, it should work. If not, try from the start ( flashing gingerbread with Odin with repartition ticked, then its root and finally cm10.2 from recovery)
Also make sure your handset is i9000 and you are using cm10.2 for the same.
And finally, All the best
CM doesn't neccesarily need Gapps to boot up. In fact most custom roms don't - they are still usable, just that everything Google-related doesn't work.
Its a bit odd seeing as how you've pretty much done what I would have done if I was installing CM to a Galaxy S. I can't think of any reason why it wouldn't work.
As far as I know as well, formatting /system is more of a last-resort method, not something you'd immediately do.
However, I had a similar problem installing a rom onto my tablet - different device, I know, but try this anyway and see if you get anywhere:
1.) Go back into recovery if its still bootlooping
2.) Wipe data, cache, Dalvik (and this is after you've flashed the CM10.2 zip twice like you did)
3.) Reboot device without flashing Gapps - this is to see if it boots up.
Let us know what happens.
Sent from my GT-P7510 using Tapatalk
Tomy_Delmar said:
In my previous post, I forgot to mention that I installed CyanogenMod without the Gapps. I’d like to try if an android-phone without the Gapps is still useful. Somehow I don’t like the data-collecting-mania of Google.
Click to expand...
Click to collapse
Tomy, now it is getting clear- of course, I tought you already had Gapps on your CM10.1.3 installed so in such case they would definitely need to be updated to 4.3
Yes, the ROM shouold work perfectly fine also without Gapps
Your workflow sounds correct, but just to make sure: after first attempt to flash CM10.2 build, there should be a warning that all your data will be wiped, right? After that you must again choose the option "install zip" and install CM10.2. It will work this time.
If it doesn't work, download again the CM10.2 zip as it may be corrupted file. BTW, I didn't like that build for several reasons and returned to RC version.
If nothing helps, flash back your CM10.1.3 and restore your nandroid backup if important files were there. If the downgrade won't work for different partition of the /system, use my unbricking guide and revert to stock, then to CM10.1.3, then to CM10.2.
Keep step by step on the guide if you use it, it has important points to control before flashing. Flashing with re-partition needs always a PIT file, or with other words: without that file re-partition option mustn't be checked. Doing it simply by clicking the re-partition (like @Rohitdahiya adviced you to) without a PIT file checked under "PIT" would brick your i9000.
Soryuu said:
However, I had a similar problem installing a rom onto my tablet - different device, I know, but try this anyway and see if you get anywhere:
1.) Go back into recovery if its still bootlooping
2.) Wipe data, cache, Dalvik (and this is after you've flashed the CM10.2 zip twice like you did)
3.) Reboot device without flashing Gapps - this is to see if it boots up.
Let us know what happens.
Click to expand...
Click to collapse
Unfortunately, Wiping data, cache and Dalvik cache again after I had flashed CM 10.2 didn’t make it start.
tetakpatak said:
Tomy, now it is getting clear- of course, I tought you already had Gapps on your CM10.1.3 installed so in such case they would definitely need to be updated to 4.3
Yes, the ROM shouold work perfectly fine also without Gapps
Your workflow sounds correct, but just to make sure: after first attempt to flash CM10.2 build, there should be a warning that all your data will be wiped, right? After that you must again choose the option "install zip" and install CM10.2. It will work this time.
If it doesn't work, download again the CM10.2 zip as it may be corrupted file. BTW, I didn't like that build for several reasons and returned to RC version.
If nothing helps, flash back your CM10.1.3 and restore your nandroid backup if important files were there. If the downgrade won't work for different partition of the /system, use my unbricking guide and revert to stock, then to CM10.1.3, then to CM10.2.
Keep step by step on the guide if you use it, it has important points to control before flashing. Flashing with re-partition needs always a PIT file, or with other words: without that file re-partition option mustn't be checked. Doing it simply by clicking the re-partition (like @Rohitdahiya adviced you to) without a PIT file checked under "PIT" would brick your i9000.
Click to expand...
Click to collapse
When I tried to flash CM 10.2 the first time – at that time RC1 was the newest version – I was asked to flash it a second time, which I did. To be precise, the following message was shown:
This ROM uses an incompatible partition layout
You /data will be wiped upon installation
Run this update.zip again to confirm install
This message hasn’t been shown again since then. I flashed CM 10.1.3 again and tried to flash 10.2 a second time, but the message wasn’t shown again.
Going back to CM 10.1.3 worked without any problem.
------------------------------------------
Now I have CM 10.2 on my phone and it starts normally
I flashed Stock-Android 2.3.6 with Odin (v1.82). Tetakpatak, thank you for the excellent guide and the video! As written in the guide, I used "s1_odin_20100512.pit" as PIT-file.
(I executed Odin on an old computer with Windows XP 32bit, as the guide says Odin 1.82 works better with Win XP.)
Then I installed CM 10.2 over Stock-Android 2.3.6. I followed the official instructions:
http://wiki.cyanogenmod.org/w/Install_CM_for_galaxysmtd?setlang=en
(I executed Heimdall on my new computer with Windows 7. Heimdall 1.4RC2 doesn’t work on Win XP. If one executes Odin and Heimdall on the same PC, I could imagine this could lead to confusion, because Odin needs the Samsung-USB-drivers and Heimdall needs WinUSB. I’m not sure if this really leads to problems. But one should keep that in mind.)
I didn’t flash CM 10.1.3 before 10.2, because I didn’t need to restore a nandroid backup previously made with CM 10.1.3. There were no important data on the phone.
Many thanks to all who gave me advice and helped my solving the problem!
Tomy
HELP MEEE
I put on TWRP 2.6.3.0 on my Nexus 5 (I used towerlroot succesfully) and i tried wiping as you should, i noticed i loaded an old twrp so i quickly powerd off my Nexus5. When i loaded, every app had a "Google play services has stopped" error and some would force close. I reloaded TWRP and tried to flash cyanogenmod and gapps, succelfully they installed. Now cyanogenmod is stuck in the boot animation and i dont know to update TWRP, HELPP PLEASSE!!!!
Pure_Android said:
I put on TWRP 2.6.3.0 on my Nexus 5 (I used towerlroot succesfully) and i tried wiping as you should, i noticed i loaded an old twrp so i quickly powerd off my Nexus5. When i loaded, every app had a "Google play services has stopped" error and some would force close. I reloaded TWRP and tried to flash cyanogenmod and gapps, succelfully they installed. Now cyanogenmod is stuck in the boot animation and i dont know to update TWRP, HELPP PLEASSE!!!!
Click to expand...
Click to collapse
This is the forum for the original Galaxy S, not the Nexus 5, sorry mate
However I think your problem can be fixed by doing a full data/cache wipe so it might be worth a shot
Flash Boot.Img. This might solve the bootloop!
I think, You just need to flash the boot.img (available in the Cynogen Bundle Zip Folder) after installing Cynogen Mod. Me too got stuck on the animation part for a long time. Then I found out this:
CyanogenMod builds for endeavoru currently do NOT support any bootloader version number below: HBOOT 1.28. As the device is S-ON (security-on bootloader), for a working installation you must extract the boot.img from the installer zip and run fastboot flash boot boot.img from fastboot mode.
Source: Cynogen Mod Wiki
Pure_Android said:
I put on TWRP 2.6.3.0 on my Nexus 5 (I used towerlroot succesfully) and i tried wiping as you should, i noticed i loaded an old twrp so i quickly powerd off my Nexus5. When i loaded, every app had a "Google play services has stopped" error and some would force close. I reloaded TWRP and tried to flash cyanogenmod and gapps, succelfully they installed. Now cyanogenmod is stuck in the boot animation and i dont know to update TWRP, HELPP PLEASSE!!!!
Click to expand...
Click to collapse
Which version of CyanogenMod are you using?
I've been trying to install milaq's 4.4 ROM on my Touchpad and I'm getting a bit stuck.
I've removed my previous 4.0.4 build so that I could start fresh and get my head around the data/media build. I've tried following the text guide and Roland's video guides but keep getting stuck at the same point.
I put the following files in the "cminstall" folder on my touchpad and ran ACMEinstaller5M:
cm-11-20140223-UNOFFICIAL-tenderloin
gapps-kk-20140105
recovery-clockwork-6.0.4.7-tenderloin
moboot_038-tenderloin
update-cm-tenderloin-data_resize_12228-0.1
So far I get the moboot menu and am able to get into the CWM-Based Recovery v6.0.4.7. This is where I'm stumped, I have no idea how to install the milaq ROM. I've had experience putting various CM Android builds on different devices (HD2, Defy+, Touchpad) but I'm struggling with this one. I know that I won't be able to install it the way I'm used to but I've tried searching and can't find what I'm supposed to do next.
I know this is a bit of a simple request but could anyone help me out with the next step? Once I'm past that, it'll be plain sailing I'm sure.
Thanks in advance.
yeoldgreat1 said:
I've been trying to install milaq's 4.4 ROM on my Touchpad and I'm getting a bit stuck.
I've removed my previous 4.0.4 build so that I could start fresh and get my head around the data/media build. I've tried following the text guide and Roland's video guides but keep getting stuck at the same point.
I put the following files in the "cminstall" folder on my touchpad and ran ACMEinstaller5M:
cm-11-20140223-UNOFFICIAL-tenderloin
gapps-kk-20140105
recovery-clockwork-6.0.4.7-tenderloin
moboot_038-tenderloin
update-cm-tenderloin-data_resize_12228-0.1
So far I get the moboot menu and am able to get into the CWM-Based Recovery v6.0.4.7. This is where I'm stumped, I have no idea how to install the milaq ROM. I've had experience putting various CM Android builds on different devices (HD2, Defy+, Touchpad) but I'm struggling with this one. I know that I won't be able to install it the way I'm used to but I've tried searching and can't find what I'm supposed to do next.
I know this is a bit of a simple request but could anyone help me out with the next step? Once I'm past that, it'll be plain sailing I'm sure.
Thanks in advance.
Click to expand...
Click to collapse
I just inherited an already rooted/android touch pad, so I'm in your same shoes right now. So i'm following close! haha.
I'm very new to the whole webos stuff here, but very experienced with rooting android.
But at this point, don't you just start flashing the .zips in clockwork after a full wipe (wipe factory, cache, davlik)?
BRUTAL BROCK said:
I just inherited an already rooted/android touch pad, so I'm in your same shoes right now. So i'm following close! haha.
I'm very new to the whole webos stuff here, but very experienced with rooting android.
But at this point, don't you just start flashing the .zips in clockwork after a full wipe (wipe factory, cache, davlik)?
Click to expand...
Click to collapse
That's what I thought but the ACMEinstaller wipes everything in the cminstall folder. Also, CWM only has the option to install zips from the sdcard which isn't there.
AcmeInstaller won't install the zip that resizes your partitions, and when you flash a data/media rom, the sdcard or media partitions are only accessible thru the rom itself so you won't be able to see them in recovery.
I think you will have to start again. Installing a data/media rom from a fresh install is, to be honest, a pain in the ass! You need to have a non-data/media build installed, ie. Jelly Bean/CM10.x, then resize partitions, etc, etc.
If you want to install kitkat from a fresh start, go for flintman's non-data/media version in the link in this post, and this recovery (20121215). Rename rom update-xxx, same for recovery, include moboot, and also have appropriate gapps to flash.
Hope this helps.
Oh yeah, and don't use AcmeInstaller5M, use the one ending in 5E =)
Data media install guide
Additional resources:
[ROM GUIDE] How to install Android on the HP TouchPad "The Easy Way"
[ROM GUIDE] How to install Android 4.4.2 Data Media builds on the HP TouchPadhttp://forum.xda-developers.com/showpost.php?p=42505399&postcount=2http://forum.xda-developers.com/showpost.php?p=42505399&postcount=2
RolandDeschain79 said:
You can't install CM11 data media builds with the ACMEInstaller. Here is my newest thread that explains how to get them fully installed. Please leave some feedback once you get it setup. :highfive:
[ROM GUIDE] How to install Android 4.4.2 Data Media builds on the HP TouchPad
Click to expand...
Click to collapse
That guide has been really helpful so far. I'm stuck at the last bit though.
I've installed PhilZ Clockworkmod but I don't know what to do from there. When I turn on the USB Drive, my PC can only see one SDcard (the WebOS one it sees normally) so I can't copy over the CM11 files to the Android one.
Any ideas?
If anyone is still having problems, this thread helped me. The instructions are in post #7 but you should read the preceding posts for background info.