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

Root unroot and s-on question.

Can I have a screenshot of windows explorer in details view, showing the file on the c: drive please?

Just so I.can check to see if I see anything awry
 
hope this will do; c drive; file attached i hope
 

Attachments

  • Capture and.JPG
    Capture and.JPG
    75.2 KB · Views: 64
to su root , i have being reading back, looking for something i may have missed. on your post #43 you said...

Edit, don't remove anything from the variables if that's what you're asking...

unfortunately i did.

it now is;

;c:\android-sdk-windows\tools

is this ok.
 
The screenshot looks fine. Why would you remove things from environment variables? How much do you know about windows? If you want windows to work properly, youll put it back exactly how it was.

I don't feel I can talk you through solving this. Do you have any.computer literate friends who could help?
 
Hello, I have now restored the variables back to there original state. I have also checked all the other prerequisite steps. They are all correct. Whilst not being a computer expert I can carry out your instructions, maybe at slower rate than someone more experienced with these programmes. I was at the pc all day yesterday and, whilst waiting for a reply, tried some ideas that came to mind. It can become boring sitting waiting for something to turn up, and you never know. I was just updating you as to what I had tried.

Somehow, as I mentioned earlier, I think the s-off problem is related to it originally being taken of by superoneclick. Then I went down the revolutionary route. This is just to let you some history. This still does not explain why fastboot is not recognised.

I realise you are hindered in your efforts to help me by not sitting at the pc but, working in a problem solving role myself, realise it is better to have as much information as possible to help solve the problem.

this is what is displayed at cmd prompt at present, also trying with the r/click administrator option.


Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Windows\system32>fastboot flash hboot c:\bravo_downgrade.img
'fastboot' is not recognized as an internal or external command,
operable program or batch file.

C:\Windows\system32>

and in user modeMicrosoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Users\stu>fastboot flash hboot c:\bravo_downgrade.img
'fastboot' is not recognized as an internal or external command,
operable program or batch file.

C:\Users\stu>
 
Fastboot was previously recognised. Cmd always gives you the first error in the command line you type.

If fastboot is not recognised, the error is associated to the first word; fastboot.

If error cannot load c:\bravo_downgrade.img, the error is associated to the last part of the command, meaning fastboot IS a recognised command.

So now we have gone backwards.

Let's forget about environment variable all together. Please go into the tools folder and move the adb file and the fastboot file into c: not in any.folder, where the downgrade image is.

Then in the command prompt window, type "cd c:\" you will see c:\users\stuey become c:\.

This means command prompt is running in the c: drive, not where any folders are, so fastboot definitely should be recognised because you put it there.

Firstly, type "fastboot devices" with your phone connected in fastboot mode. See if it can see your phone
 
ok , i am here now, but wondering what to do. i will explain later, if thats ok.;

Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Users\stu>cd c:\

c:\>c:\bravo_downgrade.img
'c:\bravo_downgrade.img' is not recognized as an internal or external command,
operable program or batch file.

c:\>fastboot devices

c:\>fastboot flash hboot c:\bravo_downgrade.img
error: cannot load 'c:\bravo_downgrade.img'


c:\>fastboot flash hboot c:\downgrade.img
error: cannot load 'c:\downgrade.img'


c:\>bravo_downgrade.img
'bravo_downgrade.img' is not recognized as an internal or external command,
operable program or batch file.

c:\>fastboot flash hboot c:\bravo_downgrade.img
error: cannot load 'c:\bravo_downgrade.img'


c:\>fastboot flash hboot c:\bravo_downgrade.img
error: cannot load 'c:\bravo_downgrade.img'


c:\>fastboot flash hboot c:\bravo_downgrade.img
< waiting for device >
sending 'hboot' (512 KB)...
OKAY [ 0.086s]
writing 'hboot'...
FAILED (remote: not allowed)
finished. total time: 0.087s

c:\>fastboot flash hboot c:\bravo_downgrade.img
sending 'hboot' (512 KB)...
OKAY [ 0.087s]
writing 'hboot'...
FAILED (remote: not allowed)
finished. total time: 0.089s

c:\>fastboot flash hboot c:\bravo_downgrade.img
< waiting for device >
sending 'hboot' (512 KB)...
OKAY [ 0.087s]
writing 'hboot'...
FAILED (remote: not allowed)
finished. total time: 0.090s

c:\>
 
Well those last 3 are usually if you're not on the fastboot sceen.

What was the output to fastboot devices?

The hboot definitely still says Alpharev on it?
 
back on this again, this is as far as i can get no matter what i try, thought it had something to do with admin permissions but can not get any further on.


Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Users\stu>cd c:\

c:\>fastboot devices
HT05FPL09205 fastboot

c:\>fastboot flash hboot c:\bravo_downgrade.img
sending 'hboot' (512 KB)...
OKAY [ 0.086s]
writing 'hboot'...
FAILED (remote: not allowed)
finished. total time: 0.088s

c:\>

no ideas left to try.
 
Well that's the stock hboot that comes with the 2.3 Rom so were trying to do something that's already been done. That's why its failing.

So to clarify, there's nothing else to do now
 
ahh, what i was trying to do was aquire s-on.

i`am pleased you have noticed that, been on hours with it.

still a good side in that i now have a understanding about flashing.

is there a way i could gain s-on again.
 
Please can you type all the words and numbers on the hboot screen please? Or better yet, take a photo of it?
 
hboot screen;

bravo pvt1 ship s-off
hboot-1.02.0001
microp-031d
touch panel-synt0101
radio-5.17.05.23
jul 22 2011.16:19:16

that is exactly whats on the screen.
 
Cool. It's completely stock and official s-off. You can't s-on that but there's no need to anyway
 
Ok, my concern is with still being s-off.

Will the new owner be able to carry out updates by the normal means? I have read about someone, cant for the life of me find the post again, who tried to update and his phone locked up with some screen with a symbol in each corner. (Wish I could find you the post.) It was put down to the fact he was unrooted, stock ruu, but still s-off and therefore could not update in the normal manner.

This is what I thought we were trying to achieve, gain s-on, as the phone was in its present state back at post #21. I was assuming you were suggesting flashing the PB zip in fastboot was somehow better than running it from the sd card.

Thanks.
 
stueym said:
Ok, my concern is with still being s-off.

Will the new owner be able to carry out updates by the normal means? I have read about someone, cant for the life of me find the post again, who tried to update and his phone locked up with some screen with a symbol in each corner. (Wish I could find you the post.) It was put down to the fact he was unrooted, stock ruu, but still s-off and therefore could not update in the normal manner.

This is what I thought we were trying to achieve, gain s-on, as the phone was in its present state back at post #21. I was assuming you were suggesting flashing the PB zip in fastboot was somehow better than running it from the sd card.

Thanks.
Click to expand...

Seriously, dont worry about it. Its factory s-off, not modder (i.e you) s-off. When deisres come back from repair from HTC they are now s-off, you just cant do anything like fastboot flash on them.

HTC even have a bootloader unlocker on their dev website. As long as the hboot doesnt say alpharev or revolutionary in the top line in pink letters, its fine.

Honestly, dont worry about it. Its now factory settings.
 
ok. thanks for that.

the last thing i would want to do is assure someone everything is ok with the phone and then problems arise.

so from what you have said all my efforts yesterday were impossible to acheive, waste of time really.
 
ok, thanks for supporting me anyhow.

one plus point is i now have reasonable understanding of the flashing system of which i was a little apprehensive to use before.

cheers.
 
Well only fastboot flashing which would be flashing re overy and hboot only really. ROMs etc will be flashed via recovery.
 
You must log in or register to reply here.
Back
Top Bottom