Database Info

Kernel for JB

Hi,
I tried several kernels for JB. Air, Matrix. None of them worked for me. After flashing it, it won't boot the system and turn off the device. I currently use JellyBelly 1.5. Any idea? Is it ROM bug? Thanks!

devcager said:
Hi,
I tried several kernels for JB. Air, Matrix. None of them worked for me. After flashing it, it won't boot the system and turn off the device. I currently use JellyBelly 1.5. Any idea? Is it ROM bug? Thanks!
Click to expand...
Click to collapse
I can't use Adam's Jelly Belly rom, as I have a NS4g, but I do follow his work. I believe that his rom comes with Thalamus kernel, and if you want to flash a different kernel, there is a file which needs to be deleted before doing so. There was quite a discussion about all this in his thread in the development forum. That's where you can figure it out ... good luck!

same for me
Hey i also tried to flash thalamus kernel but my phone didnt start it was hanged up on the boot screen. I am using Nexus S i9023 SCLD version stock rom 4.1.1 build JRO03E and it is rooted.
Can anyone please help me and also which other kernels are supported on stock rom.

There's a script you must delete in the init.d to use another kernel in Jelly Belly 0.1.5
Otherwise, your phone will poweroff

panks_4ever said:
Hey i also tried to flash thalamus kernel but my phone didnt start it was hanged up on the boot screen. I am using Nexus S i9023 SCLD version stock rom 4.1.1 build JRO03E and it is rooted.
Can anyone please help me and also which other kernels are supported on stock rom.
Click to expand...
Click to collapse
i have also a i9023 and i have allredy flashed bedalus kernel, thalamus and air kernel also matrix and vta2 worked for me..
i use JRO03E DX stock ROM..never had a problem
S.R.

(I use stock JB with Air #153, and got i9023. No OC, no NSTools, yet. I have no problem.)
On stock:
Try to do a factory reset/wipe data, or reflash the OS from scratch using factory images. And right after flashing the rom, flash the kernel. Even before installing any apps.
On JBelly:
For this, I think the Thalamus kernel is the best, the rom is come with it, so they made for each other If this kernel works with it, i think it is unnecessary to switch to another kernel right now.
Because JB kernels are not final yet, are "immature", there can be compatibility issues, collisions between (certain functions of) roms and kernels.
After a 2 or 3 releases, both on rom and kernel side, there will be more complete and stable versions.

Have you tried to fix permissions ?

Go to /etc/init.d/ folder and delete a file called 'kernel'. You can read it first if you want.
This is basically a hack that AdamG added to avoid everyone changing kernels and reporting problems about the ROM. He only allows thalamus kernel.

Can please provide me detailed steps of how to flash a thalamus kernel on stock jb because i think the procedure is wrong. I did the following steps:
1. Reboot into recovery( I am using Clockwork Mod recovery touch 6.0.1.0)
2. Wipe Cache partition
3. Wipe Dalvik cache
4. Install the kernel zip file
And after i tried restarting my phone but it hanged up on the boot screen.
Please someone advise me the correct steps if this is wrong
. Thanks in advance
Sent from my Nexus S using xda app-developers app

panks_4ever said:
1. Reboot into recovery( I am using Clockwork Mod recovery touch 6.0.1.0)
2. Wipe Cache partition
3. Wipe Dalvik cache
4. Install the kernel zip file
Click to expand...
Click to collapse
I think the cache partition wipe is your problem. You shouldn't have to wipe anything if you're flashing _thalamus' kernel on stock JB. Just flash and reboot. I've done it plenty of times without problems.

devcager said:
Hi,
I tried several kernels for JB. Air, Matrix. None of them worked for me. After flashing it, it won't boot the system and turn off the device. I currently use JellyBelly 1.5. Any idea? Is it ROM bug? Thanks!
Click to expand...
Click to collapse
To not have to deal with third party kernel support there is /system/etc/init.d/00kernel that simply powers off your phone if you flash another kernel.
Flash the rom to boot it, delete the file, then flash any kernel you want as you usually would.

charchuck said:
I think the cache partition wipe is your problem. You shouldn't have to wipe anything if you're flashing _thalamus' kernel on stock JB. Just flash and reboot. I've done it plenty of times without problems.
Click to expand...
Click to collapse
wipe is not needed...
but fix permissions should be done...but I´m not sure thats required for all kernel.
S.R.

so this are the final steps...
shivasrage said:
wipe is not needed...
but fix permissions should be done...but I´m not sure thats required for all kernel.
S.R.
Click to expand...
Click to collapse
Firstly, thanks for replying. I need to do the folloing steps (just to confirm because its better to do so and also i dont want to again restore a backup)
1. Reboot into recovery
2. Wipe Dalvik Cache
3. Install the kernel zip file
4. Fix Permissions
or 3. Fix Permissions, and then
4. Install kernel zip file
Please advise the correct steps and thanks in advance.
(I know i am getting a bit more concerned because i had it twice and i am not able to flash the same. So, I am trying to get a correct way and this the best place to ask. XDA rocksssssss<3<3<3)

panks_4ever said:
Firstly, thanks for replying. I need to do the folloing steps (just to confirm because its better to do so and also i dont want to again restore a backup)
1. Reboot into recovery
2. Wipe Dalvik Cache
3. Install the kernel zip file
4. Fix Permissions
or 3. Fix Permissions, and then
4. Install kernel zip file
Please advise the correct steps and thanks in advance.
(I know i am getting a bit more concerned because i had it twice and i am not able to flash the same. So, I am trying to get a correct way and this the best place to ask. XDA rocksssssss<3<3<3)
Click to expand...
Click to collapse
There's no need for all that... flash jellybelly latest version, boot with the original kernel and delete /system/etc/init.d/00kernel with Rom Toolbox or Root explorer. After that you can flash the kernel that you want. Mind that this will only work for version 0.1.5.1, versions after that one will probably have a framework check to prevent flashing 3rd party kernels because the dev of jellybelly doesn't want to be disturbed with bugs caused by other kernels then not the Thalamus one.
---------- Post added at 08:55 AM ---------- Previous post was at 08:34 AM ----------
Checked. Version 1.0.0 only allows Thalamus kernel to be flashed. A framework check doesn't allow 3rd party kernels to be fixed so either you stick to the stock kernel of jellybelly or get another ROM so you can use other Kernels.

Panks_4ever
What I always do.. (phone i9023 X-JB Stock).
1. flash kernel zip
2. wipe cache
3. wipe dalvik
4. fix permissions
i only know that thalamus kernel don´t need any wipe...also i don´t know if this procedure is right or not
and i don´t won´t discuss about i only can report what worked for me so try it or not its your decision....
S.R.

thank you
shivasrage said:
Panks_4ever
What I always do.. (phone i9023 X-JB Stock).
1. flash kernel zip
2. wipe cache
3. wipe dalvik
4. fix permissions
i only know that thalamus kernel don´t need any wipe...also i don´t know if this procedure is right or not
and i don´t won´t discuss about i only can report what worked for me so try it or not its your decision....
S.R.
Click to expand...
Click to collapse
DeuXGod said:
There's no need for all that... flash jellybelly latest version, boot with the original kernel and delete /system/etc/init.d/00kernel with Rom Toolbox or Root explorer. After that you can flash the kernel that you want. Mind that this will only work for version 0.1.5.1, versions after that one will probably have a framework check to prevent flashing 3rd party kernels because the dev of jellybelly doesn't want to be disturbed with bugs caused by other kernels then not the Thalamus one.
---------- Post added at 08:55 AM ---------- Previous post was at 08:34 AM ----------
Checked. Version 1.0.0 only allows Thalamus kernel to be flashed. A framework check doesn't allow 3rd party kernels to be fixed so either you stick to the stock kernel of jellybelly or get another ROM so you can use other Kernels.
Click to expand...
Click to collapse
Thank you shivasrage and DeuXGod. I am surely goona try out this, i am being eagerly waiting to flash a custom kernel because as compared to ICS i feel JB is eating up more battery. Thank you so much:good:

Viper XL and boot.img

Hey guys I just wanna to check and make sure I'm doing everything right before I flash cause I don't need anymore paperweights
1.I have successfully unlocked my bootloader and installed twrp recovery and rooted.
2. Now I want to back up my entire setup: rom, apps, setting, data, everything so that if I ever want to return to stock then I can. I have booted into twrp and ran backup and selected all options. Is that how you perform a nandroid backup in twrp or is there more to it?
3. I want to install team venom viper xl rom. Do I have to first flash boot.img first or is the kernel the same in stock and viper xl so that isn't necessary? Do I have to do I factory reset first or what?
I'm still new to this stuff so please bear with me. Thank for all your help!!

ImagioX1 said:
Hey guys I just wanna to check and make sure I'm doing everything right before I flash cause I don't need anymore paperweights
1.I have successfully unlocked my bootloader and installed twrp recovery and rooted.
2. Now I want to back up my entire setup: rom, apps, setting, data, everything so that if I ever want to return to stock then I can. I have booted into twrp and ran backup and selected all options. Is that how you perform a nandroid backup in twrp or is there more to it?
3. I want to install team venom viper xl rom. Do I have to first flash boot.img first or is the kernel the same in stock and viper xl so that isn't necessary? Do I have to do I factory reset first or what?
I'm still new to this stuff so please bear with me. Thank for all your help!!
Click to expand...
Click to collapse
Wipe flash Rom flash boot IMG sit back enjoy

ImagioX1 said:
Hey guys I just wanna to check and make sure I'm doing everything right before I flash cause I don't need anymore paperweights
1.I have successfully unlocked my bootloader and installed twrp recovery and rooted.
2. Now I want to back up my entire setup: rom, apps, setting, data, everything so that if I ever want to return to stock then I can. I have booted into twrp and ran backup and selected all options. Is that how you perform a nandroid backup in twrp or is there more to it?
3. I want to install team venom viper xl rom. Do I have to first flash boot.img first or is the kernel the same in stock and viper xl so that isn't necessary? Do I have to do I factory reset first or what?
I'm still new to this stuff so please bear with me. Thank for all your help!!
Click to expand...
Click to collapse
Different kernel. it is using the 2.41 RUU. So go ahead and flash the boot.img
Here's what you should do for any new ROM with a different kernel.
Wipe System
Factory Reset
Flash boot.img
Flash the ROM
flash gapps (if AOSP based)
reboot and have fun
When doing a nandroid backup, it is only necessary to backup
System
Data
Boot

Ok thanks for your response but I'm still a little confused. First did I back up my current rom properly so that I can return to it later on? Secondly does viper and boot img have to be flashed or can they be installed from sdcard via twrp? If they have to be flashed whats the fastboot command.?

ImagioX1 said:
Ok thanks for your response but I'm still a little confused. First did I back up my current rom properly so that I can return to it later on? Secondly does viper and boot img have to be flashed or can they be installed from sdcard via twrp? If they have to be flashed whats the fastboot command.?
Click to expand...
Click to collapse
You backed up fine, it just takes up a little more space.
You have to extract the boot.img from the ROM and put it in the same folder as fastboot.exe
open command prompt, and navigate to the folder fasboot.exe is in and do the following command
fasboot flash boot boot.img
If it gets stuck at waiting for device, reboot into your bootloader, boot into fastboot from there. and then try again.

ImagioX1 said:
Ok thanks for your response but I'm still a little confused. First did I back up my current rom properly so that I can return to it later on? Secondly does viper and boot img have to be flashed or can they be installed from sdcard via twrp? If they have to be flashed whats the fastboot command.?
Click to expand...
Click to collapse
Viper is the Rom u flash it from twrp it's. azip file that's fkashable so make it easy and flash viper there and than flash the boot IMG from fastboot the command is all over the forums I thinks it fastnoot flash boot.img

don't be confused. read.
you always have to flash boot.img in fastboot "fastboot flash boot boot.img" then flash the zip in twrp make sure to wipe, and don't download international roms. you still have to flash the boot.img from your backed up rom.
like a hundred threads asking the same stuff because no one wants to read

DvineLord said:
don't be confused. read.
you always have to flash boot.img in fastboot "fastboot flash boot boot.img" then flash the zip in twrp make sure to wipe, and don't download international roms. you still have to flash the boot.img from your backed up rom.
like a hundred threads asking the same stuff because no one wants to read
Click to expand...
Click to collapse
I'm sorry but I did read. I saw that if you have the same kernel as that of the rom you're flashing you don't have to flash boot.img. So I asked to see if stock and viper have the same kernel. I don't want to flash anything that will brick my phone.
Now one more question if you don't mind answering. I also saw that you can't downgrade RUU. So if viper is based on 2.41 RUU and stock is 2.20 RUU then will I be able to go stock after flashing viper?
I really do appreciate yalls help. i would be where I am if it weren't for you.

ImagioX1 said:
I'm sorry but I did read. I saw that if you have the same kernel as that of the rom you're flashing you don't have to flash boot.img. So I asked to see if stock and viper have the same kernel. I don't want to flash anything that will brick my phone.
Now one more question if you don't mind answering. I also saw that you can't downgrade RUU. So if viper is based on 2.41 RUU and stock is 2.20 RUU then will I be able to go stock after flashing viper?
I really do appreciate yalls help. i would be where I am if it weren't for you.
Click to expand...
Click to collapse
Yes. Just wipe you system and do a factory reset , and flash the boot.IMG for 2.20 and then flash the Rom.
If you want true stock 2.20 then you will have to relock your bootloader and then run the 2.20 RUU. You would only want to do this if making a warranty claim or something. If you want stock rooted, then yes, do what I said above
Sent from my HTC One XL using xda app-developers app

absolutelygrim said:
Yes. Just wipe you system and do a factory reset , and flash the boot.IMG for 2.20 and then flash the Rom
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Ok got it. I do appreciate your help. Flashing now.

downgrading only refers to the ruu not the zipped roms. so you can't run 1.85 ruu after running 2.20 ruu/ota but you can still flash a rom based on 1.85.
if you are reflashing the same rom you don't have to reflash boot.img but if you are flashing a new rom then you need to flash boot.img. 7-zip will tell you the crc32 of files so you see tell if it's a different checksum.

Viper Xl's great. Seems to be slightly slower than stock on some task, but the lack of bloatware, and the extensive customization is worth it. Haven't found any bugs or nothing so far. If anyones familiar with viperxl though what is the last app in the app drawer? Its got a chinese name? When it loads it says Dolby Surround but all the writing is in chinese?

ImagioX1 said:
Viper Xl's great. Seems to be slightly slower than stock on some task, but the lack of bloatware, and the extensive customization is worth it. Haven't found any bugs or nothing so far. If anyones familiar with viperxl though what is the last app in the app drawer? Its got a chinese name? When it loads it says Dolby Surround but all the writing is in chinese?
Click to expand...
Click to collapse
That's because you flashed the Voodoo mod, it's apart of the mod, theres a chinese part and a english one called "Dolby Digital" or "Dolby Surround"

When I flash ViperXL 3.1.0 JB do I need to flash a radio too? My phone has hboot 1.4 and software 2.2, so I understand that I cant flash radio with hboot 1.4? Does this mean I need to downgrade my hboot/software version?

CrossFire78 said:
When I flash ViperXL 3.1.0 JB do I need to flash a radio too? My phone has hboot 1.4 and software 2.2, so I understand that I cant flash radio with hboot 1.4? Does this mean I need to downgrade my hboot/software version?
Click to expand...
Click to collapse
Most people have good luck w/out flashing another radio.

ronnie498 said:
Most people have good luck w/out flashing another radio.
Click to expand...
Click to collapse
Hmm. Might there be a patch I'm missing out on? I just flashed one file -ViperXL 3.1.0 JB - Android File Host (692MB)
edit- Works now after another reinstall installed boot image first this time.

[Q] Changing Stock kernels

Hi,
I have managed to put on a kernel that's not working. Is there a way to revert back to the original kernel? I do have a nandroid backup, but re-installing that didn't put on the old kernel.
I am using Liquidsmooth ROM. Any help would be appreciated.
Thanks.

if you can boot into the rom use flashimagegui, if not do the normal fastboot the boot.img then do it again with flashimagegui to get the modules.
what kernel did you try to flash? the only kernel that will work with new liquidsmooth is cm10.1_vz-oc-linaro.3.zip. it contains modules, if you aren't s-off then you need to flash boot.img in fastboot then flash again in recovery for the modules.

DvineLord said:
if you can boot into the rom use flashimagegui, if not do the normal fastboot the boot.img then do it again with flashimagegui to get the modules.
what kernel did you try to flash? the only kernel that will work with new liquidsmooth is cm10.1_vz-oc-linaro.3.zip. it contains modules, if you aren't s-off then you need to flash boot.img in fastboot then flash again in recovery for the modules.
Click to expand...
Click to collapse
I did exactly that, presuming that it was working... But I have been facing issues. The phone restarts every once in a while and I have managed to get to this condition after multiple wipes and restoring a backup. Anyways I don't know what the issue is I was just wondering how to revert back to the original kernel.

im running Liquid-JB-v2.1-RC2-evita.zip and cm10.1_vz-oc-linaro.3.zip. there seem to be some general issues with the rom that present as basically glitching and gets worse overtime atleast for me. im pretty sure it isnt related to the kernel. but to revert kernel just load the liquidsmooth zip into flashimagegui and itll pull the needed files, let it wipe cache and dalvik then reboot.

DvineLord said:
im running Liquid-JB-v2.1-RC2-evita.zip and cm10.1_vz-oc-linaro.3.zip. there seem to be some general issues with the rom that present as basically glitching and gets worse overtime atleast for me. im pretty sure it isnt related to the kernel. but to revert kernel just load the liquidsmooth zip into flashimagegui and itll pull the needed files, let it wipe cache and dalvik then reboot.
Click to expand...
Click to collapse
I do not have s-off does the flashimagegui works even without it?

strommer666 said:
I do not have s-off does the flashimagegui works even without it?
Click to expand...
Click to collapse
yes, Flash Image GUI
you should also s-off your phone it will make life ALOT easier and the process is simple take like 2 minutes.

DvineLord said:
yes, Flash Image GUI
you should also s-off your phone it will make life ALOT easier and the process is simple take like 2 minutes.
Click to expand...
Click to collapse
Thanks I'll make sure I do that..

also new stable build of liquidsmooth just got released. you should flash it. imma flash it with a clean full wipe. but you should s-off first so you dont have to flash boot.img separately every rom.

DvineLord said:
also new stable build of liquidsmooth just got released. you should flash it. imma flash it with a clean full wipe. but you should s-off first so you dont have to flash boot.img separately every rom.
Click to expand...
Click to collapse
Ya, I saw the new version wanted to try that which is why I wanted to got to the old kernel version. I had tried installing it with the linaro kernel but it gets stuck on the boot screen.
Update: - I installed the flash gui image, then extracted and installed the kernel , factory reset the phone, then installed the latest liquid smooth build. But it is still not going ahead of the boot animation.
Update 3 :- Got the old kernel back. Did a restore. Working fine now . But still for some reason I cannot install the new ROM yet.

strommer666 said:
Ya, I saw the new version wanted to try that which is why I wanted to got to the old kernel version. I had tried installing it with the linaro kernel but it gets stuck on the boot screen.
Update: - I installed the flash gui image, then extracted and installed the kernel , factory reset the phone, then installed the latest liquid smooth build. But it is still not going ahead of the boot animation.
Update 3 :- Got the old kernel back. Did a restore. Working fine now . But still for some reason I cannot install the new ROM yet.
Click to expand...
Click to collapse
you need everything. you don't need to extract the kernel. just load the whole zip file.

DvineLord said:
you need everything. you don't need to extract the kernel. just load the whole zip file.
Click to expand...
Click to collapse
I did load the full file and the flash gui image extracted the kernel. The thing is I have the kernel now, but still I can't seem to be able to install the new version of the LiquidSmooth build. I am doing a nandroid backup of this thing and try installing it again.

well new liquidsmooth is nice, im using cwm now as recovery since ive had tons of issues with twrp since version 2.2.2.0

[Q] custom recovery needed?

Hello all,
I'm new to Xperia L but not to rooting. I rooted my own HTC sensation and I'm planning to do the same to the Xperia to fix a not working camera and insane battery drain. On the HTC, I needed to flash a custom recovery, update bootloader, update radio before I could install a custom ROM.
Do I need to repeat the same procedure with the XPL? Or just unlock bootloader -> flash ROM done (which is what I'm getting from going through these forums)?

onemanshow85 said:
Hello all,
I'm new to Xperia L but not to rooting. I rooted my own HTC sensation and I'm planning to do the same to the Xperia to fix a not working camera and insane battery drain. On the HTC, I needed to flash a custom recovery, update bootloader, update radio before I could install a custom ROM.
Do I need to repeat the same procedure with the XPL? Or just unlock bootloader -> flash ROM done (which is what I'm getting from going through these forums)?
Click to expand...
Click to collapse
Yep !! Kk roms n many jb roms r pre-rooted..if u dont need backup n stuff then no need to root..unlock bootloader..wic clears internal storage..so unlock>flash kk kernel>rom
Hit thanks if i helped

Rohan purohit said:
Yep !! Kk roms n many jb roms r pre-rooted..if u dont need backup n stuff then no need to root..unlock bootloader..wic clears internal storage..so unlock>flash kk kernel>rom
Hit thanks if i helped
Click to expand...
Click to collapse
thanks
the way I see it now is 2 options:
- first root, and make a TA backuo
or
- unlock, flash recovery (CWM from what I've gathered), flash kernel/ROM.
correct?
Can I backup the stock ROM in CWM if I choose to follow the second option?

onemanshow85 said:
thanks
the way I see it now is 2 options:
- first root, and make a TA backuo
or
- unlock, flash recovery (CWM from what I've gathered), flash kernel/ROM.
correct?
Can I backup the stock ROM in CWM if I choose to follow the second option?
Click to expand...
Click to collapse
I have a 3rd n better option , u can backup everything before unlock as it erases apps n internal sd..so fo this
1)root n thn titanium backup 2)cwm on locked (go to original development) recovery instaler tool
3)nandroid backup
4)unlock
5)flash custom rom..wicever ..just u cnt flash kk rom frm jb recovery
---------- Post added at 07:56 PM ---------- Previous post was at 07:53 PM ----------
onemanshow85 said:
thanks
the way I see it now is 2 options:
- first root, and make a TA backuo
or
- unlock, flash recovery (CWM from what I've gathered), flash kernel/ROM.
correct?
Can I backup the stock ROM in CWM if I choose to follow the second option?
Click to expand...
Click to collapse
I have a 3rd n better option , u can backup everything before unlock as it erases apps n internal sd..so fo this
1)root n thn titanium backup 2)cwm on locked (go to original development) recovery instaler tool
3)nandroid backup
4)unlock
5)flash custom rom..wicever ..just u cnt flash kk rom frm jb recovery
N if u go with ur 2nd option there wont be anything to backup after unlocking..so u cwm on locked bootloader by tht tool
---------- Post added at 07:59 PM ---------- Previous post was at 07:56 PM ----------
onemanshow85 said:
thanks
the way I see it now is 2 options:
- first root, and make a TA backuo
or
- unlock, flash recovery (CWM from what I've gathered), flash kernel/ROM.
correct?
Can I backup the stock ROM in CWM if I choose to follow the second option?
Click to expand...
Click to collapse

Rohan purohit said:
I have a 3rd n better option , u can backup everything before unlock as it erases apps n internal sd..so fo this
1)root n thn titanium backup 2)cwm on locked (go to original development) recovery instaler tool
3)nandroid backup
4)unlock
5)flash custom rom..wicever ..just u cnt flash kk rom frm jb recovery
N if u go with ur 2nd option there wont be anything to backup after unlocking..so u cwm on locked bootloader by tht tool
Click to expand...
Click to collapse
I like that option.
Problem is I can't get this thing rooted, I tried Doomlord Rootkit and the motochopper root method (untill I found out it won't work on 4.2.2)
I know I could just unlock and flash a custom ROM/kernel, but I really want to backup with TA before unlocking (not my own phone) and for that I need full root first.

onemanshow85 said:
I like that option.
Problem is I can't get this thing rooted, I tried Doomlord Rootkit and the motochopper root method (untill I found out it won't work on 4.2.2)
I know I could just unlock and flash a custom ROM/kernel, but I really want to backup with TA before unlocking (not my own phone) and for that I need full root first.
Click to expand...
Click to collapse
There's rooting kit in the general section that works on 4.2.2. Backing up TA partition is always a good idea. I would suggest you to take a full nandroid backup AFTER flashing a custom kernel. There's no need for titanium backup too (I don't understand why the above post mentions that). Now that you have a working recovery and backup, proceed with flashing your rom.
Hope it helps
Hit thanks if it does.

abhi007.john said:
There's rooting kit in the general section that works on 4.2.2. Backing up TA partition is always a good idea. I would suggest you to take a full nandroid backup AFTER flashing a custom kernel. There's no need for titanium backup too (I don't understand why the above post mentions that). Now that you have a working recovery and backup, proceed with flashing your rom.
Hope it helps
Hit thanks if it does.
Click to expand...
Click to collapse
thanks, I managed to get it rooted, TA backup, bootloader unlock and flashed a stock FTF. I'm looking for a kernel that contains the CWM recovery so I can flash some ROMS.

onemanshow85 said:
thanks, I managed to get it rooted, TA backup, bootloader unlock and flashed a stock FTF. I'm looking for a kernel that contains the CWM recovery so I can flash some ROMS.
Click to expand...
Click to collapse
use any custom kernel. use phantom v7 for jellybean, above that are all for kitkat onli. There's a stock kernel with recovery too. And it's really god

abhi007.john said:
use any custom kernel. use phantom v7 for jellybean, above that are all for kitkat onli. There's a stock kernel with recovery too. And it's really god
Click to expand...
Click to collapse
tnx.
One more thing though...it seems I can't get into the recovery by default. The purple LED light doesn't lit up when I boot my phone and I tried wigling the volume buttons during boot multiple times but it just boots regularly. I was on the verge to flash a recovery with a boot.img, from phantom I believe, but I figured I wouldn't before I figure out how to get into the recovery. Supose the ROM won't boot after flashing a new recovery, there's no way for me to enter CWM

onemanshow85 said:
tnx.
One more thing though...it seems I can't get into the recovery by default. The purple LED light doesn't lit up when I boot my phone and I tried wigling the volume buttons during boot multiple times but it just boots regularly. I was on the verge to flash a recovery with a boot.img, from phantom I believe, but I figured I wouldn't before I figure out how to get into the recovery. Supose the ROM won't boot after flashing a new recovery, there's no way for me to enter CWM
Click to expand...
Click to collapse
You cannot enter the recovery by keypress on stock. You'll have to do that via ADB or Gravitybox etc.

Joery360 said:
You cannot enter the recovery by keypress on stock. You'll have to do that via ADB or Gravitybox etc.
Click to expand...
Click to collapse
I see, so the volume button trick is a custom ROM only feature to enter the recovery..? So I gues I would have to flash a custom ROM with recovery included with flashtool. Can someone hoop me up with a ROM like that?
I did some research into this Gravitybox but it sais it requires a working custom recovery, which I lack.

onemanshow85 said:
I see, so the volume button trick is a custom ROM only feature to enter the recovery..? So I gues I would have to flash a custom ROM with recovery included with flashtool. Can someone hoop me up with a ROM like that?
I did some research into this Gravitybox but it sais it requires a working custom recovery, which I lack.
Click to expand...
Click to collapse
Unlock bootloader, download a JB Custom Kernel (Vengeance is a good one), extract boot.img and flash it in fastboot mode with flashtool.

onemanshow85 said:
I see, so the volume button trick is a custom ROM only feature to enter the recovery..? So I gues I would have to flash a custom ROM with recovery included with flashtool. Can someone hoop me up with a ROM like that?
I did some research into this Gravitybox but it sais it requires a working custom recovery, which I lack.
Click to expand...
Click to collapse
It's NOT the ROM. Recovery comes with custom KERNEL. If you're on stock kernel then you won't be able to enter recovery by pressing volume down.
Unlock your bootloader, flash a custom kernel and then you will have a recovery and glowing led on boot. In case your phone doesn't boot( that you cautioned) flash stock FTF using flashtool. It will reset your kernel(which means flash stock kernel, which works anyways).
Hope this helps
Hit thanks if it does.

abhi007.john said:
It's NOT the ROM. Recovery comes with custom KERNEL. If you're on stock kernel then you won't be able to enter recovery by pressing volume down.
Unlock your bootloader, flash a custom kernel and then you will have a recovery and glowing led on boot. In case your phone doesn't boot( that you cautioned) flash stock FTF using flashtool. It will reset your kernel(which means flash stock kernel, which works anyways).
Hope this helps
Hit thanks if it does.
Click to expand...
Click to collapse
ok, got it. thanks.
next problem: I got the CWM working and I was about to flash a custom ROM. the AOSP ROM from Taoshan gave me an error so I wanted to flash a different one. I dowloaded and stored a different ROM+gapps on a different SD card to save some time. Now for some reason, CWM memorizes the content of the combination of the 2 SDcards, and it won't update it's content no matter what SDcard I use. I formatted the SD card and stored the ROM+gapps again, but CWM keeps showing me the content of the old status of the SD card. So I can't select any new zips.
quesiton is, can I fix this somehow OR, can I reflash the boot.img to overwrite the current CWM without any issues? I have no working ROM atm since I already to apply a new one.

onemanshow85 said:
ok, got it. thanks.
next problem: I got the CWM working and I was about to flash a custom ROM. the AOSP ROM from Taoshan gave me an error so I wanted to flash a different one. I dowloaded and stored a different ROM+gapps on a different SD card to save some time. Now for some reason, CWM memorizes the content of the combination of the 2 SDcards, and it won't update it's content no matter what SDcard I use. I formatted the SD card and stored the ROM+gapps again, but CWM keeps showing me the content of the old status of the SD card. So I can't select any new zips.
quesiton is, can I fix this somehow OR, can I reflash the boot.img to overwrite the current CWM without any issues? I have no working ROM atm since I already to apply a new one.
Click to expand...
Click to collapse
Yes, you can flash new kernel anytime. I am not sure what's causing this problem. I wonder if there's any refresh or reload option in CWM or any option to reset/clear CWM data. Look for these options and if you don't find, feel free to flash the kernel again.
Hit thanks if it helped.

abhi007.john said:
Yes, you can flash new kernel anytime. I am not sure what's causing this problem. I wonder if there's any refresh or reload option in CWM or any option to reset/clear CWM data. Look for these options and if you don't find, feel free to flash the kernel again.
Hit thanks if it helped.
Click to expand...
Click to collapse
solved
I was using a JB kernel and trying to flash KK roms. Extracted a kernel from LS 4.4 ROM and flashed it, phone is booted and working fine now.
about the CWM issue, reflashing the same kernel won't solve the it. When I flashed a different kernel, it did do the trick. Seems CWM stores SD partitions in its own memory. I managed to install zips from the SDcard by accesing the external SDcard partition. Haven't seen any refresh or reload options in CWM.
thanks for the help, overall I just had to do some more reading. I'm quite familiar with rooting but I come from a HTC device, which is entirely different imo. (using 4ext recovery there which I personally find a lot more user friendly). Getting accustomed with Sony devices, the rooting and the terminoligy takes some time I guess.

unable to downgrade TWRP

I have ran into a problem and came here for help. I was on Android 5.1.1 and I wanted to try omni and a slimsaber build of omni so I tried to flash with 2.8.7.0 and could not get it to boot, tried for days. So I wanted to try the recommended recovery, 2.8.6.0 and tried through fastboot, flashify and toolkits. And I am unable to change recovery. Fastboot flash results in a loop to the OnePlus Android logo but flashing 2.8.7.0 is a quick fix for that but it's the only recovery I can flash. I have never seen a phone not take a fastboot partiton flash. I have flashed back to stock.. Flashed OOS you name it I tried it. I know others have had this issue but never seen a fix posted. Anyone?

I have a .zip that can be flashed on TWRP v2.8.7.0, so as to get TWRP v2.8.6.0
I'll upload it if you want me to. Thank me later!
~noob (you gotta start from somewhere)

Download the img and when are you on the twrp, change zip to img and will appear the img and it will be possible apply it. Its really simple.

evertking said:
I have ran into a problem and came here for help. I was on Android 5.1.1 and I wanted to try omni and a slimsaber build of omni so I tried to flash with 2.8.7.0 and could not get it to boot, tried for days. So I wanted to try the recommended recovery, 2.8.6.0 and tried through fastboot, flashify and toolkits. And I am unable to change recovery. Fastboot flash results in a loop to the OnePlus Android logo but flashing 2.8.7.0 is a quick fix for that but it's the only recovery I can flash. I have never seen a phone not take a fastboot partiton flash. I have flashed back to stock.. Flashed OOS you name it I tried it. I know others have had this issue but never seen a fix posted. Anyone?
Click to expand...
Click to collapse
To change TWRP version, to upgrade or downgrade, you just have to download the Flashify app from PlayStore and let it do the job in about 10 seconds, without any issue :good:

Did anything work? I'm stuck with the same problem, except on 3.0.2.0 and downgrading out of the question I can't even make any other recovery work!!!
On the OnePlus One, was trying to flash Jgcaap's MM build.

There is no downgrading or upgrading like matters. You can flash any version of twrp via twrp, FIRST GO TO YOUR TWRP AND FLASH 2.8.6 OR 3.0.2 . BOTH HAS FLASH ANY ROMS WITHOUT PROBLEMS.

drmuruga said:
There is no downgrading or upgrading like matters. You can flash any version of twrp via twrp, FIRST GO TO YOUR TWRP AND FLASH 2.8.6 OR 3.0.2 . BOTH HAS FLASH ANY ROMS WITHOUT PROBLEMS.
Click to expand...
Click to collapse
I already tried. -.- Wouldn't ask if I didn't run out of options.
The flash doesn't work, instead my recovery disappears and I reboot to system directly. Facing problems gives you experience, man :| Not a n00b here.
I found a typical kinda work around by trying this and that. Gonna create another thread to ask, now.