I have read the Kindle Fire Beginners Guide and the supplement on reverting to Stock and I read a thread about dual booting between ROM's. So as of now, it appears that you can not dual boot between cm9 and KF stock, while leaving TWRP installed. My question is, can the stock kf os be converted to a ROM that could be used in a dual boot?
MoDoCo can be used as an alternate ROM. It is basicly stock. Unused that and Jellybean 4.1.1 as my primary for quite a while
Sent from my Nexus 7 using xda premium
tobiascuypers said:
MoDoCo can be used as an alternate ROM. It is basicly stock. Unused that and Jellybean 4.1.1 as my primary for quite a while
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Ideally, I am looking for a way to switch between the original Amazon system that can be registered and an android system like CM9, using a boot menu. By the way, I really like your signature.
Related
Hi guys, i have unlocked my bootloader on my galaxy nexus and have rooted it. Upon installing a theme on my Nexus using CWM, i forgotten to back-up. Thus i installed the theme without a rom, basically installing a theme on a stock rom. How Stupid? Now im in bootloop. And all i can do is use FastBoot. Please help, im running on my Mac OSX 10.7 Lion.
Thanks
You seem like you know what to do. Just flash the factory images back with fastboot. They are located in a thread in general called reverting back to stock. Follow the Mac version of the commands. You will lose your SD card data tho.
Sent from my Galaxy Nexus using xda premium
Well, finally decided to make a thread after hours of searching.
I've got a rooted kindle fire, and it's been working fine for the past month. Out of the blue last night, I turn it on, it won't boot past the animated white and orange kindle fire logo. I still get the usual blue logo beforehand, the device is recognized by my pc, i can boot into fastmode, get into TWRP or CWM, I'm just not sure what to do from here.
Most other people with this problem seem to be stuck in fastboot, while i'm not.
Any help would be appreciated.
It sounds like your kindle's current stock rom got messed up
Here's what you should do:
Boot into twrp
Transfer a different rom to your kindle
Wipe what's needed
Flash the new rom
Reboot
Sent from my Kindle Fire using xda premium
if you find something I posted helpful please thank me
joshuabg said:
Transfer a different rom to your kindle
Wipe what's needed
Flash the new rom
Reboot
Click to expand...
Click to collapse
Thanks a bunch for helping identify the problem Any specific rom you'd recommend? CM7 or ICS?
Also, would you be able to link me to a tutorial on what needs to be wiped, as well as how to flash said rom?
If you like stock you can get modaco
Gede rom looks very customizable
I'm on modaco now
Wiping nd flashing depends on the rom
Do you have TWRP or clockwork
I know more of TWRP
Sent from my Kindle Fire using xda premium
if you find something I posted helpful please thank me
I've decided on Energy ICS CM9. Got it ready and waiting.
Oh, and i'm running TWRP
Its on post 1 of the energy rom thread: http://forum.xda-developers.com/showthread.php?t=1528024
Ive never installed this specific rom before so I dont know the exact procedure so follow the one above.
Sent from my Kindle Fire using xda premium
if you find something I posted helpful please thank me
What's the better ics kernel on dinc - I'm running paranoid? Also do you just flash those in cwr? I just came from a locked down motorola device so kernels are a bit dusty on the memory, last time I messed with any was a while back on my old fascinate.
I would suggest some incredikernels for ics.
http://www.incredikernel.com/?page_id=5
wareju said:
What's the better ics kernel on dinc - I'm running paranoid? Also do you just flash those in cwr? I just came from a locked down motorola device so kernels are a bit dusty on the memory, last time I messed with any was a while back on my old fascinate.
Click to expand...
Click to collapse
Yep, just flash them in recovery, any good kernel package like incredikernel will already include its installer script, so it's no different than flashing any other mod. The standard warning about making a nandroid backup first applies, of course.
I agree with ra9b
Sent from my Galaxy Nexus using xda app-developers app
I tried to install that paranoid android rom.I keep getting an error 7. it says no target device found. I've tried 1.9 .4, 1.9 .5, 1.9.6 and now 1.9 .7. It looks like an awesome rom but I can't install it. I get the same error with the cm 10. Presently I'm running the vicious ROM (jellybean). I wipe everything before trying to install the ROM but nothing works. I can install the maguro version with no problems other than I don't have phone service. I want this ROM bad and need some guidance.
Mr. Keith
How are you trying to flash the ROM? In recovery?
Sent from my Nexus 7 using xda premium
El Daddy said:
How are you trying to flash the ROM? In recovery?
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Yes, clockwork mod. I've also tried to manually do it in recovery, still get the status 7 error. I tried the supersu mod, no success. I have the Verizon gnex. This is week 2 of failed attempts. Do I have to start with a stock rom first?
Hope you are getting roms from Verizon thread not i9250
atifsh said:
Hope you are getting roms from Verizon thread not i9250
Click to expand...
Click to collapse
This.
The reason why you didn't have service with a maguro ROM is because that is for the gsm version.
You want the toro builds. Hopefully you can get your radio back.
if not you'll have to flash the stock Google image.
Sent from my Nexus 7 using xda premium
If you mean status 7 error, I have that with my Vibrant and have to change to a different version of clockworkmod. Try flashing an older version of CWM in fastboot.
eksasol said:
If you mean status 7 error, I have that with my Vibrant and have to change to a different version of clockworkmod. Try flashing an older version of CWM in fastboot.
Click to expand...
Click to collapse
This is likely the OP's issue. There are just too many incompatibilities with the newer recoveries. If you stick with 5.5.0.2 (for maguro), and 5.5.0.4 (for toro), you will see that you will have significantly less issues...
I have a Verizon galaxy nexus with paranoid rom all you do is go back to stick ics and use recovery to flash and it might get stuck in boot screen just take out battery and put back in and should just start up
Sent from my Galaxy Nexus using xda app-developers app
Sucess!!
Thank you, thank you, all of you. I finally installed the rom last night and its truly awesome. I didn't know that rom manager allows you to revert to older cwm versions. That did the trick. I now have some catching up to do.
Thanks again,
Mr. Keith
I just want to change my kernel to Trinity to increase battery life and root my nexus because some apps requires root permission but don't want to change my stock jelly bean 4.2
Is it possible? If yes how?
Please reply
I am new to android and have never rooted my nexus nor unlocked my boot loader
I did tried to search xda forum but all the post have mentioned about rooting with custom recovery
I don't want custom recovery
please help
Sent from my Galaxy Nexus using xda premium
Sent from my Galaxy Nexus using xda premium
Follow this guide.
It will involve setting up fastboot and adb (won't take long at all). Then instead of flashing a custom recovery, you can boot into it, flash the superSU zip found in the second link and when you reboot you will be rooted, with stock recovery.
http://forum.xda-developers.com/showthread.php?t=1830108
http://forum.xda-developers.com/showthread.php?t=1538053
Hope it helps.
Thanks for the quick reply
Will that change my kernel to Trinity or can you suggest any good kernel for increasing battery life?
From what I have searched on threads Trinity seems to be the best when it comes to getting max screen on time
So can you provide any link of for changing the kernel to any battery saving kernel like Trinity and still be on stock jelly bean?
Sent from my Galaxy Nexus using xda premium
Mmm, flashing a custom kernel will require a custom recovery I'm afraid, there's no way around that.
You could however do the same thing as you will do to get root (fastboot boot, not flash a custom recovery) and then flash the kernel, but you would have to do that every time you update the kernel as well.
My recommendation is that if you want to flash custom kernels, flash the latest TWRP recovery (2.3.2.1 I think) and do it that way.
For any questions about Trinity, just ask in the thread, I check it often, but people will be happy to help you there, they're an awesome bunch.
Also I would highly recommend Trinity, I've used it a lot. At the moment though I am using stock, rooted 4.2 while the devs start playing around with the new source. Once it's more stable I am sure I'll be back on it though.
Sent from my Galaxy Nexus using Tapatalk 2