Develop Bugs

[Q] RUU factory Main version is older

Hi im trying to restore my Desire with factory Rom without root and S-off
Now in Bootloader it says
RAVO UNKNOWN SHIP S-ON
HBOOT - 0.75.0000
MICROP-031D
TOUCH PANEL-SYNT0101
radio-4.05.00.11
mar 5 2010,21:12:15
I tryed many times to flash official RUU
RUU_Bravo_Fastweb_IT_1.15.1600.5_Radio_32.30.00.28 U_4.05.00.11_rel_121996
(my Desire was branded Fastweb)
Everytime there is an error, flashing by bootloader
Main version is older!
Update fail
It shoud happen when HBOOT is newer than RUU , but i think my HBOOT is the right one.
I used goldcard, and then i tryed without but the problem is the same
How can i solve?

The coldcard works by making the phone ignore the CID (customer ID), so that you can install a RUU of ANY brand you wish. It DOES NOT work for bootloader versions, so e.g. once you update your phone to 2.2 (from 2.1), you CAN NOT, go BACK to 2.1 using an older RUU. Hope that helps you to understand it a bit more. As for upgrading your phone, try that:
I don't know whether your phone is GSM or CDMA (since I've never heard of that network) but if your phone is GSM (has a simcard), then use this RUU http://www.mirrorcreator.com/files/...2U_5_11_05_27_release_159811_signed.exe_links
It is the latest WWE (world wide english) RUU so there is no way you will get that error. You need a working goldcard for it to work, but from reading your post it seems you have that covered so you should be fine.

You can go from 2.2 to 2.1 using teppic74's downgrade tool. Its a bit more involved than just flashiong an RUU.
That RUU is in th GSM section on shipped roms, but that doesn't necessarily mean it IS gsm

rootSU said:
You can go from 2.2 to 2.1 using teppic74's downgrade tool. Its a bit more involved than just flashiong an RUU.
That RUU is in th GSM section on shipped roms, but that doesn't necessarily mean it IS gsm
Click to expand...
Click to collapse
Yeeahhh but I said you can't go back using the RUU
and yeah I figured, there's only one BravoC RUU on SR, but I'm just being on the safe side

bortak said:
The coldcard works by making the phone ignore the CID (customer ID), so that you can install a RUU of ANY brand you wish. It DOES NOT work for bootloader versions, so e.g. once you update your phone to 2.2 (from 2.1), you CAN NOT, go BACK to 2.1 using an older RUU. Hope that helps you to understand it a bit more. As for upgrading your phone, try that:
I don't know whether your phone is GSM or CDMA (since I've never heard of that network) but if your phone is GSM (has a simcard), then use this RUU
It is the latest WWE (world wide english) RUU so there is no way you will get that error. You need a working goldcard for it to work, but from reading your post it seems you have that covered so you should be fine.
Click to expand...
Click to collapse
I tryed ur solution, but during flashing there is an error "131 customenr id error"
About the 2nd solution ( downgrade from 2.2 to 2.1) , its right to use it while i have hboot 0.75 (not 0.92) ?
Now i have on Leedroid 2.1.
RUU_Bravo_Fastweb_IT_1.15.1600.5_Radio_32.30.00.28 U_4.05.00.11_rel_121996.exe
So i think i need to have hboot 0.75, and its the hboot i can see in bootloader. Right?
I have to restore it because my touchscreen doesnt work, and warranty end with rooted phones

Downgrade dont work.
When i go in bootloader and i read PB991IMG.zip it says CID ERROR.
I've done goldcard many times, this is what i do:
Format MicroSD 4gb (stock microsd)
Open Gold Card Tool and complete the operation (it says gold card created)
what i do wrong?
When i have to install RUU in bootloader i put inside PB991IMG, so i extract Card and load the file by cardreader.
That error 131 appears everytime but when i try to install Official FASTWEB RUU it disappears and , as i said before, appears BOOTLOADER ERROR

you're either doing the goldcard wrong or your sd-card simply doesn't work as a goldcard.
try this tutorial and try again. http://theunlockr.com/2010/03/10/how-to-create-a-goldcard/

bortak said:
you're either doing the goldcard wrong or your sd-card simply doesn't work as a goldcard.
try this tutorial and try again.
Click to expand...
Click to collapse
Bortak thanks thanks and more thanks!!!
I followed ur guide and now i unrooted phone.
I installed RUU 1.15 so now i have phone branded as factory.
Tomorrow i'll go to service, and i hope they will change my touchscreen.
Thanks a lot again

sfidanza2005 said:
Bortak thanks thanks and more thanks!!!
I followed ur guide and now i unrooted phone.
I installed RUU 1.15 so now i have phone branded as factory.
Tomorrow i'll go to service, and i hope they will change my touchscreen.
Thanks a lot again
Click to expand...
Click to collapse
There's a thank button

[Q] Phone stuck in bootscreen, no answer in troubleshoot

After breaking my previous desire i got a new one from insurance past friday. I s-off and rooted it with revolutionary and ran the alpharev cm7 r2 partition table. All went fine and i installed the CM 7.2 RC rom and started downloading all my apps and stuff.
All seemed fine untill i shutdown my phone last night and when booting it up this morning it doesn't boot up into anything. I can only get into Hboot and fastboot. I've tried booting into recovery but it gets stuck on the boot screen again.
Now i've read the Q&A troubleshooter posted above here and i have already tried reflashing recovery, which sadly still didn't boot after the reflash.
Now i'm completely stuck on what to do and have been searching for over an hour now.
I've read i could do a RUU for my phone, but seeing as alpharev has protection against that i'm not certain that would even help. What would be the best solution here to get my phone working again. (and if possible with the current data on it , i hadn't made a backup of the full install yet)
Edit: some extra info
Hboot 6.93.1002
Bravo PVT3 S-off
radio 5.11.05.27
CM 7.2 RC
clockwork, not sure newest version for desire afaik

Did you try to remove battery?

yes, seeing as that is the only option right now to turn my phone off .
I also ran fastboot oem gencheckpt to force boot into recovery. The phone got stuck at htc splashscreen. I posted the cmd image information in this post.
when i pulled the battery to shut down the phone, the cmd gave and "error, to many links"
edit:
i ran the alpharev downgrade image to overwrite my hboot and see if i could get into recovery after reflashing that aswell. Sadly this didn't work and after flashing both it still gets stuck at the htc splash screen
i ran the downgrade hboot again and will not try to fix it with a RUU
hmm, the phone is still recognized by the pc, but i have a black screen and can't get it to display anything. did i use a bad ruu or? I"m really confused now :|
after looking in the troubleshoot again i tried to flash the bravo stock from alpha rev, but i'm getting a FAILED <remote: signature verify fail>

well seeing as i most likelly need a goldcard now and don't have another android device laying around i will have to continue this tomorrow or tonight.
if ANYBODY has any advice everything is really appriciated!

what RUU did you flash?
if it was under 2.xx that means you did slcd brick have look here

flash bravo stock from alpharev, then run (if you have a goldcard) the 2.2 WWE RUU, or your carriers RUU (make sure it's the latest one)
Check shipped-roms.com

i think i ran this RUU
RUU_Bravo_HTC_Europe_1.15.405.3_Radio_32.30.00.28U _4.05.00.11_release_121865.exe
which i got from this post, which i now see is terribly out-dated xD.
I got my phone from vodafone in Holland, and i just saw an RUU for bravo that was shipped by vodafone UK which also supports the same radio as mine. Is it a safe bet to use that one for the recovery process?
I wasn't able to run any images right now from fastboot for some reason so i will indeed need to make a goldcard. Will do so tomorrow and report back if i've had any succes.
Thanks for the advise!

OK, so i'm a bit confused by that guide i'm afraid...
I've noticed that in step 4 that i'm unable to enter recovery (no surprise seeing as i was unable before the RUU).
I can boot in to fastboot and hboot i think seeing as i get the "device connected sound" in windows. When i then enter ADB devices or fastboot oem gencheckpt it gives me some information, which can be seen in the screenshot.
What i'm now confused about is, do i still need to make a goldcard, and if so how? I tried running that goldcard creater software but it couldn't pull a CID. Should i create a goldcard by just using a phone of my friend (desire s :|)? Or is it possible to just run the right RUU straight away seeing as i can connect to hboot and fastboot, let that run and when that is finished use revolutionary to root my phone agian.
Attached is the cmd for fastboot oem gencheckpt and adb devices, although normally the fastboot oem gencheckpt finished with a "FAILED <status read failed<too many links>>

Gimme bootloader information, also what state is the phone in now, and what have you tried so far. (quick summary)
My bad just read you last posts.
Try the Vodafone RUU, it should work, don't see why it shouldn't. If that fails, make a goldcard with your friends Desire S, and flash the 2.2 WWE RUU.
If that fails then use the 2.3 RUU.

Ah great!!! I ran the vodafone ruu and atleast now i'm getting fastboot and hboot displayed again.
I'll see how far i can get on my own now. Thanks alot for all your help

Darn, aren't there yet...
I can now get into fastboot and hboot WITH it being displayed so that is already a big plus. However i'm still on a off partition format so i need to flash that back to the original partition format.
I'm S-ON right now so i can't do it through fastboot.
So i made the goldcard through my friends phone and place a PB99IMG.zip containing the alpharev bravostock on the goldcard.
When i then boot into HBOOT it gives me the reading PB99IMG.zip but doesn't give me an option to run the update afterwards. I then checked with the RUU i ran from my pc and created an PB99IMG.zip of that and let it run from HBOOT thus checking if the goldcard was functional. This worked perfectly apart from the partition table being screwed.
How can i now either install recovery from my goldcard while being S-ON or how can i succesfully run the bravo_stock image from my goldcard?
edit: I know i could use the old s-off trick from alpharev but i would prefer to use revolutionary instead seeing as it's more up to date...

k i think i know what to do.
i'll just create a bootable USB with the 1.8 hboot from alpharev on it. S-off my device and restore the partitions to stock.
Then run the RUU again so that my phone returns to stock sense and S-on.
After that i should be the basic root process all over again by running revolutionary etc right?

If you're S-ON. You DO NOT need to touch the hboot, and you can't anyway.
If you've got a goldcard just try the WWE RUU. And if that doesn't fix it then the 2.3 RUU.
That's all you need to do. NOTHING else.

The 2.3 RUU (the vodafone one i downloaded) doesn't work.
I don't think any RUU will work for my seeing as i'm still on the CM 7 r2 partition layout instead of the original sense layout (a little mistake i made when running the first faulty RUU). I'll try to run the WWE RUU first, but i don't think it'll achieve anything.
If i would now run the alpharev 1.8 hboot from a bootable USB it shouldn't put my device at risk right? :|
Edit:
i'm actually getting CID incorrect from the WWE RUU from the troubleshoot thread and from another WWE RUU i downloaded from shipped-roms.com
edit2:
alright, i tried 2 WWE RUUs, which when ran from my PC give me ERROR[131]: customer-ID error and a CID incorrect when done from my goldcard... i also tried alpharev hboot 1.8 but that didn't work either for the obvious reason that you need to boot into android and enable usb debugging and the WWE RUUs for i do not know what reason .
Damn i thought i had figured it out before going to college but aparently i was wrong >.<
i don't know if it's relevant but when i try to boot normally i get the HTC splash screen and it vibrates 7 times in a row...

So i think my goldcard might not be as golden as it should be. Should i try it with my other microSD, the one that i actually use in my phone, an 16 gb kingston?
If so can i use the same goldcard.img or should i create a new one?

bortak said:
If you're S-ON. You DO NOT need to touch the hboot, and you can't anyway.
If you've got a goldcard just try the WWE RUU. And if that doesn't fix it then the 2.3 RUU.
That's all you need to do. NOTHING else.
Click to expand...
Click to collapse
Dear god how many times do I just need to repeat myself.
Just download http://www.htcdev.com/process/legal_download/152 , boot into fastboot mode, then run RUU.exe
There is no vodafone 2.3 RUU, there is only one, and it is unbranded.
Elightos said:
So i think my goldcard might not be as golden as it should be. Should i try it with my other microSD, the one that i actually use in my phone, an 16 gb kingston?
If so can i use the same goldcard.img or should i create a new one?
Click to expand...
Click to collapse
If you still get CID error - you do not have a goldcard. Simple as that.
Elightos said:
The 2.3 RUU (the vodafone one i downloaded) doesn't work.
Click to expand...
Click to collapse
The 2.3 RUU always does something, if not for better than for worse.

ah right i'm sorry, i was a bit confused about that ruu because of some of the information displayed on shipped-rom.com. Prolly read it wrong or something.
Anyway the 2.3 RUU did indeed fix it! quite surprised after all this really didn't expect it! Thanks out a load and i'm sorry for touching a nerve there, it's just the first time doing anything like this so it was all a tad bit confusing!

Elightos said:
ah right i'm sorry, i was a bit confused about that ruu because of some of the information displayed on shipped-rom.com. Prolly read it wrong or something.
Anyway the 2.3 RUU did indeed fix it! quite surprised after all this really didn't expect it! Thanks out a load and i'm sorry for touching a nerve there, it's just the first time doing anything like this so it was all a tad bit confusing!
Click to expand...
Click to collapse
Lol don't worry about it, everyone starts of a newb I remember posting some scare stories of mine a while back of when I first started messing with my phone

[Q] hboot 1.03.0003 problem

Hello guys.
As I can see - my problem is unique and almost noone has solved it, but I won't give up.
Okay, let's start from the beginning.
I had stock firmware with 2.29 OS version (no matter to write all the numbers of version, just 2.29). In order to have something newer and with new HTC Sense, I managed to get the Cool3D RunnyMede v7 firmware on my phone.
Like in many tutorials I went on htcdev.com and used to unlocking bootloader. I followed all the steps and finally got the unlocked butloader, but with s-on (I saw no matter on it, as I do now).
Downloaded the clockwork mod, I proceeded to flash my phone, and after some problems I had the custom firmware. Okay, all is good, but what the problem? Problem was that I could not use anything of phone's functions, just had no service. Okay, it was the radio problem. It was caused by that fact that while s-on, I upgrade the firmware but not radio (but it was in archive with firmware too).
Cause I had s-on I had no chance to flash my radio.
S-on was caused by htcdev RUU updater, that made my phone having hboot 1.03.0003.
Now I have no firmware, just clockworkmod 2.5.0.7, s-on and hboot 1.03.0003.
When I try to setup official RUU I have the 140 error, it means that in ROM that I try to set up is lower version of hboot that I have. When I try to replace it on my hboot (extracting it from the hboot updater) I get error 132, it means CID problem, but in android-info.txt in ROM's file I have the same, that on my phone.
Can anyone help me, or I just have to write to HTC Support, and after having no answer break my phone about the nearest wall?..

Check bortak's troubleshooting guide (see my sig).

Thanks, but I've seen it for many times, don't know what can help me...
Maybe goldcard?.. Anything else?

Hi there is a way how to downgrade your 1.03 hboot in resources of bortak's guide or you can find it here
after downgrade you can run revolutionary to get s-off and flash your preferred radio

Hey guy, it looks helpful as nothing I've seen before; thank you; I'll write about the result.

It works.)
Thanks a lot.

Can't downgrade
I have an HTC Desire
S-ON
Bravo PVT4
HBOOT: 1.03.0003
MI CROP-05-1d
TOUCH PANEL-SYNT0101
RADIO-05.11.05.27
And I need a goldcard to be able to downgrade it to 1.02.0001 and I can't get it anywhere, all I've got is the CID 00B100DC08D480804734305553445303 but the website I went to is not working anymore to get the IMG. PLEASE help!

Hi Lagevae
Lagevae said:
It works.)
Thanks a lot.
Click to expand...
Click to collapse
i have the same problem. but the link that give kotag82. not help me, i cant open a USB debugging connection. I like to now how you got to work.

likeadracula said:
i have the same problem. but the link that give kotag82. not help me, i cant open a USB debugging connection. I like to now how you got to work.
Click to expand...
Click to collapse
Follow this guide:
http://forum.xda-developers.com/showthread.php?t=1550397

abaaaabbbb63 said:
Follow this guide:
http://forum.xda-developers.com/showthread.php?t=1550397
Click to expand...
Click to collapse
i tried that link to... i have install clockworkmod and works fine but Cooldroid_Revolution_v9.0 firmware stuck at second htc logo and all ather firmwares that i managed to install. Ruu give error 155. The problem is that i cant access to firmware to use USB debugging for Downgrade the hboot.. and when I tried ι take lot of errors.. looks like dead and .. If someone now how to start USB debugging without the firmware from fastboot it could to samething..

likeadracula said:
i tried that link to... i have install clockworkmod and works fine but Cooldroid_Revolution_v9.0 firmware stuck at second htc logo and all ather firmwares that i managed to install. Ruu give error 155. The problem is that i cant access to firmware to use USB debugging for Downgrade the hboot.. and when I tried ι take lot of errors.. looks like dead and .. If someone now how to start USB debugging without the firmware from fastboot it could to samething..
Click to expand...
Click to collapse
What about this one?
http://forum.xda-developers.com/showthread.php?p=24039156

abaaaabbbb63 said:
What about this one?
http://forum.xda-developers.com/showthread.php?p=24039156
Click to expand...
Click to collapse
Yes the same problem.. at the step 8.. i dont now what to do.. i dont now if i need to use GoldCard my cid is HTC_N34 and i cant change it..

[Q] Desire HD cannot enter bootloader..

I have rooted and have Ace Pvt Eng S-off using AAHK.. fyi, mine is GB shipped, but fortunately pseudo eng boot is working fine..
The problem is when i have flash custom ROM viper and set it up everything, when i enter hboot, i and enter fastboot in the dropdown in hboot menu, after i select bootloader, it scan for a while and it shows message "[PD98DIAG.nbh] No image or wrong image!" or something like that, it is blinking very fast..
But, the phone itself is working, and boot viper very well.. so my question is, do i need to bother putting the right image inside directory somewhere in the sdcard or just left it be?
Sorry for asking this, if there is any thread explaining about this, please direct me to the right way..

yumm91 said:
I have rooted and have Ace Pvt Eng S-off using AAHK.. fyi, mine is GB shipped, but fortunately pseudo eng boot is working fine..
The problem is when i have flash custom ROM viper and set it up everything, when i enter hboot, i and enter fastboot in the dropdown in hboot menu, after i select bootloader, it scan for a while and it shows message "[PD98DIAG.nbh] No image or wrong image!" or something like that, it is blinking very fast..
But, the phone itself is working, and boot viper very well.. so my question is, do i need to bother putting the right image inside directory somewhere in the sdcard or just left it be?
Sorry for asking this, if there is any thread explaining about this, please direct me to the right way..
Click to expand...
Click to collapse
That is perfectly normal....everytime you enter hboot, the phone parses for a PD98IMG.zip file and if you don't have any shows that message. What are you trying to do with the bootloader? Don't mess with that partition as you can end up with a brick. :good:

glevitan said:
That is perfectly normal....everytime you enter hboot, the phone parses for a PD98IMG.zip file and if you don't have any shows that message. What are you trying to do with the bootloader? Don't mess with that partition as you can end up with a brick. :good:
Click to expand...
Click to collapse
I see. So, where can i find the PD981IMG.zip and where should i put it into? fyi, i dont have systeminfo in bootloader but i saw some FAQ and they said that it is normal. But, with that, i dont know if i have a superCID or not. I think i read it somewhere that saying we should rename the custom ROM that we currently use into PD98DIAG.nbh and put it into the root directory so that it will not shows the message "[PD98DIAG.nbh] No image or wrong image!" again.. but is it true? I take a look at the aahk PD981IMG.zip compressed file and custom ROM compressed file but they are completely different..
I'm not using aahk PD981IMG.zip because it is downgrade ROM if i'm not mistaken which is downloaded during rooting, and if i put that file and the bootloader is reading that file, maybe there will be some inconsistency as i am running viper.. Right now i am currently running viperdhdv1.2.3, but i afraid that i might brick my desire hd if i flash another rom.. is that possible? what do you think glevitan?

yumm91 said:
I see. So, where can i find the PD981IMG.zip and where should i put it into? fyi, i dont have systeminfo in bootloader but i saw some FAQ and they said that it is normal. But, with that, i dont know if i have a superCID or not. I think i read it somewhere that saying we should rename the custom ROM that we currently use into PD98DIAG.nbh and put it into the root directory so that it will not shows the message "[PD98DIAG.nbh] No image or wrong image!" again.. but is it true? I take a look at the aahk PD981IMG.zip compressed file and custom ROM compressed file but they are completely different..
I'm not using aahk PD981IMG.zip because it is downgrade ROM if i'm not mistaken which is downloaded during rooting, and if i put that file and the bootloader is reading that file, maybe there will be some inconsistency as i am running viper.. Right now i am currently running viperdhdv1.2.3, but i afraid that i might brick my desire hd if i flash another rom.. is that possible? what do you think glevitan?
Click to expand...
Click to collapse
WHAT???? I can not get a single word of what you said. What are you trying to do?? that is the perfect path to mess your device. Please search and read before messing your device. Use the guide and the thread in my signature to help yourself.

glevitan said:
WHAT???? I can not get a single word of what you said. What are you trying to do?? that is the perfect path to mess your device. Please search and read before messing your device. Use the guide and the thread in my signature to help yourself.
Click to expand...
Click to collapse
LOL.. sorry about my messy explanation.. orait, start from the beginning. Please bear with me...
i have desire HD, GB shipped..
by using AAHK, i finally rooted it with pseudo eng hboot,
install CWM > flash viperdhdv1.2.3 > working fine..
Ok now when i enter bootloader, ( vol- + power button), it does not list systeminfo, so with that I cannot determine whether my device have SuperCID or not, because then i cannot flash unbranded ROMs.. so, question is:
Is there any way to know the CID besides systeminfo?
Is not having SuperCID will prevent my device from flashing any custom ROM?
Regarding this:
Code:
sd checking....
loading....[PD98DIAG.zip]
No Image
Loading....[PD98DIAG.nbh]
No Image or Wrong Image
Loading....[PD98img.zip]
No Image
Loading......[PD98img.nbh]
No Image or wrong image.
Where can i find the right img or nbh file? Do i need to rename the customROM boot.img into one of that and put it into root directory?

yumm91 said:
LOL.. sorry about my messy explanation.. orait, start from the beginning. Please bear with me...
i have desire HD, GB shipped..
by using AAHK, i finally rooted it with pseudo eng hboot,
install CWM > flash viperdhdv1.2.3 > working fine..
Ok now when i enter bootloader, ( vol- + power button), it does not list systeminfo, so with that I cannot determine whether my device have SuperCID or not, because then i cannot flash unbranded ROMs.. so, question is:
Is there any way to know the CID besides systeminfo?
Is not having SuperCID will prevent my device from flashing any custom ROM?
Regarding this:
Code:
sd checking....
loading....[PD98DIAG.zip]
No Image
Loading....[PD98DIAG.nbh]
No Image or Wrong Image
Loading....[PD98img.zip]
No Image
Loading......[PD98img.nbh]
No Image or wrong image.
Where can i find the right img or nbh file? Do i need to rename the customROM boot.img into one of that and put it into root directory?
Click to expand...
Click to collapse
WHATTTTTT??? no buddy...you are doing everything wrong. IF you are S-OFF and have CWM or other custom recovery, then you are ready to go. SuperCID is not for custom roms...it has to be with carriers. System info is never displayed in hboot except for the hboot and radio version...do me a favor, read what I told you or the next time you will be asking help because you got stuck...

glevitan said:
WHATTTTTT??? no buddy...you are doing everything wrong. IF you are S-OFF and have CWM or other custom recovery, then you are ready to go. SuperCID is not for custom roms...it has to be with carriers. System info is never displayed in hboot except for the hboot and radio version...do me a favor, read what I told you or the next time you will be asking help because you got stuck...
Click to expand...
Click to collapse
Ok the file for the zip and nbh is the update image, so if i doesnt want to update anything, why should i put anything inside isn't..
Orait, that one is settled.
When i enter bootloader, it shows "ACE PVT ENG S-OFF RL"
From what i read, RL stands for Relocked right? So is it mean i need to unlock it first to install custom ROM or what? And from what my friends said, ENG S-OFF is not stable and dangerous to flash custom ROMs as there is a chance to brick the device, so first i should try to make it shows "ACE PVT SHIP S-OFF" and after that I will be able to flash any ROM safely.. is that true?

yumm91 said:
Ok the file for the zip and nbh is the update image, so if i doesnt want to update anything, why should i put anything inside isn't..
Orait, that one is settled.
When i enter bootloader, it shows "ACE PVT ENG S-OFF RL"
From what i read, RL stands for Relocked right? So is it mean i need to unlock it first to install custom ROM or what? And from what my friends said, ENG S-OFF is not stable and dangerous to flash custom ROMs as there is a chance to brick the device, so first i should try to make it shows "ACE PVT SHIP S-OFF" and after that I will be able to flash any ROM safely.. is that true?
Click to expand...
Click to collapse
You are not paying attention, are you?
Sent from my GT-N7000 using xda app-developers app

Like the other person said please do a bit.more research and listen a bit more....don't mess with the partitions in your bootloader with s-off you can do some real damage...you don't need to unlock your bl if you already have s-off just go into recovery wipe and flash the zip...

omario8484 said:
Like the other person said please do a bit.more research and listen a bit more....don't mess with the partitions in your bootloader with s-off you can do some real damage...you don't need to unlock your bl if you already have s-off just go into recovery wipe and flash the zip...
Click to expand...
Click to collapse
I guess this is too much for me to comprehend so i just left it right there...
From what i read,
-S-off means security for NAND memory is deactivated, so we can write whatever we want on that..
-ENG hboot is a more advanced hboot compared to stock hboot, like able to flashing kernel or new radio using fastboot..
-So, if i just flashing new custom ROM without flashing radio, this means that my risk of bricking device is near zero right?
-So my question is, if eng hboot is better, why radio s-off is recommended in some thread?
-and why i have RL(Relocked) at the end of S-off?
Please give me some thread that explains about that.. I saw some thread but it is not answered. =.=
p/s: need to have some coffeeee....

yumm91 said:
I guess this is too much for me to comprehend so i just left it right there...
From what i read,
-S-off means security for NAND memory is deactivated, so we can write whatever we want on that..
-ENG hboot is a more advanced hboot compared to stock hboot, like able to flashing kernel or new radio using fastboot..
-So, if i just flashing new custom ROM without flashing radio, this means that my risk of bricking device is near zero right?
-So my question is, if eng hboot is better, why radio s-off is recommended in some thread?
-and why i have RL(Relocked) at the end of S-off?
Please give me some thread that explains about that.. I saw some thread but it is not answered. =.=
p/s: need to have some coffeeee....
Click to expand...
Click to collapse
Just answer this: How on earth is your bootloader relocked, if you never unlocked it?
ENG S-OFF should not be used. S-OFF is more than enough and allows you to flash whatever you want. PERIOD.....don't waste more time.

[Q] Returning to Stock

Hi all. Have not been to this site in a while.
I have an 8181 Desire (Australia - Telstra). Presently running CM7 and Runnymede ROM, with 4EXT recovery.
Before I go too far...yes, I know I should use SEARCH, but honestly I have forgotten so much about modding, I really have no idea what I'm doing anymore...
I want to return to stock and pass the phone on to a friend. I have so far installed Telstra RUU to my PC and I have run Alpharev downgrade. I have now moved to reboot and run the RUU, but I keep booting straight to Bootloader screen, not progressing to main screen. I know this means I have missed a step or forgotten something, but have nfi what that might have been.
I never really learned to flash with Fastboot, so am I able to avoid that and continue the way I am a little more familiar with?
Thanks heaps for any help. In the meantime I will continue to SEARCH and see what I can see. Cheers.

Use the troubleshooting guide stickied to the top of q&a
Search for and then run the 2.3.3 GB RUU

I've found the 2.3.3 GB Telstra RUU and renamed to PB99IMG.zip, placed on SD card. I see a blue progress bar and then "would you like to reboot now?" Each time I reboot, I am straight back to Bootloader screen (not stuck in bootloop, as such).
Working my way thru the TS Guide, but I'm pretty sure I have missed a step or forgotten something along the way... Wondering if phone won't boot properly because I am now running the Downgrade HBoot, which is obviously not compatible with Runnymede.
Am I able to uninstall 4EXT touch? Would like to simplify things as much as I can and would be happy with standard CWM for flashing purposes...
Will keep playing today. I know the phone isn't bricked, so I'm not panicking. Yet.

Try flashing the stock hboot, then RUU
Currently if only flashed the downgrade.img, it's just in a blank state with no actual hboot I believe.
(Make sure you're flashing these hboots thru fastboot, not recovery)

777ace said:
I've found the 2.3.3 GB Telstra RUU and renamed to PB99IMG.zip, placed on SD card. I see a blue progress bar and then "would you like to reboot now?" Each time I reboot, I am straight back to Bootloader screen (not stuck in bootloop, as such).
Working my way thru the TS Guide, but I'm pretty sure I have missed a step or forgotten something along the way... Wondering if phone won't boot properly because I am now running the Downgrade HBoot, which is obviously not compatible with Runnymede.
Am I able to uninstall 4EXT touch? Would like to simplify things as much as I can and would be happy with standard CWM for flashing purposes...
Will keep playing today. I know the phone isn't bricked, so I'm not panicking. Yet.
Click to expand...
Click to collapse
Dont rename the ruu to PB99IMG... It wont work as u found out. So.... On ur pc, run the ruu.exe file that u downloaded, then (if using windows) when it gets to the screen with pic of phone asking to axcept stuff, click start on ur computer, then in search box type "run" then click on run then in that search box type %temp% and search then find the first or second newest folder there will be a file there called rom.zip... Rename that to PB99IMG then put it on the root of ur sdcard and boot into bootloader
---------- Post added at 02:24 AM ---------- Previous post was at 02:22 AM ----------
eddiehk6 said:
Try flashing the stock hboot, then RUU
Currently if only flashed the downgrade.img, it's just in a blank state with no actual hboot I believe.
(Make sure you're flashing these hboots thru fastboot, not recovery)
Click to expand...
Click to collapse
I was typing as u were posting

jmcclue said:
Dont rename the ruu to PB99IMG... It wont work as u found out. So.... On ur pc, run the ruu.exe file that u downloaded, then (if using windows) when it gets to the screen with pic of phone asking to axcept stuff, click start on ur computer, then in search box type "run" then click on run then in that search box type %temp% and search then find the first or second newest folder there will be a file there called rom.zip... Rename that to PB99IMG then put it on the root of ur sdcard and boot into bootloader
---------- Post added at 02:24 AM ---------- Previous post was at 02:22 AM ----------
I was typing as u were posting
Click to expand...
Click to collapse
Nice! Thank you!! I was following the TS Guide and couldn't figure why I couldn't find that rom.zip file... Now I get it.
A bit busy for a while, but will try again as soon as I get home and report back.
Cheers.

777ace said:
Nice! Thank you!! I was following the TS Guide and couldn't figure why I couldn't find that rom.zip file... Now I get it.
A bit busy for a while, but will try again as soon as I get home and report back.
Cheers.
Click to expand...
Click to collapse
If u get stuck just google search "how to extract rom.zip from ruu xda" im sure ul get a few guides.

Well, as it happened, impatience got the better of me and I did find the rom.zip and placed onto SD. Update worked fine, but now stuck at Telstra splash screen.
I really do have to head out, but I'll check back again later on.
Would having the SD card partitioned to SD-Ext/FAT32 effect the operation??
Thanks again for the help, feeling like a real n00b here!

Partition won't affect it. RUU doesn't see or care about it
Have you flashed stock hboot yet? It should say alpharev stock in the top of the bootloader screen.
If that RUU won't work, find the 2.3.3 WWE GB RUU

I have --- AlphaRev --- at top of screen. Definitely have flashed stock HBoot.
Just flashing WWE RUU now. I notice in the tutes I've found I should be seeing
Parsing...[SD ZIP]
[1]Bootloader - OK
[2]Radio_V2 - OK
[3] Radio_Cust - OK
etc...
I have the "OK" on all points except the [1] Bootloader, which has "Bypassed" after it...
WWE RUU now flashed, rebooted and still stuck at splash. Trying to recall if I had flashed a custom Kernel to this phone, back when I was using/playing with it. Blah, too many variables! Should have returned to stock two years ago!!
Still stuck at splash...and speaking of splash, phone might need to take a dip my swimming pool, I think.........................

777ace said:
I have --- AlphaRev --- at top of screen. Definitely have flashed stock HBoot.
Just flashing WWE RUU now. I notice in the tutes I've found I should be seeing
Parsing...[SD ZIP]
[1]Bootloader - OK
[2]Radio_V2 - OK
[3] Radio_Cust - OK
etc...
I have the "OK" on all points except the [1] Bootloader, which has "Bypassed" after it...
WWE RUU now flashed, rebooted and still stuck at splash. Trying to recall if I had flashed a custom Kernel to this phone, back when I was using/playing with it. Blah, too many variables! Should have returned to stock two years ago!!
Still stuck at splash...and speaking of splash, phone might need to take a dip my swimming pool, I think.........................
Click to expand...
Click to collapse
Not sure why it's skipping the bootloader part.
Custom kernel doesn't make a difference either. Everything except your sd card gets wiped when you run an RUU.
I had a read of the troubleshooting guide again, Part 8, it said to flash the downgrader, then RUU, sorry for my bad advice. Try that.
Else try runnnig the 2.3.3 RUU using PB99IMG.zip method in the same guide.
You should eventually be able to get it to boot. You don't have the RadioV2 fail which is a good thing

eddiehk6 said:
Not sure why it's skipping the bootloader part.
Custom kernel doesn't make a difference either. Everything except your sd card gets wiped when you run an RUU.
I had a read of the troubleshooting guide again, Part 8, it said to flash the downgrader, then RUU, sorry for my bad advice. Try that.
Else try runnnig the 2.3.3 RUU using PB99IMG.zip method in the same guide.
You should eventually be able to get it to boot. You don't have the RadioV2 fail which is a good thing
Click to expand...
Click to collapse
Well, I am now S-On, so progress is occurring... Also back to 0.75 HBoot.
Still booting straight to Fastboot though. For sh.ts and giggles, I just attempted to enter Recovery, but got the dreaded red triangle. All good, phone does still boot, just not in the way I want...
Anyhoo, still ticking away. Am relearning a heap of stuff. Maybe I could re-root and S-Off again, once I get this sorted??

777ace said:
Well, I am now S-On, so progress is occurring... Also back to 0.75 HBoot.
Still booting straight to Fastboot though. For sh.ts and giggles, I just attempted to enter Recovery, but got the dreaded red triangle. All good, phone does still boot, just not in the way I want...
Anyhoo, still ticking away. Am relearning a heap of stuff. Maybe I could re-root and S-Off again, once I get this sorted??
Click to expand...
Click to collapse
You can't enter recovery because the custom recovery gets overwritten by RUU as well. Like I said, everything should go back to stock.
Try the 2.3.3. GB RUU (I assume you used the Telus one as you only have 0.75 hboot?), get it booting first before trying anything else.
The latest RUU should have 1.02 hboot, at which point you could s-off with revolutionary as it's only compatible with 0.93 or 1.02 hboot as far as I know..

My suggestion of trying to enter recovery, or re-rooting was just me playing silly buggers. I swear once this thing is sorted, I am never touching it again!!
So I just tried to re-flash the Telstra RUU and got message "Main Version is older! Update Fail!". Probably due to the 0.75 HBoot, I am guessing. Would like to find a copy of Telstra FroYo RUU and see if that works. If it does get things moving, I could then OTA update once full-boot has been achieved.
Still pretty sure I missed a step somewhere... I did full wipe before starting (cache/dalvic, system, data, SD-Ext), but not factory reset. As I said, am now back to S-On, but I assume I am still rooted, so starting to think I should go back, gain S-Off, CWM and start all over again.
You people must be about ready to reach thru your monitor and choke me! Lol!!

777ace said:
My suggestion of trying to enter recovery, or re-rooting was just me playing silly buggers. I swear once this thing is sorted, I am never touching it again!!
So I just tried to re-flash the Telstra RUU and got message "Main Version is older! Update Fail!". Probably due to the 0.75 HBoot, I am guessing. Would like to find a copy of Telstra FroYo RUU and see if that works. If it does get things moving, I could then OTA update once full-boot has been achieved.
Still pretty sure I missed a step somewhere... I did full wipe before starting (cache/dalvic, system, data, SD-Ext), but not factory reset. As I said, am now back to S-On, but I assume I am still rooted, so starting to think I should go back, gain S-Off, CWM and start all over again.
You people must be about ready to reach thru your monitor and choke me! Lol!!
Click to expand...
Click to collapse
- Please use the 2.3.3 WWE RUU...
- Ignore anything and everything to do with Telstra...
- You are not rooted. You have run an RUU but it's not booting. This has overwritten everything, so your factory reset was unnecessary...

eddiehk6 said:
- Please use the 2.3.3 WWE RUU...
- Ignore anything and everything to do with Telstra...
- You are not rooted. You have run an RUU but it's not booting. This has overwritten everything, so your factory reset was unnecessary...
Click to expand...
Click to collapse
Yep, that's what I'm experiencing.
I have flashed RUU_Bravo_HTC_WWE_1.15.405.4_Radio_32.30.00.28U_4.05.00.11_release_122704 from here previously, but still had the boot issues when I ran it.
Gave it another try just now, but now have message "Model ID incorrect! Update Fail!"

- That is not the 2.3.3 GB RUU, I think it's an ancient Eclair RUU, yes android 2.1....
- If you can't find the 2.3.3 GB RUU, at least try the Froyo RUU from that thread, version 2.29.405.5 I think. This should give you hboot 0.93 which revolutionary also works on.

http://www.htcdev.com/process/legal_download/152
Or do it the PB99IMG method
http://d-h.st/d44

KA-CHING!!
I swear, if I could hit the THANKS button a million times, I would do so in a heart beat. Using mcclue's PB99IMG link, phone is now up and running like new!
But the thanks must also go eddiehk, for your patience and taking the time to check back each day to see how I am going. I swear I had no idea that RUU was Eclair/2.1... Just ASSUMED the updates were still relevant. Was getting close to just "Meh!" and tossing it in the trash.
So, going forward from here, is it worth me checking for OTA updates to bring the phone back completely to stock (Telstra) specs...or just leave it alone??
Anyway, again a million thanks to you guys for your help. Very much appreciated!! :good::good::good::good:

777ace said:
KA-CHING!!
I swear, if I could hit the THANKS button a million times, I would do so in a heart beat. Using mcclue's PB99IMG link, phone is now up and running like new!
But the thanks must also go eddiehk, for your patience and taking the time to check back each day to see how I am going. I swear I had no idea that RUU was Eclair/2.1... Just ASSUMED the updates were still relevant. Was getting close to just "Meh!" and tossing it in the trash.
So, going forward from here, is it worth me checking for OTA updates to bring the phone back completely to stock (Telstra) specs...or just leave it alone??
Anyway, again a million thanks to you guys for your help. Very much appreciated!! :good::good::good::good:
Click to expand...
Click to collapse
The 2.3 gb upgrade is the latest for this phone so just leave it as is. And if u want custom roms again, use revolutionary to s-off.