i was wondering if there are any difference between the stock spl and the one included in the korean froyo rom. is there a way to see what is changed ?
+1
I would like to know as well.
The one included in KR_KT ROM is also included in official 2.2.1, so there is no "stock" and "non-stock" anymore. They're both stock.
One difference I know of is that the newer bootloader enlarges or otherwise takes care of BOOT partition where boot.img is stored, and allows people with bad sector in that partition flashing larger boot.img than the older one.
Related
Alright, HBoot is the bootloader - sort of like BIOS, it tells the phone what to do when I push the power button.
But what about upgrading to HBoot .35? It's recommended/required for Gingerbread, and I'm fine with performing the upgrade, I just have a few questions as to what would happen after the upgrade and reverting back.
Would the upgrade unlock my bootloader (if it were still locked)?
Would I still be able to use Nandroid to restore to a previous version of Android even if it had used a different HBoot?
Would Nandroid revert my HBoot back to .33? I know Nandroid backs up a folder called "Boot", and from what I had read that's the bootloader.
If it's not possible to revert HBoot via Nandroid, would my only other option be ADB?
And finally, is there anything else which simply cannot be stressed enough, that I should know?
Nandroid does not touch the HBOOT. HBOOT is the bootloader, boot.img is the boot image comprising the kernel and some configuration files required for the booting process.
Nevertheless, all Android versions should be able to run with higher versions of HBOOT. You might not be able to restore old Eclair builds because of the radio version, but HBOOT should not be a problem.
I imagine the OP refers about the upgrade because some gingerbread ROMS recommend having the latest HBOOT.
SPL:
[HBOOT-0.35.0017]
http://android.clients.google.com/pa...-0.35.0017.zip
Thanks you guys, you definitely helped clear up some confusion.
How do I flash it?
bryanchapman9999 said:
How do I flash it?
Click to expand...
Click to collapse
Via recovery - coun't be simpler
bryanchapman9999 said:
Via recovery - coun't be simpler
Click to expand...
Click to collapse
You just download the file and flash it from recovery (clockworkmod in my case)? I read in some threads you have to rename it and what not to a certain file name and go into the bootloader and it asks you if you want to upgrade?
I'm confused.
Just some additional info -- The NAND flash of our N1's has 5 partitions: misc, boot, cache, system, and userdata. The misc partition (mtd0) is the HBOOT. Nandroid does not back that up.
Sent from my Nexus One using XDA App
omer1112 said:
You just download the file and flash it from recovery (clockworkmod in my case)? I read in some threads you have to rename it and what not to a certain file name and go into the bootloader and it asks you if you want to upgrade?
I'm confused.
Click to expand...
Click to collapse
You don't have to rename it. You can flash it: 1) in recovery, 2) using flash_image via adb or a terminal, or 3) (I think) using fastboot.
Sent from my Nexus One using XDA App
G0belet said:
Nandroid does not touch the HBOOT. HBOOT is the bootloader, boot.img is the boot image comprising the kernel and some configuration files required for the booting process.
Nevertheless, all Android versions should be able to run with higher versions of HBOOT. You might not be able to restore old Eclair builds because of the radio version, but HBOOT should not be a problem.
Click to expand...
Click to collapse
While I believe you about higher HBOOT being ok for earlier versions I would feel safer having a copy of my current HBOOT as a flashable zip. Is it possible to revert simply by flashing a zip and does anyone know of a link to the older HBOOT?
ellesshoo said:
While I believe you about higher HBOOT being ok for earlier versions I would feel safer having a copy of my current HBOOT as a flashable zip. Is it possible to revert simply by flashing a zip and does anyone know of a link to the older HBOOT?
Click to expand...
Click to collapse
Just so I know what you are trying to accomplish: why would you ever want to downgrade? Most Nexus One's now should have the 0.35 HBOOT (some came with it out of the box, most got updated with the latest OTA package, and some upgraded manually). The version of HBOOT you have doesn't make any difference, aside from one: the newer HBOOT is larger than the older one. Basically it takes some space away from the recovery partition and adds it to the misc (HBOOT) partition. Some recoveries (like Amon_RA 2.0) are quite large and may not fit in the recovery partition if you are on the latest HBOOT, however, Amon_RA's latest recover is smaller, and fits no problem. Aside from that, there is no real differences between the two HBOOTs, and no reason to ever downgrade. And besides, word on the street is that 0.35 will be a prerequisite from installing OTA Gingerbread.
The new HBOOT isn't larger, it adds space to BOOT partition, not HBOOT. This allows to overcome a problem some Nexus Ones have - if a bad sector is present in BOOT partition, some kernels would fail to flash on the older HBOOT - not having enough space to write boot.img. New HBOOT solves it by making the recovery smaller and adding the space to BOOT partition instead.
cmarti said:
I imagine the OP refers about the upgrade because some gingerbread ROMS recommend having the latest HBOOT.
SPL:
[HBOOT-0.35.0017]
http://android.clients.google.com/pa...-0.35.0017.zip
Click to expand...
Click to collapse
The link to that HBOOT ZIP is broken...anyone have an updated link ?
marcelol said:
The link to that HBOOT ZIP is broken...anyone have an updated link ?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=9389909&postcount=109
I just wanted to add my voice to the throngs of people saying "This saved me!!" Because it just did. So, thanks!
Today I noticed I was on hboot 33.0012. Do any of the newer radios or ROMs need or work better with hboot 35.0017?
I did a search but couldn't find anything posting a reason to upgrade so I'm not sure.
Per galaxys,
"You should be using the latest & greatest hboot 35 and radio 5.08 which was how Gingerbread was OTA'd from Google Development!"
Yes, new hboot and radio versions are required for Gingerbread roms.
I assume you're running a custom rom since you haven't gotten the OTA updates?
All of this should have been pushed to your phone a long time ago.
What the new hboot does is basically change the partition sizes, allowing for a slightly bigger kernel. CM uses LZMA compressed kernels through so it's not needed for CM. The radios also don't require it but I've had no issues with it and there may very well be some other fixes in it that are less obvious.
You want the newer radios though for Gingerbread. Either 5.08.00.04 or 5.12.00.08.
Hi everybody.
I'm currently about to switch to a SGS2.
Because of this I would like to flash my N1 back to stock.
The device is an AMOLED version and currently equipped with an AmonRA recovery and as a HBOOT 0.35.0017. The bootloader is still locked!
Flashing back a stock ROM seems to be fairly easy. I found this thread at Modaco http://android.modaco.com/content/google-nexus-one-nexusone-modaco-com/300414/21-oct-stock-roms-erd79-frg83-images-zip-online-kitchen-optional-root-insecure/ and also a a GRI40 image here: http://forum.xda-developers.com/showthread.php?t=968396
But what about the recovery?
All the latest images seem not to contain a complete recovery. There are just delta patches included. The only image I have found that seems to have a complete recovery is EPE54B, which is rather old.
I try to find a more recent one without success.
Where do I find a recovery.img that has the version that the GRI40 image is expecting (and patching by its delta patch)?
Or if this is not available...
Whats is the best way to flash back to complete stock (including recovery for OTA)?
I.e. is it possible to flash EPE54B on my to device directly or do I run into problems because of the newer HBOOT I already have?
Thanks in advanced
Follow the unroot/restore guide in the wiki...
Hi.
Thanks for your reply. I was not even aware that this wiki does exist (and contains that much helpful info).
The PASSIMG method normally (hopefully) could work... even if my bootloader is still locked (no fastboot)
I will try this.
best regards
I'm a brand new Canadian Incredible S owner looking to root and flash new roms. I've been reading a lot of forum posts and have some questions about flashing roms and radios. I'm coming from the Desire (Bravo) and on that phone, I've always flashed roms and radios via CWM recovery. However, it seems that for the IncS, many users have instead flashed them through HBOOT.
Here's what I want to do:
- Apply S-OFF via Alpharevx, install CWM, and root
- Take the 2.30.405.1 stock GB ruu, extract the rom.zip, remove the HBOOT and recovery files, and root it via dsixda's kitchen
- Flash the rooted GB rom and radio via CWM
So...can it be done this way through CWM? Or does the flashing of both the rom and radio have to go through HBOOT?
I apologize if this topic has been mentioned before, but it seems as if things aren't quite as simple as my old Desire was and I want to make sure that what I'm planning to do won't ruin the phone.
I'm not sure about this, but I think you can flash .zip ( Rom, radio, recovery etc) either through hboot or recovery, only difference being that for hboot the zip has to have the specific name ( PG32IMG.zip or sometimes like that). Could somebody confirm if this is correct ?
bracketologist said:
I'm a brand new Canadian Incredible S owner looking to root and flash new roms. I've been reading a lot of forum posts and have some questions about flashing roms and radios. I'm coming from the Desire (Bravo) and on that phone, I've always flashed roms and radios via CWM recovery. However, it seems that for the IncS, many users have instead flashed them through HBOOT.
Here's what I want to do:
- Apply S-OFF via Alpharevx, install CWM, and root
- Take the 2.30.405.1 stock GB ruu, extract the rom.zip, remove the HBOOT and recovery files, and root it via dsixda's kitchen
- Flash the rooted GB rom and radio via CWM
So...can it be done this way through CWM? Or does the flashing of both the rom and radio have to go through HBOOT?
I apologize if this topic has been mentioned before, but it seems as if things aren't quite as simple as my old Desire was and I want to make sure that what I'm planning to do won't ruin the phone.
Click to expand...
Click to collapse
The latest version of dsixda's HTC kitchen now supports adding a radio.img to the rom.zip file that gets generated, so you can just flash your custom rom using CWM and not have to flash the GB radio separately.
Thanks for the info. If I do this through CWM, do I still have to worry about changing the Model ID since I have the Canadian model? Or is that something that only comes up if I flash through HBOOT?
And I'm guessing that I only have to worry about having the ENG HBOOT if I flash the radio through HBOOT. This also shouldn't be an issue if I do it through CWM as well. Is this right?
bracketologist said:
Thanks for the info. If I do this through CWM, do I still have to worry about changing the Model ID since I have the Canadian model? Or is that something that only comes up if I flash through HBOOT?
And I'm guessing that I only have to worry about having the ENG HBOOT if I flash the radio through HBOOT. This also shouldn't be an issue if I do it through CWM as well. Is this right?
Click to expand...
Click to collapse
No you don't have to worry about changing the Model ID when you flash a custom ROM using CWM. It only comes into play when flashing a PG32IMG.zip using HBOOT.
In fact I have already done the process you are going to undertake. I have a Canadian IncS and I took the latest 2.30.405.1 WWE ROM.zip and cooked it using dsixda's kitchen and my Phone Info now shows Model Number HTC IncS S710e, not S710a as it did before.
[DISCLAIMER]
I HAVE searched already, and the only result I get is a .12 radio that is NOT signed properly. I don't want this version.
[/DISCLAIMER]
Anyways, I was wondering if anyone could point me into the direction as to where to get an OFFICIAL signed radio, particularly the .12 Korean version. All links I can find to are not properly signed. I was planning to set up BLACKROSE and it requires the .12 radio to be flashed without disabling signature verification. Thanks much.
http://forum.xda-developers.com/wiki/Nexus_One/Radios
Androidity3000 said:
I was planning to set up BLACKROSE and it requires the .12 radio to be flashed without disabling signature verification.
Click to expand...
Click to collapse
Blackrose does not require the 5.12 radio. The only requirements (found in the first post of the development thread) are:
Code:
Windows PC or Linux PC
USB Debugging(ADB) ON
Connect USB before install
HBOOT 0.35.0017
The 5.08 radio (which most N1s are running) tends to be the best radio for people outside of Korea. In fact, it is the one that google released with the Gingerbread OTA update, and I am sure they did a lot of internal testing to determine which radio is the best.
Signed for "fastboot flash" on locked bootloader? Or signed ZIP to flash through recovery?
If you mean bootloader: 5.12 was only released for Korean version, which is different from Google main line (SW-wise only, since it's the same phone). Thus, if it's not accepted by your current bootloader - you won't get it Google-signed anywhere, and you won't be able to flash it through fastboot with locked bootloader, if that's what you're looking for. Last version in Google updates is 5.08.
On the other hand, if you mean signed ZIP for flashing in custom recovery - then it's funny, because ANYONE can sign those ZIPs. Anyone. I can sign it for you with a testkey (that's all that recovery needs). Would that make it more "official"?
In any case, as mentioned before, you don't need it. You need 5.08 and above.
Thanks for the link. I will just use the 5.08 version then. I thought I read that .12 was needed; however, I guess I am mistaken. Glad to know. And yes, I was planning to flash through recovery. Again, thanks much!
In that case, you can flash 5.12 as well. Being signed doesn't make the update.zip official, since all the files for flashing in custom recovery are signed by people, just like myself. 5.12 radio is just as legitimate as 5.08, and both update.zip weren't signed by Google anyway. You do need to verify the md5sum before flashing, though.