• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root problems in the installing ROM process

this is what happens

hero cvt ship s-on
hboot-1.76.0007 (hero100000)
microp-010f
touch panel -syn0104
radio-6.35.08.29
aug 4 2009, 19:43:30

hboot

checking

cid incorrect
update fail
do you want to rebbot device
yes
no
 
CID incorrect? That's the thing the goldcard is there to spoof I believe....

Have you reformatted the goldcard at any point? Or perhaps it just didn't work?

EDIT: Actually, apparently:

This guide explains how to create a GoldCard. A GoldCard is a special SD card which, when inserted into your device, allows you to flash RUU files with a different CID to your own device. For example, if you own a T-Mobile branded device, this will allow you to flash a generic ROM.

Your goldcard didn't work.

Don't want to jynx things but, maybe if we get that sorted.....
 
no i just ran the tool got the cid and patched mms then it said congratulations you now a have a goldcard
 
ok im in the middle of doing it but the goldcard method im using now is basically the same process as i have already done aprt form i only had to click to rev site etc . i will carry on tho
 
the command prompt wont work again lol cant get past part 8 .. says internal external etc etc ...

i'll give anyone
 
ok got to part 55 and it does not say anything like what it does in step 55 so i guess its all good


when this 2.1 becomes available for 3 will that update the ROM toowill i be able to mess about with it then
 
tried the heroimg again still says same thing tried update.zip from recovery still cant press nothing , tried running ruu still cuts out when waiting for bootloader
 
is there nothing like omnius on the net that will allow me to flash a ROM to my not so super hero
 
right last night i completely wiped everthing i have downloaded from ruu flash rec and everything else i have been told to download and started from scratch was up til about 6 this morning started again taking my time to make sure i was getting things right and surprise surprise nothing worked again lol everything covered in this thread and all the others sites posted here zilch :(

so i have come to the conclussion that my handset is faulty because i really cant think of any thing else
 
I've got doubts about your PC tbh. Something isn't right if you can't run basic commands from the prompt, and it's possible that's messing up the RUU installation.
 
i can run everything else in command prompt because i flashed my mums lg cookie with new firmware other day with the aid of cmd, but anything to do with what i downloaded just wont get acknowleged,

i not long ago do a re format of my pc too , everything is fine apart from cmd with the sdk
 
I don't understand why it won't recognise adb.exe when the file is run from its own directory. :confused:

What did you use to unzip the SDK archive? In Explorer right-click on the \sdk folder, select "Properties" and check under "Security" that Users have read/execute permission for that folder. Does your user account have Administrator rights?

I hate remote debugging! :(
 
i used right click and extract

as i have full control over every program i ever install , i instantly go to my user name and allow full control
 
slug i tried again in the cmd and it come up with loads of stuff but way to much to write here lol
 
attached if full list of things it says in 2 parts


although is not sdk\tools dir this is all it would let me do as when doing the dir bit it say internal external etc etc cant find path
 

Attachments

  • cmdpt1.jpg
    cmdpt1.jpg
    192.6 KB · Views: 44
  • cmdpt2.jpg
    cmdpt2.jpg
    155.7 KB · Views: 78
Well, that's how my command prompt responds given that command, so that's a good sign.

What about if you stick 'cd' infront of it and remove adb.exe?

So open command prompt and enter cd C:\android\tools\ rather than C:\android\tools\adb.exe.

Hopefully the text in front of the cursor will change from C:\users\adz to c:\android\tools\adb

Then you can try running adb remount
 
Once you've ran cd C:\android\tools\, enter and run adb remount and let it go for a few seconds. It should give you a message about the daemon being restarted successfully. From then on you can just enter any adb command you want.

EDIT: I just hope these commands work when your firmware isn't rooted.

Supposedly these are the commands you need to flash a new recovery if you have the stock recovery:

adb shell reboot bootloader
fastboot boot recovery-RA-hero-v1.6.2.img
adb shell mount /sdcard
adb push recovery-RA-hero-v1.6.2.img /sdcard/recovery-RA-hero-v1.6.2.img
adb shell flash_image recovery /sdcard/recovery-RA-hero-v1.6.2.img
adb shell reboot

(Entered and run one line at a time, not all at once).
 
ok heres what it said adb remount

adb server is out of date. killing ......
*daemon has started successfully*
remount failed : operation not permitted


just following other steps
 
Back
Top Bottom