Develop Bugs

[ROM] Stock rooted 6.3

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)?

[Q] JB can't keep a recovery?

I just upgraded to JB, and like most of you, I've been adding things to it, mostly through CWM. The problem is, the recovery partition is (kinda) broken. Let me explain.
If I turn off my GNex and reboot it to Fastboot then use Fastboot to go to Recovery mode, or even try to boot to it from ROM manager, I get the "android on his back with his panel open and a <!> floating over him" icon. I have to pull the battery to get past that. From there, if I use the Galaxy Nexus Toolkit to flash a recovery, it will boot to it, but even if I reboot immediately, I get <!> again. If I flash CWM from ROM manager, it will work, but again, only that one time. It's like something in the shutdown process is breaking recovery.
I tried it with CWM, CWM Touch, and TWRP. Same problem.
Am I alone in this?
Is there a fix?

This happened to me after I flashed stock JB. I then flashed bigxie's rooted deodexed Rom and my recovery sticks

I am on Team Liquid vicious v2 w/ franco 200 kernel. it has been very smooth and I have been able to boot into recovery seamlessly.

I am assuming you already have root. Just go to the /system folder then rename recovery-from-boot.p to something else and cwm will stick

I've got the same problem from time to time.
Suddenly CWM is away and I have to reflash it.
Can I fix this by deleting the .p file mentioned?
Sent from my Galaxy Nexus using xda app-developers app

land.apfel said:
I've got the same problem from time to time.
Suddenly CWM is away and I have to reflash it.
Can I fix this by deleting the .p file mentioned?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Kinda weird that it's from "time to time" because if that file is there, then it should bring you back to stock recovery every time after you use your newly flashed temporary recovery. Yes, rename/delete that file and it should stick.

anton2009 said:
Kinda weird that it's from "time to time" because if that file is there, then it should bring you back to stock recovery every time after you use your newly flashed temporary recovery. Yes, rename/delete that file and it should stick.
Click to expand...
Click to collapse
Looks like deleting the files has worked soo far. Thanx
land.apfel

http://forum.xda-developers.com/showthread.php?p=28083666
Sent from my Galaxy Nexus using Tapatalk 2

Installed TWRP...How do I remove CWM?

I installed TWRP and like it better than CWM...so I want to remove CWM.
How can I do this?
The 2 GB of space that blibs takes up is ridiculous...

File manager
Sent from my SGH-I747 using xda premium

woodydog said:
File manager
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
Can you be more specific? Do I just delete the Clockworkmod folder and that's it? There's nothing in the root?
Sent from my SGH-I747 using xda app-developers app

Did you use goo manager to install your twrp? I believe it removes it for you.... Cuz I don't see cwm files anywhere after in installed twrp with goo.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Deoxlar said:
Did you use goo manager to install your twrp? I believe it removes it for you.... Cuz I don't see cwm files anywhere after in installed twrp with goo.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Yes I did. I still see clockworkmod folder in my file explorer with everything in there, but I don't think deleting that will completely remove cwm
Sent from my SGH-I747 using xda app-developers app

CWM itself was removed off your phone upon installing TWRP with Goo Manager.
What you see is the folder in which backups are stored.
You can delete this folder.
If you doubt, just copy the clockworkmod folder to your PC before deleting it off your phone.

As said above twrp goes right over cwm what's left over is backups and other things not needed anymore. Those are safe to delete
AT&T SGS3 Marble White
AoCP The Collective 4.4 ROM
KT747 10/31 OC'ed & UV'ed
Medical MJ Supporter

you can choose to backup via tar method. no blibs!

crystol said:
you can choose to backup via tar method. no blibs!
Click to expand...
Click to collapse
I didn't know that, but I like the TWRPS interface better...
Thanks for the responses!

Hi. I am also in this predicament.
I had installed TWRP. Had issues with installing a ROM and installed CWM.
Was able to installed ROM using CWM.
Now I wanted to go back to TWRP more flexibility on my part like naming baks but even installing Goomanager, it does not have the "top right" option where I can install the recovery script.
Is there a way to reinstall TWRP without going back to stock and keeping my current ROM?
Thanks.

qwer43 said:
Now I wanted to go back to TWRP more flexibility on my part like naming baks but even installing Goomanager, it does not have the "top right" option where I can install the recovery script.
Click to expand...
Click to collapse
In Goomanager do you not see the option to install the script when you hit the menu button? That's where it was for me...

qwer43 said:
Hi. I am also in this predicament.
I had installed TWRP. Had issues with installing a ROM and installed CWM.
Was able to installed ROM using CWM.
Now I wanted to go back to TWRP more flexibility on my part like naming baks but even installing Goomanager, it does not have the "top right" option where I can install the recovery script.
Is there a way to reinstall TWRP without going back to stock and keeping my current ROM?
Thanks.
Click to expand...
Click to collapse
another twrp user yippe xD twrps the best recovery ive flashed cm 10 and many roms without a problem. Maybe you didnt follow flash instructions or what not... And yes delete all those nasty cwm blobs and **** they put when your done using it Go to goomanager and there should be an option for open recovery and that downloads and installs twrp for you

Yes, I had installed Goomanager but I dpnt see the option to install the script on the main page even on the top beside the search icon.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2

[Q] Installation aborted, what did I do wrong?

I downloaded CM 10.1 nightly build ( cm-10.1-20130130-NIGHTLY-d2tmo.zip ) and got the error Installation aborted. Did I do something wrong? I know it maybe a dumb question but... did I brick my phone??
This is what I got:
Finding update package...
Opening update package...
assert failed: getprop ("ro.product.device") == "
d2tmo" | | getprop ("ro.build.product") == "d2tmo"
E: Error in emmc/cm-10.1-20130130-NIGHTLY-d2tmo.zip
(Status 7)
Installation aborted.

Did you edit your build prop before hand? and no you're not bricked.

mt3g said:
Did you edit your build prop before hand? and no you're not bricked.
Click to expand...
Click to collapse
Oh, that's good! No, I didn't edit my build prop. What is a build prop?

Oh boy, what recovery are you using? I'm pretty sure you are using an old version and need to update... besides the 1-30 nightly is loaded with bugs I've been reading. restore your nandroid and update your recovery and wait for the next nightly.

and onseopm
mt3g said:
Oh boy, what recovery are you using? I'm pretty sure you are using an old version and need to update... besides the 1-30 nightly is loaded with bugs I've been reading. restore your nandroid and update your recovery and wait for the next nightly.
Click to expand...
Click to collapse
A little to over my head I guess. I think its clockworkmod recovery version 5 (CWM-Recovery-LTE-SGS3-v5).
Restore my nandroid? I don't think I made a restore point, after the error I just went back and rebooted..
Was I supposed to do that?
It looks to be working, I rebooted twice and I don't think I messed it up. Though now I'm paranoid..

Dove99x said:
A little to over my head I guess. I think its clockworkmod recovery version 5 (CWM-Recovery-LTE-SGS3-v5).
Restore my nandroid? I don't think I made a restore point, after the error I just went back and rebooted..
Was I supposed to do that?
It looks to be working, I rebooted twice and I don't think I messed it up. Though now I'm paranoid..
Click to expand...
Click to collapse
Yeah it's because you need to update cwm, make sure you flash the correct one.. And if its booting fine then you're ok, but you should always make a backup of a working ROM if your gonna do some tinkering with your phone as a safety precaution, it really bails you out at times
Sent from my SGH-T999 using xda premium

serio22 said:
Yeah it's because you need to update cwm, make sure you flash the correct one.. And if its booting fine then you're ok, but you should always make a backup of a working ROM if your gonna do some tinkering with your phone as a safety precaution, it really bails you out at times
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I'm in the process of backing up now. Is there anything special I need to do to upgrade my cwm recovery? I've heard updating cwm recovery could result in a soft brick, is that correct?

If you have rom manager just press update cwm.
(It actually says flash cwm)
If you don't have rom manager download it from the play store.
I wouldn't worry about bricking during this process
Sent from my SGH-T999 using xda premium

Dove99x said:
I'm in the process of backing up now. Is there anything special I need to do to upgrade my cwm recovery? I've heard updating cwm recovery could result in a soft brick, is that correct?
Click to expand...
Click to collapse
You don't need to worry about bricking if you use ROM manager as Android_Monster stated, it will flash the correct version too
Sent from my SGH-T999 using xda premium

Android_Monsters said:
If you have rom manager just press update cwm.
(It actually says flash cwm)
If you don't have rom manager download it from the play store.
I wouldn't worry about bricking during this process
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
So the whole issue of installations being aborted is because of the outdated cwm.
I asked if it'll do a soft brick because I did a google search and came across multiple posts warning the use of Rom Manager. Any way to uninstall CWM and replace it with something else.

Yes to installation abortion.
To replace CWM, just flash another recovery over it.

You can just get TWRP from goomanager from the play store. Just flash it over and you'll be good to go.

Dove99x said:
So the whole issue of installations being aborted is because of the outdated cwm.
I asked if it'll do a soft brick because I did a google search and came across multiple posts warning the use of Rom Manager. Any way to uninstall CWM and replace it with something else.
Click to expand...
Click to collapse
Yeah just install twrp from goo manager like mt3g.. I've used ROM manager to install and update mine but if you want to replace cwm you can flash twrp and it'll replace it
Sent from my SGH-T999 using xda premium

mt3g said:
You can just get TWRP from goomanager from the play store. Just flash it over and you'll be good to go.
Click to expand...
Click to collapse
Great... another error. Rooting isn't working out for me is it? Invalid MD5 sum from Goo Manager. What does that mean and what exactly can I do about it?
Nope, actually worked out after allowing download from unknown sources in security. Since I installed TWRP, can I delete the backup I made in clockworkmod recovery? I think its in my SD and its 3 GB. It titled "Clockworkmod" has folder titled "backup", then two folders "1970-04-23.05.07.43" and "1970-04-23.05.00.14".
I want to have space so that I can make a recovery using TWRP. I'm not sure if deleting this would cause more harm then not.

Dove99x said:
Great... another error..
Rooting isn't working out for me is it...
Invalid MD5 sum from Goo Manager. What does that mean and what exactly can I do about it?
Since I installed TWRP, can I delete the backup I made in clockworkmod recovery? I think its in my SD and its 3 GB.
Click to expand...
Click to collapse
It was probably just a bad download, try downloading that file again
Sent from my SGH-T999 using xda premium

serio22 said:
It was probably just a bad download, try downloading that file again
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
It worked, can I delete my Clockworkmod folder on my SD card? Its 3GB and I think its the backup I made before in clockwork. I'm afraid I might mess things up by deleting stuff, since I don't know what I'm doing. I want to delete that folder, go into TWRP and create a recovery.

Dove99x said:
It worked, can I delete my Clockworkmod folder on my SD card? Its 3GB and I think its the backup I made before in clockwork. I'm afraid I might mess things up by deleting stuff, since I don't know what I'm doing. I want to delete that folder, go into TWRP and create a recovery.
Click to expand...
Click to collapse
It should be fine, its kind of big for just a back up though.. Make the backup with twrp first and check where it puts the back up at.. When I used 4ext recovery with my previous phone, it put the backups in the cwm folder for some reason
Sent from my SGH-T999 using xda premium

serio22 said:
It should be fine, its kind of big for just a back up though.. Make the backup with twrp first and check where it puts the back up at.. When I used 4ext recovery with my previous phone, it put the backups in the cwm folder for some reason
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Thanks, you guys have been extremely helpful.
I'm about to install the rom now, I wanted your insight into if its a good rom and if I'm doing everything right.
- I've made a backup using TWRN
- Downloaded Titanium Backup, made another backup (Not sure what this will do)
- Changed Rom to AOKP Milestone 1 ( aokp_d2tmo_jb_milestone-1 )
- Downloaded Google Apps ( gapps-jb-20121212-signed )
Installation
- Run TWRN
- Going to wipe ( data/factory reset ) 3 times
- Going to wipe ( cache ) 3 times
- Select install zip from sdcard (First AOKP, then Google Apps)
- Reboot
Alright, does that look good to you? Do I have your blessings.

Dove99x said:
Thanks, you guys have been extremely helpful.
I'm about to install the rom now, I wanted your insight into if its a good rom and if I'm doing everything right.
- I've made a backup using TWRN
- Downloaded Titanium Backup, made another backup (Not sure what this will do)
- Changed Rom to AOKP Milestone 1 ( aokp_d2tmo_jb_milestone-1 )
- Downloaded Google Apps ( gapps-jb-20121212-signed )
Installation
- Run TWRN
- Going to wipe ( data/factory reset ) 3 times
- Going to wipe ( cache ) 3 times
- Select install zip from sdcard (First AOKP, then Google Apps)
- Reboot
Alright, does that look good to you? Do I have your blessings.
Click to expand...
Click to collapse
Looks good, but also wipe system
Sent from my SGH-T999 using xda premium

serio22 said:
Looks good, but also wipe system
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
What's your opinion on AOKP nightly build JB-MR1 ( aokp_d2tmo_jb-mr1_build-2 ). I was looking into this because it has 4.2.1 jellybean and it was suggested I avoid CM 10.1 nightly.

[Q] Hyperdrive Installation problem

Hi guys, I've been trying to flash the new Hyperdrive RLS11 on my AT&T Galaxy s3 and no matter what I do, my phone says cant open and aborts the installation. I can never get the Aroma installer to start. I do factory reset, wipe cache, dalvik, and format system, but it fails every time. Any ideas?

Could be a bad download. You could try grabbing it again. Also, is your recovery up to date?

xBeerdroiDx said:
Could be a bad download. You could try grabbing it again. Also, is your recovery up to date?
Click to expand...
Click to collapse
I downloaded it from 3 different of his mirrors none of which worked. Im of the latest version of Clockwork mod. could it be the new update from 6.0.3 to 6.0.3.1 on clockwork? or should i use something other than clockwork

you should use twrp.. check the md5 of your download after you download it for accuracy. try that.. if it doesnt work u can always flash cwm again

Flash in twrp. Get twrp by downloading goo manager app and selecting install open recovery
Also are you grtiing a status 7 error?
Sent from my SAMSUNG-SGH-I747 using xda premium

For whatever reasons, sometimes when flashing in cwm or twrp, you will have issues and installing the other custom recovery will allow you to flash the desired ROM. you obviously then have the option to return to the custom recovery you were previously running either because you prefer it or all your backups were made in it.

Alright thanks ill try it tonight, hopefully it works
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

B.domonoski said:
Alright thanks ill try it tonight, hopefully it works
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Some ROm's are picky or you have a bad download. Issues with downloading that rom seem quite common. I tend to lean more towards android file host than anything.

i'm i nthe same situation for the past 2 days i have been trying to install it , i had the problem that after flash and reboot it will reboot back to recovery , today that seems not to be happening anymore now i'm getting stuck on boot animation and i have tried every step fix anytihng you can think of and no luck , i'm running now thw rls 10 with no problems but this rls 11 is driving me crazy i'm doing a redownload se if that helps in anyway

I used twrp and it worked fine! Thanks guys
Sent from my SCH-I605 using xda app-developers app

I used CWM without a problem
"You stay classy San Diego"

B.domonoski said:
I used twrp and it worked fine! Thanks guys
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
awesome. Glad it worked for you... it can be a picky, but gorgeous rom.

Similar problem
Hey guys
I've gone through all the steps as instructed, but can't install HD RSL15 successfully. I downloaded the installation file from a mac which then automatically unzips the folder. Zipped it back up with 7zip and threw it on the phone. I went through all the prescribed steps using TWRP 2.6 and AndroidUnite's video on youtube (How To Install TWRP Recovery And Flash Custom ROM) as example . This is the 2nd time Ive downloaded the file and I switched over from CWM based on this thread's recommendations.
When it comes to installing the ROM the window ends up looking like this:
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Error flashing zip...
Updating partition files...
FAILED
Have I done something wrong during the previous steps (flashing, installing recovery) or does it have something to do with the method of zipping the files (tried fastest and store as compression options, doing store makes the file unreadable by the phone during recovery mode)? Please help