In keeping with my tradition of providing stock rooted ROMs, I've re-packaged the new 6.3 update. As with my past ones, this is completely stock except for modifications that provide root access. It does not attempt to block OTAs in any way, and it does not contain any extras like the Market.
This is a full ROM, not an incremental update, so it will wipe your /system partition when installing. If you're coming from a non-stock ROM you'll want to wipe data/cache, but if you're coming from a previous stock ROM you should be okay. This is tested in CWM (it's what I have onhand right now) but TWRP should also work.
Changes between this and a completely stock 6.3 ROM are:
REMOVED FROM ROM
The new /system/bin/check_rooted binary
Stock recovery image
Stock bootloader image
That goofy userdata-backup.zip
ADDED TO THE ROM
Superuser
su
busybox
CHANGES
Removed the entry from init.omap4430.rc that ran check_rooted at boot.
Set ro.secure=0 so adbd runs as root (insecure boot version only)
updater-script doesn't attempt to install recovery, bootloader, or userdata-backup.zip file since they are not in the ROM.
updater-script won't check your /system partition's size before installing. This means it will install on a /system partition that's been resized, but I have not tested this. My assumption is that if you resized /system you'll know how to handle any errors that you may encounter.
I'm providing secure and insecure boot images, as with my past versions. For those unfamiliar, insecure means adbd runs as root on your Fire so you get a root shell when you use adb to connect (i.e. you get # by default). Secure gives you a user shell (the $) by default, but you can still use 'su' to elevate to root.
DOWNLOADS
Stock rooted 6.3, secure boot image (md5: 37f51cd2dfaf58baffac09135236de36)
Stock rooted 6.3, insecure boot image (md5: e551a507ebc64fabe09f7d5387348585)
What's change on 6.3??
Sent from my LG-P500 using xda premium
acax456 said:
What's change on 6.3??
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
Its right there in his description..
Sent from my Nexus One using xda premium
acax456 said:
What's change on 6.3??
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
http://www.amazon.com/gp/help/customer/display.html/ref=hp_k6land_software2?nodeId=200790620
So if I flash this off Modaco gr7 to get to the latest version should I be ok as long as I wipe Dalvik and cache?
CTTKDKing said:
So if I flash this off Modaco gr7 to get to the latest version should I be ok as long as I wipe Dalvik and cache?
Click to expand...
Click to collapse
I would say probably yes since it's mostly stock, but I've never tried so I can't say for certain. Worst case should be that you bootloop, at which point you can always go back into recovery and wipe data, too.
Perhaps the dumb question, shall I just download and flash it by TWRP like other CM Roms? Please excuse I am noob. Thank you
eldarerathis said:
I would say probably yes since it's mostly stock, but I've never tried so I can't say for certain. Worst case should be that you bootloop, at which point you can always go back into recovery and wipe data, too.
Click to expand...
Click to collapse
Just flashed over Modaco GR7 throught TWRP and everything went smoothly and fine!
---------- Post added at 08:20 PM ---------- Previous post was at 08:19 PM ----------
ka724ka said:
Perhaps the dumb question, shall I just download and flash it by TWRP like other CM Roms? Please excuse I am noob. Thank you
Click to expand...
Click to collapse
Just Flashed through TWRP like any other rom (over modacos) and everything went fine !
My first kindle rom. Thanks so much. I really like stock and was happy to make this my first rom. It's awesome.
Just wondering if I can flash intersects kernel with the 6.3 Rom?
Sent from my Kindle Fire using xda premium
xolanir said:
Just wondering if I can flash intersects kernel with the 6.3 Rom?
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
I don't see why not
Sent from my Kindle Fire using xda premium
Updated successfully, but for some reason CWM is unable to make a back up, gives me an error listing that it can't write the cache img. Has anyone else had this issue or is it isolated, and is there a fix? Thx in advance for help.
Sent from my Kindle Fire using xda premium
I assume this has the new browser, how do you access the new "reading view" I feel like it should be fairly easy to see but...
xolanir said:
Updated successfully, but for some reason CWM is unable to make a back up, gives me an error listing that it can't write the cache img. Has anyone else had this issue or is it isolated, and is there a fix? Thx in advance for help.
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
I've had CWM (and TWRP, actually) refuse to mount my cache partition in the past, and rebooting generally fixed it for me. Not sure if that's what's happening to you, though.
eldarerathis said:
I've had CWM (and TWRP, actually) refuse to mount my cache partition in the past, and rebooting generally fixed it for me. Not sure if that's what's happening to you, though.
Click to expand...
Click to collapse
I recently repartitioned my KF following the guide you posted using the GNU parted method. What I did was increased my media storage and shrunk my cache partition to 350MB and userdata partition to 700MB, would those settings affect CWM in anyway? The other thing I noticed was after I get the error, I reboot and check the CWM folder to see if anything did save, and it looks like it doesn't compress the back up while saving it. I found a partial back up of 2.35GB after the error. This is a strange one
Update: okay figured it out. The problem was CWM was trying to back up the /sd-ext volume. I unchecked it in the advanced back up option and ran the back up without a hitch.
Sent from my Kindle Fire using xda premium
Can anyone confirm that the browser did not update to the newest version?
To access reading view, I was told "At the bottom of the display there is an eyeglass Icon tap it the screen says loading and you will have the view. Back arrow out of it."
I don't see an eyeglass icon on this rom.
jacewt said:
Can anyone confirm that the browser did not update to the newest version?
To access reading view, I was told "At the bottom of the display there is an eyeglass Icon tap it the screen says loading and you will have the view. Back arrow out of it."
I don't see an eyeglass icon on this rom.
Click to expand...
Click to collapse
It works for me, but only on certain web pages (I'm guessing ones that are text-heavy). Try viewing some random Wikipedia article, for example. The icon also doesn't appear until about a second or so after the page has completely finished loading.
Just bizarre, I am not getting it. I looked at wikepedia articles too. I am using the insecure rom if that makes a difference.
What version should the browser be now?
I have 1.0.13.328_10008910
Gonna go clear data, etc.
Well, heck, that did it. Thanks for that. Interesting feature!
Flashed this succesfully... but i neglected to wipe the system and accidentally flashed the 4.0 gapps package after. Boots fine but i am getting an android.process.acore FC and a Calender session FC. Any suggestions? I came from JC's ICS build and I am thinking of just going back to that.
Update. Nevermind. Just went back to ICS. The Stock Launcher gives me douche chills.
Swype?
Anyone who has Swype working on 6.2.1 or 6.2.2 installed this? If so can you tell me what happened to your Swype and were you able to get it working again?
I'm still on 6.2.1 (updates blocked with Droidwall) and went through so much hassles getting everything working *just* right, I'm trying to decide if the changes in 6.3 are worth potentially having to re-do Swype, market, calendar/contact sync, etc.
Edit: Any hope for an incremental update on this one? I loved the ones for 6.2.1 and 6.2.2.
Edit2: Any issues with market or calendar/contact syncs (for those of us who had set that up)?
so a little while back i was having issues with twrp... now it is working fine, i just have a question about flashing roms. i boot into recovery and wipe system/ factory reset, install the otter zip, gapps, and reboot. just a black screen for a few minutes. so i boot into recovery and restore my backup. i am on 6.2.2, what am i doing wrong?
So I know that AOKP's website says that the KF (otter) has its own build and it is there and lovely and such but that is just false, I get the exact same result when I try to boot it also. However, you can still boot AOKP on your fire, I believe that this is the most recent version of the ROM, http://forum.xda-developers.com/showthread.php?t=1614004 just make sure you wipe everything before you flash so you don't wind up with the frankenstein monster trying to boot on your kindle. Enjoy
nschiwy said:
So I know that AOKP's website says that the KF (otter) has its own build and it is there and lovely and such but that is just false, I get the exact same result when I try to boot it also. However, you can still boot AOKP on your fire, I believe that this is the most recent version of the ROM, http://forum.xda-developers.com/showthread.php?t=1614004 just make sure you wipe everything before you flash so you don't wind up with the frankenstein monster trying to boot on your kindle. Enjoy
Click to expand...
Click to collapse
thanks man . youve been the most helpful on here yet.
Hello guys I flashed aokp 40 today and my kindle won't charge . I have to go into twrp to get it to charge any ideas?
Sent from my SCH-I500 using xda app-developers app
tsmith1296 said:
Hello guys I flashed aokp 40 today and my kindle won't charge . I have to go into twrp to get it to charge any ideas?
Sent from my SCH-I500 using xda app-developers app
Click to expand...
Click to collapse
A few things I would try:
1) Wipe everything and reflash the ROM, obviously you want to charge the Kindle before doing this or have it charging while you're doing it to make sure you don't lose power mid-flash.
2) Flash Hashcodes 3.0 Kernel found here: http://forum.xda-developers.com/showthread.php?t=1591850
also keep these things in mind: http://forum.xda-developers.com/showthread.php?t=1615355
3. Charging indicator isn't working. But device is charging.
3) Try using this AOKP kang instead, even though it is "build 36" it is only 2 weeks older than the official build 40 and I have always had better luck using lithium's kang, for some reason. http://forum.xda-developers.com/showthread.php?t=1614004
Thanks man I'll give those a try!
Sent from my SCH-I500 using xda app-developers app
I've run into a strange problem I have fff extended and twrp installed and currently am running jandycane as my main, and the stock DoCoMo as salt but recently I tried to flash cm10 and when i tell twrp to install the ROM it starts to go then drops me back to the start up for twrp and then to the main selection screen, when I have tried to DL cm10 through goo manager it will DL the file then tell me the md5 sum is mismatched. On a side note I don't know if this a symptom of the problem or not but using an JohnNES when I save in game it will initially see the save but if I restart the app the saved game does not show but the file for it still exists.
Thanks in advance
Sent from my Amazon Kindle Fire using xda app-developers app
I used the Kindle Fire Utility to root my kindle, install superuser, install gapps and go launcher, all that happy crap along with TWRP and FFF (the one with the blue "kindle") and my TWRP is messed up. I can access it and everything but it won't let me make backups or flash anything through it, so i decided to install Clockworkmod instead (hearing it was pretty good since the final release) and so i tried to use all sorts of things i had in store (ROM manager[i hate rom manager] Flash image gui, goomanager,) and everything i try will not work to install Clockworkmod. I can't flash it through TWRP and i'm trying to learn how to use Fastboot. I was wondering if anyone else had any ideas on how to get TWRP to work or any way on how to install CWM that doesn't involve terminals, because those are a pain. Any advice will be helpful.
What TWRP says when trying to backup or flash:
instead of saying "installing..." like it did with CWM on my Optimus V it says
(i'm running a backup sequence)
Updating partition details...
Running boot script...
Finished running boot script.
Simulating actions...
Then at the top it says "backup complete"
"successful"
but when i look in the restore folder there isn't anything to speak of.
Don't use clockworkmod. It's outbid date if you read it the thread it says STOP USE IMMEDIATELY. Try flashing A newer version of TwRp through a .zip in clockworkmod and see how that works
Sent from my iPhone using Tapatalk... Don't hate
androidnooob98 said:
I used the Kindle Fire Utility to root my kindle, install superuser, install gapps and go launcher, all that happy crap along with TWRP and FFF (the one with the blue "kindle") and my TWRP is messed up. I can access it and everything but it won't let me make backups or flash anything through it, so i decided to install Clockworkmod instead (hearing it was pretty good since the final release) and so i tried to use all sorts of things i had in store (ROM manager[i hate rom manager] Flash image gui, goomanager,) and everything i try will not work to install Clockworkmod. I can't flash it through TWRP and i'm trying to learn how to use Fastboot. I was wondering if anyone else had any ideas on how to get TWRP to work or any way on how to install CWM that doesn't involve terminals, because those are a pain. Any advice will be helpful.
What TWRP says when trying to backup or flash:
instead of saying "installing..." like it did with CWM on my Optimus V it says
(i'm running a backup sequence)
Updating partition details...
Running boot script...
Finished running boot script.
Simulating actions...
Then at the top it says "backup complete"
"successful"
but when i look in the restore folder there isn't anything to speak of.
Click to expand...
Click to collapse
Reset the defaults of twrp because it`s simulating actions and not performing them.
Or run smirkit and fash COTR
BTW do you not care if you kill your device?
There is a bug sticky that says don't use CWM
Sent from my Nexus 7 using Tapatalk 2
tobiascuypers said:
Don't use clockworkmod. It's outbid date if you read it the thread it says STOP USE IMMEDIATELY. Try flashing A newer version of TwRp through a .zip in clockworkmod and see how that works
Sent from my iPhone using Tapatalk... Don't hate
Click to expand...
Click to collapse
Where do you see that)
http://forum.xda-developers.com/showthread.php?t=1454241
Sent from my Kindle Fire using xda app-developers app
Thepooch said:
Reset the defaults of twrp because it`s simulating actions and not performing them.
Click to expand...
Click to collapse
This worked but now it hangs at the end saying updating partition details. But i saw a post on that in the fourms. Thank you all!!!
Sent from my Kindle Fire using xda app-developers app
androidnooob98 said:
Where do you see that)
http://forum.xda-developers.com/showthread.php?t=1454241
Sent from my Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
In the last few pages of posts...
Sent from my iPhone using Tapatalk... Don't hate
I ran soup kit on linux installed twrp...rebooted to recovery then dirty flashed jb cm10.1 now I can't use anything except the calendar or the clock...jb boots fine though its just very buggy...windows still won't detect kindle as adb or interface or composite just as a myp storage device...linux deosent work at all it won't detect...not even as a usb drive like windows does...I need to get to recovery but I'm still on stock bootloader...
Sent from my myTouch_4G_Slide using xda app-developers app
Due to the dirty flash home wont work and settings are kinda hard to get to...i got it though...now to enable adb through developer settings and see what windows and linux says...
Sent from my myTouch_4G_Slide using xda app-developers app
Do you have fff installed?
Actually I got it...fff is installed recovery works and im now running cm10.1 jb 4.2.2....
I made a linux usb drive...i made a cd disk actually...then used kindle fire soup kit to install a custom recovery....then used the same soupkit to boot me into recovery mode...inside recovery I backed up as usual then I flashed cm10.1...now I dirty flashed it so I couldnt immediately get to developer settings and enable adb...but I got there in the end....with that enabled I finally saw android composite device on my pc ...due to the dirty flash I had to get back in recovery wipe system and flash fresh.....out of,linux and now back on windows I downloaded kindle fire utility and used that to install fire fire fire bootloader once android composite device installed...then I reboot kindle to test out bootloader...it worked and it let me change bootmodes from regular to recovery...inside recovery I fixed the dirty flash I did and then I was done....hope this helps anyone...I must note that I previously installed the drivers numerous times but I never saw cpmposite until o was on cm10. But thats me.....Sent from my myTouch_4G_Slide using xda app-developers app