Well as some of you have already seen that some phones are capable of dual booting such as ONE particular windows phone (don't remember the name of the phone) Which was able to boot into Android software while still being able to keep its stock windows Rom. Well my question is, is it possible for the kindle fire to be able to boot into another Rom like "CM7" or others as such while still keeping the stock Rom?
Sent from my Kindle Fire using xda premium
Do you mean actual dual booting, or just booting a rom within a rom? I helped a friend boot Android 2.2 on her windows phone one time and she loved it.
I dont know if you can boot one android rom within another android rom. Though I could be completely wrong.
As I do recall there is a way to boot Ubuntu Linux within an Android rom so if someone puts together a good app, it just may be possible.
A Rom within a Rom?? That's CRAZY talk lol no but In all seriousness I was thinking like when you boot up your device, it will load a screen asking you if you want to boot into the stock Rom or whichever other Rom you have installed. Such as CM9 or what have you. Or when you boot your device, it will boot into the stock Rom and from there you can choose to boot into another Rom.
Sent from my Kindle Fire using xda premium
Well in relation to what I helped a friend do with her phone and Android/Windows mobile, was that you loaded an exe from windows mobile and it rebooted her phone into android and stayed until a reboot was triggered.
But as for an option to boot to a particular OS... I suppose if someone hijacked the bootloader(which is a viable option with an unlocked bootloader such as on the fire) and then threw in a quick app that checked for bootable partitions or folders with boot files in it, listed them for you and then booted based on what you chose... then sure...
Is that possible? I think it is... although I am not the dev to do it as I have no knowledge of this type of thing.
Maybe JackpotCalvin or someone else might have some kind of better ideas.
Corey
Nothing is impossible, its just very very difficult. Unless of course you know what you're doing,then its easy. Anyways thank you for your helpful reply.you answered my question perfectly. But it IS an interesting concept towards a mobile device.
Sent from my Kindle Fire using xda premium
Glad I could be of a some help for you.
Never be affairs to ask if you need more help.
Corey
The Touchpad can dual boot. When booting, I can select which OS I want: WebOS or CM7. It's definitely possible if there's enough space, and I'm all for it since I'm a Prime member and love having access to unlimited videos.
Sent from my GT-I9100 using XDA App
Related
Someone had the idea to modify the cwm code so that a short press moved down, and a long press selected something.
I may give this a try, but I'm curious if I can edit the cwm files in eclipse, and if it would be possible to load cwm into an android virtual device?
I have very little programming experience, so being able to test and debug in eclipse would be a lot better than possibly bricking my kindle.
Sent from my Nexus S 4G using XDA App
Just curious but what's your progress on the CWM. I really like CWM for my other devices but I had some troubles with the CWM clone for the KF
I have CM7 on my KF and it's a little buggy, but it's nothing that would deter me from running or recommending it. Overall, it's sturdy and runs well. I'm happy with it.
Sent from my Kindle Fire using Tapatalk 2
My KF seems to be operating weird. On the lock menu, it doesent respond well to touch, only a few times was I able to get to my password pattern screen, and doing my pattern there would fail and say sorry try again, even though I know I did it right.
How can I fix this, I have TWRP 2 on it, but it is pretty unresponsive with the buttons ( I have to tap a few times for the button to react) is it a hardware malfunction maybe?
Are you using stock rom or custom? The touch responsiveness is a little iffy when it comes to stock sometimes.
Is this a new problem or has it always been the case? You could have background processes stealing much needed resources or it could be the pattern lock you are using.
Have you tried a touch screen booster?
Sent from my Amazon Kindle Fire using xda premium
Its new, its like the kindle fire is touching itself... lol. I went to TWRP mode and it automatically touched backup. I fully charged it and it is still acting the same. Seems to be running slow/lagging as well. These problems are new and havent happened until today. Its on Cyanogenmod 7
edit: I think its busted, there is a crack also. It looks like I will have to buy another fire or another tablet, but cant I get a cheap replacement from Amazon if they cannot tell its been modified? Can I modify it so it will look like it is native software and not the mods?
I guess you could flash unrooted stock Kindle rom, get rid of custom recovery and flash stock bootloader so you can send it back.
Just backup your sdcard to your computer and get rid of any personal information.
Sent from my Amazon Kindle Fire using xda premium
Not to hijack this thread...
But I've been having problems with using stock and it's touch responsiveness.
I've never heard of a touch screen booster. (I hate to sound stupid) but is there an app where I can calibrate the touch screen?
- D
I am in the fastboot command prompt, and I have the 6.3 kindle stock Rom downloaded, but I am not sure how to deal with partitions and knowing what is where,
what commands do I enter to flash it on there, and where should the ROM be located on my computer to do so?
edit: I did a search and saw someone had a similar problem and you helped them SoupMagnet, http://forum.xda-developers.com/showthread.php?t=1589488&highlight=flash+stock+rom, only I am not sure how to flash using ADB, what commands to use rather, I have the command prompt up and running, if you could help id be very grateful to make it stock.
13BFeder said:
I am in the fastboot command prompt, and I have the 6.3 kindle stock Rom downloaded, but I am not sure how to deal with partitions and knowing what is where,
what commands do I enter to flash it on there, and where should the ROM be located on my computer to do so?
Click to expand...
Click to collapse
I've never had to do this myself so I probably wouldn't be much help in that regard. If it were me though, I would flash stock rom through recovery first. Then use fastboot to replace the bootloader. And figure out how to either uninstall recovery or figure out which commands to use to wipe the recovery partition.
Like I said, I've never attempted it so you should probably study up before trying.
Hope this helps
[Edit: In all actually, if you just replace the rom and bootloader then recovery wouldn't even be accessible except through fastboot. I have no idea what Amazon does for repairs so its up to you whether you want to keep it installed
Cheshire.Love said:
Not to hijack this thread...
But I've been having problems with using stock and it's touch responsiveness.
I've never heard of a touch screen booster. (I hate to sound stupid) but is there an app where I can calibrate the touch screen?
- D
Click to expand...
Click to collapse
Yes
Sent from my Amazon Kindle Fire using xda premium
Alright then thanks, another option is probably just to destroy it even more... putting it in water while turned on or something so amazon cant even turn it on... lol.
Then they may replace for like 100 dollars, if not I may look for another tablet or wait... il definately get a case as well.
I installed LCD Density app from the market. Changed settings from 320 to 300 and it said to reboot phone. This put my phone into bootloop with LG logo and led flashing. My phone is Verizon, rooted with TWRP installed. I can get into TWRP but hadn't made a backup yet. Any ideas? I tried wiping will in TWRP and then rebooting but still got the bootloop. If it matters, I have a Mac. Thanks for any help...
Factory reset in twrp. Then install the rom again should work. Changing dpi can have adverse effects ☺
Sent from my LG-D800 using Tapatalk 4
How can I get the Rom onto my phone? I have a Mac?
did you delete the rom from the sdcard? if it isnt there anymore then you will need to adb push it. I dont have a mac so cant be of help on that side of it.
I was running stock Rom. Only mod was black notification bar. I hadn't downloaded any roms yet. Don't think I can get adb to recognize my phone as I can't select Ethernet connection. Any ideas?
I don't have a Mac, so I cannot help you with that. And I really hope you get this rectified with the help of the community here. That being said, please know that this next comment is not being directed solely towards you, but to a whole lot of others as well.
Order of life in customizing your phone :
1. Root method applied
2. Install appropriate custom recovery
3. Boot to custom recovery
4. MAKE A BACKUP. PERIOD! Absolutely no reason not to do this step. It will save your butt or your phone in the future, when, not if, you find yourself in a bad situation.
5. Have fun with your phone, but only after you understand what you are doing, and accept the possibility of messing up your phone. $hit happens when it's least expected.
I didn't mean for this to sound harsh, but it is really important to understand.
Anyone with a Mac that can help this person out?
Sent from my Nexus 10 using XDA Premium HD app
Yeah I have always made a back up in the past. I'm so annoyed at myself for not doing it. Any suggestion on how I can either get a rom onto my phone or edit the build.prop back to stock?
Got it fixed! Was finally able to connect to my Mac. Then put a rom on the phone using ADB and flashed the rom.
black05x5 said:
Got it fixed! Was finally able to connect to my Mac. Then put a rom on the phone using ADB and flashed the rom.
Click to expand...
Click to collapse
Excellent.
Thanks Devs. From my VZW G2.
trickster2369 said:
I don't have a Mac, so I cannot help you with that. And I really hope you get this rectified with the help of the community here. That being said, please know that this next comment is not being directed solely towards you, but to a whole lot of others as well.
Order of life in customizing your phone :
1. Root method applied
2. Install appropriate custom recovery
3. Boot to custom recovery
4. MAKE A BACKUP. PERIOD! Absolutely no reason not to do this step. It will save your butt or your phone in the future, when, not if, you find yourself in a bad situation.
5. Have fun with your phone, but only after you understand what you are doing, and accept the possibility of messing up your phone. $hit happens when it's least expected.
I didn't mean for this to sound harsh, but it is really important to understand.
Anyone with a Mac that can help this person out?
Sent from my Nexus 10 using XDA Premium HD app
Click to expand...
Click to collapse
It amazes me when people don't create a backup.
Well.... no effing clue whats happened.... it must've updated recently as no longer rooted or using golauncher... getting rather annoyed at the inability to access the internal storage via usb...
Windows brings up a massive message that when i googled it the fix was to apparently unplug the pc.... which resolved a few issues but still get the same issues with the kindle... which sucks.... managed to connect briefly with Linux but now it just seem to not acknowledge it at all....
I had what i thought were the latest drivers as i only installed them a couple of days ago.. (rediscovered scummvm!!!)
Any ideas what I can do? I want to re root and flash a totally new rom as the amazon one is truely awful
And which is the best root method for 7.4.6? If there is one....
Thanks again peeps!
Sent from my KFTT using Tapatalk now Free
shugs81 said:
Well.... no effing clue whats happened.... it must've updated recently as no longer rooted or using golauncher... getting rather annoyed at the inability to access the internal storage via usb...
Windows brings up a massive message that when i googled it the fix was to apparently unplug the pc.... which resolved a few issues but still get the same issues with the kindle... which sucks.... managed to connect briefly with Linux but now it just seem to not acknowledge it at all....
I had what i thought were the latest drivers as i only installed them a couple of days ago.. (rediscovered scummvm!!!)
Any ideas what I can do? I want to re root and flash a totally new rom as the amazon one is truely awful
And which is the best root method for 7.4.6? If there is one....
Thanks again peeps!
Sent from my KFTT using Tapatalk now Free
Click to expand...
Click to collapse
You would probably benefit most by using KFFA to return to 7.2.3 then root, remove OTA updates and install GApps. This way when you go to install a custom ROM, you have a matching boot loader. In order to put a custom ROM on, you need to flash a 2nd boot loader and TWRP. All this is covered in great detail on here. If you have questions do ask.
Sent from my Kindle Fire HD 7 running 4.3 Paranoid Android using xda app-developers app
I recommend Paranoid Android indeed!
I was bored and decided to try to build a rom and see what happens, i don't know any c coding so its a bit of it it compiles and works great, if it doesnt work then i'll need a c compiler and both my friends that know c coding dont get online often.
Anyways about the details, i have sucessfully built a 7" and 8.9" Kindle Fire HD version of the rom, soupmaget is going to test the 8.9" rom, but i need a 7" tester prefereably with a fastboot cable incase things go south like the first time where it deleted the second bootloader from the system partition, though i think i fixed that. Anyways if you are interested in testing this pre-alpha build of the rom, plz reply back and il send you a link in a private message to the rom. On another note te tester should also be prepared to do a full backup of their sdcard of their device including the sdcard because i have not ever used this os so i have no idea how it handles the sdcard data, while it shouldnt wipe it i just think it would be a good idea in general.
I can test it.
I have a fastboot cable and the only files that I have are books anyway.
OK sweet I'll pm you the link with instructions.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
I'm your Huckleberry.
---------- Post added at 04:58 PM ---------- Previous post was at 04:54 PM ----------
stunts513 said:
i need a 7" tester
Click to expand...
Click to collapse
I messed up the quote last time. Anywho, link me if you want.
Sweet I'll pm u too.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Sweet I'll pm u too.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
First test:
Downloaded and flashed just fine. After wiping Dalvik/CACHE and rebooting into system it did show the Kindle Fire Animation followed by the TWRP animation and then displayed fastboot. Holding the power button down for 20 seconds powered it off and access to TWRP was still possible. Flashed a nandroid and all is fine. Let me know when the next update is available.
LinearEquation said:
First test:
Downloaded and flashed just fine. After wiping Dalvik/CACHE and rebooting into system it did show the Kindle Fire Animation followed by the TWRP animation and then displayed fastboot. Holding the power button down for 20 seconds powered it off and access to TWRP was still possible. Flashed a nandroid and all is fine. Let me know when the next update is available.
Click to expand...
Click to collapse
So ok im confused it just went into fastboot after trying to boot or something? If thats the case there must be something very wrong with the kernel i think.
stunts513 said:
So ok im confused it just went into fastboot after trying to boot or something? If thats the case there must be something very wrong with the kernel i think.
Click to expand...
Click to collapse
Correct. The flash was successful (in other words it did not fail.) I click reboot into system from TWRP. I saw the Kindle Fire animation followed by the TWRP animation and then, then stead of the ROM animation, it went strait to fastboot. Then I force powered it down, was able to access TWRP, wiped and then flashed my backup nandroid and the Kindle booted with no permanent issues. But yes, something is not right there.
Basically, rather than booting into the system, it booted into the bootloader.
LinearEquation said:
Correct. The flash was successful (in other words it did not fail.) I click reboot into system from TWRP. I saw the Kindle Fire animation followed by the TWRP animation and then, then stead of the ROM animation, it went strait to fastboot. Then I force powered it down, was able to access TWRP, wiped and then flashed my backup nandroid and the Kindle booted with no permanent issues. But yes, something is not right there.
Basically, rather than booting into the system, it booted into the bootloader.
Click to expand...
Click to collapse
*facepalm* i'm going to have to check the kernel image, this whole setup i used is kinda rigged because this os was designed to work with a specific version of jb aosp, and cm 10.2 is close to that revision but not exact so i used aosp as my source and had to modify some of hashcodes file sto get it to compile, but it finally did compile, seeing as there were problems here and there i'm going to take a wild guess the boot.img is using the standard header and not amazons, and thats just a wild guess at best, i don't know what a normal header would do on a kindle, but i will try to decompile the boot.img and see if it errors out like a usual kindle boot.img would if you dont shave off the header with dd.
Man i hate double posting but i thought i'd mention i think what i guessed at was right because it split immediately upon running the splitting script... so now i guess i need to ask hashcode wtf is going on and how to fix it since it's not compiling the boot.img with the correct header.
Sounds like a plan.
Sent from my Amazon Kindle Fire HD running CM 10.2 using xda app-developers
Well I talked to hashcode, I'm trying to get it fixed, but I'm a bit confused, makefile coding isn't my specialty, I am going to ask other RC's and see what I can dig up.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
hi!!
stunts513 said:
I was bored and decided to try to build a rom and see what happens, i don't know any c coding so its a bit of it it compiles and works great, if it doesnt work then i'll need a c compiler and both my friends that know c coding dont get online often.
Anyways about the details, i have sucessfully built a 7" and 8.9" Kindle Fire HD version of the rom, soupmaget is going to test the 8.9" rom, but i need a 7" tester prefereably with a fastboot cable incase things go south like the first time where it deleted the second bootloader from the system partition, though i think i fixed that. Anyways if you are interested in testing this pre-alpha build of the rom, plz reply back and il send you a link in a private message to the rom. On another note te tester should also be prepared to do a full backup of their sdcard of their device including the sdcard because i have not ever used this os so i have no idea how it handles the sdcard data, while it shouldnt wipe it i just think it would be a good idea in general.
Click to expand...
Click to collapse
send me instructions for the test
I will next time I make a build after fixing this boot.IMG issue I have, I haven't seen hashcode in the IRC since Wednesday and I haven't been able to fix the makefile issue yet, I have to transfer some of the code from cm's /build/core/Makefile to mine, specifically the parts that let's board_custom_booting_mk work to generate the booting correctly. You would think there would be a patch for aosp that does this, but I guess most devices don't need a custom bootimg?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Test
stunts513 said:
I will next time I make a build after fixing this boot.IMG issue I have, I haven't seen hashcode in the IRC since Wednesday and I haven't been able to fix the makefile issue yet, I have to transfer some of the code from cm's /build/core/Makefile to mine, specifically the parts that let's board_custom_booting_mk work to generate the booting correctly. You would think there would be a patch for aosp that does this, but I guess most devices don't need a custom bootimg?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
I have understood that the boot.img should go hand in hand with the system you build,
so a custom boot.img should be mandatory
excuse my bad English, I use google translator
Any chance of a build compatible with the kf2?
I'm too broke to buy the newest fire hdx that's on sale for $180 today,so I'm holding on to my 2012 non-hd fire.
Sent from my Amazon Kindle Fire2 using XDA Premium HD app
agentfusion said:
Any chance of a build compatible with the kf2?
I'm too broke to buy the newest fire hdx that's on sale for $180 today,so I'm holding on to my 2012 non-hd fire.
Sent from my Amazon Kindle Fire2 using XDA Premium HD app
Click to expand...
Click to collapse
Keep an eye on Swappa. People are dumping their older models for cash for the newer models.
Sent from my Amazon Kindle Fire HD running CM 11 KitKat 4.4 using xda app-developers
I plan on building it for all supported kf's, right now I'm working out the build kinks and seeing if it will even boot. Just fixed the makefile issue but I may have introduced another issue by using a certain patch to disable recovery a while back, so I may need to grab a fresh copy of the make file and repatch it, I'll pm when it's more ready to test which will be soon.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Send me a PM once you get the boot.img thing fixed. I have a fastboot cable, too.
Sent from my Amazon Kindle Fire HD using xda app-developers app
Hi,
Just for understanding right. Is this for the Kindle Fire HD KFSOWI (3rd gen)?
If yes then I absolutely want to try your Rom.
Thanks in advance.