Downgrade to 902 - No app or data loss

[Dave12308]

People can stop PM'ing me about their Norton software now. I get it. Norton is flagging the HoB as a potential threat. It's a false positive and nothing I can do anything about. I can assure you that my files aren't infected so if your antivirus or security software is flagging them, it's a false positive and should be reported to your AV provider. Thanks!

It seems to be ANYTHING that contains a program to help root an Android phone is now considered malware by the big AV vendors. Apparently, this is by design. The actual root exploit itself seems to be the trigger, HoB is affected by this as a "side effect" more or less.

 

[SamuriHL]

It seems to be ANYTHING that contains a program to help root an Android phone is now considered malware by the big AV vendors. Apparently, this is by design. The actual root exploit itself seems to be the trigger, HoB is affected by this as a "side effect" more or less.

Yes, you are correct. But I'm not taking root out of the HoB.

 

[SamuriHL]

Someone PM'd me a little while ago about going from 232 to 244 and what my thoughts are on it. I thought I'd share my answer with the class....

----------------------------

I don't mind people going to 235+ as long as they are aware of, and accept, the risks of doing so. First is you can't FXZ to 905. So that complicates things in the event of a brick situation and certainly for applying new updates. That being said, I designed the HoB to help us insane people that live out on the edge. I've made it as safe as I possibly can. That does NOT mean risk free, but, I have a few safety nets in there.

First, I can build an on the fly mini-fxz to repair an install gone wrong. (I.E. brick scenario). The requirement is that the update for the version you're trying to repair *MUST* remain on the sdcard-ext. With that requirement met, I've yet to be able to unbrick someone. It's ALMOST as good as a real FXZ.

Second is the ability to add new updates to the HoB without my intervention. Meaning, let's say you get your hands on 251 and you see that it fixes EVERYTHING. I'm out camping at a NASCAR race for 4 days and don't have the ability to create an update support installer for it. (Yes, that's going to happen in 2 weeks, so....). You can add a new 251 directory, append 251 to the zip filename, and run the HoB batch file. It'll ask if you want to create a new boot img for it, you tell it yes, plug your phone in, and when the menu comes up, you'll have a INSTALL 251 and REINSTALL 251 option. Choose the INSTALL 251 option and you're no longer stuck on 244.

However, I'd caution you on newer leaks. They need to be checked with the CDTParser.exe that's in the utils dir. Basically extract the CDT.bin from your new update, and open it with the CDTParser.exe. Compare it with the CDT.bin from 244. (You can open 2 instances of the CDTParser.exe at the same time). If they're the same, you're good to go. If anything in there goes UP in security, consult the experts before installing.

 

[NuLL.n.VoiD]

Someone PM'd me a little while ago about going from 232 to 244 and what my thoughts are on it. I thought I'd share my answer with the class....

----------------------------

I don't mind people going to 235+ as long as they are aware of, and accept, the risks of doing so. First is you can't FXZ to 905. So that complicates things in the event of a brick situation and certainly for applying new updates. That being said, I designed the HoB to help us insane people that live out on the edge. I've made it as safe as I possibly can. That does NOT mean risk free, but, I have a few safety nets in there.

First, I can build an on the fly mini-fxz to repair an install gone wrong. (I.E. brick scenario). The requirement is that the update for the version you're trying to repair *MUST* remain on the sdcard-ext. With that requirement met, I've yet to be able to unbrick someone. It's ALMOST as good as a real FXZ.

Second is the ability to add new updates to the HoB without my intervention. Meaning, let's say you get your hands on 251 and you see that it fixes EVERYTHING. I'm out camping at a NASCAR race for 4 days and don't have the ability to create an update support installer for it. (Yes, that's going to happen in 2 weeks, so....). You can add a new 251 directory, append 251 to the zip filename, and run the HoB batch file. It'll ask if you want to create a new boot img for it, you tell it yes, plug your phone in, and when the menu comes up, you'll have a INSTALL 251 and REINSTALL 251 option. Choose the INSTALL 251 option and you're no longer stuck on 244.

However, I'd caution you on newer leaks. They need to be checked with the CDTParser.exe that's in the utils dir. Basically extract the CDT.bin from your new update, and open it with the CDTParser.exe. Compare it with the CDT.bin from 244. (You can open 2 instances of the CDTParser.exe at the same time). If they're the same, you're good to go. If anything in there goes UP in security, consult the experts before installing.

Holy crap! I thought I was a tech junkie but I think you just jargoned us to death.

I can't thank you enough for making it easier for folks like me who aren't afraid to tinker but aren't exactly programmers either.:hail:

 

[greeneink]

SamuriHL,
I just want to thank you again for making it too easy. I was perfectly happy living on .242 without a care as to when or if an official OTA comes out.
Then comes the "pusher man" with an all to easy fix. 15 minutes later, I got my .244 on and living the blissful life. I'm really happy with my phone now.
I'll think I'll jack up my Xoom. I've never run a ROM on either my phone or tablet. I guess it's time.

 

[SamuriHL]

You're very welcome. Give some love to the Team EOS builds on the Xoom. You won't have any regrets if you do.

 

[drice72]

This script worked very well for me. I'm on .232 now. We will see if its much better than the .2233 I was running.

 

[Delasangre4231]

This script worked very well for me. I'm on .232 now. We will see if its much better than the .2233 I was running.

I am about to do the same, very interested in mostly battery life. Like how much better it gets with the .232!

 

[altspeed]

The script worked like a dream for me like always. I have to look at my build # to actually believe I did 242/244 last night.

 

[92ehatch]

I am trying to go from 2232 to 232 and have followed the instructions, read and reread.

however when i choose "push update to sdcard-ext" it just stops at the point of "daemon started successfully"

how long does it take?

 

[SamuriHL]

10+ minutes. Patience is a virtue.

 

[SamuriHL]

I don't use it because you still have to boot the phone after the FXZ is done

Huh?

 

[92ehatch]

still waiting. i do have a question. in my windows browser under my phone i have Internal storage and SDcard.

sdcard is sdcard-ext? or am i missing something

i went from 905 to 2232 no problems, but i did it manually. was hoping not to lose apps data by using this

 

[SamuriHL]

sdcard != sdcard-ext. And you can always copy it manually if you don't want to wait.

 

[92ehatch]

flashing now. had to move update and put into AP fastboot manually. wonder why the HoB wouldnt do it for me? my computer possibly?