Related
Hey guys,
I have really been reading and learning alot since rooting my phone and flashing the MoDaCo rom. Im tempted to go back to RUU get the update and try to root again but I think its smarter for me to just wait on a updated MoDaCo ROM with the update in it. But I have a couple questions I hope someone can answer just in general.
1. Would going back to RUU to get the update, re-rooting and re-flashing MoDaCo hurt my app2SD that is already set up? Meaning I would have to re format the SD and apply all my apps back after im done.
2. Is it possible to go back to RUU, get the update, re-root and re-flash the MoDaCo ROM and not have any issues afterwards, and still have the update?
3. Whats the major benefit of updating at all. I mean after root and MoDaCo ROM, im having no issues with my phone whatsoever. But seems like everyone is updating so am I missing something key that my hero needs to have?
Thanks in advance for any answers. Im loving this android stuff. I can see myself learning alot from all of you.
swaze said:
Hey guys,
I have really been reading and learning alot since rooting my phone and flashing the MoDaCo rom. Im tempted to go back to RUU get the update and try to root again but I think its smarter for me to just wait on a updated MoDaCo ROM with the update in it. But I have a couple questions I hope someone can answer just in general.
1. Would going back to RUU to get the update, re-rooting and re-flashing MoDaCo hurt my app2SD that is already set up? Meaning I would have to re format the SD and apply all my apps back after im done.
2. Is it possible to go back to RUU, get the update, re-root and re-flash the MoDaCo ROM and not have any issues afterwards, and still have the update?
3. Whats the major benefit of updating at all. I mean after root and MoDaCo ROM, im having no issues with my phone whatsoever. But seems like everyone is updating so am I missing something key that my hero needs to have?
Thanks in advance for any answers. Im loving this android stuff. I can see myself learning alot from all of you.
Click to expand...
Click to collapse
This is basically the same situation I am in. I reflashed MoDaCo not realizing that it resets the software version back to 1.29.651.1, so there's really no point to updating in the first place if you want to run the Current 1.1 MoDaCo ROM, which also breaks the Voicemail app. If I were you, or if I hadn't already gone through the process, I'd just wait for the updated MoDaCo ROM that includes the Sprint Maint Rel update. I think he said he'd probably have it ready by the weekend or Monday (11/23). Right now I'm not sure if I'll keep what I have for a few days until the patched ROM is ready, or restore the nandroid backup I made right after applying the Sprint upgrade and rooting, or go back to stock again and not apply the update and reinstall MoDaCo 1.1.
Gambit727 said:
This is basically the same situation I am in. I reflashed MoDaCo not realizing that it resets the software version back to 1.29.651.1, so there's really no point to updating in the first place if you want to run the Current 1.1 MoDaCo ROM, which also breaks the Voicemail app. If I were you, or if I hadn't already gone through the process, I'd just wait for the updated MoDaCo ROM that includes the Sprint Maint Rel update. I think he said he'd probably have it ready by the weekend or Monday (11/23). Right now I'm not sure if I'll keep what I have for a few days until the patched ROM is ready, or restore the nandroid backup I made right after applying the Sprint upgrade and rooting, or go back to stock again and not apply the update and reinstall MoDaCo 1.1.
Click to expand...
Click to collapse
What do you mean break the voicemail app? I don't think I am having any issues with my voicemail. Can you tell me what that is you are referring to?
BTW, if you do decide to nandroid and root, will you just not flash a new ROM or use the stock ROM instead?? My main reason for using MoDaCo's ROM was for app2SD, i definately don't want to go back to apps on the internal memory now.
So currently I'm running on liberty x1.5 and when checking system phone updates, it says it is up to date. I'm sure it's not however since I see news of 2.2 laying around the net if I'm not mistaken. Do I have to revert back to factory to update my phone or how exactly does the process go about. Do I even benefit from the new version if I am running liberty or will liberty have it's own updates... sorry I am new to this whole rom scene and seeking guidance, thanks in advance.
If you put a rom on your phone you won't be able to pull any updates ota... the 2.3.3 update is a leak that tbh put on the net... in order to put it on your phone you need to sbf, and then install the 2.3.3... there are guides on doing this at mydroidworld.com
Sent from my DROIDX using XDA App
jinho11050 said:
So currently I'm running on liberty x1.5 and when checking system phone updates, it says it is up to date. I'm sure it's not however since I see news of 2.2 laying around the net if I'm not mistaken. Do I have to revert back to factory to update my phone or how exactly does the process go about. Do I even benefit from the new version if I am running liberty or will liberty have it's own updates... sorry I am new to this whole rom scene and seeking guidance, thanks in advance.
Click to expand...
Click to collapse
There is no new OTA yet. It's a leak also OTA's won't come to your phone on anything other than stock.
Thank you very Much guys. I don't want to trouble by making a new thread so ill ask here. I tried restoring to factory form from both reboot clockwork and on settings privacy but it just leads me back to liberty rom.
So to make things clear, there is no official 2.2 jslust a leak. Plus would I even benefit from any updates if I'm running a modded rom?
jinho11050 said:
Thank you very Much guys. I don't want to trouble by making a new thread so ill ask here. I tried restoring to factory form from both reboot clockwork and on settings privacy but it just leads me back to liberty rom.
So to make things clear, there is no official 2.2 jslust a leak. Plus would I even benefit from any updates if I'm running a modded rom?
Click to expand...
Click to collapse
Official 2.2 is the version that liberty is based off of. doing a factory reset from within the OS will not take you back to factory stock ROM. Did make a nandroid backup before flashing liberty? if so then you should be able to do a restore and you will have a rooted stock rom. If you didn't make a backup then you will need to SBF (I SBF between roms anyway).
Pretty sure he's just confused with version numbers.
Froyo = 2.2
Gingerbread = 2.3
The only available gingerbread rom at the moment is leaked stock and is version 2.3.3. 2.2 is Froyo and has been officially out now for months, it is what all the custom roms out (liberty, fission, rubix etc) are based off of.
so does this mean im automatically running on 2.2 because im using liberty? if so why does it say 2.1.2 on the about phone in settings? does it matter?
I'd be willing to bet it doesn't say 2.1.2 and it actually says 2.2.1. Am I right?
(To answer your question, yes you are running 2.2 Froyo. There are minor update builds to each major release, hence 2.2.1 and for Gingerbread, 2.3.3).
[BELL] Revert back to "stock" Bell Froyo 2.2.2 or GB 2.3.4 from CyanogenMod7-PreBeta2
Hi all,
The Nandroid backup I performed of Bell GB 2.3.4 before installing CM7 PreBeta2 will not restore properly, I'm getting an MD5 mismatch.
This was the only proper backup I had previous to installing CM7 PB2 - all went well and I received confirmation that the backup was successful prior to installing CM7.
How would I go about returning to Bell GB 2.3.4 without a proper Nandroid backup? Do I have to flash Stock Bell Froyo 2.2.2 first then install 2.3.4?
I do not want to brick my device by returning to an older Android - my device is unlocked.
Your help is very appreciated!
You shuold use nshimselfs gobstopper 2.2.2 to get back to stock bell 2.2.2. From there you can do whatever you want. You can also use his gobstopper bell 2.3.4 to go directly to that, instead of going back to 2.2.2 first.
Find the user page of nfhimself, then look at threads started by him.
Good luck! cheers
Magnetox said:
You shuold use nshimselfs gobstopper 2.2.2 to get back to stock bell 2.2.2. From there you can do whatever you want. You can also use his gobstopper bell 2.3.4 to go directly to that, instead of going back to 2.2.2 first.
Find the user page of nfhimself, then look at threads started by him.
Good luck! cheers
Click to expand...
Click to collapse
Thanks - Bell 2.3.4 will not install directly, I get an error while it's flashing system... I need to go back to 2.2.2 then back to 2.3.4 as per what I've read. Downloading the 2.2.2 gobstopper now... will keep you posted.
dascope said:
Thanks - Bell 2.3.4 will not install directly, I get an error while it's flashing system... I need to go back to 2.2.2 then back to 2.3.4 as per what I've read. Downloading the 2.2.2 gobstopper now... will keep you posted.
Click to expand...
Click to collapse
Ok, I'm sure it will work from the 2.2.2 gobstopper though.
Good luck!
Magnetox said:
Ok, I'm sure it will work from the 2.2.2 gobstopper though.
Good luck!
Click to expand...
Click to collapse
<Argh>. Similar problem as 2.3.4, different location... this is what happens when I choose zip Bell_2.2.2.stock.zip off Internal (tried External too) after performing a wipe data/factory reset:
Updating app.bin (system mmcblk0p12)...
assert failed: package_extract_file("app.bin", "/internal/app.bin")
E:Error in /sdcard/Bell_2.2.2.stock.zip
(Status 7)
Installation aborted.
I'm using romracer's CWM 4.0.1.5-atrix3.2
Anybody have ideas?
Think I figured it out... I needed to use Tenfar's CWM (unlocked) to install these gobstoppers...
I have a friend with a Motorla Atrix on Bell. She just upgraded to 2.3 and she does not like the ui updates and wants to go back to 2.2 (both were stock versions). Do I have to do these same steps or is there some easier way?
Thanks
dascope said:
Think I figured it out... I needed to use Tenfar's CWM (unlocked) to install these gobstoppers...
Click to expand...
Click to collapse
Exactly what's needed and make sure you UNLOCKED , oem unlock i mean .. otherwise you'll keep getting this error.
I have been getting this update for my TF101 every few days or so. It downloads an update, then when I click on install update it reboots, starts loading the update and fails halfway through the intall giving me the sad android with the triangle exclamation point. I read on another thread that you have to clear the cache in DMClient, which I do every time this happens. But why does it continue to send me this stupid update? When I followed the previous thread I mentioned, I was able to see that the update was actually meant for the prime, not the TF101. Just wish they would stop sending me an update that makes me get my hopes up for ICS.
Anybody else having this happen?
Maybe you chosen by asus to be a lucky ICS beta tester.
mikelt89 said:
Maybe you chosen by asus to be a lucky ICS beta tester.
Click to expand...
Click to collapse
haha, yeah if this is what ICS is going to be like, then no thanks. I am not really having any issues with honeycomb at the moment (after overclocking). But like most everybody else, I can't wait to try out something shiny and new.
Maybe the OP should UNROOT and install a legit ROM in order to be able get the update??
Thiesen said:
Maybe the OP should UNROOT and install a legit ROM in order to be able get the update??
Click to expand...
Click to collapse
That's probably the way to go, but I've had no luck thus far. I'm on stock Rom with Netformer 1.6 kernel. I tried doing this with OTA Rootkeeper. Unrooted, installed update, got same error. Then rebooted and re-rooted with the OTA Rootkeeper app. Does this mean I need to revert back to original kernel? Everything has been pretty good on Netformer, and it's definitely more snappy than stock.
kwaze said:
That's probably the way to go, but I've had no luck thus far. I'm on stock Rom with Netformer 1.6 kernel. I tried doing this with OTA Rootkeeper. Unrooted, installed update, got same error. Then rebooted and re-rooted with the OTA Rootkeeper app. Does this mean I need to revert back to original kernel? Everything has been pretty good on Netformer, and it's definitely more snappy than stock.
Click to expand...
Click to collapse
Which stock ROM are you on? You might be getting the OTAs if you aren't running the latest (8.6.5.21?). The custom kernel probably installed a kernel module that is preventing the update from flashing.
Can you grab the OTA? I'm curious what they are sending you. It will be in /cache/dlpkgfile- you can copy that someplace and upload it. I think these should do it, but PM if you need help with terminal commands.
In terminal, type:
cp /cache/dlpkgfile /Removable/MicroSD/
OR with adb:
adb pull /cache/dlpkgfile
Here's the zip. Maybe you can tell me what this update really is. I guess my current stock Rom version is 8.6.5.19. Sounds like the kernel is preventing me from updating. The real question is, do I want to install any of these updates from Asus? Any disadvantage that you know of?
That file is the US 8.6.5.21 OTA. I lost track of the all the root methods, but I thought that Nachoroot was working with .21. I've never used OTA rootkeeper, so I can't comment on if that will work.
It's kinda odd how you are getting it now? There is a rooted version of the stock rom you can flash via CWM so that you don't have to unroot. It will have the stock kernel and you will keep whatever bootloader you have now.
http://forum.xda-developers.com/showthread.php?t=1409584
EDIT: doaist has posted CWM friendly versions of the OTAs as well- there are much smaller files since they patch the existing rom. Look in the development forum- The OTA came out around Christmas, so it will be after that.
Thanks for the info. I'll flash the updated rom and see how it goes.
Via xda app
kwaze said:
That's probably the way to go, but I've had no luck thus far. I'm on stock Rom with Netformer 1.6 kernel. I tried doing this with OTA Rootkeeper. Unrooted, installed update, got same error. Then rebooted and re-rooted with the OTA Rootkeeper app. Does this mean I need to revert back to original kernel? Everything has been pretty good on Netformer, and it's definitely more snappy than stock.
Click to expand...
Click to collapse
You're running an image that has different hash values than Asus original image has... that is why Asus validation does not work. Hence, you should revert back to the original image Asus provides.
This answer have been given ALOT of times in other threads already.
I rooted mine with nachoroot on the 21 update. It works fine.
Sent from my Transformer TF101 using xda premium
I read somewhere on the forums, if you applied an update from asus one time, then you can't get the same again. just flash manual from download site.
My friend is goofy and doesn't remember anything about how he rooted his Nook Color except he used autonooter. He asked me to take a look because he wants to upgrade it to get flash on it and give it to his fiance. I feel it would be easier to go back to stock and start over but if anyone else has any suggestions I would be open to them. All he wants is it to support flash.
what version is he on? is he running stock rooted?
start with this thread if you're just looking at stock rooted:
http://forum.xda-developers.com/showthread.php?t=1494901
chibucks said:
what version is he on? is he running stock rooted?
start with this thread if you're just looking at stock rooted:
http://forum.xda-developers.com/showthread.php?t=1494901
Click to expand...
Click to collapse
How can I tell, like I said I am coming to this after the fact.
jonny4 said:
How can I tell, like I said I am coming to this after the fact.
Click to expand...
Click to collapse
settings > device info > about your nookcolor > software version
chibucks said:
settings > device info > about your nookcolor > software version
Click to expand...
Click to collapse
version 1.1.0
jonny4 said:
version 1.1.0
Click to expand...
Click to collapse
i'd probably first update to 1.4.2 (the link to the B&N file and what to do is in the thread that was provided earlier) - then manualnooter it using gmpower's helpful thread (put clockwork recovery on an sdcard with the files).
edit to add 1.4.2 link: http://www.barnesandnoble.com/u/Software-Updates-NOOK-Color/379003190/
My friend sent me the stuff he had for the nook and everything he sent me is listed, next. clockworkmod, nookcolor_v1.1.0_r2, win32diskimager-RELEASE-0.1-r15-win32, win32diskimager-RELEASE-0.1-r15-win32, 128mb_rootpack-0.7, auto-nooter-3.0.0, and 1gb_clockwork-0.7, and I have no clue what he actually used here or what everything is.
chibucks said:
i'd probably first update to 1.4.2 (the link to the B&N file and what to do is in the thread that was provided earlier) - then manualnooter it using gmpower's helpful thread (put clockwork recovery on an sdcard with the files).
edit to add 1.4.2 link: http://www.barnesandnoble.com/u/Software-Updates-NOOK-Color/379003190/
Click to expand...
Click to collapse
If I update to it will it wipe out the root that is already on there, if so that would be awesome because I would be able to start from scratch.
jonny4 said:
If I update to it will it wipe out the root that is already on there, if so that would be awesome because I would be able to start from scratch.
Click to expand...
Click to collapse
Yes... one issue is that if he had CWM installed on EMMC it will not update correctly... you will need to use the stock 1.4.1 cwm flashable I provided in another thread and let the nook update.
I am adding snapshots of the 2 storage spots that pop up when I hook the nook to the computer, maybe it can help you guys determine what my moronic friend actually did.
pal jonny,
While I am proud of your generosity toward your friend by helping him but, seriously, if you don't know what to do, why take up that task? If you know then you can help, sure but based on question your asked up there, I feel you don't.
Getting confusing and performing what you not comfortable with could make your friend's NC a mess.
Your friend, seems like he did it b4, why not let him do this time since he collected all info anyway.
votinh said:
pal jonny,
While I am proud of your generosity toward your friend by helping him but, seriously, if you don't know what to do, why take up that task? If you know then you can help, sure but based on question your asked up there, I feel you don't.
Getting confusing and performing what you not comfortable with could make your friend's NC a mess.
Your friend, seems like he did it b4, why not let him do this time since he collected all info anyway.
Click to expand...
Click to collapse
Because I do know what to do, I have rooted 3 phones but the Nook Color is new to me and I don't know what his dumb ass did and neither does he, lol. I am working in a different way than most people have, receiving something already rooted and not knowing what was done to get it to that point. I recently had to un-root my phone and it was easier because I was the person who rooted it to begin with.
I am also asking as many questions to get as much information to make sure I do not brick the device.
Sent from my PC36100 using XDA
jonny4 said:
I am also asking as many questions to get as much information to make sure I do not brick the device.
Sent from my PC36100 using XDA
Click to expand...
Click to collapse
My suggestion would be take it back to stock... then install what ROM he desires... quite simple.
If so,
a. if you/he wants custom ROM, get CM7.2 RC1 (KANG is a great version). Just format /data, /system, /cache and Dalvik then install ROM
b. if you/he wants stock ROM, 1.4.2 is the latest. MN 5.0.2.19 should be a good tool to root.
votinh said:
If so,
a. if you/he wants custom ROM, get CM7.2 RC1 (KANG is a great version). Just format /data, /system, /cache and Dalvik then install ROM
b. if you/he wants stock ROM, 1.4.2 is the latest. MN 5.0.2.19 should be a good tool to root.
Click to expand...
Click to collapse
Is there something wrong with the regular cyanogenmod stable 7.1?
If I go stock build does it include flash, he wants to give it to his girlfriend to play movies as well. I am trying to convince him to go with cyanogen mod but he wants the functionality of the nook software, I told him there is a Nook app but he hasn't gotten back to me.
jonny4 said:
Is there something wrong with the regular cyanogenmod stable 7.1?
If I go stock build does it include flash, he wants to give it to his girlfriend to play movies as well. I am trying to convince him to go with cyanogen mod but he wants the functionality of the nook software, I told him there is a Nook app but he hasn't gotten back to me.
Click to expand...
Click to collapse
Nothing wrong with CM7.1. It's your choice.
If he wants stock ROM then install stock for him, flash should be well supported.
Note: Nook apps is NOT equivalent of stock feature.
Why use nooks Os when cyanogen has stable 7.02 and a promising ICS? I say give the new phirenook. NOOBS seem to like the modifications. Then install the B&N app and she's good.
Just an idea. I haven't tried the stock for some time.
I am back trying to work on this nook color again and i can say without a doubt all he did was autonooter. So if I update to the newest version of the oem o.s. will it wipe out the autonooter because this will be easier for me if it does.
If there is any recovery on it other than B&N's stock recovery... the update will fail... look for my 1.4.1 cwm flashable stock file.