Root Boot Manager Pro issues

[ramjet73]

Before I rooted (like a week ago) I installed all updates. Prl, profile, firmware. All the HTC software was updated. So what would the stuff in Joe_Blow's thread do compared to Leslie Ann's thread?

The firmware, recovery and hboot in joe_blow's thread are as current as you can get and still run GB and AOSP based ROM's. The firmware is based on the official VM updates and not a really old hboot and firmware that came from different Sprint GB builds for the radio and PRI. Everything I've read says that the radio and PRI should be in sync since they are designed to work together. Here's one post that documents that and I've seen others.

If you've already updated everything to current levels there's no need to do anyone's "fix everything" thread.

Near as I can tell it would basically simplify the steps in her thread, but personally I still prefer her method.

Any particular reason why you prefer to flash a very old hboot, and a GB radio and PRI individually instead of flashing the most current stuff in one zip file?

From the OP of the original "fix everything" thread:

What we will change here are:
ENG Hboot 1.04 - allows other roms and needed for the radio flash. Engineering hboot, more recovery options, less restrictions.
PRI 2.17.651 - fixes some fluctuations, increases radio strength. This will show up as 1.53_145 in about phone.
Radio 0.97.10.0530 - fixes some fluctuations, increases radio strength. (Updated, much better!)
PRL 60690 - Updates the list of towers you can connect to (Optional but highly recommended).
Note: You can change to any Hboot once you are done with the radio, and PRI flashing.

Note that the PRI is from the Sprint GB 2.17.651.5 build and the radio is from the 1.13.651.7 Sprint GB build.

Just curious.

ramjet73

 

[remanifest]

Any particular reason why you prefer to flash a very old hboot, and a GB radio and PRI individually instead of flashing the most current stuff in one zip file?

I think it's because I'm a traditionalist really, no reason other than that. I substituted the latest updates when I ran through LeslieAnn's thread anyway, so I'm all current. I don't like the idea of yanking my battery at a specific point either. If I was to teach someone how to play with their phone, abruptly telling them to pull the battery out at a specific point in time seems awkward. What goes through the person's mind is, "What if I mess up? Will I break something?"

If I'm teaching my mother how to do this, will she have the confidence to do it correctly (reboot a few times), or will she lose confidence because she's not sure when the exact moment is to yank out her battery?

I suppose it's not much different from the wire trick as far as the timing thing goes, but at least in that case there's a crudely-worded program telling you when to do the wire trick.

ETA I also think it's important that users know *what* they are flashing, and why they're flashing those things in the specific order they're being flashed, and having an all-in-one removes that knowledge.

 

[ramjet73]

ETA I also think it's important that users know *what* they are flashing, and why they're flashing those things in the specific order they're being flashed, and having an all-in-one removes that knowledge.

Fair enough.

I'm assuming you are referring to the unknownforce "bricking" method when you mention pulling the battery and I've already said in the thread in which that was discussed that I prefer the wire trick, but if the htcdev unlock isn't available for some reason at least there is an alternative for users that can't do the wire trick, which is why that thread was started.

It's fine that you prefer to flash the items individually, but the current PRI isn't available as a separately flashable zip so when you "prefer her method" that doesn't really work without that file. Flashing the RUU, OTA (which includes radio and PRI), hboot and recovery separately does make sense, but that's not what you said. If it's confusing for me I suspect that it's even more confusing to users not familiar with the process.

Making things simpler for new users is a good thing but I agree that they should still understand what they are doing. I think joe_blow did a good job of summarizing the content and purpose of his zip files in the introduction on his OP and details the contents of each file in the download section, but if you don't think that's adequate for users to understand what they are flashing I'm sure he would be open to suggestions for making it more clear.

Detailed guides can sometimes get confusing and lead to more problems that they solve so it's good to be specific about how and when they apply. IMO, endorsing guides that are out of date just because they have been used successfully in the past is likely to cause more problems for new users than oversimplifying the process.

ramjet73

 

[remanifest]

I know this may not be received well, but here goes:

It is difficult to take a post (like the one in joe_blow's fix everything thread) seriously when there are numerous spelling and grammatical errors throughout. It destroys the credibility of the information, and makes it difficult to follow the intent of the writer's words. This is important, especially when referring new users to the post.

I don't want to get too much into that as it comes off as nitpicky and ungrateful for the work he's put in, but it is something that I notice -- and I'm sure I'm not the only one.

The only confusion that should come from a detailed thread is the result of not following explicit instructions step by step. I have yet to brick any phone in the history of owning an Android, or anyone else's for that matter. The reason is because the directions are followed as they are written. When users have problems with flashing new firmware, it's almost always a result of, "Oh, I didn't do that step. I didn't think it was that important!"

 

[ramjet73]

The only confusion that should come from a detailed thread is the result of not following explicit instructions step by step. I have yet to brick any phone in the history of owning an Android, or anyone else's for that matter. The reason is because the directions are followed as they are written. When users have problems with flashing new firmware, it's almost always a result of, "Oh, I didn't do that step. I didn't think it was that important!"

I'm not going to argue with you on that one since most of the questions I get about my rooting and S-OFF guide on XDA are from users that haven't read through the OP and and are trying to second guess the steps that are part of the procedure. My advice to them is usually to go back and read through the entire guide and follow it exactly as it is written.

If you don't care for joe_blow's version of an updated "fix everything" thread perhaps you should take a stab at it yourself. The original thread definitely needs to be updated, at least with the firmware that was released with the OTA. The choice of bootloader and PRL are more a matter of opinion, but I believe the Jbear 1.50.5050 hboot is a better choice for most users and purposes than the ENG 1.04 version, and I've never gotten much benefit from any PRL except the corporate version that allows data roaming, and that doesn't really apply to VM users. The PRL update seems to be the most difficult part of that guide for new users and and even though it is identified as optional IMO it should be handled separately from updating the firmware and hboot.

Those are the changes I would suggest, but I'm not a VM user and have no way to test procedures to update VM specific firmware so I wouldn't feel comfortable updating that thread.

ramjet73

 

[idone]

I think your boot manager issues are boot related. Not all ROMs will boot on every hboot.

 

[HaTrEd360]

Well concidering the hboot I was on worked with both ROMs I know that wasn't the problem. I can run both ROMs normally I just wanted to dual boot them. But the problem was JB isnt supported for Boot Manager.