I have create rooting method based on DooMLoRD method [ROOT] Rooting Toolkit for Xperia 2011 ICS [FW:.562]{LOCKED & UNLOCKED BOOTLOADERS} but have different approach.
special thanks to DooMLoRD
REQUIRED ROOTED DEVICE prior to update
How this method work?
1. create file /data/local.prop contain "ro.kernel.qemu=1" to enable root shell (this step must be done on ROOTED DEVICE)
2. update using Update Service/PC Companion/Flashtool without Factory Reset
3. after device updated,we should gained root shell that we use to push su binary and superuser.apk
Download : Xperia-ROOT.rev3.zip
Download : Xperia-ROOT.rev4.zip
Including autoinstall Stericson Busybox 1.20.1 and nAa CWM Recovery 5.0.2.7
extract Xperia-ROOT.rev3.zip to any folder,so you got something like this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Another great tutorial made by DragonClawsAreSharp can be found at
[Tutorial]Root.Xperia 4.0.4 ROM | 4.1.B.0.431
STEP :
1. run 01-local-prop.cmd to create /data/local.prop (enable android emulator hack)
2. power off device and update your device WITHOUT FACTORY RESET
Update Service
select Update (recommended)
Flashtool
UNMARK WIPE DATA
after your device updated
on 1st boot your device will reboot once
on 2nd boot it will boot normally
if you got bootloop run 02-push-root-files.cmd right away
until it finished wait for 1 or 2 reboot
if you still got bootloop you need to reflash rootable firmware(zergrush method) then try again
3. run 02-push-root-files.cmd to push su binary and superuser.apk
4. your device will automatically reboot
5. enjoy your new rooted firmware
this method tested on :
1. Arc S ROOTED GB 4.0.2.A.0.42 updated to ICS 4.0.4
2. Ray ROOTED ICS 4.0.3 updated to ICS 4.0.4
3. Active ROOTED GB 4.0.2.A.0.42 updated to GB 4.0.2.A.0.62
tested by user:
1. SK17i ROOTED GB 4.0.2.A.0.58 updated to GB 4.0.2.A.0.62 by Bolussimo
2. Rooted SK17i FW 4.1.B.0.431 by draco_ag
3. LWW WT19i Rooted GB 4.0.2.A.0.58 updated to ICS 4.0.4 by alness1213
4. SK17i ROOTED GB 4.0.2.A.0.42 updated to ICS 4.0.4 by DragonClawsAreSharp
Dis method can only work on non-latest firmware.... lets say am using .62 firmware which is not rooted, dat means i need to downgrade to lower version & ROOT it to use dis!!!
Nice piece of work brov...
whalesplaho said:
Dis method can only work on non-latest firmware.... lets say am using .62 firmware which is not rooted, dat means i need to downgrade to lower version & ROOT it to use dis!!!
Nice piece of work brov...
Click to expand...
Click to collapse
Yup,that's it bro.
As we know zergrush exploit doesn't works on FW starting .62 and above.
we just need any firmware that can be rooted using zergrush method then use this tool before and after upgrade to gain updated and rooted firmware.
I have tested this method on my Xperia Active running on ROOTED FW .42(rooted using zergrush method) use this tool before and after update to gain rooted FW .62
When doing update you MUST NOT do factory reset.
Wipe Data will deleted any add file & make tha phone return to factory reset right....?
whalesplaho said:
Wipe Data will deleted any add file & make tha phone return to factory reset right....?
Click to expand...
Click to collapse
it will clean all data from your phone,all user installed app and setting will gone.
in rooting process DO NOT factory reset.if you wish to factory reset you can do it after running the tool after 1st boot (step 3 - 5 )
And you really did it, bro! I will use your method, root my .62 fw and get ready for my rooted ICS. Thank you again!
Sent from my SK17a using xda premium
A little question...
Just add these line " ro.kernel.qemu=1" to already exist /data/local.prop right???
Or make another /data/local.prop???
Till-Kruspe said:
A little question...
Just add these line " ro.kernel.qemu=1" to already exist /data/local.prop right???
Or make another /data/local.prop???
Click to expand...
Click to collapse
when running 01-local-prop.cmd
it will overwrite /data/local.prop
so /data/local.prop only contain "ro.kernel.qemu=1"
you need to run 01-local-prop.cmd just before you update your device.
puppet13th said:
when running 01-local-prop.cmd
it will overwrite /data/local.prop
so /data/local.prop only contain "ro.kernel.qemu=1"
you need to run 01-local-prop.cmd just before you update your device.
Click to expand...
Click to collapse
I got bootloop...
Till-Kruspe said:
I got bootloop...
Click to expand...
Click to collapse
did you read this?
puppet13th said:
you need to run 01-local-prop.cmd just before you update your device.
Click to expand...
Click to collapse
puppet13th said:
did you read this?
Click to expand...
Click to collapse
yes...I have done all the step...but got bootloop...
Till-Kruspe said:
yes...I have done all the step...but got bootloop...
Click to expand...
Click to collapse
can you tell me what have you done step by step?
edit :
if you have updated your device and run "02-push-root-files.cmd"
it's look like the script failed to remove /data/local.prop
from 02-push-root-files.sh :
Code:
adb shell rm [COLOR="Red"]-f[/COLOR] /data/local.prop
builtin rm command syntax on GB build :
Code:
rm [-rR] <target>
workaround :
open env.cmd
type these command
Code:
adb shell rm /data/local.prop
puppet13th said:
can you tell me what have you done step by step?
edit :
if you have updated your device and run "02-push-root-files.cmd"
it's look like the script failed to remove /data/local.prop
from 02-push-root-files.sh :
Code:
adb shell rm [COLOR="Red"]-f[/COLOR] /data/local.prop
builtin rm command syntax on GB build :
Code:
rm [-rR] <target>
workaround :
open env.cmd
type these command
Code:
adb shell rm /data/local.prop
Click to expand...
Click to collapse
my phone is rooted 2.3.4 with cwm, FW .58, lock bootloader...
First I run 01-local-prop...but on my phone it doesn't ask for superuser permission...in the 01-local-prop it say complete (done replacing new local.prop)...I have checked /data/local.prop (open with text editor) it has this "ro.kernel.qemu=1"
Then I open up PCC and update my phone to FW .62...Bla bla bla...finished...restart phone.....then bootloop...
what to do now...this is my only phone...please help me...
Till-Kruspe said:
my phone is rooted 2.3.4 with cwm, FW .58, lock bootloader...
First I run 01-local-prop...but on my phone it doesn't ask for superuser permission...in the 01-local-prop it say complete (done replacing new local.prop)...I have checked /data/local.prop (open with text editor) it has this "ro.kernel.qemu=1"
Then I open up PCC and update my phone to FW .62...Bla bla bla...finished...restart phone.....then bootloop...
what to do now...this is my only phone...please help me...
Click to expand...
Click to collapse
if you have FW. 58 or erlier ftf flash it with flashtool DO NOT UNMARK wipe data.
then root it using zergrush method.
try again from step 1
edit :
it's look like you got bootloop because your data partition was full.
now i got bootloop downgraded to fw. 42 without factory reset.i only got 50mb free before flashing.
my rom was odexed before,so 50mb was not enought to hold dalvik-cache from framework and system app
updated 1st post
puppet13th said:
updated 1st post
Click to expand...
Click to collapse
Hi puppet,
How come he was not asked by Superuser for root permission?
Is it because he had allowed adb with root rights earlier and had checked "always allow"? (may be).
Or there can be some other reasons?
Thanks,
Rick
Sent from my SK17i using XDA
Till-Kruspe said:
my phone is rooted 2.3.4 with cwm, FW .58, lock bootloader...
First I run 01-local-prop...but on my phone it doesn't ask for superuser permission...in the 01-local-prop it say complete (done replacing new local.prop)...I have checked /data/local.prop (open with text editor) it has this "ro.kernel.qemu=1"
Then I open up PCC and update my phone to FW .62...Bla bla bla...finished...restart phone.....then bootloop...
what to do now...this is my only phone...please help me...
Click to expand...
Click to collapse
now i hit the bull eye
/data/local.prop : ro.kernel.qemu=1 --> cause system instability that cause bootloop if data partition was full
download Xperia-ROOT.rev3.zip from 1st post and run 02-push-root-files.cmd it will wait for device before reboot(bootloop).after /data/local.prop(ro.kernel.qemu=1) gone,it will boot normally
when it reach home screen you need to make more free space on /data partition
DragonClawsAreSharp said:
Hi puppet,
How come he was not asked by Superuser for root permission?
Is it because he had allowed adb with root rights earlier and had checked "always allow"? (may be).
Or there can be some other reasons?
Thanks,
Rick
Sent from my SK17i using XDA
Click to expand...
Click to collapse
it's look like superuser automatically allow su access from adb shell
i just check from superuser app,there is no shell in apps list.
if i remember correctly old superuser doesn't automatically allow su access from adb shell,it will prompt su access and if allowed or denied it will be added to app list as unknown
puppet13th said:
it's look like superuser automatically allow su access from adb shell
i just check from superuser app,there is no shell in apps list.
if i remember correctly old superuser doesn't automatically allow su access from adb shell,it will prompt su access and if allowed or denied it will be added to app list as unknown
Click to expand...
Click to collapse
Okay. Got it.
So if he had connected his dead cell to the pc and run the 2nd bathc file, things would become alright for him right?
Sent from my SK17i using XDA
DragonClawsAreSharp said:
Okay. Got it.
So if he had connected his dead cell to the pc and run the 2nd bathc file, things would become alright for him right?
Sent from my SK17i using XDA
Click to expand...
Click to collapse
02-push-root-files.cmd doesn't run on su access because of /data/local.prop (ro.kernel.qemu=1)
when ro.kernel.qemu=1 in effect we automatically got root shell
so when we start adb shell we got # instead of $
# = root user
$ = normal user
Related
SINCE FREE X10 IS NOW BETA, THIS HOW TO IS NO LONGER VALID
Hello world !
I noticed there was nothing to explain simply how to install the increible X10 Free Rom in dual-boot with your regular 2.1 rom of Zdzihu.
** No responsability for anything, you are all responsible of what you're doing !! **
** Please follow ALL these steps. Don't try to be Indiana Jones by flashing your device without all the tools needed !!! **
INSTALL
(for 1st install)
Before attempting anything, make sure you have AT LEAST 50% of battery charge. Don't try anything with low battery, you can abort the flashing and brick your device !!!
Please make sure you're also running a 2.1 rom (Generic, nordic, official, custom...)
- Download FreeX10 v0.0.1 file (NOT 002 yet !!!)
- Download Android SDK
You don't need to save the entire archive (but you can), you just need the Tools folder (because it contains ADB, the Android Debug Bridge we need to install files).
- On x10 :
Download and install Busybox (from Market), make sure it says "Done!".
Connect your x10 in USB, mount SD card, and copy files FreeX10.zip and install on the root of your SD Card.
Enable USB debugging (Parameters > Applications > Development).
- On your computer, go in the Tools folder, open a DOS prompt (for Windows 7 : hold CAPS + right click, you'll see Open a DOS prompt) and
type :
Code:
adb shell
(this will run ADB shell... You will get a "$")
- Type :
Code:
su
(this will make you super-user, you will get a "#")
- Type :
Code:
dd if=/sdcard/install of=/data/install && chmod 777 /data/install && /data/install
(It will display "11", "1+1", or "inflating:..." ...)
- Wait, have a beer, pray for your sins for your phone not to turn into a $600 brick
- One minute after, when it shows
Code:
All done, please reboot!
, reboot ! (But you can gently quit ADB by typing
Code:
exit
twice
)
Note : regarding me, I typed "exit" to quit ADB, I turned off ADB on phone and disconnected USB. You can do, it's even safer
- Wait up to 5 minutes for the phone to boot, it is NORMAL !!!! It looks stuck on Sony Ericsson logo and/or on Free X10 logo, it's NOT stuck !!! You MUST wait !!!!
- It will finally run normal, your phone is alive and 2.2-hearted !!
You are now eligible to install v0.0.2 (as it comes as an update).
Dual Boot usage
This rom comes with a great Dual Boot, which means the 2.2.1 is installed safely apart from your original 2.1 rom. This means you can switch back anytime to stock rom. To say it simply :
- Your Android 2.1 is here, and no changes are made to it (apps, version, etc etc). It is stored as it has to be, in the internal 1Gb phone memory storage (called the "NAND").
- FreeX10 (2.2.1) is running from image files (like .ISO files) stored in your SD Card. This means the two Android are living together peacefully, without affecting (theorically) each other.
FreeX10 mainly creates a bootloader, for you to choose whether to test 2.2.1, or go back to 2.1 for your daily use.
- To run 2.2.1 : do nothing (default boot)
- To run 2.1 : press any key at boot, when it shows "Sony Ericsson".
Notes when upgrading to v0.0.2 :
- As Android is stored into image files (.IMG), upgrading will wipe out all your content (it does a fresh "install"), make backup of what you need !
- to avoid future bugs, altough you're not forced to do, do the routines to make sure Wifi, root, packages install, ... work. This is because USB debug can break, so you won't be able to use ADB to fix these bugs
- Root is strongly recommended to work, because it's cool and because the CPU performance is set to highest : stuck at 998MHz all the time, it will drain your battery like hell ! You can switch it back to original power saving plan (ondemand plan) by using (ie) SetCPU. Root required !
If your Android goes instable, does not work anymore, or you want a fresh install after lots of tests, simply drag and drop the original v0.0.2 .img files on your SD card. This will make you boot into a fully fresh install.
For all bugs, commands, etc.. Please go first to this excellent (and very easy) thread !!
Nice..
How about one on AOSP 2.1
Perceval from Hyrule said:
Hello world !
I noticed there was nothing to explain simply how to install the increible X10 Free Rom in dual-boot with your regular 2.1 rom of Zdzihu.
Click to expand...
Click to collapse
nice dummies HOW TO
and ohhh my god there is dummies
all comands needed
INSTALLATION
1. Download the rom package (FreeX10_alpha-release_0.0.1.tar.bz2)
2. Unpack it to the root (main folder) of your SD Card
3. Connect your phone in USB Debugging mode
4. Open ADB shell, switch to root user (SU)
5. Issue the command
dd if=/sdcard/install of=/data/install && chmod 777 /data/install && ./data/install
6. Reboot when installation is finished
7. Enjoy
---------------------------------------------------------------------------------------------
CHANGE BOOT PRIORITY
Copy chargemon.txt file to
/system/bin
folder ON YOUR ORIGINAL 2.1 ROM, NOT FROYO!!!
---------------------------------------------------------------------------------------------
UPGRADE TO 0.0.2 VERSION
Boot into 2.1, unpack the content of FreeX10_alpha-release_0.0.2-UPDATE.tar.bz2 into
/sdcard/FreeX10
folder and reboot into updated 2.2!
NOTES:
1. SMS vibrate is disabled by default; open Messaging, press MENU button -> settings -> vibrate -> always
2. If you don't have radio (network) after 1st boot, please open ADB shell and issue this command:
killall servicemanager
3. If you don't have root access, please open ADB shell and issue this command:
chmod 4755 /system/bin/su
---------------------------------------------------------------------------------------------
hope it helps too
UPDATE TO v.0.0.2
Note : you can only update from 0.0.1 to 0.0.2. I mean you can't do a fresh install of 0.0.2, you MUST have 0.0.1 installed !
- Download v0.0.2 from main thread.
- Run your device on your regular 2.1 rom (while off, power on, and press any button when it displays Sony Ericsson logo)
- Mount the SD Card, then copy data.img and system.img from the archive into the folder /FreeX10. Replace the two .img files.
- Reboot into 2.2, have fun ^^
OmegaRED^ said:
Nice..
How about one on AOSP 2.1
Click to expand...
Click to collapse
I'll try to do one if I get time, but I need a fully working ROM as my phone is useful for my life (still waiting for 2.1 stable )
Thanks for your posts all, it will help everybody who want to try the 2.2
(as it is safe and running from SD card, very very very cool idea !)
Help followed your guide get adb shell not a internal command what am i doing wrong been trying this for hours now
I found drawing a pentagram in human blood and chanting a few words can do wonders too.
fastphil said:
Help followed your guide get adb shell not a internal command what am i doing wrong been trying this for hours now
Click to expand...
Click to collapse
root privileges do you have it?
unmount sdcard
OmegaRED^ said:
I found drawing a pentagram in human blood and chanting a few words can do wonders too.
Click to expand...
Click to collapse
sarcasm...love it
rendeiro2005 said:
root privileges do you have it?
unmount sdcard
Click to expand...
Click to collapse
yes mate i do have root access titanium etc works fine just cant get adb shell to run
When i installed 2.2, it rebooted and when to the sony ericsson logo for almost an hour, does this mean i have to reinstall 2.1, and if so, i would i accomplish this
fastphil said:
yes mate i do have root access titanium etc works fine just cant get adb shell to run
Click to expand...
Click to collapse
and what about sdcard?
uncheck nount/unmount
rendeiro2005 said:
and what about sdcard?
uncheck nount/unmount
Click to expand...
Click to collapse
done that too
fastphil said:
done that too
Click to expand...
Click to collapse
can you post a screenshot of cmd?
ok will do
I am still having problems also...
after I type the cmd...
dd if=/sdcard/install of=/data/install && chmod 777 /data/install && /data/install
it just says:
1+1 records in
1+1 records out
520 bytes transferred in 0.003 secs...
#
so, where am I going wrong?
fyi, I am trying to install v001, not the update, and the phone is rooted, busybox is installed. Sorry, but I have tried for a while now and I finally have to just ask for help. Thanks guys.
here pic off cmd
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
fastphil said:
Help followed your guide get adb shell not a internal command what am i doing wrong been trying this for hours now
Click to expand...
Click to collapse
Does it work when your run "adb" command only ?
It looks to me your error is because you're not in the folder where adb.exe is
It is in folder tools, if you try to run it from root directory (where is the android app with nice icon) it won't work for sure
Edit: didn't see your screenshot >> you are NOT in the correct folder !! (so Windows is searching for a registered command which does not exist, I think there's a thread somewhere on how to add it as a registered (I mean global) command)
You must download Android SDK (22mb... Lmao regarding 4gb for iOS ), extract the archive and go in the tools folder. Here is adb.exe.
when i try & run adb exe it does not open it just closes right away
All credits go to pulpoff2 for this! This is not by me, I am merely the messenger. Only thing I did was to ask pulpoff for the files and a tutorial With his permission I will share it with you.
This will provide you with a fresh and unmodified 2.1-system, exactly like you would do the official update - only exception is that it is rooted. So all the apps and games of the official firmware are available and nothing else. You can remove the crap (like the games or timescape for example) by yourself after doing the steps below.
UPDATE:
There is a newer ROM by propc you can use instead of this one. Look here:
http://forum.xda-developers.com/showthread.php?t=888427
-- NEW --
propc kindly provides us with a shellscript to automate the steps below. See here for the script and a short manual:
http://forum.xda-developers.com/showpost.php?p=10067921&postcount=120
If the script doesn't work for you or you prefer to do things the manual way, you may use the steps below.
Download these files:
x8-2.1rooted.img.yaffs.rar
and
ISO-8859-1__unyaffs-arm.rar
Also download the 2.1-firmware from here or here. Unpack it on your computer and delete the "system.sin".
Unpack "x8rooted.img", "busybox" and "unyaffs" to SDcard.
You need 1.6 with root on your phone. By the way, all the data on your phone will be lost after doing the following steps, so making a backup is advised.
Use "adb shell" to connect to your phone and become su:
Code:
su
Copy "busybox" and "unyaffs" to /data/local/tmp. (Pulpoff says you should copy to /sbin, but this requires remounting with busybox. I copied to /sbin, but I think /data/local/tmp should work just fine)
Code:
cd /data/local/tmp
cat /sdcard/busybox > busybox
cat /sdcard/unyaffs > unyaffs
chmod the files to make them executable:
Code:
chmod 755 busybox
chmod 755 unyaffs
EDIT: If you want to copy the files to /sbin (like pulpoff2 advises), you can do this OPTIONAL step:
EDIT2: It was confirmed that this is indeed not necessary!
Remount the root directory to make /sbin writable. Then copy the files over and change the working directory to /sbin:
Code:
[strike]
./busybox mount -o remount,rw /
./busybox cp -prf busybox /sbin/
./busybox cp -prf unyaffs /sbin/
cd /sbin[/strike]
Remount /system as writable:
Code:
mount -o remount,rw /dev/block/mtdblock0 /system
Switch to busybox shell:
Code:
./busybox sh
Remove /system (yes, really!). It's normal to get errors because of the "lost+found"-folders. Ignore the errors.
Code:
./busybox rm -r /system
Unpack pre-rooted image to system. It should output "end of image" if it finishes correctly.
Code:
./unyaffs /sdcard/x8rooted.img /system
Your phone won't boot anymore now and it will crash as soon as you try to use it - that's normal! Go to next step.
Just remove the battery and the usb-cable from the phone, then re-attach the battery. Flash 2.1-kernel (without system.sin !!) using the flasher-tool by Bin4ry. If the flasher gives you an error because of a missing "loader.sin" you can take this file from the 1.6-firmware. Refer to Bin4ry's thread to learn how to use his flasher and how to enter flash-mode on your phone.
The phone should now boot, although the first boot can take a little while. If you get into a boot-loop or you just see the white sony ericsson logo (not the green one after the animation) for several minutes, it probably didn't work and you have to start over again by flashing 1.6.
This was written as I remember how I did it by myself. It worked for me at first try! If it works for you, please click the thanks-button. It will make me feel better
After you have your nice rooted 2.1 you probably want to enable JIT for a nice performance boost.
But does it have root? Bad reading.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
a-k-t-w said:
But does it have root?
Click to expand...
Click to collapse
Absolutely. But no busybox. So if you plan to enable JIT, you have to copy busybox to /system/bin by yourself.
a-k-t-w said:
But does it have root? Bad reading.
Click to expand...
Click to collapse
of course it is rooted.
now we know what to do with unyaffs.
2 things:
1. I've bought the phone with 1.6 android, but I was unable to root it with any method, then I've upgraded to 2.1 update 1. Is there any way to root it?
2. I have Hungarian language. Does it contain Hungarian language?
csengoi said:
2 things:
1. I've bought the phone with 1.6 android, but I was unable to root it with any method, then I've upgraded to 2.1 update 1. Is there any way to root it?
2. I have Hungarian language. Does it contain Hungarian language?
Click to expand...
Click to collapse
1: There is no way to directly root a phone with 2.1. You need to go back to 1.6, root it and then follow the above steps.
2: I guess so. As far as I know the firmware is the same for all countries.
Works like a charm! I removed the /system folder contents one by one though, using the method from the previous thread. Anyway, the first time I tried, unyaffs exited before extracting all the files (maybe the phone ran out of memory?). I didn't notice it and went on to flash the phone, ending up stuck at the Sony Ericsson logo. So, make sure that unyaffs reports that it has reached the "end of image" before moving on to the next step!
Thanks!!
cat /sdcard/busybox > busybox invalid lenght
cat /sdcard/unyaffs > unyaffs invalid lenght
how to proceed?
isaac12 said:
cat /sdcard/busybox > busybox invalid lenght
cat /sdcard/unyaffs > unyaffs invalid lenght
how to proceed?
Click to expand...
Click to collapse
in adb shell:
enter su and you have to look your mobile screen because it will ask you to allow su. (if you rooted well your phone)
i had this problem when i didn't press the allow button in superuser confirmation.
---dobule post--- sorry
trapacska said:
in adb shell:
enter su and you have to look your mobile screen because it will ask you to allow su. (if you rooted well your phone)
i had this problem when i didn't press the allow button in superuser confirmation.
Click to expand...
Click to collapse
rooted phone yes
su confirmed
cd /data/local/tmp
cat /sdcard/busybox > busybox invalid lenght
cat /sdcard/unyaffs > unyaffs invalid lenght
does it mount data.img on sdcard???
or i'll need to use chargemon from previous way?
WARR10r said:
does it mount data.img on sdcard???
or i'll need to use chargemon from previous way?
Click to expand...
Click to collapse
This has nothing to do with App2SD. Also the ROM gets loaded from internal flash, not from sdcard. The result is the same as with the official update, but with root.
If you want to have /data on sdcard, use the modified chargemon or neptun2's method.
I'm totally new to android but somehow i managed to get to number 8, and I have no idea how to switch to busybox shell, can somebody explain this bit in lamens terms please.
gully666uk said:
I'm totally new to android but somehow i managed to get to number 8, and I have no idea how to switch to busybox shell, can somebody explain this bit in lamens terms please.
Click to expand...
Click to collapse
try adding ./ before
gully666uk said:
I'm totally new to android but somehow i managed to get to number 8, and I have no idea how to switch to busybox shell, can somebody explain this bit in lamens terms please.
Click to expand...
Click to collapse
You should still be in "/data/local/tmp" as the working directory (check with "pwd"-command). If you followed the steps correctly, you should have a working busybox-file in there. So just type "busybox sh". If it looks like it does nothing, it's all right
isaac12 said:
rooted phone yes
su confirmed
cd /data/local/tmp
cat /sdcard/busybox > busybox invalid lenght
cat /sdcard/unyaffs > unyaffs invalid lenght
Click to expand...
Click to collapse
try to use another su. i rooted my x8 with superoneclick 1.5.0
I got stuck at SE logo for at least 10mins, it doesnt re-boot cycle although..
Sectoras said:
I got stuck at SE logo for at least 10mins, it doesnt re-boot cycle although..
Click to expand...
Click to collapse
That's way too long, something isn't right there. To start over again you have to flash back to 1.6.
Ok I had not realised the superuser permissions was not popping up on my phone that's sorted now. I get to number 8 again and it said permission denied
Official ICS 4.0.4 (SONY)
On-screen keys for the latest official ICS! -> Download
ICS 4.1.B.0.431 (SONY)
On-screen keys for the latest leaked ICS! -> Download
Polish Blood ICS 4.0.4
Please note: not cwm flashable.
Code:
adb shell mount -o remount,rw /system
adb push framework-res.apk /system/framework/framework-res.apk
adb shell chmod 644 /system/framework/framework-res.apk
adb shell mount -o remount,ro /system
adb reboot
Download
screenshot please
thank you!
great work!
krzemyk1981 said:
screenshot please
Click to expand...
Click to collapse
It takes 26 pt space on the bottom of your screen, other than that, no changes.
Hence your effective screen dimens is 845-26 = 819 x 480 after installing
For new Polish ROM
Polish Blood ICS 4.0.4
Please note: not cwm flashable.
Code:
adb shell mount -o remount,rw /system
adb push framework-res.apk /system/framework/framework-res.apk
adb shell chmod 644 /system/framework/framework-res.apk
adb shell mount -o remount,ro /system
adb reboot
Download
added for official ICS
Tested working on official ICS
Thanks
noob question
how to install
and
how to unstall
max_r said:
noob question
how to install
and
how to unstall
Click to expand...
Click to collapse
1. download
2. Place on sd card
3. rename to framework-res.apk
4. use root explorer to move it to /system
5. long press on it and chose permissions
6. Tick the following boxes
[*][*][-]
[*][-][-]
[*][-][-]
7. use root explorer to move to /system/framework
to uninstall, just keep a cpy of the original framework-res.apk and replace that
gregbradley said:
1. download
2. Place on sd card
3. rename to framework-res.apk
4. use root explorer to move it to /system
5. long press on it and chose permissions
6. Tick the following boxes
[*][*][-]
[*][-][-]
[*][-][-]
7. use root explorer to move to /system/framework
to uninstall, just keep a cpy of the original framework-res.apk and replace that
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
edit :- working on my neo ICS 4.0.4
Thanks working great !!!!!!!!!!!!!
shardul_seth said:
Official ICS 4.0.4 (SONY)
On-screen keys for the latest official ICS! -> Download
ICS 4.1.B.0.431 (SONY)
On-screen keys for the latest leaked ICS! -> Download
Polish Blood ICS 4.0.4
Please note: not cwm flashable.
Code:
adb shell mount -o remount,rw /system
adb push framework-res.apk /system/framework/framework-res.apk
adb shell chmod 644 /system/framework/framework-res.apk
adb shell mount -o remount,ro /system
adb reboot
Download
Click to expand...
Click to collapse
Hey Thanks shardul_seth, working great on my neo v with locked BL 4.0.4,
but my Home Icon have moved up but other four icons are unaffected, so if you have any solution to this will be helpful
jtushar53 said:
Hey Thanks shardul_seth, working great on my neo v with locked BL 4.0.4,
but my Home Icon have moved up but other four icons are unaffected, so if you have any solution to this will be helpful
Click to expand...
Click to collapse
Known bug, no solution. Problem only cosmetic, everything works fine
Ok ,working fine on 4.0.4 stock rom .
If you dont like ADB command stuff ,just download the onscreekeys 4.0.3 zip and replace (just drag and drop) the 4.0.4 framework-res.apk file onto it in the system/framework folder and then install that zip with CWM. It worked for me.
With apex launcher i have no medium Icon issues in the low bar.
Thanks!!!
I had a rooted neo v with bootloader locked with android 4.0.4 4.3.1,which file did i need to download correctly as i had a bootloop after replacing the apk.....
yapkl said:
I had a rooted neo v with bootloader locked with android 4.0.4 4.3.1,which file did i need to download correctly as i had a bootloop after replacing the apk.....
Click to expand...
Click to collapse
first one. Did you set the right permissions for framework-res.apk? the right permissions are rw- r-- r--.
georgeiulian89 said:
first one. Did you set the right permissions for framework-res.apk? the right permissions are rw- r-- r--.
Click to expand...
Click to collapse
i did this according to the post above on the downloaded apk then copy to firmware folder,after that,it restarted itself and bootlooped,what have i done wrong?
[*][*][-]
[*][-][-]
[*][-][-]
yapkl said:
i did this according to the post above on the downloaded apk then copy to firmware folder,after that,it restarted itself and bootlooped,what have i done wrong?
[*][*][-]
[*][-][-]
[*][-][-]
Click to expand...
Click to collapse
During your bootloop, enter recovery, wipe cache and dalvik-cache. and then reboot!
If still no joy, restore framework-res.apk from your backup via adb in recovery!
shardul_seth said:
During your bootloop, enter recovery, wipe cache and dalvik-cache. and then reboot!
If still no joy, restore framework-res.apk from your backup via adb in recovery!
Click to expand...
Click to collapse
Although i just redo the process,i somehow managed to did it ^^ thx!but just a question,can i add or exchange the multitask button to option button or can i change the colour of the buttons?
yapkl said:
Although i just redo the process,i somehow managed to did it ^^ thx!but just a question,can i add or exchange the multitask button to option button or can i change the colour of the buttons?
Click to expand...
Click to collapse
Changing colors is easy, changing order a little bit more complicated..
shardul_seth said:
Changing colors is easy, changing order a little bit more complicated..
Click to expand...
Click to collapse
Great...how to change the colour then?
Hi i have rooted my galaxy tab 10.1 wifi only, after i have installed the ClockworkMod Recovery'
and after the rom [ROM][ICS] JellyBeanRom ICS v5 [P7500][P7510][13.08.2012] - xda-developers.
All seems ok i have superuser and superSu .
I have tried to use some apps for root but dont work any such as Titanium backup root explorer etc
I have update superuser and superSu by play and by flash not resolved .
Root Checker done me this:
Root Access is not properly configured or was not granted.
Super User Applications Status:
Superuser application - version 3.1.3 - is installed!
SuperSU application - version 0.96 - is installed!
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/xbin/su:
Result: /system/xbin/su: No such file or directory
Analysis: File /system/xbin/su does not exist.
Standard Location
Check Command: ls -l /system/bin/su:
Result: lrwxrwxrwx root root 2019-08-31 03:30 su -> ../xbin/su
Analysis: File: su is a symbolic link pointing to another file: ../xbin/su
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Root User ID and Group ID Status:
SU binary not found or not operating properly
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: root user - ro.secure=0
Results provided on your GT-P7510 device
please can you help me?
Try uninstalling one of the two SU apps...you should only need one to my understanding. Then reboot right after.
If that doesn't work you may have to unroot completely and start over.
Hi dear friend...
I had the same problem(likely) with some APPs in ICS...please do the following:
First if you are running ICS,disable(or uninstall) superuser(supersu is sufficient),then open supersu and look at your list of APPs in the first page,if the # mark in front of some APPs are green,then they have root access.if not, tap on them,in the window that appears,in the root access drop down list choose "Grant"...if even this didn't solve the issue please tell us to send you a working root package...
djmatt604 said:
Try uninstalling one of the two SU apps...you should only need one to my understanding. Then reboot right after.
If that doesn't work you may have to unroot completely and start over.
Click to expand...
Click to collapse
I have tried this but is the same!
arashtarafar said:
Hi dear friend...
I had the same problem(likely) with some APPs in ICS...please do the following:
First if you are running ICS,disable(or uninstall) superuser(supersu is sufficient),then open supersu and look at your list of APPs in the first page,if the # mark in front of some APPs are green,then they have root access.if not, tap on them,in the window that appears,in the root access drop down list choose "Grant"...if even this didn't solve the issue please tell us to send you a working root package...
Click to expand...
Click to collapse
Hi tank you for help me i tried this but superSu dont work : exe SU not present and uperSu cant instal this is a problem!
pls any idea?
skyone75 said:
i tried this but superSu dont work : exe SU not present and uperSu cant instal this is a problem!
pls any idea?
Click to expand...
Click to collapse
Yes...you must get su and supersu.I've put it for you in the attachment...
Note that installing superuser or supersu only doesn't mean rooting...
All the credits of this package go to Max Lee from Zedomax...
arashtarafar said:
Yes...you must get su and supersu.I've put it for you in the attachment...
Note that installing superuser or supersu only doesn't mean rooting...
All the credits of this package go to Max Lee from Zedomax...
Click to expand...
Click to collapse
Tank you i tried to install this file now i have Clocworkmod recovery v 5.8.3.1 and result is :
Installing: /sdcard/GalaxytabHacks.com_superuser.zip
Finding update package...
Opening update package...
Installing update....
Install from sdcard complete
but i have the same problem!
You think is better unroot?
It sounds like you've tried everything else. I would back up stuff you need, unroot with stock firmware and start over with just one option. You may choose to skip manually rooting altogether and just flash a rooted ROM. Good luck!
The first time you flash this you must open supersu,a message says that the su binary is outdated,press OK,after some seconds connected to the internet,you see success message,reboot(just optional) znd execute the app you want to gain root access,if it fails(no prompt appeared)don't get disappointed,close the APP,launch supersu,see the # mark in front of the APP's name,tap on it,from the "root access" select "Grant"...
Edit:if you want to flash a ROM then have a look at Jelly Bean ICS in the dev forum...it's ICS and comes with root+many other goodies...
arashtarafar said:
Yes...you must get su and supersu.I've put it for you in the attachment...
Note that installing superuser or supersu only doesn't mean rooting...
All the credits of this package go to Max Lee from Zedomax...
Click to expand...
Click to collapse
arashtarafar said:
The first time you flash this you must open supersu,a message says that the su binary is outdated,press OK,after some seconds connected to the internet,you see success message,reboot(just optional) znd execute the app you want to gain root access,if it fails(no prompt appeared)don't get disappointed,close the APP,launch supersu,see the # mark in front of the APP's name,tap on it,from the "root access" select "Grant"...
Edit:if you want to flash a ROM then have a look at Jelly Bean ICS in the dev forum...it's ICS and comes with root+many other goodies...
Click to expand...
Click to collapse
Ok i try to unroot , need only flash a firmware samsung in download mode with odin?
wich firmware ? hc 3.2 or ics i have tab 7510 wifi only buy in switzerland with italian language
Is there not an Italian ICS? If not try the UK firmware with IT support.
djmatt604 said:
Is there not an Italian ICS? If not try the UK firmware with IT support.
Click to expand...
Click to collapse
But is better honey com 3.2 or ics for unroot?
Tanks
ICS is faster but lacks flash player...but it doesn't harm too much...
arashtarafar said:
ICS is faster but lacks flash player...but it doesn't harm too much...
Click to expand...
Click to collapse
i have unrooted and now i have installed ROM][ICS] JellyBeanRom ICS v5 [P7500][P7510][03.09.2012] v6
Itink the problem was then i caming by Honeycomb:
Instructions (IMPORTANT!):
1. Coming from stock ICS.
If you don't have any recovery then flash it (for example TWRP). Then boot into recovery, make a full wipe and flash my rom.
2. Coming from Honeycomb or any other custom like CM9/CM10/AOKP etc.
First you have to flash stock ICS, regarding which version of the Tab you have (3G/non 3G). Then you have to flash a custom recovery (for example TWRP), boot into it and make a full wipe. Finally flash my rom.
tanks for help bye .
That makes sense. You can run into problems with some ROMs depending on where you're coming from. I ran into problems with ICS ROMs in the beginning because of a bootloader issue...I flashed stock firmware to change my base and built ROMs from there as you're describing in Step 2.
Enjoy!
I have similar problem...
I own a T-Mobile 10.1 Tab, stock ICS... After flashing the stock ICS (i came from CM9) with odin, i flashed the CWM, and the applyed the "root.zip" file...
Booted and I saw that Superuser has been installed.
But I have no root access... The applications return that the root requisitation timed-out...
Anyone knows why? It shoud be quite simple....
Another thread has just been opened in the General area with someone asking the same question. The answers are there, friend...you just have to look for them Here it is again (assuming you are having the same problem and it sounds like you are) - it's because the version of Superuser the root.zip you're using drops into the system is not friends with ICS. Simply update Superuser to 3.1.3. Go Here , download Super 3.1.3-ARM-Signed.zip, drop it on your tablet's root, flash it from recovery and reboot. You should be good after that.
Tab 10.1 ICS flash player 11
arashtarafar said:
ICS is faster but lacks flash player...but it doesn't harm too much...
Click to expand...
Click to collapse
Since the adobe flash player 11 work for tab 10.1 HC 3.2 P7510, and some ICS early device.
adobe system no more certificate and support for ICS 4.0.x device.
So it SHOULD work for my Tab 10.1 P7510 ICS 4.0.4 too. and Yes. It is.
You no longer fine Flash player in Tablet PLAY store once you upgrade to ICS.
but you can find it in PC version PLAY store, then PUSH install from PC to Tablet P7510.
and YES, it work fine for my P7510 with ICS!
https://play.google.com/store/apps/details?id=com.adobe.flashplayer
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
or try download this APK to your tablet to install:
View attachment adobe.flashplayer11.apk
After install , open Flash player setting in your APPs, and setup options, then yoi are ready for any FLAH web object.
even web flash online games.
Disclaimer: I am not responsible for anything that happens to your device.
This requires an unlocked bootloader.
- Stock kernel
- Roots device + installs SuperSU on first boot
- Tested on Rogers Moto X
Download Rogers image: http://d-h.st/cFB
Download ATT image: http://d-h.st/1XI
Rogers kernel version:
3.4.42-xline-gfd1a699-00157-gfb2f8fc
[email protected] #1
Thu Jul 18 20:25:42 CDT 2013
ATT kernel version:
3.4.42-xline-gfd1a699-00158-g8990abb
[email protected] #1
Sat Jul 20 14:29:07 CDT 2013
Install:
reboot to bootloader
fastboot flash boot <image file name>
reboot device
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
rob43 said:
Disclaimer: I am not responsible for anything that happens to your device.
This requires an unlocked bootloader.
- Stock kernel
- Roots device + installs SuperSU on first boot
- Tested on Rogers Moto X
Download: http://d-h.st/btV
Install:
reboot to bootloader
fastboot flash boot ghost-boot.img
reboot device
Click to expand...
Click to collapse
This Is great! Now to apply it to att!
Sent from my MB886 using XDA Premium 4 mobile app
What kernel version is this?
Thanks ! I will wait the version where you don t need to unlock bootloader...
Sent from my XT1058 using XDA Premium 4 mobile app
pixeldrew said:
What kernel version is this?
Click to expand...
Click to collapse
Added to OP
rob43 said:
Added to OP
Click to expand...
Click to collapse
Cheers.
doh... only temporarily booted into the image so it reverted back to secure=1.
All good now.
rob43 said:
Disclaimer: I am not responsible for anything that happens to your device.
This requires an unlocked bootloader.
- Stock kernel
- Roots device + installs SuperSU on first boot
- Tested on Rogers Moto X
Kernel version:
3.4.42-xline-gfd1a699-00157-gfb2f8fc
[email protected] #1
Thu Jul 18 20:25:42 CDT 2013
Download: http://d-h.st/btV
Install:
reboot to bootloader
fastboot flash boot ghost-boot.img
reboot device
Click to expand...
Click to collapse
Correct me if I am wrong, but I thought the Rogers' Moto-X has unlocked bootloader? As in, no unlocking required?
You still have to unlock it via the Motorola website to assert that you voided your warranty.
Sent from my XT1058 using xda app-developers app
pixeldrew said:
You still have to unlock it via the Motorola website to assert that you voided your warranty.
Sent from my XT1058 using xda app-developers app
Click to expand...
Click to collapse
Gotcha. Too bad I went ahead and 'bricked' the device. Fastboot Reason: Flash Failure.
;P
All is well. I had to unlock the bootloader, reflash.
Edit 2: I can't update the SuBinary. It throws a generic error message, stating to contact the developer.
hidea said:
Gotcha. Too bad I went ahead and 'bricked' the device. Fastboot Reason: Flash Failure.
;P
All is well. I had to unlock the bootloader, reflash.
Edit 2: I can't update the SuBinary. It throws a generic error message, stating to contact the developer.
Click to expand...
Click to collapse
I got this as well, you're best off finding the superuser.zip from cyanogenmod's site and installing that by hand via adb.
Code:
[email protected] $ unzip superuser.zip
[email protected] $ adb push superuser/armabi/su /sdcard/
[email protected] $ adb shell
[email protected] $ su
[email protected] # mount -o rw,remount /system
[email protected] # copy /sdcard/su /system/xbin/
pixeldrew said:
You still have to unlock it via the Motorola website to assert that you voided your warranty.
Sent from my XT1058 using xda app-developers app
Click to expand...
Click to collapse
pixeldrew said:
I got this as well, you're best off finding the superuser.zip from cyanogenmod's site and installing that by hand via adb.
Code:
[email protected] $ unzip superuser.zip
[email protected] $ adb push superuser/armabi/su /sdcard/
[email protected] $ adb shell
[email protected] $ su
[email protected] # mount -o rw,remount /system
[email protected] # copy /sdcard/su /system/xbin/
Click to expand...
Click to collapse
Cheers! Any particular Superuser.zip you used?
Cyanogenmod's https://github.com/koush/Superuser
pixeldrew said:
Cyanogenmod's https://github.com/koush/Superuser
Click to expand...
Click to collapse
My wit ends here. I've never used Github. Truth revealed, I'm just a hobbyist!
hidea said:
Cheers! Any particular Superuser.zip you used?
Click to expand...
Click to collapse
The SU binary + Superuser.apk are both from the newest SuperSU (1.51). Where are you seeing the "su requires updating" message? SuperSU is already installed for you.
If you install CM's Superuser, you will get this error. I first tried CM's su + Superuser but the apk was not cooperating.
Nonetheless, you will be able to use su from the terminal and do any update you please. Trying to get CWM recovery working at the moment so this is no longer necessary.
rob43 said:
The SU binary + Superuser.apk are both from the newest SuperSU (1.51). Where are you seeing the "su requires updating" message? SuperSU is already installed for you.
If you install CM's Superuser, you will get this error. I first tried CM's su + Superuser but the apk was not cooperating.
Nonetheless, you will be able to use su from the terminal and do any update you please. Trying to get CWM recovery working at the moment so this is no longer necessary.
Click to expand...
Click to collapse
Cheers, I managed to get Terminal to work. But TIBackup still can't get root access. No popups that I'd normally get with CM/other rooted ROMs.
hidea said:
Cheers, I managed to get Terminal to work. But TIBackup still can't get root access. No popups that I'd normally get with CM/other rooted ROMs.
Click to expand...
Click to collapse
Not sure why that would be. Uninstall CM's Superuser if you downloaded it from the market. Only SuperSU worked for me.
Titanium Backup works without a problem here.
I would suggest deleting both su + Superuser.apk and rebooting, if you modified either in /system. Upon startup, it will reroot your device with the latest SuperSU + su binary.
rob43 said:
Not sure why that would be. Uninstall CM's Superuser if you downloaded it from the market. Only SuperSU worked for me.
Titanium Backup works without a problem here.
Click to expand...
Click to collapse
I never installed CM's Superuser. But I did try installing SuperSU ;P. Do I need to reflash everything again?
hidea said:
I never installed CM's Superuser. But I did try installing SuperSU ;P. Do I need to reflash everything again?
Click to expand...
Click to collapse
Updated my reply above.
rob43 said:
Updated my reply above.
Click to expand...
Click to collapse
Sorry, I'm confused!
After flashing the fastboot image, what do I do? The image came with Superuser pre-installed?