Develop Bugs

[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

[ROOTED] Rooting An Acer Iconia A101

Yes, finally, for us A101 owners out there, a rooting method has finally been found!
Firstly, it's important to point out that I DID NOT DISCOVER this rooting method. All credit for that goes to ZeroNull and can be found in his original post here. All I have done is to essentially translate it to more native English and hopefully explain it a little better. I've been a bit more long winded than ZeroNull was, but it's kinda necessary to make things clear.
Finally, and most importantly:
DO THIS AT YOUR OWN RISK! NEITHER I NOR ZERONULL ARE TO BLAME IF YOU MESS UP YOUR TAB!
You will need a few things:
1. The A10x_Rooting.zip file attached at the bottom of this thread. This contains ADB and SU.
2. An A100 ROM. It's probably best to go for as early a verion as you can but any should probably work. Get one from vache's thread here.
3. An A101 ROM. Any version will do, again you can get one from vache's thread above. Note there are some updated ROMs on about page 13 or so of that thread.
4. The ability to follow instructions CAREFULLY. Seriously, I can't stress this enough. One typo can make the process fail, so copy/paste the commands, OK?
5. Basic knowledge of how to open a cmd shell in Windows (I'm not a Linux person, but most of this guide will probably apply).
Right, on to the instructions!
Part One
1. Download all needed file as above and extract into a directory somewhere.
2. Connect your A101 to USB, make sure USB debugging is turned on, and open a command window in the same folder you extracted A10x_Rooting.zip in to.
3. Copy the A100's update.zip to the root of your external SD card on the tablet.
4. Reboot into recovery (hold power and left side of the vol rocker until you see the text).
5. Wait for the A100 ROM to install. This is the slightly scary bit as you just emasculated your tab! :O
Part Two
6. Once your tab has booted, make sure USB debugging is on and go to your command window. Type:
Code:
adb devices
If all is well, you'll get your UID in response. You don't need this for rooting, but it's a damn good idea to write this down somewhere safe.
7. Assuming 6 was OK, then proceed. If it wasn't, you'll need to sort that out yourselves
Enter the following commands.
Code:
adb shell
/system/bin/cmdclient ec_micswitch '`echo 'ro.kernel.qemu=1' > /data/local.prop`'
Nothing will echo back to you, and trying to ls that folder will give you a permission denied. Don't worry, it should have worked.
8. Type exit at the $ prompt to exit ADB shell.
9. Copy the A101 update.zip to the root of the external SD card, reboot to recovery and flash it.
Part Three
10. Once booted back up, go back to your command window and enter the following:
Code:
adb remount
adb push su /system/xbin/
adb shell "chmod 06755 /system/xbin/su"
11. Now you need to undo the qemu command. Enter the following in the command window.
Code:
adb shell "echo '#' >/data/local.prop"
Your root should now be 95% complete, but we're not quite finished yet.
12. Load the market and download BusyBox, SuperUser, and if you want it, Titanium Backup. Install all of these but DO NOT RUN THEM YET.
13. Reboot the device. Another scary part!
14. Once booted, run SuperUser then drop back to the desktop.
15. Run BusyBox and go through the install steps. During this SU should ask permission to give BB root access, if it does, it worked!
By the way, for me at least, SU moaned about being out of date whilst installing BB. Let BB install, then afterward, let SU update itself.
Important Note
After doing this once, if you install a newer ROM, you will NOT need to go back to the A100 to re-root, that part only has to be done one time. The local.prop file will now persist between ROM's so all you'll need to do is to go back to step 7 and proceed from there.

How does one figure out which version they have?
Sent from my Acer Iconia using xda premium

Mordak said:
How does one figure out which version they have?
Sent from my Acer Iconia using xda premium
Click to expand...
Click to collapse
You mean a100 or a101? A100 is the wifi only version that most of us have. The A101 has a spot for a phone SIMM card.

Mordak said:
How does one figure out which version they have?
Sent from my Acer Iconia using xda premium
Click to expand...
Click to collapse
It's under Settings -> About
Though I'm kinda puzzled as to how come you don't know which model you bought...

Thanks
Been waiting for ages till i searched it in google today.
Is there any chance we can install recovery like CWM?

Not at this time. Devs are working hard trying to bypass the locked bootloader on the A100. I'm assuming the bootloader on the A101 is similar enough that whatever method eventually gets worked out would work on both. I may be wrong. Wouldn't surprise me if I was lol
Sent from my Inspire 4G using Tapatalk

Hope you're right
Uh, and i think you should bold this:
3. Copy the A100's update.zip to the root of your external SD card on the tablet.
Since i've missed the "external" sd card and just copied it right to the internal sd, the rom was'nt detected by then. My bad, but there may be people like me hahaha

icefish1412 said:
Hope you're right
Uh, and i think you should bold this:
3. Copy the A100's update.zip to the root of your external SD card on the tablet.
Since i've missed the "external" sd card and just copied it right to the internal sd, the rom was'nt detected by then. My bad, but there may be people like me hahaha
Click to expand...
Click to collapse
Point 4 of the "things you will need" covers that.
4. The ability to follow instructions CAREFULLY. Seriously, I can't stress this enough. One typo can make the process fail, so copy/paste the commands, OK?
Click to expand...
Click to collapse

FloatingFatMan said:
It's under Settings -> About
Though I'm kinda puzzled as to how come you don't know which model you bought...
Click to expand...
Click to collapse
I never saw a 3G version in any of the stores near me. I did see the spot where a sim could go but I had no idea this was the differentiating factor. Thanks for the info.

Will this rooting method work on the A100?

The A100 has its own rooting method, but there's no reason why it shouldn't. In fact, someone posted a slightly modded version of this method for that model, in the A100 rooting thread.

sorry but i can't apply
adb shell
/system/bin/cmdclient ec_micswitch '`echo 'ro.kernel.qemu=1' > /data/local.prop`'
what can i do?

^ Defining "I can't apply" would help...
Seriously, that's about as much help to debugging the problem as a chocolate teapot.

ok,
when i submit the command
/system/bin/cmdclient ec_micswitch '`echo 'ro.kernel.qemu=1' > /data/local.prop`'
i get this from the console
/system/bin/cmdclient ec_micswitch '`echo 'ro.kernel.qemu=1' > /data/local.prop`'
and when i follow the next steps
i cant remount

What ROM are you running on?

[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

[Q] ZVB Will Not Root on LGOG

My first phone bricked when I attempted to update ZVB from ZV9 so they gave me a new one with 4.1.2 installed. When I try to root, the fiddy's program says that the root was completed, but none of my apps (Such as Titanium Backup) will work. It says I don't have root. Any idea's?

bodehart said:
My first phone bricked when I attempted to update ZVB from ZV9 so they gave me a new one with 4.1.2 installed. When I try to root, the fiddy's program says that the root was completed, but none of my apps (Such as Titanium Backup) will work. It says I don't have root. Any idea's?
Click to expand...
Click to collapse
Run fiddy root again.
1. Settings>PC Connection, Make sure it says under USB connection type, "Charge Only"
2. Start root
3. plug phone in
4. follow what is says
It'll work. I've done this many times. And that's what I got when I got in too big of a hurry.
Also, when you switch from charge to mtp, give it about 15 sec for any extra screens that might pop up. Just close them, then finish root.

ZVB still will not root successfully
engine95 said:
Run fiddy root again.
1. Settings>PC Connection, Make sure it says under USB connection type, "Charge Only"
2. Start root
3. plug phone in
4. follow what is says
It'll work. I've done this many times. And that's what I got when I got in too big of a hurry.
Also, when you switch from charge to mtp, give it about 15 sec for any extra screens that might pop up. Just close them, then finish root.
Click to expand...
Click to collapse
thanks for the reply.
Did exactly as instructed and screen says I have been successful (I have attached screenshot thumbnail). Titanium is still unable to get root and Superuser v.3.1.3 (46) says "su binary not found" and below that a box ticked "outdated binary notification". Not sure what that means and if it is even important. I successfully rooted ZV9 using the above method, but keep striking out on JB.
Should I just factory reset and start all over? Any help would be appreciated.

It looks like busybox didn't install. Did you use fiddy Universal root? Or, install busybox from the Playstore.
Sent from my LG-LS970 using xda premium

Finally
engine95 said:
It looks like busybox didn't install. Did you use fiddy Universal root? Or, install busybox from the Playstore.
Sent from my LG-LS970 using xda premium
Click to expand...
Click to collapse
thanx once again. I manually installed busybox and SuperSU and it worked like a charm. I used fiddy's zip file for Windows each time and I guess I thought that it installed Busybox in the bat command. My bad. Maybe making a notation in the directions of it needing to be installed prior to running zip would be helpful to some other egghead like me. thanks again.
BTW, are you running a stock kernel or have any suggestions on another one i might try to improve performance?

I've used fiddy' "Universal" many times with no issues. It installs BB and SU. Strange it didn't for you.
I was running stock kernel till just a few minutes ago. Evolutionmod has been putting them out regularly. Many people running it. Jokersax1 kernel is good too.
Sent from my LG-LS970 using xda premium

I tried a few different utilities and all of them failed every time.
I bought the phone Sunday, Build: JZ054K Software LS970ZVB
I found a post at lg-phones.org with these steps.
The steps needed some tweaking, and I was able to root my phone.
Enable Install from Unknown sources
Enable USB debugging mode
Connect your phone to PC as charge only
At a CLI
adb shell “echo -en \\x0d > /sdcard/G_security"
Disconnect the phone
Disable Install from Unknown sources
Disable USB debugging mode
Power off the phone
Power on the phone
Enable Install from Unknown sources
Enable USB debugging mode
Connect your phone to PC as charge only
At a CLI
adb shell id
It should report: uid=0(root), gid=0(root)
If the response is as above, continue
else, see note below and start over
(Note: The power off/on cycle seems to be critical, I had several iterations before it worked.
Each time I powered on the phone USB debugging was already enabled. When this occured, the shell
would not run as root. These are the steps that worked for me.)
adb.exe push busybox /data/local/tmp/busybox
adb.exe shell "chmod 755 /data/local/tmp/busybox"
adb.exe shell /data/local/tmp/busybox mount -o remount,rw /system
adb.exe push su /system/xbin/su
adb.exe shell chmod 06755 /system/xbin/su
adb.exe push SuperuserPro.apk /system/app/SuperuserPro.apk
adb.exe push Superuser.apk /system/app/Superuser.apk
adb shell chmod 0644 /system/app/Superuser.apk
cycle power
install busybox from the play store
I got root...

bought this phone last thursday rooted using thus method
http://forum.xda-developers.com/showthread.php?t=
also try downloading busybox from market not sure if it was supposed to install it but it didn't,
then i used root checker from market to verify root (suppose any app thats asking for permission for root access would do though)
then unlocked with paid version of freegee now running lifeless 14 and evolution 1.6 kernel
Sent from my LG-LS970 using xda premium