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.
Related
Hi all,
Anyone having the same issues?
As far as I know, the last 4 digits (707.9 or 405.5) represent the region or mobile network and have nothing to do with the update version or build number. So this rom is still the same as 2.73.405.5. Moreover, the flashrec is using an exploit in the android kernel and should theoretically work as far as the kernel stays the same... and it IS still the same!
Now coming to your problem... let me tell you what I experienced:
I had the old stock ROM >> I upgraded it to 2.76.405.5 with the RUU >> wanted to try MoDaCo 2.2, hence installed Flashrec, backed up recovery (worked!), then flashed Cyanogens modified recovery >> turned off the phone and turned it back on with Home and Power buttons, it took me to the recovery screen (all fine!!) >> I installed MCR 2.2 and still everything was fine. The I read about Amon_RA's recovery image and wanted to flash it on top of Cyanogen's recovery using flashrec... and flashrec gave me an error on the backing up step (DIDN'T WORK!) >> I reinstalled the official ROM via RUU >> it removed the original cyanogen's recovery image >> this made flashrec work again!!
So I think, if you already have a recovery image, flashrec does not work to put another on top of it. The way to go then is via ADB SHELL command prompt. This is whay I think... you can try it.
I'm also having the trouble with the same built (2.73.707.9), when i put the cm-hero-recovery.img on the sdcard, then run flash recovery (sdcard/cm-hero-recovery.img) i cant click on backup to flash custom image button, fastboot boot isnt working for me!. Please if someone can help that would be greatly appreciated.
salmanbodla said:
As far as I know, the last 4 digits (707.9 or 405.5) represent the region or mobile network and have nothing to do with the update version or build number. So this rom is still the same as 2.73.405.5. Moreover, the flashrec is using an exploit in the android kernel and should theoretically work as far as the kernel stays the same... and it IS still the same!
Now coming to your problem... let me tell you what I experienced:
I had the old stock ROM >> I upgraded it to 2.76.405.5 with the RUU >> wanted to try MoDaCo 2.2, hence installed Flashrec, backed up recovery (worked!), then flashed Cyanogens modified recovery >> turned off the phone and turned it back on with Home and Power buttons, it took me to the recovery screen (all fine!!) >> I installed MCR 2.2 and still everything was fine. The I read about Amon_RA's recovery image and wanted to flash it on top of Cyanogen's recovery using flashrec... and flashrec gave me an error on the backing up step (DIDN'T WORK!) >> I reinstalled the official ROM via RUU >> it removed the original cyanogen's recovery image >> this made flashrec work again!!
So I think, if you already have a recovery image, flashrec does not work to put another on top of it. The way to go then is via ADB SHELL command prompt. This is whay I think... you can try it.
Click to expand...
Click to collapse
I only have cm-hero-recovery.img in my sdcard. ADB method will return a "not allowed" error..
I am also having the same problem. Flashrec says backup failed but more importantly it says flash failed.
My 2.73.707.9 ROM is straight out of the box so I do not have any recovery image installed. Much appreciated if some clever person can help out. Thanks!
Leechoonhwee said:
I only have cm-hero-recovery.img in my sdcard. ADB method will return a "not allowed" error..
Click to expand...
Click to collapse
I'm Having the exact same problem with the adb commant prompt.
I tried to close all apps with taskiller and tried to use flashrec again and again without any luck, I can't even click on the flash custom image button, I can only click on backup, and it gives me an error.
Leechoonhwee said:
Hi all,
Anyone having the same issues?
Click to expand...
Click to collapse
I have ticked usb debugging and C:\Hero>fastboot boot cm-hero-recovery.img
downloading 'boot.img'... FAILED (remote: not allow)
C:\androidsdk\tools>fastboot devices
HT991L900567 fastboot
C:\Hero>fastboot boot cm-hero-recovery.img
downloading 'boot.img'... FAILED (remote: not allow)
C:\androidsdk\tools>fastboot devices
HT991L900567 fastboot
I have tried flashrec and followed the instructions and it says fail.
It cannot start with back up.
Thanks
Can you guys who are having trouble with flashrec, please give following info:
1) Detailed version of your kernel... if the kernel has changes, flashrec is no longer supposed to work as it was an exploit in the old/current kernel.
2) Where is this ROM 2.76.707.9 from? Which region? Which carrier?
salmanbodla said:
Can you guys who are having trouble with flashrec, please give following info:
1) Detailed version of your kernel... if the kernel has changes, flashrec is no longer supposed to work as it was an exploit in the old/current kernel.
2) Where is this ROM 2.76.707.9 from? Which region? Which carrier?
Click to expand...
Click to collapse
Hi, Kernel Version is 2.6.27-44690c1a [email protected] )
Build number : 2.73.707.9 146733 CL#62020 release-keys
This version is for Singapore, malaysia and thailand regions. It's unlocked
awsy44 said:
Hi, Kernel Version is 2.6.27-44690c1a [email protected] )
Build number : 2.73.707.9 146733 CL#62020 release-keys
This version is for Singapore, malaysia and thailand regions. It's unlocked
Click to expand...
Click to collapse
I have the exactly same Kernel version. Some new discovery
1. Use the drivers from SDK 1.6. Phone in normal mode. Adb devices and fastboot devices can recognise the phone.
2. Fastboot USB mode. Fastboot devices recognise devices while adb returns nothing.
OK, I am running the official new European ROM 2.76.405.5 with the following kernel:
2.6.27-8dd6deee [email protected] )
I don't know how different it is from yours, but some numbers are certainly different. May be that is the reason, but I am afraid I am not sure. So keep trying - you may be lucky!
Or else, you can always TRY toinstall a European Hero ROM. The new official relase is really good and stable. If it installs on your device, you are all sorted You can find the links on XDA to download it as an RUU.
salmanbodla said:
Or else, you can always TRY toinstall a European Hero ROM. The new official relase is really good and stable. If it installs on your device, you are all sorted You can find the links on XDA to download it as an RUU.
Click to expand...
Click to collapse
I am getting an error when trying to update the official hero rom
ERROR [131] : CUSTOMER ID ERROR and on the phone it says update failed,
I tried 2.73.405.5 and 2.73.728.5 as well, they both gave me the same error.
I Don't why any sort of upgrade or image recovery isn't working on this phone!.
salmanbodla said:
Can you guys who are having trouble with flashrec, please give following info:
1) Detailed version of your kernel... if the kernel has changes, flashrec is no longer supposed to work as it was an exploit in the old/current kernel.
2) Where is this ROM 2.76.707.9 from? Which region? Which carrier?
Click to expand...
Click to collapse
1. Linux version 2.6.27-44690c1a ([email protected]) (gcc version 4.3.2 (Sourcery G++ Lite 2008q3-72) ) #739 PREEMPT Thu Aug 27 19:50:51 CST 2009
2. the ROM on my unbranded HK retail version (htc_asia_hk_wwe) is 2.73.721.9 146733 CL#62020 release-keys
Hey roger,
same here, look like the kernel expliot is fixed:
#adb push /tmp/flashrec-1.1.2-20090909/assets/raw/asroot /sqlite_stmt_journals
932 KB/s (81188 bytes in 0.085s)
#adb shell /sqlite_stmt_journals/asroot /sqlite_stmt_journals/abc /system/bin/sh
FAILURE: Didn't get root.
awsy44 said:
I am getting an error when trying to update the official hero rom
ERROR [131] : CUSTOMER ID ERROR and on the phone it says update failed,
I tried 2.73.405.5 and 2.73.728.5 as well, they both gave me the same error.
I Don't why any sort of upgrade or image recovery isn't working on this phone!.
Click to expand...
Click to collapse
You have CIDlock on youre phone, so it won't work without some tricks.
http://forum.xda-developers.com/showthread.php?t=559806
Heppieboeddah said:
You have CIDlock on youre phone, so it won't work without some tricks.
http://forum.xda-developers.com/showthread.php?t=559806
Click to expand...
Click to collapse
Do you think thats the problem , because I checked the link , my phone is already unlocked, Do you think HTC made the phone un update-able?.
awsy44 said:
Do you think thats the problem , because I checked the link , my phone is already unlocked, Do you think HTC made the phone un update-able?.
Click to expand...
Click to collapse
Your phone is unlocked in a sense that you can insert any sim card and it works. CID lock means that you cannot flash ROMs other than your region.
salmanbodla said:
Or else, you can always TRY toinstall a European Hero ROM. The new official relase is really good and stable. If it installs on your device, you are all sorted You can find the links on XDA to download it as an RUU.
Click to expand...
Click to collapse
Yeah... thought of that but Europe ver does not comes with Chinese IME...
Leechoonhwee said:
Yeah... thought of that but Europe ver does not comes with Chinese IME...
Click to expand...
Click to collapse
Then I think the best way to go is to install Modaco rom version 2.2 enhanced - that has Chinese IME in it. About MCR 2.3, people have several complaints, but there is no harm in trying. Oh but the main question is how will you install the recovery image to do all this rooting/flashing since flashrec is the only option available after the upgarde (I suppose!). The new hboot file won't even allow you to "fastboot boot recovery.img". That's a bit of a shame but I am sure cleverer people out there will soon find a hack
----
update:
-- just2mention: (22.03.2010)
latest HTC update (ROM Version:2.73.61.66 for Orange /Release Date: 2010-02-04)
and ROOT rights + flashing custom ROMS will NOT WORK
check page (3) for further information and problem solving :=)
------------------
continuing with original post
---------------------------------------------------------------------------
hey guys,
i bought my HTC Hero (Orange UK) locked a few days ago, and it arrived yesterday at morning
I spent at least 12h trying to unlock it :=) reading all posts over the whole www At 6am in the morning today, i finally could say: yeah i got it unlocked :=) and yeah, i also got the firmware downgraded
So, there is just one requirement (if anyone did it without one, please let me know): At least, for some time (borrowed from a friend) you need an Orange-Sim-Card
You need it to logg into your phone once, so that your pc installs the correct adb interface drivers (if you never got a sim card, you will never be able to contact adb interface) and enable the usb debugging mode on your android phone (so that adb works).
Otherwise i wouldn't have been able to get the Point 1 done correctly. (get the CID...)
=> Other Things you need to install:
- unlock code (maybe from http://www.unlock-now.com/)
- Android SDK
- i took the normal usb drivers (sdk-supports, folder "usb-driver")
so the exact how to:
1) at first (there is no way to bypass it) do exactly the following (create a Gold-Card):
Create a Goldcard (xda-post)
2) flash a custom recovery rom via adb interface (Android SDK):
Code:
adb shell reboot bootloader
fastboot boot recovery-RA-HERO-v1.2.3.img
adb shell mount /sdcard
adb push recovery-RA-HERO-v1.2.3.img /sdcard/recovery-RA-HERO-v1.2.3.img
adb shell flash_image recovery /sdcard/recovery-RA-HERO-v1.2.3.img
adb shell reboot
(got code from: http://forum.xda-developers.com/showthread.php?t=561124
3) Now you can flash any rom u like (maybe at first, if everything works, do a custom backup (nandroid))
i chose: HTC Generic 2.73.405.38
originally from: http://android.modaco.com/content/htc-hero-hero-modaco-com/291942/09-10-hero-roms-radios-in-update-zip-format/
really important: check the requirements above!
get access to an orange sim card. not important which one...
live here in austria, and got an AUT-Orange Card from a friend, but I think you definitely need one!
This was performed on a Windows 7 64 bit machine
greets && good luck to everyone who does this, hope this saves you a lot of time!
I am a novice and having probs....will be trying these steps over the weekend but a few questions in the meantime:-
I can successfully create a goldcard...
but the ROM downgrade bombs out with the 131 error which I believe is because Orange have tweaked it and is effectively locked to them?
Does the custom recovery get around the downgrading problem? I'm guessing it replaces the 'Orange Rom' with a basic image?
If the custom recovery is successful, are you 'unlocked' at that stage? Is your phone bricked if the custom recovery fails?
If the custom recovery is successful, does that give you the ability to do a Nandroid backup or are there specific steps that need to be done first?....(where does Nandroid backup the image to?...sd card? another part of the phone memory?
If custom recovery is successful, is it simply a case of getting the rom you want (such as modaco) and then launching it from the pc with your phone synched and goldcard inserted?
Apologies for all the questions but I'm trying to get my head around how this whole process works. Thanks for any help.
Trying hard to see the point of this thread/poll, when this method for unlocking the Orange Hero has been known for a while now!
Regards,
Dave
Paradaz said:
I can successfully create a goldcard...
but the ROM downgrade bombs out with the 131 error which I believe is because Orange have tweaked it and is effectively locked to them?
Click to expand...
Click to collapse
sry, never seen before
Paradaz said:
Does the custom recovery get around the downgrading problem? I'm guessing it replaces the 'Orange Rom' with a basic image?
Click to expand...
Click to collapse
custom recovery, i think, replaces just the "recovery" ;=) boot loader image, the running rom stays the same meanwhile
Paradaz said:
If the custom recovery is successful, are you 'unlocked' at that stage? Is your phone bricked if the custom recovery fails?
Click to expand...
Click to collapse
not yet regarding to above, the rom hasn't change and so the unlock key, won't work either.
Paradaz said:
If the custom recovery is successful, does that give you the ability to do a Nandroid backup or are there specific steps that need to be done first?....(where does Nandroid backup the image to?...sd card? another part of the phone memory?
Click to expand...
Click to collapse
no, if the custom recovery is complete, you can do an nandroid backup as u like. it backups directly to /sdcard/nandroid/..
Paradaz said:
If custom recovery is successful, is it simply a case of getting the rom you want (such as modaco) and then launching it from the pc with your phone synched and goldcard inserted?
Click to expand...
Click to collapse
it the easiest thing you can imagine, put the downloaded rom onto the sd drive, custom recovery lets you choose "restore: browse" you select the image file directly on your sdcard (name doesn't matteR) , wait , and it's done
Paradaz said:
Apologies for all the questions but I'm trying to get my head around how this whole process works. Thanks for any help.
Click to expand...
Click to collapse
never mind i'm welcome to answer your questions
good luck!
The one Thing i forgot above, i bought a unlock key on
http://www.unlock-now.com/
should be clear
foxmeister said:
Trying hard to see the point of this thread/poll, when this method for unlocking the Orange Hero has been known for a while now!
Click to expand...
Click to collapse
but never summed up to one thread
from the beginning to the end.
greets
I presume that the 'recovery' is not available on the phone by default? When I hold the home key after powering on, it just has a sort of warning picture next to the phone.....no text displayed and no buttons do anything at that stage, only option is to take the battery out to kill the power.
Gonna have a go at unlocking this using the instructions later tonight.
I have finally got my Orange UK Hero sorted out.......
to cut a long story short, I had the most recent Orange UK ROM, which stops the custom recovery and doesn't alllow a change of bootloader (I got the 'remote ID' error when following your instructions and therefore couldn't flash it using your method.
In the end I went down the 'flashrec' route and eventually managed to get a standard ROM on, backed it up with Nandroid and then unlocked the mobile. Took a lot of hours faffing around and I'm starting to understand how it all fits together now...thanks for the steer. Regards Daz
Paradaz said:
I presume that the 'recovery' is not available on the phone by default? .
Click to expand...
Click to collapse
Thats exactly why you have to do this whole procedure
good luck!
does the website provide the unlocking code for 3 Network locked Hero,thanks
can't tell you, just that they don't work with orange ;=) except you reflesh, but i read over the net, that the keys work in 98% of all cases.
hi
i was wondering after the goldcard thing do i have to follow the flashrec thing? because since i dont have a network i won't be able to download a file manager.
shaff said:
i was wondering after the goldcard thing do i have to follow the flashrec thing? because since i dont have a network i won't be able to download a file manager.
Click to expand...
Click to collapse
without any network connection, i don't think it will be possible...
sry && greetings,
Just to let you know my solution, as I had a PM asking for assistance.
Basically the goldcard method didn't work for me, (creating it was fine, but that's as far as it got)....after research I found out that the most recent Orange Hero's have firmware installed which blocks this process.
Anyway, I used the flashrec method, instructions are here
The url above also has the links to the two files that you need to pull this off. These aren't my instructions so credit to the author.
I have done this on two HTC Hero's now which were both locked to Orange, and they both sailed through without a problem. I also bought my unlock codes from www.htccode.com and had them both unlocked about 5 minutes after payment by PayPal.
Hope this helps anyone else with the 131 error problems (Orange firmware blocking the goldcard method) and thanks for crazyVII (thread starter) for also helping me out.
hi i am totally new to android thing and this all process. sorry if i sound stupid. when i try to run adb while creating gold card it comes on as dost windows and goes off instantly cant type any command whatsoever can u plz tell me wts wrong and i've tried on windows 7 and xp as well thanks in advance
br
it looks like you got an adb problem.
try this to see the message:
open a console window ( start-> run -> type "cmd" - pressENTER )
then run the command again!
good look!
OK, there is a very easy way.
Just upgrade your orange firmware to the oranges official latest firmware: ROM Version:2.73.61.66 for Orange
download here:
http://www.htc.com/uk/SupportViewNews.aspx?dl_id=864&news_id=514
Then you can just use the codes that you have and it will unlock the device!
you can get the code from:
http://www.unlock-now.com/
Hope this helps
cheers
hey, thx for the post )
some more questions ;=)
can you explain what this update contains? is it already android 2.1?
does it realy work
what does your little orange logo in the right upper corner of your user-box mean ? ;D
sry man would be glad for info // affirmation
greets
hi
benedict.s
thanks alot brother u saved my time thanks very much
It would be so good if this would work for Orange romania also but when i try to download the update by entering the s/n it says that the upload is not for me. so i should wait ahwhile i guess.
crazyVII said:
hey, thx for the post )
some more questions ;=)
can you explain what this update contains? is it already android 2.1?
does it realy work
what does your little orange logo in the right upper corner of your user-box mean ? ;D
sry man would be glad for info // affirmation
greets
Click to expand...
Click to collapse
It definitely wont be Android 2.1 as it hasn't been released yet, you will know for sure when it is released as EVERYONE will be talking about it!!!
Does it really work?... Hmmm,... I *think* so, but I only assume that from IRFAN99's comment saying...
irfan99 said:
benedict.s
thanks alot brother u saved my time thanks very much
Click to expand...
Click to collapse
But dont take that as gospel, you know what they say, "assumption is the mother of all f*~K ups"!!!
Can anyone please confirm if that works????
..... And the Orange logo is just referring to the network that BENEDICT.S is on, you can select yours in your profile settings.
And lastly,...
kasmq said:
It would be so good if this would work for Orange romania also but when i try to download the update by entering the s/n it says that the upload is not for me. so i should wait ahwhile i guess.
Click to expand...
Click to collapse
You can get the update that BENEDICT.S is talking about from here,... http://forum.xda-developers.com/showthread.php?t=559622
Let us know how it goes yeah?!
Peace out.
.
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
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
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!