G2 2.3.4 OTA 1-Click temp-root - G2 and Desire Z General

Thanks for the move orb3000
EDIT:
Apparently I can't post links either... what gives??? Going to have to do this the ghetto way I guess..
Anyway, I made a nice little .bat to temp-root the 2.3.4 OTA for the T-Mobile G2 (HTC Vision) for all you lazy people out there, or the people who are just tired of playing with the cmd (like myself).
It's on media fire... www(dot)mediafire(dot)com/?xwurdlpcw61oxiz
Just unzip and run "rootg2.bat"
It uses fre3vo, as it is the only method that currently works. If this for some reason does NOT work for you, edit rootg2.bat and change the address set to one of the following after a reboot
FAA90000 -end FFFFFFFF
10000000 -end 1FFFFFFF
20000000 -end 2FFFFFFF
30000000 -end 3FFFFFFF
F0000000 -end FFFFFFFF
E0000000 -end EFFFFFFF
Find one that works?? Great! Now you have a bat juuuuuust for you.
Long time lurker, first time poster, micro sized developer.

how to install
hi, i'm not very good with this. can you let me know how to install the g2root file on my g2? by the way, is this a permanent root? thx

tntx said:
hi, i'm not very good with this. can you let me know how to install the g2root file on my g2? by the way, is this a permanent root? thx
Click to expand...
Click to collapse
It says in the title this is a temporary root, not permanent. Check the [REF] Sticky is either General or Development for guides that will help you through the proces. DO NOT attempt root until you are sure you know what you are doing. READ and SEARCH!

Does anyone know of a way to temp-root on-device, without having to hook up to a PC?

After the message "daemon started successfully" the adb just hangs at that line, no crash, just doesn't advance any further. I can't input any commands either. I waited for over an hour to see if it would proceed, but not as such. Any ideas?

RebelScum75 said:
Does anyone know of a way to temp-root on-device, without having to hook up to a PC?
Click to expand...
Click to collapse
Hi!
I know that there is none
Have fun - Guhl

will this also work for the desire z ?

no dude ive been looking forever "finally had a reason to root the darn thing but i dont think there is one at least not that i have found--i work for verizon now anyways left my tmo--lol-----

dianlb50 said:
will this also work for the desire z ?
Click to expand...
Click to collapse
yes, basically same phone

Did this work for anyone?
Sent from my T-Mobile G2 using XDA App

I'm having issues getting this to work. I have tried the various addresses with no solid confirmation of whether it worked or not, aside from running the app "Root Check" or attempting to use an app that requires root, and finding that the phone is indeed, not rooted.
The results vary however at best, the process appears to have gone through smoothly. Daemon was successful, it successfully locates the region, and finally successfully dismounts and and remounts, which leaves us at the stage where it says press any key to continue.
Are there additional steps? What conditions must be met in order for this to work other than turning on debugging mode? Must the usb cord remain connected? Does the temp root end once the cord is unplugged? The guide above didn't exactly give any clear cut step-by-step directions and so I am feeling as if I'm not doing something because the guide doesn't mention it.
Can someone who has successfully temp-rooted their G2 v2.3.4 post a list of steps needed from start to finish? Example:
1) Enable USB debugging on phone.
2) Plug phone into computer via USB cord.
3) Unzip g2root.zip into a folder of your choice.
4) Run g2root.bat.
5) If successful, you will see (fill in the blank)
6) If successful, go to step 7, if unsuccessful, reboot computer/phone and retry step 1
Something like the above direct would be extremely useful to a few of us. Thanks!
-HobbesG2

Hello, I think this is my first post over here.
enable usb debugging on the phone
Plug phone into computer via USB
kill adb if it is already running:
Code:
./adb kill-server
start adb server as root:
Code:
sudo ./adb start-server
sample output:
Code:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Code:
./adb wait-for-device
and wait for this command to exit
Code:
./adb push /PUT/PATH/TO/G2ROOT/HERE/fre3vo /data/local/tmp
sample output:
Code:
218 KB/s (9796 bytes in 0.043s)
Code:
./adb -d shell chmod 777 /data/local/tmp/fre3vo
Code:
./adb -d shell /data/local/tmp/fre3vo -debug -start fb040000 -end FFFFFFFF
sample output:
Code:
fre3vo by #teamwin
Please wait...
Attempting to modify ro.secure property...
fb_fix_screeninfo:
id: msmfb
smem_start: 2fd00000
smem_len: 300000
type: 0
type_aux: 0
visual: 2
xpanstep: 0
ypanstep: 1
line_length: 1920
mmio_start: 0
accel: 0
fb_var_screeninfo:
xres: 480
yres: 800
xres_virtual: 480
yres_virtual: 1600
xoffset: 0
yoffset: 0
bits_per_pixel: 32
activate: 16
height: 80
width: 48
rotate: 0
grayscale: 0
nonstd: 0
accel_flags: 0
pixclock: 0
left_margin: 0
right_margin: 0
upper_margin: 0
lower_margin: 0
hsync_len: 0
vsync_len: 0
sync: 0
vmode: 0
Frame Buffer handle: 4
Buffer offset: 002ee000
Buffer size: 8192
Scanning region fb040000...
Scanning region fb130000...
Scanning region fb220000...
Scanning region fb310000...
Scanning region fb400000...
Scanning region fb4f0000...
Scanning region fb5e0000...
Scanning region fb6d0000...
Scanning region fb7c0000...
Scanning region fb8b0000...
Scanning region fb9a0000...
Scanning region fba90000...
Potential exploit area found at address fbb54e00:1200.
Exploiting device...
Code:
adb wait-for-device
Code:
./adb -d remount
sample output:
Code:
remount succeeded
verify you have root:
Code:
./adb -d shell id
output:
Code:
uid=0(root) gid=0(root)

Or you could verify it worked by executing 'adb shell' and if you have a # prompt rather than $, it worked.
This will stick until you reboot. Unplugging the cable will not affect it (unless you're currently running the commands)
This is not exactly a true temp-root, as it just gives adb root access, but you should be able to remount /system as rw and push su and SuperUser.apk to the right places to get a proper temp-root.
-Nipqer

Nipqer said:
you should be able to remount /system as rw and push su and SuperUser.apk to the right places to get a proper temp-root.
Click to expand...
Click to collapse
could you please describe how to do that? where do i get these packages from?

Getting closer but still not quite there. The reason why I was not having confirmations before was because I was running the rootg2.bat file directly rather than doing it through the cmd prompt, aka Start --> Run --> [type cmd]. After having ran the .bat file via the cmd prompt, I was able to apply, and confirm via the steps that were mentioned.
Problem is, I'm still not exactly truly temp-rooted, as none of my apps that require root or are designed to check root, show me as rooted. Is this because superuser and/or busybox are not operating as if they are rooted due to something I'm not aware of?
I already have the latest Superuser/Elite and BusyBox installed onto my phone via the Market. Do I have to push them into a specific folder that simply installing them from market wont do automatically?
Any thoughts?
After I get this nailed down, I will write a comprehensive explaination for others to do this as well.

Here is a true temp-root which works with fre3vo.
Just read the readme file.
-Nipqer

any update on this one?
i hope this makes rooting easier...

Nipqer said:
Here is a true temp-root which works with fre3vo.
Just read the readme file.
-Nipqer
Click to expand...
Click to collapse
I see this method listed for the Sensation, has it been proven to work for G2, stock OTA 2.3.4?

Wondering the same.

If you are running 2.3.x, and use fre3vo, then run that zip I posted, you will have proper temp-root.
It will stick until a reboot, but then you can just redo everything.
Yes it's proven to work.
-Nipqer

Related

[Gen8v2, A70B/A70IT2 Froyo] HOWTO: Enable SDE menus without Archos SDE firmware

Hi All,
As some may know, current Official SDE for gen8 doesn't work on the new Froyo Gen8 v2 devices (currently: A70b / A70it2).
As we do on Gen9, there is a way to enable SDE menu in recovery for the new Archos A70S/A70it2. It's quite easy and safe, it has been used multiple times on gen9 and only use Archos commands (except of course temp root that is done by using psneuter).
Disclaimer: I'm not responsible if you blow your device with this, I'm only using existing Archos commands but this is not an official Archos release. Use at your own risks.
If you don't know about SDE, check my Gen9 thread here, it has some pictures that could help (70it2 menus are not exactly the same but are similar).
So, to enable it:
1) You must have adb working, I won't detail how to install or use it here. "adb shell" should give you a '$' prompt, if it doesn't, check your adb installation first.
2) Unzip content of the attached file to a directory (or platform-tools if adb is not in your PATH)
3) Launch enable_sde.bat script (or enable_sde.sh for linux, don't forget to chmod 755 it)
4) It should display something like this:
Code:
5800 KB/s (557962 bytes in 0.093s)
4625 KB/s (2564188 bytes in 0.541s)
5000 KB/s (728825 bytes in 0.142s)
property service neutered.
killing adbd. (should restart in a second or two)
Generating KD...
Updating KD (3293269 bytes)...
0
100
4) If it worked properly (check file sizes, some had troubles with adb push), reboot in recovery with power+vol+, you should now see the SDE boot menu. If you go to recovery, you should see the and if you go to recovery, you should see the "Developer Edition Menu". If it doesn't work for you, please report in this thread.
Next step is to install a rooted build, you can find one here.
Cheers,
LeTama
Flawless victory...excellent.
Hello!
i get the following error:
Code:
D:\test>enable_sde.bat
D:\test>adb push psneuter /tmp
failed to copy 'psneuter' to '/tmp/psneuter': Permission denied
D:\test>adb push init_zImage /tmp
failed to copy 'init_zImage' to '/tmp/init_zImage': Permission denied
D:\test>adb push init-cpio.gz /tmp
failed to copy 'init-cpio.gz' to '/tmp/init-cpio.gz': Permission denied
D:\test>adb shell chmod 755 /tmp/psneuter
chmod: /tmp/psneuter: No such file or directory
D:\test>adb shell /tmp/psneuter
/bin/sh: /tmp/psneuter: not found
D:\test>ping 127.0.0.1 -n 5 -w 1000 1>nul
D:\test>adb shell /usr/bin/kd_flasher -i /tmp/init-cpio.gz -k /tmp/init_zImage
Generating KD...
cannot open kernel file: No such file or directory
mkflashimage failed
D:\test>adb shell sync
D:\test>
it is an archos A70it2.
Honeycomb or Froyo model ?
This one is for Froyo, I changed title to reflect it, sorry. Check my sig for the Honeycomb one...
Ok, it is the honeycomb model I will try the other one - thx!

[GUIDE] How to get root/flash custom roms with HTCDEV unlock

I know some people out there will use the new "official" htcdev.com unlock option for the G2/DZ, but they will still need to do **** to get root or flash custom roms.
I REALLY RECOMMEND USING THE XDA METHOD OF ACQUIRING ROOT AND S-OFF
S-OFF is possible! We can relock the bootloader to allow a downgrade
Go to FASTBOOT USB mode (where you got the unlock token code, and unlocked the bootloader)
Code:
fastboot oem lock
You can then downgrade by following this guide
And get S-OFF with this guide
DO NOT LOCK THE BOOTLOADER IF YOU DON'T WANT TO ROOT PROPERLY!
LOCKING THE BOOTLOADER WILL CAUSE THE REST OF THIS GUIDE TO FAIL!
-------------------------------------------------------------------------------------------------------------------
-------------------------------------------------------------------------------------------------------------------
First, some background as to why these methods are needed.
The HTC 'official' unlock method lets /system be written (given root access) in any mode.
The boot partition, and recovery are only writeable in fastboot mode though. So we need to flash a recovery through fastboot, flash a custom rom, then flash its boot image to be able to boot it.
GAINING ROOT ON STOCK ROM
Gaining Temp Root
DHD USERS WITH SENSE 3.x WILL HAVE TO USE TACOROOT
1. Download the attached files, unzip them, and place the files in your platform-tools folder. To elaborate, place the fre3vo file inside of the fre3vo.zip file in your platform-tools directory.
2. Run the following command to verify the exploit has access to what it needs. (Only the first line is the command. The second line should be the result returned if all goes well.)
Code:
> adb shell cat /dev/msm_rotator
[I]/dev/msm_rotator: invalid length[/I]
4. If you received the same message, you're good to continue on. If not... I'd recommend going back to #g2root and asking them. (I am just passing along the information after all).
5. Run the following commands from your platform-tools directory.
Code:
> adb push fre3vo /data/local/tmp
> adb shell
$ chmod 777 /data/local/tmp/fre3vo
$ /data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
6. After you enter that command, with luck you should see something similar to the last few lines in the following displayed. (It may take a minute or two. From what I can tell, this appears to be the quickest method as the exploit seems to be found in the latter regions.)
Code:
[I]Buffer offset: 00000000
Buffer size: 8192
Scanning region fb7b0000...
Scanning region fb8a0000...
Scanning region fb990000...
Scanning region fba90000...
Potential exploit area found at address fbb4d600:a00.
Exploiting device...[/I]
7. If you did get kicked out of adb shell, open it again. You should now see the lovely # instead of $, thus granting you temp root. Go ahead and exit out of shell to proceed to the next stage.
Code:
> adb shell
# exit
Getting Perm-Root
1. Download the attached file, "Vision-fre3vo-temp-root.zip".
2. Extract the contents to your platform-tools directory.
3. Run the following commands in command prompt while in platform-tools directory:
Code:
> adb push su /data/local/tmp/
> adb push busybox /data/local/tmp/
> adb push fixsu.sh /data/local/tmp/
> adb install SuperUser.apk
> adb shell chmod 755 /data/local/tmp/fixsu.sh
> adb shell chmod 755 /data/local/tmp/busybox
> adb shell /data/local/tmp/fixsu.sh
Note: If you get permission denied errors on busybox when trying to run fixsu.sh, please let me know.
4. Reboot phone, you should now have perm-root.
FLASHING A CUSTOM ROM
Flashing a custom recovery
Note: this only needs to be done once
1. Download a custom recovery: Latest Clockworkmod, Clockworkmod Touch, 4ext Touch
2. Place the recovery img in the folder with fastboot.exe (which you used to unlock your device), rename the recovery to recovery.img
3. Reboot phone to fastboot mode: Either pull battery and hold TRACKPAD and press power, or run 'adb reboot bootloader' from a cmd/terminal
4. Run
Code:
> fastboot flash recovery recovery.img
[I]sending 'recovery' (4930 KB)...
OKAY [ 0.851s]
writing 'recovery'...
OKAY [ 0.819s]
finished. total time: 1.670s[/I]
Flashing a custom rom
1. Download the rom.zip you wish to run.
2. Extract boot.img from the zip and place it in the folder with fastboot.
3. Copy the rom.zip to your sdcard
4. Flash the rom.zip from your sdcard
5. Reboot to fastboot mode (as above)
6. Run from a cmd/terminal
Code:
> fastboot flash boot boot.img
[I]sending 'boot' (4096 KB)...
OKAY [ 0.711s]
writing 'boot'...
OKAY [ 1.085s]
finished. total time: 1.798s[/I]
7. Reboot, you will now have a custom rom!
Credits:
Setherio, seeing as I ripped off half his guide.
Pierre_ja, helping figure out how to go about this.
If you get stuck with any of this, join #G2ROOT on freenode
-Nipqer
I'll try this ASAP. This bootloader have only brought me a **** load of headache, hope this works..
Thanks!
Yay a tester. let me know how it works.
We've had 1 person get root, and 2 flash custom roms with this, but I'd appreciate any feedback.
-Nipqer
fixsu.sh permissions denied
good to know that xda has people like you to help out
couldn't get root here's the result
C:\Android SDK\android-sdk\platform-tools>adb shell cat /dev/msm_rotator
/dev/msm_rotator: invalid length
C:\Android SDK\android-sdk\platform-tools>adb push fre3vo /data/local/tmp
869 KB/s (9796 bytes in 0.011s)
C:\Android SDK\android-sdk\platform-tools>adb shell
$ chmod 777 /data/local/tmp
chmod 777 /data/local/tmp
$ chmod 777 /data/local/tmp/fre3vo
chmod 777 /data/local/tmp/fre3vo
$ /data/local//tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
/data/local//tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
fre3vo by #teamwin
Please wait...
Attempting to modify ro.secure property...
fb_fix_screeninfo:
id: msmfb
smem_start: 802160640
smem_len: 3145728
type: 0
type_aux: 0
visual: 2
xpanstep: 0
ypanstep: 1
line_length: 1920
mmio_start: 0
accel: 0
fb_var_screeninfo:
xres: 480
yres: 800
xres_virtual: 480
yres_virtual: 1600
xoffset: 0
yoffset: 0
bits_per_pixel: 32
activate: 16
height: 80
width: 48
rotate: 0
grayscale: 0
nonstd: 0
accel_flags: 0
pixclock: 0
left_margin: 0
right_margin: 0
upper_margin: 0
lower_margin: 0
hsync_len: 0
vsync_len: 0
sync: 0
vmode: 0
Buffer offset: 00000000
Buffer size: 8192
Scanning region faa90000...
Scanning region fab80000...
Scanning region fac70000...
Scanning region fad60000...
Scanning region fae50000...
Scanning region faf40000...
Scanning region fb030000...
Scanning region fb120000...
Scanning region fb210000...
Scanning region fb300000...
Scanning region fb3f0000...
Scanning region fb4e0000...
Scanning region fb5d0000...
Scanning region fb6c0000...
Scanning region fb7b0000...
Scanning region fb8a0000...
Scanning region fb990000...
Scanning region fba80000...
Potential exploit area found at address fbb6e200:e00.
Exploiting device...
C:\Android SDK\android-sdk\platform-tools>adb shell
# exit
exit
C:\Android SDK\android-sdk\platform-tools>adb push su /data/local/tmp/
1205 KB/s (22228 bytes in 0.018s)
C:\Android SDK\android-sdk\platform-tools>adb push busybox /data/local/tmp/
1683 KB/s (1372660 bytes in 0.796s)
C:\Android SDK\android-sdk\platform-tools>adb push fixsu.sh /data/local/tmp/
109 KB/s (560 bytes in 0.005s)
C:\Android SDK\android-sdk\platform-tools>adb install Superuser.apk
1060 KB/s (196521 bytes in 0.181s)
pkg: /data/local/tmp/Superuser.apk
Success
C:\Android SDK\android-sdk\platform-tools>adb shell chmod 755 /data/local/tmp/fi
xsu.sh
C:\Android SDK\android-sdk\platform-tools>adb shell /data/local/tmp/fixsu.sh
/data/local/tmp/fixsu.sh: /data/local/tmp/busybox: permission denied
/data/local/tmp/fixsu.sh: /data/local/tmp/busybox: permission denied
/data/local/tmp/fixsu.sh: /data/local/tmp/busybox: permission denied
/data/local/tmp/fixsu.sh: /data/local/tmp/busybox: permission denied
C:\Android SDK\android-sdk\platform-tools>adb shell chmod 755 /data/local/tmp/fi
xsu.sh
C:\Android SDK\android-sdk\platform-tools>adb shell /data/local/tmp/fixsu.sh
/data/local/tmp/fixsu.sh: /data/local/tmp/busybox: permission denied
/data/local/tmp/fixsu.sh: /data/local/tmp/busybox: permission denied
/data/local/tmp/fixsu.sh: /data/local/tmp/busybox: permission denied
/data/local/tmp/fixsu.sh: /data/local/tmp/busybox: permission denied
C:\Android SDK\android-sdk\platform-tools>
Click to expand...
Click to collapse
Hmm, I wonder why thats happening...
Want to join the IRC channel so we can sort this out?
-Nipqer
how do i join?
EDIT: i'll do a full factory restore, format sdcard and try this out again
Go to http://webchat.freenode.net/
choose a nickname, in channels enter #G2ROOT (with the hash)
-Nipqer
Hi Guys.
I'm @ work, but gonna try this in my break asap.
Sorry if I have missed something, but don't you need the eng hboot in order to use "fastboot flash" ?
Sent from my Desire Z running CM7.
I've done everything as above.
Everything went just fine.
But when I start SetCPU, It comes up with "root acces not detected" did you allow setcpu through superuser permissions?
In the superuser app (which is visible) I can't edit anything?
Also, it's not showing a pop up with "allow"
Am I doing something wrong?
C:\>cd android
C:\Android>cd platform-tools
C:\Android\platform-tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
$ fastboot flash recovery recovery.img
fastboot flash recovery recovery.img
fastboot: permission denied
$
$ exit
exit
C:\Android\platform-tools>fastboot flash recovery recovery.img
< waiting for device >
steviewevie said:
Sorry if I have missed something, but don't you need the eng hboot in order to use "fastboot flash" ?
Sent from my Desire Z running CM7.
Click to expand...
Click to collapse
the hboot htc provides for the unlock supports fastboot commands, took us a while to figure that out at #g2root.
---------- Post added at 05:11 PM ---------- Previous post was at 05:08 PM ----------
wm6.5 said:
C:\>cd android
C:\Android>cd platform-tools
C:\Android\platform-tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
$ fastboot flash recovery recovery.img
fastboot flash recovery recovery.img
fastboot: permission denied
$
$ exit
exit
C:\Android\platform-tools>fastboot flash recovery recovery.img
< waiting for device >
Click to expand...
Click to collapse
you have to boot in fastboot mode to be able to issue fastboot commands:
from shell ($ or #) while the phone is connected to the computer:
Code:
exit
adb reboot bootloader
from normal win cmd (the > prompt):
Code:
adb reboot bootloader
petarpLab said:
the hboot htc provides for the unlock supports fastboot commands, took us a while to figure that out at #g2root.
Click to expand...
Click to collapse
Ok, cool, thanks for the info. That's something useful it does then.
Sent from my Desire Z running CM7.
wm6.5 said:
C:\>cd android
C:\Android>cd platform-tools
C:\Android\platform-tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
$ fastboot flash recovery recovery.img
fastboot flash recovery recovery.img
fastboot: permission denied
$
$ exit
exit
Click to expand...
Click to collapse
You need to run fastboot from your PC, not the phone
Sent from my Desire Z running CM7.
wm6.5: I don't know if SetCPU can work on stock roms with root. You might need a different kernel for it.
-Nipqer
Nipqer said:
Yay a tester. let me know how it works.
We've had 1 person get root, and 2 flash custom roms with this, but I'd appreciate any feedback.
-Nipqer
Click to expand...
Click to collapse
You sir, just made my day!
Guide works like a charm! thank you!
Nipqer, thanks Mate.
Got everything sorted out on G2root on irc!
Your guide is the .... thanks again!
Thanks this saved me! The guys on g2root irc are way too helpful! Much thanks to them, no thanks to HTC unlocker for wasting a day of my life.
Is there any way of getting S-Off after you've used the HTC Dev Unlock?
No, not yet. As soon as we have figured out a way I'll update the OP.
-Nipqer

Cant perm root Mytouch 4G please help before you move my thread

I have spent hours on xda, downloading gfree, trying to downgrade, trying taco root. I even unlocked bootloader at htc dev and cannot get my phone perm rooted
I have 2.3.4
software 2.32.531.1
i used the guide on how to downgrade to 2.2.1 for the visionary exploit
i keep getting permission denied
Potential exploit area found at address fbb80e00:200.
I am sorry for sounding like "noob" but i wasted the day trying to do this and have given up
Someone please help me, ill even donate a cup of coffee to whoever helps me fix this. No joke from 9 am to 530 pm, i have been going in circles, i downloaded the htc easy root tool all failed
the farthest i made it was getting temp root with taco root, but there are no clear cut instructions for what to do after, these guides are over a year old prior to my version of android
I'm not sure where your going wrong but the guides work fine. I used them to downgrade, perm root, and flash the engineering bootloader. Have you tried asking in the q and a section? I'm sure you will find a solution, if you ask in the proper place.
Sent from my HTC Glacier using Tapatalk
I would try this guide http://forum.xda-developers.com/showthread.php?p=15851661
Sent from my HTC Glacier using xda premium
i have been on here for 9 hours going through the q/a this is a brand new str8 from t-mobile mytouch 4g with the newest possible rom, a year ago i successfully did this dozens of time with visionary, its this new rom thats the problem, i put virtuous rom successfully on my first mytouch a year ago, and ive rooted my hd2 for friends and family, so i know my way around xda, this is the first time im truly stuck
cnote 74 i tried that guide my expolit area "fbb80e00:200" is not covered by that guide, if you look at the 5 or 6 lines
$ /data/local/tmp/fre3vo -debug -start 10000000 -end 1FFFFFFF
$ /data/local/tmp/fre3vo -debug -start 20000000 -end 2FFFFFFF
$ /data/local/tmp/fre3vo -debug -start 30000000 -end 3FFFFFFF
$ /data/local/tmp/fre3vo -debug -start F0000000 -end FFFFFFFF
$ /data/local/tmp/fre3vo -debug -start E0000000 -end EFFFFFFF
mine is different than all of these
this is what ive been getting, i followed the guide to the T
C:\AndroidSDK\platform-tools>adb shell cat /dev/msm_rotator
adb server is out of date. killing...
* daemon started successfully *
/dev/msm_rotator: invalid length
C:\AndroidSDK\platform-tools>adb push fre3vo /data/local/tmp
869 KB/s (9796 bytes in 0.011s)
C:\AndroidSDK\platform-tools>adb shell
$ chmod 777 /data/local/tmp/fre3vo
chmod 777 /data/local/tmp/fre3vo
$ /data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
/data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
fre3vo by #teamwin
Please wait...
Attempting to modify ro.secure property...
fb_fix_screeninfo:
id: msmfb
smem_start: 802160640
smem_len: 3145728
type: 0
type_aux: 0
visual: 2
xpanstep: 0
ypanstep: 1
line_length: 1920
mmio_start: 0
accel: 0
fb_var_screeninfo:
xres: 480
yres: 800
xres_virtual: 480
yres_virtual: 1600
xoffset: 0
yoffset: 800
bits_per_pixel: 32
activate: 16
height: 80
width: 48
rotate: 0
grayscale: 0
nonstd: 0
accel_flags: 0
pixclock: 0
left_margin: 0
right_margin: 0
upper_margin: 0
lower_margin: 0
hsync_len: 0
vsync_len: 0
sync: 0
vmode: 0
Buffer offset: 00000000
Buffer size: 8192
Scanning region faa90000...
Scanning region fab80000...
Scanning region fac70000...
Scanning region fad60000...
Scanning region fae50000...
Scanning region faf40000...
Scanning region fb030000...
Scanning region fb120000...
Scanning region fb210000...
Scanning region fb300000...
Scanning region fb3f0000...
Scanning region fb4e0000...
Scanning region fb5d0000...
Scanning region fb6c0000...
Scanning region fb7b0000...
Scanning region fb8a0000...
Scanning region fb990000...
Scanning region fba80000...
Potential exploit area found at address fbb6c400:c00.
Exploiting device...
C:\AndroidSDK\platform-tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
# exit
exit
C:\AndroidSDK\platform-tools>adb push misc_version /data/local/tmp/misc_version
1718 KB/s (15837 bytes in 0.009s)
C:\AndroidSDK\platform-tools>adb shell chmod 777 /data/local/tmp/
C:\AndroidSDK\platform-tools>adb shell
# cd /data/local/tmp
cd /data/local/tmp
# ./misc_version -s 1.00.000.0
./misc_version -s 1.00.000.0
./misc_version: permission denied
#
1st off.......THIS IS THE DEVELOPMENT SECTION! NOT Q&A! THATS WHAT THE Q&A IS FOR!
2nd....its because you unlocked via htcdev, which we have warned users multiple times if you did read the Q&A and General forums.
Htcdev method makes it harder to root/flash a ROM. We warned you. And then you complain and post in the wrong section!
Edit: also.....If you knew to put "DON'T MOVE THREAD", why did you post it here in the first place?
Sent from my HoneySmartDroid Port using XDA Premium.
Edit: I like that better /\
Sent from my HTC Glacier using Tapatalk
Chek this out bro hope it help ;-) http://forum.xda-developers.com/showthread.php?p=9551846
Sent from my HTC Mytouch 4G using xda premium
still stuck invasion2 you have a solution
michael.racelli said:
still stuck invasion2 you have a solution
Click to expand...
Click to collapse
Sorryf for flaming.....anyway I did find something... http://www.forum.xda-developers.com/showthread.php?p=21563546
Sent from my HoneySmartDroid Port using XDA Premium.
michael.racelli said:
I have spent hours on xda, downloading gfree, trying to downgrade, trying taco root. I even unlocked bootloader at htc dev and cannot get my phone perm rooted
I have 2.3.4
software 2.32.531.1
i used the guide on how to downgrade to 2.2.1 for the visionary exploit
i keep getting permission denied
Potential exploit area found at address fbb80e00:200.
I am sorry for sounding like "noob" but i wasted the day trying to do this and have given up
Someone please help me, ill even donate a cup of coffee to whoever helps me fix this. No joke from 9 am to 530 pm, i have been going in circles, i downloaded the htc easy root tool all failed
the farthest i made it was getting temp root with taco root, but there are no clear cut instructions for what to do after, these guides are over a year old prior to my version of android
Click to expand...
Click to collapse
no need to downgrade
http://forum.xda-developers.com/showthread.php?t=803682
I relocked the bootloader, still the same thing permission denied, am i the only one who has encountered this issue, i cannot root downgrade right now if my life depended on it right now
adb push misc_version /data/local/tmp/misc_version
> adb push flashgc /data/local/tmp/flashgc
> adb shell chmod 777 /data/local/tmp/* <--------(THIS LINE IS YOUR MISTAKE)
> adb shell
# cd /data/local/tmp
# ./misc_version -s 1.00.000.0
--set_version set. VERSION will be changed to: 1.00.000.0
Patching and backing up partition 17...
# ./flashgc
Click to expand...
Click to collapse
Click to expand...
Click to collapse
From what I gathered on your post, I am thinking you did a pastebin which is good. If you did, and it copied straight from you command prompt, than you are missing an (*) at the end of the adb chmod 777 /data/local/tmp/.
I recently used the guide to downgrade/root/flash e-bootloader/flash rom on 2 brand new 2.3.4 mytouch 4gs 2 weeks ago.
Also if you can manage to safe some time and headache reformat your SD card with the PD15IMG on to to fat32. If you dont you have a very likely chance that when you attempt to flash the PD15IMG to get a no image or bad image error in your bootloader when downgrading.
Slow down, step away from the computer, take a break and come back and START OVER. I spent 2 days getting that damned error on the pd15img.
edit:The quoted text is from the downgrading guide.
thank you for responding but that link you sent me shows up as a dead link, didnt go anywhere bro
michael.racelli said:
thank you for responding but that link you sent me shows up as a dead link, didnt go anywhere bro
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=15851661
This is the downgrading guide that I believe you have been using. Its the same I used. Like I said start over, and make sure every line in your cmd is typed exactly the way it is written in the thread.
If you feel you must, you can even copy and paste line by line into command prompt
Heh, sorry. Here you are! http://forum.xda-developers.com/showthread.php?p=21563546
hellmonger said:
no need to downgrade
http://forum.xda-developers.com/showthread.php?t=803682
Click to expand...
Click to collapse
Hellmonger, I never got superoneclick to work on 2.3.4 mytouch 4g. Tried it and it gets stuck on the psneuter
---------- Post added at 06:48 PM ---------- Previous post was at 06:46 PM ----------
invasion2 said:
Heh, sorry. Here you are! http://forum.xda-developers.com/showthread.php?p=21563546
Click to expand...
Click to collapse
This is for the desire/g2 it wont work. Use the link I posted.
. . .
knew someone was gonna take me the wrong way. deleted.
seeing from what other users have posted, it seems that you have "unlocked" your bootloader the Official HTC way. then there's not much anyone here can do for you, since that way wasn't recommended anyway.
but since your bootloader is now "unlocked", i don't see why you need to follow the downgrade procedure anymore. from looking at other device forums, i see that all you gotta do is get a custom recovery on there somehow, flash a rooted ROM, flash the boot image of that ROM (since you decided to do it the HTC way) and that's pretty much it...
Contacting a mod at once...
^^^^^^^ I did the same -______-

Someone please HELPP! Before...

Okay...so here Iam once more driving myself insane. I'am pretty intermediate with devices and rooting and can usually do things solo or with slight help...but!!. So just received the device from a friend of mine and I actually want to unlock it to allow Simple Mobile (sim card) and services...when i Hboot it says Radio ON...to what i presume will be the freedom I need. Okay so here goes my trouble... I know that your supposed to downgrade the device to root, or temp root, I have been following the instructions to the T (or at least I'm hoping so) on http://forum.gsmhosting.com/vbb/f62...ouch-4g-2-3-4-hb-0-89-0005-stock-rom-1344617/ and even on this site which is where i also have tried following the directions. Okay so what confuses me is that one post says tools, the other says platform-tools..and if i'm incorrect the directory has both. Okay so I've opened up a command line from both and it's around
$ adb push fre3vo /sdcard/fre3vo
$ adb shell
$ chmod 777 /data/local/tmp/fre3vo
$ /data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
that I start to have my trouble!! I was actually able to copy this...
C:\AndroidSdk\platform-tools> adb push fre3vo /sdcard/fre3vo
adb server is out of date. killing...
* daemon started successfully *
cannot stat 'fre3vo': No such file or directory <---is this the error file im supposed to get?? so I rewrite it connecting the sdcard to fre3vo and then wallah!! A whole bunch of writing like ...
C:\AndroidSdk\platform-tools> adb push fre3vo/sdcard/fre3vo
Android Debug Bridge version 1.0.31 <------------------------Right over here (excessive content so i deleted)
C:\AndroidSdk\platform-tools>adb shell
$ chmod 777 /data/local/tmp/fre3vo
chmod 777 /data/local/tmp/fre3vo
Unable to chmod /data/local/tmp/fre3vo: No such file or directory
$ /data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
/data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
/data/local/tmp/fre3vo: not found <---------------------------So I go down through the line of codes I'm supposed to trty and all say not found
$
Now as you can see this is where my problems arise. Every code or set of codes I get result in not found?? What am I doing wrong? I saw a tutorial on youtube and when he added this coding it was immediately followed by a massive amount of writing and then ADB seems to have shut down...Am i supposed to have ADB running while I do this? I've even tried rewriting the codes thinking that maybe a space was misplaced or such. Please help guys. Also what I did was manually created a directory at C;\Adroidsdk since there was none and placed all of the adb tools there or hope I did. Before that every time I'd open the executable the adb program would open from C\users\appdata\local\temp. I honestly don't know where i went wrong. I really want to root this phone. I went as far as spending 30 dollars on one of those bogus websites that can "root your device guaranteed" only to find that the programs they had like Superoneclick I already had on my desktop. Go figure..Ok I will sit here miserably until one of you rescues me. Thanks.
Some people said they used this tool to root.
http://forum.xda-developers.com/showthread.php?t=1870652
I personally have not tried it, but hey, you never know
Did you unzip the files before putting them in platform tools?
Also shouldn't you be pushing the file to the folder you are trying to chmod? It looks like you are pushing it to sdcard and I'm pretty sure it needs to be in the tmp folder:
adb push fre3vo /data/local/tmp
Instead of sdcard, but don't quote me on that I haven't done this in ages. Trying it *shouldn't* break anything... I think
If you can't push it to tmp then you are missing steps.
Edit:
Found an xda thread that verifies the file should be pushed to data local tmp
http://forum.xda-developers.com/showthread.php?t=1178912
Shame on the person who wrote the other guide.
If u already got s-off (cuz u might have to downgrade) or still in fryo u can try vissionary+ method efficient stressless
N_otori0us_ said:
Some people said they used this tool to root.
http://forum.xda-developers.com/showthread.php?t=1870652
I personally have not tried it, but hey, you never know
Click to expand...
Click to collapse
yeAh this is one of the tools the $30 dollar spot gave me. Funny because it actually says it worked..Su installed Busybox installed and once process is done..Nada..zip..is still the same now to convince them of a refund.
Relsig said:
Did you unzip the files before putting them in platform tools?
Also shouldn't you be pushing the file to the folder you are trying to chmod? It looks like you are pushing it to sdcard and I'm pretty sure it needs to be in the tmp folder:
adb push fre3vo /data/local/tmp
Instead of sdcard, but don't quote me on that I haven't done this in ages. Trying it *shouldn't* break anything... I think
If you can't push it to tmp then you are missing steps.
Edit:
Found an xda thread that verifies the file should be pushed to data local tmp
http://forum.xda-developers.com/showthread.php?t=1178912
Shame on the person who wrote the other guide.
Click to expand...
Click to collapse
Yeah, I've actually tried it this way and the other. the thing is one site says tools..the other platform tools, and then this last one sd card?? I've tried them all I think...Maybe my adb is installed in the wrong area? could that be why possibly after i chmod and start putting in the files to finally root the phone it says "file not found"? I know it's alot of writing but I'm going to copy and paste everything on a new reply to see if you or anyone can see what I'm doing wrong. I even copy and paste to the cmd and nothing.
ughoji said:
If u already got s-off (cuz u might have to downgrade) or still in fryo u can try vissionary+ method efficient stressless
Click to expand...
Click to collapse
If you could find me a place to download visionary from I'd be eternally grateful to you. It seems when they banned the app from google they must've done so everywhere else. Everytime I try to download my PC stops the download and says virus detected even with anti-virus off. Every time I go to the Visionary website and click the download link it takes me to some bogus website and never to the download link. The other sites I've found them on them on the PC says Virus detected...or maybe it's google chrome. Think I should try downloading on Internet Explorer?
what i'm gonna do guys is try the process from the xda website and then post it to see if one of you detect where I went wrong. Crossing Fingers...
now here it is ladies and gents...maybe we can find the problem here somewhere
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Jorge>adb shell cat /dev/msm_rotator
/dev/msm_rotator: invalid length
C:\Users\Jorge>cd c:\androidsdk\platform-tools
c:\AndroidSdk\platform-tools>adb push fre3vo /data/local/tmp
adb server is out of date. killing...
* daemon started successfully *
cannot stat 'fre3vo': No such file or directory <-- here also i get the no file or directory error so then i rewrite putting fre3vo and data together which follows with fre3vo/data
c:\AndroidSdk\platform-tools>adb push fre3vo/data/local/tmp
Android Debug Bridge version 1.0.31
-d - directs command to the only connected USB devic
e
returns an error if more than one USB device is
present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <specific device> - directs command to the device or emulator with
the given
serial number or qualifier. Overrides ANDROID_S
ERIAL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
devices [-l] - list all connected devices
('-l' will also list device qualifiers)
connect <host>[:<port>] - connect to a device via TCP/IP
Port 5555 is used by default if no port number
is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 5555 is used by default if no port number
is specified.
Using this command with no additional arguments
will disconnect from all connected TCP/IP devic
es.
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> [<local>] - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(-l means list but don't copy)
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-s] [--algo <algorithm name> --key <hex-encoded key> --
iv <hex-encoded iv>] <file>
- push this package file to the device and instal
l it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
('-s' means install on SD card instead of inter
nal storage)
('--algo', '--key', and '--iv' mean the file is
encrypted already)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories
)
adb bugreport - return all information from the device
that should be included in a bug report.
adb backup [-f <file>] [-apk|-noapk] [-shared|-noshared] [-all] [-system|-nosy
stem] [<packages...>]
- write an archive of the device's data to <file>
.
If no -f option is supplied then the data is wr
itten
to "backup.ab" in the current directory.
(-apk|-noapk enable/disable backup of the .apks
themselves
in the archive; the default is noapk.)
(-shared|-noshared enable/disable backup of the
device's
shared storage / SD card contents; the defau
lt is noshared.)
(-all means to back up all installed applicatio
ns)
(-system|-nosystem toggles whether -all automat
ically includes
system applications; the default is to inclu
de system apps)
(<packages...> is the list of applications to b
e backed up. If
the -all or -shared flags are passed, then t
he package
list is optional. Applications explicitly g
iven on the
command line will be included even if -nosys
tem would
ordinarily cause them to be omitted.)
adb restore <file> - restore device contents from the <file> backup
archive
adb help - show this help message
adb version - show version num
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb get-devpath - prints: <device-path>
adb status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on th
e specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be u
pdated.
- If it is "system" or "data", only the corresponding partition
is updated.
environmental variables:
ADB_TRACE - Print debug information. A comma separated list
of the following values
1 or all, adb, sockets, packets, rwx, usb, sync
, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes prior
ity over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these de
bug tags are printed.
c:\AndroidSdk\platform-tools>adb shell
$ chmod 777 /data/local/tmp/fre3vo
chmod 777 /data/local/tmp/fre3vo
Unable to chmod /data/local/tmp/fre3vo: No such file or directory <--when i input chmod 777 /data/local/tmp/fre3vo it says no such file...so i
$ chmod 777/data/local/tmp/fre3vo rewrite it and connect the 777 to data like chmod 777/data and then
chmod 777/data/local/tmp/fre3vo the usahe chmod ...etc.
Usage: chmod <MODE> <FILE>
$ /data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
/data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
/data/local/tmp/fre3vo: not found
$ <-----I can continue and write the other passwords but it says not found.
I'm wondering if i might've installed adb in the wrong place and if so how do i change the variables? should i put C:android or as currently ANDROID_SDK_HOME then C:\AndroidSdk
There's no wrong place to install adb. If your in GingerBread, I don't think visionary will work. Try ginger break. But you have to downgrade to root your phone. If your on 2.3.4, you gotta get on 2.2.1 I think
Sent from my myTouch 4G using xda app-developers app
N_otori0us_ said:
There's no wrong place to install adb. If your in GingerBread, I don't think visionary will work. Try ginger break. But you have to downgrade to root your phone. If your on 2.3.4, you gotta get on 2.2.1 I think
Sent from my myTouch 4G using xda app-developers app
Click to expand...
Click to collapse
yeA
YEAH PHONE IS ON 2.3.4...ooops sorry for caps! so can you see where i might've went wrong? I mean is it supposed to say file not found or those things? somewhere i messed up..sigh...
c:\AndroidSdk\platform-tools>adb push fre3vo /data/local/tmp
adb server is out of date. killing...
* daemon started successfully *
cannot stat 'fre3vo': No such file or directory
Is fre3vo in C:\AndroidSdk\platform-tools?
cause thats where you need to unzip the files to
-Nipqer
Found the problem...
Thanks to you guys I went back step by step and figured out the problem . So apparently when i had originally downloaded the fre3vo and misc files they were the wrong files. I looked inside of platform tools and both files were there as applications?? yeah like actual install type applications..finally it has all seemed to work so i'll now move on to step two...won't say im done till ive succesfully rooted and ill keep you posted but thank you guys.,.for your time and dedication towards helping me :_)
Playdoe said:
Thanks to you guys I went back step by step and figured out the problem . So apparently when i had originally downloaded the fre3vo and misc files they were the wrong files. I looked inside of platform tools and both files were there as applications?? yeah like actual install type applications..finally it has all seemed to work so i'll now move on to step two...won't say im done till ive succesfully rooted and ill keep you posted but thank you guys.,.for your time and dedication towards helping me :_)
Click to expand...
Click to collapse
Just in case u wanted to root an s-off phone search pd15img(2.2.1).zip got mine from 4shared rename it to pd15img.zip and move it to root of your SD card boot into bootloader navigate to the second option then OK with power on to downgrade. here is a working visionary but note most cases play store doesn't agree to download make sure u got explore or es in another phone to send it run your rooting and every.the visionary process is in the dev part its pinned
I used visionary and it worked for me

Problem with rooting MyTouch 4G Phone ($ exploit error)

Hello,
I have had my MyTouch 4G since January of 2011, and today I decided to finally root my phone (growing sick and tired of HTC sense and the tremendous bloatware lag with it). I still like the phone itself (perfect size), and so I was came across CM7, it looks like it is the most stable and popular rom for the MyTouch.
Of course, I myself, I am an IT professional, but have no idea on what the rooting process is, so I have been following the steps CM team has posted on rooting my android device (wiki(dot)cyanogenmod(dot)org/w/Install_CM_for_glacier). I was currently in the process of downgrading the android version, and came across an error. So according to this guide, it said if you come across an $, your exploit has failed, if # you have gained temporary root.
That being said, I have came across the $ sign, which I assume is the exploit. I don't know why I have come across this error, and so, I have posted all the notes from my command line:
C:\adt-bundle-windows-x86-20130729\sdk\platform-tools> ad
local/tmp
1366 KB/s (9796 bytes in 0.007s)
C:\adt-bundle-windows-x86-20130729\sdk\platform-tools> ad
/data/local/tmp
1882 KB/s (589849 bytes in 0.306s)
C:\adt-bundle-windows-x86-20130729\sdk\platform-tools> ad
/local/tmp
1753 KB/s (712688 bytes in 0.397s)
C:\adt-bundle-windows-x86-20130729\sdk\platform-tools> ad
chmod 777 /data/local/tmp/fre3vo
chmod 777 /data/local/tmp/misc_version
chmod 777 /data/local/tmp/flashgc
/data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFF
adb shell
cd /data/local/tmp
./misc_version -s 1.00.000.0
./flashgc
exit $ chmod 777 /data/local/tmp/fre3vo
./misc_version -s 1.00.000.0
./flashgc
$ chmod 777 /data/local/tmp/misc_version
$ chmod 777 /data/local/tmp/flashgc
$ /data/local/tmp/fre3vo -debug -start FAA90000 -end FFF
fre3vo by #teamwin
Please wait...
Attempting to modify ro.secure property...
fb_fix_screeninfo:
id: msmfb
smem_start: 2fd00000
smem_len: 300000
type: 0
type_aux: 0
visual: 2
xpanstep: 0
ypanstep: 1
line_length: 1920
mmio_start: 0
accel: 0
fb_var_screeninfo:
xres: 480
yres: 800
xres_virtual: 480
yres_virtual: 1600
xoffset: 0
yoffset: 800
bits_per_pixel: 32
activate: 16
height: 80
width: 48
rotate: 0
grayscale: 0
nonstd: 0
accel_flags: 0
pixclock: 0
left_margin: 0
right_margin: 0
upper_margin: 0
lower_margin: 0
hsync_len: 0
vsync_len: 0
sync: 0
vmode: 0
Frame Buffer handle: 4
Buffer offset: 002ee000
Buffer size: 8192
Scanning region faa90000...
Scanning region fab80000...
Scanning region fac70000...
Scanning region fad60000...
Scanning region fae50000...
Scanning region faf40000...
Scanning region fb030000...
Scanning region fb120000...
Scanning region fb210000...
Scanning region fb300000...
Scanning region fb3f0000...
Scanning region fb4e0000...
Scanning region fb5d0000...
Scanning region fb6c0000...
Scanning region fb7b0000...
Scanning region fb8a0000...
Scanning region fb990000...
Scanning region fba80000...
Scanning region fbb70000...
Potential exploit area found at address fbbb5600:1a00.
Exploiting device...
I hope someone can help me out on this one... would be awesome if I can manage to root my phone and install the ROM all by today...
Thanks!
Bump bump bump bump bump
please i need help!!
UPDATE: I HAVE GONE PAST THIS ERROR.
Now, my current situation, I had followed the root guide that was stickied on this forums, and it looks like my "S=Off" is on the HBoot loader thing (when you press power + volume down). But, when I try to follow the steps of flashing an actual ROM (through clockworkmod) it says I am not rooted? Any idea on how to fix that?
Been working on this phone for over 15 hours... and will only go to sleep once I know I will have my ROM installed.
How can clockworkmod tell you your not rooted? Have you already flashed a recovery?
Also try this to re-root
http://forum.xda-developers.com/showthread.php?t=1343114
Then install the 4ext app and let it install the recovery.
N_otori0us_ said:
How can clockworkmod tell you your not rooted? Have you already flashed a recovery?
Also try this to re-root
http://forum.xda-developers.com/showthread.php?t=1343114
Then install the 4ext app and let it install the recovery.
Click to expand...
Click to collapse
Actually, I have no idea why is that O.O
But I will follow those steps on that link you send me, and post an update if it all works out!!
Thanks a lot!
So, after trying out that link that was posted earlier, it looks like I have found my real problem now.
My S=off looks like is permanent. But my root is not (I dunno why, no flash or anything yet)
So when I try to connect my phone to my PC (USB Debug Mode on, USB Tethering) it doesn't connect anymore, nor show up on ADB. And in fact my PDAnet driver does not detect it either!
Any idea on what can be the problem?
Update:
I am done!! I installed cm10!! It works
omg, this is awesome!!
sorry for making this thread, i managed to re-root it and now it all worked out.
I love you xda developers, i apologize for making a thread, i managed to research all my information and it worked after 25+ hours of working on my phone.
darkgiant said:
Update:
I am done!! I installed cm10!! It works
omg, this is awesome!!
sorry for making this thread, i managed to re-root it and now it all worked out.
I love you xda developers, i apologize for making a thread, i managed to research all my information and it worked after 25+ hours of working on my phone.
Click to expand...
Click to collapse
You thought the mytouch was hard to root. Try the Panache lol.
Sent from my HTC Glacier using xda app-developers app
N_otori0us_ said:
You thought the mytouch was hard to root. Try the Panache lol.
Sent from my HTC Glacier using xda app-developers app
Click to expand...
Click to collapse
haha, that is the older version right?
Honestly, it was not hard at all, the fact is that the information provided, is all cluttered around the interwebz (requireing actual hours of researching) and to find that perfect stable rom is another animal... haha.
I don't feel like buying another smartphone, I know that the mytouch 4g is still capable of competing with smartphones in the market (of course, it has no fancy camera or gimmicks like the S4) but it works!
darkgiant said:
haha, that is the older version right?
Honestly, it was not hard at all, the fact is that the information provided, is all cluttered around the interwebz (requireing actual hours of researching) and to find that perfect stable rom is another animal... haha.
I don't feel like buying another smartphone, I know that the mytouch 4g is still capable of competing with smartphones in the market (of course, it has no fancy camera or gimmicks like the S4) but it works!
Click to expand...
Click to collapse
Naa it's not the older version... Its the Canadian version
Sent from my HTC Glacier using xda app-developers app
I guess for any moderators preference, I am open to compiling how I went about my situations and such if this is a persistent issue! If not, feel free to close this topic, as my problems are now all solved (THANKFULLY!)
~Darkgiants

Categories

Resources