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

Jelly Bean Rom Guide & Mods

So Do You Just Download The Cwm flashable Version, To Get It To Work?

I've Had A Long Night At Work And Could Do With A"Dummies GUide"For Flashing This And Having It Rooted So I Could Essentially Flash Siyah And Boot Onto Second ROM If Required!

Would This Be Possible? (Don't Mean That Siyah Would Work With The Stock It'd Just Mean My Primary ROM Didn't Work!)
 
Mate I'm off to bed now ...but if you can hang on till tomorrow I can throw something together for you..

I don't want to scare you but the stock kernel has some kind of brick bug so if youre tired hang on and approach it with a fresh head tomorrow

In answer to your question you can't use Siyah it Dorimanx on this yet ...only PhilZ Kernel ....

I'll put together what I did with links to the files etc I promise
 
Mate I'm off to bed now ...but if you can hang on till tomorrow I can throw something together for you..

I don't want to scare you but the stock kernel has some kind of brick bug so if youre tired hang on and approach it with a fresh head tomorrow

In answer to your question you can't use Siyah it Dorimanx on this yet ...only PhilZ Kernel ....

I'll put together what I did with links to the files etc I promise

Don't Worry,I Was Just Heading To Bed AfterTyping All That.

Sale Recons A Day Or Two For Him To Make One.... I May Just Wait For That. Thanks Anyway :-)
 
Why is the Phil kernel is the only one that can be used?
In theory, Siyah and Dori auto root and should be JB compatible.
Dori 7.? kernels certainly are, and Siyah has been working on CM/AOKP JB for ages.
:confused:

I guess it must be a Sammy quirk.
 
Apparently the brickbug is in this build, no sudden movements after flashing! I'm going to keep an eye out for anyone getting bricked and also hoping a siyah kernal will be released soon to get us to safety!!

Also if anyone used the sammobile link to get jb,to root you can download the cwm package here http://forum.xda-developers.com/showthread.php?p=34180283#post34180283 then rename it to update.zip, place onto external sd and flash using samsung recovery mode. This is easier than using adb, I would imagine Philz method is similar but I haven't checked. Download Superuser from play store and you're done!
 
Why is the Phil kernel is the only one that can be used?
In theory, Siyah and Dori auto root and should be JB compatible.
Dori 7.? kernels certainly are, and Siyah has been working on CM/AOKP JB for ages.
:confused:

I guess it must be a Sammy quirk.

Mate I'm just repeating what I've read... Your post is seems logical but I don't know why sorry. I'm a good researcher but i am an absolute technoob

I had a bit of a problem this morning

Everything was working fine until my signal dropped and I was asked to insert sim

I cleaned, wiped, fixed permissions to no avail

Thankfully I had a back up of Neat Rom XXLPY

Let this not discourage you dipping your toes in if you want to. I believe I need a new simcard as this would happen on my Neat Rom but a quick reboot would fix that.

I cannot express enough the need to make a backup

Whilst it was working it was frikkin awesome.. Really really nice

I may just wait for Sale before I get smothered in Jelly Bean again
 
Mate I'm just repeating what I've read... I'm a good researcher but i am an absolute technoob

I had a bit of a problem this morning

Everything was working fine until my signal dropped and I was asked to insert sim

I cleaned, wiped, fixed permissions to no avail

Thankfully I had a back up of Neat Rom XXLPY

Let this not discourage you dipping your toes in if you want to. I believe I need a new simcard as this would happen on my Neat Rom but a quick reboot would fix that.

I cannot express the need to make a backup

Whilst it was working it was frikkin awesome.. Really really nice

I may just wait for Sale before I get smothered in Jelly Bean again
I read a few posts on xda regarding what I think is your problem! NETWORK LOCK... (GASP), I think it's fixable by downloading an app (try this...)
http://forum.xda-developers.com/showpost.php?p=34187077&postcount=685

Glad you didn't get burnt restoring Neatrom (possible brickbug)
 
Please someone correct me if im wrong

But because I had flashed PhilZ kernel he said had removed the brick bug so I wasnt too worried. Am I right in thinking this ?

My belief was that the Brick Bug is only apparent in Stock Kernel

I thought it was my EFs Folder at first, nearly passed out ha ha
 
Mate I'm just repeating what I've read... I'm a good researcher but i am an absolute technoob

I had a bit of a problem this morning

Everything was working fine until my signal dropped and I was asked to insert sim

I cleaned, wiped, fixed permissions to no avail

Thankfully I had a back up of Neat Rom XXLPY

Let this not discourage you dipping your toes in if you want to. I believe I need a new simcard as this would happen on my Neat Rom but a quick reboot would fix that.

I cannot express the need to make a backup

Whilst it was working it was frikkin awesome.. Really really nice

I may just wait for Sale before I get smothered in Jelly Bean again

I get this ocasionally on my handset.
Stupid question but I guess you tried replacing the battery+sim first butty?
I'm sure on mine the SIM connection isn't quite tight enough.
 
I get this ocasionally on my handset.
Stupid question but I guess you tried replacing the battery+sim first butty?
I'm sure on mine the SIM connection isn't quite tight enough.

I certainly did mate...I even blew gently on my sim :thumbup:

I believe I done everything I could that was physically possible. Maybe after flashing Philz kernel I should have made a Efs back up... I don't know... That stuff is far beyond my knowledge that's where I was hoping you would come in Hawker ;)
 
Siyah and Dori backup your EFS on installation
This goes to /data/.siyah and has 2 files: efsbackup.tar.gz and efsdev-mmcblk0p1.img.gz

You can manually restore by doing the following:
1. go to CWM recovery
2. mounts & storage - make sure /efs is not mounted and the place where your backup file is placed is mounted (ie /data)
3. connect pc to the phone and run adb shell
4. execute following commands:

gzip -d efsdev-mmcblk0p1.img.gz
cat efsdev-mmcblk0p1.img > /dev/block/mmcblk0p1


Bit like closing the door after the horse as bolted, but a far easier way is to install an app called GSII Repair
this can be used to save a copy of your working efs folder in /sdcard/GSII_repair/efs_save.tar.gz

The app can be used to restore your efs if it ever goes buttock over breasticle
 
Siyah and Dori backup your EFS on installation
This goes to /data/.siyah and has 2 files: efsbackup.tar.gz and efsdev-mmcblk0p1.img.gz

You can manually restore by doing the following:
1. go to CWM recovery
2. mounts & storage - make sure /efs is not mounted and the place where your backup file is placed is mounted (ie /data)
3. connect pc to the phone and run adb shell
4. execute following commands:

gzip -d efsdev-mmcblk0p1.img.gz
cat efsdev-mmcblk0p1.img > /dev/block/mmcblk0p1


Bit like closing the door after the horse as bolted, but a far easier way is to install an app called GSII Repair
this can be used to save a copy of your working efs folder in /sdcard/GSII_repair/efs_save.tar.gz

The app can be used to restore your efs if it ever goes buttock over breasticle

Ah thanks very much mate the first part of your post seemed like swahilli to me so I downloaded GS2 repair and made a back up so that if my network goes I dont have to access the market to get it

Guess what.......Ive gone and flashed it again via Mobile Odin Pro. I know I know ........but it worked.....Im back in Jelly bean and loving it

Ill update the original post with the instructions I used for this as for me, it was far easier than using a PC

First things first GS2 repair just in case

Hawker if you hear of any mention of someone succesfully using Siyah or Dorimanx could you let me know please mate. The automatic back up of EFS is vital in my opinion.

Thanks

:smokingsomb:
 
Dori appears to be working on it mate. He's downloaded the firmware and he needs certain files from the download to incorporate into the kernel.

I'm not sure, but this will could well mean these will be JB specific builds so we may have to be extra careful what we flash from now on.
 
Please someone correct me if im wrong

But because I had flashed PhilZ kernel he said had removed the brick bug so I wasnt too worried. Am I right in thinking this ?

My belief was that the Brick Bug is only apparent in Stock Kernel

I thought it was my EFs Folder at first, nearly passed out ha ha

Could you send me the link for that kernel? Does anyone see an issue with me trying to flash this kernel whilst on stock JB... Idon't know enough about the brick bug so am therefore cautious as hell on doing any more flashing!
 
Could you send me the link for that kernel? Does anyone see an issue with me trying to flash this kernel whilst on stock JB... Idon't know enough about the brick bug so am therefore cautious as hell on doing any more flashing!

Link to Kernel in OP mate

As mentioned I restored a back up of Neat then reflashed via Mobile Odin Pro which allowed me to flash PhilZ kernel at the same time so my phone never had the stock kernel with Brick Bug. I like that idea.

Courtesy of Hawker (The only way to get Brick Bugged)
1. You have flashed a rogue kernel that has MC_CAP_ERASE=1 (Stock Jelly Bean has this)
2. You subsequently perform any sort of wipe (eg. cache, dalvik, factory reset) or restore via CWM Recovery whilst still on this rogue kernel.

A Flash of PhilZ Kernel should be fine as long as you DO NOT WIPE

I wouldnt do anything until hopefully Hawker spots this and confirms this is the case
 
OP updated with advice from Hawker

Hawker is this ok mate I hope you dont mind, full credit given. If its a problem let me know

Thanks Dude
 
Back
Top Bottom