Database Develop

Keep getting 2.2.1 updates after root. How can this be stopped?

Keep getting 2.2.1 updates after root. How can this be stopped? Its annoying to keep rooting only to get the system updates again and again. I'm rooting with a signed fr91 file. Any way to stop this?
Sent from my Nexus One using XDA App

Upgrade to 2.2.1 frg83 then use the one click super root to root 2.2.1 you won't get the update any more u can find it in nexus wiki
Sent from my Nexus One using XDA App

Download 'Quick Boot' from the market and use it to reboot the phone. Then, clear the update notification from the notification menu. The update message should go away for a while (mine lasted a week before it came back).
I'm still somewhat hesitant to upgrade to FRG83 and use SuperOneClick since some people in the thread are reporting problems. I love my phone how it is right now!

kornball said:
Download 'Quick Boot' from the market and use it to reboot the phone. Then, clear the update notification from the notification menu. The update message should go away for a while (mine lasted a week before it came back).
I'm still somewhat hesitant to upgrade to FRG83 and use SuperOneClick since some people in the thread are reporting problems. I love my phone how it is right now!
Click to expand...
Click to collapse
Do manual rage root ... no problems.

nexusdue said:
Do manual rage root ... no problems.
Click to expand...
Click to collapse
Agreed!
Sent from my Nexus One using XDA App

nexusdue said:
Do manual rage root ... no problems.
Click to expand...
Click to collapse
Are you and Memnoch30 referring to the post you laid out in another thread? I'm pretty sure you wrote detailed instructions on how to do the manual rage root using adb. Will this method work fine if all I want is to run stock 2.2.1 with root-requiring apps like setcpu and move2sd enabler? Sorry for being such a noob

kornball said:
Are you and Memnoch30 referring to the post you laid out in another thread? I'm pretty sure you wrote detailed instructions on how to do the manual rage root using adb. Will this method work fine if all I want is to run stock 2.2.1 with root-requiring apps like setcpu and move2sd enabler? Sorry for being such a noob
Click to expand...
Click to collapse
Yes: Instructions
But read the whole thread to make sure you know what you are doing!!

Any other options? I'm not going to fr83 and unfamiliar with rage root.
Sent from my Nexus One using XDA App

Why don't you install a custom rom and be done with it.

Big_O said:
Any other options? I'm not going to fr83 and unfamiliar with rage root.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
I just installed 2.2.1 and used the SuperOneClick method to root the phone again. I had to turn the phone off, run the program, and then boot the phone for it to work. I suggest you try this method. It couldn't be much simpler.

Now i keep getting the new firmware update message and i cant seem to turn it off even with the quickboot. Any ideas?

Install the update, root again. Now really, this "idea" is 1 message above yours - what made you post?

Hm i tried to update but failed, could be due to tampering of the build number that I did previously but after that it didn't bug me anymore, at least not for now. Will try the superoneclick one next time. Thanks.

It might be back in several days, but if you've tampered with the system and advanced the build number - it shouldn't appear anymore.

yeah i sure hope so. will know in a few days

[Q] Re: Decad3nce's 1.1 ROM

Can't post in the dev forums yet, so I'll post here.
Got Decad3nce's 1.1 update ROM and it installed fine, everything was working. A few minutes later I got a screen that said that there was a problem with authorization and the Nook needs to be reset. It would then reset and roll back to a non-rooted 1.01 version.
I have tried this several times and have had it happen with Decad3nce's first ROM and the v2 ROM. Good thing I have a backup for my nootered 1.01. This one works fine. Anyone have any ideas as to why I am the only one with this problem? Thanks in advance!
I may just have to wait around for an Auto Nooter for 1.1.

sunsurfer42 said:
Can't post in the dev forums yet, so I'll post here.
Got Decad3nce's 1.1 update ROM and it installed fine, everything was working. A few minutes later I got a screen that said that there was a problem with authorization and the Nook needs to be reset. It would then reset and roll back to a non-rooted 1.01 version.
I have tried this several times and have had it happen with Decad3nce's first ROM and the v2 ROM. Good thing I have a backup for my nootered 1.01. This one works fine. Anyone have any ideas as to why I am the only one with this problem? Thanks in advance!
I may just have to wait around for an Auto Nooter for 1.1.
Click to expand...
Click to collapse
Did you reinstall any data, such as using Titanium Backup to restore from a previous install? If so, don't restore System data, ever.

Thank you Decad3nce and dalingrin!
I can't post in the developer thread either but wanted to say thanks to Decad3nce and dalingrin for their excellent contributions.
I used dalingrin's latest 1.1 GHz kernel after applying Decad3nce's v.1.1 "pre-nootered" update and all apps are working with stable operation. Quadrant scores have been averaging between 1100 to 1200.
Thanks to all the other folks in the developer forums who share their experiences. This is a fantastic community.

khaytsus said:
Did you reinstall any data, such as using Titanium Backup to restore from a previous install? If so, don't restore System data, ever.
Click to expand...
Click to collapse
Nope, didn't try and reinstall anything, just applied the 1.1 zip. It happens if I just let my Nook sit or if I start using it. I have TiBu, but just for backing up apps and app data. It's funny how I am the only one with this issue. I might uninstall all my apps and try the update without apps. Then I can reinstall one by one and see if any of them are causing the problem.

I have the same exact issue

samseh said:
I have the same exact issue
Click to expand...
Click to collapse
Sorry to hear this, but glad that I am not alone.

Sorry to hear about your troubles. My upgrade to 1.1.0 from auto-nootered 1.0.1 worked fine.

I had the exact thing happen to me. I had to go back to 1.0.1. I am going to try starting from scratch. I will update my findings after that.

So glad to know that I am not the only one. There is also someone having this problem over on Decad3nce's thread. Thanks in advance to anyone who finds a reason and/or a workaround for this.

My nook was updated Ota to 1.1. Then I don't know how I Reverted to 1.01 afterwhich I applied the pre-nooter to 1.1 againbut only had superuser installed, so I had to install applications directly with the stock browser. Finally installEd titanium backup but still can't use Market or Gmail. No application related to google is allowed to install. This is really weird.

sunsurfer42 said:
Can't post in the dev forums yet, so I'll post here.
Got Decad3nce's 1.1 update ROM and it installed fine, everything was working. A few minutes later I got a screen that said that there was a problem with authorization and the Nook needs to be reset. It would then reset and roll back to a non-rooted 1.01 version.
I have tried this several times and have had it happen with Decad3nce's first ROM and the v2 ROM. Good thing I have a backup for my nootered 1.01. This one works fine. Anyone have any ideas as to why I am the only one with this problem? Thanks in advance!
I may just have to wait around for an Auto Nooter for 1.1.
Click to expand...
Click to collapse
This may be better served in nook color q and a forum.
Sent from my LogicPD Zoom2 using Tapatalk

compuguy1088 said:
This may be better served in nook color q and a forum.
Sent from my LogicPD Zoom2 using Tapatalk
Click to expand...
Click to collapse
There's a NookColor Q and A forums? It would be in the Development forum if I could post there yet. Soon.
Still no luck getting 1.1 to stick.....

Just a quick update... Now everytime I turn on WiFi on my nootered 1.01 it seems to want to update me to 1.1 and breaks my root. Does that just mean that it is trying to push that update? I may need to block OTA updates then. Still trying to get the 1.1 root to work.

Assuming you don't use wifi 'in the wild' you can block 65.204.48.0/24 (65.204.48.0-65.204.48.254) on your router if you have that ability. This seems to block the nooks ability to get updates. This block is in use by B&N for a lot of things.
it will block the wifi's ability to test whether it's connected or not as the internet connectivity test goes to something in this subnet.

[Q] Do I need to unroot for any stock updates?

So, when I got my first Captivate, I got into my epic Android zone with all the ROMs and all that good stuff and managed to mess all that up royally. Well I got my new one and made myself keep it at stock 2.2, but rooted (in case any cool apps came about needing root and CWM wouldn't flash correctly, got a bunch of E: errors so I am assuming that I don't have CWM installed anywhere). So, with this in mind, whenever (or should I say if they ever) they push the OTA update for gingerbread or allow non market apps (preferably both) do I need to be unrooted (meaning will they shut off my device once root is detected on from the OTA or will it just not be pushed because I'm rooted) or will it just push over my current ROM, possible recovery?, etc.?
EDIT: So, does the unroot function of superoneclick work or no?

Anyone care to touch this?
I wouldn't hold my breath waiting for another stock update, just my two cents.
Caution swyping! Read at your own risk.

When I had my rooted D1 I tried the OTA to see what would happen. I received in error saying that it did not work. I don't think it will work with a rooted phone????
Sent from my DROID2 GLOBAL using Tapatalk

No it is easier to flash updates of your favorite rom if rooted. ; )
Sent from my I897 using XDA Premium App

mcord11758 said:
No it is easier to flash updates of your favorite rom if rooted. ; )
Sent from my I897 using XDA Premium App
Click to expand...
Click to collapse
Sorry, but I'm keeping it stock man...

okachowwa said:
Sorry, but I'm keeping it stock man...
Click to expand...
Click to collapse
I know was just being a smuck. I don't think it matters if updating through kies
Sent from my I897 using XDA Premium App

okachowwa said:
Sorry, but I'm keeping it stock man...
Click to expand...
Click to collapse
If you are rooted the OTA will fail, but then OTA from Att always fails. OTA updates are not safe to begin with but that is just my 2 cents

zelendel said:
If you are rooted the OTA will fail, but then OTA from Att always fails. OTA updates are not safe to begin with but that is just my 2 cents
Click to expand...
Click to collapse
But, if it's through kies will it work?

okachowwa said:
But, if it's through kies will it work?
Click to expand...
Click to collapse
To be honest I am not sure. As I only run stock long enough to,find the info to get a custom rom. If I remember right it wipes the device kinda like Odin when flashing so you may be ok.

The first update that came out for captivate, I was rooted and it worked. Worked for many others. Then the update to 2.2 came out and those who were stock rooted lost root. Its just best to be stock with update. Those that had failed updates, the majority used dg's odin package to go back to stock. That's what I remember in the "let's figure this out" thread.

boborone said:
The first update that came out for captivate, I was rooted and it worked. Worked for many others. Then the update to 2.2 came out and those who were stock rooted lost root. Its just best to be stock with update. Those that had failed updates, the majority used dg's odin package to go back to stock. That's what I remember in the "let's figure this out" thread.
Click to expand...
Click to collapse
Does the unroot function from Superoneclick work? Or is there an unroot thing through adb because odin doesn't work with my computer

Use heimdall stock package. No problems that I know of.

boborone said:
Use heimdall stock package. No problems that I know of.
Click to expand...
Click to collapse
I don't want to get back to stock, just unroot...

Money is on you'll just lose root.

okachowwa said:
I don't want to get back to stock, just unroot...
Click to expand...
Click to collapse
Don't know man. I think one click root has an unroot button. Never used it though.

dan_maran said:
Money is on you'll just lose root.
Click to expand...
Click to collapse
i was running 2.2 then used the kies to get 2.3.5 and all my programs were still on my phone but i lost root.

Couldn't Install on USB Storage or SD Card

I don't know why this is happening when trying to install apps..Some install fine but most like this XDA Premium app does not install..Any ideas?
EDIT: Just for giggles i tried installing the free version of xda and it installs but when the paid version is attempted to install i get the could not install message

BrianBaker said:
I don't know why this is happening when trying to install apps..Some install fine but most like this XDA Premium app does not install..Any ideas?
EDIT: Just for giggles i tried installing the free version of xda and it installs but when the paid version is attempted to install i get the could not install message
Click to expand...
Click to collapse
Do you have one of the odex/deodex roms or viperrom installed? thats your issue.

youkosnake said:
Do you have one of the odex/deodex roms or viperrom installed? thats your issue.
Click to expand...
Click to collapse
I think its more to do with the root method but either way im in need of the stock ruu

BrianBaker said:
I think its more to do with the root method but either way im in need of the stock ruu
Click to expand...
Click to collapse
There is no stock RUU released yet. and my One has root and works fine, so I don't think it can be the root method.

youkosnake said:
There is no stock RUU released yet. and my One has root and works fine, so I don't think it can be the root method.
Click to expand...
Click to collapse
well..im screwed since it seems during wiping..Ive lost my nandroid back up..
Anyone happen to have a nandroid with out all user data entered yet? Hell i don't even know if that would work

BrianBaker said:
well..im screwed since it seems during wiping..Ive lost my nandroid back up..
Anyone happen to have a nandroid with out all user data entered yet? Hell i don't even know if that would work
Click to expand...
Click to collapse
I'd say just use one of the roms, sideload apps you use daily and wait it out. nandroiding to a different device is bad news, my friend.

I also am having the same issue with not being able to install to sdcard, you're not alone.

Onyoursix said:
I also am having the same issue with not being able to install to sdcard, you're not alone.
Click to expand...
Click to collapse
Same here. Luckily my TiBackup seems to be installing everything fine, just have to wait out a fix and sideload in the meantime.
Edited... Always read the entire ROM thread before posting... quick fix is listed in there.

I've been having the problem since I installed ViperROM last night. Viper is working on finding a fix. For now, I copied my TiBu files over from my Evo LTE and restored them that way.

Same problem
Running viper

[Q] Help Re-Rooting after OTA Update

hey guys i tried searching for answers. but had no success. i have a note 3 that was rooted with kingo. AT&T automatically installed an OTA update and of course it un rooted my phone. i still get the custom boot screen as well as still have safestrap on my device. my question is how do i reroot my device? ive tried kingo again and it fails after rebootong the phone 5 or 6 times. im still running 4.3 build is JSS15J.N900AUCUBNB4
i know a little on some things but im not as technical as most of you. but any help would be greatly appreciated.

Survivor058 said:
hey guys i tried searching for answers. but had no success. i have a note 3 that was rooted with kingo. AT&T automatically installed an OTA update and of course it un rooted my phone. i still get the custom boot screen as well as still have safestrap on my device. my question is how do i reroot my device? ive tried kingo again and it fails after rebootong the phone 5 or 6 times. im still running 4.3 build is JSS15J.N900AUCUBNB4
i know a little on some things but im not as technical as most of you. but any help would be greatly appreciated.
Click to expand...
Click to collapse
What version of Kingo did you try? Use 1.1.5 or 1.1.8. People have had success with that. 1.1.8 worked for me. Just Google around and you will find the download on the net somewhere.

theorioles33 said:
What version of Kingo did you try? Use 1.1.5 or 1.1.8. People have had success with that. 1.1.8 worked for me. Just Google around and you will find the download on the net somewhere.
Click to expand...
Click to collapse
it was 1.2.0 ill try an older version

In case you have trouble finding a copy
https://mega.co.nz/#!AxdHUCCQ!86DzctSWlXK4VfbInPYBgC_4QYAM2wUR8cewrflAyk0

theorioles33 said:
In case you have trouble finding a copy
unfortunately that did not work. the root failed. that was version 1.1.5, last night i tried 1.1.8 failed and tried the latest 1.2.0 with no success. would you recommend something else? i did try theese root methods with the sd card inserted im not sure if that is a no no or not
Click to expand...
Click to collapse

I'm at a loss. I had my SD card in by the way. Maybe someone else will have some ideas.
Sent from my SAMSUNG-SM-N900A using Tapatalk

theorioles33 said:
I'm at a loss. I had my SD card in by the way. Maybe someone else will have some ideas.
Sent from my SAMSUNG-SM-N900A using Tapatalk
Click to expand...
Click to collapse
that sucks. factory reset? ill most likely still have the issue but maybe not. isnt there a way to completely wipe the phone from the boot screen? id rather not if i dont have to.

You can try a factory reset and then root. If not there is a thread in the general section to go back to stock. Works great. I used it.
Sent from my SAMSUNG-SM-N900A using Tapatalk

theorioles33 said:
You can try a factory reset and then root. If not there is a thread in the general section to go back to stock. Works great. I used it.
Sent from my SAMSUNG-SM-N900A using Tapatalk
Click to expand...
Click to collapse
but arent i technically back to stock? since i dont have root access? this is very confusing to me. if my carrier didnt push that update i wouldnt be in this boat

You are but we can't figure out why you can't root when others in your situation can. There is Kingo thread you can check out. Maybe you can find some answers there.
Sent from my SAMSUNG-SM-N900A using Tapatalk

anyone have any suggestions?? 139 views in less than an hour someone has got to know something lol

Survivor058 said:
anyone have any suggestions?? 139 views in less than an hour someone has got to know something lol
Click to expand...
Click to collapse
Factory Reset after the update to NB4, also go to recovery wipe cache, then try the 1.18, during the rooting process, look your phone screen, you need to click accept something twice,

I don't know how it all works terribly well but you said you still have Safestrap? Can you still install ROMs and can they have root?
Also, for when you eventually do get it working again. I recommend freezing the ATT updater. It can be awful when it eventually FORCES an update.
I got a free app called App Quarantine and froze "AT&T Software Update".

coolmingli said:
Factory Reset after the update to NB4, also go to recovery wipe cache, then try the 1.18, during the rooting process, look your phone screen, you need to click accept something twice,
Click to expand...
Click to collapse
ok yea this is all french to me. you want me to factory reset? im not sure what the NB4 is?. and i thing i know how to wipe the cache.

Gary3 said:
I don't know how it all works terribly well but you said you still have Safestrap? Can you still install ROMs and can they have root?
Also, for when you eventually do get it working again. I recommend freezing the ATT updater. It can be awful when it eventually FORCES an update.
I got a free app called App Quarantine and froze "AT&T Software Update".
Click to expand...
Click to collapse
safestrap is on my phone but it cant be removed and just says that the phone isnt properly rooted. so no i cannot install roms and i will make sure that once i resolve this ill freezr that app
sorry for the delay guys im back at this again. i do very much appreciate all who are trying to offer assistance

ok guys so ive wiped the cache. and have done the factory reset. kingo 1.1.5 and 1.1.8 both have failed...... what is going on here maybe someone can skype with me the steps to completely flash my phone to the day i got it i see the thread but im scared ****less to try it lol

You will just have to follow the restore to MJ5 thread. The instructions are simple and very easy to follow. Go slow and follow them to the T.
What they do not mention however is do not use a 3.0 USB port. Only 2.0 will work.
Just follow that.
It is literally impossible to brick this phone to the point of it being unrecoverable. There is a tutorial to restore from hard bricks without J-Tag.
Sent from my SM-N9005A using XDA Premium 4 mobile app

graydiggy said:
You will just have to follow the restore to MJ5 thread. The instructions are simple and very easy to follow. Go slow and follow them to the T.
What they do not mention however is do not use a 3.0 USB port. Only 2.0 will work.
Just follow that.
It is literally impossible to brick this phone to the point of it being unrecoverable. There is a tutorial to restore from hard bricks without J-Tag.
Sent from my SM-N9005A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hey graydiggy, I did the restore back to MJ5, but can't seem to get the last step for rooting to work. I tried every way with putting the rdlv on internal...unzipped and zipped. I even tried doing the same on the external sd as well. When I reboot supersu doesn't do anything. Any suggestion on how to get the last step to work?
Thanks in advance for your help.

chrispyutec said:
Hey graydiggy, I did the restore back to MJ5, but can't seem to get the last step for rooting to work. I tried every way with putting the rdlv on internal...unzipped and zipped. I even tried doing the same on the external sd as well. When I reboot supersu doesn't do anything. Any suggestion on how to get the last step to work?
Thanks in advance for your help.
Click to expand...
Click to collapse
It has to be unzipped and on the internal. You have to reboot a few times for it to activate. After the first reboot, let the phone sit for a few minutes and then reboot again. You should be good to go after that.
Sent from my SM-N9005A using XDA Premium 4 mobile app

graydiggy said:
It has to be unzipped and on the internal. You have to reboot a few times for it to activate. After the first reboot, let the phone sit for a few minutes and then reboot again. You should be good to go after that.
Sent from my SM-N9005A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Wow that did the trick!!! Thanks for holding my hand lol. I hit your thanks and I appreciate your help.