Upgrading bootloader from 1.02 to 2.02/2.05
 

Hey guys, I'm sorry if this has been discussed before, but I couldn't find anything on upgrading the bootloader like this. I found all kinds of info on downgrading, but very little on upgrading.

Anyway, I have a Quest PPC6700 I bought on EBay for $15 as a test phone. I have XV6700 I use as my primary phone, so I figured I'd get another to play with until I felt comfortable enough to flash my daily phone.

My problem is, after reading a lot on this forum, it seems there are a lot of differences between bootloader versions. The XV6700 I use daily has a 2.05 bootloader, and this PPC6700 has a 1.02 bootloader. I would like to have both phones the same so I know what to expect and would not have to worry so much about different bootloaders causing different problems.

I downloaded the newest Verizon ROM (AKU3.3) from their website, but could not get it to flash to this phone. I would get an Error 100 - Model ID Error, or a Country error (can't remember exactly what that one said). I finally did get it to flash using the APACUpgradeUt_noID.exe utility. Now both phones are running a 3.14.30 WWE ROM, but the bootloaders are still different.

Before I found the PPC6700, I bought another XV6700 on EBay for my wife to play bubble breaker (this one cost $10). The guy said he tried to upgrade it and screwed it up so he was selling it as-is. Armed with the info I learned here, I was able to use BuildOS to flash that phone to WM6.1 (I did have to set it to NO_ID). This phone also had a 2.05 bootloader, I had to downgrade to 2.02 before I could get it to flash. Works great now, but now it's my wifes and I can't play with it anymore.

So, any way to make this PPC6700 upgrade to a 2.02 or 2.05 bootloader?? Or is this something I shouldn't stress over and just go have fun knowing the XV6700 will be fine???

Thanks in advance for any and all help and/or suggestions!

-Eddie

Re: Upgrading bootloader from 1.02 to 2.02/2.05
 

I believe there is no difference between bootloader versions, except that the newer ones take up more space... I wouldnt stress about it.

Re: Upgrading bootloader from 1.02 to 2.02/2.05
 

False. Different bootloader versions use different RUUs. And to answer the OP's question, don't upgrade, waste of time and can cause problems. v1.02 is one of the best. The way to upgrade it flash a stock AKU3.3 ROM with upgrade. I reccomend leaving it alone...

Re: Upgrading bootloader from 1.02 to 2.02/2.05
 

Thanks man, I appricate the help. Thanks for the ROM I am running in the otherXV6700 also (PDAJ Apache WM6.1 v2.02) - it works great!

My only concern was making a stable ROM that I liked, testing it onthe PPC6700, then finding it would not work on my daily XV6700. I gave the PPC6700 to my wife and will use the other XV6700 I have for testing - just to be sure :)

Thanks again for all the help - in this thread, and all over this forum. I have been reading for about 2 - 3 weeks now, and feel I have learned alot. I have at least learned enough to fix 2 phones!

Re: Upgrading bootloader from 1.02 to 2.02/2.05
 

Sorry about the misinformation, but the point ends up being the same, leave it alone. I'm sorry about the misinfo!

Re: Upgrading bootloader from 1.02 to 2.02/2.05
 

No problem. Yeah point is the same, unless there is a country ID error, leave the bootloader alone. And Eddie, glad you got the device running good.

Re: Upgrading bootloader from 1.02 to 2.02/2.05
 

I tried to flash my main XV6700 yesterday, but did get the country ID error. I reverted bootloader to version 2.02 like I did with the other one, but still get an error. If I set PPCKitchen to No_ID it works fine, so I'm not gonna worry about it :) I have a stable unit running WM6.1 with all the extras I wanted.

Thanks alot, I would not have been able to do it without you guys - and that goes to everyone that contributes to this forum.

Now I am about to make a contribution to the PPCKitchen development team!!!!

Re: Upgrading bootloader from 1.02 to 2.02/2.05
 

The whole reason for reverting to bootloader 2.02 is to use NoID RUU. It is nice, but whenever you have a pre-made ROM with regular RUU, you have to take out nk.nbf and put it in a NoID RUU. Anyways, glad you're back in business.