Database Users

Update to 2.3.6 and keep root

If you haven't already done so, install Rom Manager and flash Clockworkmod Recovery. It doesn't replace the actual recovery partition or the files that restore it so it won't affect flashing the update.
If you received an OTA notice don't flash it. You can go into /system/cache and copy it, or download it from the links in other threads. Place the update zip (no need to rename it) on the root of your sd card.
To install the update you must be fully stock (root is okay). That means any changed or deleted system files (including bootanimation.zip) will prevent the update from flashing. You will get a status 7 error. If you used Bloat Freezer you must defrost all before flashing the zip or it will error.
Also, have available whatever zip you used to root your Nexus one (i.e., su.zip or superboot, etc.) and put on the root of your sd card.
Once your system is back to stock reboot into CWM recovery and select flash zip from sd card. Then flash the 2.3.6 update file. Then DO NOT reboot yet. Now flash your root zip. After you have flashed both the udpate and the root zip you can reboot your phone. No need to wipe anything.
When your phone reboots you will have 2.3.6 and it will still be rooted. No bootloader gymnastics necessary.

I am using stock (almost) version of GRJ22 , but unfortunatelly I got the status 7 error when I tried to apply the update via clockworkmod recovery. I guess that's because I have already integrated some system apps into ROM using Titanium Backup.
So, if I flash stock vanilla GRJ22, then SU, then GRK39F (the incremental update) and finally SU again, won't that do the job??
Thanks..

Nikos_s3 said:
I am using stock (almost) version of GRJ22 , but unfortunatelly I got the status 7 error when I tried to apply the update via clockworkmod recovery. I guess that's because I have already integrated some system apps into ROM using Titanium Backup.
So, if I flash stock vanilla GRJ22, then SU, then GRK39F (the incremental update) and finally SU again, won't that do the job??
Thanks..
Click to expand...
Click to collapse
Yes, that will do nicely. Just need to get back to GRJ22 stock before you can flash the udpate. The updater-script does an assert and checks the md5 checksum of every system file before it allows the update to flash. If it doesn't find all stock files or checksums don't match what it is looking for, you get a status 7 error and the line above will show which file it stopped on. So you can look at those messages and keep restoring files it wants (if only a few) without having to flash completely back to stock.

I guess that would take much time, as almost all of my google apps are integrated into ROM...so I will try to follow the procedure I wrote earlier and if that won't work, I will try a ready stock,rooted ROM (Fireb33 has done it already)..
thanks mate..

Why so complicated?
You can update to 2.3.6 AND keep root even much more simple:
1.) Update from OTA to 2.3.6 (and loose root).
2.) Flash Superboot from Madaco and get back root.
Done in 3 minutes.. No need to flash, recover, overwrite and/or whatever, no need for ADB, no messing:
Code:
https://bexton.net/2011/09/24/root-access-for-nexus-one-on-android-2-3-6-grk39f-superboot/

Bexton said:
You can update to 2.3.6 AND keep root even much more simple:
1.) Update from OTA to 2.3.6 (and loose root).
2.) Flash Superboot from Madaco and get back root.
Done in 3 minutes.. No need to flash, recover, overwrite and/or whatever, no need for ADB, no messing:
Code:
https://bexton.net/2011/09/24/root-access-for-nexus-one-on-android-2-3-6-grk39f-superboot/
Click to expand...
Click to collapse
That's only for those who have the bootloader unlocked?

_raz_ said:
That's only for those who have the bootloader unlocked?
Click to expand...
Click to collapse
Well, yep. That method indicates your (phones) bootloader is unlocked. But as it's the N1, unlocking the bootloader is just 19 (up to 25) characters away -> "fastboot(-linux) oem unlock".
Edit: By the way, i looked up that post from an android platform engineer:
Code:
groups.google.com/group/android-platform/msg/b7d83992dd92accb?dmode=source
The N1 is just made for that.

tried superboot but wifi down
I flashed the update for 2.3.6 and then superboot but my wifi gives an error when I try to turn it on.

New Superboot file for GRK39F?
Is there a new Superboot file for the new OTA update?

jboxer said:
If you haven't already done so, install Rom Manager and flash Clockworkmod Recovery. It doesn't replace the actual recovery partition or the files that restore it so it won't affect flashing the update.
If you received an OTA notice don't flash it. You can go into /system/cache and copy it, or download it from the links in other threads. Place the update zip (no need to rename it) on the root of your sd card.
To install the update you must be fully stock (root is okay). That means any changed or deleted system files (including bootanimation.zip) will prevent the update from flashing. You will get a status 7 error. If you used Bloat Freezer you must defrost all before flashing the zip or it will error.
Also, have available whatever zip you used to root your Nexus one (i.e., su.zip or superboot, etc.) and put on the root of your sd card.
Once your system is back to stock reboot into CWM recovery and select flash zip from sd card. Then flash the 2.3.6 update file. Then DO NOT reboot yet. Now flash your root zip. After you have flashed both the udpate and the root zip you can reboot your phone. No need to wipe anything.
When your phone reboots you will have 2.3.6 and it will still be rooted. No bootloader gymnastics necessary.
Click to expand...
Click to collapse
I want to update to gingerbread and looking for the proper guidance going forward. I've done some looking around the forums but i'm still unclear if i need to unroot or install a stock build, etc. What i know is the phone is rooted and sim unlocked. How can i check to see if the bootloader is open/locked?
Current specs:
android version 2.2.1
Baseband 32.41.00.32U_5.08.00.04
Kernal Version 2.6.35.9-cyanogenmod
Mod Version: Cyanogenmod-6.1.1-N1
Build: FRG83D
edit:
Please treat me like an idiot and walk me through this process. It's be utterly frustrating and I'm a stone's throw away from busting out my Nokia 3390 (equipped with led disco keypad).

If your bootloader is unlocked you will see an unlocked padlock on the boot up screen...

go back to honeycomb from ics?

Ever since i've updated to ics my wifi has been terrible if I'm not in the same room as my router I get 1 bar so I wanna go back to honeycomb. I have civato's latest rom for ics idk if that matters or not and I know it's the ics that's messing up my tab because my brother has the same tab but he hasnt downloaded any updates and his wifi is fine.

rcraig617 said:
Ever since i've updated to ics my wifi has been terrible if I'm not in the same room as my router I get 1 bar so I wanna go back to honeycomb. I have civato's latest rom for ics idk if that matters or not and I know it's the ics that's messing up my tab because my brother has the same tab but he hasnt downloaded any updates and his wifi is fine.
Click to expand...
Click to collapse
3.2.1 rooted roms with the stock Acer kernel:
These will work with the new unlocked ics recovery
* Wipe your tab (you can use titanium if you need to backup app data) in recovery
* flash the rooted stock rom in recovery
* reboot
(I've tested this with my HC3.2.1 rom here: http://forum.xda-developers.com/showthread.php?t=1265847)
other HC roms with custom kernels (non-acer) or older kernels
Here you need the old HC3.0.1 bootloader/recovery before you can install, and will need to re-install the unlocked bootloader if you return to an ics rom.
http://forum.xda-developers.com/showthread.php?t=1622425
Has instructions for returning to the HC bootloader/recovery as well as going to the unlocked ics ones
Then just wipe and install as normal.
**note when downgrading system apps between android releases you must factory reset.. most of our recoveries leave the sdcard data intact (of course you ought to take a full nandroid backup of your current rom so if it doesn't work you can re-install the ics bootloader if needed and restore your current system)

COS 13.1 ZNH2KAS1KN - New Update for OPO

Cyanogen recently pused out COS13.1 for our beloved OPO.
Here is the link to OTA :-
http://builds.cyngn.com/incremental/bacon/cm-bacon-64003595ee-to-ced5430fc0-signed.zip 378 MB
"Upgrade your device to Cyanogen OS 13.1. Based on Android™ 6.0.1, Marshmallow, this update provides critical security fixes, improved stability/performance, product upgrades, and new mods for Cortana, OneNote, Microsoft Hyperlapse, Skype, and Twitter."
Changelog :-
Complete changelog currently unknown.
1st June Android Security patch level
Some MOD Addons.
Skype integration in dialer.Removal of NextDialer. Looks like stock dialer.
Hyperlapse mod in camera.
Update Instruction :-
Stock Unrooted Devices
To flash OTA you need stock unrooted phone.
Flash via stock recovery.
Rooted devices
1st unroot the device or flash system image from previous update then flash the OTA from recovery.

Hi, i've a problem flashing the OTA update...
TWRP locks the update giving me the error7
I've completly unrooted with SuperSU settings.
Thanks a lot.

gigatroned said:
Hi, i've a problem flashing the OTA update...
TWRP locks the update giving me the error7
I've completly unrooted with SuperSU settings.
Thanks a lot.
Click to expand...
Click to collapse
try flashing from stock recovery !

gauravsaini964 said:
try flashing from stock recovery !
Click to expand...
Click to collapse
Same for me lol

gigatroned said:
Hi, i've a problem flashing the OTA update...
TWRP locks the update giving me the error7
I've completly unrooted with SuperSU settings.
Thanks a lot.
Click to expand...
Click to collapse
flash the stock system with the correct recovery over, then flash update

stock recovery here. in the middle of the update it gives me an error.
All the page with red fonts, after a few second the message disappear and I have not been fast enough to read.
after reboot everything it is normal, but still COS 13.0

dam76 said:
stock recovery here. in the middle of the update it gives me an error.
All the page with red fonts, after a few second the message disappear and I have not been fast enough to read.
after reboot everything it is normal, but still COS 13.0
Click to expand...
Click to collapse
Try to install the previous update, and then with recovery stock reinstall the last update.

alijoregon said:
Try to install the previous update, and then with recovery stock reinstall the last update.
Click to expand...
Click to collapse
thanks, I tried installing previous update (same file cm-bacon-64003595ee-to-ced5430fc0-signed.zip that gave me Marshmallow in the first place)
but it gave me the same error again!
This time I took a screenshot with an old phone:
http://i.imgur.com/sW5NTyb.jpg

dam76 said:
thanks, I tried installing previous update (same file cm-bacon-64003595ee-to-ced5430fc0-signed.zip that gave me Marshmallow in the first place)
but it gave me the same error again!
This time I took a screenshot with an old phone:
http://i.imgur.com/sW5NTyb.jpg
Click to expand...
Click to collapse
Is your previous update the full OTA? The incremental is not valid. If you did root any time your system is modified. You must reinstall the full zip.

alijoregon said:
Is your previous update the full OTA? The incremental is not valid. If you did root any time your system is modified. You must reinstall the full zip.
Click to expand...
Click to collapse
yes: my system was rooted, so I had to perform a full wipe and install what I think to be the full zip (cm-bacon-64003595ee-to-ced5430fc0-signed.zip 377MB)
where can I download the full zip just to make sure?
does the full zip update wipe apps and data?
thanks in advance for the help

dam76 said:
yes: my system was rooted, so I had to perform a full wipe and install what I think to be the full zip (cm-bacon-64003595ee-to-ced5430fc0-signed.zip 377MB)
where can I download the full zip just to make sure
thanks in advance for the help
Click to expand...
Click to collapse
This time you needn't do full wipe. Only installing the full OTA via TWRP and then you must come back to the original recovery and install the incremental update. By this way you will have the last update.
All the links are in a post on this web, I don't remember the name of the post, but is easy to find.

alijoregon said:
This time you needn't do full wipe. Only installing the full OTA via TWRP and then you must come back to the original recovery and install the incremental update. By this way you will have the last update.
All the links are in a post on this web, I don't remember the name of the post, but is easy to find.
Click to expand...
Click to collapse
thanks! here I found the CM13.0 Signed flashable zip
cm-13.0-ZNH0EAS2JK-bacon-signed.zip 691 MB
rebooting
applying full zip via stock recovery
rebooting - everything apparently the same
applying update via stock recovery
rebooting... optimizing apps...
success! COS 13.1 up and running! (phone very warm though)
thank you very much for the support. (why messing with android must be so complicated?)

Hi, i also have an ERROR while installing the OTA.
1. I had updated to CM13 via OTA.
2. Since I had an issue with stuck lockscreen , installed TWRP and wiped cache ( Stock CM recovery was not helping). Phone worked great since then.
3. TWRP was not longer there, instead CM Recovery.
4. New update has arrived, but i get an "ERROR" word in the middle of screen while installing.
What can I do?
Thank you in advance for your response.

Seems to be fine. Minimal fixes but at least something...
---------- Post added at 11:29 AM ---------- Previous post was at 11:28 AM ----------
leokook said:
Hi, i also have an ERROR while installing the OTA.
1. I had updated to CM13 via OTA.
2. Since I had an issue with stuck lockscreen , installed TWRP and wiped cache ( Stock CM recovery was not helping). Phone worked great since then.
3. TWRP was not longer there, instead CM Recovery.
4. New update has arrived, but i get an "ERROR" word in the middle of screen while installing.
What can I do?
Thank you in advance for your response.
Click to expand...
Click to collapse
thanks! here I found the CM13.0 Signed flashable zip
cm-13.0-ZNH0EAS2JK-bacon-signed.zip 691 MB
rebooting
applying full zip via stock recovery
rebooting - everything apparently the same
applying update via stock recovery
rebooting... optimizing apps...
success! COS 13.1 up and running! (phone very warm though)
thank you very much for the support. (why messing with android must be so complicated?)
USER ABOVE YOU POSTED HOW HE DID IT. FOLLOW HIS GUIDE AND THANK HIM

anyone have problem with titanium backup on latest ota s1kn ? i cannot freeze and restore app , any idea ? su version 2.65

Are there also any changes with the camera?

prototyp01 said:
Are there also any changes with the camera?
Click to expand...
Click to collapse
Hyperlapse got added !

Is overall camera quality better than before? Or is Hyperlaps the only change?

prototyp01 said:
Is overall camera quality better than before? Or is Hyperlaps the only change?
Click to expand...
Click to collapse
I am sure some one else will be able to answer this better
I haven't flashed this update yet neither I am camera enthusiast.

Updated on this one yesterday, and I regret it....my phone now charges very slow, it took 8 hours to fully charge, dont have this issue before, tried everybody else fixes, but did nothing...do anybody has the flashable ZIP on the previous version and can be flashed using stock recovery?
Thanks

4.5.1 Update with Root and Recovery

Trying to update the 4.5.1 and it seemed to have gone fine until it automatically reboots into TWRP recovery. Upon rebooting into system, it states the update failed. With TWRP having all those jumbled folder names right now (has this been fixed yet?) it's hard to see if the update downloaded somewhere to internal storage, and further if it could be flashed even if I found it. Is updating with an OTA like this possible? I know on basically all other phone it is not. Has anyone gotten the update to work while being unlocked, rooted, with TWRP? Thanks.

xgerryx said:
Trying to update the 4.5.1 and it seemed to have gone fine until it automatically reboots into TWRP recovery. Upon rebooting into system, it states the update failed. With TWRP having all those jumbled folder names right now (has this been fixed yet?) it's hard to see if the update downloaded somewhere to internal storage, and further if it could be flashed even if I found it. Is updating with an OTA like this possible? I know on basically all other phone it is not. Has anyone gotten the update to work while being unlocked, rooted, with TWRP? Thanks.
Click to expand...
Click to collapse
Generally you need to reflash the previous Full ROM with TWRP and then flash the OTA on top for it to work as the system must be unmodified. Alternatively, you can just flash the latest Full ROM. Currently those are not available, but that's generally how it works.

If u have installed twrp before updating the stock rom, I guess we have to wait for full rom of latest update 4.5.1 which can be flashed via twrp.
P.s. FLASHING the dwnloaded update via twrp will gives u error.. So have to wait for full rom. ?

Revert to stock failed and cannot install custom rom as well.

I was running the June patch version of the TWRP flashable stock builds (had hard bricked my phone before so cannot use full stock firmware until and unless I get my hands on the stock Oreo firmware).
As the official Oreo update is out, (https://drive.google.com/file/d/1Zmt...IeF9vauAY/view) I downloaded the zip file and placed it in my internal storage and tried to apply the update, which took me to TWRP, and the update failed. I rebooted to see if everything was ok and it was.
Then, I tried to revert to the stock firmware of the latest edition (to see if I could apply the update) and each time I tried to run the commands or run the flash file, it failed because I was not able to flash the stock recovery. It showed 'N/A' instead of 'bad key' every time on the screen before booting into TWRP.
I gave up and tried to go back to the TWRP build I was using before, and I get this error on TWRP. Why is this happening? (I had formatted my data after entering TWRP, is this th reason?)
Please help guys! Need to get my phone back and running!
Here is an image of what's going on -