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...

Stock N4 4.2.2 build.prop

Could somebody please send me the /system/build.prop from a stock 4.2.2 Nexus 4?
I can't install the 4.3 OTA zip unless my build.prop passes the integrity check that is built into the OTA...I modified mine to enable LTE with an LTE-enabling script that didn't make a backup. It's not clear what needs to be changed back and I'm pretty sure it needs to be exactly default for it to pass the check (i.e. spaces, order of the parameters, etc...needs to precisely as it was before...)
It would be much appreciated if somebody could please upload the build.prop somewhere.

I've attached the backup of my JDQ39 build.prop file in a zip to this post. I was able to flash the 4.3 OTA update using this build.prop so it should be fine.

For anyone else in the same boat (OTA failing because build.prop not passing check in install), the above build.prop worked for me. I don't have root and I'm still 1/2 n00b so I pushed it into /system/build.prop using the nexus toolkit and it's insecure boot image (choice 13). Then I rebooted into recovery and followed the normal instructions for using ADB sideload to install the OTA (section A here: http://forum.xda-developers.com/showthread.php?t=2145848)

[Q] Help! Just broke my services.odex and cant get into my phone.

I was trying to unlock my wifi tether by editing services.jar. I renamed both services.jar and services.odex by adding ".bak" I replaced services.jar with the recompiled one but didn't replace services.odex. now when my phone boots up I get "unfortunately verizon login has stopped" as well as a few others and I can't get in. What can I do to fix this? Its a verizon S5 with the march 31 kernel version.

Restore your backup. Or you could replace just the files you renamed with an ADB shell session and push the required files. Or "dirty' flash just the system files. Or write a full, stock firmware image with Odin.
Those would be some of the ways to recover. Lots of existing threads on this, with further elaboration if you need further guidance.
.

fffft said:
Restore your backup. Or you could replace just the files you renamed with an ADB shell session and push the required files. Or "dirty' flash just the system files. Or write a full, stock firmware image with Odin.
Those would be some of the ways to recover. Lots of existing threads on this, with further elaboration if you need further guidance.
.
Click to expand...
Click to collapse
I don't have a backup or custom recovery, I just used towelroot and thought it would be pretty safe to unlock the wifi tether. I think I forgot to turn on USB debuging so I think ADB is out of the question. Is there a way to "dirty flash" with Odin?
Edit: just did a reset with Odin, this fixed the problem. The phone was new so there wasn't much on it and I do keep my contacts and messages backed up so not much is lost except for the inconvenience of setting everything back up. I will definitely be more careful in the future.

Best current method to root S5 on Lollipop with Knox 0x0 / Help needed.

Hello everyone
I just bought a new Samsung Galaxy S5 international (SM-G900F) and I am about to root it in order to be able to install a sound mod which boosts the sound. I was considering using the one from this thread: http://forum.xda-developers.com/showthread.php?t=2729652
Basically, it will modify the sound setting values found in mixer_path.xml file in /system/etc
How it is going to be done: (Help needed here)
Plan A- I am planning to downgrade to KitKat in order to root without triggering the Knox counter, then install the mod, then upgrade to LolliPop again.
Plan B- Alternatively, I can downgrade to KitKat and root, then install a prerooted lollipop rom (not sure if it will trigger the Knox counter), then install the sound mod.
Plan C- Maybe there is a method you can tell me about to access the system files of the phone from ADB on my pc without rooting and just modify the values found in mixer_path.xml file in /system/etc
Plan D- A less probable way would be to download an original Lollipop Rom, modify the mixer_path.xml file in /system/etc, save it and then flash it to the phone as an official Rom using Kies 3. I don't even know if this is possible.
Whichever method I choose to go with, I intend to unroot once the Mod is installed in order to get OTA updates. (Not sure how to do this)
My questions:
If I upgrade from KitKat to LolliPop, will it write a new mixer_path.xml file with the default values? Or will it keep the modified version of the file?
If I install the Mod on Lollipop, will an update (OTA) write a new mixer_path.xml file with the default values? Or will it keep the modified one?
Also, once my phone is rooted, I believe OTA updates will not work, so how do I manage to get back the OTA updates from Samsung without losing the modified version of mixer_path.xml file in /system/etc? I don't mind losing root access once I have my sound mod installed.
Thank you very much for your answers, and feel free to tell me what is the best plan or point me toward a better method to achieve this, or anything else that I might not know regarding rooting the S5 without triggering the Knox counter.
Have a great day

Plan A- it will be rewritten when you flash the new ROM (system partition), so you would lose the mod.
Plan B- to flash a pre rooted you will need a custom recovery, and flashing a custom recovery will trigger the knox.
Plan C- I'm not totally sure, but I guess you will need root the same way as it's going to make changes in system partition
Plan D- I'm not sure if it's possible
Enviado de meu Nexus 5 usando Tapatalk

There's always plan E......
Downgrade to KitKat, Towelroot it, use Chainfire's Flashfire to flash Lollipop with injected root, and apply the sound mod then.......(I assume the sound mod is compatible with Lollipop?)....
Sent from my rooted, debloated stocKK kn0x0 SM-G900F

Thank you luisaosan and keithross39 for the helpful answers
As suggested by Luisaosan, Plan A will not work because the file will be overwritten after the update.
Plan C will not work, I tried ADB and all I could do was to pull the files to my computer and edit them, but I couldn't push them back to the phone because the system is in Read-Only and I would need root acces to push a file using ADB.
Plan D is only partly answered following some research I did, basically the rom needs to be signed in order for Kies to accept flashing it, I don't think it's possible to sign it for Kies but it can possibly be signed to be flashed by Odin, although I don't know how to do this and I have no idea if it will trigger the knox, so let's discard this idea for now.
I guess I will have to go with Plan E as suggested by keithross39 (which is same as Plan B, lol). I will give it an evening to backup everything before flashing KitKat and following the process suggested in this method. What is sad is that there isn't a step by step guide to go through this method, and this makes me a bit scared of doing something wrong and end up triggering the Knox counter. I will do some more readings before starting this.
Btw, the only interesting guide that I found so far has this title:
Guide: Rooted Android 5.0 for the International Galaxy S5 (SM-G900F) while preserving Knox 0x0
You can easily find it if you google this title.
Also, for the Mod I was trying to do, it's just an *.xml file that I want to open in a text editor and modify few values in order to increase the volume output of my S5, so yes, it is compatible with Lollipop
Thank you again for answering my questions, and feel free to post anything you judge useful
Wish you all a great day

Question regarding stock boot image of note 3 SM-N9005

Hi, i want to install Magisk via magisk manager to root my note 3 and hide the root access from certain apps, but before this i need to dump stock boot image before install magisk. I can't find any way to backup the stock boot image from my phone without root the phone first. So i am thinking whether the boot.img inside firmware file as show in below sammobile link is the exactly same stock boot image in my phone? If it is the same file then i no need manually backup the stock boot image from my phone. I had used the phone for few years and i just worry that it will become boot-loop or bricked after i install magisk. Thank you.
www/sammobile/com.firmwares.galaxy-note3.SM-N9005.XME.download.N9005DXSGBQA1.123876 (Just change the "/" to "." while "." to "/" because i can't directly post the link due to forum restriction of new user)

Bootloaders are in the Bootloader and Modem threads .