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)?
Related
Ok I'm really irritated right about now. I am unable to flash any custom ROMS on my phone. Actually let me rephrase, I can flash them but many things do not work. I have tried Wicked, FreeGS3 and CapROM. They all have the same issues. Let me explain.
Once the ROM is booted I get odd string of numbers and TXT in the status bar, (goes away, think nothing of it)
Root not avail/accessible by root apps.
Home button does not work
Play store missing
standard Google login prompt at first boot is missing, it never asks me to login
Using CWM 5.8.4.5 Touch Recovery
TMO GS3 Rooted with Odin no trip method
I don't get it. I am i just stuck using stock ROM? If anyone can help I would love you forever.
are you clearing /cache and dalvik-cache before you reboot to the custom rom?
mrmako777 said:
are you clearing /cache and dalvik-cache before you reboot to the custom rom?
Click to expand...
Click to collapse
If you mean clearing those after the install (in recovery completes) then no. Basically after the install I just reboot. Obviously clear and reset everything before I install though.
hd2Raz said:
Ok I'm really irritated right about now. I am unable to flash any custom ROMS on my phone. Actually let me rephrase, I can flash them but many things do not work. I have tried Wicked, FreeGS3 and CapROM. They all have the same issues. Let me explain.
Once the ROM is booted I get odd string of numbers and TXT in the status bar, (goes away, think nothing of it)
Root not avail/accessible by root apps.
Home button does not work
Play store missing
standard Google login prompt at first boot is missing, it never asks me to login
Using CWM 5.8.4.5 Touch Recovery
TMO GS3 Rooted with Odin no trip method
I don't get it. I am i just stuck using stock ROM? If anyone can help I would love you forever.
Click to expand...
Click to collapse
Touch recovery might be your problem
Sent from my SGH-T999 using Tapatalk 2
horr1blek1tten said:
Touch recovery might be your problem
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Really? A recovery can cause these kinds of issues. Haven't heard of that before. Any other thoughts? What recovery are you using?
Try TWRP 2.2.1.1
hd2Raz said:
Really? A recovery can cause these kinds of issues. Haven't heard of that before. Any other thoughts? What recovery are you using?
Click to expand...
Click to collapse
Yeah I've heard touch recovery has its problems so I don't use it. Try using the recovery rom manager gives you.
Sent from my SGH-T999 using Tapatalk 2
horr1blek1tten said:
Yeah I've heard touch recovery has its problems so I don't use it. Try using the recovery rom manager gives you.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
I use TWRP and have no problems.
Do a Factory reset, wipe cache, wipe dalvik cache, fix permissions.
If that doesn't work, flash stock and reroot and try again.
I use touch recovery 5.8.4.7 and flashed it with adb. I've flashed almost everything. Cyanogenmod and every other ROM. NEVER had a problem with an instalation. Or even lost IMEI. I think people specifically aren't reading over OP's and figuring out what's safest for their devices and end up with these kind of results. Just my input.
Sent from my SGH-T999 using xda premium
Use mskips tool for our phones. It does everything you can image and then some. I have been using his tools since the HD2 and no issues to date.
The odd string of numbers that flashes upon boot in the status bar sounds like it's just identifying your external sd card. Totally normal.
OK so nothing worked. TWRP did the same thing. Tried diff ROM, same thing. I flashed back to 100% stock, unrooted ROM. Wiped the phone in the standard Android recovery. Then I rooted again, installed TWRP and flashed my ROM of choice and voila. Everything works. Problem solved. Thanks all for the inputs.
Hi guys, so I was using wicked ROM, whenever I tried to boot into recovery, it just rebooted back to system. Odin'ed back to stock, flashed twrp through goo manager app, but still no use. Any help greatly appreciated
Sent from my Nexus 7 using xda premium
eggydrums said:
Hi guys, so I was using wicked ROM, whenever I tried to boot into recovery, it just rebooted back to system. Odin'ed back to stock, flashed twrp through goo manager app, but still no use. Any help greatly appreciated
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
What methods have you tried?
adb reboot recovery is the easiest way to get to recovery
Maybe try flashing CWM, seeing if that works, and then flashing TWRP (I've never flashed TWRP through Goo Manager so I don't know how that works)?
If you don't have adb set up, get quick boot from market and try recovery through that.
If that doesn't work, I honestly don't know. I'm assuming you've done the power off then volume up+home+power at the same time trick already.
EtherealRemnant said:
What methods have you tried?
adb reboot recovery is the easiest way to get to recovery
Maybe try flashing CWM, seeing if that works, and then flashing TWRP (I've never flashed TWRP through Goo Manager so I don't know how that works)?
If you don't have adb set up, get quick boot from market and try recovery through that.
If that doesn't work, I honestly don't know. I'm assuming you've done the power off then volume up+home+power at the same time trick already.
Click to expand...
Click to collapse
With the goo app, I can boot directly into recovery, but my issue is that I get to the Recovery's splash screen, it hangs there for a second and immediately reboots back to system. I'm thinking to get the stock recovery back and try again I'm really not sure what the Hecks going on
Sent from my Nexus 7 using xda premium
Mhm OK, got cwm working, guess I'll just use that one for the time being
Sent from my Nexus 7 using xda premium
eggydrums said:
Mhm OK, got cwm working, guess I'll just use that one for the time being
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I would highly recommend putting TWRP back on there. The CWM was more for testing... people have reported issues using CWM with certain ROMs. Glad you were able to get CWM on though.
Nothing wrong with CWM.
Aerowinder said:
Nothing wrong with CWM.
Click to expand...
Click to collapse
There are a number of ROMs that do not support CWM so that statement is false. FreeGS3 loses update functionality, for example.
Also, there have been complaints in the case of CWM touch of it being too easy to wipe your entire device.
Not to mention there is no Goo Manager functionality without TWRP as well.
Lots of benefits of TWRP versus CWM. I used CWM for years then had to switch to a modified TWRP for my MAXX and was more than happy when I found out the SGS3 used TWRP as well (although I wish we had the ROM slots like the MAXX though - that was actually cool)
The statement is not false. I think FreeGS3 hasn't been updated for 4.5 months? Maybe not the best example. And I still think you should use as few automated tools as possible where flashing is concerned (Goo/ROM Manager).
It can be easy to wipe the wrong partition in CWM, if you are careless or illiterate. In the 6 months that I've used it (nearly every day), I have never once wiped the wrong partition, or my entire device. Never had a backup that wouldn't restore.
I like some of what TWRP offers. But I still experience showstopping bugs with it on my device. At this time, the devs are unable to track down the cause of the problems.
Aerowinder said:
The statement is not false. I think FreeGS3 hasn't been updated for 4.5 months? Maybe not the best example. And I still think you should use as few automated tools as possible where flashing is concerned (Goo/ROM Manager).
It can be easy to wipe the wrong partition in CWM, if you are careless or illiterate. In the 6 months that I've used it (nearly every day), I have never once wiped the wrong partition, or my entire device. Never had a backup that wouldn't restore.
I like some of what TWRP offers. But I still experience showstopping bugs with it on my device. At this time, the devs are unable to track down the cause of the problems.
Click to expand...
Click to collapse
Don't get me wrong, I've used CWM on many devices for years and even have a premium license for ROM Manager but I've seen a number of ROMs explicitly say not to use CWM, FreeGS3 was just the first that came to mind. I don't flash often because quite frankly, I have no problems with Wicked v8 and see no reason to switch to anything else.
And I am neither careless nor illiterate but I have accidentally borked things using CWM before in the past (it was a modified CWM Touch recovery) and I was not happy.
I think most of the complaints about CWM these days though come from CWM Touch, not regular CWM. Sorry TWRP has issues for you.
OK, so I'm getting a new issue, I changed to AOKP and I had problems with the ROM saying I needed to wipe data, I did, the issue persisted for few reboots, now apps won't install, and for some reason the /data folder still displays apps from my previous ROM ugh I don't know what's happening
Oh and for some reason the app exchange service kept force closing
Sent from my Nexus 7 using xda premium
eggydrums said:
OK, so I'm getting a new issue, I changed to AOKP and I had problems with the ROM saying I needed to wipe data, I did, the issue persisted for few reboots, now apps won't install, and for some reason the /data folder still displays apps from my previous ROM ugh I don't know what's happening
Oh and for some reason the app exchange service kept force closing
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Which recovery? Try erasing data, cache, and system three times each and reinstalling the ROM... If that doesn't work you might consider doing a back up of everything internally stored on your phone and then wiping the internal storage entirely and starting over.
EtherealRemnant said:
Which recovery? Try erasing data, cache, and system three times each and reinstalling the ROM... If that doesn't work you might consider doing a back up of everything internally stored on your phone and then wiping the internal storage entirely and starting over.
Click to expand...
Click to collapse
I tried. I think for some reason, the recovery isn't wiping data, even though it says so. I'm using twrp
Managed to install apps through the play website, still no go with the play store app though
Sent from my Nexus 7 using xda premium
eggydrums said:
I tried. I think for some reason, the recovery isn't wiping data, even though it says so. I'm using twrp
Managed to install apps through the play website, still no go with the play store app though
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Hmmm... Have you tried doing it through CWM? Its starting to sound like your partitions are messed up.
EtherealRemnant said:
Hmmm... Have you tried doing it through CWM? Its starting to sound like your partitions are messed up.
Click to expand...
Click to collapse
I think that's a possibility I just tried through clockwork, and it's all good now but exchange service fcs here and there
Sent from my Nexus 7 using xda premium
eggydrums said:
I think that's a possibility I just tried through clockwork, and it's all good now but exchange service fcs here and there
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Did you fix permissions?
EtherealRemnant said:
Did you fix permissions?
Click to expand...
Click to collapse
I tried while I was in twrp, it failed, something about a an error "failed to chmod data/data/ email.apk" (not exactly like that)
Sent from my Nexus 7 using xda premium
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
If TWRP is asking for a password and not booting do this: Re odin recovery twrp 2.4.4.0, wipe ALL data, odin twrp 2.6.1.0 back on to the device, reboot recovery, re-wipe data, flash desired COMPATIBLE rom.
To sum up what I found, new encryption added to 4.0+ of android encrypts user and important file partitions, updating recovery basically screws that all up. Your device has no way of accessing those files without the encryption key which was never explicitly made, its just a background feature to help protect your data.
I know this isnt much but atleast some people wont have to search around as much.
Now I cant take any credit for this, I also couldnt really find any user that took credit for it either.
Update: Something about gapps is the catalyst for this issue. After I flash gapps i get 15 mins of solid system performance, after that I start to get app download errors. The device will continue to function normally with snag and hiccups but after rebooting it goes right back to bootlock and asking for a P/W in TWRP. And of course I find a couple thread talking about this fix after, sorry for the redundancy I guess.
Can any confirm that Gapps may be causing this? Or better yet, what is actually causing this?
Jataadroid said:
If TWRP is asking for a password and not booting do this: Re odin recovery twrp 2.4.4.0, wipe ALL data, odin twrp 2.6.1.0 back on to the device, reboot recovery, re-wipe data, flash desired COMPATIBLE rom.
To sum up what I found, new encryption added to 4.0+ of android encrypts user and important file partitions, updating recovery basically screws that all up. Your device has no way of accessing those files without the encryption key which was never explicitly made, its just a background feature to help protect your data.
I know this isnt much but atleast some people wont have to search around as much.
Now I cant take any credit for this, I also couldnt really find any user that took credit for it either.
Update: Something about gapps is the catalyst for this issue. After I flash gapps i get 15 mins of solid system performance, after that I start to get app download errors. The device will continue to function normally with snag and hiccups but after rebooting it goes right back to bootlock and asking for a P/W in TWRP. And of course I find a couple thread talking about this fix after, sorry for the redundancy I guess.
Can any confirm that Gapps may be causing this? Or better yet, what is actually causing this?
Click to expand...
Click to collapse
im seeing people popping on on my phones forums (note 2) getting this message....and def not gapps...i have latest 4.3 gapps for weeks now and never seen this message
What rom you using?
PA 3.99 I have been running solid for 12 hrs now but I haven't rebooted since the last time I had to redo this process. It does fix it though.
All my apps have been installing and functioning fine. One thing I did different is I didn't flash BMS kernel. I havent checked the other threads reporting this issue but does any one know if they were using BMS?
Sent from my SPH-L710 using xda app-developers app
Jataadroid said:
PA 3.99 I have been running solid for 12 hrs now but I haven't rebooted since the last time I had to redo this process. It does fix it though.
All my apps have been installing and functioning fine. One thing I did different is I didn't flash BMS kernel. I havent checked the other threads reporting this issue but does any one know if they were using BMS?
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Now I dont have TWRP asking for a password but PA_3.99 is stuck at the splash screen with the yellow sub. No longer an encryption issue it seems but now a new one entirely. At this point it exceeds my nooby knowledge of android and im stuck waiting for a kind soul to assist.
So please anybody have any idea? Or any idea how to define the issue better so i can get some help, it seems kernel or recovery related.
Is there a bootloader Im supposed to flash for 4.3? Im at a loss entirely.
Pls&thx
Just flash clockwork. Done
Sent from my SPH-L710 using xda app-developers app
I had the same problem, just once though. I booted into my ROM and all I needed to do was reinstall TWRP through Goomanager, then everything worked out fine. I updated from 2.6.0 to 2.6.1 at that point, so maybe that fixed my TWRP password problem. I did it about two weeks ago, so far no recovery issues. I used TWRP pretty intensely about a week ago to update to 4.3 and all went according to plan.
Shoot...I odin'd twrp 2.6.1.0 so many times I thought my phone would literally die. I didn't come from 2.6.0.1 ( not sure if that's the right) but instead several versions back.
Sent from my SPH-L710 using xda app-developers app
It wouldn't be a bad idea to implement a recovery password
Sent from my Nexus 5 using Tapatalk
alvintimothyjr said:
It wouldn't be a bad idea to implement a recovery password
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
It's kind of already been done.
Really...info?
Sent from my Nexus 5 using Tapatalk
Well, I don't know if this is how I'm supposed to go about doing this, but I've been having issues recently with Quantum rom, and was planning on posting them in the actual Quantum thread, but I need 10 posts to do that because 10 posts mean something important.
Anyways, Ive been fine previously just doing
1. Wipe Dalvik, cache, and system,
2. flashing rom and gapps
3. the wipe option you get after you flash (TWRP)
Ive been doing that since i started basically, until 1.9. Anything after 1.9, it either constantly crashes, has processes constantly stopping, or on one of the versions (2.1 i think) the screen would constantly flicker (which someone else mentioned happening in the thread). So i figured I should try a clean flash, so I try wiping everything and flashing, and doing the default factory reset option and flashing, neither of which helped. In fact, after doing the clean flash it made 1.9 stop working too, so I had to restore my 1.9 backup to get it working again.
Anywho, if anyone has any advice that could help me get the newer versions working that would be great, Thanks!
EDIT: I might try flashing a different rom, to see if the issues persist elsewhere, but firstly Id like to stay on Quantum, and secondly, iirc I tried one a different rom when 4.3 first started showing up in roms, and I kept having problems, to which I just went back to Quantum.
It sounds to me you have a bad download. Have you tried re-downloading the ROM? I run the Quantum ROM and I have had no issues whatsoever.
I'm also looking forward to your reply about flashing another ROM.
Sent from my SAMSUNG-SGH-I497 using Tapatalk
codemonkey98 said:
It sounds to me you have a bad download. Have you tried re-downloading the ROM? I run the Quantum ROM and I have had no issues whatsoever.
I'm also looking forward to your reply about flashing another ROM.
Sent from my SAMSUNG-SGH-I497 using Tapatalk
Click to expand...
Click to collapse
Well, I've tried flashing every version including and after 2.0, up to the current version, and have the same problems for each one. So i somewhat doubt that that's the problem. Ill probably try to flash somethign else some time tomorrow
DanCardin said:
Well, I've tried flashing every version including and after 2.0, up to the current version, and have the same problems for each one. So i somewhat doubt that that's the problem. Ill probably try to flash somethign else some time tomorrow
Click to expand...
Click to collapse
Could be your recovery too. I believe the Quantum ROM developer recommends CWM than TWRP.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
If you do decide to change to CWM, make sure you revert to your TouchWiz backup first since TWRP and CWM backups aren't compatible. My best recommendation is to re-download the newest version (2.35 as of 11/7/13), and wipe data/factory reset, wipe /cache, wipe system, wipe dalvik cache, then install ROM and Gapps, wipe cache and dalvik again, and reboot.
iirc, i noticed a fair enough number of people on TWRP that I would prefer to stay on it (since it *should* work). I did, however just update it, tried again. For 2.31, i just get constant for closes on phone and SystemUI, and others iirc. Im trying carbonRom right now, and its working perfectly fine.
EDIT: I did get one SystemUI force close, on it, but its literally constant on quantum sadly.
also tried a couple random other roms, all work, but no Quantum rom will work after 1.9. I also tried just flashing it and not gapps, and i end up with the same thing. Now its just constant force closes though. I don't think i remember seeing any flickery screens like i was getting around 2.1X i think it was.
What bootloader and firmware are you using with the later quantum ROMs.... I believe that the more recent ones need the dmg2 or emj2 boot and firmware to run properly.... Also what were your settings in trickster did you disable mp-dec and UV... Were you OC using stock quantum kernel etc.
Sent from my SGH-I747 using XDA Premium 4 mobile app
android_geek_0507 said:
What bootloader and firmware are you using with the later quantum ROMs.... I believe that the more recent ones need the dmg2 or emj2 boot and firmware to run properly.... Also what were your settings in trickster did you disable mp-dec and UV... Were you OC using stock quantum kernel etc.
Sent from my SGH-I747 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I think that the leaked 4.3 bootloader (whatever end code they gave it) isn't necessary yet, since it hasn't been officially released by AT&T. I'm personally holding off on flashing any 4.4 rom until they're a bit more mature and don't have as many hiccups (although pwncake's work is superb). The UV depends on your device and how it handles it, usually, mine needs +25 than stock but it doesn't seem to shorten battery life. All throughout 4.3, it was best to keep MP-Decision off since he built one into the rom. In the case of 4.4, IIRC from Quantum v3 beta3 and forward, he removed his own MP- Decision, so you could keep it switched on.
android_geek_0507 said:
What bootloader and firmware are you using with the later quantum ROMs.... I believe that the more recent ones need the dmg2 or emj2 boot and firmware to run properly.... Also what were your settings in trickster did you disable mp-dec and UV... Were you OC using stock quantum kernel etc.
Sent from my SGH-I747 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I just flash the ROM and boot. If I should be flashing a seperate firmware slash bootloader, I'm not (and never have to my knowledge). I couldnt have gotten to the trickster settings if i wanted to due to the constant force closes.
Would anyone know why when I enable ART mode on Quantum 4.4 Beta3 Rom, my phone continually has pop up messages with unexpected errors? -Such as calendar storage issues or the google keyboard(This should probably be in the ROM section but I can't write there.)
DanCardin said:
I just flash the ROM and boot. If I should be flashing a seperate firmware slash bootloader, I'm not (and never have to my knowledge). I couldnt have gotten to the trickster settings if i wanted to due to the constant force closes.
Click to expand...
Click to collapse
Can't run Quantum either. Same boat. I think it's an issue with the Core kernel and Rev0 processors.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
I tried flashing the new beta 8 of v3, and it worked with the odd restart and FC on the side. But the restarts were starting to get a bit annoying so I tried reflashing, and now I just get infinite boot animations no matter what I do. And if I try to restore my nandroid backup, there's this flash every 2 or 3 seconds around the boot animation. Sigh
EDIT: actually, completely reflashing works, but still ends up with the random reboots when doing random things
DanCardin said:
I tried flashing the new beta 8 of v3, and it worked with the odd restart and FC on the side. But the restarts were starting to get a bit annoying so I tried reflashing, and now I just get infinite boot animations no matter what I do. And if I try to restore my nandroid backup, there's this flash every 2 or 3 seconds around the boot animation. Sigh
EDIT: actually, completely reflashing works, but still ends up with the random reboots when doing random things
Click to expand...
Click to collapse
I get the same thing...
supahdaniel said:
I get the same thing...
Click to expand...
Click to collapse
sorry to hear of your problems. it is not the rom. enough folks are running it and I have had flawless installs. Read the OP and follow the directions, it works.
there is a new TWRP (from their site) that I downloaded as a .tar file and flashed with odin. flashes 4.4 roms now so you might try that rout.
my suggestion, in its limited knowledge is this:
put the rom, superuser, and the gapps on your SD card.
Reboot into the new TWRP and format the system- your phone is now blank.
install rom zip
install superuser zip
reboot.
first boot may take a bit, but not forever. Set up CM stuff and go from there
---------- Post added at 12:29 PM ---------- Previous post was at 12:17 PM ----------
Demminex said:
Would anyone know why when I enable ART mode on Quantum 4.4 Beta3 Rom, my phone continually has pop up messages with unexpected errors? -Such as calendar storage issues or the google keyboard(This should probably be in the ROM section but I can't write there.)
Click to expand...
Click to collapse
search the quantum thread about google settings. you have to turn on google now and disable notifications. also, I've been using the swift keyboard and don't have to deal with the google or android keyboard. that seems to have helped.
enable art after loading apps and be prepared for a wait for android to upgrade.