This applies the 9.2.1.21 US ota update. It will install Superuser and the su and busybox binaries; and set ro.secure=0. It does not modify recovery at all.
As usual, flash at your own risk- I didn't test this.
To flash, you need:
a non-stock recovery
a stock system, rooted is OK
custom kernels, deleted system files, modified build.props or audio files will FAIL.
Good luck!
edit: new url! Find it in the OTA section.
http://www.xdafileserver.nl/geeone/
MD5(gee_one-cwm-9.2.1.21-US.zip)= 30bf3ad60698d41793d992823e942076
I made this with Ubuntu!
Thanks to doaist for paving the way! and thanks to Korumera for the server space!
Edit:
It seems like some people will "lose" root in titanium backup because it looks for the su binary in /system/bin instead of /system/xbin (X!). See post 19 and 20 for how to get it back. I don't use titanium backup very often, so I'm not familiar with it.
I get a status 7 installation aborted error when trying to flash on the stock rom thats rooted no mods.
Thanks
Worked fine on my TF101 US....
Hope it fixes some of the battery issues I've been seeing with .17
Hmmmm.............strange it didnt for me and Im on the stock ICS rom ver .17 currently.
I'm not sure what status 7 is. How much free space do you have? I don't remember the number but the patch does check free space before flashing.
sent while running with scissors
Ive got 20gigs of free space Im using Rogue Recovery............not sure if that makes a difference.......
20 gbs on the sdcard? I think it checks internal memory, or maybe you have a 32gb transformer?
sent while running with scissors
Error Im getting:
Verifying current system....
assert failed: apply_patch_check("/system/lib/modules/battery_rvsd.ko", "66c516b01d95c36310cc3e7ee7771b32ed5cb823",
E: Error in/sdcard/gee_one-cwm-9.2.1.21-US_30bf3ad606.zip
(Status 7)
Installation aborted.
---------- Post added at 04:00 PM ---------- Previous post was at 03:59 PM ----------
Ive got a 32gb transformer with a 32gb microsd card.
For whatever reason, your battery kernel module is different? Maybe you changed it while sleeping or maybe the 32gb version uses a different one.
The US firmware is available on the asus site, so you could just download it, extract the offending file, and push it to your transformer. It will be the 92121 version, but the updater will just skip it since it matches the target.
sent while running with scissors
Could it be because Im not using a stock kernel?
y2kardell said:
Could it be because Im not using a stock kernel?
Click to expand...
Click to collapse
Bingo- see the note about FAIL in the first post. You'll want to flash back to a stock kernel to apply the update, or more likely, just flash a full custom rom and a new modded kernel.
sent from my transformer
I no longer have root after I flashed this.
Any suggestions?
kdog78 said:
I no longer have root after I flashed this.
Any suggestions?
Click to expand...
Click to collapse
are you sure you flashed my version and not the other one?
type in "ls -l /system/xbin/su" and "getprop ro.secure" in the terminal and see what pops up.
Ok, I tested this on my TF and it works for me, your experience may differ.
Try updating Superuser and the su binary in superuser. Maybe I have an updated version on /data/app?
sent from my transformer
I flashed this and after I click reboot system now it just gets stuck at CWM.
I'm using CWM v3.2.0.1 by roach2010
Tried clearing cache, it still gets stuck in CWM. Help?
wzseow said:
I flashed this and after I click reboot system now it just gets stuck at CWM.
I'm using CWM v3.2.0.1 by roach2010
Tried clearing cache, it still gets stuck in CWM. Help?
Click to expand...
Click to collapse
That is a recovery issue - there is a trouble shooting thread in the dev section.
sent from my transformer
gee one said:
are you sure you flashed my version and not the other one?
type in "ls -l /system/xbin/su" and "getprop ro.secure" in the terminal and see what pops up.
Click to expand...
Click to collapse
It had a 0.
Sent from my Transformer TF101 using Tapatalk 2
can anyone advice on how to get this to flash on a system with a custom kernel? i can't seem to get it to flash with error 7
Sent from my Transformer TF101 using Tapatalk 2
kdog78 said:
It had a 0.
Sent from my Transformer TF101 using Tapatalk 2
Click to expand...
Click to collapse
Sorry to answer your earlier question, yes I used yours. I didn't know there was another. Here are two screen shots.
Sent from my Transformer TF101 using Tapatalk 2
It looks like you have 2 su binaries, and the one ti backup is looking for isn't superuser executable.
Try ls -l /system/*bin/su and this time use the -l flag to check the permissions. The bin/su will be normal, but the xbin one should be rws....
Try this in terminal
/system/xbin/su
mount -o remount,rw /system
chmod 06755 /system/bin/su
mount -o remount,ro /system
Exit...exit...
Then try getting root in tibu. I don't use it, so I'm not terrible familiar. You might also try updating the su binary via superuser apk.
sent while running with scissors
Related
is there a way to install busyboxy with ClockWorkMod recovery?
Well most roms have a version of it what rom are you running?
Sent from my SPH-D700 using XDA App
no need to install busybox unless your on an older rom/kernel, but for whatever reason you need to there is one in the market
I am running the epic experience v1.2.06 and i have tried the one on the market and it always comes up fails
Try downloading titanium backup and go to the problems section and it will install busybox.
sent from the epic
tried that and it failed
Well I looked and the ee rom has busybox and just wondering what do you need it for?
sent from the epic
Metamorph keeps telling me I need to install it but the installer tells me its installed :-( what location shuld I pick?
HI
Can some one explain what is busy box thank you very much
luvjones305 said:
Can some one explain what is busy box thank you very much
Click to expand...
Click to collapse
Search bar! Use it!
Also, in before moved to General.
igotsthemagicinme said:
Metamorph keeps telling me I need to install it but the installer tells me its installed :-( what location shuld I pick?
Click to expand...
Click to collapse
Maybe it's already installed. Most of the ROMs have it already built in.
igotsthemagicinme said:
Metamorph keeps telling me I need to install it but the installer tells me its installed :-( what location shuld I pick?
Click to expand...
Click to collapse
you need to adb shell or run a terminal on your handset and create a link where metamorph is expecting to find busybox (or simply copy the binary)
i.e.,:
$su
#ln -s /sbin/busybox /system/bin/busybox
- or -
$su
#cp /sbin/busybox /system/bin/busybox
linking saves you the trouble of version mismatching, but some people seem to have issues with it.
3/14. I had to do a complete reset after a botched install of Revolver
I really want to get back to the PRIME ROM I had running before I messed up.
On Sunday, I did a one click root, then installed CWM and then the PRIME ROM ( wished I would have left well enough alone.)
Now I can't even get this Tablet to root ( TF101). ( Razorclaw)
I updated to 4.0.3 yesterday. Could that be the issue? If so, any suggestions on how I get back to the Prime ROM, CWM and root.
Thanks in advance, and please feel free to kick the sh!t out of this noob.
ViperMod will root ICS on both TF101 and Prime.
I just tried vipermod today and it won't work . I'm using Ubuntu and at every line in the script it says " cannot stat no such file or directory
Sent from my Transformer TF101 using xda premium
Sounds like it might be path errors. ViperMod is only a batchfile of ADB commands. You should be able to open up the batchfile and manually type and run the pertinent commands at a prompt if you have to, changing path and filenames where necessary.
You need to
chmod +x adb
Also remember to ensure adb can see your device. Use
adb devices
If your device is not seen, you need to add a udev rule in /etc/udev/rules.d/
Krish.Nagarajan said:
You need to
chmod +x adb
Also remember to ensure adb can see your device. Use
adb devices
If your device is not seen, you need to add a udev rule in /etc/udev/rules.d/
Click to expand...
Click to collapse
I did that and it does see the tf. But once I am in the path where my adb resides then I do sudo sh primetime.sh I still get all those errors.
Do I need to chmod the adb file that's residing in the PrimeTime folder as well?
I did add the rules to the 99-android.rules also
Sent from my SGH-T959 using xda premium
Hey E, I sent you a PM for a possible solution.
Woodrube said:
Hey E, I sent you a PM for a possible solution.
Click to expand...
Click to collapse
Got it man. I'm rooted now. :-D my issue was using wrong command in terminal.
Sent from my Transformer TF101 using xda premium
Here is a dump of my /system/app and /system/framework that is deodexed/zipaligned. Its just the directories; its not flashable in CWM. I'll try and put together a stock zip later, but I don't have time at work. If someone else wants to do it, feel free to PM me a link and I'll host it.
For now, developers will know how to use this. In addition, if you feel brave, you can use the following steps:
Prework:
Download the zip. Extract it. Copy the deodex_app and deodex_framework directories to your external SD card.
1) Boot your phone into recovery
2) Mount /system and /sdcard from the mount menu
3) adb shell rm /system/app/*.odex
4) adb shell rm /system/framework/*.odex
5) adb shell cp /sdcard/deodex_app/* /system/app/
6) adb shell cp /sdcard/deodex_framework/* /system/framework/
7) adb shell chmod 644 /system/app/*
8) adb shell chmod 644 /system/framework/*
9) Wipe Dalvik cache from the advanced menu
10) Make sure /system, /data, and /sdcard are unmounted in the mounts menu
11) Reboot. It took about 5 minutes for my phone to boot and then it said "Upgrading Android" or something like that and went through 175 apps or so.
Download here.
ROM developers, feel free to use this to base your ROMs on. Please give credit for the base source of your ROM as always.
Edit: Clarified its also zipaligned.
Awesome!! I wish I was brave enough to try this..
So rom does this mean you'll be whippin up a kernel?? : ))))))
Sent from my SAMSUNG-SGH-I727 using xda premium
pingfl00d said:
So rom does this mean you'll be whippin up a kernel?? : ))))))
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
I need the source which is not available yet. I suspect it will be shortly after this is OTA'ed. But yes, once it is, I will be updating my stock-ish
Procedure works perfectly.
At "Android is upgrading... " message now
Edit: Home button dead.
rjohnstone said:
Procedure works perfectly.
At "Android is upgrading... " message now
Edit: Home button dead.
Click to expand...
Click to collapse
My home button works fine. This seems to be a common problem if you restore with TiBu. Did you do that?
romracer said:
My home button works fine. This seems to be a common problem if you restore with TiBu. Did you do that?
Click to expand...
Click to collapse
Only user apps, no system data.
And the button worked prior to replacing files, so I'm curious what was deleted/changed that caused the button to stop working?
rjohnstone said:
Only user apps, no system data.
And the button worked prior to replacing files, so I'm curious what was deleted/changed that caused the button to stop working?
Click to expand...
Click to collapse
My guess would be something that "Android is updating..." did. I'm still not entirely sure what that is doing.
romracer said:
My guess would be something that "Android is updating..." did. I'm still not entirely sure what that is doing.
Click to expand...
Click to collapse
Most likely... no biggie.
Factory reset should take care of it.
Worst case, I have a nandroid backup.
Edit: factory reset didn't fix it... time for a restore.
I will try and add this too a zip. Thank you
EDIT:
I added this to my ROM. I am still working on ironing out all of the issues, but this helped!
http://forum.xda-developers.com/showthread.php?t=1566820
And if you want to mirror that would be amazing.
that actually worked perfectly! although you should probably add in there that people can use emmc instead of sdcard if they dont have an external card (i dont).
Thanks for this.
Sent from my SAMSUNG-SGH-I727 using xda premium
thanks
I waiting for .Zip flasheable
if you don't mind me asking, how did you come across deodexing this rom? I know others were having troubles doing so. Also how did you zipalign it? I zipaligned my leak by using rom toolbox pro, did you use the kitchen?!?!
Thanks romracer, always run into issues with the kitchen. I'm going to try your classpath includes in a sh script and see if it works where the kitchen hadn't.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2 Beta-4
mjwhirly said:
if you don't mind me asking, how did you come across deodexing this rom? I know others were having troubles doing so. Also how did you zipalign it? I zipaligned my leak by using rom toolbox pro, did you use the kitchen?!?!
Click to expand...
Click to collapse
I do most of it by hand. I'm a Linux/Windows System Administrator by day, so I'm comfortable with the command line I do use Cygwin for just about everything though rather than the Command Prompt.
promiseofcake said:
Thanks romracer, always run into issues with the kitchen. I'm going to try your classpath includes in a sh script and see if it works where the kitchen hadn't.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2 Beta-4
Click to expand...
Click to collapse
The one liner I pasted in the other thread should work for both app and framework. It has more includes in the class path than are necessary for framework, but I don't think it'll break it.
It assumes the following:
You are in a directory with app, framework, deodex_app, deodex_framework and tmp subdirectories. app and framework contain the originals from the phone. The one liner should be run from this top level directory. I'd recommend doing framework first. You'll also need to Google java.awt.jar and put it in the framework directory too. Don't upload this to your phone though, its just needed for deodex'ing.
finally abit stable with these deodexed files
flash ics leak through odin
boot into android and get past the attready2go
flash cwm through odin
copy your deodexed files to sd and boot into cwm
follow your adb commands to copy and replace
reboot
only problems were superuser being a pain to flash in cwm. someone else mentioned toggle signature verification which is just before choosing your zip to install in cwm. looks good now.
mjwhirly said:
if you don't mind me asking, how did you come across deodexing this rom? I know others were having troubles doing so. Also how did you zipalign it? I zipaligned my leak by using rom toolbox pro, did you use the kitchen?!?!
Click to expand...
Click to collapse
i think the problem most people are having isnt related to the deodexing (anymore) but trying to flash it in CWM. it seems that flashable zips are messing up everything, as i used the same files i tried flashing in a zip this way and it works now. the zip version was unusable.
quikt said:
finally abit stable with these deodexed files
flash ics leak through odin
boot into android and get past the attready2go
flash cwm through odin
copy your deodexed files to sd and boot into cwm
follow your adb commands to copy and replace
reboot
only problems were superuser being a pain to flash in cwm. someone else mentioned toggle signature verification which is just before choosing your zip to install in cwm. looks good now.
Click to expand...
Click to collapse
That's basically exactly what I did (and my phone seems stable). Thanks for typing out the parts I left out
I've always had to flash the Superuser zip twice for some reason. I just flash it twice right on top of each other (without rebooting, exiting CWM, etc). Never have any problems in the actual OS doing it that way.
Grab the official Superuser zip from goo-inside.me/superuser
Is there already a method on the root 9.2.2.3 ?
aga37 said:
Is there already a method on the root 9.2.2.3 ?
Click to expand...
Click to collapse
Perhaps downgrade your ROM to an earlier version. Someone has done it with HC.
http://forum.xda-developers.com/showthread.php?t=1400532
[Edit] Ignore me. Apparently you cannot go back to a lower version number.
Bump
aga37 said:
Is there already a method on the root 9.2.2.3 ?
Click to expand...
Click to collapse
aga37 said:
Is there already a method on the root 9.2.2.3 ?
Click to expand...
Click to collapse
have you tried this
http://forum.xda-developers.com/showthread.php?t=1515470
TNS201 said:
have you tried this
http://forum.xda-developers.com/showthread.php?t=1515470
Click to expand...
Click to collapse
It has been patched up with this update
wolf849 said:
It has been patched up with this update
Click to expand...
Click to collapse
confirmed
if you have a B50 or B60 TF101 you can try my way. this will restore it back to 9.2.1.11 and then OTA 9.2.3.3
http://forum.xda-developers.com/showthread.php?t=1524302
chadster214 said:
if you have a B50 or B60 TF101 you can try my way. this will restore it back to 9.2.1.11 and then OTA 9.2.3.3
http://forum.xda-developers.com/showthread.php?t=1524302
Click to expand...
Click to collapse
Problem is that 9.2.2.3 update came for tf101g and that means SBK3 device, therefore root by nvflash will not make the trick...
P.S. As far as we are talking about 3g devices
Is it possible to flash recovery.img on device via adb ? (Fastboot) Then boot into CWM and flash a rooted rom ?
Sent from my GT-I9100 using XDA
Nick502 said:
Is it possible to flash recovery.img on device via adb ? (Fastboot)
Click to expand...
Click to collapse
The bootloader does support the fastboot protocol (and some obscure methods of booting a kernel via JTAG), but it's locked down to the point that you can't even get fastboot to recognize the device.
So no luck there
ViperMod is your answer I believe
I've not had to root since any version of ICS, but many are have success with ViperMod: http://forum.xda-developers.com/showthread.php?p=21009605
You might have to drop back to a 9.2.2.17 or 19 but there are lots of roms out there that are still on that version. I would give it a try on the 9.2.2.3 though, my guess would be it will work. cheers.
chadcspencer said:
I would give it a try on the 9.2.2.3 though, my guess would be it will work. cheers.
Click to expand...
Click to collapse
It doesn't work
I tried with my TFT101G build 9.2.2.3 but didn't work!
OK, so to sum it up:
1. SUID /proc/<pid>/mem write has been patched in this release (aka 9.2.2.3) therefore mempodroid exploit and basing on it viperMod is useless
2. qEmu vulnerability in /data/local.prop is also patched up so TPsparkyroot will also fail.
3. The location of backed up files and temp storage have been shifted out from data therefore all rooting tools connected with ASUS backup app will not do the trick.
4. Jumping back to previous software is unachievable without root.
So I ask you to post ONLY methods that are not listed above.
(However I think that we have to wait for next linux Local Privilage Escalation bug to be discovered in order to get rooted)
Cheers
P.S. Sorry for any mistakes English is not my native.
ICS 9.9.23G
I have a question is 9.2.23 ics available for all transformers? When I got my update it was 9.2.17. Then I used vipermod to root and voodoo root keeper.do I need to temp unroot to receive this update?
thunderman98 said:
I have a question is 9.2.23 ics available for all transformers? When I got my update it was 9.2.17. Then I used vipermod to root and voodoo root keeper.do I need to temp unroot to receive this update?
Click to expand...
Click to collapse
OTA is only for TF101G. You can install firmware pack from ASUS website through custom recovery, but I do not see any point of doing that.
Any news ? Anyone succeeded in rooting 9.2.2.3??????
Thanks in advance
hearts king101 said:
Any news ? Anyone succeeded in rooting 9.2.2.3??????
Thanks in advance
Click to expand...
Click to collapse
Nope, I've only achieved /data and /cache readwrite access but nothing more Unless you know any thing that can be done in that situation.
wolf849 said:
Nope, I've only achieved /data and /cache readwrite access but nothing more Unless you know any thing that can be done in that situation.
Click to expand...
Click to collapse
If you can write to arbitrary locations on /data try dropping a /data/local.prop with 'ro.kernel.qemu=1' inside (without quotes), reboot and then issue "id" through adb shell to check if adb is running as root.
If it works, ViperMod can be adapted almost painlessly to push su, Superuser.apk and busybox with the correct permission bits
sbiriguda said:
If you can write to arbitrary locations on /data try dropping a /data/local.prop with 'ro.kernel.qemu=1' inside (without quotes), reboot and then issue "id" through adb shell to check if adb is running as root.
If it works, ViperMod can be adapted almost painlessly to push su, Superuser.apk and busybox with the correct permission bits
Click to expand...
Click to collapse
Unfortunately I've tried that and than I came to a conclusion that 'ro.kernel.qemu=' has been shifted... Try read build.prop on /system and you will find it there, so /data write does nothing for now
EDIT:
Nonetheless, I have rw access to /cache where dlpkgfile is held, so maybe it is possible to do a downgrade of firmware through that hole.
EDIT2:
BTW, I did it by flashing TW 9.2.2.3 firmware on to WW 9.2.2.3 through EP101_SDUPDATE (or similar).
Than:
adb mv /data/local/tmp /data/local/tmp.bak
adb shell ln -s /cache /data/local/tmp
adb rebbot
After that /data becomes readwrite
EDIT3:
There is also one more question: where is held /tmp partition needed to repack the blob maybe by accessing it and pushing blob we can manually force its update.
For some reason I am not able to install any custom ROM's with TWRP 2.3.3 I transfer the files across to the root directory of my internal storage using ADB pusher but whenever I try and install a ROM I seem to get this error message
E:Mount: Unable to find partition for path '/[email protected]_Edition_V02.zip'
Error flashing zip '/[email protected]_Edition_V02.zip'
Updating partition details..
Click to expand...
Click to collapse
Does anyone have any idea as to why this is happening, and how I can get around it?
I currently dont have a ROM installed on my TF300 due to me being an idiot, but I can use ADB, TWRP and fastboot so I should be able to sort this out.
Nekrom4n said:
For some reason I am not able to install any custom ROM's with TWRP 2.3.3 I transfer the files across to the root directory of my internal storage using ADB pusher but whenever I try and install a ROM I seem to get this error message
Does anyone have any idea as to why this is happening, and how I can get around it?
I currently dont have a ROM installed on my TF300 due to me being an idiot, but I can use ADB, TWRP and fastboot so I should be able to sort this out.
Click to expand...
Click to collapse
I can not remember,
Is the update a complete rom ??
If not,then install OC V.3 instead..
Nekrom4n said:
For some reason I am not able to install any custom ROM's with TWRP 2.3.3 I transfer the files across to the root directory of my internal storage using ADB pusher but whenever I try and install a ROM I seem to get this error message
Does anyone have any idea as to why this is happening, and how I can get around it?
I currently dont have a ROM installed on my TF300 due to me being an idiot, but I can use ADB, TWRP and fastboot so I should be able to sort this out.
Click to expand...
Click to collapse
Try Clockwork, this 4.2 is weird. I can do a backup in TWRP, but it cannot find what I placed on the sd card, so I have to use Clockwork for some reason....
Managed to sort it. For some reason TWRP didn't like installing from root, and changed to a sub directory and it works fine now. Installed paranoid android in the end
Sent from my Transformer Pad TF300T using XDA Premium HD app
same issue
i have the same proble only im stalling from /mnt/sdcard not from root.
On htc one s3..........
have been withoutmy droid for weeks!
samo problem
I have the same issue but when i put the ROM in a folder it does not work.
I have a goophone i5 and i wiped my system have no OS on it only TWRP.
I need to install a new recovery can anyone help me i am a noob for this !
Thank you
What command are any of you using to push the file??
Thx Josh
problem
lj50036 said:
What command are any of you using to push the file??
Thx Josh
Click to expand...
Click to collapse
i am trying to install a rom from the TWRP recovery .
i uploaded the file on the external SD card .
Nekrom4n said:
Managed to sort it. For some reason TWRP didn't like installing from root, and changed to a sub directory and it works fine now. Installed paranoid android in the end
Sent from my Transformer Pad TF300T using XDA Premium HD app
Click to expand...
Click to collapse
Thanks! As soon as I put the zips (PA4.4 + gapps) into my sdcard folder my nexus 7 was able to install w/ out fail.
Nekrom4n said:
Managed to sort it. For some reason TWRP didn't like installing from root, and changed to a sub directory and it works fine now. Installed paranoid android in the end
Sent from my Transformer Pad TF300T using XDA Premium HD app
Click to expand...
Click to collapse
How did you changed to your root directory to sub directory