I had Odin 1.0 and i have flashed gingerbread 2.3.3 without any problem. But in forums so many peole talking about bootloader. I really dont understand what is the disadventages installing or updating bootloaders?
And if i want to go back froyo rom do i get problems due updating bootloader.
I have also a problem more, i dont find "format internal sd" section in new 3e recovery screen. Is it because of new bootloader?
Thanks for your answers..
Hi try
http://forum.xda-developers.com/showthread.php?t=1011701
Quite a bit of info here on the bootloader issues
rhitey said:
Hi try
http://forum.xda-developers.com/showthread.php?t=1011701
Quite a bit of info here on the bootloader issues
Click to expand...
Click to collapse
Thank you. I got my answers
How could we downgrade the bootloader to 2.2.1 version? Do we need to flash the 2.2.1 stock rom?
Related
Hey guys
I'm preparing my N1 for 2.3.3 and since I had it repaired I'm now stuck with some weird Vodafone(?)-FW.
2.2.1
2.6.32.9-g6624e39htc-kernel [ät] and18-2
5.12.00.08
HBOOT 35.0017
Anyways, I tried to flash it back to stock 2.2.1 but when I apply the PASSIMG.zip it says "Main version is older. Update failed!"
Is there a workaround?
I read something about downgrading HBOOT to a lower version?
Thanks!
If FRG33 isn't flashing by PASSIMG method - then you can't use it. If you exercise your abilities to search the forum, you'll find a thread where people were trying to circumvent that - updating from Eclair to Froyo (just like now) - and those attempts failed.
If you have SLCD phone - and if recently repaired, you definitely have it - downgrading HBOOT will leave you with a nice brick.
Root your phone, install custom recovery, flash whatever you want from there.
I'll try that. Thank you very much.
Now running on Cyanogen.
Thanks again!
You're welcome
All,
I unlocked the bootloader (I see the unlocked padlock at the bottom of the screen at boot) some time ago on my N1. Now that the official 2.3.3 update is out, I thought I would give it a try.
I keep getting 'signature verification failures' when I tried to install either the official or other versions of 2.3.3
So, I learned it was likely because my HBOOT needed to updated. I downloaded an tried to install the new version (0.35.0017?) and it sorta acts like it is going to update it, reboots a couple of times, but doesn't seem to work.
Could someone please give me some guidance on exactly what I need to do from here to get the 2.3.3. update applied?
Thanks in advance,
-Rob
You most probably have custom recovery, and your problem isn't bootloader at all.
Flash the stock version packaged for custom recovery, found in Development section.
So,
My HTC Incredible S is rooted, and the bootloader is unlocked (what the point of unlocking the bootloader is I still don't know as I can't install custom ROMS... but back to the point at hand...), and the OTA update to 2.3.5 arrived 2 weeks ago.
Needless to say, the update would not install. Despite researching the issue, I'm still confused as to what exactly is preventing the update from working. Is the the fact that my device is rooted? Or is it the unlocked bootloader? I tried relocking the bootloader and that had no effect, so I'm assuming rooted devices for some reason are rejected by the update.
So considering I can't install custom ROMs (I'm HBOOT 1.16 and the downgrade guide didn't work for me, so no s-off), and I now can't upgrade officially, I'm feeling a little stuck.
Is there a way to force an official update to install on a phone in my 'condition'?
Note: My recovery is custom - Revolutionary CWM - and I can't find (and therefore cannot flash) an original recovery image... would this affect the updating process?
Thanks guys/gals,
G
Root won't stop an ota but an unlocked bootloader will. You can check in your boot screen if its still unlocked or if its relocked.
nope_okay said:
So,
My HTC Incredible S is rooted, and the bootloader is unlocked (what the point of unlocking the bootloader is I still don't know as I can't install custom ROMS... but back to the point at hand...), and the OTA update to 2.3.5 arrived 2 weeks ago.
Needless to say, the update would not install. Despite researching the issue, I'm still confused as to what exactly is preventing the update from working. Is the the fact that my device is rooted? Or is it the unlocked bootloader? I tried relocking the bootloader and that had no effect, so I'm assuming rooted devices for some reason are rejected by the update.
So considering I can't install custom ROMs (I'm HBOOT 1.16 and the downgrade guide didn't work for me, so no s-off), and I now can't upgrade officially, I'm feeling a little stuck.
Is there a way to force an official update to install on a phone in my 'condition'?
Note: My recovery is custom - Revolutionary CWM - and I can't find (and therefore cannot flash) an original recovery image... would this affect the updating process?
Thanks guys/gals,
G
Click to expand...
Click to collapse
You need to replace CWM with the standard HTC recovery (you simply need to extract the recovery.img file from a RUU/ROM.zip file) and then relock the bootloader before the OTA will install correctly.
At hboot 1.16 and rooted all you should have to do is install Cwm and than you can flash custom ROM's..... Not sure what your problem is.
Sent from my anus using xda crap
@itsbeertimenow - yeah, unlocking the bootloader never did anything for me in terms of being able to flash custom ROMs... I guess 's-off' is required
@tpbklake, nonverbose
Yeah, I had a feeling the custom recovery had something to do with it. As I mentioned before, even relocking the bootloader had no effect.
Does the recovery have to be a specific version? I'm running Android 2.3.3, so will any 2.3.3 recovery work or does it have to be a recovery for an HTC Incredible S running Android 2.3.3 - that's a little harder to find. Any suggestions for an ruu/zip file to extract a recovery img from?
Thanks again for the helpful responses.
G
nope_okay said:
@itsbeertimenow - yeah, unlocking the bootloader never did anything for me in terms of being able to flash custom ROMs... I guess 's-off' is required
@tpbklake, nonverbose
Yeah, I had a feeling the custom recovery had something to do with it. As I mentioned before, even relocking the bootloader had no effect.
Does the recovery have to be a specific version? I'm running Android 2.3.3, so will any 2.3.3 recovery work or does it have to be a recovery for an HTC Incredible S running Android 2.3.3 - that's a little harder to find. Any suggestions for an ruu/zip file to extract a recovery img from?
Thanks again for the helpful responses.
G
Click to expand...
Click to collapse
Instead of trying to install the OTA update for Sense 3/2.3.5 why don't you flash the stock, rooted version of 2.3.5/Sense 3 ROM that I posted in the Dev section. With the unlocked bootloader and CWM you can flash this ROM and then manually flash the boot.img in that ROM's zip file and you should be good to go.
@tpbklake
I think I'd already tried that and the update process aborted pretty early on. I'll give it another go and check out troubleshooting threads related to the process. thanks again.
G
Update: I'm following the instructions as per this thread: http://forum.xda-developers.com/showthread.php?t=1337105
Update 2: It worked and I managed to install CM7... happy day Thanks guys
nope_okay said:
@tpbklake
I think I'd already tried that and the update process aborted pretty early on. I'll give it another go and check out troubleshooting threads related to the process. thanks again.
G
Update: I'm following the instructions as per this thread: http://forum.xda-developers.com/showthread.php?t=1337105
Update 2: It worked and I managed to install CM7... happy day Thanks guys
Click to expand...
Click to collapse
Here is the 2.3.5/Sense 3.0 stock, rooted ROM built directly from the OTA you were trying to install. You would flash it in CWM just like you did for CM7.
http://forum.xda-developers.com/showthread.php?t=1430535
Thanks for the link, will come in handy when I want to go back to a 'stock' setup... wasn't very impressed with CM7 so I then tried the Virtuous Affinity ROM (2.3.5/S3.5) - fantastic. Thanks again for your help!
G
[UPDATED]
Bootloaders...
1. i9000 was launched with Éclair so the bootloader was of course an Éclair bootloader?
My answer: Yes (Or a Froyo one... before Froyo came out).
2. People who upgraded to Gingerbread from Éclair without upgrading via Kies had to flash a Gingerbread bootloader via Odin?
My answer: Yes, unless flashing different rom complete with a bootloader.
3. Flashing ANY rom wont change the bootloader? Like CyanogenMod.
My answer: No, some rom's do come complete with a bootloader like stock or stock based ones. But CyanogenMod does not.
4. I'm running CM9... does that mean I have an Ice Cream Sandwich bootloader now?
My answer: No, the Gingerbread bootloader is more than capable.
Are my own answers correct?
I'm so confused by different things I've read off the net... please please someone put my mind to rest! I'm writing a few BIG guides and kinda came unstuck when I got to this subject lol.
mod2max said:
Bootloaders...
1. i9000 was launched with Éclair so the bootloader was of course an Éclair bootloader?
2. People who upgraded to Gingerbread from Éclair without upgrading via Kies had to flash a Gingerbread bootloader via Odin?
3. Flashing ANY rom wont change the bootloader? Like CyanogenMod.
4. I'm running CM9... does that mean I have an Ice Cream Sandwich bootloader now?
I'm so confused by different things I've read off the net... please please someone put my mind to rest! I'm writing a few BIG guides and kinda came unstuck when I got to this subject lol.
Click to expand...
Click to collapse
No cyanogenmod packages come with bootloaders. I don't think that cwm will flash them. I think you need Odin or Heimdall to flash bootloaders. Unless you flashed a package that had bootloaders, you should still be on gb bootloaders, which work for just about everything.
Sent from my SGH-I777 using xda premium
1. Idk that was along time ago lol
2. If you update with Odin factory images, it always contains the boot loader.
3/4. Flashing custom ROMs use the gingerbread bootloader, and do not change it ever.
Sent from my GT-I9000 using xda premium
Hello everybody,
I was quite happy with my Incredible S until I updated it via OTA to ICS 4.0.4 + Sense 3.6...
Before that, I had been using it with Gingerbread 2.3.3 (or 2.3.5 ?!?) and Sense 2.1 and it was pretty good! I mean.. it did its job without significant problems..
Last week I decided to do ALL the updates in a rush and now it's laggy and slow...What drives me crazy is when I type some text (text messages, whatsapp, browser web, etc.): the touchInput seems not to be as responsive as it was once.. and it is frustrating!
I read a lot about this topic and I discovered that it's a common problem.
I tried to install other keyboards, other messaging apps, I made a factory reset, but nothing helped!
Now I'd really like to downgrade it to Gingerbread + a lighter Sense because I think that Sense 3.6 is too much heavy for this stupid phone.
Since I was (indeed I currently am) a complete noob about mobile systems I need help from you!
My idea is to install a stock rom and not a custom rom because every custom rom have some drawbacks or flaws.. while the stock Gingerbread 2.3.3 was flawless (I swear!).
I read that it's not possible to install an older version of Android via RUU.. is it right?
Is it possible to do something without rooting / s-offing the phone? (I'm not sure about s-off = having root priviledges...)
I read all the threads but I didn't find a clear answer to my problem.. please help!
Thank you guys!
p.s. I'm quite sure that android gb 2.3.3 came with sense 2.1 while gb 2.3.5 came with sense 3.0
Sadly you can't downgrade with an RUU - that would be sweet. Since you are on ICS, i'd assume your hboot version is 2.00+. I'm not sure if you can downgrade that, but take a look around. Essentially, you'd want to install CWM recovery, and install this GB 2.3.5 rom with sense 3. Note, there are no radios, you will have to flash those as well. Unfortunately, this is the only way to downgrade. Also, you will need S-off.
seba_t said:
Hello everybody,
I was quite happy with my Incredible S until I updated it via OTA to ICS 4.0.4 + Sense 3.6...
Before that, I had been using it with Gingerbread 2.3.3 (or 2.3.5 ?!?) and Sense 2.1 and it was pretty good! I mean.. it did its job without significant problems..
Last week I decided to do ALL the updates in a rush and now it's laggy and slow...What drives me crazy is when I type some text (text messages, whatsapp, browser web, etc.): the touchInput seems not to be as responsive as it was once.. and it is frustrating!
I read a lot about this topic and I discovered that it's a common problem.
I tried to install other keyboards, other messaging apps, I made a factory reset, but nothing helped!
Now I'd really like to downgrade it to Gingerbread + a lighter Sense because I think that Sense 3.6 is too much heavy for this stupid phone.
Since I was (indeed I currently am) a complete noob about mobile systems I need help from you!
My idea is to install a stock rom and not a custom rom because every custom rom have some drawbacks or flaws.. while the stock Gingerbread 2.3.3 was flawless (I swear!).
I read that it's not possible to install an older version of Android via RUU.. is it right?
Is it possible to do something without rooting / s-offing the phone? (I'm not sure about s-off = having root priviledges...)
I read all the threads but I didn't find a clear answer to my problem.. please help!
Thank you guys!
p.s. I'm quite sure that android gb 2.3.3 came with sense 2.1 while gb 2.3.5 came with sense 3.0
Click to expand...
Click to collapse
You will have to unlock the bootloader using the procedure at HTCDEV.com. After that, you can use an unsecured boot.img to boot your phone and then modify the phone's version-main so that you can then flash the older GB 2.3.3/Sense 2.1 RUU.
tpbklake said:
You will have to unlock the bootloader using the procedure at HTCDEV.com. After that, you can use an unsecured boot.img to boot your phone and then modify the phone's version-main so that you can then flash the older GB 2.3.3/Sense 2.1 RUU.
Click to expand...
Click to collapse
Its as simple as that? unlock through htcdev and flash on older RUU? That would also work with a phone unlocked with an xtc clip right?
m82a1 said:
Its as simple as that? unlock through htcdev and flash on older RUU? That would also work with a phone unlocked with an xtc clip right?
Click to expand...
Click to collapse
No, you misread the post.
1. Unlock the bootloader using HTCDEV.com
2. Boot your phone using an unsecured boot.img
3. Modify the version-main value.
4. Flash a RUU.
If you have a IncS that has S-OFF via XTC Clip, then you can simply modify the version-main value and then flash a RUU.
tpbklake said:
No, you misread the post.
1. Unlock the bootloader using HTCDEV.com
2. Boot your phone using an unsecured boot.img
3. Modify the version-main value.
4. Flash a RUU.
If you have a IncS that has S-OFF via XTC Clip, then you can simply modify the version-main value and then flash a RUU.
Click to expand...
Click to collapse
Gotcha, good to know, thanks!
well.. thank you for showing interest in my thread.
I understand that is not possible to downgrade without at least unlocking the bootloader..
so.. flashing a RUU is the same as flashing a custom rom?
After unlocking the bootloader I have to:
- flash a custom recovery
- flash a RUU/custom rom?
mmm.. is it really possible to install an older version of android while keeping the hboot at version 2.02 (like mine)?
I don't understand what is an "unsecured boot.img" and what "Modify the version-main value" means..
thank you again
seba_t said:
well.. thank you for showing interest in my thread.
I understand that is not possible to downgrade without at least unlocking the bootloader..
so.. flashing a RUU is the same as flashing a custom rom?
After unlocking the bootloader I have to:
- flash a custom recovery
- flash a RUU/custom rom?
mmm.. is it really possible to install an older version of android while keeping the hboot at version 2.02 (like mine)?
I don't understand what is an "unsecured boot.img" and what "Modify the version-main value" means..
thank you again
Click to expand...
Click to collapse
Look at the Downgrade script sticky post and then download the Downgrade Kit zip file and take a look at it.
The script file has all of the functions you need. One the script is done, you should be able to run the RUU.
U have to relock the bootloader then run the ruu file (the one u choose) while the phone is in fastboot mode
Sent from my HTC Incredible S using xda app-developers app
Is it possible to flash Android 2.3.3 Rom on 2+ hboot?
Sent from my Incredible S using xda app-developers app
Silversniper said:
Is it possible to flash Android 2.3.3 Rom on 2+ hboot?
Sent from my Incredible S using xda app-developers app
Click to expand...
Click to collapse
Yes it is. You can use the downgrade script to reset your version-main so that you can flash the 2.3.3 RUU.
tpbklake said:
Look at the Downgrade script sticky post and then download the Downgrade Kit zip file and take a look at it.
The script file has all of the functions you need. One the script is done, you should be able to run the RUU.
Click to expand...
Click to collapse
Are you talking about this thread:
http://forum.xda-developers.com/showthread.php?t=1373697
or this:
http://forum.xda-developers.com/showthread.php?t=1337105
or more probably this one:
http://forum.xda-developers.com/showthread.php?t=1761319
If you point me to the thread where I can find the Nonverbose's Downgrade script and the Downgrade kit I will be grateful...
Thank you!
seba_t said:
Are you talking about this thread:
http://forum.xda-developers.com/showthread.php?t=1373697
or this:
http://forum.xda-developers.com/showthread.php?t=1337105
or more probably this one:
http://forum.xda-developers.com/showthread.php?t=1761319
If you point me to the thread where I can find the Nonverbose's Downgrade script and the Downgrade kit I will be grateful...
Thank you!
Click to expand...
Click to collapse
The first thread you posted is the one you want.
tpbklake said:
The first thread you posted is the one you want.
Click to expand...
Click to collapse
Thank you tpblake! I'll try to follow that guide asap