Related
Had my X for a week now. It is rooted and running DarkSlideBlur 4.2, I have several other ROM's I am wanting to try out......
If I understand what I have been reading right, I can use Nandroid Backups to return to ROM's I like, or is it better to reflash them?
Trying to avoid the whole setup process....
Thanks in advance
Mace
A nandroid would be the route to go. It restores your phone to the exact state it was when you backed it up. Every call text message everything will be as it was.
Nandroid all the way. Works every time
Sent from my HTC Glacier using XDA App
MaceBewley said:
Had my X for a week now. It is rooted and running DarkSlideBlur 4.2, I have several other ROM's I am wanting to try out......
If I understand what I have been reading right, I can use Nandroid Backups to return to ROM's I like, or is it better to reflash them?
Trying to avoid the whole setup process....
Thanks in advance
Mace
Click to expand...
Click to collapse
As already stated, a nandroid is a best bet. Just keep in mind if you do any updates (OTA) and the radio gets updated (i.e. 2.3.15 to 2.3.340) an old nandroid will brick your phone due to an older bootloader
Sent from my DROIDX using XDA App
Thanks guys! I thought that was the case, as I have been all over these forums "researching" for a couple months before I got the X!
Now off to research "Radio"?? (thats a new one to me)
But what if you mount your system and get stuck in the bootup. i cant even get to the recovery. i dont know what to do.
Nandroid always has your back. Something gets screwed and you are stuck in a boot loop, plug in the usb or charger, pull the battery, put it in and boot up. That will hijack back into Clockwork.
Always Wipe Data/Factory Reset, Wipe Cache/Advanced/Wipe Dalvik before you flash a new ROM and you "almost" always avoid a boot loop.
Sent from my DROIDX using XDA App
that is clockwork recovery, the stock recovery is accessed with a combination of hard keys which i am not sure which they are off the top of my head. in that you can wipe, but unfortunately no nandroid restore.
I tried every rom out there. The fastest most stable best battery life is stock. Deodexed stock. You can theme and font.
Sent from my DROIDX using XDA Premium App
mattmartin77 said:
that is clockwork recovery, the stock recovery is accessed with a combination of hard keys which i am not sure which they are off the top of my head. in that you can wipe, but unfortunately no nandroid restore.
Click to expand...
Click to collapse
The hard keys are volume down and camera button if you wanted to know
Thats to get to the bootloader. Recovery is home and power and hold on until it comes up. To get into safe mode you hold power and the menu button
Sent from my DROIDX using XDA Premium App
Excited as all outdoors because it was already rooted. Got home, sat down and went to put in my information, hmmmmmm, I got it from a black guy but there's a asian gmail account. :sirens: Maybe he purchased it from the guy just as I've done. I enter my account info and try to remove his, the apps need his so I cant delete him. Nothing a wipe won't fix right? Wrong. So after reading here a very small amount I realize I may need the original owner's B&N account info to resolve this.
Anyone care to chime in on this before I bother this guy for my money back?
Try to do a full wipe and return to original firmware. Then register an account for BN. Flash to cm7 afterwards. Hopefully it will work.
Sent from my NookColor using Tapatalk
If you use another rom like cm7 you won't have to worry about it. They don't register anything with Barnes and noble.
Sent from my NookColor using XDA Premium App
deezndc said:
Excited as all outdoors because it was already rooted. Got home, sat down and went to put in my information, hmmmmmm, I got it from a black guy but there's a asian gmail account. :sirens: Maybe he purchased it from the guy just as I've done. I enter my account info and try to remove his, the apps need his so I cant delete him. Nothing a wipe won't fix right? Wrong. So after reading here a very small amount I realize I may need the original owner's B&N account info to resolve this.
Anyone care to chime in on this before I bother this guy for my money back?
Click to expand...
Click to collapse
If you are already at CM7 on the NC, then you will have to delete the old gmail and youtube accounts and sign-in to your own gmail and youtube accounts.
I just did a complete wipe of everything (SD card included) and his information disappeared. Thanks for the replies! Now to really dig into this.
Sent from my NookColor using XDA Premium App
How can I determine which method was used to root the Nook?
deezndc said:
How can I determine which method was used to root the Nook?
Click to expand...
Click to collapse
Try to do the 8 failed boots and you shouldn't have to worry about it...
8 failed = system recovery (will take it back to stock)
update to 1.2 if necessary
register with B&N if not going to CM7 (I do it anyway even using CM7)
Root or CM7
Now its how YOU want it... not some asian girl/guy/whatever.
DizzyDen said:
Try to do the 8 failed boots and you shouldn't have to worry about it...
8 failed = system recovery (will take it back to stock)
update to 1.2 if necessary
register with B&N if not going to CM7 (I do it anyway even using CM7)
Root or CM7
Now its how YOU want it... not some asian girl/guy/whatever.
Click to expand...
Click to collapse
What if once I do the system recovery, its already B&N registered? Am I at a lost then?
Sent from my NookColor using XDA Premium App
deezndc said:
What if once I do the system recovery, its already B&N registered? Am I at a lost then?
Sent from my NookColor using XDA Premium App
Click to expand...
Click to collapse
If you are using CM7, the "CyanogenMod 7" logo appears when booted. There is no registration of the NC with CM7. CM7 is not rooting. It is firmware that replaces the B&N firmware.
A rooted NC will initially splash the "Read Forever tm" logo when booted. The older B&N firmware splashed "Touch the Future of Reading" logo, if I remember correctly. A rooted NC is the stock B&N firmware that has been altered to allow (root) access to the Android Market apps and still retain all the original B&N functions/features. A rooted NC does require registering the NC.
If the rooted NC is not registered to your B&N account, then:
1. Touch the "U" with the up-arrow icon, select Settings.
2. In Settings, select Device Info.
3. In Device Info, select Erase & Deregister Device.
4. Touch the Erase & Deregister Device button to start the process.
5. Follow any other instructions to complete the erase and deregister the NC process which may follow.
6. Reboot NC, it should return to stock setup, as when it was new.
7. Follow the instructions and register the device using your own B&N account.
8. Update NC to 1.2.
9. Root NC using ManualNooter 4.6.16. Instructions are here.
10. Enjoy!
I hope this helps.
Thanks for the info Bluepen.....I now have a new issue. Somehow, someway I've managed to be in a boot loop, the funny part is it's flashing between the CM7 splash and ClockworkMod Recovery. I've been searching since last evening to no avail, not one single instance matches this one.
Any help would be greatly appreciated.
I've tried the 8x boot thing, I can't tell if it's even shutting down. Also tried the three finger deal, may need to do more research on that one. I've also formatted my sdcard so basically I'm in route to stock which I don't mind if I can just get there.
Slowly but surely this thing will run like my Shift...!!!!! I got it, basically I'm registered with B&N and on the stock ROM, WHEWWWW!
I went to nookdevs.com ( http://mrm3.net/nook-color-recover-any-bricked-device/ ) along with the help perusing around here I was able to fix.
Cyanogen is up and running again.....
deezndc said:
Slowly but surely this thing will run like my Shift...!!!!! I got it, basically I'm registered with B&N and on the stock ROM, WHEWWWW!
I went to nookdevs.com ( http://mrm3.net/nook-color-recover-any-bricked-device/ ) along with the help perusing around here I was able to fix.
Cyanogen is up and running again.....
Click to expand...
Click to collapse
It is good that your NC is back running CM7!
Are you dual booting from/on emmc or booting from the micro sdHC memory card or have you applied CM7 to emmc overwriting theB&N firmware?
Sent from my NOOKcolor using XDA Premium App
I've overwritten the B&N firmware, so I guess out of those three options it would be the latter.
Sent from my NookColor using XDA Premium App
Congrats. Now overclock the **** out of it =D and install the tegra 2 games.
Sooo....I try to to reboot and I get hung up in Recovery. The only way to reboot is to remove the SD card.
Anyone else experience this?
Sent from my NookColor using XDA Premium App
So amongst all my stupor I realize (after reading so much more) that I need to remove the SD card to boot back into cm7 or stock once I'm done in CWM. What a difference that makes. Smh.
Sent from my NookColor using XDA Premium App
deezndc said:
So amongst all my stupor I realize (after reading so much more) that I need to remove the SD card to boot back into cm7 or stock once I'm done in CWM. What a difference that makes. Smh.
Sent from my NookColor using XDA Premium App
Click to expand...
Click to collapse
Or format the uSD to remove CWM and make it usable to yourCM7 install.
YCGIYWG
Will that allow me to not have to remove it everytime and what are the chances of getting Nook Stock to boot once its formatted?
Sent from my NookColor using XDA Premium App
The reason I ask that is because I've been stuck on the "N" screen several times to no avail.
When you copy your ROM to your SD card, be sure to leave it on there after you flash. If you somehow manage to brick your phone, go into recovery, wipe data, wipe cache, and wipe dalvik cache. Flash the saved ROM that was on your SD card. Boom. Simple.
I had a personal experience that made me post this. Though It's obvious to most, it probably isn't to noobs.
Sure saved me a trip to the Sprint store
Sorry if this was already posted before by somebody else.
Sent from my PC36100 using XDA Premium App
Actually, I think if you brick your phone there isn't much of anything you can do. When the phone is bricked it will not power up, into recovery charge anything. Now, bootloops on the other hand this works for.
Isn't boot loop soft bricking? If so, that's what I meant.
Sent from my PC36100 using XDA Premium App
Jardicel said:
Isn't boot loop soft bricking? If so, that's what I meant.
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
No it is not, you can get a loop just by placing a mismatch file on your phone. I get bootloops if my phone dont like framework apk's I change. I think you should remove the work "brick" from the heading. Alot of people get confused about bricking. Now in all honesty if you brick your phone you are generally S.O.L....
Also the ability alone to go into recovery means its not bricked...
From what I've learned on different threads, there are three types of bricking. Including soft brick, where you cannot load the system UI and are stuck somewhere before. You could access recovery.
Sent from my PC36100 using XDA Premium App
This is very basic stuff.. I wouldn't consider boot loop to be soft brick.
Deck's + SZ + SuperCharger script + ViperMod script.
Jardicel said:
From what I've learned on different threads, there are three types of bricking. Including soft brick, where you cannot load the system UI and are stuck somewhere before. You could access recovery.
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
ok but really bricking is not good and a boot loop is not a big deal my friend.. Just saying don't throw that word around in my opinion unless its really over for you... like not booting up at all
Edit; why not change titile Just in case you Bootloop your phone... Use this method
I agree that people use the term brick a bit too often. A brick is nothing less than a paper weight of a phone. No booting, no recovery, and won't charge.
Sent from my PC36100 using XDA App
Bricked is a state, like being dead, there are no shades of grey it is a binary, it is either bricked or it isn't. It is bricked because you can't bring it back to life.
Mine is so dead the Jig doesn't even phase it. It is graveyard, doornail dead. Dead as dead gets.
Jardicel said:
When you copy your ROM to your SD card, be sure to leave it on there after you flash. If you somehow manage to brick your phone, go into recovery, wipe data, wipe cache, and wipe dalvik cache. Flash the saved ROM that was on your SD card. Boom. Simple.
I had a personal experience that made me post this. Though It's obvious to most, it probably isn't to noobs.
Sure saved me a trip to the Sprint store
Sorry if this was already posted before by somebody else.
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
my phone very well
Hello!
I had my S4 rooted and nandroid back up. I was trying to install this link:
http://forum.xda-developers.com/showthread.php?t=2316308
I installed it and gapp installed too and rebooted. I got this message appears
"System software not authorized by AT&T has been found on your phone"
upper corner in orange says "kernel Failed"
That means I did something wrong?
I read about odin. Does Stock rom get you back to fully stock?
Thanks
Did you run loki doki? see.your on at&t..locked bootloader and i dont think that rom is autolokied. Boot back into recovery flash ld.and see if it boots.
Yes odin will put your phone back to.stock,been there done that lol.
sent from my CleanRom 1.5 i337m
force70 said:
Did you run loki doki? see.your on at&t..locked bootloader and i dont think that rom is autolokied. Boot back into recovery flash ld.and see if it boots.
Yes odin will put your phone back to.stock,been there done that lol.
sent from my CleanRom 1.5 i337m
Click to expand...
Click to collapse
Ok, I been reading some threads about recovery, I didn't relieze, i was away from s3 so long. I just restored from backup data and it boots into this stuck Samsung screen with custom unlocked logo. Bootloop?
Havent seen that particular screen but yeah sounds like your bootlooped. If.you can three finger back into recovery and have a nandroid i would full wipe then Restore your back up (even though people.say restoring wipes anyway..id wipe.if u.are using twrp do not format data!).if.your still looped you may have to try and odin back to stock.firmware can be found on sammobile.com had to do this the other night due to a bad nandroid..lots of fun lol.
sent from my CleanRom 1.5 i337m
force70 said:
Havent seen that particular screen but yeah sounds like your bootlooped. If.you can three finger back into recovery and have a nandroid i would full wipe then Restore your back up (even though people.say restoring wipes anyway..id wipe.if u.are using twrp do not format data!).if.your still looped you may have to try and odin back to stock.firmware can be found on sammobile.com had to do this the other night due to a bad nandroid..lots of fun lol.
sent from my CleanRom 1.5 i337m
Click to expand...
Click to collapse
Thank you!:victory:
My heart dropped like fainting ghost after I see the at&t software showed up. I wiped factory reset and goes past the samsung with unlocked logo into at&t boot up like new phone. It took 5 mins to get into welcome screen. All is working.
Now, I begun to wondering why my logo says it bootloader unlocked and I download correct at&t rom is in? I use this causal download from this link:
http://forum.xda-developers.com/showthread.php?t=2297900
I am trying to understand and pick my first rom. Was thinking downloading pure google rom. Had to read again
That mod.will loki your kernel,prolly why it says unlocked. I.have the.canadian. version..unlocked already thank.god lol.
A.simple wipe can work wonders..if you can get into.recovery and have something.to.flash most times your gona be okay.
Glad your back in.business!
sent from my CleanRom 1.5 i337m
Flash another kernel made for your device, or go thru the ODIN thing, your choice. this is for anyone who have that triangle.
Yes, I read some thread and the roms need kernel, without kernel installed which was has leaded me into that warning att screen. I tried again with roms above link with ktoon kernel and made it through. I was probably be dumb. Pardon me, lots to relearn here.
I own iPhone 4s but I went back to android.
Sent from my SM-T310 using xda app-developers app
You should be able to get rid of that boot screen with the lock on it by using triangle away. http://forum.xda-developers.com/showthread.php?t=1494114
Does anyone know what that com2s and the one below it is? And anyway to delete them?
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
[email protected] said:
Does anyone know what that com2s and the one below it is? And anyway to delete them?
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
delete em (un-install), junk, are you getting spam and such? Did you install those? Do you have any protection on your device? Just curious.
Thank you
TheAxman said:
delete em (un-install), junk, are you getting spam and such? Did you install those? Do you have any protection on your device? Just curious.
Thank you
Click to expand...
Click to collapse
I can't find them to uninstall them just to force stop and unable them. Not getting any spam but I have used 4shared and and downloaded some stuff that didn't work and just download to my storage. No protection for my device. Any suggestions? I haven't had an android since the mytouch on T-Mobile years ago and I'm still new to this.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
I installed the HORSEMAGEDDON ROM and it worked - for the most part. But it kept giving me annoying errors about different apps that were attempting to update every time I turned it on. So I tried to restore my backup that I had made with CWM 6.0.2.8. However the backup apparently did not restore properly because it now boot loops back into CWM any time I try to start it. I get the errors:
E:Can't open cache/recovery/log
E:Can't open cache/recovery/log
E:Can't open cache/recovery/last_log
E:Can't open cache/recovery/last_log
So I tried to reflash HORSEMAGEDDON but it still loops back into the CWM recovery screen.
I have wiped everything according to the instructions on the HORSEMAGEDDON thread.
HELP!! This happened to me on another U8800-51 phone and I wound up hard bricking it trying to get back to stock.
Anybody???
Does anybody have any ideas on how I can fix this?
Did you wipe cache/dalvik cache?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
iheartsamsung said:
Did you wipe cache/dalvik cache?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Yes. I did a wipe of data and factory reset as well.
What I would do is get an SD card with a custom rom on it and try installing it from recovery menu
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Obviously you have been having problems with that rom, so go with something different.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
iheartsamsung said:
Obviously you have been having problems with that rom, so go with something different.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Okay. Here is what I did step by step:
1. I was on Stock 2.2.2 Froyo and flashed HORSEMAGEDDON successfully. But I had some errors related to updates since it was such an old ROM the updates were all for much newer versions of the apps tied to 4.x.x.
2. I attempted to restore my backup made with CWM 6 to return to the stock. It said it completed successfully but when I rebooted it just looped into the recovery screen with the error messages posted in my first post.
3. So I tried to reflash HORSEMAGEDDON and it said it completed successfully. But it still bootloops into recovery.
4. I can access most of the features of the recovery. I can access the pink screen and swap recovery versions. I can access my SD card from my PC when I mount it from recovery.
5. Yes, I did do full wipes with each attempt to reflash.
The ROM was not the problem. It worked and worked well other than update issues for apps. It was only after attempting to restore to stock I ran into issues.
The problem appears to be something was corrupted when I tried to restore my backup, even though it said it completed successfully.
So if I try to flash yet another custom ROM, even if I could find one I trust given all of the version issues etc., I don't think it would act any differently. But if somebody can recommend one I am all ears. Keep in mind I have a -51 phone so it will have to be for that or the PRO.
Given that, how can I get back to stock? Am I the only person who has ever had this problem? I don't believe that is the case, so somebody must know how to fix it or can point me to a procedure to repair the internal memory.
Help!!
I'm new at xda so it's not letting me post an external link. Google "bootlooping" and the first one in list is from xda, just follow the instructions
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Thanks but.....
iheartsamsung said:
I'm new at xda so it's not letting me post an external link. Google "bootlooping" and the first one in list is from xda, just follow the instructions
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
None of the fixes on this link seem to apply to my situation.
When I said "bootloop" I may have misused the term. What happens is I power up, it goes to logo screen for about 10 seconds, shuts down and restarts to logo screen then goes into recovery after about 5 seconds. From other info that I have found it is due to a corrupt bootloader and I need to reflash the bootloader. Problem is, reflashing the bootloader i.e. CWM, does no good at all.
I am also hampered by lack of info specific to the -51 model. And I cannot find a copy of the stock ROM anywhere that is for the -51.
So essentially I am screwed. All of that said, I have found a new phone for $40.00 so all is not lost. It's a U8800 but not the -51 or PRO. I don't plan on customizing it, I'll just stick with stock. After trashing two phones even after following the advice to "BACKUP" I think enough is enough. Backing up did me no good whatsoever in both cases.
In my estimation, the culprit is CWM, or at least the versions I used.
If anybody has any advice I'm all ears.