audio2u
Newbie
Hi all,
So here's the story.
Got the Galaxy Note (GT-N7000) about 3 or 4 months ago.
Got root and loaded ICS Stunner (1.4.26.1, if that's important).
For the most part, it was a good ROM, and I like the Apex launcher which came as part of that ROM.
The only hiccup was bluetooth. It would only lockup with my car's BT system about 1 time in 20. As you can imagine, that got old real quick.
So, earlier this week, I see that CM9RC1 came out with support for the N7000.
I've never run a Cyanogen ROM on any device, but I know they are considered to be one of the best custom ROMs out there, so I thought "what the hell... let's backup, wipe, and load the CM9RC1 build".
So, I boot into CWM recovery menu, backup to internal memory (ie the 16GB of data space), and then wiped everything.
And by everything, I mean:
* wipe data/factory reset
* wipe cache partition (redundant, I know, 'cause the factory reset does this anyway)
* advanced/wipe dalvik cache
* advanced/wipe battery stats
Then:
* install zip from sd card/choose zip from internal sd card/cm-9.0.0-rc1-n7000.zip
I then see:
Finding update package....
Opening update package....
Installing update...
assert failed: getprop("ro.product.device") == "galaxynote" || getprop("ro.build.product") == "galaxynote" || getprop("ro.product.device") == "n7000" || getprop("ro.build.product") == "n7000" || getprop("ro.product.device") == "GT-N7000" || getprop("ro.build.product") == "GT-N7000"
E:Error in /emmc/cm-9.0.0-rc1-n7000.zip
(Status 7)
Installation aborted
I didn't know what any of that meant, other than it was not what I was wanting to see.
So, I figured "oh well, that didn't work, let's just wipe everything again and reload the backup."
Upon selecting the restore file, I see:
Checking MD5 sums....
Erasing boot before restore...
Restoring boot image...
Restoring system...
At this point, I see hundred of file names cycling through.
Then suddenly, this:
Error while restoring /system!
Ahhh crap.
Oh well, I still have the ICS Stunner zip file, so I'll just wipe everything and reload that and rebuild everything from scratch. Slow, painful, but at least I'll be ok.
Except the load process never finishes. The progress bar (which takes up perhaps the middle 50% of the screen) proceeds nicely all the way to the end, but then keeps drawing all the way to the right hand edge of the screen and never terminates. Have to hold the keys for about 8 seconds to get the device to reboot... and then we're back to square one.
So, that's my tale of woe.
Anyone got any suggestions on how to get out of this situation?
Any advice would be greatly appreciated.
So here's the story.
Got the Galaxy Note (GT-N7000) about 3 or 4 months ago.
Got root and loaded ICS Stunner (1.4.26.1, if that's important).
For the most part, it was a good ROM, and I like the Apex launcher which came as part of that ROM.
The only hiccup was bluetooth. It would only lockup with my car's BT system about 1 time in 20. As you can imagine, that got old real quick.
So, earlier this week, I see that CM9RC1 came out with support for the N7000.
I've never run a Cyanogen ROM on any device, but I know they are considered to be one of the best custom ROMs out there, so I thought "what the hell... let's backup, wipe, and load the CM9RC1 build".
So, I boot into CWM recovery menu, backup to internal memory (ie the 16GB of data space), and then wiped everything.
And by everything, I mean:
* wipe data/factory reset
* wipe cache partition (redundant, I know, 'cause the factory reset does this anyway)
* advanced/wipe dalvik cache
* advanced/wipe battery stats
Then:
* install zip from sd card/choose zip from internal sd card/cm-9.0.0-rc1-n7000.zip
I then see:
Finding update package....
Opening update package....
Installing update...
assert failed: getprop("ro.product.device") == "galaxynote" || getprop("ro.build.product") == "galaxynote" || getprop("ro.product.device") == "n7000" || getprop("ro.build.product") == "n7000" || getprop("ro.product.device") == "GT-N7000" || getprop("ro.build.product") == "GT-N7000"
E:Error in /emmc/cm-9.0.0-rc1-n7000.zip
(Status 7)
Installation aborted
I didn't know what any of that meant, other than it was not what I was wanting to see.
So, I figured "oh well, that didn't work, let's just wipe everything again and reload the backup."
Upon selecting the restore file, I see:
Checking MD5 sums....
Erasing boot before restore...
Restoring boot image...
Restoring system...
At this point, I see hundred of file names cycling through.
Then suddenly, this:
Error while restoring /system!
Ahhh crap.
Oh well, I still have the ICS Stunner zip file, so I'll just wipe everything and reload that and rebuild everything from scratch. Slow, painful, but at least I'll be ok.
Except the load process never finishes. The progress bar (which takes up perhaps the middle 50% of the screen) proceeds nicely all the way to the end, but then keeps drawing all the way to the right hand edge of the screen and never terminates. Have to hold the keys for about 8 seconds to get the device to reboot... and then we're back to square one.
So, that's my tale of woe.
Anyone got any suggestions on how to get out of this situation?
Any advice would be greatly appreciated.