Hello all!
I'm trying to root my HTC Legend using Chirag's manual.
I somehow managed to complete all steps until step 4 (that is, flashing the rooted rom), but now i'm stuck.
I but the phone in fastboot mode, plug it to my computer, and the phone says "fastboot USB". When i run 'step1-windows.bat', nothing happens, i get the message:
"Legend Root Step 1
Erasing cache and rebooting in RUU mode...
<waiting for device>"
And that is all. Any ideas? It would be pretty lousy to go through all those steps, including downloading and losing all apps not to be able to finish the very last step...
--edit--
I do have superuser "app" in the drawer of my legend. Don't know if it's important...
Ok, so my PC doesn't see the legend when in FASTBOOT mode, "adb devices" returns an empty list. When the phone is on, and normal, i see it with adb services.
Okay, made it past step one. I turned off HTCSync, and the PdaNet, which i installed earlier (i was that desperate). Nothing seemed to work. I then entered FASTBOOT mode, plugged it into the PC, and then in control panel went to 'devices', found 'Android 1.0 devices' and installed the drivers automatically. The moment i did that, step one started to work, and finished in about couple of minutes.
Just in case someone else gets this problem, this is the solution.
Now starting step 2, i hope it will succeed.
--edit--
Yesss!!! It worked like a charm, i now (finally) have rooted 2.1 with sense
Sorry for talking to myself, but i wanted to share the solution, i usually get pissed when someone solves his problems and doesn't share
Nah Your all right with me, its good to see you managed to get it fixed on your own. I think all the guides need to be updated with that information regarding the need for android 1.0 drivers as it seams to be THE most common issue when not being able to get through the rooting steps.
Enjoy and have fun!
Sent from my HTC Legend using XDA App
Related
So I've been trying to root my thunderbolt for about a week with no success.
At first I used the method here: http://forum.xda-developers.com/showthread.php?t=1005292
It has continually failed on step 2, tried on different computer also. No luck.
I gave up on rooting it for a few days/
Since the first step went through I am downgraded, running 1.03.605. It's got quite a few bugs and when I try to software update from the phone nothing is found. All I really wanted was to get it to the current firmware to fix connectivity bugs but after searching high and low I still have no idea how to/if it is possible.
I assumed I may have to just root it at this point, so I gave the manual root on theMikMik a shot. While setting up my ABD everything runs smooth until I try to enter commands into abd. I get permissions denied, every time. I've tried looking for an answer to this with no luck. Guide I used found here: http://www.themikmik.com/forums/viewtopic.php?f=66&t=256
So my main question, is there any way to get the latest firmware onto my phone without rooting? I've tried downloading an update, naming it update.zip then updating from bootloader with no luck.
If not, what the hell am I doing wrong that is denying me permission in ABD. I've turned anti-virus off, rebooted etc.
assuming adb is properly set up (drivers working), you've checked Debugging and unchecked Fastboot (under setting->apps->dev), plugged the phone into your computer, and typing "adb devices" acknowledges your phone is connected, and you are in fact on the downgrade as you said you were. Make sure PG05IMG.zip is removed from your sdcard then...
Go here and start at step 5: http://forum.xda-developers.com/showthread.php?t=996616
You were getting permission denied errors with those adb commands on mikmik because you are not rooted yet hence the "rooted evo" under requirements.
Edit:
While that may should work, I believe you could start from the beginning with Step 1 using the link I just posted as well. Just don't flash the old firmware (1.0.3.605 that you currently have) after you go through that for any reason (see: http://forum.xda-developers.com/showthread.php?t=1008824).
Absolute_Zero said:
assuming adb is properly set up (drivers working), you've checked Debugging and unchecked Fastboot (under setting->apps->dev), plugged the phone into your computer, and typing "adb devices" acknowledges your phone is connected, and you are in fact on the downgrade as you said you were. Make sure PG05IMG.zip is removed from your sdcard then...
Go here and start at step 5: http://forum.xda-developers.com/showthread.php?t=996616
You were getting permission denied errors with those adb commands on mikmik because you are not rooted yet hence the "rooted evo" under requirements.
Click to expand...
Click to collapse
*Facepalm*
So I tried what you said from that guide, step 5 failed for me. So I tried from the beginning...still failed.
So, I decided to record it and hopefully you can tell me what I'm doing wrong.
Link: http://www.youtube.com/watch?v=o2AFZEIVIio
Figured that'd be a better way to get the help I need with less reading on your part.
Sorry, I was commuting home from work.
According to the output of "adb shell" you're either already rooted or psneuter has already been run since boot. (note the "#" output instead of "$").
There's no reason to run psneuter to gain permroot again. So once you see that pound sign, start from a two steps down where it says "/data/local/busybox md5sum /data/local/misc.img". IOW, skip that particular "/data/local/psneuter" step.
And I would highly recommend that if you are going to copy/paste, only copy one line at a time to prevent errors.
Off to grab dinner. I'll check back later when I can but hopefully you will be good from here on out.
Edit:
I'm perfectly happy with walking you through it (and I believe you should be fine after this post anyway) but if you still wanted to use that easyroot method that you started with you might want to read this if you haven't http://bit.ly/qsvOkN. I didn't use that easyroot method but it looks like if a step fails, people just run it again until it works. /shrug
I like adb and people should know how to use it anyway.
I am trying to use 'adb' from the android dev kit but I cannot see the devices, i.e. 'adb devices' doesn't report any devices. It appeared to be working earlier this evening but not any more. I was going to push a rom file to my rooted phone but obviously since I no longer see the device I am stuck. I rooted yesterday and installed the maximus rom but my phone went into a loop of restarting. Unfortunately I didn't backup before I rooted and installed Maximus rom.
Can anybody offer any help? I am using Mac OSX.
Desperate since phone is now effectively redundant
adiemask said:
I am trying to use 'adb' from the android dev kit but I cannot see the devices, i.e. 'adb devices' doesn't report any devices. It appeared to be working earlier this evening but not any more. I was going to push a rom file to my rooted phone but obviously since I no longer see the device I am stuck. I rooted yesterday and installed the maximus rom but my phone went into a loop of restarting. Unfortunately I didn't backup before I rooted and installed Maximus rom.
Can anybody offer any help? I am using Mac OSX.
Desperate since phone is now effectively redundant
Click to expand...
Click to collapse
try this: http://forum.xda-developers.com/showthread.php?t=1706918
if it didnt help u just reply and we´re gonna look whats next to unbrick ur phone
Hi
Thanks for your reply, I have hit the 'Thanks' button
I read the posting you referenced but it doesn't really offer a solution to my problem.
As described earlier I rooted my phone and flashed a Rom (Maximus) succesfully but on turning the phone on after installing the new Rom I got into a cycle of the phone rebooting without actually getting past the lock screen. My thoughts at that stage were to re flash using stock rom but on running fastboot and plugging into my Mac OSX machine via USB, the phone doesn't show up in 'devices' on the Mac. I have also tried 'adb devices' form within Android Dev Tools and although 'adb' runs fine no device is reported. Of course without devices being avaialble to 'adb' then I cannot reflash!
I have also tried from within a bootcamp installation of 'Windows XP' installed on the mac with the same results, this with 'HTC Sync' installed and therefore providing the USB Drivers required within Windows.
I have tried logging into fastboot using 'power' and 'Down Volume' at various stages of the boot process on the phone but have never seen the phone within devices.
Clearly prior to installation of the Rom (Maximus) I could see devices at both the Finder window on the Mac and from adb devices.
Any help or insight you could provide would be very gratefully received
Ok ok ok dont worry
I had to read a bit and found quit much german threads where they flash back the stock rom
as is suggested u cant flash it with odin...
the only solution i woul suggest is that u have to find a computer running windows
there its very easy to restore the stock with the methods u described earlier in the thread...
hope u get done let me know what happend
=)
The question remains; how can I flash anything be it a hacked rom or an official rom when I cant see the 'device' in both windows and mac osx?
I think what I am looking for is a reason why the phone isn't seen when plugging in via USB. Once it is seen as a 'device' I will be able to flash anything via 'adb'.
Thank you for your continued interest and assistance
ok so u know how the get it back but ur phone is not really recognized by ur computer
but i found a method using the bootloader
the problem is that the instructions are in german
but i think if u google a bit u may find it
Don't know if I misunderstood what you said..but to get into recovery, you hold volume down and the power button when the phone is turned off. Not during the boot process.
Yes you can do it with bootloader (power+volume down)
Sent from my HTC Salsa C510e using xda premium
moksha098 said:
Yes you can do it with bootloader (power+volume down)
Sent from my HTC Salsa C510e using xda premium
Click to expand...
Click to collapse
Yes, I know that. He said he attempted to do that DURING the boot process. I was stating that he had to do it while the phone was powered down.
Guys, I can get into recovery no problem. The issue is that my phone doesn't show up in devices on the mac finder window and hence when I run 'ADB Devices' from the mac when the phone is plugged into the mac with USB no device is found and so no serial number is reported in my terminal window on the mac. If I can get to see the device with 'ADB' I can push the rom and recover the phone. At the moment the phone is bricked.
Thanks guys for your continued assistance.
adiemask said:
Guys, I can get into recovery no problem. The issue is that my phone doesn't show up in devices on the mac finder window and hence when I run 'ADB Devices' from the mac when the phone is plugged into the mac with USB no device is found and so no serial number is reported in my terminal window on the mac. If I can get to see the device with 'ADB' I can push the rom and recover the phone. At the moment the phone is bricked.
Thanks guys for your continued assistance.
Click to expand...
Click to collapse
But if this doenst work why dont u try the method with the recovery mode or the bootloader i suggested
Hello there!
I've been trying to install a custom rom to my sk17i running 4.1.B.0.587, I'm also using Windows 8 64 bit.
I first follow this http://forum.xda-developers.com/showthread.php?p=31376248#post31376248 initially as it seems that it's a complete guide. But in that thread, I was unable to unlock the bootloader as the command is not letting me run the fastboot.exe -i 0x0fce getvar version / fastboot device etc.
So I end up trying this thread http://www.androidgadgematic.com/2012/11/how-to-unlock-any-sony-xperia-bootloader-easily.html
Which I able to run those commands ( fastboot.exe.... etc ) but when I run this command to unlock the bootloader ( fastboot.exe -i 0x0fce oem unlock.. ) I got an error " failed remote oem unlock " so I double checked the IMEI and got new bootloader key. Then I tried again, I got an error this time " too many links ". As per other thread, they advised to clear cache ( fastboot clear cache ) but it doesn't made any difference.
After too many trials, I decided to use this http://forum.xda-developers.com/showthread.php?t=1879982 (using flashtool and flashmode) I was able to get 14% when the LED light on my xperia gone. Then what I did was I reconnected the cable then proceeded with flashtool method.
At this point, when I rerun flashtool, it's stock at 2% with checking headlines. Goes about more than 10mins on that phase so I decided to reconnect it. Then my computer crashed, so I have to restart. When I turned my computer on, It loaded for 5 mins then I got a pop up message, "upgrading android" afterwards, other programs loaded but then at the end, I got another error saying " Unfortunately, startup programs stopped..." then it restarts itself continuously that I have to remove the battery to completely turn it off.
I assumed that my phone is now "bricked" that is why i follow this "6. Turning the "brick" into a smartphone" http://forum.xda-developers.com/showthread.php?p=27376017 but it didn't worked. same as the last time I used the flashtools.
Can I still revive my phone? I just want to downgrade it back to GB 2.3 or upgrade it to CM10 JB if possible.
I'm definitely stupid and noob in this field. Can someone help me out for this one? It'll be highly appreciated! Many thanks!
*Drivers are successfully installed.
*downloaded kernels.
*Windows 8 64 bit
I'm on the point of losing hope that I could still use it. =((((
Give this a read - http://www.androidgadgematic.com/2012/06/how-to-fix-bricked-sony-xperia-android.html
Many thanks! I'll give it a try. hope it works. =)):fingers-crossed:
**by the way, I can't see the xperia mini pro component when I try to install the flashtool driver. what component shall I choose?Please advise.Thanks!
Cant find any threads about this. So confusing.
nejakkin said:
Cant find any threads about this.
Click to expand...
Click to collapse
See the general section, everything has been covered before so finding it should be easy.
Hello All,
I've been rooting etc for a few years now, but last night I ran into my first snag I can't seem to get out of. I was attempting to install Viper 3.0, I had flashed in twrp2.6.3.0 beta like they said to do. Went through the wipe, etc installed and it failed. Message was along the lines of "Failed: Installer status 7." So i went through the process of trying to again, but now I'm stuck in Recovery or hboot/fastboot. I had to reinstall Windows 7 on a old hard drive because the whole Windows 8.1 thing doesn't work right. So I can see my phone in adb in WIndows 7. I've successfully pushed twrp2.5 to my phone, but I can do nothing else. I've tried sideload, but that won't work. At this point the main thing I'm trying to do is push an older ROM over to my phone to see if it installs correctly, but I can't seem to even push files in adb. Any help would be greatly appreciated on the matter, as I'm sure I'm overlooking something.
C
combsco said:
Hello All,
I've been rooting etc for a few years now, but last night I ran into my first snag I can't seem to get out of. I was attempting to install Viper 3.0, I had flashed in twrp2.6.3.0 beta like they said to do. Went through the wipe, etc installed and it failed. Message was along the lines of "Failed: Installer status 7." So i went through the process of trying to again, but now I'm stuck in Recovery or hboot/fastboot. I had to reinstall Windows 7 on a old hard drive because the whole Windows 8.1 thing doesn't work right. So I can see my phone in adb in WIndows 7. I've successfully pushed twrp2.5 to my phone, but I can do nothing else. I've tried sideload, but that won't work. At this point the main thing I'm trying to do is push an older ROM over to my phone to see if it installs correctly, but I can't seem to even push files in adb. Any help would be greatly appreciated on the matter, as I'm sure I'm overlooking something.
C
Click to expand...
Click to collapse
Put the phone in recovery mode and plug it into your PC, and make sure adb devices shows your serial number. Then you should be able to just run
adb push C:\path\to\your\rom.zip /sdcard/rom.zip
Then just find it in recovery and flash it
.torrented said:
Put the phone in recovery mode and plug it into your PC, and make sure adb devices shows your serial number. Then you should be able to just run
adb push C:\path\to\your\rom.zip /sdcard/rom.zip
Then just find it in recovery and flash it
Click to expand...
Click to collapse
It made the file location, I'm waiting to see if it finishes copying it, as it's just sitting still at the moment.
Got it to work. Mods, you can delete this thread.
Hello XDA community, this is my first thread, i had never needed to post anything cause i always find everything im searching for in this awesome community... until now :crying:
Last week I got a new android device which is made by Polaroid, model: PSPR355, its a pretty low class device but I thought it would be enough for me.... then i realize I needed root permissions, for obvious reasons... easy I thought... i had rooted many devices...how hard can it be...right?... WRONG! :crying: . The first problem I encountered were the drivers..couldnt find em anywhere... fortunatelly i found a tutorial were i could install the drivers in a different way...although I took 2 days to do this...Ive been about 5 days trying to root my phone.... Ive tryied about 10 different programs with their different versions... and any of those rooted my phone, nor Oneclikroot, nor Unlockroot, etc, etc..... I really gave up trying to find something on the web cause i didnt even find the phone on its official site, so I came her defeated asking for any solution, idea, or if you want to help me with commands, a programm or anything else to root my phone, Im not even afraid of trying programming (Im trying to learn how to make roms, kernels, etc for this phone cause theres nothing on the web abou it but this is a theme for another time) if you wanted to help me i would really appreciate it, im a little desperate so anything would come useful thanks everyone and I hoppe you can help me!!! :fingers-crossed:
MecaMarck said:
If you wanted to help me i would really appreciate it, im a little desperate so anything would come useful thanks everyone and I hoppe you can help me!!! :fingers-crossed:
Click to expand...
Click to collapse
I would recommend trying the towelroot application. It can be downloaded from here, just click on the orange lambda to download the tr.apk file. Then open towelroot follow the instructions in the application. After the device reboots I would recommend downloading, Root Checker Basic form the Play Store and running that to make sure your device is rooted. Finally install SuperSU, and you should be good to go.
First thanks for answering so fast shimp208! And I guess I forgot to tell that I was in Mexico and Im using Telcel's network, I downloaded and installed the apk file but it doesnt starts I click the button pops up a black screen and then closes to the last app I used...any idea about this error...or if its beacuse of the carrier, by the way the device has Android 2.3.7 I dont know if it has something to do with this error
MecaMarck said:
First thanks for answering so fast shimp208! And I guess I forgot to tell that I was in Mexico and Im using Telcel's network, I downloaded and installed the apk file but it doesnt starts I click the button pops up a black screen and then closes to the last app I used...any idea about this error...or if its beacuse of the carrier, by the way the device has Android 2.3.7 I dont know if it has something to do with this error
Click to expand...
Click to collapse
Does it present an error message of any kind before it force closes? Try uninstalling and then re-installing the application, and if that doesn't work go to application manger under settings, find the towelroot application and select the options to clear it's cache and data. The carrier won't have any effect in this case, and with it being Android 2.3.7 your device most definitely has a kernel build date before June 3rd, 2014.
shimp208 said:
Does it present an error message of any kind before it force closes? Try uninstalling and then re-installing the application, and if that doesn't work go to application manger under settings, find the towelroot application and select the options to clear it's cache and data. The carrier won't have any effect in this case, and with it being Android 2.3.7 your device most definitely has a kernel build date before June 3rd, 2014.
Click to expand...
Click to collapse
No it simply closes without showing anything, and without even giving the "Force Close" message, i thought it was because i first installed it on the sd card, or because of not enough space but no, I moved it to the phone and uninstalled some apps I had, I uninstalled and installed towelroot twice and it didnt work, I installed the v1 of it and i got to the [make it ra1n] screen but when I click the button it closes immediately again without any error message
MecaMarck said:
No it simply closes without showing anything, and without even giving the "Force Close" message, i thought it was because i first installed it on the sd card, or because of not enough space but no, I moved it to the phone and uninstalled some apps I had, I uninstalled and installed towelroot twice and it didnt work, I installed the v1 of it and i got to the [make it ra1n] screen but when I click the button it closes immediately again without any error message
Click to expand...
Click to collapse
Very interesting, while in theory the app should work for any kernel build date earlier then June 3rd, 2014 the app many not be compatible with devices running an Android version less then 4.x.
shimp208 said:
Very interesting, while in theory the app should work for any kernel build date earlier then June 3rd, 2014 the app many not be compatible with devices running an Android version less then 4.x.
Click to expand...
Click to collapse
Yes that´s what i thought, do you think that theres no rooting method for this phone? if so, do yo think there´s a way of doing one?
MecaMarck said:
Yes that´s what i thought, do you think that theres no rooting method for this phone? if so, do yo think there´s a way of doing one?
Click to expand...
Click to collapse
Since you have the usb drivers working on your computer, try booting into the bootloader and using fastboot to see if the command fastboot devices returns anything. If the computer see's the device in fastboot that's a good sign. If your device doesn't have a locked bootloader which it likely doesn't, then I can try and create a rooted system image for you to flash in fastboot. Provided fastboot see's your device if it does, if you can provide me an adb dump of your /system folder then I will see what can be done.
Interesting for me.,.
Sent from my LT26w using xda premium
Same Boat
shimp208 said:
Since you have the usb drivers working on your computer, try booting into the bootloader and using fastboot to see if the command fastboot devices returns anything. If the computer see's the device in fastboot that's a good sign. If your device doesn't have a locked bootloader which it likely doesn't, then I can try and create a rooted system image for you to flash in fastboot. Provided fastboot see's your device if it does, if you can provide me an adb dump of your /system folder then I will see what can be done.
Click to expand...
Click to collapse
I'm in the same boat
I use moto-fastboot (any way it's fastboot)
#:\moto-fastboot devices
? fastboot
don't show any info...
I do a system dump in this way
#:\adb pull / c:\PSPR355
mega,co,nz/#!ThIUQYiS!LLbJ9e1-yVJI4juNlWQuPfa9GFH6HP9lr4X8Gwu1MBY
Change "," please, sorry mod if you want i can delete it! =$
klonic0 said:
I'm in the same boat
I use moto-fastboot (any way it's fastboot)
#:\moto-fastboot devices
? fastboot
don't show any info...
I do a system dump in this way
#:\adb pull / c:\PSPR355
mega,co,nz/#!ThIUQYiS!LLbJ9e1-yVJI4juNlWQuPfa9GFH6HP9lr4X8Gwu1MBY
Change "," please, sorry mod if you want i can delete it! =$
Click to expand...
Click to collapse
Unfortunately if fastboot doesn't show your device without any other flashing utility, even with the system dump there is no way to flash a rooted system image if it was created.
Got to see if this guys do the trick!
http://forum.xda-developers.com/showthread.php?t=2066041
shimp208 said:
Since you have the usb drivers working on your computer, try booting into the bootloader and using fastboot to see if the command fastboot devices returns anything. If the computer see's the device in fastboot that's a good sign. If your device doesn't have a locked bootloader which it likely doesn't, then I can try and create a rooted system image for you to flash in fastboot. Provided fastboot see's your device if it does, if you can provide me an adb dump of your /system folder then I will see what can be done.
Click to expand...
Click to collapse
Hello shimp well I connected my device on FastBoot Mode and my computer recognized it and it installed a driver named: ADB Testing Interface I dont know if thats a good sign or what should I do, I tried entering into recovery mode but it shows only an android little guy and exclamation quote... so I think it doesnt have a recovery boot I dont know if thats relevant, Could you help with the adb dump i dont know how to get it. And.... I dont know if besides you help me with the rooted system image you could teach me how I do this.... anyways thanks a lot for helping me! I'll keep doing everything you need so we can root this device!
MecaMarck said:
Hello shimp well I connected my device on FastBoot Mode and my computer recognized it and it installed a driver named: ADB Testing Interface I dont know if thats a good sign or what should I do, I tried entering into recovery mode but it shows only an android little guy and exclamation quote... so I think it doesnt have a recovery boot I dont know if thats relevant, Could you help with the adb dump i dont know how to get it. And.... I dont know if besides you help me with the rooted system image you could teach me how I do this.... anyways thanks a lot for helping me! I'll keep doing everything you need so we can root this device!
Click to expand...
Click to collapse
Since your computer recognizes the device and installed the driver and shows the device when in fastboot mode that's a good sign. The Android with the exclamation point is part of normal stock Android system recovery, it just means that the recovery menu has been hidden (You should be able to get the menu to appear by pressing the power and both the volume buttons in recovery mode). To dump /system run the following command:
Code:
adb pull /system
Then please send me a link to the /system dump, from there I will make a rooted system image.
Factory Rooted??
Hey guys I'm new to this so I may be wrong but has anybody thought to check if the Polaroid PSPR355 comes Factory Rooted??? I had a Polaroid Tablet, PID something(I forget the name), which I tried for hours to root resulting in: bootloop, hard reset, root, bootloop, hard reset, root, bootloop, hard reset, about to give up. So I Googled how to root Polaroid PID something (again, I forget the name), and I come to a post somewhere(forgot that too) that tells me my Tablet and similar Polaroid electronic devices(as well as most electronic devices coming from China) are factory rooted due to some Chinese law. So after the last hard reset, I downloaded HowToRoot App to check if my Polaroid Tablet is, in fact, rooted. I press the little lock button(root checker) and I find that, to my surprise, my Polaroid Table is in fact rooted. So all I had to do was download SuperSU from Google Play Store and Update Binary when prompted and I was Super User. Don't know if this helps but it worked for me.