[Q] unrevoked worked but phone still not rooted? - Desire Q&A, Help & Troubleshooting

It took me 4 hours to get unrevoked root my phone (turned out that the actual version is buggy) but somehow it seems not "really" rooted.
I want to install titanium backup, so when I start it I get this popup to grant root access but titanium still says it is not ok.
I can do a "su" in the shell but not a whoami. - I don't understand why.
If I go into the recovery menu it says ClockworkMod Recovery v.3.0.0.5
Bravo PVT1 SHIP S-ON
HBOOT 0.93.0001
Microp-031d
Radio-5.10.05.23

If you bothered to check the Titanium website you'd see you need to click the 'Problems' box to install BusyBox. Without this TB won't work
http://matrixrewriter.com/wiki/tiki-index.php?page=TB+-+User's+guide

EddyOS said:
If you bothered to check the Titanium website you'd see you need to click the 'Problems' box to install BusyBox. Without this TB won't work
http://matrixrewriter.com/wiki/tiki-index.php?page=TB+-+User's+guide
Click to expand...
Click to collapse
It even says on first Titanium Backup launch!

Yep...pops up a message. Click "Problems?" at the bottom for a reliable busybox.

Believe me I bothered a lot to look around and I tried for hours and hours.
Titanium complained about not having root privileges not about busybox. And in the help on their homepage there was this guide "how to check if your phone is rooted properly" by issuing the su command followed by whoami which is obviously misleading.
However, thank you for pointing me in the right direction. It seems to work now.

OK. Now I am convinced - this was completely not my fault. Not only is the documentation missleading, the software is buggy as well.
Going to the Problems? Menu suggests it would fix your issues with busybox by installing it and such...
Well, it does download it to your device but it is not usable until you install it manually via the android sdk in recovery mode. Until then you will not get an app listing. I wonder where to find this little detail in the docu (talking about laziness)

No one else seems to have this issue so not sure what you're doing differently
I just went to running a custom ROM so once rooted didn't have any issues

When you flash your phone with unrEVOked, try using Clockwork 2.5.0.7 as I used this version and it worked 1st time.

SOLVED
Thanks guys. I already solved all problems. It was horribly difficult to get over all these pit falls but finally I reached my goal (a Titanium Backup).
What caused me most trouble was the unclear description of Titanium Backup, especially the part in which they state "if whoami does not respond so and so you are not root"... BULL****!!!
"Short" list of how I got my Desire with HBOOT 0.98 rooted and installed Titanium Backup:
Unrevoked root, but not the latest version 3.32. This one will stop with an Error: Cannot get root. Is your firmware too new? or something similar. Instead use version 3.2
Install Titanium and start it. Superuser will popup and ask for permissions - grant.
Make the changes in the application settings that Titanium asks for (I think usb debugging and allow applications that are not from market) and forget about the message telling you you have no sufficient root privileges, that is not true - I guess what they really mean is that busybox is not installed on your system (would be nice if they'd said what they mean).
Go to the "Problems?" button and let Titanium install Busybox.
... not over yet!
Titanium will now not complain about root privileges any longer but you will still not see any application listings in the software. So maybe there is still something wrong. But what could that be? The root priviliges? WRONG!. Titanium downloaded busybox but did not bother to also install it, although it said it did ;-)
Get the android SDK from Google and install it. (you will also need the Java JDK). You can uncheck most of the packages during installation, probably all. We are only interested in the adb tool that is included in the base installation (I think it is, I also installed the Android SDK Platform tools, SDK Tools and SDK Platform Android 2.2 - just because I was not sure about it).
Boot phone into recovery and connect with the adb shell. (this is a little tool that you will find in the tools subdirectory in the android sdk. You need to start it from the command prompt)
Once connected you need to install busybox manually. Titanium did download the data but did not install! How to do this is described by Loccy here:
Code:
Actually, what I did was use Titanium's busybox:
* install Titanium
* run Titanium
* click the "problems" button and install Busybox
* boot into recovery
* adb shell from my Mac
* mount /system
* cp /data/data/com.keramidas.TitaniumBackup/files/busybox /system/bin
* cd /system/bin
* ./busybox --install -s .
Instead of using the mount commands, listed above I mounted the mentioned directories with the mount option in the ClockworkMod recovery menu, that comes with the unrevoked rooting, because the mount commands did not work properly for me. Also, I had to cd into the /data/data/com.keramidas.TitaniumBackup/files/busybox directory and copy busybox to /system/bin/. from there.
Code:
cd /data/data/com.keramidas.TitaniumBackup/files
cp busybox /system/bin/.
cd /system/bin
./busybox --install -s .
But I might have had a typo.
reboot the device and enjoy.
I should mention, if you NOW issue the suggested "su" and "whoami" commands in a shell that according to Titaniums super HOWTO should tell you if you have root privileges, THEN you will get the right response.
In Conclusion:
Forget about the Titanium howto. If Unrevoked finished with no error you HAVE root privileges, no matter what Titanium tells you. Another indicator: If the superuser popup appears, you should be rooted as well.
Install Busybox either completely manually or with the above described method via Titanium. The busybox setup has worked if you can issue the "su" and "whoami" command in a shell.
@EddyOS: "Noone" might not be entirely true - If Titanium was so clear you would not find tons of "how do I install it" questions in the forum. If it works on some *or most* devices but on others not, this is just an indication for sloppy coding. And a user should not have to spend hours over hours to surf some forums for solutions that should have been provided by the developers in the first place. Some people have a life...

Related

[Q] Concern before continuing install of custom ROM....

Alrighty..... I've read / had open the posts regarding ADB, Unrooting, Nandroid, etc multiple times, and I want to make sure things are OK / voice some concerns before I continue.
I've installed the USB drivers needed (installed those only, did NOT install the rest of the components).
Ran SDK setup, edited the android_winusb.inf (have original as .bak)
Had USB Debugging enabled
Confirmed Android Phone listed in Dev. Manager as Android Bootloader Interface
Ran UnrEVOked3 reflash tool, without difficulty, and phone finished in koush clockworkmod recovery, and rebooted.
Used Nandroid Backup to backup to SD card, later confirmed via exploring SD card for confirmation with observing clockworkmod folder. Afterwards, reset back to "Charge Only"
At this point, I wanted to confirm root, and using ADB shell in command prompt typed in at $ su and was rewarded with the response of su / Permission denied / $.
A bit concerned, I rebooted the phone, everything works (well, I don't directly observe any issues, can make / receive calls, texts, etc).
Under "Software Information" I see:
Firmware Version: 2.1-update!
Baseband version: 1.00.03.04.06
I'm very much aware that I need to update the radio, plan on using unrEVOked Forever. I have the option to use Clockworkmod "apply sdcard:update.zip" next.
I'm wanting to make sure things are "OK" and the phone is sucessfully "rooted" before I carry on.
I have no doubt this is the "umteenth" thread, but it's my first "smartphone", and my first time doing this, so please be gentle, it really is my first time
Thanks for any time on this, and posted responses.
If you got permission denied when running su in adb shell the your root didnt go correctly. It should of just dropped you to a # prompt. When you typed su did you then go to your phone and get the popup by superuser asking if you allow or deny? Did you select allow?
while in adb and typing su it should look like this
Code:
$su
#
I never got the option, or I didn't see it. ::Confirmed::, I still get the $ after typing in su
Another question: Should I install the packages listed in the SDK update as well? I have 2.2, API 8, revision 2, 2.1-update1, API 7, revision 2, and 1.6 listed, and 2.1-update1 is listed as my latest firmware
**Update** Via unrevoked.com/rootwiki/doku.php?id=public:adb_in_recovery, I see device listed with (recovery) next to it. I presume with the 3 files listed to download, I place them in the root of my SD card?
I think that $ is normal on the stock rom with the phone booted up. Your nand is still locked because you haven't done the unrevoked forever, yet. Boot into recovery and do it and you should get the # root prompt. Sounds like you're on the right track.
Typed on my Incredible phone!
Last question (I think)....
I'm assuming that I rename unrevoked-forever.zip to update.zip, and thats the file that I place in the in the root of my SD card, reboot into recovery and select apply update?
#
The update can be installed like any custom .zip file. Simply flash it from your custom recovery. Both Amon_RA and Clockworkmod Recoveries support custom .zip installs from the sdcard.
#
Either select the option to install a .zip from your SD card, or apply it as an update.zip as follows:
#
Place the update.zip file into the root of your SD card. You can do this with adb with the command: adb push unrevoked-forever.zip /sdcard/update.zip
I have a feeling I'm misunderstanding some part of that, but I want to make sure before I finalize this.
Does this look good for a final step?
***Update****
Applied Forever Patch, no issues what so ever. Phone loads back to previous states, now I get the # after su request in shell.
I"m still seeing a Baseband Version of: 1.0.03.04.06. The next step is to update the radio, then off to a custom ROM of my choice?
HyperTension said:
***Update****
Applied Forever Patch, no issues what so ever. Phone loads back to previous states, now I get the # after su request in shell.
I"m still seeing a Baseband Version of: 1.0.03.04.06. The next step is to update the radio, then off to a custom ROM of my choice?
Click to expand...
Click to collapse
Correct. Be sure to do a nandroid before you do each thing. I know it sounds silly and like a lot of backing up, but you'll be glad you've got it if something goes wrong. You can almost always get back to good with a nandroid backup.
Isnt that the truth
Takes 5 minutes to backup, and 5 seconds to break lol. NANDROID
I have not had a chance to flash the radio / install a custom ROM, but everything works!
Big thanks for the support / guidance through this!
Next question, obviously asked in several previous threads, but I'm unable to resolve the next issue at hand with that data.
When I power on, and hit hboot, I'm still seeing S-On, yet if I log into abb shell, su, I get "#", as well as now having the icon for "Superuser Permissions".
I've attempted to install the radio update "PB31IMG.zip" via root of SD card. I'm able to see / install it, yet baseband is still showing 1.00.03.04.06.
I have W7, and have the option to "Hide extensions for known file types" off (Can't stand not seeing exactly what files are what).
What am I missing? I've seen that others have had to do the "*22899 then *228 option 2", yet If it doesn't show it as being a valid install, I'm hesitant to try and reinstall it
****Edit**** If this is the case, then I will wear the obligitory "dunce" cap for a bit.... Do I need to rename PB31... to update, the port over to root of SD and install then select "apply sdcard:update.zip"?

Getting Started [Update 12/23 - OTA Update Install fix for root]

[Update 12/23] For those of you unable to install the new system update, I've found a solution -- scroll down to the update! I AM NOT RESPONSIBLE FOR ANY DAMAGES THAT MAY OCCUR!
So I figured I'd at least get things started - Credit goes to whomever first tried z4root on their Droid Pro - and to mahst687 for the deodexing.
Lets Begin!
Resources:
Motorola ADB Driver
Android SDK
xUltimate V2.2.2
(Can't post links apparently, sorry -- googles your friend!)
#1 Root:
As seen on numerous android sites already, root is obtainable via z4root in the market. It may not work the first, second, or even third time -- just keep trying, it works I promise.
#2 Bootstrap and Clockwork Recovery
Download and install 'Rom Manager' from the Market. Once installed flash the Droid2 Clockwork Recovery. After flashing, obtain the Droid2 Bootstrapper and install it. Confirm Clockwork Recovery works by booting to recovery via Bootstrap.
#2 Deodex:
Download Android SDK for ADB, as well as the Motorola ADB Drivers posted above. Second, download xUltimate - also posted above. Once everything is downloaded and installed we're ready to begin.
1. Run Main in the xUltimate package - if the ADB drivers installed successfully you should be greeted with a menu containing several options - great!
2. Next run option 1.
3. Run option 2.
3. Run option 3 - sit back and relax for a bit
4. Once option 3 is done doing its thing, navigate to the xUltimate folder, more specifically the "origi_frame", and delete guava.odex
5. Run option 4 - it'll be a short wait
6. Exit the xUltimate
7. Enable USB Mass Storage on the phone and transfer both "done_app", and "done_frame" to the ROOT of the SD card.
8. Once both folders have transferred disable USB Storage, but keep the phone plugged in via USB.
9. Open up a command prompt and browse to the android SDK Tools folder (or where ever your ADB executable is located).
10. Enter the following commands:
Code:
adb shell
su
stop
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/done_app/* /system/app/
cp /sdcard/done_frame/* /system/framework/
rm /system/app/*.odex
rm /system/framework/*.odex
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
11. If all went well your phone should reboot - which may take a few minutes. Enjoy!
[Update]12/23/2010
For those of you unable to get the new Droid Pro OTA working I have found a solution! You will need:
1)Root
2)Clockwork Recovery
3)System.img from update
4)Current Nandroid backup of your phone
5)ADB drivers and ASDK
So lets begin.
1)Boot into Clockwork recovery and create a backup of your phone.
2)Once complete, mount the phone as USB storage and pull the system.img file from the nandroid backup folder, as well as the nandroid.md5 (KEEP THESE FILES SAFE!!!!!)
3)Obtain the system.img file from here (Compliments of whoopsiedaisy).
4)Replace the system.img file in the Nandroid backup folder on your PHONE.
5)ADB into your phone (preferably still in recovery) and do the following:
Code:
adb shell
# cd /sdcard/clockworkmod/backup/2010-xx-xx.xx.xx.xx
# rm nandroid.md5
# md5sum *img > nandroid.md5
6)If all goes will it should create a new MD5 checksum file utilizing the new system.img
7)Go to the 'backup and restore' menu in Clockwork, and select 'Advanced Restore'
8)Select the correct nandroid backup folder where the new system.img file is located, and then select 'Restore System'
9)Assuming all goes well, go to Settings, About and check your new system version!
Nice, can't wait to try this on my wifes phone after work.
Sent from my ADR6300 using XDA App
Is the second step necessary if you just want root access so you can install Wireless tether, etc?
jayhammy said:
Is the second step necessary if you just want root access so you can install Wireless tether, etc?
Click to expand...
Click to collapse
Not at all. Simply run z4 if all you require is root access (and a host of apps like Wireless Tether, DroCap, Titanium Backup ...)
Can you please post the quickoffice apk from the Dpro so I can put on an DX? Same would go for the software that allows me to Invite attendees to meetings using GAL. It be copasetic if you can.
Thanks a ton! Freaking worked flawlessly on my Droid X.
Nate
Cool. Cant wait to try this on my wife's phone.
I downloaded everything you said and i started my deodex but when i select option 3 in main it tells me "error no odex file" have i done something wrong please advise
Is it really that simple?
I feel like I must be missing something. I just download an app from the market and reboot and I'm rooted?
Also, what is the deodex for? I want to root my phone to install the apps I want and I want wifi tether. Do I need it?
Also, I really want to understand what is going on under the hood, but I don't know where to start. Is there a 'for dummies' tutorial somewhere that I can go to to start understanding what all of this stuff is, so I can make informed decisions for myself about what I want instead of begging for help on internet forums? Thanks in advance for any suggestions.
Is there a way to unroot? I am not rooted but just curious.
rllong1 said:
Is there a way to unroot? I am not rooted but just curious.
Click to expand...
Click to collapse
Yes, Z4Root app allows you to root, re-root, and UNroot.
I see no uproot button on the screen. Only a root button
Sent from my DROID PRO using XDA App
I had version 1.1 of z4. I now have the. 3 version and it has the unroot button
Sent from my DROID PRO using XDA App
rllong1 said:
I see no uproot button on the screen. Only a root button
Sent from my DROID PRO using XDA App
Click to expand...
Click to collapse
You'll only see the unroot button once you've rooted. Otherwise, it will first show only the "root" option.
jayhammy said:
You'll only see the unroot button once you've rooted. Otherwise, it will first show only the "root" option.
Click to expand...
Click to collapse
I was rooted. I had titanium installed and superuser. Z4 ran fine but I had an old version of it. I dont know if that matters but thats all I did. I downloaded the 1.3 version and I now have the unroot button. On the old version there was no option for temp root either. Just root. On the version I have now there is a temp root and perm root button.
Would just like to let people know that your method for "updating" via nandroid backup would not work for me. Followed all the instructions to the letter and during the advanced restore I continually received md5sum mismatch errors.
So I took the chance and updated through the OTA update, it installed fine but lost root. Ran z4root (twice) and gained root access again .
Looking forward to some real custom daily driver roms for this guy.
darkninja157 said:
Would just like to let people know that your method for "updating" via nandroid backup would not work for me. Followed all the instructions to the letter and during the advanced restore I continually received md5sum mismatch errors.
So I took the chance and updated through the OTA update, it installed fine but lost root. Ran z4root (twice) and gained root access again .
Looking forward to some real custom daily driver roms for this guy.
Click to expand...
Click to collapse
Is there a way to uninstall the CWM recovery?
darkninja157 said:
Would just like to let people know that your method for "updating" via nandroid backup would not work for me. Followed all the instructions to the letter and during the advanced restore I continually received md5sum mismatch errors.
So I took the chance and updated through the OTA update, it installed fine but lost root. Ran z4root (twice) and gained root access again .
Looking forward to some real custom daily driver roms for this guy.
Click to expand...
Click to collapse
Kinda new to the whole rooting thing, just got a new Pro and rooted successfully with z4root, got rid of bloatware and installed titanium backup, wifi tether, etc. Am I correct in reading your post that I can unroot, OTA update, and re-root again? If so, will I have to uninstall bloatware again, or reinstall root apps? Or any other repeats? Any danger in doing this?
mynameismolotov said:
Kinda new to the whole rooting thing, just got a new Pro and rooted successfully with z4root, got rid of bloatware and installed titanium backup, wifi tether, etc. Am I correct in reading your post that I can unroot, OTA update, and re-root again? If so, will I have to uninstall bloatware again, or reinstall root apps? Or any other repeats? Any danger in doing this?
Click to expand...
Click to collapse
No need to un-root. This update is for the system portion only and does not touch the userdata. I simply went ahead on the rooted phone, let the OTA update download and install. In doing so lost root, but had no trouble gaining root access again via z4root. Did not have to re-remove any of the bloatware, at least if I remember correctly. Root apps will not need to be reinstalled but you may need to re-give them permission for root access. No danger that I have noticed or can think of.
For anyone doing the update the android method....
For it to work
You must do the adb "new" md5 creation portion with your phone in clockwork recovery for it to work and to not receive the mismatch error...
To do this, reboot recovery... then plug in usb from your computer... during the phone boot into recovery you should hear the alert from your computer that something from usb was plugged in. Finally, use the mount option in recovery to mount sd card to be able to transfer the .img file over to the correct directory then unmount sd card and do the adb commands in terminal window...
I had the same mismatch errors using my windows 7 machine and creating the md5 with android booted
Hope this helps

[Q] busybox installed, but where?

Hi there,
i'm actually trying to do the wimax backup found here:
http://forum.xda-developers.com/showthread.php?t=887900
I went through all of this trouble trying to install busybox until I found out that Titanium backup already installed 1.16 on my phone. However I can't seem to find where it was installed to and the,
busybox sed -n '/BEGIN CERTIFICATE/,$p' /dev/mtd/mtd0 > /sdcard/rsa_OEM.key
command isn't working. Any thoughts? Sorry if this is the wrong spot to post. I'm still getting the hang of this forum.
I have the same problem. I think I'm getting this error in the terminal emulator because I don't have the system Busybox installed, just Titanium's app busybox, which is apparently different?. When I try to run Busybox installer, it errors saying I'm possibly not nand unlocked... I used UR3 and UR forever, and can confirm that I am S-Off. Doesn't S-Off = nand-unlock?
I haven't played too much with busybox to know much of its capabilities, but if you want to know the directory it is located in, run this from Terminal Emulator, or adb.
find -iname "*busybox*"
that will get you any and all file listings with busybox in it.
says denied, so I typed su, and get the #
then I type the find command, and tells me that 'find' is not found.
topdawgn8 said:
I haven't played too much with busybox to know much of its capabilities, but if you want to know the directory it is located in, run this from Terminal Emulator, or adb.
find -iname "*busybox*"
that will get you any and all file listings with busybox in it.
Click to expand...
Click to collapse
greyopaque said:
says denied, so I typed su, and get the #
then I type the find command, and tells me that 'find' is not found.
Click to expand...
Click to collapse
you should be able to run find without a hitch. I have had issues running a find while executing a remove, but find had always worked...
try remounting the system:
Code:
su
remount rw
find -iname "*busybox*"
Edit: I just ran find with only SU. What rom and kernel are you running? The only two things I can think of are:
1: The dev removed it from the rom
2: User error-- ensure the commands are lower case, there is a space where appropriate (denoted by ">")
Code:
find>-iname>"*busybox*"
The busy box that tb installs doesn't have all the commands. I had to install from the market to get all the commands.
Sent from my PC36100 using XDA App
its in system/bin most of the time but can be in different spots
Usually you can find busybox in /system/xbin
OMG... I feel stupid... I had install location set for SDCard. That's why busybox installer was failing. I changed it back to auto, and installed busybox, and now everything is working!
Don't waste your time with the rsa keys backup. You'll never be able to restore them.
Use the recovery (amon's 2.2.x) to make a backup of the entire wimax partition. Should the need arise, recovery will be easy. To date, i've yet to see instructions how to restore just the keys.
That's exactly what I did. Thanx!
gpz1100 said:
Don't waste your time with the rsa keys backup. You'll never be able to restore them.
Use the recovery (amon's 2.2.x) to make a backup of the entire wimax partition. Should the need arise, recovery will be easy. To date, i've yet to see instructions how to restore just the keys.
Click to expand...
Click to collapse

Almost Complete Directions for A100(root, unlock, cwm, flash ROM)(HC & ICS info)

A Work in progress.
DISCLAIMER!
This Document ONLY applies to Acer Iconia A100 devices. For info on upgrading from HC to ICS you can look HERE to see the method I used to upgrade from stock HC 3.2 GEN2 to ICS (Note: This was before the general ICS release. It works on OTA update also) Then follow these directions to get to CWM with Custom ROM.
I'm writing this because we STILL don't seem to have a single clear set of instructions. So here is my attempt at getting one started. Please feel free to point out errors, or help us build a set of directions. I'm not trying replace anyones documentation or take credit for anything. All the info in these directions can already be found here in various posts.
Thanks to Vache, Civato, ZeroNull, Euclid's Brother, Ptesmoke, abliss, aznmode, eew245, crossix, Icewyng, toyface, PG101, Smokku and Everyone else for all the Work an Insight.
ROOT
To root ICS Leaks you need to use mempodroid(info & file here). Eew245 wrote up instructions (on applying mempodroid on A100 to obtain a root shell). ZeroNull also has made a basic script found here that will root the device for you if you prefer.
I use the method outlined by Eew245. You can use your own "su" and "busybox" binaries if you saved them. This method provides full permanent root.
I suggest you install superuser.apk and busybox installer after rooting. Superuser.apk will provide access control for superuser and busybox installer will allow you to update busybox. I also recomend installing terminal emulator(don't forget to configure it to use /system/xbin/sh after you install busybox).
UNLOCK
ZeroNull has made an easy to use package with instructions here If you don't have the Android SDK installed ZeroNulls method works fine. However if you want to use your own platform-tools you will need to modify the scripts first.(Just change the path for adb. Otherwise it will try to look for adb in the scripts working directory instead of platform-tools).
Pic of Bootloader warning about unlocking from Acer
PIC HERE
Lock Unlock Icons from same bootloader screen.
PIC HERE
Note: If you miss the window of oportunity running the script or unlock commands the first time. You DON'T need to rerun the whole script. The a200 bootloader is already installed. You just need to fastboot reboot bootloader again from your console, THEN you can use the vol keys and home to unlock the bootloader. BUT do what ever you feel safest doing and just pay attention and be careful. (Here I'm referring to the waiting too long after the script boots recovery into unlock mode. If you wait too long it times out and you can't choose unlock until you fastboot reboot bootloader again.)
RECOVERY
(make sure you have installed the a200/unlocked bootloader first. You will see a message at the top of the screen that says (UNLOCK MODE) when bootloader is showing it's message at boot.)
Here is the message I'm referring to PIC HERE
NOTE: When installing a Custom Recovery at some point you have to rename /etc/install-recovery.sh or remove it. I would recomend you rename it to install-recovery.sh.bak. You should do this before doing "adb reboot bootloader" otherwise when you try to reboot into recovery from ROM manager you will get a dead android because cwm will be overwriten with the old recovery(and you don't want that). If you DO get a dead android carefully read the directions again. Q. Why didn't I put this in a step? A. Because I dont want people to brick a device so I want to make sure they are paying attention before I tell them to rename a file that will keep the system from fixing recovery if they mess up.
Using Acer Recovery Installer 2.99 Beta(NOT MARKET VERSION)
=======================================
Download .apk enable non-market installers. Run installer, enjoy.
The Acer Recovery Installer 2.99 Beta is found HERE
Using ADB/Fastboot to flash CWM
============================
Use the steps found HERE(obviously don't re-root, unlock, just follow the other parts.
Or you can also use A100 TWRP recovery v2.1.0+ I have not tried it yet. It looks nice, has touch screen functionality, I think it uses a different backup format or something though. I'm not sure and have not had time to read up on it yet.
NOTE: Read my note above about /etc/install-recovery.sh
FLASH FROM CWM
==============
If you used ADB/Fastboot method you will need a way to reboot into CWM. ROM manager or bootloader reboot thingie will work for this.
If you installed Acer Recovery Image you can use it the app to boot into CWM.
CWM 5.5.0.4 uses the Volume Up/Down Toggle to navigate the menu and a short click of the power button to select things. Be careful about what you choose to do in CWM.
MAKE A BACKUP!!
===============
If you have just installed a custom recovery NOW would be a GOOD time to make a backup with CWM.
To Install a Custom ROM
===============
(BE CAREFUL. MAKE SURE The ROM you choose to install DOESN'T have a bootloader.blob and/or /recovery folder inside. Otherwise it could overwrite your CWM)
Just put the .zip file on an SD card and put it into the device. Use ROM Manager or Acer Recovery Installer
More to come, and I will add some pics showing what various screen look like when I'm able.
"I suggest you install superuser.apk and busybox installer after rooting. Superuser.apk will provide access control for superuser and busybox installer will allow you to update busybox. I also recomend installing terminal emulator(don't forget to configure it to use /system/xbin/sh after you install busybox)."
So ZeroNull says to not update busybox ...you say to update it...is there really a problem if you update it??
cheeb said:
"I suggest you install superuser.apk and busybox installer after rooting. Superuser.apk will provide access control for superuser and busybox installer will allow you to update busybox. I also recomend installing terminal emulator(don't forget to configure it to use /system/xbin/sh after you install busybox)."
So ZeroNull says to not update busybox ...you say to update it...is there really a problem if you update it??
Click to expand...
Click to collapse
i +1 the question what will break if i update busy box?
cheeb said:
"I suggest you install superuser.apk and busybox installer after rooting. Superuser.apk will provide access control for superuser and busybox installer will allow you to update busybox. I also recomend installing terminal emulator(don't forget to configure it to use /system/xbin/sh after you install busybox)."
So ZeroNull says to not update busybox ...you say to update it...is there really a problem if you update it??
Click to expand...
Click to collapse
I don't know if this helps or makes things worst, but I have updated busybox after using Zeronull's root script on pretty much every ICS leak, CM9, and Flexreaper without any issues at all. I always read that warning, but ignored it because I need a more complete busybox version for certain tasks I run on my tablet.
NoSudo said:
A Work in progress.
Using ADB/Fastboot to flash CWM
============================
Use the steps found HERE(obviously don't re-root, unlock, just follow the other parts.
Click to expand...
Click to collapse
Just a little tip. Actually same thread post#28 uses very simple method thanks to mapaz04 to flash the recovery.
Great job though!
I did almost the same in my native language.
cheeb said:
"I suggest you install superuser.apk and busybox installer after rooting. Superuser.apk will provide access control for superuser and busybox installer will allow you to update busybox. I also recomend installing terminal emulator(don't forget to configure it to use /system/xbin/sh after you install busybox)."
So ZeroNull says to not update busybox ...you say to update it...is there really a problem if you update it??
Click to expand...
Click to collapse
I have not used ZeroNulls root method. So I am not sure why he says that. I think his script MAY just use the su and busybox in place in /data/local/ or something(not sure havnt D/L the package to figure it out). You CAN setup su and busybox in the correct locations WITHOUT an issue in ICS.
I use the "hard" method which is very simple. I KNOW you can remove the /data/local/tools copy afterwords doing it by hand.
An Explanation:
The reason you have to push su, mempodroid, busybox, and a mount script to /data/local/ is because you can get write access to it WITHOUT su. Then you run mempodroid which does a little magic and tricks system into thinking a shell was started by root. This drops you into the # prompt(temp). Then you mount /system(still using the files from /data/local). Then you copy the files to the correct path inside /system. Once you chmod su and run it you get root becase su is a special kind of executable. It's what is called an SUID application. As long as the permissions are correct to allow you read/exec access to both su and busybox. You no longer need /data/local/tools. At this point you CAN update busybox and su if you like.
P.S. You can also use your OLD su and busybox for the whole thing. I saved my old su and busybox and always just reuse them then update.
If you want to understand more I would suggest reading up on what SUID is all about and also learn about Unix file permissions.
I can confirm that: rooting,bootloader unlock and change on the recovery can be made with OTA update.
Nice work!
gertjanad said:
Nice work!
Click to expand...
Click to collapse
Thanks, and a bump to keep the info around the first page.
Added to bump it back up so people can find it.
Is there a kernel that allows overclocking yet
Sent from my A100 using XDA
I have not played with OCing, I honestly don't see a need.
I know cwm 5.5.0.x has an Overclock menu so I'm guessing yes you can. But I am not familiar enough with the device/cpu to know how the multipliers etc are to be configured, nor do I experience lag or performance issues that would cause me to desire lowering battery efficiency and increase heat for faster performance.
Though I am familiar with the process on PCs both jumpered and jumperless.
Up!

[HOW-TO] [GSM & CDMA] How to root without unlocking bootloader (for ITL41D to JRO03O)

[HOW-TO] [GSM & CDMA] How to root without unlocking bootloader (for ITL41D to JRO03O)
As of Oct 10, 2012: Google has patched this vulnerability starting with JRO03U. That is to say, this works on versions of ICS and JB from ITL41D to JRO03O inclusive. It will not work for JRO03U or newer. (My previous guide found here only worked on Android versions 4.0.1 and 4.0.2, i.e., ITL41D/F and ICL53F.
Once you have root, you can use segv11's BootUnlocker app to unlock your bootloader without wiping anything. Easy as pie!
Disclaimer: I take no credit for this exploit or the implementation of it. All credit goes to Bin4ry and his team. I just isolated the parts required for the GNex, modified it slightly and eliminated the script.
So, it looks like Bin4ry (with the help of a couple of others) has managed to find a way to exploit a timing difference in the "adb restore" command. See source here. (Although this may be old news to some, I hadn't seen it before a few days ago.) This is more for informational purposes, as having a Nexus device, we are able to backup our data, unlock the bootloader and restore the backup, so this is guide is not really that useful for most, but you still have those users who are scared to unlock their bootloader. It is useful however, for those with a broken power button, as it allows them to unlock their bootloader without the power button.
How this works
The way this works is as follows: the "adb restore" command needs to be able to write to /data to restore a backup. Because of this, we can find a way to write something to /data while this is being done. Now, Android parses a file called /data/local.prop on boot. If the following line exists in local.prop, it will boot your device in emulator mode with root shell access: ro.kernel.qemu=1. So, if we can place a file called local.prop with the aforementioned line in /data, once your device boots, it will boot in emulator mode and the shell user has root access, so we now can mount the system partition as r/w.
So what does this all mean:
You can now root any version of ICS and JB released to-date without having to unlock your bootloader (and without losing your data).
Moreover, you should now be able to root your device even if your hardware buttons are not working.
Additionally, this allows those who have not received an OTA update and want to apply it without having an unlocked bootloader or root to do so by copying the OTA update to /cache from /sdcard.
Notes:
1) Please read the entire post before attempting this.
2) This does not wipe any of your data, but I take no responsibility if something happens and you lose your data. Maybe consider doing a backup as per this thread before attempting this.
3) This assumes that you have USB Debugging enable on your device (Settings > Developer Options > Enable USB Debugging) and the drivers for your device installed on your computer. For the drivers, I would recommend you remove all old drivers and install these. If you don't know how to install them, or are having issues, look here.
4) This obviously needs to be done over ADB, as you cannot run adb in a terminal emulator on-device. If you do not have ADB, I've attached it in the zip (Windows and Linux versions). Unzip all files.
Step-by-step:
1) Download the attached files to your computer and unzip them;
2) Open a command prompt in that same directory;
3) Copy the root files to your device:
adb push su /data/local/tmp/su
adb push Superuser.apk /data/local/tmp/Superuser.apk
4) Restore the fake "backup": adb restore fakebackup.ab Note: do not click restore on your device. Just enter the command into the command prompt on your PC and press the enter key.
5) Run the "exploit": adb shell "while ! ln -s /data/local.prop /data/data/com.android.settings/a/file99; do :; done" Note: when you enter this command, you should see your adb window flooded with errors -- this is what is supposed to happen.
6) Now that the "exploit" is running, click restore on your device.
7) Once it finishes, reboot your device: adb reboot Note: Do not try and use your device when it reboots. Running this exploit will reboot your device into emulator mode, so it will be laggy and the screen will flicker -- this is normal.
8) Once it is rebooted, open a shell: adb shell
Note: Once you do step 8, your should have a root shell, i.e., your prompt should be #, not $. If not, it did not work. Start again from step 4. (It may take a few tries for it to work. Thanks segv11.)
Now we can copy su and Superuser.apk to the correct spots to give us root.
9) Mount the system partition as r/w: mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
10) Copy su to /system: cat /data/local/tmp/su > /system/bin/su
11) Change permissions on su: chmod 06755 /system/bin/su
12) Symlink su to /xbin/su: ln -s /system/bin/su /system/xbin/su
13) Copy Superuser.apk to /system: cat /data/local/tmp/Superuser.apk > /system/app/Superuser.apk
14) Change permissions on Superuser.apk: chmod 0644 /system/app/Superuser.apk
15) Delete the file that the exploit created: rm /data/local.prop
16) Exit the ADB shell: exit (May have to type exit twice to get back to your command prompt.)
17) Type the following (not sure if this is needed for the GNex, but it shouldn't matter): adb shell "sync; sync; sync;"
18) Reboot: adb reboot
19) Done. You now should have root without having to unlock your bootloader. If you want to unlock now, you can without wiping anything. See segv11's app linked at the beginning of this post.
Note: If you still do not have root access after doing these steps, redo them and add this step between 10 and 11:
10b) Change the owner of su: chown 0.0 /system/bin/su (Thanks maxrfon.)
I've done all. It installs supersuser app but the phone is not really rooted and apps that requires it doesn't work
Lorenzo_9 said:
I've done all. It installs supersuser app but the phone is not really rooted and apps that requires it doesn't work
Click to expand...
Click to collapse
Did you try opening the Superuser app?
What happens when you open an app that requires root? Do you get the request for su access?
You can open the app but whith apps that requires root there are no requestes and they don't... Even using root checker you see that you're not rooted
Lorenzo_9 said:
You can open the app but whith apps that requires root there are no requestes and they don't... Even using root checker you see that you're not rooted
Click to expand...
Click to collapse
Re-run the entire procedure again (including pushing the su and Superuser.apk files). When I had done it, I used the latest version of su and Superuser.apk, but when I uploaded the files in the attachment in post #1, I used the files that Bin4ry had in his package, which I assume are older. Regardless, re-download the attachment in the first post and try it again.
efrant said:
Re-run the entire procedure again (including pushing the su and Superuser.apk files). When I had done it, I used the latest version of su and Superuser.apk, but when I uploaded the files in the attachment in post #1, I used the files that Bin4ry had in his package, which I assume are older. Regardless, re-download the attachment in the first post and try it again.
Click to expand...
Click to collapse
Ok I'll do it and then I'll report you what happens. So now have you updated su and superuser.apk?
Lorenzo_9 said:
Ok I'll do it and then I'll report you what happens. So now have you updated su and superuser.apk?
Click to expand...
Click to collapse
Yes, I put the latest versions in the zip in the first post.
I can confirm that this works, and also that step 10b was not needed for me. This is the first time I have not used a toolkit so if I can do it, anyone can.
Running a Verizon Galaxy Nexus, this allowed me to update to the leaked Jelly Bean OTA with a locked bootloader. I first flashed stock 4.0.4 and locked the bootloader. I then used the exploit to gain root access, allowing me to apply IMM76Q and JRO03O OTA updates via stock recovery. (Rebooting between updates.) Thank you for creating a guide that this newb could easily understand and follow.
serty4011 said:
I can confirm that this works, and also that step 10b was not needed for me. This is the first time I have not used a toolkit so if I can do it, anyone can.
Running a Verizon Galaxy Nexus, this allowed me to update to the leaked Jelly Bean OTA with a locked bootloader. I first flashed stock 4.0.4 and locked the bootloader. I then used the exploit to gain root access, allowing me to apply IMM76Q and JRO03O OTA updates via stock recovery. (Rebooting between updates.) Thank you for creating a guide that this newb could easily understand and follow.
Click to expand...
Click to collapse
Thanks for confirming that step was not needed.
Thanks!
Bookmarked for future reference :good:
does it work on nexus 7 ?
dacc said:
does it work on nexus 7 ?
Click to expand...
Click to collapse
Yes, it should.
thans for quick response
Works fine for my GNex, big thanks! How about putting it into a script for non-advanced users here?
wictor1992 said:
Works fine for my GNex, big thanks! How about putting it into a script for non-advanced users here?
Click to expand...
Click to collapse
Glad you got it working!
As for putting it into a script, I could but I'd rather not. As with most of the guides that I have written up, I purposely do not put things into a script so that people would actually go through all the steps and, by doing so, maybe get an understanding of what they are actually doing, and hopefully learn something in the process. If I would have packaged it up into a script, a lot of the less experienced users would not even try to go through the steps -- they would just use the script, and no one learns anything yet again. See here for some discussion on one-click scripts. Granted, blindly following a step-by-step is not much better, but I have tried to put comments and explanations throughout to facilitate learning. It's about the journey...
P.S.: I would appreciate it if no one else posts a script in this thread.
efrant said:
P.S.: I would appreciate it if no one else posts a script in this thread.
Click to expand...
Click to collapse
can i make a script that just puts in big text "STOP USING TOOLKITS AND 1 CLICKS"
Zepius said:
can i make a script that just puts in big text "STOP USING TOOLKITS AND 1 CLICKS"
Click to expand...
Click to collapse
LOL! Yes, sure, that's one script I don't mind being posted. LOL!
Heh, fair enough. I think I'm learning a bit about adb
One question: I can't replace system APKs by installing them, it tells me that there is a signature conflict. How can I fix that? I thought it shouldn't happen after rooting. (I'm trying to install the "international" velvet.apk).
wictor1992 said:
Heh, fair enough. I think I'm learning a bit about adb
One question: I can't replace system APKs by installing them, it tells me that there is a signature conflict. How can I fix that? I thought it shouldn't happen after rooting. (I'm trying to install the "international" velvet.apk).
Click to expand...
Click to collapse
Let's try to keep this thread on-topic please.
But to answer your question, don't install the apk. Using a file explorer that has root access, copy it to /system/app (after making sure that system is r/w) and make sure the permissions are set to match the other apks in that directory.
when running adb after running the command where i tell it to restore fake restore and then while the "exploit" is running ikeep getting , in cmd, link failed, no such file or directory, and it just keep doing that. is this normal or did i do something wrong.
efrant said:
Let's try to keep this thread on-topic please.
But to answer your question, don't install the apk. Using a file explorer that has root access, copy it to /system/app (after making sure that system is r/w) and make sure the permissions are set to match the other apks in that directory.
Click to expand...
Click to collapse

Categories

Resources