Database Users

[Q] K1 rooted 14_14 ROM

Hi
To be able to bypass the process of a flash to v13_13, open the backdoor, flash to 14_14 etc. can anyone point me to a rooted 14_14 rom?
In particular "K1_A301_14_14_120109_US"
Thanks

http://rootzwiki.com/topic/13407-alpha-ideapad-k1-cwm-stock-rooted-rom-120109-build/
Although still in the alpha stage, I switched from using timmydean's rom to this one specifically so I could successfully run the 14_14 rom and keep my root. Nothing against timmydean and his work, this just worked easier and faster. Also this rom add cwm which is the only rom out currently that does this for the k1, from what I've seen.
Just reemeber that this is still just an alpha, so be sure to read the post fully. Hope this helps!

Thanks for posting the link Dueces99. I compiled the CWM and ROM that Deuces99 linked to. I just wanted to add that there is nothing alpha about the ROM, just CWM. The ROM is stock and rooted and has no bugs (Other than the ones the stock ROM has).
The reason I left the Alpha status is because backup/restore don't work in CWM, and there is currently no key combination to boot into recovery. You must boot to recovery using the included app/widget

Right, there is no physical key combo. associated to booting into Recovery, the rom atleast provides the means to boot into recovery (widget/app) which atleast leaves the option. I personally, have not had any issues at all with this rom, and love the fact that all the bloatware misc. 3rd party apps and some Lenovo apps were removed, which made the rom seem that much more responsive upon first boot IMO.
Glad to hear that was of some help to you, kinda surprised there hasnt been anyother spinoff roms from this, regardless of its released stage. Just how cut and dry it is with flashing the 2nd newest update with root, then simply flashing the 14_14 update through CWM and keeping root. That was my biggest hurdle following timmydean's guide (and still is) was keeping root once taking the update from Lenovo.
Just my 0.02

so all i need is to flash alpha 3 and latest update 120109 in order to be on a rooted 14_14 build? can someone confirm?
Sent from my K1 using xda premium

prfstrkr said:
so all i need is to flash alpha 3 and latest update 120109 in order to be on a rooted 14_14 build? can someone confirm?
Sent from my K1 using xda premium
Click to expand...
Click to collapse
Correct. After that you will be up to date and rooted.

Right, confirming with khanning88 flashing alpha 3 would be the 13_13 update. After flashing that, reboot into recovery via the Reboot Recovery app/widget included in the ROM, follow the instructions from there provided by the rootzwiki post and you'll be good to go with the latest 14_14 update. By far, the most cut-n-dry rooted ROM out there as far as I know. IMHO kinda deceiving that the ROM is listed as an Alpha (for CWM understandably) only because it's been extremely stable for me with nada one FC.
Wierd how an alpha build ROM is more stable than the OS that the K1 comes with...

Dueces99 said:
Wierd how an alpha build ROM is more stable than the OS that the K1 comes with...
Click to expand...
Click to collapse
From what I understand, it's the same firmware as the stock Lenovo, so maybe a little bit of a placebo effect? The CWM ROM does take out all the built-in non-Google apps, so maybe that has something to do with it.
I hope Lenovo gets its act together and shares out the proper source code so that some good samaritan out there can build a stock Android ROM to run on the K1. I've been using it a bit on the 14_14 CWM firmware, and it's still not as good as the firmware I've experienced on the ASUS Transformer TF101 or the Acer Iconia A500. The biggest issue I've found with the Lenovo firmware is that there is a lag closing out of apps and going back to the launcher, sometimes to the point that a forceclose-wait window pops up. I've not experienced that on the Honeycomb ROMs of any of those other two devices, so I wonder if it's because of Lenovo's customizations to Honeycomb, like the ability to close apps from the multitasking sidebar. In that case, maybe a more vanilla version of Honeycomb won't have that problem. Don't get me wrong; I think it's a great feature that Lenovo added to the taskswitcher. But I'd rather not have it than have the operating system lag. I trust Android's memory management enough to not really need to go manually closing apps.

Right, im sure all the bloatware taken out from Lenovo had to have some effect on overall performance. As far as stability between the two, maybe I meant to say "Wierd how an alpha build ROM feels more stable than the OS that the K1 comes with..."
But placebo effect or not, I've experienced zero issues with this rom even though I probably don't do near as much as other K1 owners with their tab. Lenovo does need to fix this, or preferably just provide full source to all...

khanning88 said:
Correct. After that you will be up to date and rooted.
Click to expand...
Click to collapse
Thank you so much! I am finally rooted with 14_14 with all the bloatware removed

prfstrkr said:
Thank you so much! I am finally rooted with 14_14 with all the bloatware removed
Click to expand...
Click to collapse
Welcome, glad you like it.
P.S. I should have an update ready in a couple of days....... and this one is a BIG update

I'm glad I remembered to check back on my thread!
I'll be a rooting tomorrow morning
Thanks Dueces99

omg ... plz tell me it's ICS
Sent from my Xoom using xda premium

khanning88 said:
Welcome, glad you like it.
P.S. I should have an update ready in a couple of days....... and this one is a BIG update
Click to expand...
Click to collapse
Thank you so much, khanning, for all of your efforts. As I mentioned in this thread http://forums.lenovo.com/t5/IdeaPad-Slate-Tablets/K1-not-booting-after-update/td-p/548285 , your CWM firmware is the only effective workaround at the moment for those of us whose K1's are inexplicably locking up with "unrecoverable bootloader" errors to get onto the latest firmware.
We still aren't completely out of the woods though. In post 44 of your rootzwiki thread http://rootzwiki.com/topic/13407-al...-120109-build/page__view__findpost__p__390175 and post 47 http://rootzwiki.com/topic/13407-al...-120109-build/page__view__findpost__p__392343 , the users kennethrkennedy and aig787 both confirm that the "unrecoverable bootloader error" can still come back with updates, even through your CWM recovery. With your Alpha3 and your 120109.zip update, you managed to avoid updating whatever it is that causes the "unrecoverable bootloader error." This is my long rambling plea that, whatever you did there, you will continue to do for the latest update you are working on, so that those of us with these K1's that are prone to the "unrecoverable bootloader errors" can join the fun too. Thanks!

Is updated bootloader needed

Hey guys what's up sorry I'm sure there are other threads about this but I haven't been able to find one to answer me directly....is the updated ics sandwich boot loader necessary I was able to flash flexreapers and lightspeed's ics custom rooms without it? So is it really needed does it make it faster update cmw or just allow recovery boot menu and dual boot I'm at a lost on weather its neccesary or not thanks once again

It will be soon, alot of the developers, including Civato, have said they are going to stop development for the HC bootloader. It does significantly improve performance and eliminates most of the glitches on ICS.

And it will make life easier in the future - upgrading the bootloader, etc. straight from CWM among others.

strongergravity said:
And it will make life easier in the future - upgrading the bootloader, etc. straight from CWM among others.
Click to expand...
Click to collapse
cruise350 said:
It will be soon, alot of the developers, including Civato, have said they are going to stop development for the HC bootloader. It does significantly improve performance and eliminates most of the glitches on ICS.
Click to expand...
Click to collapse
Alright sweet +thanks ;-) I'll update it later then

gears177 said:
Alright sweet +thanks ;-) I'll update it later then
Click to expand...
Click to collapse
Just stick with whatever custom recovery that is provided with the package you
use...not all features in all recoveries are yet supported.
some are meant only for certain BL's for instance HC3.2 and TWRP
from v4 BL on you are able to flash a zip thru recovery and more fastboot commands are available.
You need to read the change logs for each version as things are being added with each new release.
One thing i am certain of and that is if you are having ANY weird issues, sod, wifi OFF, nvflash issues then what seems to settle everything down is a rollback to HC - I think alot of us myself included, never flashed the right thing at the right time when first upgrading to ICS (and at some future point ending up with a "freakenstein" not one thing or the other and not working all that well either) when you start running a "compatible system" i.e kernel, bootloader, recovery, rom all working as they should, then things look and work a whole heccuvalot better!!!

I will not support HC bootloader for the Overclocking kernel for ICS.
To much problems. So expect no OC support for my rom if you stay on HC bootloader.

Stock JB unlock and custom recovery considerations

First of all, I like to share I am not a stranger with rooting, flashing, granting bootloader access (not an tablets, but on HTC an SE WM phones in the past (assuming the S-off/S-on switching is somewhat comparable)). Despite not being a stranger, I am no whizzkid either, it's just that I am able to read instructions well, re-read them and carefully follow the instructions step by step. During the process I have reasonable understanding of what I am doing, but I am not someone that could have 'invented' such workflows and adjustments myself.
So, what is new for me? Installing a custom recovery. I haven't done that before. No problem, because I know there are enough techs on XDA that have the great quality to share their knowledge, something I appreciate very much and use regularly.
My story:
Asus created a situation in which you have to register your device and actively decline your warranty, whenever you want to unlock the bootloader. This is why I didn't do that yet. Now, having my TF300 for almost 6 months, reasonably comfortable with the feeling there will be no issues to need the warranty, I am willing to unlock my bootloader and void my warranty. However, shortly after the JB OTA I read a lot of messages that this was not possible with a TF300 on JB. Later I read it might be possible, but that changing the bootloader was not possible. Then I read this was possible too, but you could only install roms based on official Asus JB OTA.
Well... I guess things have evolved since the initial JB OTA, but I am not sure that I understood things well enough to just give it a try (yet). So I am looking for confirmation and a bit more in depth info. First I will summarize my TF300's history in detail and things I found so far regarding custom recovery. In this way you know what the situation is and I also hope this post becomes 'informative' for other TF300 owners too, besides being a question topic for me only.
Ok, what do I have:
- An original TF300T (no dock), bought in June 2012 with stock ICS
- Granted myself root access via 1-Click Transformer Root
- All original Asus OTA's applied, including the upgrade to JB (and succeeding OTA's)
- Still have root (kept root during all OTA's, including upgrade to JB with help from Voodoo OTA rootkeeper)
- Recently wiped/factory reset my device (still have root)
What I used in the past, but currently not running on the tablet:
- Used different Custom build.props on ICS and JB, but now have stock build.prop again
- Used SwitchMe profile manager (still want it, but waiting on decision to possibly unlock/install custom recovery first)
- Used browser2ram (don't want to need it anymore, but ability to boost performance with a custom rom will be a requirement)
What custom recovery options did I see? There are 3 of them and all seem to be safe with the TF300 JB OTA:
- TWRP 2.3.1.0
- CWM 6.0.1.3 / 5.5.0.4 (don't know why it has 2 version numbers... ICS and JB version?)
- Clockworkmod 6.0.1.4 Touch (same as CWM 6.0.1.3 but with touch functionality?)
Ok, what do I want confirmed to be sure enough to give it a shot on my TF300 without bricking?
- Is it possible to use official Asus unlock tool on a stock OTA JB TF300? If possible:
- Are above mentioned custom recovery options indeed safe to run on a (unlocked) stock OTA JB TF300? If safe:
- What is (technical) the best custom recovery option? Or are the mentioned options mostly identical and is it a matter of personal preference?
- Can I run any roms after installing a custom recovery or am I restricted to roms based on official Asus JB?
- What will happen with root access after (if possible) installing a custom recovery? And after installing a custom rom?
These are my major 'need to knows' before I dare....
Besides this information, I am curious if someone can confirm my representation of (or explain) the different parts in Android/Asus installation and how it is affected by a custom recovery. During reading along the forums, I have created this visualization of the different parts of the system:
1. Bootloader or kernel (first thing on system, somewhat comparable with a PC BIOS? Are the terms bootloader and kernel interchangeable?)
2. Asus recovery/boot options or custom recovery (custom recovery replace the standard Asus recovery/boot options, I assume)
3. Android (stock JB/ICS or custom rom)
Is this a correct representation?
Well, that was all... Hopefully my post didn't become a TLDR and some of you are willing to help me out. I am very thankful in advance!

1. Bootloader is something else then a kernel. You just have to have the right kernel for the 2 different bootloader
2. Boot options are in the bootloader. Stock Recovery has no options.
3. dont understand your question
1st if you are still on ICS I would recommend to use NVflash and create the needed NVflash files. After that your tablet is nearly unbrickable and you are able to NVflash back to the ICS bootloader (my opinion not so importent anymore, caus even CM is now compatible with the JB Bootloader)
2nd If you are still on ICS I would use the unlock app on ICS not on JB and would then flash the JB update.
The Custom Recovery is best right now would be TWRP 2.2. Its the only one with no known issues.
Hope that helps a little and hope that my explanations are correct, because I am just a flasher like you
Last but not least. The best ROMs out there in my opinion are the Clean Rom 2.5 for the TF700 with clemsyns Kernel and BlueAndroid V.1.0.

Thank you for your reply, it helps me a bit. Unfortunately it doesn't answer my major questions, but I don't blame you (not at all). Every bit of help is welcome.
mikaole said:
1. Bootloader is something else then a kernel. You just have to have the right kernel for the 2 different bootloader
Click to expand...
Click to collapse
Ok... clear... but then.. what is a kernel...? (*feeling noob*)
mikaole said:
2. Boot options are in the bootloader. Stock Recovery has no options.
Click to expand...
Click to collapse
Ok, so what happens if I install a custom recovery? Does it replace the bootloader with a different one that includes recovery options? Or does it add recovery options to the existing bootloader?
mikaole said:
3. dont understand your question
Click to expand...
Click to collapse
The numbers (1, 2 and 3) were the 'layers' I imagined on how Android is build up from boot to OS, where 3 being the final layer (Android OS presented to the user on screen).
mikaole said:
1st if you are still on ICS I would recommend to use NVflash and create the needed NVflash files. After that your tablet is nearly unbrickable and you are able to NVflash back to the ICS bootloader (my opinion not so importent anymore, caus even CM is now compatible with the JB Bootloader)
2nd If you are still on ICS I would use the unlock app on ICS not on JB and would then flash the JB update.
Click to expand...
Click to collapse
That's the point why I started this topic, I am on (stock OTA) JB already. If I was still on ICS, I would have had the guts to unlock and install custom recovery. I am hesitating because I read about issues with JB and unlocking/installing custom recovery.
mikaole said:
The Custom Recovery is best right now would be TWRP 2.2. Its the only one with no known issues.
Click to expand...
Click to collapse
Thanks for the tip, I will keep this in mind.
mikaole said:
Hope that helps a little and hope that my explanations are correct, because I am just a flasher like you
Click to expand...
Click to collapse
*shakes hands* Yes, it helped a bit.
mikaole said:
Last but not least. The best ROMs out there in my opinion are the Clean Rom 2.5 for the TF700 with clemsyns Kernel and BlueAndroid V.1.0.
Click to expand...
Click to collapse
Thank you, I will consider this when I am ready to search for custom roms.
@all: Is there someone out there that can (and is willing to) answer my 'major' questions? I will re-post them below:
Ok, what do I want confirmed to be sure enough to give it a shot on my TF300 without bricking?
- Is it possible to use official Asus unlock tool on a stock OTA JB TF300? If possible:
- Are above mentioned custom recovery options indeed safe to run on a (unlocked) stock OTA JB TF300? If safe:
- What is (technical) the best custom recovery option? Or are the mentioned options mostly identical and is it a matter of personal preference?
- Can I run any roms after installing a custom recovery or am I restricted to roms based on official Asus JB?
- What will happen with root access after (if possible) installing a custom recovery? And after installing a custom rom?

Ok, what do I want confirmed to be sure enough to give it a shot on my TF300 without bricking?
- Is it possible to use official Asus unlock tool on a stock OTA JB TF300? If possible:
- Are above mentioned custom recovery options indeed safe to run on a (unlocked) stock OTA JB TF300? If safe:
- What is (technical) the best custom recovery option? Or are the mentioned options mostly identical and is it a matter of personal preference?
- Can I run any roms after installing a custom recovery or am I restricted to roms based on official Asus JB?
- What will happen with root access after (if possible) installing a custom recovery? And after installing a custom rom?
Yes the unlock tool works on JB as well as ICS. I used it while on JB.
Recovery choose one for JB since you have said you were on JB. In fact that is how you will determine which roms you can use as well (JB).
There have been many complaints posted about problems with CWM on this device.
Safe is something I can't answer - twrp itself appears to be safe but that is relative.
One mistake can usually be overcome (or one weird issue); add a mistake to that and you are out at two strikes with this unit most of the time. That is the way I see it after reading hundreds of posts.
You must have recovery, adb, or fastboot working to recover from a problem with this unit.
Before you make any changes make sure adb and fastboot work.
When you flash a rom make sure early in the game you turn on usb debugging in developer options. Learn to get into and use the bootloader menu for adb, fastboot, and recovery access. This would be with both stock recovery and twrp.
Custom roms are usually by default rooted. With a custom recovery you can flash root at will.
It is long but I feel I touched on each of your questions, if not ask.

If your phone is a ferrari, the kernel is the "driver" ... the kernel you use can be tweaked to allow you to overclock your process. By default, overclocking is not possible (usually) on stock kernels because phone makers don't want you effing up your phone.
Other kernels can let you run "low voltage" or "ultra low voltage" settings for the processor. This allows you to send less power to the processor but still get the same amount of oomph out. The result is greater battery life, and no cost to performance. Obviously this can be dangerous to some hardware... so be careful and know what you're doing. It can be as bad as damaging hardware, or as minor as getting your phone stuck in a boot loop. DO A BACKUP with Rom Manager before installing a kernel. Always do a backup before you do anything to your phone.

moisaal said:
If your phone is a ferrari, the kernel is the "driver" ... the kernel you use can be tweaked to allow you to overclock your process. By default, overclocking is not possible (usually) on stock kernels because phone makers don't want you effing up your phone.
Other kernels can let you run "low voltage" or "ultra low voltage" settings for the processor. This allows you to send less power to the processor but still get the same amount of oomph out. The result is greater battery life, and no cost to performance. Obviously this can be dangerous to some hardware... so be careful and know what you're doing. It can be as bad as damaging hardware, or as minor as getting your phone stuck in a boot loop. DO A BACKUP with Rom Manager before installing a kernel. Always do a backup before you do anything to your phone.
Click to expand...
Click to collapse
+1

tobdaryl said:
Ok, what do I want confirmed to be sure enough to give it a shot on my TF300 without bricking?
- Is it possible to use official Asus unlock tool on a stock OTA JB TF300? If possible:
- Are above mentioned custom recovery options indeed safe to run on a (unlocked) stock OTA JB TF300? If safe:
- What is (technical) the best custom recovery option? Or are the mentioned options mostly identical and is it a matter of personal preference?
- Can I run any roms after installing a custom recovery or am I restricted to roms based on official Asus JB?
- What will happen with root access after (if possible) installing a custom recovery? And after installing a custom rom?
Yes the unlock tool works on JB as well as ICS. I used it while on JB.
Recovery choose one for JB since you have said you were on JB. In fact that is how you will determine which roms you can use as well (JB).
There have been many complaints posted about problems with CWM on this device.
Safe is something I can't answer - twrp itself appears to be safe but that is relative.
One mistake can usually be overcome (or one weird issue); add a mistake to that and you are out at two strikes with this unit most of the time. That is the way I see it after reading hundreds of posts.
You must have recovery, adb, or fastboot working to recover from a problem with this unit.
Before you make any changes make sure adb and fastboot work.
When you flash a rom make sure early in the game you turn on usb debugging in developer options. Learn to get into and use the bootloader menu for adb, fastboot, and recovery access. This would be with both stock recovery and twrp.
Custom roms are usually by default rooted. With a custom recovery you can flash root at will.
It is long but I feel I touched on each of your questions, if not ask.
Click to expand...
Click to collapse
Thank you for this clear answer. Allow me to summarize your answer (actually it is a confirmation request to see if I fully understand your answer):
- Asus unlock tool is working fine on JB, no problems
- Since my TF300 is on JB and to stay on the safe side (no guaranties) your advice is to use TWRP 2.3.1.0 for JB (to use the JB version is obvious for me, thanks for confirming)
- Once these steps are done (unlock and custom recovery) , I can flash roms at will, but have to keep in mind to use JB-based roms
Did I summarize (and thus understand) your answer correct?
Thanks for pointing out to have adb and fastboot working before making changes and to learn to get into and use bootloader menu for adb, fastboot and recovery access (with both stock recovery and twrp). I am very much aware of this, but it is always wise to make that clear to anyone whom wants to play with this stuff.
You helped me very much! To be complete sure, I'll wait for confirmation, but then I have more than enough confidence to give it a go (Yes, I will beware it won't exaggerate into over-confidence and I become sloppy . I'll stay punctual and cautious during the process.).

moisaal said:
If your phone is a ferrari, the kernel is the "driver" ... the kernel you use can be tweaked to allow you to overclock your process. By default, overclocking is not possible (usually) on stock kernels because phone makers don't want you effing up your phone.
Click to expand...
Click to collapse
Can I see the kernel somewhat equal to the bios on a pc, or is that a misinterpretation?
If I understood it correct, then it is not fully comparable to a pc bios, as on Android the kernel also determines which version of Android is able to run on your device (ICS needs another kernel than JB), right?

ralph075 said:
Can I see the kernel somewhat equal to the bios on a pc, or is that a misinterpretation?
Click to expand...
Click to collapse
BIOS (basic input-output system, or something along those lines) is loaded before the kernel! They are different. The kernel acts as a mediator between hardware and software.
Trimis de pe Motorola Defy

vap_66 said:
BIOS (basic input-output system, or something along those lines) is loaded before the kernel! They are different. The kernel acts as a mediator between hardware and software.
Click to expand...
Click to collapse
Thanks for clarifying. I found this article and read it to learn more... (I had a few questions again, but realized that there probably would be something to read in here that could answer those questions too... )

Did I summarize (and thus understand) your answer correct?
Yes that is correct.

tobdaryl said:
Did I summarize (and thus understand) your answer correct?
Yes that is correct.
Click to expand...
Click to collapse
Thanks again, now the challenge is to find some spare time this weekend

ralph075 said:
Thanks again, now the challenge is to find some spare time this weekend
Click to expand...
Click to collapse
Good Luck!
Go slow and enjoy your new tab.

tobdaryl said:
Good Luck!
Go slow and enjoy your new tab.
Click to expand...
Click to collapse
Thank you. Well, slow it will go, as last weekend didn't have any spare time...
Hopefully I will experience my new tab soon...

ralph075 said:
Thank you. Well, slow it will go, as last weekend didn't have any spare time...
Hopefully I will experience my new tab soon...
Click to expand...
Click to collapse
You're very welcome.
Yes, it seems time to play is sporadic and limited.
Life would probably be very boring if we always had time.

[Q] TWRP = only flash roms that are based on the Asus OTA?

I've had my TF300 for a few weeks now and am disappointed with the sluggishness of the offical JB ROM when compared to my GS2 on AOKP or even my wife's Tablet S with stock ICS. I'd like to try some of the modified official ROMs or CM10.
After searching these forums for a while and reading the various guides, it seems like the easiest way to unlock and root the tablet is to use the Asus unlocker apk then use fastboot to install TWRP. When I downloaded TWRP I noticed it said:
"If you have taken the official Asus Jellybean OTA then be sure to install the '-JB' version of the recovery for your device - and only flash roms that are based on the Asus OTA."
Does this really mean I'm restricted to ROMs based on the official JB? If I go with CWM will I be able to install any ROM? Am I stuck no matter what because I already have the OTA JB? Thanks for the help if anyone can answer, I just couldn't cobble together a clear answer from the threads I read.

You can flash any Rom you like with Twrp. You just have to dl the right version for the bootloader.
I am using Twrp from the beginning and never had any problems with it.

mikaole said:
You can flash any Rom you like with Twrp. You just have to dl the right version for the bootloader.
I am using Twrp from the beginning and never had any problems with it.
Click to expand...
Click to collapse
Thanks for the reply. So is the caution on the TWRP site just superfluous? I have to admit that it makes me nervous going forward.

It means you need to flash roms that support the JB bootloader. So no ICS roms.
there are a few CM roms that are based on JB that will flash fine. Just today I tried 2 CM roms and one hybrid CM+AOKP port on my TF300t that was running the OTA JB update (unlocked and TWRP'd).

Just be for sure anything you flash says for JB bootloader. There are a few 4.1 cm based roms for the old ics bootloader. The warning you saw on the website is just trying to warn because so many people just flash **** without reading.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

Got it. Thanks guys.
I'll be unlocking and putting TWRP on tonight to see what kind of ROM I like. Appreciate the clarification.

hfeigel said:
Got it. Thanks guys.
I'll be unlocking and putting TWRP on tonight to see what kind of ROM I like. Appreciate the clarification.
Click to expand...
Click to collapse
Care to make a how-to video? Joking of course... Just bemoaning my incompetence... I get the Asus bootloader apk, and I know how to flash roms using twrp (I have used it for about a year on my S2 and S3) but from what I read, installing twrp on the tf300 looks more challenging than on my phone. I will keep searching, but I may be forced to throw on my flame suit and start a thread if I cant get this resolved soon! :laugh:

go the the video thread and look for the video titled
"How to Flash ClockWorksMod Recovery + ROOT ( Works on ALL Fimrware )"
just use the twrp.blob instead of the CM one and you're good to go.

[Q] Help With JB Energy™ Rom

Just recently flashed a friend's phone with Energy Rom. The rom looks amazing and is very well designed. There are just a few issues that he is having and I have not seen anyone else experience these problems in the tread. (Too few posts to post there)
Her camera is not working and I guess her Hotspot gave her a "timed out" message. . . . If anyone else has experienced this, please let me know if you were able to resolve this and how.
Thanks!

marcusw3 said:
Just recently flashed a friend's phone with Energy Rom. The rom looks amazing and is very well designed. There are just a few issues that he is having and I have not seen anyone else experience these problems in the tread. (Too few posts to post there)
Her camera is not working and I guess her Hotspot gave her a "timed out" message. . . . If anyone else has experienced this, please let me know if you were able to resolve this and how.
Thanks!
Click to expand...
Click to collapse
Are you on the 4.1.2 update? If so you will need to flash back down to 4.1.1 kernel because the new kernel is not compatible with the 4.1.1 camera
Sent from my XT907 using Tapatalk 2

marcusw3 said:
Just recently flashed a friend's phone with Energy Rom. The rom looks amazing and is very well designed. There are just a few issues that he is having and I have not seen anyone else experience these problems in the tread. (Too few posts to post there)
Her camera is not working and I guess her Hotspot gave her a "timed out" message. . . . If anyone else has experienced this, please let me know if you were able to resolve this and how.
Thanks!
Click to expand...
Click to collapse
Energy ROM is based off of the the 4.1.1 build, the latest update has the XT907 at 4.1.2. So if her phone was previously on 4.1.2, then flashing this ROM could cause problems as the previous poster mentioned due to the new kernel. Not sure if the developer will update his ROM any time soon (which I loved by the way, and keep checking his thread for any updates),
also, Energy ROM can only be installed via SS right now, and given that the bootloader has been unlocked, I believe that all ROMs will be flashable via TWRP/CWM going forward - thus making SS obsolete for the XT907.
Here's what I suggest though:
unlock bootloader
install TWRP recovery
try out the DeadRage ROM, which is based on the 4.1.2 build: http://www.droidrzr.com/index.php/topic/17778-romretail-deadrage-v12a-05092013-412-base/
if you really want to stick with Energy ROM with working camera, then you still can:
flash back to stock (4.1.1)
root
install SS
unlock bootloader
install TWRP
install Energy ROM on Slot 1
backup Energy ROM via SS
move Energy ROM to stock slot via SS
backup Energy ROM via TWRP (basically making a nandroid, and this can be installed going forward as a backup)
uninstall SS

Thanks!
jco23 said:
Energy ROM is based off of the the 4.1.1 build, the latest update has the XT907 at 4.1.2. So if her phone was previously on 4.1.2, then flashing this ROM could cause problems as the previous poster mentioned due to the new kernel. Not sure if the developer will update his ROM any time soon (which I loved by the way, and keep checking his thread for any updates),
also, Energy ROM can only be installed via SS right now, and given that the bootloader has been unlocked, I believe that all ROMs will be flashable via TWRP/CWM going forward - thus making SS obsolete for the XT907.
Here's what I suggest though:
unlock bootloader
install TWRP recovery
try out the DeadRage ROM, which is based on the 4.1.2 build:
if you really want to stick with Energy ROM with working camera, then you still can:
flash back to stock (4.1.1)
root
install SS
unlock bootloader
install TWRP
install Energy ROM on Slot 1
backup Energy ROM via SS
move Energy ROM to stock slot via SS
backup Energy ROM via TWRP (basically making a nandroid, and this can be installed going forward as a backup)
uninstall SS
Click to expand...
Click to collapse
I will give the first suggestion a reply, if that does not work, the second. I will keep you all posted on results. Thank you!

Kernel?
Any clue of where I can find just the kernel I need to download and flash?
Sorry for coming across as a newbie, but I am used to other phones that have a bit larger of a community. Thanks again.

marcusw3 said:
Any clue of where I can find just the kernel I need to download and flash?
Sorry for coming across as a newbie, but I am used to other phones that have a bit larger of a community. Thanks again.
Click to expand...
Click to collapse
no worries - we all were newbies at some point in time.
I have not seen a thread dedicated to the stock 4.1.1 kernel, but I did find this:
http://forum.xda-developers.com/showthread.php?t=2017200
my advice at this point is to backup your apps/data via TiBu (and then copy that backup folder to your mnt/external1 directory).
so that way, after you pick your ROM, you can re-download your apps from the market (I always recommend doing this as opposed to letting TiBu restore them), then you can use TiBu to restore data ONLY from your apps. I do NOT recommend restore system data though when switching ROMs (however, I do restore WiFi settings and bluetooth pairings).
hope this helps.

All worked out great! I appreciate the help. I ended going with Energy 4.1.1 I have that stupid grateful dead image stuck on first power up due to rage. -Annoying!!

marcusw3 said:
All worked out great! I appreciate the help. I ended going with Energy 4.1.1 I have that stupid grateful dead image stuck on first power up due to rage. -Annoying!!
Click to expand...
Click to collapse
anytime - see this thread regarding the boot logo:
http://www.droidrzr.com/index.php/topic/17708-boot-logos-request-for-custom-one-here/