[Q] Permission denied on downgrade from hboot 0.98 - Verizon Droid Incredible 2

Recently I sent my phone in for warranty repair and unrooted the phone before doing so. I now have my phone back with hboot 0.98 and keep running into snag when trying to downgrade to 0.97.
Per instructions from attn1, when I enter
Code:
adb shell /data/local/tmp/sh -c '/data/local/tmp/misc_version -s 2.18.605.3'
I get a permission denied error and the downgrade subsequently fails. The first time I did it I had no problems and am using the same files and method I used in December, so I almost wonder if warranty repair did something special to the rom (doubtful though). I have 3 GB free on the Micro SD card, but I have not tried reformatting yet.
I've seen a similar issue reported on these two posts in addition to other sites with no resolution:
http://forum.xda-developers.com/showthread.php?t=1298990&page=25
http://forum.xda-developers.com/showthread.php?t=1364035
Any suggestions on what to try next?

Are u using windows?
Sent from my Incredible 2 using Tapatalk 2

I am using windows but I could also use a mac. I have not tried mac yet.

Why don't u just and fast boot adb devices and then run the hack-vivow file... I did in even bother with the adb shell
Sent from my Incredible 2 using Tapatalk 2

This was quoted from that thread...
Instructions for Downgrading Hboot from 0.98 to 0.97 on Verizon HTC Incredible 2 (followed by Instructions to root hboot 0.97 and 2.3.3 Android)
1. On your computer, disable or remove all phone, HTC Sync, iTunes, and all Antivirus software and suspend all unnecessary processes.
2. Install SDK Manager and then upgrade as it requires. Only install platform tools.
3. Install HTC USB Drivers on your PC. They can be found at http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe
4. Unzip downloaded package for downgrading hboot and extract to C:\hboot
5. Get adb and fastboot working on your PC
a. Turn on USB debugging on phone (settings>applications>developer>USB debugging)
b. Connect phone in charge only mode
c. Your phone should show up in device manager under “Android USB Devices”
d. If not, get this working before proceeding
e. Open command window as administrator
f. At C:\hboot, type “adb fastboot”
g. At C:\hboot, type “adb devices”…you should get a device code if the phone is properly connected
h. If not, retry steps, SDK settings, and file locations to get this working properly
6. After you get your proper device code, at C:\hboot, type “hack-vivow.cmd”
7. Let it run until totally complete (three to five minutes)
8. Restart phone
9. Turn USB debugging back on
10. Turn off phone
11. At this point, the phone should be unlocked, but still S-ON.
12. Go to step 4 in Incredible 2 Rooting Instructions (below) to turn S-OFF and unroot phone.
Alternatively to step 6 above, you can enter line by line the manual instructions below which is what is included in the “hack-vivow.cmd” command:
adb shell rm -r /data/local/tmp/*
adb push zergRush /data/local/tmp/zergRush
adb push misc_version /data/local/tmp/misc_version
adb shell chmod 777 /data/local/tmp/zergRush
adb shell chmod 777 /data/local/tmp/misc_version
adb shell /data/local/tmp/zergRush
adb shell /data/local/tmp/sh -c '/data/local/tmp/misc_version -s 2.18.605.3'
adb reboot bootloader
fastboot oem rebootRUU
fastboot erase cache
fastboot flash zip RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_Radio_1.09.01.0622_NV_VZW1.92_release_199487_signed.zip
fastboot reboot
Instructions to Root HTC Incredible 2 with hboot 0.97 and Android 2.3.3 – Verizon…12/8/11
1. Look for program conflicts:
a. Go to Control Panel > Programs and Features
b. Check to make HTC Sync is NOT installed
2. Obtain needed files:
a. Download “HTC_rooting_files.zip” from web, and unzip to your computer with 7zip (note unzipped file location and note that I may have renamed some of the files to match what is below)
3. Install drivers:
a. Open directory named “1_HTCDriver_incredible2” and run “1_HTCDriver3.0.0.007.exe” by double clicking.
4. Set phone parameters:
a. On phone, turn on USB debugging by going to Menu>Settings>Applications>Development>
b. Turn on USB debugging. Hit “OK”.
c. Connect phone to computer with USB cable. Select “charge only”, then “done”. Close any pop-up warning or box that appears.
5. Change phone to S-Off:
a. Open directory named “2_revolutionary_s-off_files_incredible2”
b. Run “revolutionary.exe” by right clicking and selecting “run in administrative mode”. (Allow if warned by security program).
c. Note the serial number on the screen when this command program stops running. Do not close this window! You will need to complete this step by adding the beta key provided in the next step.
d. Jump to step 6.
e. Input the exact beta key (case sensitive) and hit enter. Close any popups that appear on your computer.
f. While still in the black command program on your computer, allow the requested download and flash Clockwork Modrecovery by hitting “y”, and the pressing “enter”. (Allow is questioned by security program).
g. Your phone should now be a white screen with Revolutionary at the top in a purple box. Your phone is now “S-Off”
h. With “fastboot” selected on the screen, press the power button to accept.
i. Jump to step 7.
6. Obtain beta key for S-Off process:
a. Go to http://revolutionary.io
b. Click on “Downloads for Windows”. This will pop open a beta key form within the window.
c. Then cancel the download (you already have the files in the above Step 2 folder).
d. Put in your device type (Incredible 2), the Hboot (only one choice comes up), and the serial number that shows in Step 5c above. This will generate a beta key to use in the above Step 6c which will complete the S-Off process.
e. Jump back to step 6c.
7. Reset phone and load superuser files:
a. Unplug USB cable.
b. Use volume key to navigate to “recovery”, and press the power key to accept.
c. Select “reboot system now” and press the power key to accept.
d. After reboot, go to Settings>Power. Then turn off Fast Boot.
e. Connect USB and select “Disk Drive”, then “Done”.
f. Open the drive in your file explorer on your computer.
g. Drag or copy the “4_superuser.zip_ folder to this Removable Disk. This will put the folder on the mini-SD card in your phone.
h. Power off phone. Disconnect USB cable.
8. Restart phone in boot load mode.
a. With phone off, hold “down volume” and “power button” at the same time for a about five seconds and then release. Your phone should boot up with a white screen and text. If it boots to the regular phone, turn off and try again.
b. Navigate to “recovery” using the volume button and push the power button to accept.
c. Navigate to “install zip from sdcard” using the volume button, and push the power button to accept.
d. Navigate to “choose zip from sdcard” and push the power button to accept.
e. Navigate to “4_superuser.zip” and push the power button to accept.
f. Navigate to “Yes- Install” and push the power button to accept.
g. Navigate to “go back” and push the power button to accept.
h. Navigate to “reboot system now” and push the power button to accept.
9. Install apps
a. Go to Android Market app on your phone and search for AntTek App Manager. Download and install. When using agree to superuser permissions.
b. Go to Android Market app on your phone and search for Open Garden WiFi Tether. Download and install. When using agree to superuser permissions.
10. Test changes:
a. Go to app list and check to see that you have a Superuser app.
b. Go to AntTek App Manager and try to delete one of the worthless apps (approval may be required).
c. Go to Open Garden WiFi Tether and start program (approval may be requires).
11. Reconfigure settings:
a. Go to Menu>Settings>Applications>Development>. Turn off USB debugging. Hit “OK”.
b. Go to Settings>Power. Then turn off Fast Boot.
c. Go to Settings>Connect to PC>Default Connection Type, and select “Charge Only”. Then hit “Done”.
Sent from my Incredible 2 using Tapatalk 2

Actually I did run hack-vivow.cmd as administrator
If you notice in that script there is a line
Code:
adb shell /data/local/tmp/sh -c '/data/local/tmp/misc_version -s 2.18.605.3'
The result of that line is a permission denied error. That is the first error I see in the output from hack-vivow.cmd, and I believe is the reason it will not downgrade.

digitalshepard said:
Actually I did run hack-vivow.cmd as administrator
If you notice in that script there is a line
Code:
adb shell /data/local/tmp/sh -c '/data/local/tmp/misc_version -s 2.18.605.3'
The result of that line is a permission denied error. That is the first error I see in the output from hack-vivow.cmd, and I believe is the reason it will not downgrade.
Click to expand...
Click to collapse
Just had to warranty replace mine and I'm running into the exact same problem. I get the permission denied error and a failed downgrade every time. Tried it on two separate computers. I'm honestly thinking of using the HTC approved bootloader unlocker. Why is that not the recommended method for unlocking the bootloader?
Also using a completely clean sd card, if that makes a difference.

So it seems like warranty might have done something. I did get a printout saying that the software had been upgraded.
I was considering unlocking the bootloader, but I read some posts indicating that you can't install ROMs like CM7 or MIUI just by unlocking the bootloader. There again, I could be mistaken.

Just try doing a full factory reset. See if that helps. Re run it after.
Sent from my Incredible 2 using Tapatalk 2

faehsemc said:
Just try doing a full factory reset. See if that helps. Re run it after.
Sent from my Incredible 2 using Tapatalk 2
Click to expand...
Click to collapse
No Joy, Went through the setup process and didn't select anything. Only allowed it to activate, no Google account, no location. Same access denied message as before. I'm wondering if they've somehow tweaked the .98 bootloader in the phone they're currently sending out as warranty replacements.

Also no luck after a factory reset. Is there some way we can check to see if in fact the bootloader installed is different?
Sent from my ADR6350 using XDA

What does it all say? Either take a pic or write it... or both
Sent from my Incredible 2 using Tapatalk 2

My bootloader screen displays the following
Code:
VIVO-W XB SHIP S-ON RL
HBOOT-0.98.0000
RADIO-1.09.01.0312
EMMC-boot
Jul 18 2011,12:39:36
With a rev year of 2011, I wouldn't think its anything recent.

Try flashing this pg32img.. just like an update then try to downgrade... this is the latest ota update
http://forum.xda-developers.com/showthread.php?p=24854198
Sent from my Incredible 2 using Tapatalk 2

he has to have that ruu installed first then downgrade, i went through the same grap trying to get s-off after unlocking bootloader then relocking and flashing the ruu then everything clicked

When I tried to load the file referenced by faehsemc in the bootloader, I received the following error:
Code:
Main Version is older!
Update Fail!
Press <Power> to reboot.
The phone then reboots as if nothing has happened. I did the MD5 sum check before hand and it checked out.

Man dude I'm at a loss.... I'm sorry
Sent from my Incredible 2 using Tapatalk 2

Just out of curiosity, what does that error message mean? Is the rom on the phone the same as the one I tried to load, or actually newer than the one I tried to load?

[Edited for better understanding of what's going on and another URL of where this discussion is happening]
Just jumping into say that I'm having the exact same issue-- no matter if I use hack-vivow or if I copy-paste line by line. I got a refurb via warranty and February and this process (with the exact same setup) gave me no problems; I had to get another refurb via warranty this week (stupid charging port keeps coming loose), and am stalled. Update: it would seem that zergrush is failing to gain temp root. (I discovered over at a thread on rootzwiki (to which I can't post a link because I'm new-- thread is called "Gain S-OFF and Root the HTC Incredible 2 (works on 2.3.4)"), that that's what the hellions with blue flames mean, heh.) I'm adding to my list of things tried below.
My setup & things I've tried:
-- Mac OSX 10.7 with VirtualBox VM running Ubuntu 11.04
(I realize VMs can cause wackiness, but again, I used this same setup 2x before)
-- Open terminal, and I sudo bash to run everything as root
-- I've tried re-downloading the package from the main thread
-- I've tried different ports and cables (OEM and non)
-- I've tried gaining temp root via other older means, but it seems they've all been patched, too.
Results of using hack-vivow (emphasis mine):
[email protected]:~/Downloads# hack-vivow.sh
* daemon not running. starting it now *
* daemon started successfully *
257 KB/s (21215 bytes in 0.080s)
154 KB/s (15837 bytes in 0.100s)
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x00017118
[*] Scooting ...
[*] Sending 149 zerglings ...
[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
Sleeping 10 secs while adb restarts on the device....
/data/local/tmp/sh: permission denied
< waiting for device >
... OKAY
< waiting for device >
erasing 'cache'... OKAY
sending 'zip' (292817 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOchecking main version...
FAILED (remote: 43 main version check fail)
rebooting...

I get the same output as randomdeanna. Also like randomdeanna I have previously done this with the exact same files and setup.
Seems like those warranty repairs do something to these phones.

Related

Alternative method to Root your HTC Hero

HTC Hero Root access
By fakker1
1. Download:
1. http://developer.android.com/sdk/download.html?v=android- sdk-windows-1.5_r3.zip
2. http://rapidshare.de/files/47972320/orange-htc-hero-uk-boot.img-28-july-2009.zip.html
2. Install HTC Sync from your HTC device
1. Connect device to computer using USB cable.
2. Mount the SD card from the HTC Alerts Menu (Drag from the top of the screen).
3. Install the sync application from the newly discovered drive in Windows.
3. Extract the two zip files into some folder (separate folders for each zip).
4. Go to the Android SDK folder and open the tools folder.
5. Copy the two files from the boot image zip (1.b) into the tools folder:
1. boot.img.insecure
2. boot.img
6. Shutdown the phone.
7. Press and hold the back key and power on the phone.
This is get you into the fastboot screen (the white screen with three androids at the bottom).
8. Connect the phone to the USB cable if it’s unplugged.
9. On Windows, open cmd.exe (Start -> Run -> cmd.exe -> Enter):
1. Change the directory to the tools directory you’ve created earlier.
2.Run fastboot.exe boot boot.img.insecure from within the tools directory.
Output: downloading 'boot.img'... OKAY
booting... OKAY
3. Now your device will start from the given image with root access.
10. Gain root access:
1. In the phone’s alerts menu, click HTC Sync. This will popup the HTC Sync tool in Windows. Ignore it!
2.In cmd type: adb.exe shell
Output:
#
3. From the prompt you got (#) run the following command to mount the phone’s file system in RW mode:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
11. Add su command to your Phone
1. Run the the following commands in the shell (#) – Run each command separately (don’t just copy-paste all the lines!):
1.cat /system/bin/sh > /system/bin/su
2. chmod 4755 /system/bin/su
12.Reboot the phone by typing reboot in the shell (#).
13. The phone will restart and load the original Android ROM.
14. Enjoy the your Rooted Device
From Android Forum
Perhaps better titled "Alternative method to Root" since I personally had a nightmare just installing HTC Sync and on reading, this method certainly seems more complex than the one here http://forum.xda-developers.com/showthread.php?t=543571
Dayz xx
hummm
sorry but that would lose many n00bs....just like me...
i am going to change the title and let the pubic go for what they think is best.
liamhere said:
sorry but that would lose many n00bs....just like me...
i am going to change the title and let the pubic go for what they think is best.
Click to expand...
Click to collapse
You Noob!
Lol. Just kidding, Yeah i think this title is much better! I've been Rooting Android Devices since the g1 came out so im familiar to all this.
Im still waiting for my HTC Hero to arrive, it should be here any second. Once my dog starts barking, it will probably mean fedex guy is here.

[GUIDE][30/06/2011]Root AND Downgrade Desire Z/G2(S-OFF/ClockWorkMod) -No Gingerbread

This guide is now obsolete. Please use this guide instead.
For Gingerbread Phones, Please use this guide.
Hey guys, this is probably the easiest guide to follow for rooting a branded desire Z. The reason why this can sometimes be hard is cause it uses a unique identifier (INFOCID) and the companies that brand the phones ONLY want roms from their company on them. This stops us from using a WWE rom like every else to downgrade and then root.
But ultimately, the reason I'm making this is because every other guide I've read constantly links you to other guides or other pages and it sorta annoyed me. So after I figured it all out I posted one concise guide that doesn't redirect you 50 times.
Now I’m gonna run you through EVERYTHING so you won’t get stuck anywhere.
This guide will work with:
Device: Desire Z or G2
Firmware Version: Any Firmware version will be fine (All you need to do is downgrade using step 1)
Android Version: Froyo or any previous variation of Android (Absolutely no gingerbread device will root with this method)
Btw, I take no responsibility for any damage taken by using these procedures. Sorry =P
Also if you don't have ADB and Fastboot set up then go ahead and follow the guides on the first two posts here. -Thanks nephron
g4b4g3 said:
If your INFOCID is NOT one of these you need to make a goldcard to downgrade!
HTC__001
HTC__032
HTC__E11
HTC__203
HTC__Y13
HTC__102
HTC__405
HTC__304
HTC__A07
HTC__N34
HTC__J15
Which can be checked by typing the following two commands:
adb reboot bootloader
fastboot oem boot
Click to expand...
Click to collapse
If your CID matches one of the CID's above then you can skip Step 1.
1. Creating a Goldcard:
Prerequisites:
ADB Set up and running fine (to check if it is working just connect your phone and have USB debugging enabled. Then type adb devices in your CMD Prompt)
HxD Hex Editor (see attachments of post 1)
USB Debugging enabled on your phone
1.Firstly we need to mount the memory card on a windows PC.
2. Format the memory card as FAT32 using all the default options.
3. Mount the memory card on your Phone. Then give it a couple of seconds.
4. Remount the memory card on your PC.
5. Find your CID by using the follow command in your cmd prompt (YOU NEED ADB)
Code:
adb shell cat /sys/class/mmc_host/mmc2/mmc2:*/cid
6. Use the excel sheet provided to reverse the CID (see Attachments)
7. Goto this website and send yourself a goldcard.img
http://psas.revskills.de/?q=goldcard
8. Run HxD hex editor AS AN ADMINISTRATOR! (I can’t stress how important having admin rights is)
9. Go to Extras > Open Disk Image. Then select your goldcard.img
10. Go to Extras > Open Disk. IMPORTANT: Select your memory card UNDER the Physical Drives category. DO NOT open the logical drive.
11. Switch to your goldcard.img tab. Go to Edit > Select All. Then Edit > Copy.
12. Go to the physical drive tab and select the lines 00000000 until you get to the one with 00000170.
13. Go To Edit > Paste Write.
14. You should have a huge block of red characters now. This is good btw.
15. Mount your SD card on your Phone and let it detect it. If it comes up with a corrupt SD card error you have done it wrong and you may have to start over.
16. You are done with the goldcard.
2. Downgrading and Debranding
Before you start this please do the following:
1a. Download the RUU I’ve linked (it should be a ~300mb exe file) -Thanks g4rb4g3
ii. If you are a BELL User. Please download this RUU instead.
1b. Run the setup until you get to the screen with the tick boxes (Some Users may have to run this as an Administrator)
1c. Leave the setup running and go to C:\Users\<your account name>\AppData\local\temp ( Or Try %AppData%\Local\Temp\ ). Then right click and Sort By Date Modified. Look for the most recently created folder which should look like {xxxxxxx-xxxxxx-xxxxxxxx}. Then navigate into it and its then into its one folder. Look for rom.zip and copy that to your goldcard/memory card.
1d. Rename the rom.zip on your memory card to PC10IMG.zip (Make sure it is exactly the same as the way I've typed it there)
1e. Mount your sd card back onto your phone.
2. Download the attachments (misc_version & psneuters) and extract them in a folder like C:\RootVision\
Now you are ready to begin:
1. Open a CMD prompt window
2. Navigate your way to the folder with psneuter & misc_version IN CMD PROMPT. (So the cmd prompt window should be something like this C:\RootVision> )
3. Now we will use the following 5 commands one after the other
Code:
adb push psneuter /data/local/tmp
adb push misc_version /data/local/tmp
adb shell chmod 777 /data/local/tmp/psneuter
adb shell chmod 777 /data/local/tmp/misc_version
adb shell /data/local/tmp/psneuter
adb shell
4. After the last command you should have a # and a flashing line for you to enter text. This is good. (If you get a $ you have done it wrong and should try typing the commands out again)
5. Now you have the # type the following command in: (This will spoof the radio version)
Code:
/data/local/tmp/misc_version –s 1.33.405.5
Then go ahead and type:
Code:
exit
6. Type this command into your cmd prompt (btw you should be back with the normal C:\RootVision>)
Code:
adb reboot bootloader
7. Once on your white screen with colourful text you can go ahead and press the power button ONCE
8. Now just wait for the rom to install and verify. If you get INCORRECT CID your gold card doesn’t work or your CID doesn't match and you'll need a goldcard. (Go to Step 1. and make a goldcard for your phone)
9. Go ahead and install the rom when it asks you.
10. You are done downgrading and can now begin the Rooting process.
See Post 2 For Rooting
Assuming all as gone well and you now have a rom without superuser but you have a baseband version that is 1.34xxxx.
Alright, let’s begin.
Prerequisites:
Download psneuter
Download gfree 0.5
Download root_psn
Download flash_image
Download the Desire Z hboot
Download Clockwork Recovery
ALL of these are in the attachments section
They all should be extracted into the same folder. Use something simple like C:\RootVision\Root
3. Root your Desire Z!
Before you start:
Enable USB Debugging and Allow Unknown Market Installations again.
Also delete the PC10IMG.zip on your phone if you downgraded.
Okay lets go:
1. Now Assuming you succeeded at the last part you should have a stock-ish rom without superuser. What we want to do is start by pushing all the files across with the following adb commands (use in cmd prompt the same way you pushed files in 2.)
Code:
adb push psneuter /data/local/tmp/
adb push gfree /data/local/tmp/
adb push busybox /data/local/tmp/
adb push root_psn /data/local/tmp/
adb push flash_image /data/local/tmp/
adb push su /sdcard/
adb push hboot-eng.img /data/local/tmp/
adb push Superuser.apk /sdcard/
adb shell chmod 755 /data/local/tmp/*
2. Alright now we have all the files we need to root the phone. Input the following command. This is just putting our clockwork recovery in a convenient place with an easy name.
Code:
adb push recovery-clockwork-3.0.2.4-vision.img /data/local/tmp/recovery.img
3. Now we’re gonna temp root again by typing in the following:
Code:
adb shell /data/local/tmp/psneuter
adb shell
4. This should leave us with another #. Now enter the following commands:
Code:
cd /data/local/tmp
./gfree -f -b hboot-eng.img
./flash_image recovery recovery.img
./root_psn
sync
5. Type in: (thanks for the correction john_d1974)
Code:
reboot
6. You should have a rooted phone with superuser after the reboot. Also it will have clockworkmod, SuperCID, secu-flag off & an Unlocked HBOOT-ENG.
If gfree 0.5 doesnt work for you then this section is for you:
Prerequisites:
Download psneuter
Download gfree 0.2
Download root_psn
Download flash_image
Download the Desire Z hboot
Download Clockwork Recovery
ALL of these are in the attachments section
They all should be extracted into the same folder. Use something simple like C:\RootVision\Root
1. Now Assuming you succeeded at the last part you should have a stock-ish rom without superuser. What we want to do is start by pushing all the files across with the following adb commands (use in cmd prompt the same way you pushed files in 2.)
Code:
adb push psneuter /data/local/tmp/
adb push gfree /data/local/tmp/
adb push busybox /data/local/tmp/
adb push root_psn /data/local/tmp/
adb push flash_image /data/local/tmp/
adb push su /sdcard/
adb push hboot-eng.img /data/local/tmp/
adb push Superuser.apk /sdcard/
adb shell chmod 755 /data/local/tmp/*
2. Alright now we have all the files we need to root the phone. Input the following command. This is just putting our clockwork recovery in a convenient place with an easy name.
Code:
adb push recovery-clockwork-3.0.2.4-vision.img /data/local/tmp/recovery.img
3. Now we’re gonna temp root again by typing in the following:
Code:
adb shell /data/local/tmp/psneuter
adb shell
4. This should leave us with another #. Now enter the following commands:
Code:
cd /data/local/tmp
./gfree -f
./flash_image recovery recovery.img
./root_psn
sync
5. Type in: (thanks for the correction john_d1974)
Code:
reboot
6. You should have a rooted phone with superuser after the reboot. Also it will have clockworkmod, SuperCID and secu-flag off.
4. Installing your own custom ROM
This section is just in case you don't know how to install a custom ROM.
Note: Always make sure the ROM you are installing is FOR YOUR PHONE! If you install a ROM meant for another phone you could potentially damage it or brick the phone itself.
1. Download the ROM you want and copy it to your SD Card. (Try to keep it in a folder that is easy to get to)
2. Turn off your phone.
3. Hold down the volume down button and then press the Power Button. This should take you to a white screen with lots of colourful text. One of which says FASTBOOT or FASTBOOT_USB.
4. Press the power button ONCE when BOOTLOADER is selected(BLUE)
5. Navigate using the volume buttons until you get to RECOVERY and then press the Power Button again.
6. The HTC Logo will come up then you will get a black screen with text.
7. From here you should Always do a NANDROID Backup so you can restore a working ROM if something fails.
NANDROID Backup
7a. Navigate to 'backup and restore' and then select it by pressing the trackpad button.
7b. Select 'Backup' and then let it finish. Once done you have a backup of your android.
8. Now you want to do these before you start installing:
a. 'wipe data/factory reset
b. 'wipe cache partition'
c. Go into 'advanced' and select 'Wipe Dalvik Cache'
9. Now you can install the ROM itself. This is done by selecting 'install zip from sdcard' in the main menu. Now you can select 'choose zip from sdcard' and just go ahead and select the ROM you copid to your sd card earlier.
9a. If the phone says verification failed then just toggle the signature verification option.
FAQ - For Anyone with any issues.
1. My version is 1.7xxxx or higher. Can I use this method?
Yes you can. This method will downgrade your phone to 1.34 so your radio is no longer locked thereby allowing you remove the secu-flag, add superCID and allow you to install a custom recovery (like ClockWorkMod)
2. My CID is XXXXXXXX and isn't on that list, will this method still work?
Yes it will. The reason why it will work is because a goldcard is essentially a manufacturers way of bypassing the CID checks used by ROMs. Therefore, by creating our own unique goldcards we can also bypass the CID check.
3. My CID is on the list that you mentioned. Do I need this goldcard?
No, you can skip the 1st step because when the ROM checks your phones CID it will match up perfectly and the phone will install the older radio without issue.
4. What Benefits does rooting a phone grant you?
Simply, it allows you to install any ROM of your choosing onto the phone as well as use custom kernels and certain applications that access locked functions on the phone. This can ultimately lead to; a longer battery life; more stable roms and more frequently updated roms; and finally an overall faster Android experience.
5. What is root access?
Root access essentially gives you access anything locked by the manufacturer on the phone. This most importantly means that you can read and write to any system partitions on the phone that would normally be locked.
6. Whats psneuter?
psneuter is an application used to grant temporary root access. This is done through an exploit in the android system and will give us a window to further exploit the system and ultimately grant us Permanent Root Access.
7. How do I find my CID?
To find your CID you run two commands. Firstly, in your CMD prompt you type 'adb reboot bootloader' when your phone is connected and USB debugging is active. This will restart your phone into its bootloader. Then once you see the words FASTBOOT_USB you type 'fastboot oem boot'. Then look for the words CID and then just read the 8 character CID.
Also there is a post with a screenshot here.
8. My phone will not find PC10IMG.zip
You will need to double check that the PC10IMG.zip is the correct ZIP file from the RUU that has been linked. It should be roughly 250mb in size and should be placed in the root folder of your SD Card. Also your SD Card must be compatible with your device (able to be read/written to). If you cannot access your SD Card from your Desire Z or G2 then there is probably something wrong with your SD Card. It should probably be reformatted.
9. Can I use this on the Desire Z/G2 running Gingerbread?
So far no one has been able to root the gingerbread version of android on the Desire Z/G2. Unfortunately, this guide still cannot root gingerbread desire Zs or G2s.
If there are any more, feel free to post them and I'll add them
10.I'm Missing my AdbWinApi.dll? What now?
espentan[U said:
][/U]
I don't know if you've figured this one out yet, but here's the solution to a potential cause.
You need to add the directory containing the "AdbWinApi.dll" to Windows' path under Environment Variables, so Windows know where to look for the necessary files when you enter commands in the shell.
For this exercise I'm going to assume that you have installed the Android SDK in the directory called "android-sdk-windows" on your C: hard drive. If you have it installed somewhere else, change the path I'm mentioning below accordingly.
Go to the Windows "Control Panel".
Click on "System and Security".
Click on "System".
Click on "Advanced system settings" in the left column of the window you're in.
Find the button called "Environment Variables" in the window that opens (it's at the bottom on the first tab).
Scroll down in the "System variables" box until you find "Path".
Select "Path" and click the "Edit" button.
At the very beginning of the input field called "Variable value" enter the following:
"C:\android-sdk-windows\platform-tools;" (without the quotes).
Do not remove any of the other paths, and make sure you have a semi colon at the end of the new path you're adding.
Reboot.
Now the windows command shell knows where to find the necessary DLL's and whatnot.
Click to expand...
Click to collapse
will this work if i have 1.84.666.2?
anyone? thought?
Should work fine as long as you've got a Desire Z or G2 lol.
hi, manageage to root the DZ sucessfully, however on step 5 you say
"5. Type in:
Code:
Reboot"
i got an Reboot: error not found
i retried with with "reboot" and was sucessful
Hi, im sure this has been covered before in other posts, but, could someone tell me, if i were to use the above method to downgrade and root etc, would this prevent me from doing an official upgrade, to, say gingerbread in the near future? Also is there any real benefits to going to gingerbread? I ask as im sure ive read somewhere its only possible to flash to cooked roms, not official ones (once downgraded and rooted etc).. this would concern me as ive moved over from win mo to android, and in my experiance, EVERY cooked unoficial rom i ever flashed (xperia x1) was simply rubbish, and i tried alot of them. (Even though people would say the roms would be fine, bugs smoothed out etc), i went back to stock in the end after constant dissapointment.
Sorry for the rant, just need to know where i stand.. thanks people..
jmpcrx said:
Hi, im sure this has been covered before in other posts, but, could someone tell me, if i were to use the above method to downgrade and root etc, would this prevent me from doing an official upgrade, to, say gingerbread in the near future? Also is there any real benefits to going to gingerbread? I ask as im sure ive read somewhere its only possible to flash to cooked roms, not official ones (once downgraded and rooted etc).. this would concern me as ive moved over from win mo to android, and in my experiance, EVERY cooked unoficial rom i ever flashed (xperia x1) was simply rubbish, and i tried alot of them. (Even though people would say the roms would be fine, bugs smoothed out etc), i went back to stock in the end after constant dissapointment.
Sorry for the rant, just need to know where i stand.. thanks people..
Click to expand...
Click to collapse
It is pretty difficult to go back to stock updates from your carrier for example Vodafone. This is because of the unique CIDs used and the fact that it is extremely hard to find a stock ROM since no one can give you a NANDROID backup.
Anyways, there are numerous benefits to rooting your phone included with most ROMs. These benefits include longer battery life, faster ROMs & various other things depending on each chef.
Ok, thanks, but are the roms buggy at all, will some of the hardware not work properly, or will i have freezing probs etc, as i found this always to be the case with win mo roms?.. have you personally found a rom that works perfectly that includes htc sense? As i do like the UI..
My goal is to have all security off, full perm root, with a perfecly working sense rom that i can then overclock to a speed that works well with my particular phone, and to underclock when idle etc..
Thanks..
I need to verify that my Tmobile G2's INFOCID is compatible.
I typed in the two commands:
adb reboot bootloader
fastboot oem boot
The first one worked. The second command is not recognized once I'm in the bootloader. Can someone suggest a solution?
Newbie question,
how to unroot if i rooting the phone using this metode?
and how to go back to original rom?
Vader™ said:
Newbie question,
how to unroot if i rooting the phone using this metode?
and how to go back to original rom?
Click to expand...
Click to collapse
Firstly, to root the phone just follow the steps and once you've finished them all you will be done.
Second, it should technically be possible once you've rooted the phone to simply do a NANDROID backup via ClockWorkMod Recovery before you start flashing new ROMs. If you have backed it up and later decide you want to unroot then all you would need to do from there is restore your nandroid backup and unroot the phone through this method.
forceOnature said:
I need to verify that my Tmobile G2's INFOCID is compatible.
I typed in the two commands:
adb reboot bootloader
fastboot oem boot
The first one worked. The second command is not recognized once I'm in the bootloader. Can someone suggest a solution?
Click to expand...
Click to collapse
Using this method you don't have to worry about your CID. If you make a goldcard it will completely bypass the need for one of the CID's listed in the first post. So to put it simply, you don't need to worry about your unique CID if you create and use a goldcard to downgrade.
Aegishua said:
It should technically be possible once you've rooted the phone to simply do a NANDROID backup via ClockWorkMod Recovery before you start flashing new ROMs. If you have backed it up and later decide you want to unroot then all you would need to do from there is restore your nandroid backup and unroot the phone through this method.
Click to expand...
Click to collapse
okay, but we need to root the device first right? before ClockWorkMod Recovery can run, the problem is, if I root the device first, the device must be downgrade to build 1.34.405.5, and now my Desire Z using build 1.82.xxx.x
is it if we backup via ClockWorkMod, the ROM that we backup is 1.34.405.5? not my current build?
please help bro, really confused here
Hi forceonature, im no expert, but when i was having a look myself, i found out it was simply my enviroment variables wernt set up for the directory fastboot was located.. an easy way round this was just to enter the directory fastboot was in (program files, 'some directory'.. do a quick search) within your command prompt, and type the second command from there.. hope that helps..
Everything goes fine until
mmap() failed. Operation not permitted
when I put in
adb shell /data/local/tmp/psneuter
Any help?
Also I can only put su and Superuser.apk on my sdcard if I manually transfer them.
Hi forceonature, im no expert, but when i was having a look myself, i found out it was simply my enviroment variables wernt set up for the directory fastboot was located.. an easy way round this was just to enter the directory fastboot was in (program files, 'some directory'.. do a quick search) within your command prompt, and type the second command from there.. hope that helps..
Click to expand...
Click to collapse
I need to verify that my Tmobile G2's INFOCID is compatible.
I typed in the two commands:
adb reboot bootloader
fastboot oem boot
The first one worked. The second command is not recognized once I'm in the bootloader. Can someone suggest a solution?
Click to expand...
Click to collapse
I tried the same thing to get my DZ phones CID and the first one worked and the second didn't. If I don't have to make a gold card all the better. How can I find out for sure if my CID is on the list or not? Also if I have to make a gold card do I need to have a micro SD card to make the gold card?
Thanks,
Chevy
chevy2410 said:
I tried the same thing to get my DZ phones CID and the first one worked and the second didn't. If I don't have to make a gold card all the better. How can I find out for sure if my CID is on the list or not? Also if I have to make a gold card do I need to have a micro SD card to make the gold card?
Thanks,
Chevy
Click to expand...
Click to collapse
You should get a line that says INFOt.cid=XXXXXXXX or any of the lines that say your 8 Digit CID. However, as you can see there are multiple lines that say it and they should all be the same.
If your CID does match one on that list then you will not need a goldcard.
I've attached a screenshot to make things easier.
forceOnature said:
okay, but we need to root the device first right? before ClockWorkMod Recovery can run, the problem is, if I root the device first, the device must be downgrade to build 1.34.405.5, and now my Desire Z using build 1.82.xxx.x
is it if we backup via ClockWorkMod, the ROM that we backup is 1.34.405.5? not my current build?
please help bro, really confused here
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
Yeah, you can only have a NANDroid backup of 1.34.xxx because there is no way to get clockwork onto a 1.72+ rom.
Hi, I'm new to rooting the G2. Iv'e been trying to follow this tutorial, but I'm having some trouble. After renaming Rom.zip to PC10IMG.zip I booted into the bootloader and it says 'no image found' or something like that. What am I doing wrong? Am I not supposed to put the zip file on the root of the SD card? Is it possible to just use the RUU to downgrade?
And regarding the downgrade, the build number on my G2 shows 1.22 . Isn't that lower than 1.34?
Any help is appreciated!
I followed the instructions twice and both times I get to
"/data/local/tmp/misc_version –s 1.33.405.5"
I get
/
Patching and backing up partition 17
Error opening backup file.
#
The first time around I iqnored it and went through hboot, the rom PC10IMG.zip was checked and verified and finally failed prompting "the main version is older"
what am I missing?
EDIT: checked SD card, unmount and remounted phone/sdcard no avail.
Will try 1.33 Bell rom next.
EDIT2: Patching and backing up sucessful, problem was I couldn't get my phone to stay in debugged mode without being in DISK DRIVE, had to start HTC Sync to mount the phone in that way to relieve the sd card, allowing adb to patch the file. Now running through PC10IMG.zip with fingers crossed.
EDIT3: Everything went smooth after that! Thanks. Now I will attempt to update to 2.3 and Sense 3.0
EDIT4: Now running on 2.3.3 and Sense 3.0 Virtuous port. Testing...probably going back to more stable gingerbread and sense 2.1

[GUIDE] Mini guide to root Gnex manually

1. Download and install Samsung_USB_Driver_for_Moblie_Phones_v1_4_6_0.exe
Link to download: http://www.multiupload.co.uk/YXE6FWLFAR
2. Download and install Android SDK (http://dl.google.com/android/android-sdk_r16-windows.zip)
3. With the phone turned OFF, hold VOLUME UP + VOLUME DOWN and power the phone on. This will put you in bootloader mode
4. Using windows/cmd go to the folder where Android SDK was installed (make sure that the folder android-sdk/platform-tools/ contains fastboot.exe and adb.exe etc....
5. using windows/cmd go to the folder /android-sdk/platform-tools
From this folder try the command "fastboot devices" (do not include ") which should list the device connected to your PC.
6. First we have to unlock bootloader,
use this command to unlock bootloader > fastboot oem unlock
(warning.. you will loose all data)
After the bootloader is unlocked the device will reboot normally.
7. Once normally booted from the command prompt issue the commands given below (after each command press enter button)
Note: you need su and superuse.apk (which can be downloaded from here: https://rapidshare.com/files/1319181583/su.zip)
unzip the downloaded file in the same folder where fastboot.exe exist i.e /android-sdk/platform-tools/
adb root
adb remount
adb push su /system/bin
adb push Superuser.apk /system/app
adb shell chmod 06755 /system/bin/su
adb shell chmod 06755 /system/app/Superuser.apk
adb reboot
Done!... your device is now rooted.
it would be good to note that many people have issues with the initial android driver installation.
if you install the drivers, but the phone doesn't show up after a period of time, open control panel -> system -> device manager and look for any devices that have a yellow triangle error (no driver). right click and open properties, and manually select the driver, not auto! the next screen will give you an option to 'select from a list', do this, and find SAMSUNG, then select the latest drivers.
after this, it can still take a minute or two the first time for drivers to install properly, you usually can see the status of this in the usb system tray icon.
if you rebooted to the bootloader (power vol(+) vol(-)), from the command line, if you type "fastboot devices" it should list a device and serial number. if not, you need to go check your drivers, something is missing. also, don't forget how magical a windows reboot can be at times : )
cancerouspete said:
it would be good to note that many people have issues with the initial android driver installation.
if you install the drivers, but the phone doesn't show up after a period of time, open control panel -> system -> device manager and look for any devices that have a yellow triangle error (no driver). right click and open properties, and manually select the driver, not auto! the next screen will give you an option to 'select from a list', do this, and find SAMSUNG, then select the latest drivers.
after this, it can still take a minute or two the first time for drivers to install properly, you usually can see the status of this in the usb system tray icon.
if you rebooted to the bootloader (power vol(+) vol(-)), from the command line, if you type "fastboot devices" it should list a device and serial number. if not, you need to go check your drivers, something is missing. also, don't forget how magical a windows reboot can be at times : )
Click to expand...
Click to collapse
Hi
Thanks for this note which would help many users.
Hi, noob here.
First of all, thanks for the guide.
I have already unlocked the bootloader about a month ago (up to step 6), but would like to root.
Will my phone lose all data again if I root the phone now? I'm not even sure what this actually does, but would like to learn and mess around with it.
You will not loose data. Rooting gets access your system folders by pushing su and superuser through adb.
Hope it helps.
Sent from my Galaxy Nexus using xda premium
smohanv said:
Note: you need su and superuse.apk (which can be downloaded from here: https://rapidshare.com/files/1319181583/su.zip)
unzip the downloaded file in the same folder where fastboot.exe exist i.e /android-sdk/platform-tools/
adb root
adb remount
adb push su /system/bin
adb push Superuser.apk /system/app
adb shell chmod 06755 /system/bin/su
adb shell chmod 06755 /system/app/Superuser.apk
adb reboot
Done!... your device is now rooted.
Click to expand...
Click to collapse
Did you actually test that with a stock rom?
Because adb root will not work with ITL41F at least.
Code:
./adb root
adbd cannot run as root in production builds
Furthermore the chmod for Superuser.apk is totally bogus. No need to mess with it's permissions.
i think a better way is get su and SuperUser.apk from the developers (ChainsDD) site and install it with a temporary boot CWM to install it.
(these instructions are also from memory And i rooted my one from source, but that's a bit involved)
this would mean instead of step 7 do.
7. Download CWM into the same directory as fastboot
http://download.clockworkmod.com/recoveries/recovery-clockwork-5.5.0.4-toro.img (Verizon)
or
http://download.clockworkmod.com/recoveries/recovery-clockwork-5.5.0.2-maguro.img (GSM)
Make sure to get the right version for your device.
8. download http://downloads.androidsu.com/superuser/Superuser-3.0.7-efghi-signed.zip
onto the internal storage of the phone( "sdcard" )
9. With the phone turned OFF, hold VOLUME UP + VOLUME DOWN and power the phone on. This will put you in bootloader mode
10. again using windows/cmd go to the folder /android-sdk/platform-tools
From this folder try the command "fastboot devices" (do not include ") which should list the device connected to your PC.
11. Start CWM (without installing it)
fastboot boot recovery-clockwork-XXX-XXX.img
(use the right filename from step 7)
12. choose install update and select the zip from step 8.
You need to use volume up/down to navigate and power to select.

Need help

so i really need help rooting my htc one vx! im following the tutorial here http://forum.xda-developers.com/showthread.php?t=2203225 but the thing is when i enter recovery mode i get teh red triangle. how do i fix this? please help iv tried other methods but none have worked i really want to have my phone rooted.
To Root HTC One VX
LordXombie said:
so i really need help rooting my htc one vx! im following the tutorial here http://forum.xda-developers.com/showthread.php?t=2203225 but the thing is when i enter recovery mode i get teh red triangle. how do i fix this? please help iv tried other methods but none have worked i really want to have my phone rooted.
Click to expand...
Click to collapse
First Unlock Bootloader And Then Root. :silly:
i have unlocked the phone. but it will not allow me to access the bootloader unless threw other means. while in the bootloader it says tampered followed by unlocked. i cannot seem to figure out what is going on.
How to root htc one vx
HTC One VX comes from the
HTC One series of
smartphones consisting of
high-end specifications, such
as Dual-Core processors and
the latest version of Android
on-board. While we already
have a root guide for the
One VX, another root
method has popped-up on
XDA and to help users root
their devices with this new
method, here we’re
presenting a tutorial
explaining everything you
need to root your device.
So, let’s see how you can
root your HTC One VX
smartphone.
I. Before You Begin:
1. This will void the warranty
of the device. However, you
can reinstate it by unrooting
the device if there’s any
unrooting procedure
available.
2. The following procedure
works on Windows based
PCs only.
II. Downloading
Required Files:
download file. http://forum.xda-developers.com/showthread.php?t=2123359
III. Rooting the HTC
One VX:
1. Place the Root Package
archive on the Desktop of
your PC.
2. Extract files from the
archive to your Desktop.
Don’t launch any files just
yet.
3. Turn ON the USB
debugging option on your
device by heading to
Menu>>Settings>>Developer
options>>USB debugging .
4. Turn OFF the device.
5. Reboot the device into
Fastboot mode. To do so,
simply hold down the
Volume DOWN+Power
buttons together.
6. Once inside the Fastboot
mode, connect the device to
your PC using the USB cable.
7. Open a Command Prompt
Window on your Desktop. To
do that, hold down the Shift
button on your keyboard
and right-click on any empty
area on the screen, then
select Open command
window here .
8. Type in following
command into the Command
Prompt Window:
fastboot flash boot boot.img
9. Once it’s done, issue the
following command:
fastboot reboot
10. Your device will reboot.
Once it boots up, enter the
following command:
adb remount
11. Next, enter following
commands into the
Command Prompt Window
one-by-one. Press ENTER
after each line you type:
adb push Superuser.apk /system/app/
adb push su /system/xbin/
adb shell mkdir /system/bin/.ext
adb push .su /system/bin/.ext/
adb shell chmod 6755 /system/xbin/su
adb shell chmod 6755 /system/bin/.ext/.su
adb shell chmod 777 /system/bin/.ext
adb shell ln -s /system/xbin/su /system/bin/su
adb reboot
12. Your device will reboot
in normal mode.
13. Once it boots up, simply
open the Superuser app
from your App Drawer.
14. Tap the Update binaries
button in the app and let it
do the rest of the work.
15. And you’re all done!
Brilliant! Your device has
been successfully rooted and
the SU binaries have also
been updated. Now load-up
some root-only apps on
your device to realize the
power of root-access!

[ROOT]How to Root KVT49L.D85110r and Install TWRP. My experience

I am not sure if this is the correct forum for this. Moderators, Please feel free to remove it or relocate it
First of all thanks to all amazing people on this forum ( thecubed,777jon,Dees_Troy, chainfire, supernoman, crashfocus, etc)
This is not my work . It is a compilation of what it worked for me from the work made by others. It is directly toward newbie users.
Instructions
1- Make sure you install LG G3 drivers in your computer( you can get them attached on this thread). Connect phone to the PC using USB cable. Make sure the phone is recognized when you plug it in with the usb cable
Also phone shall be connected as Media device (MTP), if it is in Charge Phone change it to MTP.
Scroll down this post. You will find the correct usb drivers attached. Install them in your pc.
2- Enable Developer options in your phone on Setting > General> About phone > Software information > and click seven times Build number until it enables it
3- Enable USB debugging on your LG G3 from your phones Settings > Developer options > tick ‘USB debugging’ check box. A window should pop up in your phone display to allow USB debugging. Select Allways Allow from This Computer and hit OK.
It will also be convenient to Enable installation of apps from Unknown Sources: Open phone’s Settings » select Security » Tick the “Unknown sources” check box (under Device administration section)
4- Download and unzip
- Pupledrake-Lite at http://downloads.codefi.re/thecubed/lg_g3/purpledrake/PurpleDrake-Lite_R03.tar.gz Thanks to Codefi.re
- Download and unzip the attached ADB LOCAL READY with TWRP recovery.img
Thanks to @Dees_Troy & TeamWin - for TWRP Touch recovery
ATTACHMENT IS HERE- JUST CLICK HERE
5- Download -Latest SuperSu at http://download.chainfire.eu/641/SuperSU/UPDATE-SuperSU-v2.40.zip Thanks to Chainfire
6- Transfer UPDATE-SuperSU-v2.40.zip to the internal sdcard
7- Open Purpledrake-Lite and Run purpledrake_windows.bat. It should detect your devices if it is not, you need to check if the drivers were installed properly and unplug-plug back your phone.
Hit Enter as instructed on the computer screen until it gains temporary root.
IMPORTANT : READ AND DO NOT CONTINUE TO PERMANENT ROOT INSTRUCTIONS DISPLAYED. FOLLOW INSTRUCTIONS TO CONTINUE WITH ADB INSTEAD.
Hit Ctrl+C to exit to use adb.
This process takes a few seconds and The phone start on download mode and it will stay on it.
8- Open ADB LOCAL READY folder you downloaded and hit Start Here.bat
Type "adb devices" to ensure that your phone is connected and it accept adb commands . On list of devices attached it should show LGD851........
Unplug it and plug it back if it is not .
NOTE: SOME PEEPS HAVE REPORTED PROBLEM WITH ADB NOT WORKING PROPERLY ON USB 3.0 PORTS. PLEASE USE USB 2.0 PORTS
9- Type "adb push recovery.img /temp"
You will see that it pushes the data. it should take a few seconds
Note: you may need to push it a few times if you do not find the recovery file on the /temp folder when you do step 12.
Some members stated that they need to push it ..5 times.
rubbamade tip
" This does work. If after you do the "adb push....", Hit the up key on your keyboard. What you just typed " adb push...." will appear again. Hit enter. It will "push" again. Hit up again. Hit enter. Do this at least 5 times. Now proceed with next step "adb shell"..... Should work now"
For some reason others user needed to push it more than 5 times, i assume that it is due to the file size of the image and your operating system and pc settings(i used win7). It is recommended to verify if it was pushed on step 12.
10- Type "adb shell" and it should go to shell command $
11- Then type "/temp/fakesu". This will put you in a superuser shell on your device. It should show su command line # .
12- Type "ls /temp" to make sure that recovery.img and fakesu are in /temp folder . If it is not, then you did not complete correctly the above instructions..repeat it
13- Type "dd if=/temp/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery". it will take a few seconds to complete and install TWRP recovery.
14- Type type "reboot recovery" It should boot onto TWRP Touch recovery. it could take a few but it should
15- Once in TWRP, select install,go to the SD card directory, select UPDATE-SuperSU-v2.40.zip and install it. Reboot the phone once complete. Do not panic, it should take a while to cook and update applications, but it will, be patient.
16- Your device is rooted and with TWRP custom recovery. IF you do not see SuperSu in your application drawer, do not panic, just install it from the Play Store.
17- Now you are ready to install custom Roms, any application that requires root, or enjoy root features.
Quick References
How to Boot into TWRP(Recovery Mode)
1.Turn off your phone
2.Now, press and hold Power and Volume down buttons at the same time.
3.When the LG logo appears, release the keys.
4.Immediately press Power and Volume Down buttons again until the Hard Reset menu will be displayed.
5.Press volume down to Select "YES" on reset data. Do not panic, it will not . Select "yes" again . It will boot into TWRP recovery mode.
If you do not like hardware method you can use Quickboot or TWRP Manager applications from the Play store
How to Boot LG G3 Download Mode
-Disconnect your phone from PC.
-Power off your G3 and wait 4-5 seconds after lights go off.
-Hold the Volume Up button on phone, and while holding it, connect the phone to PC using a USB cable
If you get the "Windows cannot find '.\assets\windows\bin\mintty.exe'." error..on purpledrake temproot step 7.
Try just double-clicking on the .bat instead of running as admin.
Also make sure the script is extracted properly first before running
Disclaimer: It worked for me, but I am not responsible for any damages to your phone.
Your experience is very interesting vcurbel!
I was under the impression there was no way to root untouched stock 10R.
It would appear you have found a way! :good: Thanks for your contribution.
I am curious if anyone else has replicated this?
thank you so much had a little trouble but successfully rooted my device
Where was this guide yesterday?
Last week I just thought rooting build R was impossible as of yet, got fed up, and 5 minutes ago ran the LG Update tool to revert my phone back to stock/ Build C and root that way.
vcurbel said:
I am not sure if this is the correct forum for this. Moderators, Please feel free to remove it or relocate it
13- Type "dd if=/temp/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery". it will take a few seconds to complete and install TWRP recovery.
Click to expand...
Click to collapse
dd if=/temp/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
This command doesn't work for me. It shows, "cannot open for read: no such file or directory".
Can you help?
Edit: Nevermind, had to repush recovery. Didn't go through properly the first time. Thank you
Everything worked great. Thank you for the guide! Rooted on 10r!
NO GO
- Type "ls /temp" to make sure that recovery.img and fakesu are in /temp folder . If it is not, then you did not complete correctly the above instructions..repeat it
AT THIS POINT I AM GETTING "NOT FOUND". DID THE STEPS ABOVE SEVERAL TIMES.
I saw 8xxxkb data pushed after 'push'
==========================================================================================
C:\Users\nick\Downloads\ADB LOCAL READY>c:\windows\system32\cmd.exe
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\Users\nick\Downloads\ADB LOCAL READY>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
LGD851xxxxxxxx recovery
C:\Users\nick\Downloads\ADB LOCAL READY>adb push recovery.img /temp
9716 KB/s (11245568 bytes in 1.130s)
C:\Users\nick\Downloads\ADB LOCAL READY>adb shell
[email protected]:/ $ /temp/fakesu
/temp/fakesu
# Is /temp
Is /temp
/temp/fakesu: Is: not found
#
=========================================================================================
sharkoparko said:
- Type "ls /temp" to make sure that recovery.img and fakesu are in /temp folder . If it is not, then you did not complete correctly the above instructions..repeat it
/temp/fakesu: Is: not found
#
=========================================================================================
Click to expand...
Click to collapse
try to redo step number 7. But, you are getting into su command line which is #
after you do the ls/temp on su #, you should get the list of files in your temp folder.....check if recovery and fakesu are there
then continue to step 13
vcurbel said:
try to redo step number 7. But, you are getting into su command line which is #
after you do the ls/temp on su #, you should get the list of files in your temp folder.....check if recovery and fakesu are there
then continue to step 13
Click to expand...
Click to collapse
Thanks. I did it several times, I did number 7 also. Phone is found, it says creating permaroot....Once I click CTRL C screen disappears then I go to ADB file and follow procedures. IT STILL DOES NOT WORK
===================================================================================
Welcome to PurpleDrake!
Please ensure your phone is connected, powered on, and USB debugging is properly enabled.
Your phone should be showing your homescreen with no other apps open. This is to ensure a clean state.
When you're ready, press [enter]...
Press [enter] to continue...
Waiting for device... Found device!
Your phone is a [ LG-D851 ] on [ TMO ] running SW version [ V10r ] ...
Alright. We're ready to go. We're going to temproot your phone first. Press enter when you're ready!
Press [enter] to continue...
Rebooting phone...
Waiting for device... .... Found device!
Found device, checking if vulnerable...
Yep, performing temproot...
Waiting for system to settle...
Temproot worked, all done here. Moving on...
Alright, now that you're temprooted, you can press CTRL-C here and get
a temproot prompt through 'adb shell /temp/fakesu' if you're so inclined...
However, if you'd like to permaroot, let's continue.
Press [enter] to continue...
===============================================================================================
DO I NEED TO RE-ROOT?
sharkoparko said:
Thanks. I did it several times, I did number 7 also. Phone is found, it says creating permaroot....
DO I NEED TO RE-ROOT?
Click to expand...
Click to collapse
Here is the problem. You pressed to continue (enter) to create permanent root after temporary root was created
You need to press CTRL C instead , then it will exit......then continue to next step with ADB LOCAL READY.
Ill clarify this better on step 7.
Sent from my SAMSUNG-SM-N900A using XDA Free mobile app
vcurbel said:
Here is the problem. You pressed to continue (enter) to create permanent root after temporary root was created
You need to press CTRL C instead , then it will exit......then continue to next step with ADB LOCAL READY.
Ill clarify this better on step 7.
Sent from my SAMSUNG-SM-N900A using XDA Free mobile app
Click to expand...
Click to collapse
Once I click CTRL C screen disappears then I go to ADB file and follow procedures. IT STILL DOES NOT WORK
That's what I do. I clicked enter first time rooting following purple instructions. Then I realized it does not work with January update. I run purple drake again (after I found this "fix") and, as I said, I DO NOT PROCEED WITH ENTER. I use CTRL C. The window closes and I open ADB, then click start hereand follow the rest of the procedures. So YES I did click enter once initially (because purple drake post is not updated that it does not work with JAN 15 update).
sharkoparko said:
Once I click CTRL C screen disappears then I go to ADB file and follow procedures. IT STILL DOES NOT WORK
That's what I do. I clicked enter first time rooting following purple instructions. Then I realized it does not work with January update. I run purple drake again (after I found this "fix") and, as I said, I DO NOT PROCEED WITH ENTER. I use CTRL C. The window closes and I open ADB, then click start hereand follow the rest of the procedures. So YES I did click enter once initially (because purple drake post is not updated that it does not work with JAN 15 update).
Click to expand...
Click to collapse
Ok....lets do it one at a time
Once you open and run ADB LOCAL READY. When you type adb devices, is it show your device?
Let me know on which step you got stuck.
Ill try to help you
Sent from my LG-D851 using XDA Free mobile app
Just got home with a Craigslist buy.
rooted in 15min thanks vcurbel !
now to find CM12 for this baby
hi sorry for the newbiness but for some reason i donload everything i need, basically preperation is done to the T, but as soon as i click on purpledrake_windows.bat it goes into dos window and complety exits out in less then a second, so fast that i can barely read whats on that lil black screen, im pretty sure i can make out "command not found" at the end of it..any help would be greatly appreciated
tomez206 said:
hi sorry for the newbiness but for some reason i donload everything i need, basically preperation is done to the T, but as soon as i click on purpledrake_windows.bat it goes into dos window and complety exits out in less then a second, so fast that i can barely read whats on that lil black screen, im pretty sure i can make out "command not found" at the end of it..any help would be greatly appreciated
Click to expand...
Click to collapse
Did you run it as Administrator?
Did you install LG drivers and the device is being recognized as Media device?
Sent from my LG-D851 using XDA Free mobile app
all drivers are installed, the device is recognized, and nothing, when i do run it as administrater i get a whole different error msg
vcurbel said:
Did you run it as Administrator?
Did you install LG drivers and the device is being recognized as Media device?
Sent from my LG-D851 using XDA Free mobile app
Click to expand...
Click to collapse
---------- Post added at 08:43 AM ---------- Previous post was at 08:38 AM ----------
windows cannot find '.\assets\windows\bin\mintty.exe'. Make sure you type the name correctly and try again...thats the error i get when trying to run as administrator
tomez206 said:
all drivers are installed, the device is recognized, and nothing, when i do run it as administrater i get a whole different error msg
---------- Post added at 08:43 AM ---------- Previous post was at 08:38 AM ----------
windows cannot find '.\assets\windows\bin\mintty.exe'. Make sure you type the name correctly and try again...thats the error i get when trying to run as administrator
Click to expand...
Click to collapse
It seems your windows os is missing the default mintty.exe terminal...
Google it and you will find a solution to manually install it.
Or use other pc
Sent from my LG-D851 using XDA Free mobile app
tomez206 said:
hi sorry for the newbiness but for some reason i donload everything i need, basically preperation is done to the T, but as soon as i click on purpledrake_windows.bat it goes into dos window and complety exits out in less then a second, so fast that i can barely read whats on that lil black screen, im pretty sure i can make out "command not found" at the end of it..any help would be greatly appreciated
Click to expand...
Click to collapse
If I recall if the PD batch file/script is closing on you or giving you trouble, then you can run the script manually.
See link below to thecubed PD lite thread and read the 5th grey portion down of the OP, it is titled:
"But, what if I don't want to run your script to root?"
If you must use command line because the PD batch file/script is closing immediately just be sure to STOP after gaining temporary root!
From OP step 7:
IMPORTANT : READ AND DO NOT CONTINUE TO PERMANENT ROOT INSTRUCTIONS DISPLAYED. FOLLOW INSTRUCTIONS TO CONTINUE WITH ADB INSTEAD. [/FONT]
lagvoid said:
dd if=/temp/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
This command doesn't work for me. It shows, "cannot open for read: no such file or directory".
Can you help?
Edit: Nevermind, had to repush recovery. Didn't go through properly the first time. Thank you
Everything worked great. Thank you for the guide! Rooted on 10r!
Click to expand...
Click to collapse
Hello,
I am also having the same issue. I tried the above steps a couple times and am not sure if I am doing something wrong (more than likely I am). What did you mean by repush recovery?
Try step 9 again
9- Type "adb push recovery.img /temp"
You will see that it pushes the data. it should take a few seconds
vcurbel said:
Ok....lets do it one at a time
Once you open and run ADB LOCAL READY. When you type adb devices, is it show your device?
Let me know on which step you got stuck.
Ill try to help you
Sent from my LG-D851 using XDA Free mobile app
Click to expand...
Click to collapse
-------------------------------------------------------------------------------------------------------------------------------------
C:\Users\nick\Downloads\ADB LOCAL READY>c:\windows\system32\cmd.exe
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\Users\nick\Downloads\ADB LOCAL READY>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
LGD851xxxxxxxx recovery
C:\Users\nick\Downloads\ADB LOCAL READY>adb push recovery.img /temp
9682 KB/s (11245568 bytes in 1.134s)
C:\Users\nick\Downloads\ADB LOCAL READY>adb shell
[email protected]:/ $ /temp/fakesu
/temp/fakesu
# Is /temp
Is /temp
/temp/fakesu: Is: not found
# dd if=/temp/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/temp/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
/temp/recovery.img: cannot open for read: No such file or directory
#
--------------------------------------------------------------------------------
Yes, The phone is recognized and the file as you see was pushed (see script above). I think there is some issue with this method, as other people are reporting problems following the procedure in post #1??!! I guess it work for some and it does not for others.

Categories

Resources