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

Root Jellybean Discussion for rooted users (Now Official)

Does the install itself fail or does it fail to boot after flashing?

Check md5 and file sizes. Re-download and try again. You may have gotten a corrupted download.

If you're on hboot 1.15 you need to extract the boot.img and flash via fastboot. Explicit instructions here: S-ON 1.15 HBOOT Dev Unlocked flashing help for kernels, roms and recovery & poll

The install itself fails. After it fails I just restore my BU. File size is 153MB, I've redownloaded a couple of times.

I tried extracting boot.img, flashing with Flash Image GUI, and flashing rom through recovery. I have S-Off, would those instructions still work for me?
 
If you have S-OFF theres no reason to mess with anything in that post because you are able to flash kernels through recovery.

Did you check the MD5 SUM of the download to make sure it wasn't bad?
 
The install itself fails. After it fails I just restore my BU. File size is 153MB, I've redownloaded a couple of times.

I tried extracting boot.img, flashing with Flash Image GUI, and flashing rom through recovery. I have S-Off, would those instructions still work for me?


Have you updated your Hboot to 1.12.222 after getting S-off? That might do it. Also Through Goo manager you can update your Recovery if you have TWRP.
There is more info in the TWRP thread.




Naters
 
Have you updated your Hboot to 1.12.222 after getting S-off? That might do it. Also Through Goo manager you can update your Recovery if you have TWRP.
There is more info in the TWRP thread.

Hmm I have Hboot 1.12.1111. How do I go about updating to 1.12.2222? TWRP I have 2.2.1.
 
I was messing around with this again, and couldn't get Wifi Tether to work. I had it set to Generic ICS, but it wasn't showing up as a recognizable network on my computer or iPad. Is Wifi Tether working for anyone else?
 
Hmm I have Hboot 1.12.1111. How do I go about updating to 1.12.2222? TWRP I have 2.2.1.

You get the new Hboot version from the Unlimited.io website where the lazy panda files came from.

This post helps. Also the first post from the Lazy Panda thread has the link to get the new Hboot.

http://androidforums.com/evo-4g-lte...anda-s-off-ltevo-locked-unlocked-devices.html


http://androidforums.com/evo-4g-lte...anda-s-off-ltevo-locked-unlocked-devices.html



Naters
 
I haven't flashed the JB yet. FFC working?

This moved really quickly. I've followed the thread and Deck and Toast seemed to be working non stop!
Kudo's to them!


Naters
 
had to download a camera app for my setup there was none I could find. Its the latest 8-20. wonder what happend or if i killed it:o
 
You get the new Hboot version from the Unlimited.io website where the lazy panda files came from.

This post helps. Also the first post from the Lazy Panda thread has the link to get the new Hboot.

http://androidforums.com/evo-4g-lte...anda-s-off-ltevo-locked-unlocked-devices.html


http://androidforums.com/evo-4g-lte...anda-s-off-ltevo-locked-unlocked-devices.html



Naters

#1 I ended up updating my Hboot to 1.12.2222. Not sure what advantages this gives me because...

#2. I ended up UNCHECKING the signature option when I flash and I think that was the issue the entire time. I could have sworn I had it unchecked before but I guess I didn't. I'm as current as today's build and flashing does not work when I have signature checked. Weird.

Thanks for the help, fellas!
 
freenode Web IRC (qwebirc)

You have to go to IRC to get it. Newest build and newest gapps are always linked at the top.

Deck doesnt want links anywhere else yet.

Update: ill have 6 hours of screen on time before this battery dies. I could do better but I was Web browsing in a 1x 1bar area today and ate some serious battery.

Tried to acsess the website from my desktop(using Google Chrome Browser) after typing a nick name and all that jazz the chat said I was banned :confused::(:mad:

EDIT: I ended up having to reset my router nothing big.. I'm downloading now!
 
So I've been latest version for the last day or so... Really wish I could use it as a daily driver. Every thing worked well for me when I finally got it running.

The first time I tried to flash and boot up it got caught in boot loop. Yes I did wipe cache and dalvik.... After I re downloaded, ran super wipe, and flashed everything ran smooth but phone didn't work. It could make and receive calls but there is nothing but silence.

I repeated the steps above just to make sure it wasn't my phone but still not working. Besides that though everything else is really good. Jelly Bean is extremely smooth compared to sense As soon as this is fixed I will definitely run as my daily. Until then back to stock. .

EDIT: As someone stated in a post earlier in the thread if you want the rom to run properly you need to have all the sounds & vibrations under the Sounds setting checked on or else it won't fully work

The only sound n vibration settings that can be altered without causing issue to the rom are the 1's pertaining to the Keyboard.
 
So I've been latest version for the last day or so... Really wish I could use it as a daily driver. Every thing worked well for me when I finally got it running.

The first time I tried to flash and boot up it got caught in boot loop. Yes I did wipe cache and dalvik.... After I re downloaded, ran super wipe, and flashed everything ran smooth but phone didn't work. It could make and receive calls but there is nothing but silence.

I repeated the steps above just to make sure it wasn't my phone but still not working. Besides that though everything else is really good. Jelly Bean is extremely smooth compared to sense As soon as this is fixed I will definitely run as my daily. Until then back to stock. .

Did you make sure you had touch tones enabled in settings - sounds? I haven't heard of any call audio issues in the last few builds.
 
Did you make sure you had touch tones enabled in settings - sounds? I haven't heard of any call audio issues in the last few builds.


I found the issue.... I had Vibrate on press checked off. I remember keeping the sounds on because I read in a earlier post that was the "fix all" lol I didn't think it would apply to the vibration too.
 
Prompted by recent conversation over in the Viper thread, I decided to take a look at the memory management settings as implemented by JB. Here they are, as reported by Rom Toolbox Lite:

Foreground: 30
Visible: 38
Secondary server: 46
Hidden: 54
Content provider: 62
Empty app: 77
VM Heap: 256

I'm not knowledgeable enough to draw any conclusions comparing these numbers to what is used stock or by other ROMs. Probably not much basis for comparison anyway.
 
Those numbers tell us a lot, actually.

The minfree settings are not at all aggressive, a huge part of the stock multitasking problem.

The vm setting changed meaning with ICS - that number anticipates that apps wanting more space will want a good deal of it.

Roms vary as to how much ram they'll bite into, but Android is Android. ;) :)
 
Back
Top Bottom