ATTN: My rom is bare basic, if your looking for a more streamlined rom
check out grdlock bluid based on the same source. Link removed because of assholes.
SNIP SNIP Several others released far more indepth and better roms, use them (like grdlock's).
http://www.androlib.com/android.application.com-hookerbots-rpics-twDt.aspx
I don't take donations. If you like my worth, the above app is from my favorite author, support him and of course XDA.
jcase said:
# id
uid=0(root) gid=0(root)
# busybox whoami
whoami: unknown uid 0
# busybox uname -a
Linux localhost 2.6.29-564a4a15 #1 PREEMPT Thu Feb 25 15:56:06 CST 2010 armv6l GNU/Linux
#
Just wanted to put that out there. If not one else puts out a better rom based on OTA tomorrow, I'll release it.
Its just bare OTA with su/superuser.apk.
Click to expand...
Click to collapse
That's exactly what i'm looking for an OTA with su added.
Thanks! can't wait for the upload.
i see you conquered the problem. MAGIC! well done
Thanks jcase! Will be testing tomorrow. Don't forget to rm /system/etc/security/otacerts.zip
flashing now. letting it run overnight should let me know if the stock Messages app bug is fixed. if not, Handcent it is!
So once again... no root for us that went to the 2.1 leak?
LexusBrian400 said:
So once again... no root for us that went to the 2.1 leak?
Click to expand...
Click to collapse
Nope. In order to flash a new rom without root, the HTC signature needs to be valid. In order to preserve root, the rom was modified by jcase to include su which breaks the signature hash. So, while you will be able to update to the official OTA update (assuming version is higher, which I believe to be the case), you can't install this rom.
Since most people will be updating to the OTA 2.1 away from the leak or away from 1.5, I'd personally recommend installing the OTA 2.1 directly from HTC. We'll likely be targeting it for root exploits next and abandoning version 1.5.
hoban_eris said:
Since most people will be updating to the OTA 2.1 away from the leak or away from 1.5, I'd personally recommend installing the OTA 2.1 directly from HTC. We'll likely be targeting it for root exploits next and abandoning version 1.5.
Click to expand...
Click to collapse
To be clear, install the otaroot rom released by jcase if you already have root. Install the OTA rom direct from HTC if you currently have the leaked 2.1.
hoban_eris said:
Nope. In order to flash a new rom without root, the HTC signature needs to be valid. In order to preserve root, the rom was modified by jcase to include su which breaks the signature hash. So, while you will be able to update to the official OTA update (assuming version is higher, which I believe to be the case), you can't install this rom.
Since most people will be updating to the OTA 2.1 away from the leak or away from 1.5, I'd personally recommend installing the OTA 2.1 directly from HTC. We'll likely be targeting it for root exploits next and abandoning version 1.5.
Click to expand...
Click to collapse
Thanks for the clarification. I really appreciate it. Can't wait for OTA root
The new 2.1 is exactly what I wished the last leaked 2.1 would have been. Its working so much better with no noticeable lag at all.
Thanks again guys!
wipe data
I have root now and am currently running the .3 rom, question
1. is this just an update to what i am running now?
2. Do i need to preform a wipe?
3. if i dont wipe does the phone maintain all my apps and settings i.e email google etc?
Damn, I was just uploading my all-in-one batch script and then I noticed this had been released... I started making a rom of it, then I noticed you already did! hah!
Thanks for being a night owl and already doin the work jcase. I'm gonna incorporate this into the all-in-one script.
mv error: cross-device link
i have updated this rom, works great!
bu i can't mv from /system/app to /sdcard
error message is "cross-device link"
but i had already remount the /system partion as rw, and i notice that rm is working fine - i can remove files in /system/app, but can't move to another directory!
before update to this rom, mv is working correct
any advice?
btw, there is no busybox in this rom
liushk said:
i have updated this rom, works great!
bu i can't mv from /system/app to /sdcard
error message is "cross-device link"
but i had already remount the /system partion as rw, and i notice that rm is working fine - i can remove files in /system/app, but can't move to another directory!
before update to this rom, mv is working correct
any advice?
btw, there is no busybox in this rom
Click to expand...
Click to collapse
same problem here. you can copy files and then remove the source. that's what I've been doing for my moves. As for busybox, I installed it myself, but I'm sure someone (if not me) will release an update.zip to install it sooner rather than later.
hoban_eris said:
same problem here. you can copy files and then remove the source. that's what I've been doing for my moves. As for busybox, I installed it myself, but I'm sure someone (if not me) will release an update.zip to install it sooner rather than later.
Click to expand...
Click to collapse
thanks for reply
I tried install busybox myself, but it dosn't work. this is my steps:
adb push busybox /sdcard/
adb shell
remount /system
mv /sdcard/busybox /system/xbin
failed
adb shell
remount /system
switch to another console
adb push busybox /system/xbin
failed
and, there is no "cp" command, I didn't find another way to copy from /system/app to /sdcard/
Wipe??
I just want to reiterate denonlake's question, does installing rooted OTA 2.1 require a wipe of DATA and CACHE partitions like the original root process? Can we preserve settings through this flash or is it best to go through the whole setup process again?
The mv and cp commands are in busybox. I did not install busybox, so you don't have them. The Toolbox that comes with the OTA is lacking them.
Install busybox yourself, or wait for grdlock or ivan's release.
in case anyone is interested, the Messages app bug and cell standby bugs are fixed in this release too (as well as the already known gmail login bug fix) the phone also seems to power down a lot faster than previous leaks.
havent tested google voice yet, probably cant till later today. someone else feel free..
shickfaced said:
I just want to reiterate denonlake's question, does installing rooted OTA 2.1 require a wipe of DATA and CACHE partitions like the original root process? Can we preserve settings through this flash or is it best to go through the whole setup process again?
Click to expand...
Click to collapse
I first tried installing from zip through recovery.
This did not appear* to work.
Next, wiped device and cache, then installed zip through recovery.
Success!
*My experience is limited. Maybe it did work, but nothing on the phone appeared changed.
Ok so this is just a rooted version of the Official OTA 2.1 right??? Nothing else has been done to it??
rustyman14 said:
Ok so this is just a rooted version of the Official OTA 2.1 right??? Nothing else has been done to it??
Click to expand...
Click to collapse
All this info is in the first post... X_X
jcase said:
This is the 2.1 OTA Rom with su, a modified sh, SuperUser.apk and spare_parts.apk added (root). Thats it, nothing else modified.
Click to expand...
Click to collapse
Hi All,
I'm facing a weird problem. I've just updated to android 2.2.1 by international galaxy (PDA I9000XWJS8) and I wanted to root it using update.zip applicable to 2.2 android version.
I have put the update.zip into /mnt/sdcard/ directory, then reboot into android recovery 3e, then 'install sdcard:update.zip'
Well, this is what I get:
----
Install from sdcard
Finding update package ...
Opening update package ...
Verifying update package ...
E:failed to seek in /mnt/internal_sd/update.zip
(Invalid argument)
E:signature verification failed
Installation aborte
----
Apparently the file cannot be found, because it is looked for in the /mnt/internal_sd directory and not /mnt/sdcard directory. But my internal sd is mounted in /mnt/sdcard.
How can I either change the behaviour of android recovery to look for zip file in /mnt/sdcard - or - mount my internal sd card as /mnt/internal_sd?
This of course does not permit me at all to install whatever update.zip.
During flashing to froyo 2.2.1 I've updated PIT to 8xx version (812?) and used repartition from ODIN.
Appart of that things look OK, any help greatly appreciated.
Search is your friend.
Since Froyo you cannot install update.zips from recovery (3e). You need 2e recovery.
SuperOneClick should work linkage .....
Alternatively you could flash a custom kernel via odin & have root, clockwork recovery & lagfix if you wanted.
is there any recommended kernel known to work with following configuration:
PDA: I9000XWJS8
PHONE: I9000XXJQ1
CSC: I9000OXXJP9
(build 2011.03)?
thanks
dejfson said:
is there any recommended kernel known to work with following configuration:
PDA: I9000XWJS8
PHONE: I9000XXJQ1
CSC: I9000OXXJP9
(build 2011.03)?
thanks
Click to expand...
Click to collapse
They pretty much all work with that config, just choose the one that would be most suited to your needs & level of competence.
And be sure to download the Odin version of the kernel you choose ......
List of I9000 custom kernels
try hardcore's speedmod-kernel-k13c-500hz, and root from CMW
i am trying to install busybox on my gt s5360
my device is rooted
i am running ICS Fusion v2.0 rom
Kuro's Kernel
When i select the busybox version & set the location of the installation to /system/xbin
and select install .
It shows Installed Busybox v1.18.2
but below it shows
your device is rooted
Busybox is not installed
System Storage: 51.19mb free
Rom Version : ICS Fusion v2.0
and when i open script manager to run a script
i get a error saying permission denied & says please reinstall busybox.
Can anyone please tell me what is the problem ???
I need to install it so that i can use v6 supercharger on my gt s5360
Please Help ME !!!!!!!!!!!!!
Unroot your phone
Then root it again
Update.zip contains a busybox file
Then try to update it
Or replace busybox file in /system/xbin
And set permission
Copied signature
i am using hyperion 9 rom
how to install busy box in that ??
yhi said:
i am using hyperion 9 rom
how to install busy box in that ??
Click to expand...
Click to collapse
https://play.google.com/store/apps/details?id=stericson.busybox
Hi there
I would like to root my Samsung Galaxy Y, but I encounter a problem while doing it.
When I select "apply update from sdcard" in the recovery menu, it would tell me this:
E: failed to mount /sdcard (No such file or directory)
E: Can't mount /sdcard
Install from sdcard complete.
Could somebody tell me how to get through this?
BTW. Some additional information about my phone. Maybe it could help.
Model Number: GT-S5360
Android Version: 2.3.6
Baseband Version: S5360DXLF1
Kernel Version: 2.6.35.7 [email protected]#1
Build Number: GINGERBREAD.DXLF2
P.S. I'm still new to these forums so please forgive me if I did something that you didn't like
http://www.mediafire.com/?26m8sgx144bitpz
Try it
Peace
Hit Thanks & It will Disappear
Sent from S II Running Official ICS 4.0.4 with Siyah 4.1 [/size]
First sorry for my bad english
My phone is f320k(LG G2 Korea model)
I'm trying to use xposed so I installed twrp and downloaded [xposed-sdk22-arm-20150514.zip]
and I go to recovery mode and wiped Cache,Dalvik Cache
Next i tried to install xposed-sdk22-arm-20150514.zip but
[LOG]
-Mounting /system and rootfs
-extracting files
-checking environment
Xposed version: 3.0 alpha4 (20150514)
! Wrong SDK version: 21, expected 22 - 22
! Please download the correct package
! for your platform/ROM!
-Unmounting /system
-Done !
E : Error executing updater binary in zip '/sdcard/xposed-sdk22-arm-20150514.zip'
Error flashing zip '/sdcard/xposed-sdk22-arm-20150514.zip'
Updating partition details...
...done
DId i use wrong things?
LLCR said:
-checking environment
Xposed version: 3.0 alpha4 (20150514)
! Wrong SDK version: 21, expected 22 - 22
! Please download the correct package
! for your platform/ROM!
Click to expand...
Click to collapse
Your english is fine, but your log shows exactly why it fails, you're using a 5.0.x firmware while flashing xposed for a 5.1.x firmware.