Related
hi
have a problem with my htc magic
sapphire pvt 32b ship s-on g
hboot-1.33.0004 (sapp10000)
cpld-10
radio-2.22.19.261
apr 9 2009,23:30:40
and android froyo 2.2 cyanogenmod 6-310710-artifexed.v03
my problem 1 is this : i have wifi signal only im 2-3meters about router but still low signal
my problem 2 is : cannot connect to gps satelite( gps looking for satelite and thats all )
problem 3 : ram : i do wipe and restart mobile go on loading system but free ram only 24mb from 196mb ( where is problem ?)
if i want root mobile (super one click)
click on root but break on
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
SuperOneClick v1.7.0.0
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Pushing rageagainstthecage...
337 KB/s (5392 bytes in 0.015s)
OK
chmod rageagainstthecage...
OK
Running rageagainstthecage...
ROOTED
Pushing busybox...
1230 KB/s (1062992 bytes in 0.843s)
OK
chmod busybox...
OK
Getting mount path...
/dev/block/mtdblock3
OK
Reading OS Version properties...
Version: 2.2
OK
Remounting system with read-write access...
OK
Pushing su-v2...
820 KB/s (26264 bytes in 0.031s)
OK
chmod su...
OK
Creating /system/xbin...
mkdir failed for /system/xbin, File exists
OK
Copying busybox (/system/xbin/)...
cp: can't create '/system/xbin/busybox': File exists
OK
chmod busybox (/system/xbin/)...
chmod: /system/xbin/busybox: Read-only file system
OK
Installing busybox (/system/xbin/)...
--install: applet not found
FAILED
ro.board.platform=msm7k
ro.product.locale.region=US
ro.product.brand=google
ro.product.device=dream_sapphire
ro.product.model=Dream/Sapphire
ro.build.date.utc=1280565228
ro.build.date=Sat Jul 31 08:33:48 UTC 2010
ro.build.version.codename=REL
ro.build.product=dream_sapphire
ro.product.cpu.abi=armeabi
ro.build.tags=test-keys
ro.product.manufacturer=HTC
ro.product.name=cyanogen_dream_sapphire
ro.build.type=user
ro.build.fingerprint=ver
ro.build.host=fembot
ro.build.version.sdk=8
ro.product.board=sapphire
ro.build.display.id=FRF91
ro.build.id=FRF91
ro.product.locale.language=en
ro.build.description=cyanogen_dream_sapphire-eng 2.2 MASTER eng.ctso.20100731.083208 test-keys
ro.build.version.release=2.2
ro.build.user=ctso
ro.build.version.incremental=eng.ctso.20100731.083208
ro.wifi.channels=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
and dont continue. where is problem pls
can you tell me somethink about this version system for better system work pls
sorry for my english im czech
thanks for help!
Since you've got Cyanogenmod loaded then you've already got root permissions and don't need to re-root. Do you already have a custom recovery installed? If so, I would just try reflashing the ROM or flashing a different ROM.
i have this mobile a 3 days
i dont know who installed os to this mobile
and question this android froyo 2.2 cyanogenmod 6-310710-artifexed.v03 dont want new radio ?
and exists any app for testing gps connect to sat ? on wm no problem find app
marc0pol0 said:
i have this mobile a 3 days
i dont know who installed os to this mobile
and question this android froyo 2.2 cyanogenmod 6-310710-artifexed.v03 dont want new radio ?
and exists any app for testing gps connect to sat ? on wm no problem find app
Click to expand...
Click to collapse
No CM doesn't require the new radio. There is a GPS test app in the market but I can't remember the name.
Sent from my LG-P500 using Tapatalk
yes i found on market gps test but still no gps satelite
q.: what is better flash new radio and rom or new cm ?
sry for my quest im lamer on android
You can try either one, but either way I'm thinking your more looking at a hardware issue than firmware. I would try just grabbing a different ROM that's compatible with your SPL/radio and flashing it.
thx
but i dont know how
im big lamer
marc0pol0 said:
thx
but i dont know how
im big lamer
Click to expand...
Click to collapse
Alright. I'll give some guidance when I get back home. Should be about an hour.
Sent from my LG-P500 using Tapatalk
ok thanks a lot
There IS a chance you could brick your phone if you hose this procedure up, so be very careful to do everything precisely as I've put it here. Read through the entire post before starting, then re-read as you go through it. If you get stuck somewhere, STOP and post the problem here. Don't just try to figure it out or just try random stuff.
Download this engineering SPL and this file. Take the first file and put it on your SD card. For the other two you will need AndroidSDK, which you can get from here. Take the AndroidSDK.zip file and unzip it to somewhere on your computer (somewhere you remember). Unzip the two files inside the dream2708updatekip.zip and extract them to the AndroidSDK tools folder. Boot into recovery by holding home+power, select the "flash ZIP from SD card" option. Select the engineering SPL ZIP file, and press home to confirm the flash. After it flashes, go back to the main menu, select "Reboot" and immediately press and hold the home button until you reboot back into recovery. Once back in recovery, select the "Turn the phone off" option. Boot into fastboot mode by holding back+power and then plug the phone into the computer. Open a command prompt from the AndroidSDK tools folder where you extracted the two files earlier. From the command prompt, type the following commands:
Code:
fastboot flash radio radio-2.22.27.08.img
fastboot flash hboot hboot-1.33.0013d.img
fastboot reboot-bootloader
You should then have the 1.33.0013d SPL and 2.22.27.08 radio. Next download this ROM and this kernel. Copy both those files to your SD card, boot back into recovery, go to "Wipe", then select "Wipe data", "Wipe cache", and "Wipe dalvik-cache". You'll be asked to press home after selecting each to confirm. Then go back to the "Flash ZIP from SD" and flash the two new files (not the engineering SPL). After flashing, reboot the phone.
have a problem not boot into recovery after holded home+power blink vodafone screen and thats all
Crap. Flashing the new radio/SPL hosed the recovery. Your going to need to make a goldcard. A Google search will get you the procedure. You will need another Android powered phone. Get that going and I'll post the rest of the instructions when I get home.
Sent from my LG-P500 using Tapatalk
ok gold card complete and what now
you might try the app “gpsstatus”
Download this file and put it on the goldcard. Put the goldcard in your phone and boot into hboot mode by holding (volume down+power). Hit ACTION when prompted to flash the sappimg file. Hit action again to reboot. Once it boots up to the ROM, turn the phone off and then back on in fastboot mode. Download this file and put it in the fastboot folder. Open a command prompt from the Tools like in the other guide and type this:
Code:
fastboot flash radio radio-2.22.27.08.img
fastboot flash hboot hboot-1.33.0013d.img
fastboot flash recovery recovery.img
fastboot reboot-bootloader
Should be able to now boot into recovery and finish the other guide.
thx a lot for help but magic go out from my home
because i have new mobile lg p500 oo from t-mobile operator for free
marc0pol0 said:
thx a lot for help but magic go out from my home
because i have new mobile lg p500 oo from t-mobile operator for free
Click to expand...
Click to collapse
All if you plan on rooting that one I would suggest using the void ROM. Very fast and very neat.
Sent from my LG-P500 using Tapatalk
ok i will write to you for help
new mobile one year dont flash because i need warranty
marc0pol0 said:
ok i will write to you for help
new mobile one year dont flash because i need warranty
Click to expand...
Click to collapse
Actually the Optimus is a lot easier to get back stock than the Magic.
Sent from my LG-P500 using Tapatalk
I called HTC support in Egypt about 10 days ago to ask about the update and they confirmed HTC Legend Froyo update is available with version 3.30.466.6 and the update is rolling in batches by the phone IMEI, please has anybody got this update? my phone is showing "Your phone is up to date" !!!
There is an update available already for 1.27.466.7 to 3.30.466.6 but we don't have the original ROM to make a custom ROM or extract the Arabic support!
zorbakun said:
There is an update available already for 1.27.466.7 to 3.30.466.6 but we don't have the original ROM to make a custom ROM or extract the Arabic support!
Click to expand...
Click to collapse
I called HTC Support to tell them about the problem with updating to Froyo, they told me: I have either update the phone within Safe Mode or take the phone to Support Center in Cairo and they will update it manually within 2 hours.
I guess there is a missing update my phone needs to get: 1.27.466.5 to 1.27.466.7 and that must be manually updated.
I hope this helps some one out there.
I have the same problem. so what is the solution only going to the software support for them to update.
You have two options actually:
1. Wait the update to come to your phone
2. Go to the support center and do the update
I went to the support center and upgraded my phone to froyo, It took 2 hours, and they did for free, I'm now a happy FroYo phone owner .
My phone now has SW# 3.30.415.6
Remember to backup all your data and apps before you go, they will do a factory data reset to the phone.
Working hours of the support center is from 11AM to 6PM.
Can you softroot it and make a dump of /system.
Sent from my HTC Legend
BlaY0 said:
Can you softroot it and make a dump of /system.
Sent from my HTC Legend
Click to expand...
Click to collapse
I tried already using "Universal Androot 1.6.2 beta 5", did not work, do you have another way that is compatible with FroYo 2.2?
Download Tools.zip
We will need to do a backup of the SYSTEM partition of your phone.
1- Use VISIONary to temp root your phone but make sure USB Debugging is enabled for it to work.
2- Extract the Tools.zip to c:/tools
3- use CMD command prompt and type below commands
cd c:\tools
4- push busy box to your phone
adb push busybox /data
adb shell chmod 755 /data/busybox
5- make a copy of the system parition
adb shell
su
/data/busybox tar -cv -f /sdcard/system.tar /system
6- finally upload the system.tar file from the root of your sdcard.
zorbakun said:
4- push busy box to your phone
adb push busybox /data
adb shell chmod 755 /data/busybox
Click to expand...
Click to collapse
I guess he will have to push it to /data/local or /data/local/tmp directory:
Code:
adb push busybox /data/local
adb shell chmod 755 /data/local/busybox
...and execute it from there:
Code:
adb shell
su
/data/local/busybox tar -cvf /sdcard/system.tar /system
Ok I'll try all of that, but I have 2 questions:
1. Is this a softroot and will go away once I restarted my phone?
2. Does this will collect my personal data with it when I TAR the system partition?
1. Yes.
2. No.
Sent from my HTC Legend
BlaY0 said:
1. Yes.
2. No.
Click to expand...
Click to collapse
ok, I'll enjoy a little adventure today
v77 said:
ok, I'll enjoy a little adventure today
Click to expand...
Click to collapse
thx alot we are waiting for you
P.S which branch u went in jovitronix,? or did u went to vodafone (which sell the phone on egypt) ? and which number did u called,I barely get any useful info from calling them.
I am done , I am uploading a 131.6MB system file (230 MB TAR compressed in zip), once it finished I'll provide a link to download it.
aelsharawi said:
P.S which branch u went in jovitronix,? or did u went to vodafone (which sell the phone on egypt) ? and which number did u called,I barely get any useful info from calling them.
Click to expand...
Click to collapse
Call HTC call center, not Vodafone's, and you just need to ask the right questions.
I went to Jovitronix Giza branch,
address: 17,El-mathaf el-zeraey& Dr.shahin street., Infrontt of Ezz El-arab, below 6th October bridge, El-Agouza,Egypt.
GPS: http://maps.google.com/maps?q=%2030.0476%20%2C%2031.2142
Thx a lot for help,u really saved lots of ppl on Thai from.
Viva Egypt !
Sent from my HTC Legend using XDA App
@ BlaY0
Kindly prepare a zip Rom update from this rpm ,I use ur B 0.7
Sent from my HTC Legend using XDA App
A very huge THANK YOU for your help man!
VIVA EGYPT
waiting the uploaded file
@aelsharawi and @mdableh
You are quite welcome, uploading still in progress, my ADSL upload is a little bit slow.
i keep refreshing this thread every 2 min
mdableh said:
i keep refreshing this thread every 2 min
Click to expand...
Click to collapse
U know what to do with this tar file,or shall we wait for BlaY0 ??
I cant wait testing arabib on froyo !
I was able to root my MT4G with ease using VisionARY r14. My friend purchased a MT4G shortly after and I was trying to root it for him, I used several methods and no luck on any of them.
I've tried using:
1. Visionary temp root>attempt perm root
2. Visionary temp root>terminal (sh root.sh)
3. Visionary temp root>terminal (/data/local/wpx.ko)
From what I understand #2 & #3 basically are the same. So going back to the problem, on MY phone (I don't recall if I used #1 or #2), I rooted with no issues. On his phone, the root is not sticking, every time I go into the bootloader on his S=on still. Nothing stands out or is out of the ordinary, and I would think it would have rooted just fine, the scripts ran via terminal emu and looked okay and all.
Something else I've noticed is when I install CWM Recovery via ROM Manager, after temp root from Visionary the install of CWM Recovery itself was fine, though after going into bootloader and trying to access recovery or booting into recovery from ROM Manager, it doesn't go into recovery, I get the cell with red triangle and "!" on it. I'm assuming that this is a result of it being unrooted still? Anyone else run into a stubborn MT4G like this? I've attached 2 pictures for visual aid of the phone's bootloader screen and about screen below.
Any suggestions or help is greatly appreciated, I've been trying to root it for over a week now and no luck.
I can't see the pics you posted, but I had this issue myself, for me the answer was to find a stock recovery pre ota update and force it, then I ran visionary and terminal with sh root.sh or whatever... Hope this helps... Just try to find an image of pre ota stock rom and go from there... There is a good forum here with a walkthrough to do this... Post results please, would like to know if this was your issue...
Sent from my HTC Glacier using XDA App
Hey I ran into the same problem, with that 86.0000 boatloader u must use the gfree chmod777 process its because its after the ota update
Sent from my HTC Glacier using XDA Premium App
grankin01 said:
Ok guys, first of all Scotty2 gets all the credit for the program R&D. I used my device as a test bed and have tried a couple different kernels (Gr8Gorilla's O/C Kernel and the stock kernel).
Now for the boring stuff ...
This is a very invasive way of rooting your device but the benefit is TRUE S=Off and root privileges throughout the system. As such, you do this at your own risk and if you brick your device neither Scotty2 nor myself are responsible, YOU ARE!!! Do this at your own risk!!!
This is not for the faint of heart and if you have any reservations about doing things like this do not do it.
This process will do three things for your device. I will explain them here:
1. It will set up Super CID on your device allowing you to flash any carriers rom (not just tmobile). Giving you more freedom with your choice of software. The software still needs to be device specific to the glacier for compatability reasons though. Like vodafone glacier roms etc.
2. It will subsidy unlock your device. In other words, it will SIMUNLOCK your phone allowing you to use an AT&T sim card and so on in your device without needing the unlock code from HTC.
3. Most important of all it will turn the RADIO S=Off. This is the ultimate S=Off because the radio is what controls the security flag in the first place. Once you turn it off here it is off everywhere and will allow you pure unadulterated access to your device.
This process will not change your bootloader (unless your on 0.86.0000 and you follow the optional steps).
Now, you may be asking "Why do this? I already have root from your other guide and it has given me r/w access to system and recovery. I thought this meant we had permanent S=Off." This is only partially true. We have had an engineering bootloader and "Label" s=off not radio s=off. When you turn the security off in radio it is off permanently no matter what hboot you have installed engineering or otherwise. However, it is optional but you can still copy the engineering hboot over and it will allow you to flash whatever you like without (as much) fear of bricking your device.
This guide assumes you know how to use ADB. If you do not there are guides all over XDA to show you how. There is even a really good one in this forum. Also here is a video on how to setup adb discovered by topgun303: http://www.youtube.com/watch?v=1UF5w1dKe2U
*NOTE*
For some reason this process can bork your recovery. If you notice after following the steps below that in order to reboot from recovery you have to uninstall/reinstall the battery and hit the power button, just install/reinstall clockwork recovery through Rom Manager in the android market and it will fix your problem.
CONFIRMED: Guide does work for pre-OTA devices!!! Thanks xanz!
Here we go:
If you are already permarooted per the other guide just follow the first 11 steps.
Make sure you have visionary installed on your device. (If you were already permarooted w/s=off ignore this step.)
Download this file:
http://www.mediafire.com/?s7afymwe2wb3x60 New version of gfree with more options! See below.
md5sum: b73c56ca0e21664c5756d4ad295063c5
1. Now unzip the file into your SDK tools directory.
2. Plug your device into your computer.
3. Now open explorer and hold down shift at same time you right mouse click on your SDK tools directory (platform-tools if you have the R8 version of the SDK). Select open command window here. If you are in linux (ubuntu) right mouse click on your SDK tools folder, choose actions, and choose open command window(or whatever it's called). Otherwise, open a command prompt and cd your way to your SDK tools directory.
4. Type "adb push gfree /data/local" and hit enter.
Optionally, you could dl the file to your phone use androzip or something like it to unzip the file and then use root explorer to move the file named gfree to /data/local. Not the gfree.h file. All the other files are source code inlcuded for the gnu license. This would skip the first 4 steps.
5. Now unplug your device from the computer.
6. Run visionary to gain temp root. (If you were already permarooted w/s=off ignore this step.)
7. Open terminal emulator on your device, type "su", and hit enter to gain root privileges.
8. Type "cd /data/local" and hit enter.
9. Now type "chmod 777 gfree" and hit enter to make the program executable.
10. Type "./gfree -f" and hit enter.
New features in gfree.
gfree usage:
gfree [-h|-?|--help] [-v|--version] [-s|--secu_flag on|off]
-h | -? | --help: display this message
-v | --version: display program version
-s | --secu_flag on|off: turn secu_flag on or off
-c | --cid <CID>: set the CID to the 8-char long CID
-S | --sim_unlock: remove the SIMLOCK
With the new features you can turn off one thing at a time. You can also turn security back on and set the CID back to stock if you wish. To turn simlock back on you still have to follow the revert procedures on this page as the information that is patched to turn the lock off is encrypted and we can't write back to it other than restoring the entire image.
So, if you wanted to leave simlock on but turn security off and set super CID the command would be "./gfree --secu_flag off --cid 11111111" + enter. The -f switch after ./gfree that is now in the above step (./gfree -f) just tells gfree to patch everything.
11. Wait for the program to finish and then reboot into HBoot to see if S=Off. Also, check your bootloader version. If it says s=off and has bootloader version 0.86.0000 it worked.
If you already had hboot 0.85.2007 you can check it through the hboot menu. It gives you an option for "system info" in the hboot menu. Highlight it and hit power. It should say CID = 11111111 or something like that. If it does your golden.
Congratulations!
12. If this is the first time you have rooted your device you will need to run visionary again (temproot w/set system r/w after root checked and then attempt permroot) to make root privileges permanent and then reboot again. Now "su" should work properly for you.
Gfree writes a backup of the file that it patches named Part7backup-numbers.bin on your sdcard. I suggest putting this file in a safe place as it is the only way to revert if you need to.
[Optional] Steps to flash engineering bootloader.
1. Restart your phone and plug it back into your computer.
2. Download this file: http://www.megaupload.com/?d=NN5726Z8
md5sum: df4fd77f44993eb05a4732210d2eddc6
3. Copy the file to your SDK tools directory.
4. Open a command prompt again and cd into your SDK tools directoty (platform-tools if your on the new R8 SDK).
5. Type "adb push hboot_dhd.nb0 /data/local" and hit enter.
6. Now open terminal on your device and type "su" and enter to gain root priviliges.
7. Type "cd /data/local" and enter.
8. Now type "dd if=hboot_dhd.nb0 of=/dev/block/mmcblk0p18" and hit enter.
9. You should see something like: 2048 bytes in 2048 bytes out 1048576 bytes copied blah blah blah.
10. Now restart the device into hboot and check if your bootloader version is 0.85.2007. That is what you want to see.
Congratulations, you now have a TRUE root and engineering bootloader on your shiny MT4G!!!
Click to expand...
Click to collapse
Sent from my HTC Glacier using XDA Premium App
ZuluNexus said:
Hey I ran into the same problem, with that 86.0000 boatloader u must use the gfree chmod777 process its because its after the ota update
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
I second this, gfree works great
ZuluNexus said:
Hey I ran into the same problem, with that 86.0000 boatloader u must use the gfree chmod777 process its because its after the ota update
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
This would explain why I had to flash the pre ota stock image before I could root using the sh root.sh.... I am sure the chmod777 would have worked also...
Sent from rooted Royal Glacier using XDA app
powduh09 said:
I can't see the pics you posted, but I had this issue myself, for me the answer was to find a stock recovery pre ota update and force it, then I ran visionary and terminal with sh root.sh or whatever... Hope this helps... Just try to find an image of pre ota stock rom and go from there... There is a good forum here with a walkthrough to do this... Post results please, would like to know if this was your issue...
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
I see. So just get a pre ota stock rom and Visionary would be the simplest way then? But would the pre ota stock ROM also include the < 86.0000 botloader?
ZuluNexus said:
Hey I ran into the same problem, with that 86.0000 boatloader u must use the gfree chmod777 process its because its after the ota update
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
ZuluNexus said:
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
ziggy34 said:
I second this, gfree works great
Click to expand...
Click to collapse
Thumbs up
powduh09 said:
This would explain why I had to flash the pre ota stock image before I could root using the sh root.sh.... I am sure the chmod777 would have worked also...
Sent from rooted Royal Glacier using XDA app
Click to expand...
Click to collapse
Which method did you use to flash the pre ota image?
And thanks everyone for the quick replies!
When I flahed pre ota I found the forum on here for it. Just placed the file on my sd card and named it PD15IMG and booted phone to hboot, it found update and went from there
Sent from rooted Royal Glacier using XDA app
powduh09 said:
When I flahed pre ota I found the forum on here for it. Just placed the file on my sd card and named it PD15IMG and booted phone to hboot, it found update and went from there
Sent from rooted Royal Glacier using XDA app
Click to expand...
Click to collapse
Awesome, what is hoped for! Thanks!
Sent from my HTC Glacier using XDA App
EDIT!!
RESOLVED!
Unfortunately the method of just using the PD15IMG did not work because the bootloader recognized it as an older image and wouldn't update it. I came across this thread and successfully rooted!! =]
http://forum.xda-developers.com/showthread.php?t=995549
I improvised a bit and did not use "Androzip" I had "Adao File Manager" already installed on my friends phone. Basically.
Credit goes to the OP of the posts!! But here's the link to the gfree the OP is referring to. http://forum.xda-developers.com/showthread.php?t=858996
I am having a problem getting the gfree files to move where they need to be and sry guys, unsure of ow to use sdk, im need the dummy dummy guide anyone? Ive been researching for days lol
Rainbowbright081 said:
I am having a problem getting the gfree files to move where they need to be and sry guys, unsure of ow to use sdk, im need the dummy dummy guide anyone? Ive been researching for days lol
Click to expand...
Click to collapse
You need a root explorer.
*Root can be accomplished without SDK.
Sent from my Glacier running CM7 RC2 via XDA app.
YOu can try using mt4groot.zip google it
I managed to get it done right with adb, s=off perm, running cm7 with honeycomb. Quite awesome!
Sent from my HTC Glacier using XDA Premium App
lilazngoku8 said:
YOu can try using mt4groot.zip google it
Click to expand...
Click to collapse
It's in the second link I posted. Safer than Googling.
Rainbowbright081 said:
I managed to get it done right with adb, s=off perm, running cm7 with honeycomb. Quite awesome!
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
Running CM7 with Honeycomb? I am mistaken? You mean the honeycomb theme?
Sent from my Glacier running CM7 RC2 via XDA app.
Sry yes running the honeycomb theme
Sent from my HTC Glacier using XDA Premium App
Rainbowbright081 said:
Sry yes running the honeycomb theme
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
Lol cool, I was going to say, 3.0??!! ; )
gordonzhao said:
Awesome, what is hoped for! Thanks!
Sent from my HTC Glacier using XDA App
EDIT!!
RESOLVED!
Unfortunately the method of just using the PD15IMG did not work because the bootloader recognized it as an older image and wouldn't update it. I came across this thread and successfully rooted!! =]
http://forum.xda-developers.com/showthread.php?t=995549
I improvised a bit and did not use "Androzip" I had "Adao File Manager" already installed on my friends phone. Basically.
Credit goes to the OP of the posts!! But here's the link to the gfree the OP is referring to. http://forum.xda-developers.com/showthread.php?t=858996
Click to expand...
Click to collapse
This is just a laid out variant of the ./gfree method. It'll work but it's been around since the dawn of the Glacier. It's nothing special .
ATTENTION! this thread is OUTDATED
unrevoked has always been a finicky program,3.22 working fine for some,not so much for others.recent updates seemd to have made it even worse, i see alot of issue and fustration with it lately. as such, i do not recomend this method any longer.
IMO,at this time htcdev is the best way to root,downgrade,and achieve s-off. while it technically does void your warranty,and wipe your data,it has thus far at least proven to be reliable. i doubt may original droid incredibles have factory warranty left anyway it does not use unrevoked,or any otehr root tools or programs,just htcs own unlock(you can giggle loudly,or silently,as you use their unlock to achieve s-off
the original home of the hctdev method is here, on android forums.
it is also here: http://forum.xda-developers.com/showthread.php?t=1600904 but not as well supported since im not here as much.
_______________________________________________________________________________________________________________________
*outdated guide:
i wasnt sure if this should be here,or in development,so feel free to move it if you feel its in the weong spot. i cant take credit for any of this,i just took it all from different places and put it all here. unfortunately,i cant gaurantee that this will work for everyone. but several have succesfully downgraded and regained s-off.
its intended for someone who has no adb experinece,and is overwhelmed at the thot of downloading and installing the SDK. if your proficient at adb,your welcome to pull flash_image and mtd0 out,and place them in tools,platform tools,or wherever you usually push files from,rather than changing to the mini-adb_inc directory.
thots and feed back are welcome. ive had this guide up here on AF for a few days. ill try and provide support here as well,but please underdstand computer time is limited these days and i dont make it here as often. in otherwords,please help each other out
_______________________________________________________________________________________
PLEASE NOTE: this thread is for the original droid incredible. NOT the incredible 2(vivow) or incredible S(vivo)
for info on downgrading the inc 2 to .97 hboot so you can root with revolutionary,see this thread here in the inc 2 all things root subforum
if you DO have an original droid incredible,aka Inc 1,then procede
_________________________________________________________________
**********************************************************
_________________________________________________________________
READ THIS: i dont mean to sound like i dont want to be bothered with questions. however,folks are having basically the same issues thru-out the 600+ posts,so i can almost gauarntee if you have a prollem,it has been covered. please try and search for some answers before jumping to the end and posting. answering the same things over and over is just making the thread even longer and harder to search.
if you do have trouble and need to post questions about ADB commands,please provide a copy of your entire session in the command window along with the question. its usually pretty easy to see what went wrong when we can see the whole thing.
copy everything in the command window,and paste it into a code box by:
-right click in the command window,click mark.
-highlight everything in white. hit enter.
-then,in your "reply to thread" box here,click the "#" up top
-right click and "paste" everything between the
Code:
tags.
_________________________________________________________________
i cant take credit for any of this,i just took it all from different places and put it all here. unfortunately,i cant gaurantee that this will work for everyone. but several now have rooted 2.3.4,and 1 has succesfully downgraded and gained s-off.
its intended for someone who has no adb experinece,and is overwhelmed at the thot of downloading and installing the SDK. if your proficient at adb,your welcome to pull flash_image and mtd0 out,and place them in tools,platform tools,or wherever you usually push files from,rather than changing to the mini-adb_inc directory.
thots and feed back are welcome. there will prolly be several edits of this as i try to clarify it,and make it a lil better. but for now im tired and 5am comes early ;)
[B]first and foremost,giving proper credit to all that deserve it:[/B]
*alpharev and unrevoked for all they for the root community :cool:
-efizzle for getting the ball rolling in [URL="http://forum.xda-developers.com/showthread.php?t=1286223"]this thread[/URL] on xda by figuring out that an older version of unrevoked would get superuser access on 2.3.4
-iowabowtech for point me in the direction of [URL="http://forum.xda-developers.com/showthread.php?t=768295&highlight=ota"]this thread[/URL] that i collected the misc image,and parts of the guide. also for his support answering questions.
-sele and the crew in the "rescue squad" on [URL="http://api.viglink.com/api/click?format=go&drKey=1153&loc=http%3A%2F%2Fandroidforums.com%2Fthunderbolt-all-things-root%2F418539-thunderbolt-root-unroot-thread.html&v=1&libid=1318297929451&out=http%3A%2F%2Fwww.thunderboltforums.com%2F&ref=http%3A%2F%2Fandroidforums.com%2Fthunderbolt-all-things-root%2F&title=Thunderbolt%20Root%2FUnroot%20Thread%20-%20Android%20Forums&txt=HTC%20Thunderbolt%20Forum&jsonp=vglnk_jsonp_13182980284911"]the thunderbolt forum[/URL] for what i like to call the "mini-adb" concept.
-rooter28 for testing and keeping me updated as he made progress. hopefully he will stop in and help answer questions :)
-mkreiger for fearlessly jumping in to be the second official tester
-lovejess for finding a mac download for unrevoked 3.22
-gkinsella2 for contributing the mac specific instructions
-whomever origianlly came up with the images and guide linked above. if i can figure out who this was,ill add you in later.
*special thanks to sdrawcab for his invaluable support in helping answer questions and prollems
-prolly more,im sure there will be several edits of this.
1)[B][I]download these files[/I][/B],and save them somewhere you can easily find them:
[U]unrevoked 3.22[/U] [url=http://www.multiupload.com/WMGYYGL97Z]unrevoked 3.22[/url]
[U]mirror:[/U] [URL="https://www.box.net/shared/8e3nb5l5lnjjuh6vbqt7"]unrevoked 3.22 mirror[/URL]
md5: [COLOR="red"]5760fbe8ed6d44752e78433252f2d5b2[/COLOR]
[U]unrevokeds modified usb drivers[/U] [url=http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install]public:windows_hboot_driver_install [RootWiki][/url]
[U]mini-adb_inc[/U](contains misc image,flash image,and some basic adb tools)[url=http://www.multiupload.com/0G635MCZS2]Multiupload.com - upload your files to multiple file hosting sites![/url]
md5: [COLOR="red"]a793cc0142e1cd18f60849894bbc47cd[/COLOR]
[U]mirror:[/U][url]http://www.mediafire.com/?o6c4kq4wyccuom5[/url]
mirror md5: [COLOR="Red"]7c5211686a20b558ccd660c782f82e2b[/COLOR]
[I]*clockwork and zergrush included in mirror[/I]
[U]PB31IMG for 2.2[/U] (2.2 downgrade) [url=http://www.mediafire.com/?uvha2u2pv3xp8d5]PB31IMG.zip[/url]
[U]mirror:[/U] [url]http://pvillecomp.com/?page_id=22[/url]
md5: [COLOR="red"]31bb1611a0fa8197d447c0438426717e[/COLOR]
[U]clockwork 5.0.2.0[/U] [url=http://www.multiupload.com/FGEU9VPGKF]Multiupload.com - upload your files to multiple file hosting sites![/url]
[U]mirror:[/U][url]http://pvillecomp.com/?page_id=28[/url]
md5: [COLOR="Red"]e8ac35ddc1c37000bb0852d1f380b5bb[/COLOR]
**make sure to check the md5 sums match those listed!**
if you dont have an md5 sum verifier on your PC,there are many out there for free. heres an example: [url=http://www.md5summer.org/]Home of the MD5summer[/url]
2)[B][I]root with unrevoked 3.22[/I][/B]
-go to settings/applications and [U]uncheck[/U] "fastboot". having this checked will prevent you from getting to hboot via power/vol down.
-open the recovery-clockwork-5.0.2.0-inc_PB31IMG download. extract it first if you need to. inside there is an image called "recovery-clockwork-5.0.2.0-inc". right click on this image,then click "copy". navigate to a directory you can easily find it,then right click in that directory,then "paste". alternatively,you can drag it from the extracted folder to a convienient spot(i personally like to drag files around,but its fine either way).
-use your md5 summer to verify the md5 of just the image,not the whole .zip. it should be: [COLOR="Red"]ea382ca5809cb872d0582aa22741d592[/COLOR]
-install the drivers as described on unrevokeds page above.
-unplug your phone.
-extract the contents of the unrevoked 3.22 .zip. open the folder, right click on "reflash" and run as administrator if possible.
-click on "file" in the corner of the relfash window
-click custom recovery
-navigate to,and select your "recovery-clockwork-5.0.2.0-inc" image and select it. at the bottom of your reflash app window, it should now say "recovery:custom" and "waiting for device"
-make sure usb debugging is checked ON in settings/applications/development.
-plug in your phone and place it in charge only mode. assuming you installed the drivers correctly,unrevoked 3.22 will start. let it do its thing. it will reboot a couple of times. when its finished,it may leave you on a blank screen. if this is the case,pull the battery and reboot.
-you [I]should[/I] now have the superuser app in your app drawer. if so,go to settings/applications/manage apps/superuser and clear data. test that superuser is working and granting permissions by downloading rom manager,and using it to flash the newest clockwork recovery. alternatively,download and run a "root checker" or any of your favorite "root only" apps and make sure they work.
-once you get "successfully flashed clockwork recovery" boot to it and make a backup,since downgrading to get s-off [U]WILL[/U] wipe all your data. boot back into the operating system.
*[I]special note to slcd users[/I]: this version of unrevoked is installig an old, non-compatible version of clockwork,so you will just see a black screen if you do not install newer clockwork as described above.
-if you plan to install a custom rom after downgrading,now is a good time to download titaium backup,and its pro key(WELL worth the $$) and do a batch backup of all your user apps and app data(no system data)
*at this point,you could just enjoy root access without doing anything else. if all you care about is using a couple of root only apps,and deleting some bloatware,you can remain rooted and s-on if youd like. id personally reccomend to downgrade and become s-off in case future OTAs knock out your root access.
3)[B][I]prepare to downgrad[/I]e[/B]
-extract the mini-adb_inc .zip. place the extracted folder on the root of your c drive. it comtains mtd0,flash_image,and some adb tools.
-place the 2.2 downgrade on the root of your sd card,and verify it is named "PB31IMG". now is a good time to verify that your SD card is formatted "FAT32" by right clicking on the drive that is your phones sd card,then click "properties". if you find your card is formated anything else,youll have to re-format it. start by backing up all files to your PC as reformatting [U]WILL[/U] wipe it clean. using your PC,do a full format to FAT32. you can then transfer the files back. *this is important-as your phone will not find the downgrade PB31IMG unless your card is formatted to FAT 32,and the file is correctly named.
[U]special notes on hboot flashing PB31IMG files[/U] a common issue folks are having is the PB31IMG is not being found by hboot.
*there are only 2 reasons a PB31IMG is not found on the root of the sd card:
a)not named correctly. the phone muse see exactly "PB31IMG.zip". due to the way windows automatically adds and hides file extensions,it is usually correct to name the file "PB31IMG" with windows. common errors are for the file to be named "PB31IMG.zip.zip" after manually tying in the ".zip". on rarer occasions,it may not be adding/hiding the file extension,resulting in the file actually beening seen by the phone as "PB31IMG" :eek: [I]check your file with a file manager on your phone[/I] and see how its seeing it.
b)sd card not formatted FAT32. if it is plain FAT or anything else,PB31IMG is invisible. on rare occasion,i have seen claims that a bad sd card,or card that needs reformatted(even tho it may be FAT32) will have the same affect.
*this has been addressed [U]several[/U] times in the thread,skim thru it for more information.
4)[B][I]downgrade with adb[/I][/B]. make sure your phone is charged to 100% before starting.
-on windows 7,click the start bubble and type "command" in the search box. this should open a small black command window. from this point forward,all code will be in [B]bold[/B] so you know what lines to copy and paste(or type,if you really want to type them all in). additional comments will be blue,and should not be copy/pasted. please note that each line is one command. copy/paste it into the prompt in your command window,and push enter. one line at a time.
at the end of the post,is a copy of my session,to show what the outputs of the entered lines should look like. hopefully,its a little less scary when you know that youre getting the right responses to the things you enter.
-make sure phone is plugged in and usb debugging checked on,in charge only mode
-at the promt in your command window:
[B]cd c:mini-adb_inc [/B] [COLOR="Blue"]this should change your command promt to "mini-adb_inc",indicating youre using that directory.[/COLOR]
[B]adb devices[/B] [COLOR="blue"]this should output your phones serial number,indicating its recognized[/COLOR]
[B]md5sums mtd0.img [/B] [COLOR="blue"]it should output a few things.at the end you should see this number 34307be744275f1db1dd16af04c37839
[/COLOR]
[B]md5sums flash_image[/B] [COLOR="blue"]again,it will output some things,then you should see this number: 0098a7dd6600b55fac34fc6645be5d7a[/COLOR]
[COLOR="Red"]*both those numbers must match exactly. if they do then you can procede.
[/COLOR]
[B]adb push flash_image /data/local/[/B]
[B]adb push mtd0.img /sdcard/[/B]
[B]adb shell[/B] [COLOR="Blue"]your prompt should change to a #. if it changes to a $,then type[/COLOR] [B]su[/B] [COLOR="blue"]note your phone may pop up a message asking you to allow permissions the first time you do this. if it does check "always" and touch "allow" on the superuser request on the phone screen.[/COLOR]
[B]cd /data/local[/B]
[B]chmod 0755 /data/local/flash_image[/B]
[B]cd /data/local[/B]
[B]./flash_image misc /sdcard/mtd0.img[/B]
[COLOR="blue"]you can now downgrade back to 2.2,so you can run "unrevoked forever" to regain s-off[/COLOR]
[B]exit[/B] [COLOR="Blue"]to get out of your adb shell,and back to the "mini-adb_inc" prompt[/COLOR]
[B]adb reboot bootloader[/B] [COLOR="blue"]this will boot your phone to "fastboot" select "bootloader" with the power button.[/COLOR]
hopefully what you will see now,is a blue status bar as your phone finds the PB31IMG,unpacks it,checks it,then asks if youd like to update. select yes to update with the volume up rocker. if youve never installed a full ruu in hboot,it will take a few minutes,so dont panic. place the phone gently down somewhere where it wont fall and spit out the battery. let it do its thing. push power to reboot when prompted.
let the phone fully boot,then place in disk drive mode and immediately delete PB31IMG from your sd card,as it will interefere with running unrevoked forever.
*[I][U]special note:[/U][/I] if your phone does not fully boot after running PB31IMG,dont panic. its happened to quite a few users,for some reason. simply pull your battery,boot to hboot via power/volume down and run PB31IMG again.
download unrevoked forever from here: [url=http://www.unrevoked.com/recovery/]unrevoked3 recovery reflash tool, v3.32[/url]
run it as you did the previous version. before plugging in your phone,make sure "disable phone security is checked" in the file menu. this time,it will root you,and turn the secure flag off on your radio. this is good,as it will allow you to always flash things that werent signed and approved by htc. you can flash new radios and recoveries,and flash any ruu you wish. the secure flag is in the radio,so running ruus or even accepting OTAs will not over-ride it. you will always stay s-off.
[I][U]*unrevoked 3.32 note:[/U][/I] if you check the "disable phone security" box as described above,and unrevoked still fails to turn s-off,you are not lost.[U]simply flash the s-off tool in recovery[/U]. you can find it here: [url=http://unrevoked.com/rootwiki/doku.php/public/forever]public:forever [RootWiki][/url]
if you wish to return to where you were,sign into google,download rom manger,flash the latest clockwork recovery. boot to recovery,then restore the back you made before we started.
optionally,you can now install the custom rom of your choice,along with a new recovery and radio if you desire. :)
and heres what you will see when entering the commands(the red are my copy/paste's):
[CODE]Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:UsersScott>[COLOR="Red"]cd c:mini-adb_inc[/COLOR]
c:mini-adb_inc>[COLOR="red"]adb devices[/COLOR]
List of devices attached
HT07DHJ02777 device
c:mini-adb_inc>[COLOR="red"]md5sums mtd0.img[/COLOR]
MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes - http://www.pc-tools.net/
Type md5sums -h for help
[Path] / filename MD5 sum
-------------------------------------------------------------------------------
[c:mini-adb_inc]
mtd0.img 34307be744275f1db1dd16af04c37839
c:mini-adb_inc>[COLOR="red"]md5sums flash_image[/COLOR]
MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes - http://www.pc-tools.net/
Type md5sums -h for help
[Path] / filename MD5 sum
-------------------------------------------------------------------------------
[c:mini-adb_inc]
flash_image 0098a7dd6600b55fac34fc6645be5d7a
c:mini-adb_inc>[COLOR="red"]adb push flash_image /data/local/[/COLOR]
1547 KB/s (76044 bytes in 0.048s)
c:mini-adb_inc>[COLOR="red"]adb push mtd0.img /sdcard/[/COLOR]
1662 KB/s (655360 bytes in 0.385s)
c:mini-adb_inc>[COLOR="red"]adb shell[/COLOR]
$ [COLOR="red"]su[/COLOR]
su
# [COLOR="red"]cd /data/local[/COLOR]
cd /data/local
# [COLOR="red"]chmod 0755 /data/local/flash_image[/COLOR]
chmod 0755 /data/local/flash_image
# [COLOR="red"]cd /data/local[/COLOR]
cd /data/local
# [COLOR="red"]./flash_image misc /sdcard/mtd0.img[/COLOR]
./flash_image misc /sdcard/mtd0.img
# [COLOR="red"]exit[/COLOR]
exit
$ [COLOR="red"]exit[/COLOR]
exit
c:mini-adb_inc>[COLOR="red"]adb reboot bootloader[/COLOR]
c:mini-adb_inc>
other info:
-unrevoked 3.22 for mac can be found here: http://downloads.unrevoked.com/recovery/3.22/Reflash.dmg at this point youre on your own converting the adb commands. if someone wants to translate,or make a mac adb guide,ill gladly add it in
-until we put together a mac specific guide,directions for modifying the rest of it to work on a mac are found in post #629,here: http://androidforums.com/incredible...-3-4-root-downgrade-s-off-13.html#post3623666 courtesy of gkinsella2. mac users(and everyone else ) make sure to click the thanks button on his post!
______________________________________________________________________________________
*last and not least,this is a direct copy/paste of the AF thread,so any references to pages numbers are references to THAT thread on AF
the zergRoot method
this is for folks who for whatever reason,unrevoked 3.22 does not work to get them root access.
this could also be used if youve got a replacement device thats not setup,and you could care less about installing a recovery. this still requires unrevokeds drivers to be set up,so you can root with unrevoked 3.32 after downgrading,but otherwise,it prolly is a lil quicker since you dont need to download and run unrevoked 3.22.
alternately,use this if you just like ADB if your proficient in adb,feel free to remove the images from mini-adb_inc,and place them and the zergRush tool into whatever folder you typically push files from.
like above,this is intended for someone whose never installed ADB or entered command lines before.
1)download these files,and save them somewhere you can easily find them:
unrevokeds modified usb drivers public:windows_hboot_driver_install [RootWiki]
mini-adb_inc(contains misc image,flash image,and some basic adb tools)Multiupload.com - upload your files to multiple file hosting sites!
md5: a793cc0142e1cd18f60849894bbc47cd
PB31IMG for 2.2 PB31IMG.zip
md5: 31bb1611a0fa8197d447c0438426717e
zergRush tool from xda: Revolutionary - zergRush local root 2.2/2.3 - xda-developers
md5: 12c52b97e75e73595b325c03610b3380
**make sure to check the md5 sums match those listed!**
if you dont have an md5 sum verifier on your PC,there are many out there for free. heres an example: Home of the MD5summer
3)prepare to downgrade
-extract the mini-adb_inc .zip. place the extracted folder on the root of your c\ drive. it comtains mtd0,flash_image,and some adb tools.
-extract zergRush.zip. take the image inside,and either copy/paste or drag it into your mini-adb_inc folder
-place the PB31IMG of 2.2 on the root of your sd card. rename PB31IMG. now is a good time to verify that your SD card is formatted "FAT32" by right clicking on the drive that is your phones sd card,then click "properties". if you find your card is formated anything else,youll have to re-format it. start by backing up all files to your PC as reformatting WILL wipe it clean. using your PC,do a full format to FAT32. you can then transfer the files back. *this is important-as your phone will not find the downgrade PB31IMG unless your card is formatted to FAT 32,and the file is correctly named.
4)downgrade with adb. make sure your phone is charged to 100% before starting.
-on windows 7,click the start bubble and type "command" in the search box. this should open a small black command window. from this point forward,all code will be in bold so you know what lines to copy and paste(or type,if you really want to type them all in). additional comments will be blue,and should not be copy/pasted. please note that each line is one command. copy/paste it into the prompt in your command window,and push enter. one line at a time.
at the end of the post,is a copy of my session,to show what the outputs of the entered lines should look like. hopefully,its a little less scary when you know that youre getting the right responses to the things you enter.
-make sure phone is plugged in and usb debugging checked on in charge only mode
-at the promt in your command window:
cd c:\mini-adb_inc this should change your command promt to "mini-adb_inc",indicating youre using that directory.
adb devices this should output your phones serial number,indicating its recognized
md5sums mtd0.img it should output a few things.at the end you should see this number 34307be744275f1db1dd16af04c37839
md5sums flash_image again,it will output some things,then you should see this number: 0098a7dd6600b55fac34fc6645be5d7a
md5sums zergRush again,output stuff, then this number: 3cf8a3fbceb667121d91f4ef1a66684c
*all those numbers must match exactly. if they do then you can procede.
adb push zergRush /data/local/
adb shell this will change your promt to a $
chmod 755 /data/local/zergRush
/data/local/zergRush
this will cause zergRush to start,and it shoudl say "found a gingerbread!" followed by a bunch of other funny stuff.
last thing it says will be: Killing ADB and restarting as root... enjoy!
you should then be returned to your "mini-adb_inc>" prompt
adb push flash_image /data/local/
adb push mtd0.img /sdcard/
adb shell your prompt should change to a #
cd /data/local
chmod 0755 /data/local/flash_image
cd /data/local
./flash_image misc /sdcard/mtd0.img
you can now downgrade back to 2.2,so you can run "unrevoked forever" to regain s-off
exit to get out of your adb shell,and back to the "mini-adb_inc" prompt
adb reboot bootloader this will boot your phone to "fastboot" select "bootloader" with the power button.
hopefully what you will see now,is a blue status bar as your phone finds the PB31IMG,unpacks it,checks it,then asks if youd like to update. select yes to update with the volume up rocker. if youve never installed a full ruu in hboot,it will take a few minutes,so dont panic. place the phone gently down somewhere where it wont fall and spit out the battery. let it do its thing. push power to reboot when prompted.
let the phone fully boot,then place in disk drive mode and immediately delete PB31IMG from your sd card,as it will interefere with running unrevoked forever.
download unrevoked forever from here: unrevoked3 recovery reflash tool, v3.32
run unrevoked(extract the contents,right click on "reflash",run as adminstrator if possible). this time,it will root you,and turn the secure flag off on your radio. this is good,as it will allow you to always flash things that werent signed and approved by htc. you can flash new radios and recoveries,and flash any ruu you wish. the secure flag is in the radio,so running ruus or even accepting OTAs will not over-ride it. you will always stay s-off.
and heres what you should see when entering the commands(my copy/pastes are in red):
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Scott>[COLOR="Red"]cd c:\mini-adb_inc[/COLOR]
c:\mini-adb_inc>[COLOR="red"]adb devices[/COLOR]
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
HT117HJ00242 device
c:\mini-adb_inc>[COLOR="red"]md5sums mtd0.img[/COLOR]
MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes - http://www.pc-tools.net/
Type md5sums -h for help
[Path] / filename MD5 sum
-------------------------------------------------------------------------------
[c:\mini-adb_inc\]
mtd0.img 34307be744275f1db1dd16af04c37839
c:\mini-adb_inc>[COLOR="red"]md5sums flash_image[/COLOR]
MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes - http://www.pc-tools.net/
Type md5sums -h for help
[Path] / filename MD5 sum
-------------------------------------------------------------------------------
[c:\mini-adb_inc\]
flash_image 0098a7dd6600b55fac34fc6645be5d7a
c:\mini-adb_inc>[COLOR="red"]md5sums zergRush[/COLOR]
MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes - http://www.pc-tools.net/
Type md5sums -h for help
[Path] / filename MD5 sum
-------------------------------------------------------------------------------
[c:\mini-adb_inc\]
zergRush 3cf8a3fbceb667121d91f4ef1a66684c
c:\mini-adb_inc>[COLOR="red"]adb push zergRush /data/local/[/COLOR]
1150 KB/s (21215 bytes in 0.018s)
c:\mini-adb_inc>[COLOR="red"]adb shell[/COLOR]
$ [COLOR="red"]chmod 755 /data/local/zergRush[/COLOR]
chmod 755 /data/local/zergRush
$ [COLOR="red"]/data/local/zergRush[/COLOR]
/data/local/zergRush
[**] 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 ! 0x00015108
[*] Scooting ...
[*] Sending 149 zerglings ...
[+] Zerglings found a way to enter ! 0x10
[*] Sending 149 zerglings ...
[+] Zerglings caused crash (good news): 0x401219e4 0x006c
[*] Researching Metabolic Boost ...
[+] Speedlings on the go ! 0xafd158bf 0xafd1ace3
[*] Sending 149 zerglings ...
[+] Rush did it ! It's a GG, man !
[+] Killing ADB and restarting as root... enjoy!
c:\mini-adb_inc>[COLOR="red"]adb push flash_image /data/local/[/COLOR]
1547 KB/s (76044 bytes in 0.048s)
c:\mini-adb_inc>[COLOR="red"]adb push mtd0.img /sdcard/[/COLOR]
1017 KB/s (655360 bytes in 0.629s)
c:\mini-adb_inc>[COLOR="red"]adb shell[/COLOR]
# [COLOR="red"]cd /data/local[/COLOR]
cd /data/local
# [COLOR="red"]chmod 0755 /data/local/flash_image[/COLOR]
chmod 0755 /data/local/flash_image
# [COLOR="red"]cd /data/local[/COLOR]
cd /data/local
# [COLOR="red"]./flash_image misc /sdcard/mtd0.img[/COLOR]
./flash_image misc /sdcard/mtd0.img
#[COLOR="red"] exit[/COLOR]
exit
c:\mini-adb_inc>[COLOR="red"]adb reboot bootloader[/COLOR]
c:\mini-adb_inc>
edit:apparently the zergRush tool has changed. ive included the new md5s,so hopefully there wont be any more confusion like the old md5s caused earlier. be aware of this,however, in case they do change again. you are right to be cautious if it doesnt match,so ill do my best to keep up with it.
This does work, but god I wish it was all ADB it was all so easy before unrevoked it didn't work the first time it gave me SU and root but no s-off then unrevoked would not run again due to new firmware. I did full downgrade to 2.2 and followed all directions ADB is so simple but unrevoked took 2 hours of just missing around to get s-off which included flashing 2.2 in hboot again starting over, running what I could run again in ADB without the gingerbreak since I was now on froyo, it was mostly just repushing the files and binary. But after all that unrevoked ran and gained root and s-off. Worst root I have ever done but people its all about making smart decisions before you do it if you make a mistake and get stuck, get help or trouble shoot but use you head before you battery pull and make sure you read before you hit anything.
If I helped you in any way please use the thank you button
sorry you had such issue with unrevoked. usually thats the easy part most folks are confused by adb and running commnads and wish it was all automated!
just a couple things that may help folks in the future:
-if you dont want to fool with unrevoked 3.22 in 3.2.4 use the "zergRoot"method in post 2. its all adb up to the downgrade. once you get to this point,you could easily roll yourself all the way back to the shipping firmware(assuming amoled screen) if you wanted,and then use an adb method(if one exists,im not that flamiliar with the inc). you dont have to go back to 2.2. i just picked that cause most folks are familiar with it,and with using unrevoked 3.32 to root/s-off it
-there have been a few complaints of unrevoked not giving s-off on 2.2. before you start,make sure "disable phone security" is checked in the file menu. if s-off still fails,but gives you root and a recovery,its worked for everyone thus far to just run the "forever" .zip in recovery,no real need to reflash the 2.2 ruu and run unrevoked multiple times.
-last and not least unrevoked is not ever going to give s-off in the 2.3.4(unless they release a new version for 2.3.4),as is uses an unsupported baseband,thats why the 2.2 downgrade is needed. folks that have no intention of backing up or returning to 2.3.4 and are fairly savy like the poster above,id strongy encourage to just use directions in post 2,its a lil quicker to not have to mess with unrevoked 3.22. its mainly included for the folks that want to make a nandroid or run tibu prior to the downgrade(plus zergRoot hadnt come out yet,when i originally put this together )
once your back on 2.2 you could even just use z4root to get get root access,install rom manager and clockwork,then flash the forever patch. once you can downgrade,there are alot of ways to skin the cat
Worked after a few tries!
Thanks Scotty for this writeup. I thought for a minute that things wouldn't work, but a third try proved fruitful.
Here's a few tips that I can add to things.
Things failed for me at the restore 2.2 part - HBOOT would not recognize the zip file as correct.
I am on a Win XP machine... Format the sd card to fat 32 using something other than Windows - I used a little program called "fat32format.exe". Windows seems to have a problem formatting sd cards correctly, so that could have been it.
Once I made sure the sd card was formatted, I put the 2.2 zip (PB31IMG) back on the sd card and started over using the zergRush method.
If you have tried this before, you will have to remove two directories from the /data/local/tmp directory. These are sh and boomsh. Thanks to ieftm in this forum for this tidbit of info.
If your zergRush is giving you problems stating:
[-] Cannot copy boomsh.: Permission denied
Then use this method to fix as I stated in paragraph above: remove sh and boomsh
Once these directories were removed and the zergRush was completed, the downgrade commenced just as described.
Side note - Unrevoked 3.32 installed Unrevoked forever automatically onto my DInc, so there was no reason to do the additional forever installation. You may have the same results.
For anyone else that can't seem to get things working, the search is your friend. It took me a while of hacking away at things, but eventually they all turned up roses...
Good Luck!
problems install roms
I have a problen,I can't install a Rom error e: can't open/sdcard/primexl3d.zip, why?
saosinalm:
First off, that's the wrong name for the downgrade zip according to the instructions that scotty posted above. Make sure the file is titled correctly and follow his instructions from beginning to end. I believe when mine succeeded my file title was "PB31IMG.zip" but in his instructions he leaves off the ".zip" at the end.
If there is an error in the process, you will have to start over from about step 3. You can't just start back from where you left off if you reboot the phone. Make sure you check your MD5's once you download, then you won't have to go back over that step.
I found the zergRush method easier, but I am more comfortable with adb...
I would suggest re-reading the instructions and following closely - he walks you through things really well.
I have one question....
Why root a phone? I had my phone rooted and honestly it was a complete waste of time. NONE of the Roms I downloaded ever worked properly, the apps never worked, and it was nothing but trouble for me. My phone always "force close" my apps too. No offense to the developers I just didn't see a benefit.
Am I wrong?
epescina:
That's really best answered differently depending on the type of person you are. If you like to play around and experiment with things or like learning how things work, maybe this works for you. Some people do it to get a custom look that no one else has, some do it to try and get better performance out of their phone that may have been bloated with apps out of the factory, and others are learning about developing apps and programming with it. Every person is different. Maybe it's just not for you, but others on this board can't live without it. To each his (her) own...
saosinalm said:
I have a problen,I can't install a Rom error e: can't open/sdcard/primexl3d.zip, why?
Click to expand...
Click to collapse
what are you trying to do exactly? no part of this guide requires you to flash a rom. so if youre tryingto root,be more specific what youre having trouble with, and if this is just a general question about flashing roms,you might do some research and/or post a new thread where more people will see it
epescina said:
I have one question....
Why root a phone? I had my phone rooted and honestly it was a complete waste of time. NONE of the Roms I downloaded ever worked properly, the apps never worked, and it was nothing but trouble for me. My phone always "force close" my apps too. No offense to the developers I just didn't see a benefit.
Am I wrong?
Click to expand...
Click to collapse
i personally have the opposite experience. while there are a couple minor issues with the rom that i run,i feel my phone is faster and more pleasureable after root. i love htc phones,but hate htc sense,so i root mainly root so i can run AOSP based firmware.
but as was said,to each his(her) own
scotty1223 said:
i personally have the opposite experience. while there are a couple minor issues with the rom that i run,i feel my phone is faster and more pleasureable after root. i love htc phones,but hate htc sense,so i root mainly root so i can run AOSP based firmware.
but as was said,to each his(her) own
Click to expand...
Click to collapse
I too hate the HTC Sense and wish I could change the overall layout of my phone. When I did load a new ROM that changed the layout it always seemed to be screwed up for one reason or another.
For example the lastest rom (Cyanogen) I absolutely loved but it didn't have market and I never could find out how to load it!
scotty1223 said:
i personally have the opposite experience. while there are a couple minor issues with the rom that i run,i feel my phone is faster and more pleasureable after root. i love htc phones,but hate htc sense,so i root mainly root so i can run AOSP based firmware.
but as was said,to each his(her) own
Click to expand...
Click to collapse
Couple of quick questions (which might appear silly):
"place the PB31IMG of 2.2 on the root of your sd card. rename PB31IMG"
#1) What do we rename "PB31IMG.zip" to? The directions simply state to rename it.
#2) Move it to the root of the external sdcard or internal sdcard?
tia, and I hope these questions weren't too ridiculous.
kjy2010 said:
Couple of quick questions (which might appear silly):
"place the PB31IMG of 2.2 on the root of your sd card. rename PB31IMG"
#1) What do we rename "PB31IMG.zip" to? The directions simply state to rename it.
#2) Move it to the root of the external sdcard or internal sdcard?
tia, and I hope these questions weren't too ridiculous.
Click to expand...
Click to collapse
It should be named PB31IMG.zip
It all depends how you rename it, if you use your pc it may not show the.zip extension if you have "show extensions" turned off. So on your pc it may just say PB31IMG even though it is really a zip. Sometimes when extensions are off people end up naming it PB31IMG.zip.zip wich will not work. It is best to have your pc show extensions you can do that by going to controll pannel / folder options / view tab uncheck hide extensions for known file types.
cmlusco said:
It should be named PB31IMG.zip
It all depends how you rename it, if you use your pc it may not show the.zip extension if you have "show extensions" turned off. So on your pc it may just say PB31IMG even though it is really a zip. Sometimes when extensions are off people end up naming it PB31IMG.zip.zip wich will not work.
Click to expand...
Click to collapse
wow lol ok, that just seems common sense, but I guess you never know who your audience is
Which sdcard should the file be on?
kjy2010 said:
wow lol ok, that just seems common sense, but I guess you never know who your audience is
Which sdcard should the file be on?
Click to expand...
Click to collapse
It should be on the removable sd not the internal storage if thats what you were asking.
cmlusco said:
It should be on the removable sd not the internal storage if thats what you were asking.
Click to expand...
Click to collapse
thanks again, just making certain. going for my third try now!
---------- Post added at 01:20 PM ---------- Previous post was at 01:14 PM ----------
I'm getting an unmatched number on zergRush
"md5sums zergRush again,output stuff, then this number: 795275fb9c41ebd5b9fe7ab19108c52b"
I get "4bf71b766a9603fa7db98e71e3f3b470"
??
It states:
"*all those numbers must match exactly. if they do then you can procede."
What do you do if they don't match?
Sorry for the n00b questions, been dealing with nothing but HC since June.
I would try redownloading and then check it again. If its still wrong i would contact the op scotty and ask him, as he is the one who provided the original md5.
cmlusco said:
I would try redownloading and then check it again. If its still wrong i would contact the op scotty and ask him, as he is the one who provided the original md5.
Click to expand...
Click to collapse
thanks, d/l it three times already what a PITA
I get a md5 of
3cf8a3fbceb667121d91f4ef1a66684c
for the zergrush file in the zip and.
12c52b97e75e73595b325c03610b3380
for the zip it self, different than both of your guys.
Edit. I believe that the zergrush file has been updated since this post to include more phones so that is probably why the md5 is different.
I will update the method as and when newer methods are available!
So confirmed Root is here presented by @cybojenix
I am making the thread only for making it Noob friendly, and making the instructions bit more detailed!
All credit goes to @cybojenix
DISCLAIMER:
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
Procedure
Download mfastboot-v2 extract its content and use that for unlocking Bootloader
Unlock your bootloader From Here
TIPs:
Unlocking bootloader will wipe your device, Backup your photos, music, contacts using applications in play store or whichvere method you prefer
The motorola site tells us to download the android SDK, You can skip that big download and use the fastboot in step 1
Follow the further steps given on motorola's site, After clicking on Request an Unlock Key, You will get an email which will consist guideline to proceed further!
Clicking on Request an Unlock Key is the point where you lose your warranty
Download The TWRP recovery from here(thread) or here(Goo.im) rename it recovery-twrp.img and move it in the same folder as of step 1
Download The SuperSU from here(thread) or here(chainfire.eu)() and copy it into the root of your internal memory!
Connect your phone to PC and Reboot to bootloader by pressing VolumeDown+Power button for about 6-7 seconds.
Go to the directory in step 1, Do Shift+RightClick in empty space in the folder without selecting anything, Select Open a command window here.
Run following command
Code:
fastboot boot recovery-twrp.img
If facing errors refer to TIP No. 2 and 3
[*]Now touch doesn't work in recovery straight away, so wait 60 seconds without touching the phone, The phone screen will go blank.
[*]Press power button and do swipe to unlock to get your touch working again!
As Motorola released source code for the kernel, @cybojenix has fixed the touch issue, you can skip to step 10 directly!
Select Install, scroll down and find the SuperSU Zip downloaded in step 4.
Swipe to confirm, wait untill the flash is complete and then select reboot, to boot into your phone which is rooted now
Check your app drawer, There should be SuperSU installed. Congratulations you are rooted!
TIPS:
Downloading things from the thread link is a better option as the hotlinks may get outdated, Thread links will not!
If you want to install twrp rather then just booting into it for once, you can use following command to flash it permanently
Code:
fastboot flash recovery recovery-twrp.img
If stuck on Boot Logo of Motorola (blue M), @JerryGoyal has provided a Thread Here to solve the problem using CWM instead of TWRP.
According to the method you can download CWM and Rename it to recovery-cwm.img in place of TWRP in step 3. Execute other steps the same
And in step 7 Replace the given code with
Code:
fastboot flash recovery recovery-cwm.img
In CWM Touch doesn't Work to scroll Use Volume Buttons and Use Power Button to select the choice
in Step 10 you would select Install from sdcard
If you do something wrong and stuck somewhere, The stock firmwares are available for restoring.
[Condor][Stock Firmware] Restore your Moto E to Stock[Lock Bootloader][Noob Friendly]
Reply if any issues! I'll try my best to help!
Reserved!
Very good effort :thumbup:
Some newbies actually need it
Sent from my XT1022 using XDA Free mobile app
quick question.. is it possible to remove that annoying bootloader unlocked warning that shows up everytime you start up the device?
dpool94 said:
quick question.. is it possible to remove that annoying bootloader unlocked warning that shows up everytime you start up the device?
Click to expand...
Click to collapse
Right now it's not but in the coming days I will look into a method similar to this for our device to "remove" the warning.
shimp208 said:
Right now it's not but in the coming days I will look into a method similar to this for our device to "remove" the warning.
Click to expand...
Click to collapse
You don't need to do it bro.. Motorola updated their bootservice .. I mean the warning shows up but only for 2-3 secs and after that comes a new logo loading.. So I think It would be best not to waste time on such things
Just a suggestion.. Instead of flashing a custom recovery, you could also just boot into the recovery using "fastboot boot recovery.img".. This way the stock recovery won't get changed for people who would like to keep it.
I unlocked the bootloader,installed twrp and flashed the superuser.. and I can even see superuser in my app drawer but none of the apps that require root like titanium backup are working.. it says my device isn't rooted :/ help please
dpool94 said:
I unlocked the bootloader,installed twrp and flashed the superuser.. and I can even see superuser in my app drawer but none of the apps that require root like titanium backup are working.. it says my device isn't rooted :/ help please
Click to expand...
Click to collapse
Check your device by installing this device if you really rooted it or not. DOWNLOAD THIS APP
Mrtoxicgamer10 said:
Check your device by installing this device if you really rooted it or not. DOWNLOAD THIS APP
Click to expand...
Click to collapse
Root Access is not properly configured or was not granted.
Super User Applications Status:
Superuser application - is NOT installed!
SuperSU application - version 1.00 - is installed!
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/bin/su:
Result: /system/bin/su: No such file or directory
Analysis: File /system/bin/su does not exist.
Standard Location
Check Command: ls -l /system/xbin/su:
Result: -rwsr-sr-x root root 96144 2008-08-01 17:30 su
Analysis: Setuid attribute present and root user ownership present. Root access is correctly configured for this file! Executing this file can grant root access!
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Root User ID and Group ID Status:
SU binary not found or not operating properly
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1
Results provided on your XT1022 device by Root Checker Pro version 1.3.0 from joeykrim in the Android Market - http://goo.gl/NcnHn
Guys check this too
We can flash this through stock recoveryhttp://forum.xda-developers.com/galaxy-s2/orig-development/30-10-2012-k-la-lp-t1103399
Sent from my XT1022 using XDA Free mobile app
dpool94 said:
I unlocked the bootloader,installed twrp and flashed the superuser.. and I can even see superuser in my app drawer but none of the apps that require root like titanium backup are working.. it says my device isn't rooted :/ help please
Click to expand...
Click to collapse
I am sorry, I by mistake provied the superSU 1.00 link
I changed and updated it superSU 1.64
Please Try again! using the new link from the description for step 4
vin4yak said:
Just a suggestion.. Instead of flashing a custom recovery, you could also just boot into the recovery using "fastboot boot recovery.img".. This way the stock recovery won't get changed for people who would like to keep it.
Click to expand...
Click to collapse
Could you confirm it?
I cannot test it till tuesday?
startracker said:
Guys check this too
We can flash this through stock recoveryhttp://forum.xda-developers.com/galaxy-s2/orig-development/30-10-2012-k-la-lp-t1103399
Sent from my XT1022 using XDA Free mobile app
Click to expand...
Click to collapse
Friendly warning about this Do NOT I repeat DO NOT flash this in recovery this is meant for the Galaxy S2 and is not only outdated by not compatible with our Motorola E. Only flash things intended for your device!
dpool94 said:
Root Access is not properly configured or was not granted.
Super User Applications Status:
Superuser application - is NOT installed!
SuperSU application - version 1.00 - is installed!
Results provided on your XT1022 device by Root Checker Pro version 1.3.0 from joeykrim in the Android Market - http://goo.gl/NcnHn
Click to expand...
Click to collapse
See ? Your device is not rooted. You must have missed something. Try again. Good luck.
Mrtoxicgamer10 said:
See ? Your device is not rooted. You must have missed something. Try again. Good luck.
Click to expand...
Click to collapse
Nah i fixed it. OP posted link of superSU v1.00 which is why my phone wasnt getting rooted. He fixed it. T
but not able to flash recovery.
it gives error -
target reported max download size of 299892736 bytes
error: cannot load 'recovery.img': No error
Click to expand...
Click to collapse
vivekbumb said:
but not able to flash recovery.
it gives error -
Click to expand...
Click to collapse
Did you flash this recovery image, TWRP 2.7.0.0 V1.2, using fastboot?:
vivekbumb said:
but not able to flash recovery.
it gives error -
Click to expand...
Click to collapse
You have copied the recovery.img file in some other folder, bring it to the same folder as of fastboot.exe
and it will work!
deej_roamer said:
You have copied the recovery.img file in some other folder, bring it to the same folder as of fastboot.exe
and it will work!
Click to expand...
Click to collapse
got it thanks.