• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [Boost Mobile] [ROM] HaloBean 9 FINAL (SkinnyHALO Included)

New Name?

  • Total voters
    60
Here's a version that will overwrite the powernap script in this rom only, in this rom since it's called S09sleepyhaloz it'll overwrite S09sleepyhaloz safely; however it may be named different in other roms, and this script is really modified for this rom mostly anyways. It'll work in other roms as long as you can find a remove the script before flashing. As a recap, this sets the governor to conservative-122 min-248 max when the screen goes off
https://copy.com/XxXBfDJrVnI9QrlE
 
Uh oh....
I seem to have lost root
Opened TB & got this msg:
Could not acquire root privileges. This attempt was made by using the command "/system/bin/su"​

Opened SuperSU & got this msg:

There is no su binary installed & SuperSU cannot install it​

I went to /system/xbin/ and there is a file named su but I didn't try to open it as I would have no idea if it looked right.

Rebooted twice

I decided to uninstall/reinstall SuperSU to see that the app was in good shape. In App Manager, Uninstall is not a choice. In it's place the option is Uninstall Updates.
- I uninstalled updates. Got msg that SuperSU is restored to factory version
- Opened SuperSU. Same msg-- no change-- no root
- Reinstalled updates. No change

While re-updating I noticed these 2 items listed under What's New:
-- Binary denies root if PIN code set previously but GUI not present
-- Fixed some devices losing root​
Hmmm... don't know if there's a PIN code. Don't know if it means some fundamental GUI that's coded in or whether superficial changes (like playing with icons) can affect SuperSU's ability to detect GUI (?) Of course the SuperSU error msg said: "no su binary installed", which is a step before the "binary denies root" (changelog), but then again the effect of denying root might make it appear that there is no binary ... [aimzzz pulls hair with both hands]

If SuperSU update change re. GUI caused the binary to deny root, should root be reestablished when I reset SuperSU to the older version, or is a matter of once it's gone, it's gone? (Heh...it may sound like I know what I'm talking about but I only have a vague idea about it. More likely I sound like I don't know squat)

Is there another SU-like app I could install to test whether the problem is the result of SuperSU update?

If not, do I need to start over? If so, is it just a matter of reinstalling the root zip file?

Of course the problem might have a totally different cause ... :rolleyes:
 
aimzzz said:
Uh oh....
I seem to have lost root
Opened TB & got this msg:
Could not acquire root privileges. This attempt was made by using the command "/system/bin/su"​

Opened SuperSU & got this msg:

There is no su binary installed & SuperSU cannot install it​

I went to /system/xbin/ and there is a file named su but I didn't try to open it as I would have no idea if it looked right.

Rebooted twice

I decided to uninstall/reinstall SuperSU to see that the app was in good shape. In App Manager, Uninstall is not a choice. In it's place the option is Uninstall Updates.
- I uninstalled updates. Got msg that SuperSU is restored to factory version
- Opened SuperSU. Same msg-- no change-- no root
- Reinstalled updates. No change

While re-updating I noticed these 2 items listed under What's New:
-- Binary denies root if PIN code set previously but GUI not present
-- Fixed some devices losing root​
Hmmm... don't know if there's a PIN code. Don't know if it means some fundamental GUI that's coded in or whether superficial changes (like playing with icons) can affect SuperSU's ability to detect GUI (?) Of course the SuperSU error msg said: "no su binary installed", which is a step before the "binary denies root" (changelog), but then again the effect of denying root might make it appear that there is no binary ... [aimzzz pulls hair with both hands]

If SuperSU update change re. GUI caused the binary to deny root, should root be reestablished when I reset SuperSU to the older version, or is a matter of once it's gone, it's gone? (Heh...it may sound like I know what I'm talking about but I only have a vague idea about it. More likely I sound like I don't know squat)

Is there another SU-like app I could install to test whether the problem is the result of SuperSU update?

If not, do I need to start over? If so, is it just a matter of reinstalling the root zip file?

Of course the problem might have a totally different cause ... :rolleyes:
Click to expand...

I know Superuser by KoushikDutta had this issue, but not SuperSU... I'm not having this issue on my new test builds... but the test builds use the same supersu as the one in HaloBean8 so there should be no issues?
 
Skinnyjeans21 said:
I know Superuser by KoushikDutta had this issue, but not SuperSU... I'm not having this issue on my new test builds... but the test builds use the same supersu as the one in HaloBean8 so there should be no issues?
Click to expand...
Should I just reinstall the root zip then?

Edit: or should I do factory reset first in case there's some residual garbage?

Edit2:
Hmmm... maybe not factory reset. There have been several software updates since I got the phone. Will test by reinstalling root zip & check root with SuperSU. Then update SuperSU & see if still rooted
 
aimzzz said:
Uh oh....
I seem to have lost root
Opened TB & got this msg:
Could not acquire root privileges. This attempt was made by using the command "/system/bin/su"​

Opened SuperSU & got this msg:

There is no su binary installed & SuperSU cannot install it​

I went to /system/xbin/ and there is a file named su but I didn't try to open it as I would have no idea if it looked right.

Rebooted twice

I decided to uninstall/reinstall SuperSU to see that the app was in good shape. In App Manager, Uninstall is not a choice. In it's place the option is Uninstall Updates.
- I uninstalled updates. Got msg that SuperSU is restored to factory version
- Opened SuperSU. Same msg-- no change-- no root
- Reinstalled updates. No change

While re-updating I noticed these 2 items listed under What's New:
-- Binary denies root if PIN code set previously but GUI not present
-- Fixed some devices losing root​
Hmmm... don't know if there's a PIN code. Don't know if it means some fundamental GUI that's coded in or whether superficial changes (like playing with icons) can affect SuperSU's ability to detect GUI (?) Of course the SuperSU error msg said: "no su binary installed", which is a step before the "binary denies root" (changelog), but then again the effect of denying root might make it appear that there is no binary ... [aimzzz pulls hair with both hands]

If SuperSU update change re. GUI caused the binary to deny root, should root be reestablished when I reset SuperSU to the older version, or is a matter of once it's gone, it's gone? (Heh...it may sound like I know what I'm talking about but I only have a vague idea about it. More likely I sound like I don't know squat)

Is there another SU-like app I could install to test whether the problem is the result of SuperSU update?

If not, do I need to start over? If so, is it just a matter of reinstalling the root zip file?

Of course the problem might have a totally different cause ... :rolleyes:
Click to expand...

What the heck have you done? Flashing the rom should have been short & sweet, no issue.... Not bitching at ya, just wondering what went wrong. Are you playing with scripts and such? Leave all of the other stuff alone, and keep the rom as is. That's why we have these guys here. "they test and find the problems, and or, have us test it out". I'm not criticizing you Honey, Believe me I was the first to try to tweak things, and I fubbed up. And it's a learning thing. And you're probably smarter than I am. I just read the post and wondered, WTH? Love ya, And have a Merry X-mas.
And then, on the other hand, I believe that experimenting is the mother of invention, and exploration of what' could be and what should be.
 
Skinnyjeans21 said:
That's how I bricked my Warp... messing around with it. I did bring it back to life after toying around for a day with it
Click to expand...

Oh, I did to! We all like to play with it. And believe me, I'm not as savvy as you guys. And It all comes with experimentation, and seeing what we can do on our own. It's a learning experience. I'm sure she's a lot better at this than I am. But, I've learned, "ask first". LOL. Bless her heart, she's trying!
BTW, Good job my brother! And have a great holiday!
 
sb43 said:
Oh, I did to! We all like to play with it. And believe me, I'm not as savvy as you guys. And It all comes with experimentation, and seeing what we can do on our own. It's a learning experience. I'm sure she's a lot better at this than I am. But, I've learned, "ask first". LOL. Bless her heart, she's trying!
BTW, Good job my brother! And have a great holiday!
Click to expand...

Ask first... for me its "search-all-over-the-internet-and/or-ask-for-tips-from-TeamOsiris-if-I-don't-know-what-the-bleep-I'm-doing-anymore-because-I've-effed-so-much-stuff-up", then ask questions later :D

And you have a great holiday too! :D


Also, about losing root... a reflash of the rom will definitely fix it I'm sure, changing an icon on the desktop ain't gonna do a thing. I'm running my 6th HaloBean 9 Release Candidate on both my Warps, and they both have the supersu included in 8. Both running just fine. And I just had to flash RC6 to my personal Warp, the battery life was so great on my dev unit I just had to try it on my other Warp :D
 
sb43 said:
What the heck have you done?
Click to expand...
You don't sound inclined to believe me, but I haven't done anything I can think of that would cause such a problem. Definitely haven't messed with any scripts... I wouldn't know where to start.

Since the 10th I haven't used anything requiring root, except I used root explorer, but only in the Storage section, not the root side. I'm not even sure exactly when the problem happened. This morning I decided to back up some stuff using TB. When I went to the Backup tab, I got the msg that it could not acquire root privileges.

Over the last couple of days, I DL'd some icon packs & played around with them using Holo launcher. I installed a couple of keyboards & tried them out. Reinstalled a scanner app that I hadn't gotten around to since rooting.... cant remember anything else

Skinnyjeans21 said:
The root zip? No... that won't do it. Factory reset won't fix it either.
Click to expand...
Yeah, I tried both earlier. Also I did a restore which didn't help at all.... same error mag
How do I reflash the rom?

Edit:
In the old days I used to tank my PC's playing around with them, but almost impossible to brick them (tho I did have to do the occasional reformatting of the drive). But I haven't run amok with the phone :P
 
aimzzz said:
You don't sound inclined to believe me, but I haven't done anything I can think of that would cause such a problem. Definitely haven't messed with any scripts... I wouldn't know where to start.

Since the 10th I haven't used anything requiring root, except I used root explorer, but only in the Storage section, not the root side. I'm not even sure exactly when the problem happened. This morning I decided to back up some stuff using TB. When I went to the Backup tab, I got the msg that it could not acquire root privileges.

Over the last couple of days, I DL'd some icon packs & played around with them using Holo launcher. I installed a couple of keyboards & tried them out. Reinstalled a scanner app that I hadn't gotten around to since rooting.... cant remember anything else


Yeah, I tried both earlier. Also I did a restore which didn't help at all.... same error mag
How do I reflash the rom?
Click to expand...

Flash it again through recovery: just locate the zip file that you downloaded to your SD card in ClockworkMod, install like you did before, and that's it. Then you can go in titanium and restore your apps from a nandroid. In fact, make a nandroid before installing the rom again so you can restore the apps from the nandroid backup in Titanium Backup. Really cool feature :)
 
Skinnyjeans21 said:
Flash it again through recovery: just locate the zip file that you downloaded to your SD card in ClockworkMod, install like you did before, and that's it. Then you can go in titanium and restore your apps from a nandroid. In fact, make a nandroid before installing the rom again so you can restore the apps from the nandroid backup in Titanium Backup. Really cool feature :)
Click to expand...

It looks easy but, I'm not using the Warp-- am using the Flash, so I didn't use ClockworkMod. I rooted with Root_with_Restore_by_Bin4ry_v32 from xda.
To install it you extract the zip file onto the PC desktop. Then you run a .bat file from the PC (RunMe.bat). I'm trying to remember what I did earlier to get the recovery but I think I did recovery by running that file. I had done factory reset & I think .bat file did a recovery instead of re-rooting... arghhh! I can't believe I don't remember what I did just a few hours ago

Edit: I renamed the .bat as a .txt & am attaching it here: View attachment RunMe.txt. It shows the code that directs the recovery. If it's the equivalent of recovery through ClockworkMod, then I already reflashed-- couldn't be since still not rooted. Maybe I'll try it again while waiting... (Used option 1 for my device)
 
aimzzz said:
It looks easy but, I'm not using the Warp-- am using the Flash, so I didn't use ClockworkMod. I rooted with Root_with_Restore_by_Bin4ry_v32 from xda.
To install it you extract the zip file onto the PC desktop. Then you run a .bat file from the PC (RunMe.bat). I'm trying to remember what I did earlier to get the recovery but I think I did recovery by running that file. I had done factory reset & I think .bat file did a recovery instead of re-rooting... arghhh! I can't believe I don't remember what I did just a few hours ago

Edit: I renamed the .bat as a .txt & am attaching it here: View attachment 65442. It shows the code that directs the recovery. If it's the equivalent of recovery through ClockworkMod, then I already reflashed. Maybe I'll try it again while waiting... (Used option 1 for my device)
Click to expand...

I'm not exactly an expert with the ADB, but it looks like all the script does is install SuperUser and BusyBox with varying methods for different devices. There's some backup-related stuff in there, but as far as I can tell, it's spoofed backup stuff that acts as part of the install method.

So there shouldn't be anything in there that'd backup/restore any nandroids/etc, if that's what you're asking.

Quick Edit: The method you used does have an ADB backup call in it, but it'd be for the actual time you run the script, so if you ran it after losing root, as would be the case, it wouldn't help (restore your device to when it had root).

It may also be more helpful to you to post in the device-specific forum. Not telling you I or we don't want to help you, but you'd likely find more relevant help there.
 
WhisperingClaw said:
It may also be more helpful to you to post in the device-specific forum. Not telling you I or we don't want to help you, but you'd likely find more relevant help there.
Click to expand...
Sorry everybody!!! I meant to stop posting in the HB8 thread about this problem if/when it got past the point of being a general problem & became specifically about my current phone (ZTE Flash). I managed to forget my intentions by the time I got to my last post.

Sorry!!!!! :o
 
Don't know if this will help but here's my two cents worth. I rooted my phone with teamwin and then flashed it to the cyanogenmod. After too many bugs I decided to flash to halobean 8. I still was rooted with teamwin so I just used it to flash to halobean. No problems at all. Even flashed his latest script again no problems. My phone is zte warp n860. Hope this helps.
 
aimzzz said:
Sorry everybody!!! I meant to stop posting in the HB8 thread about this problem if/when it got past the point of being a general problem & became specifically about my current phone (ZTE Flash). I managed to forget my intentions by the time I got to my last post.

Sorry!!!!! :o
Click to expand...

Honey, you're okay,. All of your input is useful information. It makes the dev's think about the "what if's, and if I did That's". You keep on keepin on!
 
in a little different direction, but hroark posted return to stock b08c, but how do I return to stock b10? is there an update from b08c to b10, or ...?
thought I read you used to be able to update from stock rom to a newly released rom (all stock, without root), but that the method has since been shelved? color me confused, eh?

ps. really liking halobean and droidsmith so far. skinnyjeans, you mentioned halobean 9? holiest of cows, do we have a timeline?
 
cmpyutr said:
in a little different direction, but hroark posted return to stock b08c, but how do I return to stock b10? is there an update from b08c to b10, or ...?
thought I read you used to be able to update from stock rom to a newly released rom (all stock, without root), but that the method has since been shelved? color me confused, eh?

ps. really liking halobean and droidsmith so far. skinnyjeans, you mentioned halobean 9? holiest of cows, do we have a timeline?
Click to expand...

Stock B10... that was an update. I'm certain you can use the stock b08c update, wait a few minutes or hours, and you'll get a prompt telling you to update to b10, after which the phone will download the update and install :)

Also... I did make a timeline... its called the changelog lol but I do have the dates of all the days I uploaded an update to Dropbox/Copy. But yeah, HaloBean 9 is in the works and it'll have the best battery life out of all the HaloBean/HaloJelly versions I've made :D
 
Hey Skinnyjeans21 I have been using this rom since 2.75 RC2, sometimes skipping a release due to the fast dev of the rom and releases coming fast! lol
Currently running HB8, lately my extended batteries are not lasting a full day when they used to last nearly 3. I know others have mentioned battery drain also so I won't go into any detail. Also looking forward to the next release.

I wanted to mention a possible bug in the camera app, the one that comes with the rom is timestamping my photos for 2002! I checked the time to make sure it was correct and it is. I dl another camera app and it timestamps correctly so you might want to delve into that for future releases. I hope I did not just give you another headache! lol

Happy Holidays!
 
You must log in or register to reply here.
Back
Top Bottom