Database Users

Gearing up for some Gingerbread cookies...

saw some articles about this but they weren't this specific...
so I have a Nexus One 2.2.1 stock, rooted with rageagainstthecage thing...
will my phone update to 2.3 as-is, or will I have to unroot the rageagainstthecage method first?
from 2.2 to 2.2.1 I had to uninstall Universal Androot (useless anyways) and reinstall some missing APKs that I had deleted (Amazon MP3 and GenieWidget)

Don't quote me on that, but I'm pretty sure that you will not get OTA automatically. However, as soon as it's out, it will be posted here and you can flash it manually. You will loose root though.

thanks, I hope you're right. Losing root is no biggie (hopefully a nice easy root method will come up shortly)

If anything it will be here before you get the OTA anyway.
Atleast that's what happened with Froyo.
Someone will logcat the address then DL it, then it will get mirrored all over XDA

Once it's here on XDA the flashing will begin long before the OTA arrives

question
I had CM6.1 Nightlies on my N1 with Clockwork, now I went back to stock recovery, stock FRG83 and I have my bootloader unlocked.
I'm wondering if the OTA will come automaticaly (probably gonna install the "XDA" version before OTA even starts going around)?
And I'm wondering if anybody knows what is supposed to be the criteria for the OTA to come automaticaly?

I was rooted with 2.2 and got the OTA for 2.2.1.
As far as I know you need a stock rom (rooted or otherwise) with a locked bootloader.
Sent from my Nexus One using XDA App

are you certain about the locked bootloader?

Its kinda pointless to go back to stock and such if you like the CM nightlies, its what I run, because the first phones to receive the OTA will be the "Holiday" Nexus one, based on imei. It will be up on xda with many mirorrs and versions shortly after! If you remener froyo it will be like that. So just look here for the update.zip
Just my two cents
Sent from my Nexus One using XDA App

Yeah I know I was just wondering about the update process, requirements, etc.
I love CM6.1, I'll probably go back to it when I'm fed up with Ginger there was another reason to go back to stock and that's that I still had ere27 stock backup and it was time to update the stock ROM to frg83 and back that up for the future

It doesn't matter if you have an unlocked bootloader or not, nor does it matter if you have rooted. You must have a stock recovery as the ota will use it to install, if it doesn't find it the installation will fail. Previous updates were available here for rooted users before the update went ota

i also was rooted but had a stock bootloader and recovery... got the 2.2.1 OTA. lost root though.
now for my question... i dont care if i lose root for gingerbread but since i rooted.. SU is in my rom and i cant delete it. i just dont want something on my phone that i cant use.
will the gingerbread update bring me to full stock gingerbread? or would SU be still stuck there. just asking since i rooted after i got froyo so im not sure.

If memory serves, with an OTA su will be removed, but Superuser.apk will remain.
Anyways, if you try this app, you should be able to regain root with ease, even if it's only to bin the files you don't want.

Rusty! said:
If memory serves, with an OTA su will be removed, but Superuser.apk will remain.
Anyways, if you try this app, you should be able to regain root with ease, even if it's only to bin the files you don't want.
Click to expand...
Click to collapse
yeah i got root back because of that app! my main grip was superuser.apk was still in the phone without SU access. now im back to rooted i just left it there.
so basically if i get gingerbread and lose root superuser.apk will still be left in the phone? any thoughts? if so ill just delete it then install it back somewhere i could delete it if i lose root again.

I believe so, yes.
Bin it before updating to be 'safe', I guess.

Rusty! said:
I believe so, yes.
Bin it before updating to be 'safe', I guess.
Click to expand...
Click to collapse
is there an easy way to do it... say just delete it via astro file manager? this is the tutorial i used to root in the first place..
http://forum.xda-developers.com/showthread.php?t=736271
.. lost root then i used the "one click root" that first appeared in the market, then lost root again after 2.2.1 then used visionary.
theres a lot more in the phone that was put in there by rooting (like busybox right?)... but i guess superuser.apk is the visible one since it shows on the app drawer so i wanna remove it from the phone and just install it via the market.

ASTRO can't do it as far as I'm aware, but it's easy from ADB shell or a terminal:
Code:
su
mount -o remount,rw /dev/mtdblock3 /system
rm /system/bin/su
rm /system/app/Superuser.apk
rm /system/bin/busybox
and it's goodbye root (and busybox since you mentioned it).

Rusty! said:
ASTRO can't do it as far as I'm aware, but it's easy from ADB shell or a terminal:
Code:
su
mount -o remount,rw /dev/mtdblock3 /system
rm /system/bin/su
rm /system/app/Superuser.apk
rm /system/bin/busybox
and it's goodbye root (and busybox since you mentioned it).
Click to expand...
Click to collapse
thanks will give it some thought

krabman said:
It doesn't matter if you have an unlocked bootloader or not, nor does it matter if you have rooted. You must have a stock recovery as the ota will use it to install, if it doesn't find it the installation will fail. Previous updates were available here for rooted users before the update went ota
Click to expand...
Click to collapse
I think that the latest Amon RA will flash an update, regardless of signature verification.

GldRush98 said:
I think that the latest Amon RA will flash an update, regardless of signature verification.
Click to expand...
Click to collapse
You're right, same as the latest ClockworkMod recovery...they disable signature check

[Q] Is Superuser.apk necessary for Flashing a custom ROM?

Hi,
I'm trying to root my TF and flash a custom rom.I've rooted and flashed a different rom for my moto phone before,but root+recovery for TF seems a bit more complex for me...
I'm gonna do that according to this thread:
[GUIDE] STOCK (8.2.3.9/8.2.3.13/8.4.4.5) to 3.1 (PRIME! v1.4) + Overclock!
However,I noticed that this tutorial skiped the steps below:
Code:
adb remount
adb push su /system/xbin
adb shell chmod 6755 /system/xbin/su
adb push Superuser.apk /system/app/
Which are shown in:
[UPDATED][Video] How To Root Transformer & Downgrade Honeycomb 3.1
Does it mean it's unnecessary to do the steps above if i'm going to flash a custom rom?If so,will the apps that require root work well on the flashed custom rom?(e.g. Using Root Explorer to modify system files)
Thanks in advance.

I'm confused on what you're asking. Why would you not want Superuser.apk is there a specific reason why you don't want it?
And you don't need to use that GUIDE anymore, its outdated. Use NVFlash. It's a one-step process to become rooted and use PRIME 1.4

zephiK said:
I'm confused on what you're asking. Why would you not want Superuser.apk is there a specific reason why you don't wan tit?
And you don't need to use that GUIDE anymore, its outdated. Use NVFlash. It's a one-step process to become rooted and use PRIME 1.4
Click to expand...
Click to collapse
Thanks.
I searched for "NVFlash",and found this article Nvflash on ASUS Transformer
Does it work for MoDaCo Hr7?

botzl said:
Thanks.
I searched for "NVFlash",and found this article Nvflash on ASUS Transformer
Does it work for MoDaCo Hr7?
Click to expand...
Click to collapse
It should work for all ROMs. Just use the instructions provided on that website. When you're done with those steps, you'll be rooted + on PRIME 1.4. If you wish to change ROMs, then just boot into Clockwork Recovery (already preinstalled!, steps to go into it: shut tablet off, vol down + pwr up) and wipe data/factory/dalvik flash the .zip.
And you're done! It's easy just like that. Much easier than downgrading to 3.0.0 then rooting and doing it yourself.
Edit: http://forum.xda-developers.com/showthread.php?t=1123429 is the thread on XDA for NVFlash. There is a video included in there so it'll help resolve any problems you might face. Although, you shouldn't really, its very straight forward.

Thanks again!
I'm watching that video right now...

Failed root with Signed CWM package

I tried rooting with the signed CWM package from the SGS2 forum, however, it failed, busybox and su are in system/xbin but if I try root apps no go.
The reason I opened this thread is to give some info I found;
When I try run su, nothing, if I try run busybox su I get an error that user root is not found. All I can thing is that Samsung have removed the root user from this build to make life more difficult.
I don't want to flash a CF-Root kernel or other insecure kernel and so I'm going to aim towards a clean root method like the one I have for SGS2 using the signed CWM that can be booted from official recovery (see my other thread about that; http://forum.xda-developers.com/showthread.php?t=1647177).

Turns out, the prerooted rom here was broken but i got official from checkfus. Then i found the thead with modified cwm files for note and rooted fine. I found out later that LPY suffers from the same brick bug so went back to GB.
Anyway, dont flash LPY it suffers same brick bugs.
Mods, please close/delete this thread.
Sent from my GT-N7000 using Tapatalk 2

[Q] Wont root after manual update?

I just pushed the new 4.2 update via adb,
I then tried re-rooting as I lost root in the project.
I used WugFreshs at first, which said successful. I tried root check and titanium backup which both said no root access.
I then tried mikes toolkit and chose root and install busybox, all that wen through great and said successful, so I retried Tibackup and rootchecker again, both were denied root access.
This time round, rootcheck said "System Running Slow" whilst checking for root access.
What should I do?
Re-boot into recovery and clear cache etc?
Factory reset?
Both?
For some reason superuser is installed not supersu if that makes a difference?
Any help appreciated.

Wilks3y said:
I just pushed the new 4.2 update via adb,
I then tried re-rooting as I lost root in the project.
I used WugFreshs at first, which said successful. I tried root check and titanium backup which both said no root access.
I then tried mikes toolkit and chose root and install busybox, all that wen through great and said successful, so I retried Tibackup and rootchecker again, both were denied root access.
This time round, rootcheck said "System Running Slow" whilst checking for root access.
What should I do?
Re-boot into recovery and clear cache etc?
Factory reset?
Both?
For some reason superuser is installed not supersu if that makes a difference?
Any help appreciated.
Click to expand...
Click to collapse
I apply the update by doing fresh install:
-always backup your data
Then I use wug's nexus root toolkit:
-flash stock + unroot 4.1.2 jzo54k
-flash zip stock + unroot 4.2 jop40c
-change the model type to "NAKASI: Android *.*.* Any build"
-apply root

gesitkumara said:
I apply the update by doing fresh install:
-always backup your data
Then I use wug's nexus root toolkit:
-flash stock + unroot 4.1.2 jzo54k
-flash zip stock + unroot 4.2 jop40c
-change the model type to "NAKASI: Android *.*.* Any build"
-apply root
Click to expand...
Click to collapse
I applied the update over the top of 4.1.2, wiped cache and then restarted.
I then used Wug's toolkit to root, which didn't work.
So I tried Mikes, which also didnt work.
Both report the Root as being succesful, but they arent.
If I change the model to all types on Wug's, would that make a difference?
Is it worth trying a manual root?

I use the Google Nexus 7 Toolkit which was great in fixing the problems after upgrade. Flashing the previous version bootloader (I think that is what it was) solved the root problem. The hints and guidance in this application are great and have always solved my problems. No offence meant to Wug here, I just find the other application suits me better.
Sent using Tapatalk 2

Waxwrong said:
I use the Google Nexus 7 Toolkit which was great in fixing the problems after upgrade. Flashing the previous version bootloader (I think that is what it was) solved the root problem. The hints and guidance in this application are great and have always solved my problems. No offence meant to Wug here, I just find the other application suits me better.
Sent using Tapatalk 2
Click to expand...
Click to collapse
As already said, both Toolkits have been attempted and both report that its rooted, but my device tells me otherwize, as do Titanium Backup.
Can someone just give me a step by step for what I should do to gain Root again?!

Wilks3y said:
As already said, both Toolkits have been attempted and both report that its rooted, but my device tells me otherwize, as do Titanium Backup.
Can someone just give me a step by step for what I should do to gain Root again?!
Click to expand...
Click to collapse
Hi, are you using the fully updated version of Toolkit (updated to include the 4.2 stuff. When I did mine I was told to go ahead but if it didn't work the next step was to flash the 4.1 bootloader? as it was compatible with 4.2
The root with the 4.2 bootloader didn't give me root so I flashed the 4.1 bootloader and rooted again. This was successful for me. The Toolkit application gives you step by step instructions as you request as long as it is updated to do 4.2 and follow the advice you should have no problem.
I don't think you can do the full updates in the application unless you are a donater. If I remember correctly you cannot update the application unless you use the donater version. The update for 4.2 came out at almost the same time as 4.2 was being pushed to devices.
You sound cluey enough to know you must use USB debugging but many users don't realise this or the tapping on the build trick to get the developer options available so you can select USB debugging.
Sent using Tapatalk 2

Waxwrong said:
Hi, are you using the fully updated version of Toolkit (updated to include the 4.2 stuff. When I did mine I was told to go ahead but if it didn't work the next step was to flash the 4.1 bootloader? as it was compatible with 4.2
The root with the 4.2 bootloader didn't give me root so I flashed the 4.1 bootloader and rooted again. This was successful for me. The Toolkit application gives you step by step instructions as you request as long as it is updated to do 4.2 and follow the advice you should have no problem.
I don't think you can do the full updates in the application unless you are a donater. If I remember correctly you cannot update the application donate version. The update for 4.2 came out at almost the same time as 4.2 was being pushed to devices.
You sound cluey enough to know you must use USB debugging but many users don't realise this or the tapping on the build trick to get the developer options available so you can select USB debugging.
Sent using Tapatalk 2
Click to expand...
Click to collapse
Hey mate, thanks for your reply !
I downloaded both ToolKits yesterday, so I'm guessing they are the newly updated ones?
Yes my tablet has usb debugging enabled, and is put into the Camera Mode.
I will have another go tonight, and try a different way, including using the "All Models" choice you mentioned.
If this doens't work, whereabouts in the ToolKit(Wug's) if the option to downgrade HBOOT in order to try the Root method you attempted which was successful.
Again, thanks mate !

Wilks3y said:
Hey mate, thanks for your reply !
I downloaded both ToolKits yesterday, so I'm guessing they are the newly updated ones?
Yes my tablet has usb debugging enabled, and is put into the Camera Mode.
I will have another go tonight, and try a different way, including using the "All Models" choice you mentioned.
If this doens't work, whereabouts in the ToolKit(Wug's) if the option to downgrade HBOOT in order to try the Root method you attempted which was successful.
Again, thanks mate !
Click to expand...
Click to collapse
I don't use Rug's Toolkit but Mike's Toolkit (only because it is easier to follow and use because it tells you what to do at all stages). You can see if it is updated by checking whether it has functions for 4.2 - I always use it for flashing the latest roms as well as the unlocking, root, recovery, etc, all of which the Toolkit guides you through. It even downloads the roms for you.
My only question is why did you put it in camera mode, change it back.
Sent using Tapatalk 2

Just install the 4.2 that is already Stock rooted, de-odexed apps.
Install the ROM as already Stock rooted, de-odexed apps.
Here is the link for the download: http://www.scottsroms.com/downloads.php?do=file&id=288
Thanks to Scott's post http://forum.xda-developers.com/showthread.php?t=1991157

[Q] Can't root 4.1.2 (Motochopper) after OTA update

so, I used motochopper after update ota
Motochopper claimed complete success, yet now I have two superusers (one with blue and white #, other with pirate android head). .the phone is essentially unrooted
what can I do to fix this? does anyone know what happened?

maybe you can try reset the phone data and root again, I have no problem to root 4.1.2 with motochopper, or if your phone is unlocked,and try to flash a cwm recovery and install a cm10, is a very fast rom.

v0rtex604 said:
so, I used motochopper after update ota
Motochopper claimed complete success, yet now I have two superusers (one with blue and white #, other with pirate android head). .the phone is essentially unrooted
what can I do to fix this? does anyone know what happened?
Click to expand...
Click to collapse
K you have 2 su solutions installed. You need to run both and try to update binary. One should work.
Are you unlocked? If you are, flashing a su zip would be an easy route to go if that doesn't work
Sent from my GT-P3113 on CM10.1 using Tapatalk HD

sloosecannon said:
K you have 2 su solutions installed. You need to run both and try to update binary. One should work.
Are you unlocked? If you are, flashing a su zip would be an easy route to go if that doesn't work
Click to expand...
Click to collapse
Both failed to update binary (error - no root). Locked - can't flash su zip.
So i used Droid Utility - flashed 4.1.2 and rooted by motochopper.
Problem resolved.