Need help with downgrading G2 - G2 and Desire Z Q&A, Help & Troubleshooting

Is there a way to downgrade to froyo so I can root my G2. it's currently on 2.3.4. But I can't seem to get adb working on my computer
---------- Post added at 09:42 AM ---------- Previous post was at 09:23 AM ----------
I'm trying to input these lines into command line (adb)
chmod 777 /data/local/tmp/fre3vo
I keep getting this
'chmod' is not recognized as an internal or external command,
operable program or batch file.
NEED HELP!!!

Make sure you're in adb shell first before doing chmod.
If you need more help, feel free to join #g2root irc on freenode
-Nipqer

Related

[Q] downgrade htc desire hd HELPPPPP

hi i have been trying to downgrade my htc desire hd so i can root it but when i get to command prompt i go to the c: drive as it says and add the downgrade file and it says
c:/downgrade is not recognized as an internal or external command,operable program or batch file
what can i do to get this working have i done something wrong please help me..thanks
the link i used was this one
http://forum.xda-developers.com/showthread.php?t=905003
Which instructions did you use (thread link would be good) and can you make a screenshot from the command error?
i downgraded my dhd yeaterday, following the thread http://forum.xda-developers.com/showthread.php?t=905003. I had no problems.
Sent from my HTC Desire HD using XDA App
You can also use the ace hack kit aswell. Its menu driven way of downgrading and rooting.super easy
Sent from my Inspire 4G using XDA App
I just downgraded yesterday with this
http://forum.xda-developers.com/showthread.php?t=1180639
I experienced one bug though, the program was never able to copy PD98IMG.zip onto the sdcard for me. So when I got to the "press power for hboot" I had to pull my sd card out and copy PD98IMG.zip on. worked like charm.
http://forum.xda-developers.com/showthread.php?t=905003
put Downgrade_v3 in your C: drive then open cmd with this command
c:\users\yourname>cd c:\
c:\>cd Downgrade_v3
rockztahh said:
http://forum.xda-developers.com/showthread.php?t=905003
put Downgrade_v3 in your C: drive then open cmd with this command
c:\users\yourname>cd c:\
c:\>cd Downgrade_v3
Click to expand...
Click to collapse
Thats what i did before and i got the error??why???
Drowngrading problem with DHD 2.37+
when i downgrade my DHD(2.37+) with UMT2.18.
it cant continue after Bootloader and HBOOT.
Dbug log from UMT is following
20/8/2011 6:05:40 PM : HTC Desire HD connected
20/8/2011 6:08:24 PM : Check Version ROM
20/8/2011 6:08:24 PM : Open Downgrade
20/8/2011 6:08:25 PM : Execute Downgrade
20/8/2011 6:08:25 PM : Downgrade use fre3vo
20/8/2011 6:09:03 PM : MD5 Success
20/8/2011 6:09:03 PM : Pushing PD98IMG.zip
20/8/2011 6:11:28 PM : Open About
20/8/2011 6:11:37 PM : Pushing fre3vo
20/8/2011 6:11:37 PM : misc_version
20/8/2011 6:11:37 PM : CHMOD fre3vo
20/8/2011 6:11:37 PM : CHMOD misc_version
20/8/2011 6:11:37 PM : Execute fre3vo
20/8/2011 6:11:52 PM : Patching ok
20/8/2011 6:11:52 PM : Reboot bootloader
20/8/2011 6:12:06 PM : Close Downgrade
20/8/2011 6:12:07 PM : Device disconnected
20/8/2011 6:12:55 PM : Device connected
20/8/2011 6:12:55 PM : Retrieving Product Device
20/8/2011 6:12:55 PM : HTC Desire HD connected
20/8/2011 6:13:28 PM : Open Debug Log
can anybody help, pls..
I would suggest that you do the steps manually. If you run win 7 or vista you could try running the cmd as administrator. It sometimes give better access to ports and drivers. Downgraded my dhd without problems yesterday following the links in the sticky post in dhd android dev thread. Win7 and cmd as admin just to avoid any rights issues.
Please post more details of the execution of the downgrade or simply run dir c:/ supposed to be a backslash but my android keyboard don't seem to have it.
Sent from my HTC Desire HD using XDA App
i had to run cmd as admin to, otherwise it didn't work.
Sent from my HTC Desire HD using XDA App
Let's go there step by step.
What did you do until now?
I mean from this guide.
You have the folder unzipped, right?

[Q] Temp Root and Downgrade issues 2.3.3

Hi Guys.
I have watched your Noob video and it's very funny.
However,I am going to have to risk being a "noob" due to the fact that im unable to post in the dev thread for downgrading.
I have decided to root my DHD and everyone says this is the place to go to learn how to do it.
I have read the instructions throughly and decided to take the plunge, however I'm having some problems
with the method described in the first post!
Please let me tell you what I have done so far.
1) I have read the posts at http://forum.xda-developers.com/showthread.php?t=879525 (doesn't seem to apply to me.)
2) I am running Build version 2.50.405.2 (So I need to downgrade.)
3) I have the latest version of HTC Sync installed.
4) I have created a gold card as directed in the "How to downgrade" post and also placed PD98IMG.zip in the root of the gold card
inserted in the phone.
5) My DHD is running Gingerbread 2.3.3, Software number 2.50.405.2 so I followed section b2 of the downgrade thread
http://forum.xda-developers.com/showthread.php?t=905003
However at the end of the cmd process I see a "$" symbol, not the "#" as per the screenshot.
Any ideas anyone?
Cheers.
Greg.
Update: I just tried the method here
http://forum.xda-developers.com/showthread.php?t=1152233
for "TEMP-ROOT ANY Gingerbread build and downgrade to 1.32.405.6"
I manage to temproot using the alternative method of typing the adb commands under the Temp Root heading.
I finally get the "#"
I still have the gold card with PD98IMG.zip in the DHD.
I go to Downgrade step 4 and again use the alternative method and type in the commands only for cmd to say
"adb: not found"
AAAGGGGHHHHHHH!
I have been trying this all day.
I'm going to curl up in a corner and cry now.
Any help greatly appreciated.
Greg.
Hi Greg, try this method, http://forum.xda-developers.com/showthread.php?t=952352
or this one : http://driphter.com/index.php?topic=3867.0
you won't get ur hands dirty with adb commands or other stuff
Hi Alex.
I have tried this method too.
Alas, no luck there either! :-(
alex6vasy said:
or this one : you won't get ur hands dirty with adb commands or other stuff
Click to expand...
Click to collapse
---------- Post added at 02:31 PM ---------- Previous post was at 02:30 PM ----------
Hi Mich.
I'll give this a go tonight.
Many thanks.
Greg.
MichDHD said:
Hi Greg, try this method, http://forum.xda-developers.com/showthread.php?t=952352
Click to expand...
Click to collapse
As Alex said try his link its easy and no telnet etc,id tried it many times through various ways and failed,the key is I found anyway...is to always format the sd card fully not a quick format,always do the 'takes longer' option I came from 2.50 also,it'll work
Sent from my HTC Desire HD A9191 using XDA App
adb push fre3vo /data/local/tmp
adb push misc_version /data/local/tmp
adb shell chmod 777 /data/local/tmp/fre3vo
adb shell chmod 777 /data/local/tmp/misc_version
adb shell /data/local/tmp/fre3vo -debug -start F0000000 -end FFFFFFFF
adb shell
after this # type:
/data/local/tmp/misc_version -s 1.31.405.3
exit
adb reboot bootloader
have a good time .....................
this is the simple method to downgrade ur device.........you may los ur apps...but will be restored from google after flashing sense roms..........
believe me...this will work 100% sure...........
I'm pretty sure I have tried this method, but I'll give this a go, cheers buddy.
Greg.
hi greg
i am a noob too but i tried this and i was successful.
http://forum.xda-developers.com/showthread.php?t=1180639
I hope I could help you, best regards, gluecke63
Hey dude.
Tried this, didn't work.
I successfully manage to get temproot using the code you gave, but then on reboot the below happens.
Always, when I get to the boot loader it recognises PD98IMG.zip and looks like it's loading it. After loading it I get a "Checking PD98IMG.zip" message then the bootloader just returns to the main screen, I am never asked if I want to update!
Getting totally flumoxed with this! :-(
So I have made a youtube video of the problem.
rohithksaj said:
adb push fre3vo /data/local/tmp
adb push misc_version /data/local/tmp
adb shell chmod 777 /data/local/tmp/fre3vo
adb shell chmod 777 /data/local/tmp/misc_version
adb shell /data/local/tmp/fre3vo -debug -start F0000000 -end FFFFFFFF
adb shell
after this # type:
/data/local/tmp/misc_version -s 1.31.405.3
exit
adb reboot bootloader
have a good time .....................
this is the simple method to downgrade ur device.........you may los ur apps...but will be restored from google after flashing sense roms..........
believe me...this will work 100% sure...........
Click to expand...
Click to collapse
You can't just flash PD98IMG.zip when this is an older base then your current.
When your phone is finished checking, it decide not to flash it cause it's older.
Apologies, I should have said I manage to get temproot using the code supplied. I have updated the post now.
Cheers.
MichDHD said:
You can't just flash PD98IMG.zip when this is an older base then your current.
When your phone is finished checking, it decide not to flash it cause it's older.
Click to expand...
Click to collapse
I wonder if my PD98IMG.zip file is corrupt.
I just did an MD5 check but it's tough to tell as the original PD98IMG.zip file I downloaded from here didn't have an MD5 Checksum with it
Hi guys.
Quick update. I have successfully downgraded my DHD.
The issue was a corrupt PD98IMG.zip
I downloaded MD5 Check 2.1 from here and tested the checksum of the PD98IMG.zip against the MD5 Checksup posted at the top of the page here, post 261,
Quick Ref - (C3D244A9F056E48EE3851A14FF52204C)
When MD5 Check 2.1 showed it as not matching, I downloaded a new PD98IMG.zip from here.
I used MD5 Check 2.1 to the checksum this new PD98IMG.zip. Success, it matched.
I transferred the new PD98IMG.zip to the goldcard I made using these instructions (I don't know if I actually needed a goldcard).
I put the Goldcard in my DHD, used cmd to run the below code as given by rohithksaj, thanks bud, which echoed the instructions here.
Code:
adb push fre3vo /data/local/tmp
adb push misc_version /data/local/tmp
adb shell chmod 777 /data/local/tmp/fre3vo
adb shell chmod 777 /data/local/tmp/misc_version
adb shell /data/local/tmp/fre3vo -debug -start F0000000 -end FFFFFFFF
adb shell
after this # type:
/data/local/tmp/misc_version -s 1.31.405.3
exit
adb reboot bootloader
When the DHD rebooted into bootloader, I selected "bootloader", then waited about 5 seconds for the bootloader to recognise the PD98IMG.zip.
the DHD then goes through a process of loading the PD98IMG.zip then it checks the PD98IMG.zip.
Finally the screen that eluded me appeared, the "Do you wish to start update?" screen.
I chose yes, 5 mins later I had a downgraded phone.
Thank you all for your help on this issue.
Props to you all.
Greg.
My next question is how do I change the thread title to "XXXX -Solved"?
All the best mate.............
Flash carefully reading all instructions..............
welcome to the world of custom roms ~~~~~~~~~~
Cheers bud.
just done Radio S-OFF
Just about to do ENG S-OFF
What Rom do you recommend?
I have been thinking about the Sense 3.0 rom for the DHD!
Thoughts?
Cheers.
Greg.
rohithksaj said:
All the best mate.............
Flash carefully reading all instructions..............
welcome to the world of custom roms ~~~~~~~~~~
Click to expand...
Click to collapse
TeamDraven said:
Cheers bud.
just done Radio S-OFF
Just about to do ENG S-OFF
What Rom do you recommend?
I have been thinking about the Sense 3.0 rom for the DHD!
Thoughts?
Cheers.
Greg.
Click to expand...
Click to collapse
thinking about sense 3........may use ARHD 6.1.1
or
any rom with official sense 3...........
flash what u like mate..............
All have different taste ~~~~~~

Help G2 downgrade with 2.3.4

Please help. Im trying to downgrade so i can root my g2 on 2.3.4 I set up ADB on my mac. Everything works. But when i try to adb push fre3vo /data/local/tmp, i get permission denied. What am im doing wrong??? SD is mounted on phone, not pc storage mode. Help me.
WHen i do enter
$ adb shell cat /dev/msm_rotator
i get this. /dev/msm_rotator: invalid length so this works.
Thank you
I have the same issue have you resloved it ?
crazylee27 said:
Please help. Im trying to downgrade so i can root my g2 on 2.3.4 I set up ADB on my mac. Everything works. But when i try to adb push fre3vo /data/local/tmp, i get permission denied. What am im doing wrong??? SD is mounted on phone, not pc storage mode. Help me.
WHen i do enter
$ adb shell cat /dev/msm_rotator
i get this. /dev/msm_rotator: invalid length so this works.
Thank you
Click to expand...
Click to collapse
What's the exact error you're getting when you run the command to push fre3vo?
Sent from my HTC Vision using XDA App
I finally go it to work. The problem was terminal on mac, have to first navigate to where platform -tools is then follower the guide. #g2root helped me a lot credit to them over there
Sent from my T-Mobile G2 using XDA App
I'm also on a mac and am having issues when I get to the point where I start to downgrade the ROM. I've downloaded the 2.2 ROM and Fastboot.exe and placed them both where my ADB is located. I then rebooted and I get the fastboot usb in red on my phone. Now the next step is where I have issues.
Below is what I get:
fastboot oem rebootRUU
-bash: fastboot: command not found
Has anyone had this issue or know how it could be solved? Could it be my Fastboot.exe file?
---------- Post added at 11:32 AM ---------- Previous post was at 11:14 AM ----------
eburms said:
I'm also on a mac and am having issues when I get to the point where I start to downgrade the ROM. I've downloaded the 2.2 ROM and Fastboot.exe and placed them both where my ADB is located. I then rebooted and I get the fastboot usb in red on my phone. Now the next step is where I have issues.
Below is what I get:
fastboot oem rebootRUU
-bash: fastboot: command not found
Has anyone had this issue or know how it could be solved? Could it be my Fastboot.exe file?
Click to expand...
Click to collapse
Nevermind, I just realized I had the PC fastboot

[Acer _AV041_A100_1.037.00_ww_gen1] root?

[Acer _AV041_A100_1.037.00_ww_gen1]
root
Can be successfully???
alexsec said:
[Acer _AV041_A100_1.037.00_ww_gen1]
root
Can be successfully???
Click to expand...
Click to collapse
ZN's method still works just fine.
http://forum.xda-developers.com/showthread.php?t=1531646
i can't root!
i can't root!
Verify the device is showing under the device manager, usb debugging is turned on, and that it is being run as administrator.
What OS are you using?
i have the same problem. Can't root after the recent update. using W7, executing it with and without administrator rights. Executing with administrator rights it says something of ADB.
alexsec said:
i can't root!
Click to expand...
Click to collapse
Updating script. Try once again.
rooted!! thanks!!
How to Updating script. Try once again.
@ ZeroNull, can you confirm whether ICS_rooting_A10x_A5xx works for the latest build?
Build number
Acer_A100_2.001.01_COM_GEN2
I have been unsuccessful so far:
==========================================
Preparation is finished.
-
Executing of the main script.
remote object '/system/bin/su' does not exist
The file "su" isn't created!
-
Not getting root!
-
Error!
I can confirm that I successfully rooted my A100 using ZeroNull's simple method (http://forum.xda-developers.com/showthread.php?t=1531646)
Build number: Acer_AV041_A100_1.037.00_WW_GEN1
I didn't even use the new script, I'm still using the old one (ICS_rooting.zip)
Unfortunately I can also confirm problems with recent updates of the SuperUser APK (It did not assign the correct Group ID), but apparently they were fixed in the latest update (v3.1.3)
Good Luck.
---------- Post added at 10:30 AM ---------- Previous post was at 10:05 AM ----------
alexsec said:
i can't root!
Click to expand...
Click to collapse
alexsec said:
How to Updating script. Try once again.
Click to expand...
Click to collapse
Hi alexsec, did you try with the new script, it creates a different directory than the old script did, and it uses the mkdir -p option so it creates any parent directories it needs:
Code:
adb shell "mkdir -p /data/local/tmp"
adb push tools /data/local/tmp
adb shell "chmod 0755 /data/local/tmp/mempodroid"
And it does a better job by waiting longer for the tablet to reboot:
Code:
rem Wait reboot tablet
for /L %%i in (1,1,7000000) do @rem
I even modify the getroot.sh script just to change back to the old su command and modify its permissions:
Code:
cd /data/local/tmp
echo >/data/local.prop
toolbox mount -o remount, rw /system/
cat su >/system/bin/su
ln -s /system/bin/su /system/xbin/su
chmod 06755 /system/bin/su
sync ; sync ; sync
reboot
Good Luck...

[UPDATED] Get s-off and root for 6.01.605.05 software

Update: Found better instructions here and updated this post with them: http://rootzwiki.com/topic/27003-root-dinc2-on-any-firmware-may-want-to-sticky-later/
Be warned that this has been reported to cause bootloops on Sense ROMs, proceed at your own risk.
A few disclaimers before I begin:
1) I AM NOT RESPONSIBLE FOR ANYTHING YOU DO TO YOUR PHONE. ANYTHING YOU ATTEMPT TO DO YOU DO AT YOUR OWN RISK
2) This method requires use of adb and is not for thr faint of heart. your phone WILL be bootlooping along the way; this is exactly what we want (at a specific point)
Now to begin in earnest
First find what we need!
We need the patched misc version, tacoroot, and the earlier GB RUU
Modified htc drivers or linux, both with working adb installation
disable fastboot on your device
A few disclaimers before I begin:
1) I AM NOT RESPONSIBLE FOR ANYTHING YOU DO TO YOUR PHONE. ANYTHING YOU ATTEMPT TO DO YOU DO AT YOUR OWN RISK
2) This method requires use of adb and is not for thr faint of heart. your phone WILL be bootlooping along the way; this is exactly what we want (at a specific point)
Now to begin in earnest
First find what we need!
We need the patched misc version, tacoroot, and the earlier GB RUU
Modified htc drivers or linux, both with working adb installation
disable fastboot on your device
Now we push, make executable, and execute the tacoroot method
adb push tacoroot.sh /data/local/
adb shell chmod 755 /data/local/tacoroot.sh
adb shell /data/local/tacoroot.sh
At this point we will run tacoroot with the --recovery, (push volume up and power at the triangle) (reboot after this) --setup and --root (run one, wait for the device to settle then run the next)
AT THIS POINT YOUR DEVICEWILL BE BOOTLOOPING; THAT IS PERFECTLY NORMAL
Now we downgrade the misc_version
adb push misc_version /data/local
adb shell chmod 777 /data/local/misc_version
adb shell /data/local/sh -c '/data/local/tmp/misc_version -s 2.18.605.3'
If everything so far has succeeded, youre almost there!
adb reboot bootloader
fastboot oem rebootRUU
fastboot erase cache
fastboot flash zip <your RUU>
fastboot reboot
If everything so far has succeeded, youre almost there!
adb reboot bootloader
fastboot oem rebootRUU
fastboot erase cache
fastboot flash zip <your RUU>
fastboot reboot
Click to expand...
Click to collapse
Tacoroot: https://github.com/CunningLogic/TacoRoot
misc_version: https://github.com/downloads/hyuh/misc_version_universal/misc_version_universal.zip
2.3.3 RUU: http://jellybellys.minus.com/mvivow/2
prototype7 said:
All credit goes to jcase on the RootzWiki forums, I can't try this out myself but I thought I'd share it for those who could use it:
Here are my instructions to preform this. If you do pack this in a script/program , please follow the license that comes with Tacoroot and misc_version
Download https://github.com/d...n_universal.zip
and unzip it
Preform manual tacoroot exploit
adb reboot recovery
(Reboot normally once in recovery, this creates the directory for the log. Continue once booted)
adb shell
rm /data/data/recovery/*
ln -s /data/local.prop /data/data/recovery/log
exit
adb reboot
adb shell
echo 'ro.kernel.qemu=1' > /data/local.prop
exit
adb reboot
(Device will appear to bootloop, but ADB will work, continue once adb is working)
adb push misc_version /data/local/
adb shell
chmod 755 /data/local/misc_version
/data/local/misc_version --set_version 1.11.605.11
rm /data/data/recovery/log
echo 'ro.kernel.qemu=0' > /data/local.prop
adb reboot
Now you can flash the proper ruu to s-off with
Sent from my Incredible 2 using Tapatalk 2 Beta-5
Click to expand...
Click to collapse
I'm going to try this when I get home hopefully I can FINALLY get downgraded...
Sent from my ADR6350 using XDA
Jayydude_SGP said:
I'm going to try this when I get home hopefully I can FINALLY get downgraded...
Sent from my ADR6350 using XDA
Click to expand...
Click to collapse
Let me know how it works .
Sent from my Incredible 2 using Tapatalk 2 Beta-5
I'm just a little unclear about what comes before and after this...
Can we get a post that has ALL the code/instructions spelled out? For instance, the "Preform manual tacoroot exploit"... is that the tacoroot code from before in its entirety, or just a certain part of it?
And then when the instructions in this post are done, are we to then follow the downgrade instructions from beginning to end?
Sorry to be pesty, but really want this to work and I'm just unsure of what all to do. Many many super thanks.
tcwota said:
I'm just a little unclear about what comes before and after this...
Can we get a post that has ALL the code/instructions spelled out? For instance, the "Preform manual tacoroot exploit"... is that the tacoroot code from before in its entirety, or just a certain part of it?
And then when the instructions in this post are done, are we to then follow the downgrade instructions from beginning to end?
Sorry to be pesty, but really want this to work and I'm just unsure of what all to do. Many many super thanks.
Click to expand...
Click to collapse
After you do this, use an RUU to downgrade and then use revolutionary to obtain s-off. I'll look into the tacoroot in a minute, like I said these aren't my instructions.
Edit: Nothing like a quick google search to make you feel like an idiot lol. The adb commands are the manual tacoroot exploit. I'll update the OP to make it more clear.
Sent from my Incredible 2 using Tapatalk 2 Beta-5
OP updated. Make sure to post and tell me if this works.
Thanks, but still unclear about one thing. To flash the RUU, do we follow all the instructions in the downgrade vivow .98 thread?
You have to combine all the instructions.
If you go to the rootzwiki page I spelled it out. Just can't link to external sites because I'm new to xda.
Perfect. Thanks and can't wait to give this a try in the morning.
Do you (or anyone) think it will matter that I have already (successfully) used the HTCDev boot unlocker?
aaronc222 said:
You have to combine all the instructions.
If you go to the rootzwiki page I spelled it out. Just can't link to external sites because I'm new to xda.
Click to expand...
Click to collapse
It took some tinkering (and a bit of sweating), but I was able to get this to work successfully.
I had previously used the HTCdev tool to unlock and was running clockwork recovery. I had to flash the stock recovery and do a factory restore, but still got a "99 unknown fail" when trying to flash the RUU at the end of this process.
A quick google search told me to relock the bootloader with "fastboot oem lock." After the relock, I had to do ANOTHER factory restore and then everything worked fine.
One difference for me: the bootloop started earlier, ie after "adb shell /data/local/tacoroot.sh --root". But I just continued to use adb when I could and got through it.
About to run Revolutionary. Thanks to everyone up to this point! Such a fantastic community!
not to rain on your parade but this makes no sense. after the adb reboot recovery..... i do the adb shell and then it cant find the file/directory
dets34 said:
not to rain on your parade but this makes no sense. after the adb reboot recovery..... i do the adb shell and then it cant find the file/directory
Click to expand...
Click to collapse
Are you rebooting out of the recovery? You do "adb reboot recovery," and then when you get to the red triangle, hold down volume up AND volume down and then the power button, reboot, let the phone reboot back into normal, and then continue the instructions.
unstuck! ... then stuck again
Trying this on a warranty replacement Dinc2 that's got Android 2.3.4, Software number 6.01.605.05 710RD ... the above post got me past the red triangle "!" thing, so I proceeded to:
Code:
adb shell
rm /data/data/recovery/*
ln -s /data/local.prop /data/data/recovery/log
exit
adb reboot
adb shell
echo 'ro.kernel.qemu=1' > /data/local.prop
and got:
Code:
$ echo 'ro.kernel.qemu=1' > /data/local.prop
cannot create /data/local.prop: permission denied
Is it significant that I'm seeing a "$" prompt instead of a "#"? or is that later in the process? Is it significant that, after the sym-linking of /data/local.prop to the log file and then rebooting, my phone had no signal and seemed pretty inoperable, but then after the write to /data/local.prop failed (and I sat googling around for a bit) the phone rebooted itself (no adb commands, and I didn't even breath in its direction) and came back to having signal and my settings, etc. and full operability?
Any help appreciated - I'll come back to this tomorrow ...
jehosephat said:
Trying this on a warranty replacement Dinc2 that's got Android 2.3.4, Software number 6.01.605.05 710RD ... the above post got me past the red triangle "!" thing, so I proceeded to:
Code:
adb shell
rm /data/data/recovery/*
ln -s /data/local.prop /data/data/recovery/log
exit
adb reboot
adb shell
echo 'ro.kernel.qemu=1' > /data/local.prop
and got:
Code:
$ echo 'ro.kernel.qemu=1' > /data/local.prop
cannot create /data/local.prop: permission denied
Is it significant that I'm seeing a "$" prompt instead of a "#"? or is that later in the process? Is it significant that, after the sym-linking of /data/local.prop to the log file and then rebooting, my phone had no signal and seemed pretty inoperable, but then after the write to /data/local.prop failed (and I sat googling around for a bit) the phone rebooted itself (no adb commands, and I didn't even breath in its direction) and came back to having signal and my settings, etc. and full operability?
Any help appreciated - I'll come back to this tomorrow ...
Click to expand...
Click to collapse
I'm in the same situation, any idea's yet? I wonder if I should htcdev unlock just to have root privilages
Here's a better guide for it, I'll update the OP in a minute: http://rootzwiki.com/topic/27003-root-dinc2-on-any-firmware-may-want-to-sticky-later/
Edit: OP updated.
prototype7 said:
Here's a better guide for it, I'll update the OP in a minute: http://rootzwiki.com/topic/27003-root-dinc2-on-any-firmware-may-want-to-sticky-later/
Edit: OP updated.
Click to expand...
Click to collapse
Thanks a lot, quick question though, will this send my phone into a continuous bootloop if I don't run aosp?
Sent from my ADR6425LVW using Tapatalk 2
prototype7 said:
Here's a better guide for it, I'll update the OP in a minute: http://rootzwiki.com/topic/27003-root-dinc2-on-any-firmware-may-want-to-sticky-later/
Edit: OP updated.
Click to expand...
Click to collapse
Trying this now. Hopefully it fixes the
Code:
cannot create /data/local.prop: permission denied
errors other people and myself are seeing.
---------- Post added at 02:46 PM ---------- Previous post was at 02:03 PM ----------
worked until i ran the tacoroot.sh --root command. Didn't root my phone and left me hanging at
Code:
adb shell chmod 777 /data/local/misc_version
adb shell /data/local/sh -c '/data/local/tmp/misc_version -s 2.18.605.3'
after --root this is what i received.
Code:
Usage:
--recovery : For this exploit to work, you must have booted recovery at least on
ce after your last factory reset.
--setup : Setup the phone for root, must be done before --root.
--root : Root the phone.
--undo : Remove TacoRoot.
----------
Rebooting into root.
C:\Program Files (x86)\Android\android-sdk\platforms>abd shell chmod 777 /data/l
ocal/misc_version
'abd' is not recognized as an internal or external command,
operable program or batch file.
C:\Program Files (x86)\Android\android-sdk\platforms>adb shell chmod 777 /data/l
ocal/misc_version
Unable to chmod /data/local/misc_version: No such file or directory
C:\Program Files (x86)\Android\android-sdk\platforms>adb shell /data/local/sh -c
'/data/local/tmp/misc_version -s 2.18.605.3'
/data/local/sh: not found
C:\Program Files (x86)\Android\android-sdk\platforms>
dets34 said:
Trying this now. Hopefully it fixes the
Code:
cannot create /data/local.prop: permission denied
errors other people and myself are seeing.
---------- Post added at 02:46 PM ---------- Previous post was at 02:03 PM ----------
worked until i ran the tacoroot.sh --root command. Didn't root my phone and left me hanging at
Code:
adb shell chmod 777 /data/local/misc_version
adb shell /data/local/sh -c '/data/local/tmp/misc_version -s 2.18.605.3'
after --root this is what i received.
Code:
Usage:
--recovery : For this exploit to work, you must have booted recovery at least on
ce after your last factory reset.
--setup : Setup the phone for root, must be done before --root.
--root : Root the phone.
--undo : Remove TacoRoot.
----------
Rebooting into root.
C:\Program Files (x86)\Android\android-sdk\platforms>abd shell chmod 777 /data/l
ocal/misc_version
'abd' is not recognized as an internal or external command,
operable program or batch file.
C:\Program Files (x86)\Android\android-sdk\platforms>adb shell chmod 777 /data/l
ocal/misc_version
Unable to chmod /data/local/misc_version: No such file or directory
C:\Program Files (x86)\Android\android-sdk\platforms>adb shell /data/local/sh -c
'/data/local/tmp/misc_version -s 2.18.605.3'
/data/local/sh: not found
C:\Program Files (x86)\Android\android-sdk\platforms>
Click to expand...
Click to collapse
Interesting. Looking over the code and tacoroot.sh, nothing actually puts the misc_version where it needs to be lol. Updated the instructions and added "adb push misc_version /data/local" before "adb shell chmod...", try that.
yeah i was just going to say looks like a the push misc_version was missing which solved everything for me.
as for others with this problem if the push misc_version doesn't seem to help i'd take a loot at this post here http://forum.xda-developers.com/showthread.php?t=1526316 for manually changing the version.
s-offffffed
dets34 said:
yeah i was just going to say looks like a the push misc_version was missing which solved everything for me.
as for others with this problem if the push misc_version doesn't seem to help i'd take a loot at this post here http://forum.xda-developers.com/showthread.php?t=1526316 for manually changing the version.
s-offffffed
Click to expand...
Click to collapse
So it worked?

Categories

Resources