Related
I REFER to this guide: http://forum.xda-developers.com/showthread.php?p=10757949#post10757949
My thought is that this is definetely a step in the right direction.
Whereas it does not give the HBoot access that we are all waiting for, it might re-open some vulnerabilities that do, so I think that I am going to have a happy day now.
step3 we get shell root now. open a cmd and input adb shell(make sure you have install relative tools) relative tools ? what are u mean from where//?
When i enter su root, it says : su not found
Whats the matter ??
Sent from my HTC Wildfire using XDA App
Hi
The link dont work http://www.android-hilfe.de/attachme...lash_image.zip on step 9
sorry but I think you guys won't have any chance here. I think it doesn't matter which ROM you have running as long as the boot loader is still locked... The problem was never the FroYo 2.2 ROM itself but the HBOOT it contains.
So I think the only way to get rid of this problem is waiting for Unrevoked to support HBOOT 1.01.0001....
Nice that's like they're doing it with the legends.
http://forum.xda-developers.com/showthread.php?t=894465
Can you try to put on a recovery mod? Then It " doesn't " matter what hboot is on you wildfire.
I'm trying to find a way to push a another hboot over this one. Like htc has the possibility. There has to be a way to change your hboot version. My biggest problem is finding the right signature.
nice job!
I noticed they have managed to downgrade the rom and the hboot on the legend, its seems more people work on legends then on our wildfire. Simply meaning it seems to take us ages to do what other people have already done.
I for one am trying and getting nowhere fast lol is there any one out there thats close to rooting or downgrading the wildfires new hboot? I have got temp root and downgraded to the 2.1 rom but still have the same hboot so cant get root! Also cant downgrade the hboot still searching for ideas!
I'm trying to modify an old Hboot so that the new Hboot thinks it's newer so let it update. Or modify a new one so that I doesn't make a problem to be downgraded. Supposing that you can flash hboot 1.01 to hboot 1.01 and then to a lower version.
Am I right to think that the cn froyo came with hboot 0.83 ?
If it works like you said, then this is something new as this exploits 1.01 and not 0.83 ?
Anyone knows the difference between the two hboots or is this question. Irrelevant here ?
Do flashing a RUU rom with Hboot 0.83 included will downgrade the Hboot ?
BlasBlas said:
I'm trying to modify an old Hboot so that the new Hboot thinks it's newer so let it update. Or modify a new one so that I doesn't make a problem to be downgraded. Supposing that you can flash hboot 1.01 to hboot 1.01 and then to a lower version.
Click to expand...
Click to collapse
That would be great if it works, you are more knowledgable then me lol i wouldnt know where to start on that. I've been tinkering but not as deep as replacing or modding the hboot. Been hoping unrevoked would have a solution by now but there are little or no comms from them saying if its possible or even how far they have got! so its still a waiting game.
kev94 said:
Do flashing a RUU rom with Hboot 0.83 included will downgrade the Hboot ?
Click to expand...
Click to collapse
No, if it were so easy, the solution would have certainly be posted already.
since we can gain temp root, there should be a way to replace tha hboot manually...can we replace it via cmd using simple copy-paste commands?
step3 we get shell root now. open a cmd and input adb shell(make sure you have install relative tools)
Please explaint me because i am confused (open cmd from the windows or from the wildfire and what is the relative tools must i install in order to proceed?
dem012 said:
step3 we get shell root now. open a cmd and input adb shell(make sure you have install relative tools)
Please explaint me because i am confused (open cmd from the windows or from the wildfire and what is the relative tools must i install in order to proceed?
Click to expand...
Click to collapse
open command prompt on your pc (go to start then run or the text box if your on vista and type cmd) this will open a command prompt window.
the tools you need are the android sdk tools to access adb found here:- http://developer.android.com/sdk/index.html download the .zip and once downloaded un zip to c:/
google search for a guide to set up android sdk and adb loads of guides out there
also install htc sync from htc site as the drivers in the package will be needed to connect to adb.
Can some body give me the flash tool or a working link to it?
thx!
BlasBlas said:
Can some body give me the flash tool or a working link to it?
thx!
Click to expand...
Click to collapse
Sorry my bad - I'm not allowed to post outside links yet, due to the board rules.
You will be able to find the link in this topic:
http://forum.xda-developers.com/showthread.php?t=847443
i will update the first post with the correct link
this can be a solution a modified hboot. I still don't know why its good to downgrade to 2.1 with hboot 1.00.10 We cannot use unrevoked so its no use to do that.
Hi guys, Once again this guide thread comes from the mixture of everyone suggestions and ideas to make your phone S-ON with shipped ROM for warranty!
Collected the following info from the thread, Not my own idea!
First install the ADB and SDK tools and folders, mainly install the Fastboot!
If u dont have fastboot enabled see this http://wiki.cyanogenmod.com/wiki/Fastboot and this http://dottech.org/tipsntricks/21534/how-to-install-adb-and-fastboot-on-your-windows-computer-for-use-with-your-android-phone/
First Go here http://forum.xda-developers.com/showthread.php?t=1033922 and install the shipped ROM which u had before .
Use this method http://forum.xda-developers.com/showpost.php?p=18079795&postcount=1 to install the ROM, But this alone wont get you s-on when you do the process from the above link, Your phone will be Physically S-On but in the bootloader it will still show you s-off!
To change the bootloader to s-on then you need to follow the steps below,
1 . Now download this file from http://alpharev.nl/vivo_downgrade.img
2 . You should enable USB debugging mode, Turn your phone into FastBoot by unchecking the fastboot option in power settings
3 . Now your device will be switched off Remove your battery and insert it again.
4 . Now press (VOL DOWN + POWER Button) You will go into bootloader menu.
5 . When you boot into HBOOT, The first option is FASTBOOT. You select the menu options using the Volume Up/Down key. Once you select FASTBOOT menu, press the Power Button and it will take you to the FASTBOOT menu.
6 . Plug your USB cable in and the screen should change to FASTBOOT USB. Then on your PC, open a CMD window and change to the directory where you have installed the Android SDK tools, such adb.exe, fastboot.exe, etc. In the CMD window you would type the command:
fastboot flash hboot vivo_downgrade.img
7 . Wait for sometime, Then you would type the next command:
fastboot reboot-bootloader
8 . Now this is a tricky step, You should Select and open the ROM package you downloaded (But dont install) go to C:\Users\%username%\AppData\Local\Temp and at last folder find rom.zip
9 . You need to open the ROM.zip file and extract the file HBOOT.img from it and copy it to the same directory as the vivo_downgrade.img. Then you would type the command
fastboot flash hboot HBOOT.img
10 . Now again, wait for sometime type the next command:
fastboot reboot-bootloader
That's it you are back to s-on with stock !!!
You may check this by booting your device into BOOTLOADER , If it shows S-on, that's all You Performed the steps correctly!
If you are stuck at SECURITY WARNING BOOTLOADER because of missing some steps, Go to this following thread
http://forum.xda-developers.com/showpost.php?p=18706124&postcount=6
If you have a faulty USB port shake the usb cable it should definitely work at some angel, worked for me!
Thanks to ehsan76, John Anderton, tpbklake, exnerjan
Definitely it willl work
Tested myself!
thanks bro, this is quite useful
Thank you !
Thank you so much my friend ! you really helped me a lot ! now i can root and flash roms feeling safe that i can SN-ON any time again !
ps : I tried the method , it works perfectly !
thanks again !
hassanhm said:
Thank you so much my friend ! you really helped me a lot ! now i can root and flash roms feeling safe that i can SN-ON any time again !
ps : I tried the method , it works perfectly !
thanks again !
Click to expand...
Click to collapse
Glad it worked for you
And this method by santhoshpirate did't work 4 me,
okay i'll tell u one more time, mb it's gonna be quite clear:
i got in the hboot next text:
VIVO PVT SHIIP S-OFF RL
HBOOT-1.13.0000
RADIO-3805.06.03.03_M
But fo real my phone is s-on Revolutionary tell's me that it's s-on, i looking the awy that the right information was in the HBOOT. i hope you understood me.
and yes, i can use OTA update.
Thz, will try it when I.need.to. get bck.the waRranty
Sent from my HTC Incredible S using XDA App
lolkasasa said:
And this method by santhoshpirate did't work 4 me,
okay i'll tell u one more time, mb it's gonna be quite clear:
i got in the hboot next text:
VIVO PVT SHIIP S-OFF RL
HBOOT-1.13.0000
RADIO-3805.06.03.03_M
But fo real my phone is s-on Revolutionary tell's me that it's s-on, i looking the awy that the right information was in the HBOOT. i hope you understood me.
and yes, i can use OTA update.
Click to expand...
Click to collapse
Have you flashed both the .img file correctly?
Sent from my HTC Incredible S using xda premium
yep flash - rebbot - flash - reboot.
Ok now.. s-off ur phone using revolutionary method again and do the whole process(restoring s-on from first as posted in my thread) again..
It should definitely work.. i guarantee it!!
did it about 10 dimes with different ROMS and Hboots.
lolkasasa said:
did it about 10 dimes with different ROMS and Hboots.
Click to expand...
Click to collapse
Now u have custom Rom or the stock ruu which is physically s-on?
Sent from my HTC Incredible S using xda premium
fot ruu rom with sense 3.0 and 2.00.0000 and got S-oFF typed in Hboot but physically s-0n.
now s-off ur device via revolutionary again and install a custom rom , then follow the whole process a posted in the main thread, it should definitely work for your hboot!
santhoshpirate said:
now s-off ur device via revolutionary again and install a custom rom , then follow the whole process a posted in the main thread, it should definitely work for your hboot!
Click to expand...
Click to collapse
Hi Santhosh, Thanks for the detailed steps for guys like me.
I have S-off and Revolutionary recovery and nik's custom rom, i would like to go back to stock rom to get the new update. But do now how to go.
One more thing is you have mentioned that we have to download the shipped rom. But i am not sure which file i have to download and execute it .I am from india and very very newbie here.
Please help me how should i go back to the custom rom and with S-On in order to receive the OTA Update from HTC
sathishmk0280 said:
Hi Santhosh, Thanks for the detailed steps for guys like me.
I have S-off and Revolutionary recovery and nik's custom rom, i would like to go back to stock rom to get the new update. But do now how to go.
One more thing is you have mentioned that we have to download the shipped rom. But i am not sure which file i have to download and execute it .I am from india and very very newbie here.
Please help me how should i go back to the custom rom and with S-On in order to receive the OTA Update from HTC
Click to expand...
Click to collapse
hI SATISH
if u revert back to s-on to update the latest OTA you cannot s-off ur device again because it comes with a newer bootloader.. To know which RUU you should install, then check with fastboot getvar all to know your mainver
Read my full thread and also this http://forum.xda-developers.com/showpost.php?p=16684717&postcount=38
Everything is inside those two threads .. just sit and read .. You will figure it out!
santhoshpirate said:
hI SATISH
if u revert back to s-on to update the latest OTA you cannot s-off ur device again because it comes with a newer bootloader.. To know which RUU you should install, then check with fastboot getvar all to know your mainver
Read my full thread and also this http://forum.xda-developers.com/showpost.php?p=16684717&postcount=38
Everything is inside those two threads .. just sit and read .. You will figure it out!
Click to expand...
Click to collapse
Hi Santosh,
Thank you for the update, I had infact done the S-on ( dont know how i managed to do it, i was having the OTA update somewhere, and i run it as PG32IMG.zip and then flashed the HBOOT image file as you have mentioned and voila the S_ON is back. ).
I know there is no option for S_off again, but i have my bet on you dev's.
Is the update for 2.3.5 is released for indian IS user's or any expected date.?
Waiting to see how the performance.
sathishmk0280 said:
Hi Santosh,
Thank you for the update, I had infact done the S-on ( dont know how i managed to do it, i was having the OTA update somewhere, and i run it as PG32IMG.zip and then flashed the HBOOT image file as you have mentioned and voila the S_ON is back. ).
I know there is no option for S_off again, but i have my bet on you dev's.
Is the update for 2.3.5 is released for indian IS user's or any expected date.?
Waiting to see how the performance.
Click to expand...
Click to collapse
Ya it's worldwide we the indian users will get the OTA in couple of days.. Can you please tell your software number..
If it is 2.12.720.5 please do share with us..! Some of the indian users need the OTA software
Thanks in advance!
santhoshpirate said:
Ya it's worldwide we the indian users will get the OTA in couple of days.. Can you please tell your software number..
If it is 2.12.720.5 please do share with us..! Some of the indian users need the OTA software
Thanks in advance!
Click to expand...
Click to collapse
Hi Santhosh,
This is the file i am having.
OTA_Vivo_Gingerbread_S_hTC_Asia_India_2.12.720.5-1.36.720.1_release. If this is the one Please let me know how should i upload.
Ya this is the one and please upload... It will be really appreciated .. upload it in multiupload and give the link in the shipped rom collection..then football will do the remaining to upload it in file factory
Once again thanks
Sent from my HTC Incredible S using xda premium
I get stuck between step 6 and 7. I entered the command but it keeps saying: sending 'hboot' <1024 KB>...
Any tips?
EDIT: After couple of times trying and turning usb debugging off instead of on it worked (maybe helpful information if others have the same problem)
Hi evre boody...
can any one help me to Arabization this rom:
http://forum.xda-developers.com/showthread.php?t=1583395
Or
give me the last Rom Arabic but not be RUU I need be Zip because my phone is Hong Kong , and I was try to setup Original Arabic RUU and It come to stop at HTC screen
thanks,,,
azoz123456 said:
Hi evre boody...
can any one help me to Arabization this rom:
http://forum.xda-developers.com/showthread.php?t=1583395
Or
give me the last Rom Arabic but not be RUU I need be Zip because my phone is Hong Kong , and I was try to setup Original Arabic RUU and It come to stop at HTC screen
thanks,,,
Click to expand...
Click to collapse
Did you try the Sense 3.0/Android 2.3.5 ROM that is show in this post?
http://forum.xda-developers.com/showthread.php?t=1531904
tpbklake said:
Did you try the Sense 3.0/Android 2.3.5 ROM that is show in this post?
http://forum.xda-developers.com/showthread.php?t=1531904
Click to expand...
Click to collapse
Not Work
Any one can learn me How I can convert the ROM "RUU" to "Zip" ?
azoz123456 said:
Not Work
Any one can learn me How I can convert the ROM "RUU" to "Zip" ?
Click to expand...
Click to collapse
The way to learn is to search. Execute the RUU on the PC and leave the opening screen open. Then go to the %TEMP% directory and search for a file named ROM.zip. That is the file you are looking for. Copy this to our SD card and rename it PG32IMG.zip and then reboot into the bootloader and it will begin installing.
If you need more information search because there is plenty of posts that will give you more information.
tpbklake said:
The way to learn is to search. Execute the RUU on the PC and leave the opening screen open. Then go to the %TEMP% directory and search for a file named ROM.zip. That is the file you are looking for. Copy this to our SD card and rename it PG32IMG.zip and then reboot into the bootloader and it will begin installing.
If you need more information search because there is plenty of posts that will give you more information.
Click to expand...
Click to collapse
thanks bro..
I know this step but this step I do it the and the result is = stay my phone in HTC page why? I dont Know
My CID is hongkong
azoz123456 said:
thanks bro..
I know this step but this step I do it the and the result is = stay my phone in HTC page why? I dont Know
My CID is hongkong
Click to expand...
Click to collapse
Are you S-Off with Revolutionary? If so and you are trying to run the 3.11.405.x RUU, then Revolutionary is preventing the RUU from overwriting the HBOOT.
tpbklake said:
Are you S-Off with Revolutionary? If so and you are trying to run the 3.11.405.x RUU, then Revolutionary is preventing the RUU from overwriting the HBOOT.
Click to expand...
Click to collapse
What is the solution from your view?
my phone is S-Off And I have Recovery and I do S-Off from this youtupe video:
youtube#.com/watch?v=kvg0i8in96M
azoz123456 said:
What is the solution from your view?
my phone is S-Off And I have Recovery and I do S-Off from this youtupe video:
youtube#.com/watch?v=kvg0i8in96M
Click to expand...
Click to collapse
Well the RUU has changed your recovery back to stock, so you need to reflash your custom recovery. After you have your custom recovery back, just flash a custom ROM and you will be good to go.
tpbklake said:
Well the RUU has changed your recovery back to stock, so you need to reflash your custom recovery. After you have your custom recovery back, just flash a custom ROM and you will be good to go.
Click to expand...
Click to collapse
Thanks Bro...
Finally read this:
1-
I have A kitchen Android "Cygwin".
Can you learn my, How I can add Arabic to my custom ROM? or any ROM like this:
http://forum.xda-developers.com/showthread.php?t=1583395
2-
When I flash this:
RUU_Vivo_Gingerbread_S_HTC_ARA_2.12.415.5_Radio_20.2805.30.085AU_3805.04.03.27_M_release_188261_signed
It is Work
but when I flash this:
RUU_VIVO_SENSE30_S_HTC_ARA_3.09.415.2_Radio_20.4802.30.0822U_3822.10.08.28_M_release_227378_signed
It is don't work
Why I don't know.
my Question is :
Why the second ROM don't work with me?
and the zip file can I change some thing inside it "for both RUU" ??
azoz123456 said:
Thanks Bro...
Finally read this:
1-
I have A kitchen Android "Cygwin".
Can you learn my, How I can add Arabic to my custom ROM? or any ROM like this:
http://forum.xda-developers.com/showthread.php?t=1583395
2-
When I flash this:
RUU_Vivo_Gingerbread_S_HTC_ARA_2.12.415.5_Radio_20.2805.30.085AU_3805.04.03.27_M_release_188261_signed
It is Work
but when I flash this:
RUU_VIVO_SENSE30_S_HTC_ARA_3.09.415.2_Radio_20.4802.30.0822U_3822.10.08.28_M_release_227378_signed
It is don't work
Why I don't know.
my Question is :
Why the second ROM don't work with me?
and the zip file can I change some thing inside it "for both RUU" ??
Click to expand...
Click to collapse
S-Off Revolutionary will not be able to flash any Sense 3.0 RUU that because they all require that HBOOT 2.0x be present to boot, which Revolutionary is preventing.
You can use the XDA Kitchen to take the RUU ROM.zip and change it into a flashable custom ROM, but for the 3.09.415 RUU you need to modify and recompile the boot.img file to get it to run on Revolutionary HBOOT like I did for the 3.08.405/3.11.405 stock rooted ROMs.
You could try taking the boot.img file from one of those ROMs and try it with your 3.09.415 RUU. After you flash the RUU, reboot into FASTBOOT USB mode and flash the boot.img file and then it should boot.
[Q] Downgrade HBoot 2.00 Gingerbread 2.3.5 with HTC sence 3.0 "Permission denied"
I think it's the right place to ask this question
I read almost every thread, however I got confused and couldn't for the life of me, figure out what to do
Here's the problem that is asked so many times, but all with confusing discussions:
I got HTC Incredible s with Gingerbread 2.3.5 and Hboot 2.00 and software number 3.09.415.2
I did the unlock via HTCdev -------------------> no problem
Installed recovery ---------------------------------> no problem
The problem is, I can't downgrade Hboot 2.00 to 1.16 or 1.13. I face this problem after giving command for adb shell:
cd C:\Android
adb.exe shell
adb misc_version /data/local/tmp/ ----------------> from this point. All i get is "permission denied"
I tried using HTC toolkit, making a gold card (the process in which 3 questions were to answer: you device rooted? - want a goldcard?-got unlocked via HTCdev?) - HIS tool.... none would work and after doing these steps, RUU wouldn't install with the error.
can anyone give me a hand?
thanks
Use the script that is in this thread. It should work just fine.
http://forum.xda-developers.com/showthread.php?t=1373697
Just because you have unlocked the bootloader does not mean you are rooted.
You should probably try answering NO to the are you rooted question and see where that gets you.
tpbklake said:
Use the script that is in this thread. It should work just fine.
http://forum.xda-developers.com/showthread.php?t=1373697
Just because you have unlocked the bootloader does not mean you are rooted.
You should probably try answering NO to the are you rooted question and see where that gets you.
Click to expand...
Click to collapse
I did. I responded with no, and of course another time with yes.
but nonetheless, RUU aborts and tells me that I haven't picked the right RUU.
Edit: I forgot to tell, I flashed Superuser through recovery, nothing changed
mr-baan said:
I did. I responded with no, and of course another time with yes.
but nonetheless, RUU aborts and tells me that I haven't picked the right RUU.
Edit: I forgot to tell, I flashed Superuser through recovery, nothing changed
Click to expand...
Click to collapse
Flashing SuperUser will give your apps root access, but in order to run the script successfully, you need a ROM that has an unsecured boot.img, such as any custom ROM. Try installing CM 7 and then re-run the script.
That is why you are getting the access denied message while the script is running.
tpbklake said:
Flashing SuperUser will give your apps root access, but in order to run the script successfully, you need a ROM that has an unsecured boot.img, such as any custom ROM. Try installing CM 7 and then re-run the script.
That is why you are getting the access denied message while the script is running.
Click to expand...
Click to collapse
Thanks for the info.
CM7? Where can I find that?
If you mean cm7 ROM, as far as i know, it's a custom ROM. will I be able to install a ROM regarding my cell is s-on and don't have access to root?
mr-baan said:
Thanks for the info.
CM7? Where can I find that?
If you mean cm7 ROM, as far as i know, it's a custom ROM. will I be able to install a ROM regarding my cell is s-on and don't have access to root?
Click to expand...
Click to collapse
You will just be required to pull the boot.img from the .zip file. After installing the ROM, reboot to fasboot menu.
Then type in command: fastboot flash boot boot.img
Both "boot" are required and do not forget the .img at the end. If you changed the file name, just replace the second "boot" in the command line with whatever u renamed it to but do not forget to put .img at the end
072665995 said:
You will just be required to pull the boot.img from the .zip file. After installing the ROM, reboot to fasboot menu.
Then type in command: fastboot flash boot boot.img
Both "boot" are required and do not forget the .img at the end. If you changed the file name, just replace the second "boot" in the command line with whatever u renamed it to but do not forget to put .img at the end
Click to expand...
Click to collapse
I'm sorry, could you expand your answer a little bit and guide me more specifically?
thanks
When u download CM7, its in the form of a .zip file. Open the zip file using winrar or whatever unzipping tool u use. Open it, do not extract it. When you open it, you will find a file named "boot." This is a .img file. Copy (not cut) this file where u have adb.exe, fastboot.exe, and AdbWinApi.dll. I will assume u have these files when u downloaded Android SDK. For simplicity sake, do not rename it. Then put the ROM onto your phone and flash the ROM through your recovery. The boot.img file is in the ROM. After you finish flashing the ROM, reboot to bootloader and from there, enter fastboot mode (shud be the first option. just click power button to select it. Then on you computer, open command prompt and navigate to the file with the boot.img, adb.exe, fastboot.exe, and AdbWinApi.dll. In the command prompt, it should say cd c:/(wherever your android stuff is in)/ another folder maybe for organization)/.....>
from there type in fastboot flash boot boot.img
After a few seconds the ROM will have been flashed to your phone. Reboot and u have CM7 on your phone. Then run the RUU.
If the RUU fails, tell us the error number. Although i dont really know much about this, tpblake does and im sure hed be willing to tell you what the error code means cuz the RUU really doesnt tell u jack.
So I did, step by step
I did all, cm7 worked perfectly. then I did as you said, fastboot boot boot.img
As foreseen, error 155 popped out. "please get the correct ROM update utility and try again"
I would be thankful if you guys help me through.
Yet I have another question. If installing custom ROMs are this easily possible, then why should we do the s-off?
Re: [Q] Downgrade HBoot 2.00 Gingerbread 2.3.5 with HTC sence 3.0 "Permission denied"
mr-baan said:
So I did, step by step
I did all, cm7 worked perfectly. then I did as you said, fastboot boot boot.img
As foreseen, error 155 popped out. "please get the correct ROM update utility and try again"
I would be thankful if you guys help me through.
Yet I have another question. If installing custom ROMs are this easily possible, then why should we do the s-off?
Click to expand...
Click to collapse
You have to s-off to change hboot , rom , kernel , and radio. If you want to downgrade just relock the bootloader and then run the ruu
Sent from my Incredible S using xda premium
zulmajdi said:
You have to s-off to change hboot , rom , kernel , and radio. If you want to downgrade just relock the bootloader and then run the ruu
Sent from my Incredible S using xda premium
Click to expand...
Click to collapse
Once I did the relock, it faced security problems and wasn't working, so I had to unlock it again.
About the second question of mine, I know what s-off is for. My question is, moments ago I flashed CM7 custom ROM to my phone and it works properly. For installing ROMs, being s-off doesn't seem so necessary. or am I wrong?
zulmajdi said:
You have to s-off to change hboot , rom , kernel , and radio. If you want to downgrade just relock the bootloader and then run the ruu
Sent from my Incredible S using xda premium
Click to expand...
Click to collapse
Yes this. Error 155 will pop up if u have an unlocked bootloader. Relock bootloader and rerun RUU assuming the script ran everything right
Edit: To your above question, yes S-OFF isnt necessary. However, it is necessary for some ROMs to have S-OFF or Blackrose HBOOT, the latter of which can only be obtained from achieving S-OFF. And what kind of security problems
Re: [Q] Downgrade HBoot 2.00 Gingerbread 2.3.5 with HTC sence 3.0 "Permission denied"
mr-baan said:
Once I did the relock, it faced security problems and wasn't working, so I had to unlock it again.
About the second question of mine, I know what s-off is for. My question is, moments ago I flashed CM7 custom ROM to my phone and it works properly. For installing ROMs, being s-off doesn't seem so necessary. or am I wrong?
Click to expand...
Click to collapse
No you're not. If you want to custom install radio , kernel , hboot and rom need to gain s-off but some rom no need to s-off. Like miui rom need s-off and hboot blackrose. Just ignore the security thingy. I had the same problem before for the security but i just run the ruu and install it works. It say security problem on fastboot rite? Then just run the ruu while you on fastboot mode. Hope it works
Also adb shell command need super permission from the device. You have to root your device.
Sent from my Incredible S using xda premium
thank you all. it worked. my Hboot is now 1.13.0000
now Revolutionary is giving me crap! It says: invalid Beta key... I did it like a thousend times!
Quick question. shall I unlock it again? because when I do, In the process of HTCdev, I get this error: <fastboot> unknown error
Re: [Q] Downgrade HBoot 2.00 Gingerbread 2.3.5 with HTC sence 3.0 "Permission denied"
mr-baan said:
thank you all. it worked. my Hboot is now 1.13.0000
now Revolutionary is giving me crap!
Quick question. shall I unlock it again? because when I do, In the process of HTCdev, I get this error: unknown error
Click to expand...
Click to collapse
There is a video for incs device tutorial to set revolutionary at youtube. Watch it and try. Glad we can help you ^^
Sent from my Incredible S using xda premium
zulmajdi said:
There is a video for incs device tutorial to set revolutionary at youtube. Watch it and try. Glad we can help you ^^
Sent from my Incredible S using xda premium
Click to expand...
Click to collapse
Oh, I know how. I have this cell phone for about two years. It was root and s-off was due. But some accidents happened and I sent it for warranty, they sent it back with Hboot 2.00.0000.
But my problem is, Beta code sent by revolutionary is invalid when inserted in revolutionary.exe command propmt.
Thank you guys, this worked.
To sum it up, If you have "permission denied" problem with runme - and then, installing the RUU - relock your phone, run the RUU. and everything is there.
Peace
Re: [Q] Downgrade HBoot 2.00 Gingerbread 2.3.5 with HTC sence 3.0 "Permission denied"
mr-baan said:
Thank you guys, this worked.
To sum it up, If you have "permission denied" problem with runme - and then, installing the RUU - relock your phone, run the RUU. and everything is there.
Peace
Click to expand...
Click to collapse
Install blackrose and you basicly done my friend have a good day
Sent from my Incredible S using xda premium
I just got a HTC vivid from a friend .first thing I did is unlock bootloader flash recovery s-off root . Phone is running gb . Here is where I need your help.I try to.flash jb Rom and it would boot. And when I touch screen phone would freeze and reboot.so I restore. What do I have to do to run jellybean ?
Sent from my HTC PH39100 using xda app-developers app
please read the stickies in the dev forum. in order to flash ics or jb you must flash the RUU if you are running gb. just flash the ics RUU and flash whatever jb rom you want after
ZeRo2o9 said:
please read the stickies in the dev forum. in order to flash ics or jb you must flash the RUU if you are running gb. just flash the ics RUU and flash whatever jb rom you want after
Click to expand...
Click to collapse
thanks!!
I'm having a similar problem, but i just dont find the right ICS RUU to flash it seems.
I live in austria, have the htc velocity 4g, with 2.3.7 gingerbread.
Bootloader tells me:
*** UNLOCKED ***
HOLIDAY PVT SHIP S-ON RL
HBOOT-1.85.0023
eMMC-boot
Feb 1 2012,01:02:37
what i did for now:
i unlocked the bootloader (with htcdev), put on the twrp-recovery (2.4.4.0) (with hasoons-tool) and also tried wcxrecovery.img (for BoRKed)
wiped it clear, installed the cm10 [cm-10-20130310-NIGHTLY-holiday] and gapps / later BoRKed
since i am s-on i ran the "fastboot flash boot boot.img" command.
And the result is the reboot-cycle (cyanogenmod10 - with freezing short after the pin-code / permanently rebooting with BoRKed).
I read through the forums and found out that i need a newer hboot (ICS) to be able to install Jellybean ROMS.
as mentioned before, i think that i should lock my bootload and flash the right ICS RUU like told in the vivid-developers-forum.
i tried out the htc_vivid_att_RUU_3.26.502.56_US.exe but it told me [error130] wrong model, so i couldnt finish the RUU.
the wire-trick for s-off is a little bit scary to me, so i didnt try that for the time being.
so, for the time being i am a little bit out of clues and would be very glad if somebody could help me out with the right version of the RUU i should flash (and where i could get it) or am i completely off track here?
thnx, joe
Don't you flash the boot.IMG before you flash the ROM?
HTC_Vivid said:
Don't you flash the boot.IMG before you flash the ROM?
Click to expand...
Click to collapse
the step-by-step written guide from hasoon2000 (link) tells me to do it after i installed the ROM.
Now go back and press install. Go to the folder where the ROM you downloaded, is located in. Select the ROM and slide the screen to flash it. After it flashes, press the back button. Press Reboot and Reboot into bootloader. Open the ROM you downloaded from your computer. You should see boot.img. Extract it to your computer. Open my toolkit and press Flash a Kernel. Locate the boot.img and it will flash it.
After it flashes, press reboot from the phone.
Congrats! Enjoy your fully working or borked ROM! Remember, DO NOT ASK FOR ETAs, DO NOT BUG/PM A DEV ABOUT UPDATES, and BE RESPECTFUL TO THE DEVELOPERS!
Click to expand...
Click to collapse
Don't use twrp 2.4.4...
Switch to 2.4.2.0
Sent from my Vivid 4G using Tapatalk 2
oh, but right now i found it just the other way around.... in the
[SUPERGUIDE] ICS-Root-Flash-Stock
(Optional) Flash a custom Kernel/Recovery (Three options, I suggest the THIRD)
*ATTENTION* IF FLASHING A KERNEL FOR A NEW ROM YOU WANT, YOU MUST FLASH THE ROM IMMEDIATELY AFTER FLASHING THE KERNEL WITHOUT BOOTING UP, THE KERNEL COMES FIRST. OTHERWISE, YOU MIGHT BOOT LOOP.
Click to expand...
Click to collapse
i will give it a try, thanks!
--
edit:
will switch to 2.4.2.0
kernel flash first and then rom (with trwp-2420 recovery) led to the same boot - freeze - cycle with cyanogenmod10 as described before...
i still think that i have to flash to an ICS RUU first, but i just need a working one (without the 130 model-id error)
Joehittn said:
kernel flash first and then rom with trwp-2420 recovery led to the same boot - freeze - cycle with cyanogenmod10 as described before...
i still think that i have to flash to an ICS RUU first, but i just need a working one (without the 130 model-id error)
Click to expand...
Click to collapse
The model id error is because you're trying to flash a Vivid RUU to a Velocity. You'll either need to s-off and super CID, then you can run whatever RUU you want, or you need to get the correct RUU for your device. I was pretty sure that 1.85.0023 and 1.85.0025 were bootloaders that came with ICS though. Maybe I'm remembering wrong about that, but I thought that the first ATT leak had .0023 and the official release had .0025
please run this (from fastboot USB) and reply back with the return
fastboot getvar mainver
(I have the Telstra ICS RUU uploading now if that's what you'll need)
Edit: Here is RUU_HOLIDAY_ICS_35_S_Telstra_WWE_3.25.841.4_Radio_3.02.4740.09_34.20.701040.19_release_246698_signed
Also - if you'd like to try this before any of that, it may work as well (others have had success). From fastboot USB:
fastboot erase cache
Now flash recovery, ROM, boot.img (from my experience, it doesn't matter if the boot.img is flashed before or after the ROM, as long as it's flashed BEFORE trying to actually boot the ROM)
(note that if the problem is your bootloader version, this won't work.)
homeslice976 said:
The model id error is because you're trying to flash a Vivid RUU to a Velocity. You'll either need to s-off and super CID, then you can run whatever RUU you want, or you need to get the correct RUU for your device. I was pretty sure that 1.85.0023 and 1.85.0025 were bootloaders that came with ICS though. Maybe I'm remembering wrong about that, but I thought that the first ATT leak had .0023 and the official release had .0025
please run this (from fastboot USB) and reply back with the return
fastboot getvar mainver
(I have the Telstra ICS RUU uploading now if that's what you'll need)
Edit: Here is RUU_HOLIDAY_ICS_35_S_Telstra_WWE_3.25.841.4_Radio_3.02.4740.09_34.20.701040.19_release_246698_signed
Also - if you'd like to try this before any of that, it may work as well (others have had success). From fastboot USB:
fastboot erase cache
Now flash recovery, ROM, boot.img (from my experience, it doesn't matter if the boot.img is flashed before or after the ROM, as long as it's flashed BEFORE trying to actually boot the ROM)
(note that if the problem is your bootloader version, this won't work.)
Click to expand...
Click to collapse
Camo has a ruu index too.. I think in dev thread
Sent from my HTC PH39100 using Tapatalk 2
mainver: (shows nothing...)
CID: VODAP120
i gave the telstra ruu you uploaded (thank you very much) a try, but it also gave me the model-id-error.
do i have to flash the recovery back (where do i find the stock-recovery? in the backup?), i am always using the twrp242-recovery now.
i tried the steps you wrote down with the same result (boot-cycle).
i think i will have to give the "s-off and super CID" as u mentioned before a try and then use the telstra-ruu. i read that this worked out for some guys in germany. i will do this on saturday, i need to be fully concentrated to do that, not next to work...
thank you very much for now!
One other thing.. you are relocking your bootloader before trying to run the ruu, and you're trying to run the ruu from fastboot?
Sent from my HTC PH39100 using Tapatalk 2
homeslice976 said:
One other thing.. you are relocking your bootloader before trying to run the ruu, and you're trying to run the ruu from fastboot?
Sent from my HTC PH39100 using Tapatalk 2
Click to expand...
Click to collapse
yes, always relocked.
first i ran the RUU (telstra) from the gb-2.3.7 screen, now i tried it from fastboot.
same result - error 130 (model-id)
---------- Post added at 01:36 PM ---------- Previous post was at 01:16 PM ----------
XxSHaDoWxSLaYeRxX said:
Camo has a ruu index too.. I think in dev thread
Sent from my HTC PH39100 using Tapatalk 2
Click to expand...
Click to collapse
I think you mean this thread [Collection] Stock Roms [3/25/13] but i cant find my provider (austria / a1 [telekom]) there. also there has been no OTA ICS launched in austria...
seems that i have to postpone the s-off, cant find the time to do it right now...
i will revive the thread when i finally went through it.
thanks for your help till now.
cyas