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
Related
UPDATE: My Experience Getting The Phone Flashed to the 2.73.405.5-rooted-signed.zip
Phone CAN be flashed!
Old Version:
Build: 2.73.728.5 146733 CL#61267 release-keys
Kernal: 2.6.27-8dd6deee [email protected] )
Baseband: 63.18.55.06EU_6.35.06.18
New Version (pre-rooted):
Build: 2.73.405.5 146733 CL#61267 release-keys
Kernal: 2.6.27-8dd6deee [email protected] )
Baseband: 63.18.55.06EU_6.35.06.18
The phone did not have android market on it initially as it was the Malaysian (SEA) version. This is how I flashed it to the WWE version with market and most locales etc.
1. Choose a ROM (Link to Generic ROM's inc. pre-rooted
They will be in the update.zip format, as this is the format we need. The link I have given is for the generic versions with nothing added to them.
2. Download the appropriate files
- Flashrec Download the latest version from here (fastboot will not work for this phone kernal)
- Amon RA Recovery Image
Either: (For Installing .apk's)
- HTC Sync
or
- OI File Manager
3. Install Flashrec
Either using HTC Sync or OI File Manager install the flashrec apk onto your phone.
To install with OI File Manager, just copy to your SD Card, and browse to the SD card and select the file.
4. Run Flashrec
Select backup recovery image (the last option), and let that finish
Then type into the box up the top the following
/sdcard/Recovery-RA-HERO-v1.2.2.img
And select the button below the textbox (flash recovery image)
Once this is done, your recovery image will be flashed, and you can now boot into recovery mode!
5. Backing Up
Rename the ROM file you downloaded to update.zip
Save it to the root directory on your SD card
Turn the phone off, hold down the home and power buttons until a green menu comes up.
*** Select nandroid backup first ***
Let it run its course and then reboot you phone (first option in the menu) and copy the folder 'nandroid' from your SD card to your computer and store it somewhere safe
6. Flashing new ROM
Reboot your phone again into the recovery image (home + power buttons)
And select Wipe/Factory Reset
Then select Apply:update.zip
Let this run, and when it is finished, you will have the 'good' software, and android market!
With this method you can apply any other ROM you want (MoDaCo for instance)...
Hope my learning experience will help some other people!
I have the exact ROM (bought my Hero in Malaysia)
It can be flashed. I use flashrec, Amon Ra's and official pre-rooted 2.73.450.5 update image.
Yes there is no Market, and that's why I flashed it with another ROM.
Micksta said:
I've been looking around for a while and found one thread that's related to my phone. And only found 1 with people talking about this release.
But I am unsure if this phone can be rooted/flashed.
Build: 2.73.728.5 146733 CL#61267 release-keys
Kernal: 2.6.27-8dd6deee [email protected] )
Baseband: 63.18.55.06EU_6.35.06.18
It came like this, I have not flashed the updated Hero rom on it, from what I know its the SEA version of the Hero with no market on it. And I really would like to have the market on it
Has anyone else had experience in trying to root/flash this version of the Hero?
Thanks
Click to expand...
Click to collapse
You're damn lucky dude that you've got THAT kernel version. Check out the thread which says that flashrec doesn't work and those guys have a slightly different kernel and are having hell of a trouble trying to flash a recovery image and a new ROM.
Yep, your best bet is to use FLASHREC AND AMON_RA'S recovery image, then go for any ROM you like (as long as you do not get and Customer ID error). Good luck
Geochelone said:
I have the exact ROM (bought my Hero in Malaysia)
It can be flashed. I use flashrec, Amon Ra's and official pre-rooted 2.73.450.5 update image.
Yes there is no Market, and that's why I flashed it with another ROM.
Click to expand...
Click to collapse
How did you bypass the customer ID error? Did you use RUU or update.zip??
salmanbodla said:
How did you bypass the customer ID error? Did you use RUU or update.zip??
Click to expand...
Click to collapse
I am assuming he used update.zip, I have updated my first post to reflect on my experiences flashing my Hero.
hey guys I'm totally new to this and I think I messed this up already... I'm pretty confused by all this - I am not a computer/technical person in the least I just want market place... anyways I messed up in flashrec and now I don't have the right options - I reset the phone and reinstalled flashrec and I get "phone is ebi1/32a" at the top, the type box, and 'download recovery image' and 'restore backup image buttons'... how do I fix this or atleast get it back to original..? sorry I'm so ignorant, I've not done anything like this before.
Micksta said:
/sdcard/Recovery-RA-HERO-v1.2.2.img
Click to expand...
Click to collapse
I know this is going to be a dumb question but where does this go... after /flashrec or after .org or in place of the whole thing... ?
NM I got it
Thanks for this post. I just succesfully flashed my htc hero.
No i can look for some nice custom roms.
Awesome
The unlockr instructions were way too involved and require hacking an sdcard.
Thanks for sharing.
for some reason i did all kinds of editing to the phone supposed by the website the unlocker to unlock my htc hero.. now after doing all that they said it was as easy as 1...2...3... so after i did the cmd editing and phone cmd editing im still not being able to backup the original img that i have now.. so i understand that once you select backup that there is a load bar that starts working but when using fleshrec (or watever) i select backup and nothing happens... i might have done it already just not too sure is there anyway to check on the HTC Hero by Sprint???
-Thanks in advance
also holding down menu and power button on my phone (htc hero) it just puts me in safe mode ?????
I had to follow unlockr instructions for hackign an sd card as i had perfect spl. It was the only way
----
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 guys,I'm trying to root my Hero,but I am having sort of a technical difficulty.I have tried using the flashrec method,but when I click "Backup recovery image" it says "Backup failed:Command not found".I searched the forums and only thing I found was that if my firmware is patched flashrec will not work.What does it mean that I have a patched firmware?Sorry for the question,but I am partially noob!Also,can I try this http://forum.xda-developers.com/showthread.php?t=543571 method?Seems pretty easy,but the title says "If you have a 2.73+ rom with the new boot you will need to follow This Post to boot the recovery image".I have the stock Cupcake ROM and just fed up waiting for Eclair!My build number is 2.73.405.38 CL#70768 release-keys(yes,it says all that exactly).
And for god's sake guys,please tell me for sure!If I brick my phone I am screwed!Tottaly!
And finally,why the heck will we won't be able to root if we update our Hero with the official 2.1?Seriously,it doesn't make sense to me!
Thanks in advance!
tolis626 said:
Hey guys,I'm trying to root my Hero,but I am having sort of a technical difficulty.I have tried using the flashrec method,but when I click "Backup recovery image" it says "Backup failed:Command not found".I searched the forums and only thing I found was that if my firmware is patched flashrec will not work.What does it mean that I have a patched firmware?Sorry for the question,but I am partially noob!Also,can I try this http://forum.xda-developers.com/showthread.php?t=543571 method?Seems pretty easy,but the title says "If you have a 2.73+ rom with the new boot you will need to follow This Post to boot the recovery image".I have the stock Cupcake ROM and just fed up waiting for Eclair!My build number is 2.73.405.38 CL#70768 release-keys(yes,it says all that exactly).
And for god's sake guys,please tell me for sure!If I brick my phone I am screwed!Tottaly!
And finally,why the heck will we won't be able to root if we update our Hero with the official 2.1?Seriously,it doesn't make sense to me!
Thanks in advance!
Click to expand...
Click to collapse
Everything you need is at http://www.villainrom.co.uk/viewtopic.php?f=46&p=14520#p14520
You will need gold card method iirc.
As for new ROM, there's a new splthat makes it secure, and exploits via. Kernel are patched.
Oops. Double post
Ouch...
First off thank you very much for your reply!But are you absolutely sure there is no alternative?The goldcard procedure seems like a major pain in the a$$ to get working!And,if there is no alternative,is it surely safe?No danger to brick my phone etc.
Thanks!
I'm pretty sure, there's no alternative. But I can tell you, Goldcard Method just sound so much more complicated then it really is. Just read the guide once or twice and your phone will be downgraded and rooted within a few minutes.
Good luck on your rooting. It's worth it
But no bricking,eh?I know I start being annoying,but please try to understand!I don't mind about the complexity,I will nail it,I just haven't tried anything with my Hero and Android yet and don't know what to pay attention to,what to avoid etc..
And another question.I have backed my data up using MyBackup.I will be able to recover it using a custom rom,right?
Also,do I need to be root to flash a radio?And is it necessary?I have radio 63.18.55.06FU_6.35.07.08.Thanks!
You need a recovery rom to flash a radio - you'll find that is very different from "rooting"
tolis626 said:
But no bricking,eh?I know I start being annoying,but please try to understand!I don't mind about the complexity,I will nail it,I just haven't tried anything with my Hero and Android yet and don't know what to pay attention to,what to avoid etc..
And another question.I have backed my data up using MyBackup.I will be able to recover it using a custom rom,right?
Click to expand...
Click to collapse
As a total newbie to this i managed it on my second attempt yesterday. Most important thing i found was to make sure you mount the card as a physical and not a logical.
It's pretty safe from bricking too, i allowed flashrec to download its own recovery image but from what i can tell it downloaded the wrong one so when i tried to boot into it the phone crashed. Not to worry, back into android and put a different image on it via usb and used flash rec to to install it and that fixed it.
Then later that evening i put a villain rom release on it and found everything on it was crashing, tried a different one and things were still crashing so in the end i put a leaked unmodified 2.1 build on there and that fixed it
Guys,I'm desperate!I've done the Goldcard procedure to the letter,but get stuck where I have to downgrade my phone.It connects allright with the Goldcard's SD plugged into the phone,the RUU starts,recognises the phone,and then it begins by rebooting it into bootloader.Then,my phone reboots into bootloader and the RUU says waiting for bootloader and an increasing number appears next to the "waiting for bootloader" prompt.It waits for a while,but then the RUU stops and says "Error 172:No usb connection" or something like that.What now?
Try BTDAGs guide on setting up drivers for x64 + x86,... then try again.
-------------------------------------
Sent via the XDA Tapatalk App
Nah,nailed it!It was either a wrong driver or that I had left USB Debugging on.Anyway,thank you all for your support!Right now running VillainROM 10.2 and lovin' it!
Only thing is it gets a little hot when overclocked.Will trying a newer radio help?Everything else is a-okay!
memory card cid not showing
help!! when i try to create a goldcard the memory card CID wont show. after i have typed adb shell the hash symbol come up not the dollar symbol, wat am i doing wrong
cameronA57 said:
help!! when i try to create a goldcard the memory card CID wont show. after i have typed adb shell the hash symbol come up not the dollar symbol, wat am i doing wrong
Click to expand...
Click to collapse
It's meant to be a # not a $ for adb shell.....
ok, sorry to be annoying, why is the cid not found then?
cameronA57 said:
ok, sorry to be annoying, why is the cid not found then?
Click to expand...
Click to collapse
Edit: wait a sec - you did actually type the command at the hash line didn't you? After adb shell you type: "cat /sys/class/mmc_host/mmc1/mmc1:*/cid" after the # symbol and then it comes up with your CID
Driver is probably not set up correctly (my guess). Try following my goldcard procedure instead (part of newbie guide) and see if that helps.
I havent used this method myself but I have heard good things about it.
Cheers,
Captainkrtek
I have T-Mobile G2 touch that is running Android 2.1 and now I want to take it to Android 2.3
A friend of mine "debranded" it from T-Mobile and put a custom ROM on it for me over a year ago but not sure what procedure he used.
The phone doesn't seem to have been rooted.so I am first of all following the procedure I have seen all over these forums and various other sites which is to take it back to kernel 2.73.405.5 in order to root it then proceed from there
The procedure I am following is:
Get the SD card CID code using either ADB or the goldcardtool.exe
Calculate the reverse string using either a website tool or the goldcardtool.exe (tried both methods)
Get emailed the goldcard img file generated by the website
Format the SD card with fat32 and write the contents of the img file to it using either the goldcard tool or manually using a hex editor from sectors 000 to 170 (I have tried both methods)
Restart the phone (should something obvious happen at this point ?)
Thenwith the phone connected to the PC via HTC sync run:
RUU_Hero_HTC_WWE_2.73.405.5_WWE_release_signed_NoDriver.exe
After it goes through trying to install I get an error
Error (140) bootloader version error
I have also tried using RUU_HEROR_HTC_WWE_1.76.405.1_R3_WWE_release_signed_NoDriver.exe
With the same error.
My phone details are
Hboot 1.76.0007 (Hero10000)
Firmware version 2.1- update 1
Baseband version 63.18.55.06PU_6.35.15.11
Kernel 3.36.405.1
Software Number 3.36.405.1
Browser version webkit 3.1
Can anyone tell me where i'm going wrong please ?
thanks in advance
Glen
Harani said:
I have T-Mobile G2 touch that is running Android 2.1 and now I want to take it to Android 2.3
A friend of mine "debranded" it from T-Mobile and put a custom ROM on it for me over a year ago but not sure what procedure he used.
The phone doesn't seem to have been rooted.so I am first of all following the procedure I have seen all over these forums and various other sites which is to take it back to kernel 2.73.405.5 in order to root it then proceed from there
The procedure I am following is:
Get the SD card CID code using either ADB or the goldcardtool.exe
Calculate the reverse string using either a website tool or the goldcardtool.exe (tried both methods)
Get emailed the goldcard img file generated by the website
Format the SD card with fat32 and write the contents of the img file to it using either the goldcard tool or manually using a hex editor from sectors 000 to 170 (I have tried both methods)
Restart the phone (should something obvious happen at this point ?)
Thenwith the phone connected to the PC via HTC sync run:
RUU_Hero_HTC_WWE_2.73.405.5_WWE_release_signed_NoDriver.exe
After it goes through trying to install I get an error
Error (140) bootloader version error
I have also tried using RUU_HEROR_HTC_WWE_1.76.405.1_R3_WWE_release_signed_NoDriver.exe
With the same error.
My phone details are
Hboot 1.76.0007 (Hero10000)
Firmware version 2.1- update 1
Baseband version 63.18.55.06PU_6.35.15.11
Kernel 3.36.405.1
Software Number 3.36.405.1
Browser version webkit 3.1
Can anyone tell me where i'm going wrong please ?
thanks in advance
Glen
Click to expand...
Click to collapse
If your phone has a custom ROM on it then it will be rooted. And what you are doing is a method I'm not familiar with when rooting..
There are simple one-click root methods available in the form of;
z4root or androot.
Use one of them and you will find the process to be much simpler.
Sent from my Hero using XDA Premium App
Hi,
You are right I've just tried Androot and it reports that my phone is already rooted.
However i'm still having a problem that when I try to download and install a 2.3 ROM (Elelinux-7.1.0-Hero-v2.6) i copy it to the SD card rename to update.zip then when i try to enter the updater HOME+PWR i just get a picture of a phone with a red triangle with a red exclamation mark in it.
I had thought this was because i wasn't root which was why i was trying to get to a baseline to start from but it appears not.
I think this and the previous problem may be down to the bootloader version i have installed ?
Harani said:
Hi,
You are right I've just tried Androot and it reports that my phone is already rooted.
However i'm still having a problem that when I try to download and install a 2.3 ROM (Elelinux-7.1.0-Hero-v2.6) i copy it to the SD card rename to update.zip then when i try to enter the updater HOME+PWR i just get a picture of a phone with a red triangle with a red exclamation mark in it.
I had thought this was because i wasn't root which was why i was trying to get to a baseline to start from but it appears not.
I think this and the previous problem may be down to the bootloader version i have installed ?
Click to expand...
Click to collapse
No its because you dont a custom recovery installed, there are a couple guides in these forums which should tell you how to install one or download rom manager from the market and install one from there.
Sent from my Hero using XDA Premium App
Ok Thanks,
have already been trying to flash a custom recovery image but flashrec doesn't work for me. I keep getting "could not run command" the flashrec page http://zenthought.org/content/project/flashrec suggests this may be due to a patched ROM being installed which is part of the reason i was trying to downgrade the ROM in the first place.
I've also been trying to use ADB to flash the recovery image from my PC but i can never seem to get the SD card mounted via USB.
I'll try a market app and see how i get on
update:
downloaded "ROM manager"
When trying to Flash Clockworkmod recovery with it i get an error which says "an error occurred when attempting to run privileged commands"
this sounds like my phone is not rooted despite with androot says. (which fits with what i've read on these forums and also here http://theunlockr.com/2009/10/18/how-to-downgrade-your-htc-hero-so-it-can-be-rooted/
here that i need to go back to kernel 2.73.405.5 in order to root correctly.
I seem to be going round in circles :-/
it seems like i can't flash a custom recovery until i downgrade the ROM and Root it
and i can't downgrade the ROM until i have custom recovery installed
<bangs head against wall>
Did you get a prompt while trying to flash the recovery? ie; A prompt which asked you to allow ROM manager superuser access and you have a yes/no option.
Sent from my HTC Hero using XDA Premium App
Yes and i allowed it. i now have "superuser" running in the background with ROMmanager allowed superuser privileges
i did the first option in the menu which is to flash "clockworkmod recovery"
this time it didn't complain about privileges (Some progress !)
but I then told it to reboot into recovery mode but i still got a red triangle with an exclamation mark in it
then i tried it again and SUCCESS i now have a recovery utility
Off to try to install EliLinux 2.3 now.
Many thanks for the pointers !
it is very much appreciated.
No problem, its what I'm here for .
Sent from my HTC Hero using XDA Premium App
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.