Hello eveyone
I am trying to root my legend. First, I tried the method on http://wiki.cyanogenmod.org/wiki/HTC_Legend:_Full_Update_Guide
It has 2 steps: downgrading and rooting.
I completed whole step 1 (downgrading) and went back to android 2.1 through the RUU.
Then I came at step 2, rooting the device. In step two of the rooting, it gives a link to the rooting files. This mediafire link is dead.
I went online searching for another link, and eventually i came at http://forum.xda-developers.com/showthread.php?t=1680584#3 wich guides to do the root through HTVdev. Before i actually went and tried this i needed a working phone for work so i did a full reset and updated trough android OTA update.
When I tried to unlock it through HTVdev, i runned into a problem.
Before i even could start, it asked me to update my rom with one of the given links. It says:
NOTE: If you do not find your ROM version in the table below, and your ROM version is newer, then your device does not require the RUU. Please bypass these steps and continue to the next page.
Click to expand...
Click to collapse
So my problem is, my version is not listed, but it is ALSO NOT newer than the versions listed below. The versions that are listed are:
3.14.161.1
3.14.163.1
3.15.1600.
3.15.178.3
3.15.405.3
3.15.708.2
3.15.709.3
3.15.720.3
3.18.751.2
3.19.1010.1
3.20.666.1
3.30.415.6
3.30.466.6
Click to expand...
Click to collapse
My problem is, i got version 3.15.405.7, very similar to the one listed, 3.15.405.3. First i skipped this part, and went ahead to follow the steps anyway. When i had to type fastboot oem get_identifier_token (step 8) in command prompt, it supposed to give me a large list of numbers.
Mine did nothing, so i knew i was wrong. I tried all of the steps a few times but with no effect. Then i thought, can't i just use the RUU of 3.15.405.3, maby then it will work?
But when i tried to run it, it didn't work since i dont have the right version to begin with.
So now what, can anybody help me? I realy want to unlock my device, it is so slow on stock 2.2 i'm getting crazy
I'll trie to follow every suggestion somone gives me but i cannot guarentee i can do everything since i'm a bit new to this stuff (although i know a lot about computers)
Thank you very much!
http://forum.xda-developers.com/showpost.php?p=34921904&
hope this helpful
Related
Hi guys I have a generic unbanded hero running 2.73.405.66 and have been trying to root it for the past few days with no sucess.
Ive managed to create a goldcard ok (I think) and am able to start the install of the earlier rom ok, but once the install starts and reboots the phone, after a minute or so i get an incorrect bootloader error and the install stops.
Just wondering if anyone using this ROM has managed to downgrade to gain root, if so a prod in the right direction would be appreciated
Oh and I know some of you are going to say search the forums, but I cannot seem to find any info on this latest rom, all the guides seem to cover earlier or carrier specific ROMS.
I dont think you need to downgrade the 405 bootloader. Have you tried the one click method at unlocker.com.
rosso22 said:
Hi guys I have a generic unbanded hero running 2.73.405.66 and have been trying to root it for the past few days with no sucess.
Ive managed to create a goldcard ok (I think) and am able to start the install of the earlier rom ok, but once the install starts and reboots the phone, after a minute or so i get an incorrect bootloader error and the install stops.
Just wondering if anyone using this ROM has managed to downgrade to gain root, if so a prod in the right direction would be appreciated
Oh and I know some of you are going to say search the forums, but I cannot seem to find any info on this latest rom, all the guides seem to cover earlier or carrier specific ROMS.
Click to expand...
Click to collapse
My guide can be used for all users.
You just need to downgrade! You need the correct driver, check my ADB / Sync guide for the driver.
im having a little problem rooting my htc hero.
using the unlocker website to root it.
(cant send link. wont let me)
ive got to instruction number 11. downloaded the two files (apk and img) and started to install the flashrec.apk. i get to the screen where i backup recovery image but it says the back up failed could not run command when i try to back it up, how do i fix this?
used both 1.1.2 and 1.1.3 files, both the same.
Try using BTDAG's guide in my signature.
Let us know if/where it throws up errors.
AHA,...
Is this where you get issues,....
TAKEN FROM BTDAG's GUIDE
btdag said:
10. When it is installed click Open. Click on Backup Recovery Image and wait for it to finish. If you get "backup failed" response see the text on the right for more details, if the backup is a success carry on to step 11.
a. Installing the correct HTC ROM
Orange UK Users - Please downgrade your ROM version to 2.73.61.5
Generic Hero Users - Please downgrade to 2.73.405.5, or follow the goldcard method if this doesn't work
T-Mobile UK Users – Please follow the "Goldcard" method below
All Other Users - Please follow the "Goldcard" method below
Click to expand...
Click to collapse
what firmware version do you have 2.73.x.x
also What Network
yeh, the 2.73. just updated it
im on orange. my friend sent me the file and uploaded it.
i used linda manager and i cant even load the recovery file of 1.1.2 but no backup on 1.1.2
used astro. can load it but still no back up
sorry. thats cant load on 1.1.2 and no back up on 1.1.3
getoveryourego101 said:
sorry. thats cant load on 1.1.2 and no back up on 1.1.3
Click to expand...
Click to collapse
more accurate 2.73.x.x
x= some numbers
you need to use the goldcard method first. It worked for me with an orange phone
You MIGHT be able to just downgrade to 2.73.61.5 WITHOUT a goldcard, then just install flashrec and then the amon-ra recovery.
MIGHT!!!
But again, follow BTDAG's guide I said earlier, everything you need to know is there.
hey, ive sorted out the problem.
i while back i was trying to download the htc software but had a bit of trouble, wouldnt accept my serial number. so a mate gave me a copy of it
he gave me the 2.73.6 version and i loaded it
i decided to to download the software off the htc website again and serial accepted and it was the 2.73.5 version. went through the whole thing again and it worked like a beaut!
Got the new rom install, just gotta figure whats new.
so the problem was the htc rom was a different version that i should have had.
but thanks guys for all your help, i really appreciate it!
Hey all,
I have a Hero on 3 UK network and since the stupid network dont seem to be releasing any updates for it, I want to root it and manually put 2.1/2.2 on there.
Problem is, NONE of the guides on how to flash it work.
Here's what I've tried so far:
Goldcard method - I have succesfully created a goldcard using a Kingston 1GB card (tested on a Desire and works). Trying to downgrade to the stock HTC ROM using HTC's RUU gives me error 140 (bootloader version error).
Rooting the phone - Phone is all hooked up to ADB, can poll it for information etc. Tried to boot it into a recovery image but get an error saying the following: "downloading 'boot.img'... FAILED (remote: not allow)"
Alternate rooting method - So I found out ROM version 2.73 or whatever it is has some kind of extra security on it. The guides are advising me to download flashrec.apk and install on phone to backup then flash the recovery sector of the phone. This doesnt work. I can neither backup nor apply the recovery images. Even if I override the backup part, it still wont work Just gives me yet another error.
Seems that my Hero is locked down with some impossible to break security. Anyone else having the same difficulty with Three UK? If so are there any other ways you guys may have come up with to root/flash your phone? I'm getting really pissed off with it and am probably going to do an insurance job on it if I cant flash it.
FYI, this phone has not been updated since August 2009. Everything on it is stock from Three UK.
Versions (if you think it's useful):
Firmware: 1.5
Build: 2.73.771.62
Baseband (radio): 63.18.55.06IU_6.35.08.22
Kernel: 2.6.27-430d1aea
Any help I shall be most grateful for!!
Follow my newbie guide. Should talk you through it step by step.
The bootloader error is probably a driver thing. Update your HTC Sync and it should update the drivers.
Sorry, just noticed the thread got moved, my mistake.
Anyone able to shed any more light on it?
I followed the noobie guide and it didnt work. I have the latest version of HTC Sync installed.
Insurance job looking more likely.
Still with error 140? Did you update the driver in fastboot / bootloader mode?
Alternatively try this: http://forum.xda-developers.com/showthread.php?t=726118
btdag said:
Still with error 140? Did you update the driver in fastboot / bootloader mode?
Alternatively try this: http://forum.xda-developers.com/showthread.php?t=726118
Click to expand...
Click to collapse
Which one is your noobie thread mate? I followed several threads off this forum all claiming to be noobie. TBH, they were all pretty straight forward enough, and worked when I helped my mate flash his Desire.
Min can be found here: http://forum.xda-developers.com/showthread.php?t=645253 (it's also in my signature )
Ok yeah, I'll just go over the points in your guide then explain how it failed...
Using Flashrec to backup and apply a recovery image...
Flashrec simply doesnt work on my phone (have tried about 3 different versions, including the very latest which is 1.13). No functions work. Cant even use the bypass backup button (hidden button to the right of backup button). That section ended there for me.
Goldcard method...
No matter what RUU I try to downgrade to, it does not work. Keep getting error 140 (incorrect bootloader version). The goldcard I made definitely works as we used the same one to downgrade my mates Desire today.
I found some other guides, which looked like they might help as they go a bit further, but ultimately every time I try and actually do something, it gets blocked, access denied or some other error.
Flashrec won't work if you're on the wrong version of android (i.e. not downgraded using goldcard).
Goldcard is fine it is most likely your drivers in your bootloader mode that are wrong - check them first.
Drivers were ok. I managed to downgrade using a newer version of the stock HTC ROM after scouring these forums for hours.
So in short... ALL GOOD.
Only problem I have now is that there is no manual update option on eclair (1.5). The 2.1 FOTA updates attempted to download before I setup the WiFi and now it wont come back.
If you want to stay official then you can put the month forward a few and the update should show up again.
Surely the point of this was to get root and a custom rom though no?
The point was actually to get Droid 2.1 'cos 3Uk are dragging their heels big time, but now opens up the options of loading custom ROM's.
TBH I'm happy just to have 2.1. Eclair was doing my head in with all its bugs.
Thanks for the tip with the date - it worked!
i wounder if you did it or not ? cuz o have the same demmn problem with my hero G2 touch t-mobile nothing work for me i try all methods i think last solution is to bring a big hummer and break it as i like (
Fellow 3 UK Hero Owner
I'd just like to add how angry I was when the 2.1 update failed to show up. The Goldcard method worked perfectly for me, then I looked at custom ROMs. I currently run Gingerbread and I have to say, not only is it SUPER fast and smooth but its way less buggy than the stock Hero ROMs.
I'm with the Cronos crew. To get the latest ROM, search for cronosproject (.org) and click forums. (cant post link because i haven't posted 8 times )
Seriously, you wont regret it
best way to fix this is...... make sure u have a file manager, download universal androot to your computer and then to your phone install through file manger and root phone then once rooted install rec image with rom manager from market.....there you go its rooted now follow my guide to flash custom roms properly and to root phones....
mayb its ur android version
may i please know it i can surely help you
As Modaco's boot image "Superboot (for Nexus One)" got no more updates after Android build version GRI40 and we're on GRK39F for some time now; and even though the Superboot GRI40 version gave you root as desired (https://bexton.net/2011/09/24/root-access-for-nexus-one-on-android-2-3-6-grk39f-superboot/), that Superboot version also caused some problems with wifi connection and had an outdated su binary, as well as an outdated Superuser.apk.
To cut a long story short, i did it on my own: Bexboot. A boot image - especially for Android GRK39F on passion devices. I compiled it (based on a guide by Modaco himself) from the stock GRK39F source of my own Nexus One. Also it includes the lates Superuser.apk (v3.0.5) and the latest su binary (v3.0).
Here you go: https://bexton.net/2011/10/12/bexboot-root-nexus-one-passion-grk39f/
Any feedback highly appreciated.
[UPDATE#1 08.11.2011]:
Please don't use v1 (link above) any longer. Instead use the Bexboot v2.0 (link below). It was rebuilt from a completely clean stock rom, what solves the compatibilty issues, some reported for v1. (Also it includes the latest Superuser.apk (3.0.6), as well as the latest su binary (3.0.3).)
https://bexton.net/2011/11/07/bexboot-for-passion-version-2-root-for-nexus-one-with-android-grk39f/
[UPDATE#2 11.12.2011]:
As i forgot to pay the invoice for the server where my blog is running on, it is offline since yesterday. :/ Anyway, i uploaded a copy of the zip archive containing all files you need to root your device to http://www.nahklick.de/user/stephan/bexboot.v2.GRK39F_OTA.zip. To get the instructions, follow this link http://www.google.com/search?q="bexboot"+version+2 and use the Google cache to view the original site. Thx
[UPDATE#3 20.02.2012]:
Files and instructions mirrored at request: http://code.google.com/p/bexboot/
i've posted this on my blog aswell. Nice work
http://patrick.oberdorf.net/2011/10/12/nexus-one-root-rechte-mit-stock-rom/
I've tried that, it does not work.
The fastboot utility says:
downloading 'boot.img'... OKAY
booting... OKAY
Then the phone reboots still not rooted.
zc2 said:
I've tried that, it does not work.
The fastboot utility says:
downloading 'boot.img'... OKAY
booting... OKAY
Then the phone reboots still not rooted.
Click to expand...
Click to collapse
Hi zc2,
sorry for the long response time, i was on a business trip and didn't had the time to check in. I received a bunch of similar issue reports so i did a factory reset and rebuilt the bootloader from a completely clean stock rom.
First comments confirm that it now also works for persons, that had the same issue like you with v1. So if you're still interested in it, check out the updated release version: https://bexton.net/2011/11/07/bexboot-for-passion-version-2-root-for-nexus-one-with-android-grk39f/
Hi Bexton, thank you for the response. I actually was able to root my phone using the instructions from the following post:
http://forum.xda-developers.com/showpost.php?p=18527514&postcount=1853
V2 Failed for me
Bexton said:
...use the Bexboot v2.0 (link below)....
Click to expand...
Click to collapse
Hi there. Thanks for your efforts. I have build GRK39F and ran your version 2 on Windows 7 (64 bit).
During step 6 of your procedure, the write proceudre failed with this error:
FAILED (remote: signature verify fail)
Any ideas? Diagnostic questions for me?
goattee said:
Hi there. Thanks for your efforts. I have build GRK39F and ran your version 2 on Windows 7 (64 bit).
During step 6 of your procedure, the write proceudre failed with this error:
FAILED (remote: signature verify fail)
Any ideas? Diagnostic questions for me?
Click to expand...
Click to collapse
Have you seen this comment / my answer: https://bexton.net/2011/11/07/bexbo...or-nexus-one-with-android-grk39f/#comment-179 ?
It is much likely due to an issue with your hboot version. Your provider probably pushed a locked SPL in an update that renders fastboot unusable. Maybe the link in my comment can help!? Let me know..
Greetz
Thanks for such a fast reply. I bought the phone in Bangkok. It was a "grey market" item from the Hong Kong market. I am not sure whether my Thai carrier even bothers with such things.
I looked at the link but unfortunately for me, I have only the most primitive understanding of how to deal with the bootloader, etc. So I can't even grasp what aspects of that thread apply to me. I really need step-by-step instructions. So unless I can find someone with more mastery, I guess I will only dream of Cyanogen Mod on my phone.
goattee said:
Hi there. Thanks for your efforts. I have build GRK39F and ran your version 2 on Windows 7 (64 bit).
During step 6 of your procedure, the write proceudre failed with this error:
FAILED (remote: signature verify fail)
Any ideas? Diagnostic questions for me?
Click to expand...
Click to collapse
Bexton said:
Have you seen this comment / my answer: https://bexton.net/2011/11/07/bexbo...or-nexus-one-with-android-grk39f/#comment-179 ?
It is much likely due to an issue with your hboot version. Your provider probably pushed a locked SPL in an update that renders fastboot unusable. Maybe the link in my comment can help!? Let me know..
Greetz
Click to expand...
Click to collapse
You will get that error if you are trying to use fastboot commands without first having unlocked your bootloader.
That error has nothing to do with the HBOOT version on Nexus One's. You cannot "push" a locked SPL to an N1 if you've already unlocked your bootloader. The bootloader unlock flag is set in the radio NV memory, so once you have unlocked the bootloader, you cannot relock it (unless you have S-OFF), even if you reflash another stock hboot.
efrant said:
You will get that error if you are trying to use fastboot commands without first having unlocked your bootloader.
That error has nothing to do with the HBOOT version on Nexus One's. You cannot "push" a locked SPL to an N1 if you've already unlocked your bootloader. The bootloader unlock flag is set in the radio NV memory, so once you have unlocked the bootloader, you cannot relock it (unless you have S-OFF), even if you reflash another stock hboot.
Click to expand...
Click to collapse
I realize you're trying to clarify. But I don't understand any of the terminology. The only thing I am capable of is following a prescribed procedure. I thought this procedure was going to unlock and root the phone. I guess I was wrong.
I don't have the diagnostic skills to change direction if things don't go in a predictable fashion-- I've only used stock devices up until now and this was my first attempt. I guess the best I can hope for is to make contact with someone more experienced when I am next in the US and have that person assist me. It makes it more difficult because most of what I am finding online is either old (pre-Gingerbread) or it assumes the user has hacked their Nexus One in the past and just needs to bring it up to date.
My goal is to get past the memory problems I am having by installing a custom ROM with a minimal set of apps in phone memory-- and more customizability.
nice man! It worked on the first go! Top job!
I have one question though! Is it safe to flash Clockword Mod recovery and then flash custom ROMs, or will it end in not finding the recovery image as is the case with other efforts to root 2.3.6?
Thanks!
davelis828 said:
nice man! It worked on the first go! Top job!
I have one question though! Is it safe to flash Clockword Mod recovery and then flash custom ROMs, or will it end in not finding the recovery image as is the case with other efforts to root 2.3.6?
Thanks!
Click to expand...
Click to collapse
No prob. You can use: https://bexton.net/android/n1/recoveries/recovery-clockwork-5.0.2.0-passion.img
If needed, here's the full stock GRK39F: https://bexton.net/android/n1/sys/grk39f/ota.zip and here the update: https://bexton.net/android/n1/sys/grk39f/d323ca384aaa.signed-passion-GRK39F-from-GRJ22.d323ca38.zip
o thanx ma! i appreciate your feedback, you did it on both sites aswell
Respect!
Mirror created at request: http://code.google.com/p/bexboot/
I gave superoneclick a go before trying this method. It worked flawlessly.
Sent from my Nexus One using Vodka
Source code availability?
Hi Bexton,
first of all, thanks for your work!
Next, I'd like to replace the Superuser app by Koush' one (https://github.com/koush/Superuser/).
Would it be possible to get the source code of bexboot?
None is available at http://code.google.com/p/bexboot/source/checkout...
Regards,
Patrick.
I have an at&t variant HTC m8, I recently stitched to cricket wireless. SIM swap went fine. I've been wanting to gain root to remove att bloatware. I'm on android version 5.0.2. My main issue is I've gotten nowhere unlocking boot loader using a pc. Tonight I resorted to using kingroot from Google play,which worked on third attempt. However supersu said it needs an update.
So basically I'm lost and trying to find away to gain root without a computer if possible.
I've never used kingroot. What happens if you try to update the root binary?
May be a bit irrelevant. I think you'll need to unlock the bootloader to do what you want (delete bloatware). I don't think kingroot alone will get it done. Reason being, you can't modify the system partition with root alone. You need kernel mod wp_mod, which is flashed with custom recovery TWRP. And you need an unlocked bootloader to flash custom recovery.
What issues did you have exactly when trying to unlock the bootloader?
I believe my main issue was that my pc is out of date running an unauthorized widows 7 lol. I was unable to obtain adb or any twrp files to unlock boot loader hence my attempt at a one click type solution. I think I'm going to read up more and try the whole process over this weekend, but any tips guides or instructions would be helpful. The more I have looked into this the more conflicted things have become.
Lewis715 said:
I was unable to obtain adb or any twrp files to unlock boot loader hence my attempt at a one click type solution.
Click to expand...
Click to collapse
Not sure what "unable to obtain adb" means if you don't explain what happens exactly, where you are trying to get the files, etc. So all I can do is assume, and hope that I don't suggest you do things you already tried.
If you want an adb/fastboot installer, the following should work, and decently up to date: http://forum.xda-developers.com/showthread.php?t=2317790
Otherwise, there are other adb installers if you just type "easy adb" into the XDA search function.
No such thing as TWRP files that can help you unlock the bootloader. By definition, you can't install custom recovery until the bootloader is unlocked, and TWRP is a custom recovery. So nothing can be done with or by any TWRP files until you unlock the bootloader.
Lewis715 said:
I think I'm going to read up more and try the whole process over this weekend, but any tips guides or instructions would be helpful. The more I have looked into this the more conflicted things have become.
Click to expand...
Click to collapse
Again, can't really help with what is "conflicted" unless you give some specific details.
Its understandable that a lot of the threads may be confusing, as the info is often outdated. This is getting to be an old device, and a lot of folks that wrote the various guides have moved on, and not updating the guides.
The following is a pretty good AT&T specific guide: http://forum.xda-developers.com/showthread.php?t=2799796
But as mentioned, some things are outdated:
1) The driver package is old. You can get updated drivers by downloading HTC Sync from the HTC website. After installing (which will also install HTC drivers) you can uninstall Sync, but keep the drivers; if you don't want Sync (but I haven't had any problems keeping it).
2) I believe the Dropbox link for adb installer is dead, but I already gave an alternative above.
3) The TWRP version is really old, don't use it! Get TWRP 3.0.2 from here: https://dl.twrp.me/m8/
The exception might be in the stock Android version on your phone is old, but if you tell me what it says for OS number on the bootloader screen, I can advise more specifically.
4) TWRP version is old, again, don't use it! v2.76 is the latest "stable" version, and you can get it here: https://download.chainfire.eu/969/SuperSU/UPDATE-SuperSU-v2.76-20160630161323.zip
Everything else in the guide should still apply.
Vomer's guide is also a good one:
http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
Again, the TWRP version is out of date (use the current one linked above).
You only need to do Sections 0 and 1, as the remainder of the guide (S-off, SuperCID) doesn't apply for what you are doing (unlock bootloader, custom recovery, and root).
Also, highly recommended to make a TWRP backup of the stock ROM, before you root.
After root, flash wp_mod with TWRP to enable system partition changes to stick (and deleting bloatware is a system change). What wp_mod depends on your Android version. But for Marshallow, the wp_mod can be found here (you just need the zip wp_mod, not the whole ROM): http://forum.xda-developers.com/htc-one-m8/development/rom-stock-unlocked-developer-sense-7-t3262894
Thanks for the help I'll give it another try, honestly have no real need to mess with device. I know the phone is old but I still have it and it works better than others I've had.
Lewis715 said:
Thanks for the help I'll give it another try, honestly have no real need to mess with device. I know the phone is old but I still have it and it works better than others I've had.
Click to expand...
Click to collapse
Of course, the vast majority of us don't have any real need to mess with the device. But we do, nonetheless!