I have been flashing ROMs on my Kindle since the days of GB and ICS. I went away for a year and just got back early this month so I lost much time regarding all the updates. I did upgrade TWRP from 2.5.x to the latest 2.7.x and all works fine. I'm currently on twa_priv's CM10.2 and satisfied. I also have the Kindle set up to dual boot with either CM10.2 or the alt-ROM which is a CM7 build.
Anyways, my main question is how would having the Kindle set up for dual booting affect the process of the OtterX installation? Please forgive my ignorance lol. I really like the ability to dual between the to OS version extremes. Could someone please at least point me in the right direction? Thanks!
Related
Now that we have an ICS build to play with (see dev thread here), has anyone tried using Boot Manager with it?
In theory it shouldn't matter what version of Android is being installed, but before I buy it I want to make sure it'll be at least a semi-painless process switching between everyday-use GB and testing-for-fun ICS.
spitzaf said:
Now that we have an ICS build to play with (see dev thread here), has anyone tried using Boot Manager with it?
In theory it shouldn't matter what version of Android is being installed, but before I buy it I want to make sure it'll be at least a semi-painless process switching between everyday-use GB and testing-for-fun ICS.
Click to expand...
Click to collapse
Until we get hardware acceleration I wouldn't recommend it but it should be possible. I can't remember if I was successful in booting it. I think I was for the SDK but didn't test it. It would be awfully slow, even slower than a normal boot.
I was able to boot Alpha 3 after reading about it in the dev thread. I was hoping it'd be stable enough that I could test it out but still have a usable phone. Lockups and lag prevent that.
However, quickly switching between CM7 and the ICS alphas would make it bearable. Right now the easiest way is nandroids.
I tried installing the newest ICS build through boot manager while running the last CM7 nightly. It installed fine, but when I would boot into it from Boot Manager, it would go to the CM7 boot animation and go on for ever.
Finally, I broke down and just wiped my phone and installed ICS. Its pretty sweet, but not something I want to use as a daily driver just yet, so I figured I would install CM7 through Boot Manager. I have tried several times and while installing I either get a "Unfortunately, Boot Manager has stopped working" or a reboot.
It does not seem like it is going to work... might try a different ROM or another CM7 build later. Would love to have these dual booting as well but right now it doesn't seem possible. If anybody has progress on this, let us know!
Thats exactly the answer I was looking for. Thanks for testing it out! Think I'll hold off on Boot Manager and just keep backup/restoring.
So did anyone of you get ICS working on boot manager? It would be great if the beta version would be working. Do you have any ideas what I could try to get it working? It didn't work as normal install. And as nandroid backup it didn't work, too.
It should be working via nandroid, thats how I've been testing the OMX releases as they come out. All a nandroid is doing is backing up /root, /system, /data, /datadata, and /cache. Since both GB and ICS use those paths, nandroid is version-independent.
Could not boot into ROM1 from ICS
I installed Boot Manager while running ics-deck ROM on my Evo 4g. I installed MIUI on slot 1 and the install went fine. I had to select ext2 fs and make sure that my screen stayed on (I had a setCPU profile to throttle CPU on screen-off) and that no other app interrupted the slot install.
After installing, I tried to boot into MIUI in slot 1 and got stuck in bootloader. Could not go past even into recovery. Thankfully through trial and error I found a way to boot into recovery. (flashed Amon-Ra from bootloader, said 'No' to power down and then chose to go to recovery). Once in recovery, I flashed the update.zip from the Bootloader 'PhoneRom' directory to be able to boot back into ICS.
Unless I am doing something wrong here and if someone else has this working, I'd say BM does not work in ICS. I am able to load ICS into slot 1 and boot into it though. It just cannot be the PhoneRom for some reason.
Anyone have this same issue? Or a solution? I'd love to keep my ICS build as the primary phone ROM.
i got ics working=) i installed cyanogen nightly as phone rom... then from there i installed on first rom cyanogen nightly and over that i did a full wipe and installed ics beta 6.1 from lord. after this i changed my phone rom again to coredroid. now i have a working ics rom in my boot manager
So there is a thread similar to this, but they don't seem to be interested in anything else apart from getting the Glide working in any way. But I need my phone to stretch and bend over backwards for me, otherwise I can't even get started on development. And the thread seems to be dead..
This one:
http://forum.xda-developers.com/showthread.php?t=1953672
Basically, I got this Glide on ebay. New and unlocked for under $200. I have a feeling that whoever did the unlock lurks here on xda and did a hasty bitflip or something. But the deal is when I got this phone it was running the GB stock rom. But right out of the box it started doing this.
https://www.youtube.com/watch?v=mBC89c_NfPo
Not on the Samsung boot screen in my case but a little bit into running GB. I thought "no problem" so I booted into download mode and flashed UCLJ3 and it worked fine.
But I did not get this phone intending to stop there. So I rooted and flashed CWMR and booted into recovery and it did the same thing again.. But the system was still fine.
Having no choice. I flashed TWRP and flashed LiteROM 0.9 and that worked fine. But only because that's the only non-stock rom TWRP can flash. It still has those package assert problems pretty much every other rom..
I've tried flashing back to GB stock rom and it still doesn't work.
SO FOR THOSE WHO TL;DR
- CWMR doesn't work
- TWRP works
- Any ROM based off of UCLJ3 or later works
- GB based ROMs do not work
- I can boot into download just fine
Anyone have any idea what's wrong?
chrisyjwai said:
So there is a thread similar to this, but they don't seem to be interested in anything else apart from getting the Glide working in any way. But I need my phone to stretch and bend over backwards for me, otherwise I can't even get started on development. And the thread seems to be dead..
This one:
http://forum.xda-developers.com/showthread.php?t=1953672
Basically, I got this Glide on ebay. New and unlocked for under $200. I have a feeling that whoever did the unlock lurks here on xda and did a hasty bitflip or something. But the deal is when I got this phone it was running the GB stock rom. But right out of the box it started doing this.
https://www.youtube.com/watch?v=mBC89c_NfPo
Not on the Samsung boot screen in my case but a little bit into running GB. I thought "no problem" so I booted into download mode and flashed UCLJ3 and it worked fine.
But I did not get this phone intending to stop there. So I rooted and flashed CWMR and booted into recovery and it did the same thing again.. But the system was still fine.
Having no choice. I flashed TWRP and flashed LiteROM 0.9 and that worked fine. But only because that's the only non-stock rom TWRP can flash. It still has those package assert problems pretty much every other rom..
I've tried flashing back to GB stock rom and it still doesn't work.
SO FOR THOSE WHO TL;DR
- CWMR doesn't work
- TWRP works
- Any ROM based off of UCLJ3 or later works
- GB based ROMs do not work
- I can boot into download just fine
Anyone have any idea what's wrong?
Click to expand...
Click to collapse
You have to use Odin to flash back down to GB.. make sure you format /system with cwmr before doing it ...
As the title says, I am running gedeROM 1.55 for the past year, since I experimented with a couple ROM's and settled on this one. For the most part its been a decent daily driver but have found it a little 'sluggish' lately and it annoys me. The lack of deep sleep keeps me always scrambling to keep it charged and ready to go so I don't find it dead when I want to use it.
Of course in the process I am using an older version of FFF and TWRP, so I know an update of them would be necessary.
A couple questions, looking for opinions:
1. Is it possible to just use KFU and update FFF and TWRP without disturbing everything else? I'd like to get them up to date.
2. After reading for 2 hours or more I am unclear on the limitations of 10.1 JB and wonder if I should be changing to JB at all?
3. Are the 10.1 ROM's a better option than I am running for speed and reliability? If so, any shining star amongst them?
I know asking for opinions will bore most people to death reading this, but I need some guidance from those that have been active and keeping up with ROM dev on this unit while I left mine alone and got behind.
Thanks in advance.
This might help you:
1. Look on the first post of this thread. Theres a flashable zip for FFF1.4 (Just flash in TWRP)
2. Here is Ichigo's flashable zip for TWRP 2.5.0 (Just flash in TWRP) https://www.dropbox.com/s/b4idirzkmgvnm07/TWRP-Blaze-2.5.0.0.zip
Those will not disturb anything else.
And try This ROM first and see if you like 4.2.2. This is the OFFICIAL cyanogenmod 10.1. To me its by far the best in terms of stability and speed. Make sure you wipe everything BUT /sdcard in TWRP before you flash!
Moving to a recent JB ROM will be a good move compared to gede because not only will you have better battery life but you'll have almost another year of improvements made to the Kindle since then.
Thanks for the info.... I'm gonna give this a shot I think. Not much to lose, nothing mission-critical on my tablet anyway
I'll post back once it's done!
Thanks again.
Bozz5384
It seems to have gone well, thanks for all the info. Updated FFF, TWRP, and now on CM 10.1 ... I did the 5/20 nightly, wasn't sure which one to do -- seems pretty bug free at this point.
Hey guys, just thought I'd try and revive my Kindle Fire. I've had roms on my Kindle Fire since I bought it when it came out (never even used stock Kindle). We all know the KF is dated now, and I've had kitkat and also lollipop on it but it just seems too slow to really use lollipop or kitkat. Constant redraws and the device just hangs for a few seconds before apps start up
I'd like to see what everyone else's ideas are as far as revitalizing this device even if it means going back to an older version of android or using specific roms. Thoughts?
This tablet is dogpoop slow on Lollipop. I have confirmed it with at least 3 other owners.
Anyway, I have TWRP installed and I am HOPING that Cyanogen solves a little of this. Can I just move right off of stock into CM or do I need any prep?
Haven't flashed this device in a while and don't want a bricked device.
abuttino said:
This tablet is dogpoop slow on Lollipop. I have confirmed it with at least 3 other owners.
Anyway, I have TWRP installed and I am HOPING that Cyanogen solves a little of this. Can I just move right off of stock into CM or do I need any prep?
Haven't flashed this device in a while and don't want a bricked device.
Click to expand...
Click to collapse
Chances are anyone that says flo runs slow on lollipop runs strictly stock with every mainline Google application syncing in the background... The perception of slow performance on lollipop for flo has more to do with the hardware in flo aging enough so that Google's increasingly large applications have less and less free ram on which to run.
If you're unlocked, rooted, and have the latest TWRP (2.8.7.0) installed, as well as the latest bootloader, which you likely have due to coming from stock, you just need to reboot to recovery, perform a full wipe, and install your ROM and gapps .zips of choice.
Flo?
Yes, it was strictly stock. Runs a lot better with CM12.1
Sent from my XT1060 using Tapatalk