Related
I had to restore my system using the SBF and got everything up and running. The only issue now is that if I have to restart, it's a nightmare. It'll go through the entire boot sequence, not a half boot or that glitchy boot to DROID logo, all the way from the M to my main screen. Then it'll stay up for about 1-2 minutes before rebooting again. No idea what's going on here. I wiped the cache, reformatted my SD card and still, random reboots. The kicker is, once I get it to stay and not reboot (5-10 reboots later) it'll be up and running at 100%, no problems at all. The suspects are:
My modified build.prop file (which I restored to the backup quickly after one reboot)
Overclocker app (I turned off the settings at boot though)
Auto memory manager (turned off the 'apply at boot' setting there too)
and/or
Black status bar "remnants"(?) - I tried to make my status bar black WITHOUT de-odexing and it messed me up bad, that why I had to SBF in the first place. I'm wondering if that has anything to do with it? I deleted the framework-res.apk and services.jar from the SD card but I'm at a loss here. It seemed to happen after I changed the build.prop file but I reverted back to stock. Anyone have any ideas?
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.
Hey guys I just flashed Temasek's unofficial CM 7.2 ROM onto my phone. My optimus 2x says it can't find my SD card. For example, I can't open up ROM manager and I can't open up my gallery. Here's what I did:
- Rooted my phone with superoneclick
- Downloaded cm7kang and placed onto my phone (internal SD card, because I don't have an external)
This is when things got strange. I guess this is when I made my mistake, but the next instruction I got was to boot into recovery mode. I searched up how to do this for our particular device and all it said was to turn device off and press Volume down + Power at the same time. I did this, and I got this android icon after 30 seconds, but then my phone booted up with all data deleted (everything was as it was when I'd first unboxed the phone). However, what was strange was when I looked at my phone storage in my settings my internal SD had 3.42GB left, the same as it was before I tried to boot into recovery.
After this issue I just went into market and downloaded ROM manager, and subsequently flashed CWM from there. Then I booted into recovery mode using the manager and downloaded the CM7 zip.
Here I am now. The new ROM seems quite nice, but I have no idea what to do from here My storage settings still shows that I have the internal SD data stored somewhere. In fact, using a file manager, going through the pathways "mnt" and then "emmc", I can see all the data that I had before is actually there. However I cannot move it or do anything to the folder "emmc".
Can anyone please help me? I'm sorry for having to make you read through all that. Thank you.
You did nothing wrong. The Cyanogenmod uses the external sdcard as primary card, not the internal like LG's ROM.
You just need to use the following setting and everything should be back to normal:
Settings -> Cyanogenmod Settings -> Application -> Use Internal Storage
By the way, the trick to go into recovery is indeed holding volume down + power until the second LG logo appears, then release power but still hold voldown. Just try it, nothing can happen. But you don't need to go there again because ROM Manager did that for you, just of you need it in the future.
Sent from my LG-P990 using XDA
tonyp said:
You did nothing wrong. The Cyanogenmod uses the external sdcard as primary card, not the internal like LG's ROM.
You just need to use the following setting and everything should be back to normal:
Settings -> Cyanogenmod Settings -> Application -> Use Internal Storage
By the way, the trick to go into recovery is indeed holding volume down + power until the second LG logo appears, then release power but still hold voldown. Just try it, nothing can happen. But you don't need to go there again because ROM Manager did that for you, just of you need it in the future.
Sent from my LG-P990 using XDA
Click to expand...
Click to collapse
I actually realised that a couple of hours after posting this thread :L I felt so stupid.
Thanks for helping, but right now I have a couple more issues. Perhaps once again I'm not experimenting enough with my new ROM but for now I'm stuck with them.
The first is just a small issue. Even though I've enabled this in the CM settings, I can't see the time in the status bar! There's this little gap on the far right of the status bar where I'm assuming the time should appear but its blank.
The second issue is slightly bigger. I can't watch any YouTube videos at all! I haven't tried downloading the app yet but I've tried the site through the browser; it just keeps saying "Sorry, this video cannot be played. If the videos on the site don't work I don't see why I should be bothered downloading the app. I heard this might be a flash problem so I installed flash player from the market - still not working.
Thanks!
1. Change the clock color. By default is black
2. Update to latest cm7 build.
I have Samsung i897 Captivate (i9000) with SlimICS 4.1.1 Cyanogenmod installed.
Yesterday morning I've found, that my phone is repeatedly show me boot screen (video on boot with many blinking pieces/elements colors shown to me), but did not load an Android at all. I've tried to reboot the phone (with battery eject), but nothing changes: phone shows start-up animations repeatedly.
Last my action evening before was setting alarm (usual task that I've done for one year probably). Dont know what reason to reboot was, maybe no free space available, but dont sure. Before this problem with load I have no problems with phone at all.
I have Clockworkmod installed, but there's no options to boot an Android in safe mode or some similar options. I could get access to the internal phone memory, but not for system partitions. I've tried to wipe dalvik/cache, fix permissions, but no changes at boot.
So could you gents help me to get access to the filesystem: I have memo's & uncynchronised contacts & SMS, which I would like to save before do anything. I know how to reinstall the system (I have backup for it, but not for contacts & memo's).
Thanks.
kalabazoo said:
I have Samsung i897 Captivate (i9000) with SlimICS 4.1.1 Cyanogenmod installed.
Yesterday morning I've found, that my phone is repeatedly show me boot screen (video on boot with many blinking pieces/elements colors shown to me), but did not load an Android at all. I've tried to reboot the phone (with battery eject), but nothing changes: phone shows start-up animations repeatedly.
Last my action evening before was setting alarm (usual task that I've done for one year probably). Dont know what reason to reboot was, maybe no free space available, but dont sure. Before this problem with load I have no problems with phone at all.
I have Clockworkmod installed, but there's no options to boot an Android in safe mode or some similar options. I could get access to the internal phone memory, but not for system partitions. I've tried to wipe dalvik/cache, fix permissions, but no changes at boot.
So could you gents help me to get access to the filesystem: I have memo's & uncynchronised contacts & SMS, which I would like to save before do anything. I know how to reinstall the system (I have backup for it, but not for contacts & memo's).
Thanks.
Click to expand...
Click to collapse
The I9000 and the I897 are 2 different phones. I9000 is the international version of the Captivate, therefor, if you flashed the I9000 bootloaders on a I897 Captivate, you'll have distorted colors/screen.
What exactly was done to the phone before this happened?
Pardon, I have AT&T i897 Captivate phone. I did not flashed, nor updated phone, nothing similar, that could affect phone booting process. Just set an alarm (default, from Clocks), then go sleep. In morning found that my phone stuck in boot process - it show boot-up animation but don't load OS.
kalabazoo said:
Pardon, I have AT&T i897 Captivate phone. I did not flashed, nor updated phone, nothing similar, that could affect phone booting process. Just set an alarm (default, from Clocks), then go sleep. In morning found that my phone stuck in boot process - it show boot-up animation but don't load OS.
Click to expand...
Click to collapse
Have you tried re-flashing the ROM (Without factory reset)? Wipe cache and dalvik.
BWolf56 said:
Have you tried re-flashing the ROM (Without factory reset)?
Click to expand...
Click to collapse
No, I'm no so clean understand reflashing process, so worry to lost my data (I know that my contacts lie here - /data/data/com.android.providers.contacts , but can't found where memo's saved). I could choose "Restore /system" from
"Backup & Resore -> Advanced" in CWM, you mean this?
BWolf56 said:
Wipe cache and dalvik.
Click to expand...
Click to collapse
Yes, did it, but no changes at boot at all (wait there >10 minutes).
kalabazoo said:
No, I'm no so clean understand reflashing process, so worry to lost my data (I know that my contacts lie here - /data/data/com.android.providers.contacts , but can't found where memo's saved). I could choose "Restore /system" from
"Backup & Resore -> Advanced" in CWM, you mean this?
Yes, did it, but no changes at boot at all (wait there >10 minutes).
Click to expand...
Click to collapse
Reflashing your ROM won't touch your data as long as you don't wipe/factory reset. It's what we call a dirty flash, you just wipe cache/dalvik and flash your ROM again with the Gapps.
Thank you for the way to resolve the problem. Spend some time to understand the process of reflashing. Now I collected all files (bootloader, ROM, essentials, gapps and so on of my actual setup) and ready to reflash it with Heimdall.
But still have a question: is there any possibilities to get access to filesystem (for maybe just copy all files from system partitions into Big Brother) before take action in my case?
Will I get access to my contacts & memo's after reflashing? As I understand, if I reflash phone, /data & /datadata partitions (as part of freshy ROM reinstall) will be touched too, then I lost as minumum link to the Wizard Memo (and I'm not sure that installing it from Google Play will restore access to my memo's).
As you could realise, I have no actual backup of my data, so asking maybe dumb questions (
Could I simple use Clockwork's mod option "Restore /system" & "Restore /data" (as I have it in almost fresh backup - 2 months ago)? Will it be analogue to reflashing? Or it revert /system and /data to the stage when it was make, with contacts, programs and so on with 2 months ago state, not current?
kalabazoo said:
Thank you for the way to resolve the problem. Spend some time to understand the process of reflashing. Now I collected all files (bootloader, ROM, essentials, gapps and so on of my actual setup) and ready to reflash it with Heimdall.
But still have a question: is there any possibilities to get access to filesystem (for maybe just copy all files from system partitions into Big Brother) before take action in my case?
Will I get access to my contacts & memo's after reflashing? As I understand, if I reflash phone, /data & /datadata partitions (as part of freshy ROM reinstall) will be touched too, then I lost as minumum link to the Wizard Memo (and I'm not sure that installing it from Google Play will restore access to my memo's).
As you could realise, I have no actual backup of my data, so asking maybe dumb questions (
Could I simple use Clockwork's mod option "Restore /system" & "Restore /data" (as I have it in almost fresh backup - 2 months ago)? Will it be analogue to reflashing? Or it revert /system and /data to the stage when it was make, with contacts, programs and so on with 2 months ago state, not current?
Click to expand...
Click to collapse
I guess i wasn't so clear. What I mean by reflashing is to simply get in recovery mode and reflashing RemICS and their Gapps. Not to start fresh with stock.
Sent from my SGH-I747 using xda app-developers app
You explained well, errors on my side Resolved this issue with copying all data from filesystem, then reflashing with fresh slimrom . For those who fall into same situation: you could get access to filesystem of your phone trough ADB tool, and just copy sensible data to another partition/SD/device. See QtADB program also, very friendly for that.
Turned on my Wi-Fi
Samsung account asked to make update, and install push service
Play store forced to make updates
Facebook app section expired
Then the phone starts to be super slow, then the screen's touch stopped responding and everything was going crazy and lagging and not working.
I was successfully able to stop the PLAY Store updates and turned off my Wi-Fi
then I removed the battery only to force restart
The phone was stuck at the message of ( SAMSUNG Galaxy Note N7000 ) and nothing, after several seconds the processor area is super HOT
Sometimes I was able to see the BootAnimation with the whole music played.
I can successfully enter the download mode and Recovery mode
A message in red is written in Recovery mode:
E:Error in /data/log/recovery_kernel_log.txt (read-only file system)
I am currently using PhliZ
I don't want any format of any type please, the device contains important information especially the SNote app
any way I can recover my phone back, and if possible without formatting ?
By the way I downloaded Odin, rooted the phone with the right matching version, updated to official German jellybean, then downloaded the UAE version to support Arabic language and the system just went updating and all the information was not erased, then the whole things I mentioned above happened.
One of the apps that was always crashing (Root Toolbox PRO), caused the system to hang for several seconds then a message appear saying it stopped responding
mido_ameer said:
Turned on my Wi-Fi
Samsung account asked to make update, and install push service
Play store forced to make updates
Facebook app section expired
Then the phone starts to be super slow, then the screen's touch stopped responding and everything was going crazy and lagging and not working.
I was successfully able to stop the PLAY Store updates and turned off my Wi-Fi
then I removed the battery only to force restart
The phone was stuck at the message of ( SAMSUNG Galaxy Note N7000 ) and nothing, after several seconds the processor area is super HOT
Sometimes I was able to see the BootAnimation with the whole music played.
I can successfully enter the download mode and Recovery mode
A message in red is written in Recovery mode:
E:Error in /data/log/recovery_kernel_log.txt (read-only file system)
I am currently using PhliZ
I don't want any format of any type please, the device contains important information especially the SNote app
any way I can recover my phone back, and if possible without formatting ?
By the way I downloaded Odin, rooted the phone with the right matching version, updated to official German jellybean, then downloaded the UAE version to support Arabic language and the system just went updating and all the information was not erased, then the whole things I mentioned above happened.
One of the apps that was always crashing (Root Toolbox PRO), caused the system to hang for several seconds then a message appear saying it stopped responding
Click to expand...
Click to collapse
I got that error message too E:Error in /data/log/recovery_kernel_log.txt this morning while trying to reflash JB but it was something odd i was trying and i think i got it due to that, as you can enter recovery you will have to format data in order to fix this or format everything to reflash firmware but before you do that, go to philz recovery and then to mounts/Storage go to last option mount USB (while it is connected to the computer ofcourse) you should see both the internal and external card on computer after that with all your data. Back it up on computer. Unmount once you are done and then do all the wipes and reflash JB.
Cheers!!!
Mounting failed
I am currently working on PhilZ-cwm6-JPLSB-UAE-4.93.6-signed
then I coped recovery CWM-6.0.1.2-n7000.zip to the external sd card
I booted in recovery mode, and installed update
then I followed your instructions but no mobiles where detected by the windows 7, a unknown Samsung android is detected in control panel > printers & devices
every time I restart the phone it returns back to PhilZ
Is there is a windows drivers problem ?
mido_ameer said:
I am currently working on PhilZ-cwm6-JPLSB-UAE-4.93.6-signed
then I coped recovery CWM-6.0.1.2-n7000.zip to the external sd card
I booted in recovery mode, and installed update
then I followed your instructions but no mobiles where detected by the windows 7, a unknown Samsung android is detected in control panel > printers & devices
every time I restart the phone it returns back to PhilZ
Is there is a windows drivers problem ?
Click to expand...
Click to collapse
Download from http://forum.xda-developers.com/showthread.php?t=1901191
this:
Code:
<< 12.05.2013 - PhilZ-cwm6 v5.03.0 with CWM 6.0.3.2 based recovery >>
DDLSC - DXLSE - JPLSB - XXLT5 - ZSLO2 Fixed for bootloop
go to recovery and choose install zip and choose the file i mentioned above (zip file) and go the location where you have saved it (external SD) and reboot into recovery, mount storage.
Go to Dr. Ketan's thread for latest samsung drivers install them and see if it shows up your internal and external storage on computer. Backup and go to dowload mode and flash JB again.
Thanks so much
I installed PhliZ 5.0.3.0 updated and installed succussfully
I was able to mount the sdcard and copied all the folders was there to my PC
Then I downloaded a new LSB jellybean UAE edition and worked like sharm
Now my note is working
Thanks for your support
Noise Cancelling is not working
It seems that the phone noise cancelling feature is not working any more, whatever I do in the options while call in progress
Mobile GT-N7000
Android 4.1.2
Baseband N7000XXLSO
Kernel 3.0.31-906407
Build number JZ054.N7000JPLSB