Related
I'm writing this becuase i recently had trouble following other guides rooting my Bell and Virgin (canada) htc Legend with 2.1 on it (2.2 is out here yet)
First follow this guide
[HOWTO] DOWNGRADE to 1.31 which you can then root for Legend 2.1
http://forum.xda-developers.com/showthread.php?t=725430
Click to expand...
Click to collapse
(By now your should have adb set up and your gold card)
If it dosnt downgrade and shows that it fails its okay just move on
After following downgrade guide and it failing install temp root
the best way is to get the apk is to go to this link in the android browser
goo.gl/TcP1o <---Download link to visionary apk
In the web browser open downloads and install the visionary apk
Then connect your phone to your computer open cmd.exe and via adb get root
with cmd.exe
go
Code:
cd c:\AndroidSDK\platform-tools\
for me adb is under platform tools, if you dont update the sdk it is under just tools
then
Code:
adb shell
a # should be at the bottom line, then type in
Code:
su
This gets you root, if it says denied run the visionary app and try again, then
Code:
/data/local/flash_image misc /data/local/misc1-2.img
Then for the actual root
Flash the Rooted ROM1. Download the Rooting Tools
Legend Rooting Tools:
2. Unzip them to the C: drive on your computer (so the file path is C:\r4-legend-root\)
3. Turn off your phone and turn it back on by holding down Back and Power until you see Fastboot come up on the screen. Push the Power button while highlighting Fastboot on the phone and Fastboot should show up in red now on the phone (if it doesn’t push Power again until it does).
4. Plug the phone in via USB cable to the computer.
5. Open the folder you extracted to the C drive and double click “step1-windows.bat” and wait for it to finish.
6. Once you see the menu on the phone come back up, navigate to BOOTLOADER and push power, then navigate to RECOVERY using the volume buttons to navigate and the power button to select and the phone should boot to the ! screen.
7. Now on the computer double click the “step2-windows.bat” file and wait for it to finish. (UPDATE 12.13.10 – You MUST have HTC Sync version 2.0.33 not a newer version for step2 to work. Please uninstall HTC Sync and download and install this version instead, unplug then plug your phone back in, then rerun step2-windows.bat).
8. Now you should see a custom recovery screen, using the optical trackpad navigate to Wipe and push on the trackpad to select it. Then navigate to Wipe data/factory reset and select that.
9. Once that is done, push volume down to go back to the main menu and select Flash zip from sdcard and select the rootedupdate.zip file and wait for it to flash. All done, you have root access and can use any root required app! Enjoy!
Click to expand...
Click to collapse
This worked when all else did not ill try and help others just ask
i got all this info from the links below and reading all the response's i hope this info helps some one
http://forum.xda-developers.com/showthread.php?t=725430
http://android.modaco.com/content/htc-legend-legend-modaco-com/323201/downgrading-from-froyo-ota/
http://theunlockr.com/2010/06/07/how-to-root-the-htc-legend/
This deserves a sticky
mike998 said:
This deserves a sticky
Click to expand...
Click to collapse
What's wrong with the current sticky?
TheGrammarFreak said:
What's wrong with the current sticky?
Click to expand...
Click to collapse
i think maybe just the first post of the sticky needs to be updated to include something along these lines
Hello, Having some trouble here.
I got to the step where you run the Step1 batch file from windows. The cmd prompt comes up and says "erasing cache....." then sits. a few minutes later. i get
"FAILED <status read failed <unknown error>>
< Waiting for device>
During the erasing cache part, my phone had the boot menu on screen with no response from the controls. Also, a little green status bar was at 90%. (Second thought, that may be battery level. not sure. Confirm?)
Yeah, so, can't get step1 to work.
EDIT: ok. got step 1 and 2 to work. I basically just kept trying over and over and it went through.
So, i got to the custom boot menu. But i try to install update.zip from sd. But i get an error.
It says.
Installation aborted.
--wiping data...
formatting data...
formatting cache...
data wipe complete.
--install from sdcard
finding update package
opening update packing verifying update package.
E: failed to open /sdcard/update.
zip (No such file or directory)
E:signature verification failed
installation aborted.
So, wtf did i do wrong? now my phone is completely wiped, so.... now what?
sig ver
FourForty said:
Hello, Having some trouble here.
I got to the step where you run the Step1 batch file from windows. The cmd prompt comes up and says "erasing cache....." then sits. a few minutes later. i get
"FAILED <status read failed <unknown error>>
< Waiting for device>
During the erasing cache part, my phone had the boot menu on screen with no response from the controls. Also, a little green status bar was at 90%. (Second thought, that may be battery level. not sure. Confirm?)
Yeah, so, can't get step1 to work.
EDIT: ok. got step 1 and 2 to work. I basically just kept trying over and over and it went through.
So, i got to the custom boot menu. But i try to install update.zip from sd. But i get an error.
It says.
Installation aborted.
--wiping data...
formatting data...
formatting cache...
data wipe complete.
--install from sdcard
finding update package
opening update packing verifying update package.
E: failed to open /sdcard/update.
zip (No such file or directory)
E:signature verification failed
installation aborted.
So, wtf did i do wrong? now my phone is completely wiped, so.... now what?
Click to expand...
Click to collapse
okay when your in the recovery menu the one with green text and you go to flash the file theres an option to "toggle signature verification " or something along those lines
then when the verification is off flash it
k after i finally succeeded to downgrade (thinkin that the hard part is done!!!!), but i cant get past step 1, i keep gettin either "waiting for device", or htc black screen, or nothing happens. step 2 is even worse, all i get is "device not found", or loads of "FAILED". ive reinstalled htc sync 2, uninstalled htc drivers.
i think it seems that my computer is not recognising the phone as an android device, cos everytime i connect it, win7 seems to automatically install drivers (nd i cant stop that) and recognises it as HTC ANdroid Device (it appears as a "Disk Drive")..... tried to use htc sync, phone keeps searching nd it fails.. help please i cant use my phone
saifbunni said:
k after i finally succeeded to downgrade (thinkin that the hard part is done!!!!), but i cant get past step 1, i keep gettin either "waiting for device", or htc black screen, or nothing happens. step 2 is even worse, all i get is "device not found", or loads of "FAILED". ive reinstalled htc sync 2, uninstalled htc drivers.
i think it seems that my computer is not recognising the phone as an android device, cos everytime i connect it, win7 seems to automatically install drivers (nd i cant stop that) and recognises it as HTC ANdroid Device (it appears as a "Disk Drive")..... tried to use htc sync, phone keeps searching nd it fails.. help please i cant use my phone
Click to expand...
Click to collapse
You should install the old version of HTC Sync until you're rooted, have you done that?
saifbunni said:
k after i finally succeeded to downgrade (thinkin that the hard part is done!!!!), but i cant get past step 1, i keep gettin either "waiting for device", or htc black screen, or nothing happens. step 2 is even worse, all i get is "device not found", or loads of "FAILED". ive reinstalled htc sync 2, uninstalled htc drivers.
i think it seems that my computer is not recognising the phone as an android device, cos everytime i connect it, win7 seems to automatically install drivers (nd i cant stop that) and recognises it as HTC ANdroid Device (it appears as a "Disk Drive")..... tried to use htc sync, phone keeps searching nd it fails.. help please i cant use my phone
Click to expand...
Click to collapse
You need HTCsync 2 only for step2, to step1 you need the most updated HTCsync.
And you need step1, don't ignore that step just because it's not working.
Install the latest HTCsync, connect your phone to the computer, and put the phone on fastboot mode (should be written "fastboot usb" on phone)
now on the computer, in the folder of the rooting tools, write:
fastboot-windows.exe devices
Does it recognize your phone? (Should output details bout the phone including serial I think)
wel ive done step 1 now. i created a thread for this here..
http://forum.xda-developers.com/showthread.php?t=1095017
step 1 worked without htc sync, computer is good wen phone is in fastboot, it recognises it straight away, but wen i got into recovery is wher it messes up still even with htc sync. sum1 suggested another way, hav a look at the link, but im gettin signature verification failed or sumthin like that
help
saifbunni said:
wel ive done step 1 now. i created a thread for this here..
http://forum.xda-developers.com/showthread.php?t=1095017
step 1 worked without htc sync, computer is good wen phone is in fastboot, it recognises it straight away, but wen i got into recovery is wher it messes up still even with htc sync. sum1 suggested another way, hav a look at the link, but im gettin signature verification failed or sumthin like that
Click to expand...
Click to collapse
what hboot do you have on/ do you have android 2.2 on it?
keep getting this message even though I have installed drivers..pc says they work..phone registers that usb is connected..debugging is selected...what am I doing wrong here...thanks
Update Failed
Please check the PC side and devise side status.
1. Power on your devise and select USB debugging on your phone
-Press Menu and then tap Settings>Applications>Development
-Tap the USB debugging check box if it's not selected
-The USB cable must be connected to your devise and PC
2. Check your driver is installed correctly.
3. Close all other applications in the device and PC.
is your antivirus/internet security shut off?
Have you removed all instances of the drivers (confirmed through device mgr&ctl panel), rebooted an installed the drivers again (making sure phone is not connected until post-install)?
What OS are you running?
running windows7..will check on the antivirus...try reloading USB drives...back in minute with update...lol
32bit or 64bit?
nt sure...wife's laptop..window 7 home premium? Edit...64 bit..sorry
topherdownfrown said:
nt sure...wife's laptop..window 7 home premium? Edit...64 bit..sorry
Click to expand...
Click to collapse
There have been multiple people that have been having odd results with updating through win7 x64.
I would suggest running the update on a 32bit machine.
will try after work..thank you..post result later.
Spz0 said:
There have been multiple people that have been having odd results with updating through win7 x64.
I would suggest running the update on a 32bit machine.
Click to expand...
Click to collapse
Exactly. I tried for 4 hours on my Windows 7 Home Premium 64 bit machine with no luck. Drivers were installing properly from the CD included with the phone, but the update would always fail at 98%. First try on my older Vista 32 bit machine the update went right through the first time with absolutely no issues.
Don't give up
Spz0 said:
There have been multiple people that have been having odd results with updating through win7 x64.
I would suggest running the update on a 32bit machine.
Click to expand...
Click to collapse
I agree. However, I got the "failed to update" message even when I tried to install using my desktop computer that's running Vista32. BUT, then I installed the drivers (the ones that came with the update) to my Toshiba netbook (running Windows 7 Starter). The first update failed, same as before. So I disconnected my Zio, and rebooted it. I plugged it back into the netbook, ran the update installer, and it installed in like 7 minutes. Works great too. So far none of the issues that have been brought up on other threads.
edit: froyo 2.2.1 installed successfully on the Zio in less than 10 mins. i forgot to unmount the damn sd card and this was the really why my phone froze on the "modem download mode" and why the install GUI on pc dissapeared.
piece of cake! thanks a lot guys for posting this update and for creating the Zio forum.
installed the zio m6000 drivers directly from retail cd and ran the kyocera updater. i'm running Win XP on an old-school Dell optiplex.
anyway the update has been taking up at least 20 mins now. the screen on my Zio is black and the message "modem download mode" (i figure that its the tethering part) appears.
why is this update taking so long?
I've heard of varying times. Myself, it only took 6 mins or so, others had to wait more like 20-30.
What does the update program say?
OMG!!!! Its happening to me too! HELP!!! I get error code [0x50015001]. SDcard is out, uninstalled modem driver and installed the one that came with the upate, and still 98% then failed. Any help PLEASE?????
itrustno1 said:
OMG!!!! Its happening to me too! HELP!!! I get error code [0x50015001]. SDcard is out, uninstalled modem driver and installed the one that came with the upate, and still 98% then failed. Any help PLEASE?????
Click to expand...
Click to collapse
don't panic!
you have to follow the directions straight to the teeth on the install instructions.
1. make sure that you have the correct Zio usb drivers installed on your PC.
2. when the installer window (GUI) pops up, read the instructions. make sure that USB debugging is 'checked.' usb debugging option is the settings.
3. make sure that you unmount your sd card (not pulled out).
4. i reset my Zio to factory default right before i updated 2.2
5. if the update installer didn't appear at first then run it again and watch the progress.
Turn your phone off, Hold the volume + (up) and - (down) and the power button to place your phone into Modem Download Mode.
Make sure you have the Kyocera M6000 Drivers installed on your machine properly first. Once you are sure the drivers are installed correctly you can plug your phone in... wait a minute or so before you launch the update file.
I have installed the update to my phone 3 times with no problems other than when I extracted the file from the zip, I found it worked best running it without extracting the file. I have Win 7 32bit and it takes about 5 - 6 minutes to update.
If all else fails. You might have to download the sdk manager and use fastboot and flash the boot image then do the update and it will put the phone into recovery.
Spz0 said:
I've heard of varying times. Myself, it only took 6 mins or so, others had to wait more like 20-30.
What does the update program say?
Click to expand...
Click to collapse
By the way, The updater says 5 - 10 minutes.
Success!!!! ok...I dont know if it mattered but I also installed the future dial suite on the zio disk...I went through first and erased all other zio usb drivers before reinstalling the disk versions...plugged in phone..drivers got the OK..then ran the installer..took 5 minutes plus 2 for reboot..lol..
Also...fyi..I did this to my wifes phone but forgot to factory reset...all of her programs and contacts including adw ex remained intact after update (smoke from ears) oh well..thank god for titanium backup..
So does that confirm my thoughts of when I updated the other day to fix a goof after my original update. My apps and everything were still there after the update. So that must mean that the update from 1.6 to 2.2 does not format the phone unless go into the phone settings and do a factory reset.
Im at the end of my chain, please help me. My zio is stuck on the black screen "modem download mode" ever since the 98% thing happened. Try after try i keep getting error code. Im using windows vista 32-bit, i got the disc that came with my zio, i think i may have opened/extracted the zips wrong or didnt install in order or something. I think i uninstalled everything to do with this from my cpu even the zips so i can start fresh with ANY help i can get.
Uninstall the drivers for your zio that you have currently installed. Install the drivers that are on the site for the update download. Turn the phone off, unplug your battery for about 10 seconds if you need to. Hold + up and - down on the volume and the power button to put your phone into Modem Download Mode manually. Give the computer a minute to recognize the device. Run the updater again and if it fails or gives you an error message I would reccomend downloading the updater again. I have been able to run the updater several times already with no issues.
If you are still having problems, you may need to download sdk-manager if you do not have it already. You can always just use fastboot to erase the system and then run the update. The update will then set up the system partition and update the phone.
I had to do this just a few hours ago after I semi-bricked my phone while messing around with the cpu. What I did to get it working again after "bricking" it was...
1. you will need to have the android folder for the sdk-manager in the root of your hard drive to make it easier, unless you know where it is located.
2. Open command prompt and change to the tools directory within the sdk-manager folder. Mine was located in C:\Android\SDK-Manager\Tools
3. You may need to find the AdbWinApi.dll file, mine was located in the platform-tools directory so I just copied it to the main Android folder then copied fastboot from the tools directory and also placed that into the main Android folder.
4. Put your phone into fastboot. Hold Volume + up and the send and power keys. You can do "fastboot -w" and it will wipe user data and cache. You will need to type "fastboot erase system" and it will erase the system partition. Now type "fastboot reboot" and your phone will restart.
5. Put your phone in Modem Download Mode and run the updater.
Mattix724 said:
Uninstall the drivers for your zio that you have currently installed. Install the drivers that are on the site for the update download. Turn the phone off, unplug your battery for about 10 seconds if you need to. Hold + up and - down on the volume and the power button to put your phone into Modem Download Mode manually. Give the computer a minute to recognize the device. Run the updater again and if it fails or gives you an error message I would reccomend downloading the updater again. I have been able to run the updater several times already with no issues.
If you are still having problems, you may need to download sdk-manager if you do not have it already. You can always just use fastboot to erase the system and then run the update. The update will then set up the system partition and update the phone.
I had to do this just a few hours ago after I semi-bricked my phone while messing around with the cpu. What I did to get it working again after "bricking" it was...
1. you will need to have the android folder for the sdk-manager in the root of your hard drive to make it easier, unless you know where it is located.
2. Open command prompt and change to the tools directory within the sdk-manager folder. Mine was located in C:\Android\SDK-Manager\Tools
3. You may need to find the AdbWinApi.dll file, mine was located in the platform-tools directory so I just copied it to the main Android folder then copied fastboot from the tools directory and also placed that into the main Android folder.
4. Put your phone into fastboot. Hold Volume + up and the send and power keys. You can do "fastboot -w" and it will wipe user data and cache. You will need to type "fastboot erase system" and it will erase the system partition. Now type "fastboot reboot" and your phone will restart.
5. Put your phone in Modem Download Mode and run the updater.
Click to expand...
Click to collapse
okay, let me give that a shot, stay with me please!!!!!!
hi, this is how i managed to get root working on my tab, everything went fine for me till it came to booting into recovery then nothing use to happen so i combined two separate guides to get it working. thanks (bcmobile and 411tecknology)
the command in "(getting root 5) )" worked for me as i was getting stuck with "fastboot flash recovery skitzandroid-recovery.img"
i unlocked the bootloader by firmware upgrade the the following
for all those people like me with no experience in dos commands or linux, hope this works for you
PREPARE:
1) With your Tab in fastboot mode (step 1 of “GETTING ROOT” below), make sure you have a working fastboot implementation:
working dir\\fastboot devices
If all is well, you should see your device serial number. If there is a problem, you won’t get any response.
2) Downlad the two files attached to this thread
3) create a folder in drive c naming it "root"
This will be referred to as the working directory throughout the rest of this guide
4) Copy skitzandroid-10-1v-root.zip to your working directory (DO NOT UNZIP!) c: root
5) Extract the skitzandroid-recovery.img file from skitzandroid-stock-recovery.zip to your working folder. Your working folder( c: root) should now have 1 IMG file and one ZIP file.
6) copy fastboot files to the the folder that you are going to use as working dir ( c:root)
7) Copy the skitzandroid-10-1v-root.zip file to the root of your sdcard. You can eithe drag/drop, or run:
working dir or c:\root>adb push skitzandroid-10-1v-root.zip /sdcard
GETTING ROOT:
1) Power off your Tab and power it back on, while holding the VOLUME DOWN button.
2) When the DOWNLOAD / FASTBOOT icons appear, press VOLUME DOWN again to select FASTBOOT icon (the one with the USB logo) and press VOLUME UP to confirm selection.
3) Confirm you are now in fastboot mode and do a:
fastboot devices
If all is well, you should see your device serial number.
4) Open a terminal / CMD prompt and CD to your working folder
keep doing cd.. until you get to "c:>" then
cd/root
5) Run the following command:
c:\root> fastboot boot skitzandroid-recovery.img
..and wait. It might not look like anything is happening but it is.
6) You should now have a recovery menu. Use the volume rocker (up/down navigates menu options)
to select “Install zip from SDCARD” (or something like that)
7) Navigate to the root of your internal storage (/sdcard), select the skitzandroid-10-1v-root.zip file and press (tap!) the POWER button to confirm selection.
Once complete, use the Volume rocker to select “REBOOT” from the menu and press (tap!!!) the POWER button to confirm selection.
9) YOUR’RE DONE. Press the thanks button on this thread to continue
TESTING:
Check your apps menu to confirm the existence of SuperUser app.
whats wrong with this?
http://forum.xda-developers.com/showthread.php?t=1079781
Nothing!
I used it on UNLOCKED 10.1v (not from Vodafone) and had no data loss!
Great, Thanks
Frank
I do not understand: 3) Confirm you are now in fastboot mode and do a:
fastboot devices
If all is well, you should see your device serial number.
Where do I enter this data?
I mean - fastboot deviсes
TNTCOSMOS said:
I do not understand: 3) Confirm you are now in fastboot mode and do a:
fastboot devices
If all is well, you should see your device serial number.
Where do I enter this data?
I mean - fastboot deviсes
Click to expand...
Click to collapse
once you start your device in fastboot mode and connect it with the computer to make sure your device is recognized by the computer you open command prompt take it to your working dir.. (ie. c:>root) in our case type fastboot devices and hit enter, if your computer recognized your device you will the serial number under it.
im sorry> can you help me?
When i write in the command line "fastboot.exe devices" nothing happens....
TNTCOSMOS said:
im sorry> can you help me?
When i write in the command line "fastboot.exe devices" nothing happens....
Click to expand...
Click to collapse
assuming you have installed sdk if not please do so, then staying in sdk go to
(C:\android\android-sdk-windows\platform-tools ) by clicking your mouse in desktop
(not cmd prompt). above eg.. is how i installed sdk on my desktop yours may be different, now in platform-tools you will see two files called fastboot copy them both to to your folder called ..root.. and you are set to go.
bottom line is if you want to start fastboot from any folder in cmd you have to have these two files in the folder.
also if you know that your device is detected by your computer dont worry about step 3. all it does is tell you that your device is connected.
I have all turned out, the problem was the drivers. I copied the driver from pdanet and it worked!
TNTCOSMOS said:
I have all turned out, the problem was the drivers. I copied the driver from pdanet and it worked!
Click to expand...
Click to collapse
Glad to hear that you finally got the root.
same problem
TNTCOSMOS said:
im sorry> can you help me?
When i write in the command line "fastboot.exe devices" nothing happens....
Click to expand...
Click to collapse
i've tried with pdanet too but it's not working....like the computer can't see the device...any ideea ???
and when i write "fastboot boot ......etc......" it says <waiting for the device>
please help
You need the drivers installed for fastboot, have you installed them? Please have a look at the [Guide] Unlock your bootloader thread. it contains all the details to get fastboot working.
thank you...finally did it
another noob question...how do i enter in cwm for installing another ROM ???
zbuggy said:
thank you...finally did it
another noob question...how do i enter in cwm for installing another ROM ???
Click to expand...
Click to collapse
The easiest way if you are rooted is to install rom manager from the market. It has an option to reboot to recovery if you have CWM installed. It also allows you to update to the latest CWM recovery if there is one.
i've tried putting the TB Galaxy 1.0.9: Honeycomb 3.1 + TouchWiz UX and i made a mistake... in cwm i've uploaded the zip file only with the update and not the rom itself.since then the tab won't start...it stop's in the beggining at the "samsung galaxy tab 10.1v"...any ideea...what can i do ?
Download latest rom and instructions from samfirmware.com using odin Get ur tab into fastboot mode with 3 button recovery and start from scratch.
It should work out
Sent from my GT-P7500 using Tapatalk
zbuggy said:
i've tried putting the TB Galaxy 1.0.9: Honeycomb 3.1 + TouchWiz UX and i made a mistake... in cwm i've uploaded the zip file only with the update and not the rom itself.since then the tab won't start...it stop's in the beggining at the "samsung galaxy tab 10.1v"...any ideea...what can i do ?
Click to expand...
Click to collapse
Do the following. If you have not yet odin.
Download the full rom.
Follow instructions in how to get into fasboot in sticky thread.
Once in fastboot you can load recovery via it, to do that download the recovery from droidbasement.com/blog, search on pershoot's website for recovery 4.0.4 if i remember correctly then type
fastboot boot recovery.img
where recovery.img is the name of the file you downloaded from droidbasement.com
Recovery will then load give it a minute or so.
Once loaded you can push the downloaded full rom via adb. That is part of the android sdk.
Like this: adb push romfile.zip /data/media/ (this will take a few minutes)
Then in cwm instal rom.
I hope it helps. Btw, remember you need to flash the wipe script of the rom before you install the rom if you are comming from stock.
Send from my GT-P7100
10x everybody it worked!!!!!!!!
Still me, posting in yet another thread. Still can't get the proper drivers. Pda method is not working. Which version of PDanet should I use ? The latest ? This is ****ing irritating...
I'm used to have to struggle to get things work at the beginning, but with my Magic and Hd2 it was a matter of hours...not weeks ! I'm sure it's something stupid but everybody deserted these guides topics...
I'm actually considering posting in the Dev section just to get attention...
Also, pershoot blog's advices are a joke : with no tags, a not working search field, no categories, try to find an info ! Knowing that the word "Recovery" will pop about 3 times per subject, I'm good to spend the week-end searching...
DannyBiker said:
Still me, posting in yet another thread. Still can't get the proper drivers. Pda method is not working. Which version of PDanet should I use ? The latest ? This is ****ing irritating...
I'm used to have to struggle to get things work at the beginning, but with my Magic and Hd2 it was a matter of hours...not weeks ! I'm sure it's something stupid but everybody deserted these guides topics...
I'm actually considering posting in the Dev section just to get attention...
Also, pershoot blog's advices are a joke : with no tags, a not working search field, no categories, try to find an info ! Knowing that the word "Recovery" will pop about 3 times per subject, I'm good to spend the week-end searching...
Click to expand...
Click to collapse
Hello,
I have been successful with rooting on win7. With win xp - after a few day struggling - fastboot did not give a go. Hope this helps
I just can't get the "Adb Original" signature from Pdanet. I always get standard Adb. I add the galaxy tab lines in the .inf file but still...
Do you guys edit the inf file with Wordpad or another tool ?
Preface:
I was performing a nandroid restore and then accidentally removed the battery at some point.
Situation:
Phone does not boot past black and white galaxy S screen.
Going into Clockwork Recovery, I am unable to factory reset, or start a restore because it seemingly is not able to detect any of the storage of the device....
(sample messages below):
Code:
E:unknown volume for path [/data]
E:unknown volume for path [/cache]
E:unknown volume for path [/sdcard]
E:unknown volume "/data"
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
Furthermore, I can't just re-flash in download mode because the computer refuses to detect it in windows. At first I thought it was a driver problem, because i've had difficulty with my computer detecting the phone at times, but now I suspect download mode is broken somehow (after trying to reinstall the drivers and installing kies, and various combinations therein). When the phone is plugged into a different computer ( laptop ) running linux, I get messages like these on the command line:
Code:
usb 1-1: device not accepting address 2, error -71
usb 1-1: device descriptor read/64, error -71
usb 1-1: device descriptor read/8, error -71
hub-1.0:1.0: unable to enumerate USB device on port 1
On another note assuming I can't resolve this in a more delicate manner, can someone tell me if it is possible to use a jtag programmer to flash the phone?
Would using a jig to get into download mode make a difference?
Thank you very much for your assistance.
Wich Rom where you trying to restore to?
and what Rom were you on before you hit the Restore button?
pzayx said:
Wich Rom where you trying to restore to?
and what Rom were you on before you hit the Restore button?
Click to expand...
Click to collapse
I was trying to restore to stock JVR (rooted, no lagfix, semaphore kernel I think), from the ice cream sandwich port.
okey, i see, you might need to download android sdk and download the latest usb package or search around for the drivers for Nexus, since the usb drivers for galaxy s doesnt work with cm7/ics builds.
if you manage to make your pc recognise your phone you could check out this thread:
http://forum.xda-developers.com/showthread.php?t=1134975
btw, if you want to restore from ICS to stock gingerbread i think you will have to install a stock gingerbread ROM before you restore.
Hope this helps you!
(edit: if you find the driver or download it from SDK you can head here http://www.dkszone.net/setup-install-adb-android-debug-bridge-windows-7 to see a guide for how to set the driver manually)
Hm, Well I had already had the SDK and the drivers on my computer, but do I need to do anything special to install them? I recall previously trying the [right-click inf > Install] method, for some reason, but that didn't work
zeco said:
Hm, Well I had already had the SDK and the drivers on my computer, but do I need to do anything special to install them? I recall previously trying the [right-click inf > Install] method, for some reason, but that didn't work
Click to expand...
Click to collapse
i had to manually set the drivers,
i used this thread to do it:
http://www.dkszone.net/setup-install-adb-android-debug-bridge-windows-7
Just jump straight to step #7 if you have the drivers
Upon selecting the driver, windows immediately complains:
"The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems."
Agh, And I thought this might actually work too.
EDIT:
Unknown if this is a success or not... but i've been alternating computers trying various permutations of fixes, and this time my laptop actually says the word samsung in the device manager....
EDIT2: Odin Sees it! I am going to try to flash JVR now... then retry restore from there....
P.S. I hope to god this is not related, but I actually just dropped my phone in between switching to attempt on laptop....
EDIT3: Detection, but immediate failure open attempting to flash. Then rebooted phone and now upon pressing start again it seems to be flashing.........
P.P.S: I've got to say, the most stable thing about this series of phone has got to be the bootloaders :#, Like seriously, this thing is boss.
EDIT4: Well. Managed to flash, Now I just get stock recovery with the same problem of it not finding the storage... I guess I will try flashing with repartion and a PIT?
I had to manually choose the folder where i store the Android SDK.
like c:\sdk\sdk\
it sucks when things dosent work like they should do!
So Yeah... Despite not really changing very much at all, download mode connects, and My phone now boots, Which is a lot better than where I was at previously So thanks for your help.
yw, happy i could help you!
The next mystery to solve is why Recovery is still screwed, and why I can boot my device anyway....
Hmm
So youre still getting the E:\ unknown volume *****?
Wich odin version do u use?
I had to use Ezodin last time to get it to flash,
then i flashed full stock JVH (with pda, phone & csc)
but i guess you could try to flash a stock Gingerbread bootloader too,
http://forum.xda-developers.com/showthread.php?t=1089989 Here is both Froyo and Gingerbread bootloaders.
And i have Atached EZodin for you.
I am trying to flash a customer recovery to my device, but when the phone gets put in download mode i am getting " "lge android mtp device cannot start code 10". " I can not perform any of the essential fastboot commands because the device can't start. I have tried, updating drivers, and trying different mtp drivers available to me, none of which worked. I've tried to do this on 3 pcs running windows 7, 8 , and 10 and they all fail.
Is there a solution to this issue? surely i'm not the only one having this problem. Searching the forum yielded only Samsung results with the same error message. Following the lines of going to the registry and deleting a specific entry, it still didn't work, so please, any help?
PS. reinstalling the drivers for my device does nothing, and windows is already updated.
bump
Did you solved it? I have the same problem
Sunaj1 said:
I am trying to flash a customer recovery to my device, but when the phone gets put in download mode i am getting " "lge android mtp device cannot start code 10". " I can not perform any of the essential fastboot commands because the device can't start. I have tried, updating drivers, and trying different mtp drivers available to me, none of which worked. I've tried to do this on 3 pcs running windows 7, 8 , and 10 and they all fail.
Is there a solution to this issue? surely i'm not the only one having this problem. Searching the forum yielded only Samsung results with the same error message. Following the lines of going to the registry and deleting a specific entry, it still didn't work, so please, any help?
PS. reinstalling the drivers for my device does nothing, and windows is already updated.
Click to expand...
Click to collapse
because flashing twrp.... phone doesnt have to be in download mode..
you turn on phone plug usb. then install minmal adb
copy twrp file into adb folder/ keep pressed SHIFT KEY on empty space in minimal adb.. then right click mouse
then select start command prompt here.
then send command you should see a message on phone .. turn on screen. select ok. then again send command
the twrp files both one in sd card and in minimal adb and the command should be named the same for twrp. example twrp.v.1.1.3 the command has to be the same .. just edit command or both or rename twrp the twrp file.