Database Develop

[HOWTO] get root back after ota update!

this is how i did it anyways. i had to flash the boot.img and update via stock recovery to get the ota to flash. but then no root!
so heres how i got it back:
download the superboot/paulobrien method (http://forum.xda-developers.com/showthread.php?t=882333).
boot phone to fastboot.
Code:
fastboot boot boot.superboot.img
let phone boot, open terminal, su, just to check.
reboot phone.
rooted and ota'd now!

I've got root back, but not by that method. I think it might be a mistake to flash that boot.img, as the 2.3.1 update patched boot.img... so replacing it with one from 2.3 might not be the best idea. But I guess no one really know what the changes might be.
I guess time will tell
The method I used was:
1. Boot into fastboot.
2.
Code:
fastboot flash recovery recovery-clockwork-3.0.0.0-crespo.img
3. Reboot from fastboot directly into recovery (not doing so will cause android to replace CWR).
4. Mount USB, copy su-2.3.6.1-ef-signed.zip to the /sdcard via windows/linux
5. Mount /system
6. Install update from zip (browse to were you put su-2.3.6.1-ef-signed.zip).
7. Install it, and reboot.
8. open root explorer, and rename /etc/install-recovery.sh to install-recovery.sh.old
9. open ROM Manager, reflash CWR.
now you are all done, rooted, w/ CWR

I reflashed CWM, then from CWM, remounted /system, then used adb to chmod 6775 su. That restored root pretty easily.
What Recovery image are you using? Are you able to get into it consistently? I can't from fastboot except for if I immediately hit it up after flashing CWM with fb, or from ROM Manager (flash from RM, then select reboot to recovery).

Luxferro said:
I've got root back, but not by that method. I think it might be a mistake to flash that boot.img, as the 2.3.1 update patched boot.img... so replacing it with one from 2.3 might not be the best idea. But I guess no one really know what the changes might be.
I guess time will tell
Click to expand...
Click to collapse
its not flashing it. read the command. its only booting to that image to install su. then reboot will bring you back to stock 2.3.1 boot.img.

distortedloop said:
I reflashed CWM, then from CWM, remounted /system, then used adb to chmod 6775 su. That restored root pretty easily.
What Recovery image are you using? Are you able to get into it consistently? I can't from fastboot except for if I immediately hit it up after flashing CWM with fb, or from ROM Manager (flash from RM, then select reboot to recovery).
Click to expand...
Click to collapse
im using stock recovery.

I'm rooted on 2.3.1 but I lose clockwork recovery when I reboot an gota reflash it using rom manager. Anyone having this problem

k0mpresd said:
its not flashing it. read the command. its only booting to that image to install su. then reboot will bring you back to stock 2.3.1 boot.img.
Click to expand...
Click to collapse
Sure it is. But on Android bootup, a script is running somewhere to replace it with stock recovery. They did this on Droid_1 after the first or second update (that's my only other android phone... so my android experience is limited).
edit: I just found the script. It's /etc/install-recovery.sh .... just renamed my to install-recovery.sh.old. gonna reflash CWR and test it now.
edit2: yep, works great now. CWR, and retained my 2.3.1 boot.img

So is this something that the devs of clockworkmod need to fix in order to not lose clockwork recovery when u reboot the phone

chris6278 said:
So is this something that the devs of clockworkmod need to fix in order to not lose clockwork recovery when u reboot the phone
Click to expand...
Click to collapse
No, it's a safety mechanism so you can't lose recovery... It has nothing to do with clockworkmod. Someone can make a root script or app that disables it easily. Or people can just do it themselves manually.
edit: actually, all that needs to be done is add some code to the update script inside su-2.3.6.1-ef-signed.zip so when it installs the update, it renames install-recovery.sh

distortedloop said:
I reflashed CWM, then from CWM, remounted /system, then used adb to chmod 6775 su. That restored root pretty easily.
What Recovery image are you using? Are you able to get into it consistently? I can't from fastboot except for if I immediately hit it up after flashing CWM with fb, or from ROM Manager (flash from RM, then select reboot to recovery).
Click to expand...
Click to collapse
I want to attempt to restore my root by using your method. But I'm lost at the part when you use adb chomd 6775 su,
When I go into adb, do i just type chomd 6775 su? Do I have to download something else to use this? Please explain, thanks

If u dont mind can u please provide the instructions on how to do it manually. Id really appreciate it. Sorry im a noob lol

Where in root explorer do i need to rename

Where in root explorer do i rename it

plmiller0905 said:
I want to attempt to restore my root by using your method. But I'm lost at the part when you use adb chomd 6775 su,
When I go into adb, do i just type chomd 6775 su? Do I have to download something else to use this? Please explain, thanks
Click to expand...
Click to collapse
chmod needs to be done at a # prompt.

chris6278 said:
Where in root explorer do i rename it
Click to expand...
Click to collapse
I'm trying not to be rude... but if you can post in this thread, you can read it to. Before you asked your question a couple different step by step posts outlined all you need to know.... and this thread is only 2 pages...

Is it just me or does adb remount no longer work?
If I use the old koush rootboot.img it works, but no wifi, if I use the stock boot.img, I get no wifi but am able to remount.

I can read an ive done all the steps u posted but my ? Is where in root explorer do i find /etc/install-recovery.sh so i can rename it? Im learning this as i go so excuse me if i sound stupid sometimes

chris6278 said:
I can read an ive done all the steps u posted but my ? Is where in root explorer do i find /etc/install-recovery.sh so i can rename it? Im learning this as i go so excuse me if i sound stupid sometimes
Click to expand...
Click to collapse
do you have root explorer? if not, it's just a file explorer that has root access. by default when you open it you are at /
you need to scroll down to /etc
go in that folder and find the install-recovery.sh
look up top for the button to turn it from read-only to read-write, click it
go back to the file long press it, and then choose rename.

Luxferro said:
I'm trying not to be rude... but if you can post in this thread, you can read it to. Before you asked your question a couple different step by step posts outlined all you need to know.... and this thread is only 2 pages...
Click to expand...
Click to collapse
Thanks..I already rerooted but thanks anways

I got root explorer an followed ur directions an now everything works great. Thanx for ur help an sorry for being a pain lol

[Q] I9000T stuck during boot, can't get root

I used z4root's temporary root and enabled RyanZA's OCLF but the phone never booted again (stuck at Galaxy S logo, after my carrier's logo.)
"adb logcat" shows that pretty much everything in /data is missing.
I can't get root to investigate much further. I installed update.zip from this thread:
http://forum.xda-developers.com/showthread.php?t=728754
which gave me su and busybox, but su just reports "Permission denied" and logcat shows
E/su ( 3315): stat failed with 20: Not a directory
W/su ( 3315): request rejected (2000->0 /system/bin/sh)
(in recovery mode, the stat fails with 2: No such file or directory instead). "su -s /system/xbin/busybox" fails in the same way.
I have /system/app/Superuser.apk, but given that nothing is really running due to the state of /data I don't think that helps. I can't see what's in /data due to not having root though.
any suggestions?

ok I have unfucked the phone. I couldn't get RageAgainstTheCage to run (never got a root shell), but the newer KillingInTheNameOf worked.
In /data I found that the lag fix had renamed data, system, app, app-private, dalvik-cache with .old suffixes. The ext2 volume was there but nothing was mounting it on boot. The directories had been replaced with files just containing the text "stump".
For now I nuked the files, renamed the .old directories back to what they should've been, and the phone is working again. (Still no lagfix though.)

[Q] Is it safe to root a ICS stock rom?

Hey dudes, I want to root my note to have more options to work with, but Im quite afraid that something wont go as planned.
I updated my note to ICS ( LPY ) stock from germany ( 4.0.3 ), and Ive seen a couple of post explaining how to do it, some of them through CMW, others through ODIN.
So Ive got two questions:
Is it really safe to root without any trouble? ( I know nothing is 100% safe, but as far as I know a lot of people have bricked their notes either flasing ICS custom roms or rooting ) So Im quite afraid by that.
And if its really safe to do, wich way is the safer?
Cheers.

Its relatively safe, its what you do before and afterwards thats probably not. Dont wipe anything, or factory reset on ICS unless you have read its safe (like cm9 from entrophy, xplodwild and co)
Just follow any of the many tutorials and you will be fine.
Notice: moment you root you loose warranty
Sent from my GT-N7000 using Tapatalk 2

baz77 said:
Its relatively safe, its what you do before and afterwards thats probably not. Dont wipe anything, or factory reset on ICS unless you have read its safe (like cm9 from entrophy, xplodwild and co)
Just follow any of the many tutorials and you will be fine.
Notice: moment you root you loose warranty
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
I know that I loose warranty, but I also know that I can unroot
Yes I actually knew something about factory resets or wipe things can damage it.
Thanks

Please read here ;http://forum.xda-developers.com/showthread.php?t=1659768 .....Make sure to download the Toolkit from the link at the end of this post and put the "Root" .zip in your device's internal memory. You will enter Bootloader Mode, and then Recovery Mode as detailed in the FAQ above. You will now select "install zip from sdcard" then "choose zip from sdcard" and look for the Root.zip which you previously put in your SDcard. Select it with the Power button to flash it and then reboot your device. When your device finally boots, check if the Superuser app is available, if it is then you're rooted now.
*Fixing Root*
In some cases a ROM can come with a broken root. You will need to flash a file with root encountered in this LINK. Be sure to download from the device if possible and select the appropiate version, yes the one that as of this writing says "Eclair/Froyo/Gingerbread/Honeycomb/IceCreamSandwich (2.1 – 4.0.3)". It also works with Android 4.0.4. Flash that package using CWM Recovery, by selecting "install zip from sdcard" then "choose zip from sdcard" and you're set.
[Unrooting]:::::::::::::::::::::::::::::::::::::::::::
There are two ways to unroot: the automatic way (which consists of a CWM Recovery flashable little file provided in the Toolkit link at the end of this guide) and the manual way. For the manual way I will here quote phonic's excellent post (modified the word "program" with "app" to avoid confusion and added an app link):
So if you want to unroot your tablet, you simply need to remove the 'su' binary. There are various ways to accomplish this, but one of the easier methods would be to download/install a terminal app such as "Terminal Emulator", launch it, and issue the following commands:
Code:
su
mount -o remount, rw /system
rm /system/app/Superuser.apk
rm /system/bin/su (or "xbin" instead of "bin" in some cases)
umount -o remount, ro /system
exit

root is safe but u loose warranty...u can also unroot ur phone to get the warranty again
Sent from my Galaxy Mini using xda premium

[Q] Help with 498 Error under Ginger Yoshi 1.5

I installed Ginger Yoshi 1.5 on my Android Dev Phone 1 by following these instructions:
http://forum.xda-developers.com/showthread.php?t=1178665
I found that most things are working, but I cannot install CoPilot GPS (28MB)
Error 498 in Google Play seems to mean the /cache partition is too small. My cache partition is 27MB.
I tried redirecting /cache to larger place with Cache Fixer 1.1
The "Data" option doesn't succeed in expanding the cache.
The "Tmpfs" option successfully makes the cache bigger, but it makes Play force close when I try to install the app.
I Tried using CacheDownload2SD 1.7.1, but it doesn't do anything
I got a message saying my su binary should be updated. I don't know if that is related or not.
I tried updating the SuperUser su binary from 2.3.2-efgh to 3.1.1
su Binary Updater says "Make sure new su works... fail!"
When I try again, su Binary Updater says "Copying su to /system... fail!"
When I try yet again, su Binary Updater again says "Copying su to /system... fail!"
I used Root Checker to verify root access. The phone is properly rooted. I don't know if this issue is related
I've considered downloading an apk and manually installing it. That should work, but then Google Play wouldn't let me know when an update became available. Any ideas on how to solve the problem? Does anyone know why Cache Fixer and CacheDownload2SD dont' work? Can anyone see why the su binary won't update? I've spent all day clearing caches, rebooting, and attempting installs. Why does Google Play need to download to such a tiny partition?

@IMSargon if your /cache partition is too small then you need to use custom MTD.

HTCDreamOn said:
@IMSargon if your /cache partition is too small then you need to use custom MTD.
Click to expand...
Click to collapse
Thanks for that. I certainly have some more reading before I fully understand the topic. When I upgraded to Ginger Yoshi 1.5, I changed from DangerSPL to hboot-1.33.0013d which gives practically the same partition sizes, except /cache is 27MB instead of 30MB, which is why I didn't have this problem before.
So you're saying I can flash to this custom bootloader to increase my cache size (decreasing /system and/or /data accordingly), install the GPS app, then flash back for normal operation? It sounds like a risky proposition. Is there no way to permanently or temporarily redirect the location to which Play downloads APKs? Such solutions appear to exist (Cache Fixer, etc), but they don't seem to work for me (why?).

No, if you change partition sizes you will be wiping those partitions. Maybe a better option is to do it just once but bind mount to sdcard, see the link htcdreamon gave for more info on this
Sent from my Nexus 4 using xda premium

demkantor said:
No, if you change partition sizes you will be wiping those partitions.
Click to expand...
Click to collapse
This is a relief to hear. It sounded like they would just redefine the partition boundaries with the data in place and hope for the best. I was wondering how that worked. After re-reading, the instruction do call for wiping the partitions and re-flashing the ROM.
demkantor said:
Maybe a better option is to do it just once but bind mount to sdcard, see the link htcdreamon gave for more info on this
Click to expand...
Click to collapse
That would work, and it's something I'll seriously consider once I have a chance to read all the documentation. It seems to me, though, that I should be able to unmount and remount elsewhere the /cache partition on a live system from the command line. Any reason I should not attempt that?

If you want to resolve your problem then follow these steps
- Clean your Device Cache
- Erase Market Data
- Scan your Device for Viruses
- Restore Smartphone to Factory Settings
I also have tutorial like article where you will find all the solution steps to fix the error here is the link:
optimum-systems.com/2013/04/error-498-in-android.html
I hope you will resolve your problem

I tried making a folder under /sdcard, removing /cache, and replacing it with a symlink to the folder in /sdcard. That didn't work for a number of reasons. Firstly, mkdir was missing, which was a pain. I just made the directories with File Manager on the phone - I'll fix that later. Then it wouldn't let me change the ownership of the target directory on the sdcard, even though I was root. When I tried downloading my app, Play force closed.
My next idea was to put the folder in /sd-ext, which is my next largest partition. This is an ext4 partition on the sdcard. I created a folder there. Then I deleted /cache/download and created a symlink to my folder in /sd-ext. I didn't have any problems changing permissions this time. For whatever reason, Play did not force close, and successfully installed the app.
I'll write what I did here, but I'll pretend mkdir worked.
Code:
rm /cache/download
mkdir /sd-ext/download
chown system:cache download
ln -s /sd-ext/download /cache/download
chown -h system:cache /cache/download
I'd expect this setup to survive a reboot, so maybe you want to delete the symlink and remake the original folder to set things back to normal. If not, only apps that use /cache/download are effected, so you might as well leave it. Just clean that folder out every so often.

Bootloop after CM install. Won't restore backup, mount /data, flash stock

Hi developers. I am sorry for posting this. I spent the last week trying to solve it by myself with no hope. This is my second time installing something on a phone, but it is my only phone, so I beg anyone for a help...
-What I did:
Some days ago I downgraded to this ROM C5503_10.1.1.A.1.310_GLOBAL-LTE.ftf to use DoomLord rooting script. I did it with flashtool for linux and I applied his .bat step by step in the terminal since windows would not detect my phone.
It worked. I had root for some days, but I was still annoyed by sony default android. So I decided to install Cyanogenmod.
I unlocked the device with sony official system and wen't straight to this instructions, before the first reboot
wiki.cyanogenmod.org/w/Install_CM_for_yuga
I booted succesfully in CWM, followed everything as it says there. But that's where weird things happened:
-The problems:
-The backup
I tried, it wouldn't mount /sdcard. Since I don't understand much about this, I thought it was normal. The next choice was sdcard1, I backed up there. Or so I thought...
-The factory reset
I factory reset, again, not mounting sdcard. Here is the message that shows when I try this now:
can't mount /data!
Error mounting /sdcard.android_secure
Skipping format...
Data wipe complete.
Since it said it is complete, I went on installing the zip file from my sdcard1. Both CM 10.2.1 (dogo, the right one for my phone) and the appropriate GAPPS.
Now it loops on the CM loop animation and I have to remove the battery...
-The restore problem
It still boots on the recovery mode. So I tried recovering my backup from sdcard1. But the image name is 1970.01.01.00.03.16. And it says "md5 mismatch"
I tried flashing again the stock rom with flashtool. The proccess goes on but nothing happens. I still have CWM and the boot loop.
I read elsewhere someone with a similar problem who solved using sony "emma" software. I installed it, it won't even recocnize my phone.
It recocnizes that there is a phone, but don't know which one.
But that has alway been the case with windows. I haven't been able to do anything in windows other then accessing the sdcard (when the phone worked).
Is there something I can do? I imagine that somehow, for some reason, the /data and /sdcard partitions got corrupted. I imagine I would need to repartition this and install again, but I have no idea how this happens on phones...
I can mount /system /cache and /storage/sdcard1. just /data I can´t. Says "error mounting /data"
This is my only phone and a vey recent $400 thing. I was very stupid to do that withouth a replacement and really need this phone. I greatly appreciate any help...

I found this post forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/ searching the internet. Is it possible that this would solve my problem? or would it finish bricking the phone?
Here's what you'll need:
Working recovery, basic knowledge of adb & the shell
Parted (download here)
stock PB31IMG.zip
Note also that I had run unrevoked forever (so my phone was S-OFF) ... I'm not sure if that's required or not.
So, grab parted from the link above. Now you need to extract the individual binaries from the .zip (the 6 files in the sdparted folder within the zip), ideally to your android-sdk\tools directory. Now push all 6 files (adb push [file] /sbin/). Next, we need to make them useable, so go into the shell (adb shell). Change to your /sbin/ directory, and run: chmod 0755 <file> on each of the 6 files.
Now, we need to fix the partitions. This is assuming that the partitions are there, just the wrong format (which is what happened to me .. I accidentally made them FAT32 instead of ext). So, run the following: parted /dev/block/mmcblk0 mkfs ext2. It will ask if you want to continue, hit yes. When it asks for the partition number, enter 1. Next, when it asks for the format, enter ext2. Let it do its thing. Now, once it's done, run parted again. This time, enter partition 2 (everything else is the same).
Click to expand...
Click to collapse