The title pretty much says it all. This has been going on for a while now, and it's starting to annoy me. Does anybody have a fix for this? I couldn't seem to get any of the fixes from other Galaxy S devices to work.
did you revert to stock from cm7?
SpaceToast7 said:
The title pretty much says it all. This has been going on for a while now, and it's starting to annoy me. Does anybody have a fix for this? I couldn't seem to get any of the fixes from other Galaxy S devices to work.
Click to expand...
Click to collapse
The only time I have seen this happen is when returning to stock from either the CM7 betas or any of the ROMs built off of it, and the reason for it is you lost your EFS data and unless you have a backup of that (CWM backups DO NOT have this backed up).
If you do indeed have an EFS backup then you can use Zaclimon's recovery thread and just add the EFS to that, that is the proper fix.
If you where a total newb like I was and completely lost it because you thought a CWM backup was enough, the only "temporary" fix is to flash Klin's IcyFusion, Han's Etheral or Dream Ultra then reboot into CWM recovery and "wipe data / factory reset" then reboot player, this will restore the boot menu and lockscreen for aslong as you run any of those ROM's but if you go back to stock it will vanish again.
Well, I somehow lost it when I wiped data on klin's klassic. A restore of data fixed it, and I haven't wiped my data since or gone back to stock so idk if it is still there.
Sent using Tapatalk
Thanks. I guess i will be using one of those roms you mentioned.
UPDATE: Ethereal did not fix EFS. As a matter of fact, it broke my home button.
SpaceToast7 said:
Thanks. I guess i will be using one of those roms you mentioned.
UPDATE: Ethereal did not fix EFS. As a matter of fact, it broke my home button.
Click to expand...
Click to collapse
Using Zaclimon's recovery method to go back to stock is the only way i've been able to fix the home button when Ethereal broke mine (this seams to be another side effect of losing the efs). restore to factory with zac's method thru heimdall (using a different usb port other then the one used for Odin) then Odin flash to Icy Fusion and Terrasilent kernel and follow previous instructions.
I did go back to stock rooted, and i think i will be staying there for the forseeable future because it seems that there arent any mature kernels or ROMs for this device - too unstable.
At any rate, am i correct in assuming that my EFS issues are related to (the abomination that is) TouchWiz, and that AOSP builds of Android do not have this issue? Ive never heard of this outside of Samsung devices.
Sent from my YP-G1 using xda app-developers app
SpaceToast7 said:
I did go back to stock rooted, and i think i will be staying there for the forseeable future because it seems that there arent any mature kernels or ROMs for this device - too unstable.
At any rate, am i correct in assuming that my EFS issues are related to (the abomination that is) TouchWiz, and that AOSP builds of Android do not have this issue? Ive never heard of this outside of Samsung devices.
Sent from my YP-G1 using xda app-developers app
Click to expand...
Click to collapse
I don't think so, what happened to me was I flashed one of the CM7 beta's and since they convert every partition from rfs to mtd it messed with my efs partition and so since I didn't have a backup of the EFS it was lost (CWM backups DO NOT backup the efs), from what I have gathered it holds your serial number and stuff like that which is why the deviceID hack implemented in Icy Fusion is able to "fill in the blanks" and that is what causes it to come back while on that ROM, I don't see how it can have anything to do with touchwiz, I use LauncherPro myself.
Icy Fusion and Dream Ultra are stable ROM's I haven't had any problems with them (other then Dream Ultra coming up in Russian after doing a wipe data/factory reset, but thats easy enough to fix) and the Terrasilent kernel is totally functional as long as you don't reboot into recovery on a ROM where you've converted all partitions to ext4, just load up a program like Tegrak or my choice of No Fills CPU tuner and change the governor to smartass V2. I couldn't conceive running stock at this point.
This phone was an insurance replacement from ATT, so alway a bit wary of these refurbished phones.
So for the longest time it has always been a bit glitchy, hanging, and unstable. I assumed it was a software problem, and something i had done wrong when flashing...but now I am wondering if maybe my phone is a lemon. Lately it has been rebooting randomly on its own,
I wanted to try flashing back to stock, just to start from scratch, and I did with Da G's stock rom . Then i just rooted it with Da G's root, and put on CWR. Then I flashed King Kang Rom. It's been still real buggy. Maybe I need to to stock ICS or JB then flash a ROM? OR maybe it's just this phone....either way not real happy with the stability i've been dealing with.
If youve tried multiple roms and stock roms and its still buggy then its probably the phone, I have got so many replacement phones that were duds
Are you doing a wipe between all those roms or just flashing one over the other? That could be a major problem that is easily fixed.
Yes, i do full wipes/factory reset in CWM every time.
I know i have seen some guys say you must flash like 3 times, so maybe i'm not flashing it enough times or something..? i also saw someone say don't touch your phone for 15 minutes after flashing. i have no idea if these tricks actually work or what. doesn't seem to be a definitive rule book on how to flash the right way
How are you restoring your apps? TB or letting Play reinstall them?
using TB. I usually do a just apps reinstall, then data
Was the TB backup from a different version of android, i.e. GB, ICS then installed on JB?
yes, i did create it on an ICS rom. you think that could be causing me problems?
Good possibility. I had the same issue. Moved from CM9 to CM10 and restored through TB. Lots of FC and reboots. Wiped and let Play reinstall everything, now its smooth.
great thought and worth a shot if that's what could be causing a problem. so did you lose all your data then with all apps? msgs, etc? sucks to start from complete scratch. i'll even miss call log
Lost data, but was able to d/l everything else. Messages and call logs were gone. It is worth it to have a working phone with out glitches. Let me know if it works.
Well a good test is to install a known solid ics problem free ROM like Padawan or Black ice? (exact name escapes me). If it works for u then over clock it to 1836 with setcpu and u will have a ROM VERY close to the JB rom smoothness but actually works.
If u still have problems then u may very well have a flaky phone.
(Oh yeah don't get to worried about stuff like wipe 3 times etc...old wifes tales. I haven't done that for over a year on 3 android phones. ). Also it is Safe to restore apps AND data with titaniumb (just not system data).
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
+1 on the old wives tale. Seems more like a placebo effect. I only wipe once, and I've flashed roms on tons of phones.
Sent from my Galaxy Nexus using xda premium
tried installing padawan...so far so good, have not overclocked yet....will report back
Some roms will format your system partition prior to flashing the rom while others do not.
Beyond the wipe of data, cache, dalvik and such, it is wise to go into " mounts and storage" and format the system partition while in CWM recovery.
This ensures that nothing remains on the device before the new rom image is pushed to the system partition.
I agree that wiping 3 times is a bit over the top, but wiping the entire image base before flashing a new one is almost always mandatory.....g
For future reference, you can back up call and sms logs and restore them without causing lags or fc. The logs are simple .xml files.
Hey guys,
I just got a few questions with this,
Will i lose my apps, theme and such when installing only a ROOT?
Also what do you guys prefer as ROOT method goes, Chainfire and Odin?
I've seen a ROOT BAT program a while ago that realy did everything for you, i just can't remember the name at the moment...
With that i would also like to ask what happens if i update my device? Will i still be able to update it when Samsung pushes a new update ?
Would i need a custom flash recovery? I used to have a phone wich i did it on, But as this is more of my expensiver phone i aint looking to realy risk it. and due all my apps info etc, has well over 150 apps.
Thanks everybody
Bump,
Sorry if nagging but i'm kinda in a rush, if anyone could help me a little?
I basicly know how you most likely root and stuff, just wanna be sure about a few things and what program/apk is best to get into the S3 at 4.3 firmware
Dr.Luigi said:
Hey guys,
I just got a few questions with this,
Will i lose my apps, theme and such when installing only a ROOT?
Click to expand...
Click to collapse
You might lose data.
Few things can be saved, because you have an official (so unrooted) device.
Also what do you guys prefer as ROOT method goes, Chainfire and Odin?
Click to expand...
Click to collapse
Odin is needed, Chainfire root is the most famous method.
I've seen a ROOT BAT program a while ago that realy did everything for you, i just can't remember the name at the moment...
Click to expand...
Click to collapse
Personally I did root with an automatized software, called Unlock Flash.
The better one is Framaroot, but I don't know how it works.
With that i would also like to ask what happens if i update my device? Will i still be able to update it when Samsung pushes a new update ?
Click to expand...
Click to collapse
You'll lost Samsung warranty (no more assistance support, excluded mine and use for software problems [emoji6]), update check and the access to some proprietary apps (You shouldn't be able to download/update from Galaxy Apps).
Normally when you root the device, a CWM custom recovery is included, otherwise you can simply flash via Odin the excellent Philz Recovery, so you'll be able to flash a new Samsung-based rom (ARHD, ArchiPort, Omega, Imperium... aborting the limited stock) or try the greatful AOSP roms (CyanogenMod, Omnirom, PacRom, etc.).
Also custom kernels (BOEFFLA, Googy Max, ArchiKernel and some others, I prevent to cite you outdated ones) and mods (everything!).
Would i need a custom flash recovery? I used to have a phone wich i did it on, But as this is more of my expensiver phone i aint looking to realy risk it. and due all my apps info etc, has well over 150 apps.
Thanks everybody
Click to expand...
Click to collapse
Highly recommended, as I said you need this to install a new rom and any other zip file.
For the rest... I haven't understood you.
Can you explain better last things?
Simone98RC said:
You might lose data.
Few things can be saved, because you have an official (so unrooted) device.
Odin is needed, Chainfire root is the most famous method.
Personally I did root with an automatized software, called Unlock Flash.
The better one is Framaroot, but I don't know how it works.
You'll lost Samsung warranty (no more assistance support, excluded mine and use for software problems [emoji6]), update check and the access to some proprietary apps (You shouldn't be able to download/update from Galaxy Apps).
Normally when you root the device, a CWM custom recovery is included, otherwise you can simply flash via Odin the excellent Philz Recovery, so you'll be able to flash a new Samsung-based rom (ARHD, ArchiPort, Omega, Imperium... aborting the limited stock) or try the greatful AOSP roms (CyanogenMod, Omnirom, PacRom, etc.).
Also custom kernels (BOEFFLA, Googy Max, ArchiKernel and some others, I prevent to cite you outdated ones) and mods (everything!).
Highly recommended, as I said you need this to install a new rom and any other zip file.
For the rest... I haven't understood you.
Can you explain better last things?
Click to expand...
Click to collapse
Well i would only be intrested in ROOT if i can keep all of my files, apps, widgets and such,
I would have done a new ROM if i wouldnt have had so many apps, it would take hours if not days to get everything back as it used to be would be a rather pain in the ***.
Thanks for your help!
Been a while when i unlocked my old device and rommed it undervoltaged it etc etc.
Dr.Luigi said:
Well i would only be intrested in ROOT if i can keep all of my files, apps, widgets and such,
I would have done a new ROM if i wouldnt have had so many apps, it would take hours if not days to get everything back as it used to be would be a rather pain in the ***.
Thanks for your help!
Been a while when i unlocked my old device and rommed it undervoltaged it etc etc.
Click to expand...
Click to collapse
My same problem: too many apps to be restored.
With MyBackupsPRO, the only working without root permissions, you can only keep some settings, contacts, SMS and MMS, then all your apps and games... but without any relative data.
Because as I said you're on an unrooted/official system.
I think you are using an external SD for documents and multimedia files, when you run the first start of your custom rom (highly recommend for the updates, instead the limited stock), be sure that the "Restore data from Google" option is checked.
A discrete help for you, better than nothing.
You have to think that when you did root, backups will be complete, via the greatful Titanium Backup or via recovery with Nandroid backup (my words should be useless if you already have experience with an old device).
Good hacking
As Samsung-based roms I suggest you Android Revolution HD 4.3 or ArchiPort to get the new and officially unsupported 4.4 system.
Pro:
-Compatibility with other Samsung devices;
-Much better camera stabilization than AOSP roms.
Con:
-Touchwiz is heavy for RAM memory and CPU performance;
-Many AOSP functions are completely removed or altered.
As AOSP rom I suggest you CyanogenMod 11, the M builds to have a more stable system, the nightlies for daily updates and less (but always enough) stability.
Pro:
-Latest updates daily/monthly available;
-Many features, AOSP and Cyanogen specific;
-Fully configurable, launcher can be completely replaced, at opposite of Samsung-based roms;
-Greater performance than Samsung-based roms.
Con:
-Some little bug;
-Poor compatibility with Samsung devices and proprietary apps.
As custom kernel, no better one than BOEFFLA: obviously OC and UV support, then lots of functions such "Touch to Wake", a great audio engine, zRAM support, a rich choice of governors and schedulers... it's available for Samsung and many AOSP roms.
Simone98RC said:
My same problem: too many apps to be restored.
With MyBackupsPRO, the only working without root permissions, you can only keep some settings, contacts, SMS and MMS, then all your apps and games... but without any relative data.
Because as I said you're on an unrooted/official system.
I think you are using an external SD for documents and multimedia files, when you run the first start of your custom rom (highly recommend for the updates, instead the limited stock), be sure that the "Restore data from Google" option is checked.
A discrete help for you, better than nothing.
You have to think that when you did root, backups will be complete, via the greatful Titanium Backup or via recovery with Nandroid backup (my words should be useless if you already have experience with an old device).
Good hacking
As Samsung-based roms I suggest you Android Revolution HD 4.3 or ArchiPort to get the new and officially unsupported 4.4 system.
Pro:
-Compatibility with other Samsung devices;
-Much better camera stabilization than AOSP roms.
Con:
-Touchwiz is heavy for RAM memory and CPU performance;
-Many AOSP functions are completely removed or altered.
As AOSP rom I suggest you CyanogenMod 11, the M builds to have a more stable system, the nightlies for daily updates and less (but always enough) stability.
Pro:
-Latest updates daily/monthly available;
-Many features, AOSP and Cyanogen specific;
-Fully configurable, launcher can be completely replaced, at opposite of Samsung-based roms;
-Greater performance than Samsung-based roms.
Con:
-Some little bug;
-Poor compatibility with Samsung devices and proprietary apps.
As custom kernel, no better one than BOEFFLA: obviously OC and UV support, then lots of functions such "Touch to Wake", a great audio engine, zRAM support, a rich choice of governors and schedulers... it's available for Samsung and many AOSP roms.
Click to expand...
Click to collapse
Thanks for the great help,
I aint realy sure yet realy,
But isnt there a way you can simple backup almost everything with the PC?
I thought that was faster, then root it and get those back up on the phone with the PC?
Youve made me thinking realy as my phone was getting slower, Samsung OS isnt that great quiet slow indeed,
I might just drop a few games i dont play realy, so i can get my faster phone back as it used to be.
I used to love tweaking my phone realy, till it broke due rain, was a quiet cheap phone 150e or so.
Do you mind giving your SKYPE or Steam? so i could ask you there, Its been 2 years when i did this, some are kinda floating around in my head but i just cant remember it all anymore.
http://forum.xda-developers.com/gal...msung-galaxy-s3-unified-toolkit-v8-0-t1979290
This is what i meant, Its simple and all in 1, just aint sure if its still up to date?
Via ADT Development Tool, you can do the "adb backup" command, but I think it will include the bootloader, so you'll restore the official and unrooted device state.
But I'm not sure, I never used to backup via PC.
Games are almost innocue, except for notification services who consume a bit of resources.
Can you tell me the heavier apps you're using?
According to your words, having too many apps you're not very satisfied about your performance... or I'm wrong?
Simone98RC said:
Via ADT Development Tool, you can do the "adb backup" command, but I think it will include the bootloader, so you'll restore the official and unrooted device state.
But I'm not sure, I never used to backup via PC.
Games are almost innocue, except for notification services who consume a bit of resources.
Can you tell me the heavier apps you're using?
According to your words, having too many apps you're not very satisfied about your performance... or I'm wrong?
Click to expand...
Click to collapse
Ye it used to be quiet a bit faster, Might be Samsung OS i forgot the name of the OS but anyhow, wizard or something,
Oh well, i will just do it i guess and i will see on the road what apps i need, the rest clearly seems that i dont need em if i never use em.
I'm guessing that the best would be Clockwork recovery and the SUroot? together with cyanogen ROM and buffalo.
As apps goes its basicly my home screen wich has quiet some widgets and such, all diffrent apps, in some folders like 100 apps etc.
Dr.Luigi said:
Ye it used to be quiet a bit faster, Might be Samsung OS i forgot the name of the OS but anyhow, wizard or something,
Oh well, i will just do it i guess and i will see on the road what apps i need, the rest clearly seems that i dont need em if i never use em.
I'm guessing that the best would be Clockwork recovery and the SUroot? together with cyanogen ROM and buffalo.
As apps goes its basicly my home screen wich has quiet some widgets and such, all diffrent apps, in some folders like 100 apps etc.
Click to expand...
Click to collapse
SuperSU is included in CF-Root and so is the most known, but Superuser (from Clockworkmod, the other Superuser is obsolete!) is a great open source alternative.
The best recovery is Philz, always based on CWM, but with extra and TWRP functions.
CyanogenMod yes, is the better choicr and also the easiest choice for root newbies.
Ps Buffalo is a kernel? If it's true, try BOEFFLA, is considered absolutely the best.
Simone98RC said:
SuperSU is included in CF-Root and so is the most known, but Superuser (from Clockworkmod, the other Superuser is obsolete!) is a great open source alternative.
The best recovery is Philz, always based on CWM, but with extra and TWRP functions.
CyanogenMod yes, is the better choicr and also the easiest choice for root newbies.
Ps Buffalo is a kernel? If it's true, try BOEFFLA, is considered absolutely the best.
Click to expand...
Click to collapse
Well i meant boeffla of course, Well i cant get it to work, What are the keys to get into TWRP recovery?
As in download mode it tells me its custom, but i cant get into it..
tryed quiet a few combis already
Dr.Luigi said:
Well i meant boeffla of course, Well i cant get it to work, What are the keys to get into TWRP recovery?
As in download mode it tells me its custom, but i cant get into it..
tryed quiet a few combis already
Click to expand...
Click to collapse
Edit:
Tryed again, i cant reboot if i did it would get the old recovery back, so in a push method it worked,
Now SuperSU, i might get a ROM but aint sure yet, Do kernels work on the stock rom aswell?
Dr.Luigi said:
Edit:
Tryed again, i cant reboot if i did it would get the old recovery back, so in a push method it worked,
Now SuperSU, i might get a ROM but aint sure yet, Do kernels work on the stock rom aswell?
Click to expand...
Click to collapse
Yes, BOEFFLA works also on stock rom (make sure to flash the correct zip file)... but I haven't understood your problem: can't reboot, old recovery back... what?
Simone98RC said:
Yes, BOEFFLA works also on stock rom (make sure to flash the correct zip file)... but I haven't understood your problem: can't reboot, old recovery back... what?
Click to expand...
Click to collapse
Ye nevermind that,
The problem is when i flashed my recovery, that when i reboot it switched automaticly back to the orginal stock recovery,
Only way to repair this was to not reboot, but goto the Philz recovery directly and reinstall the recovery program,
Also rooted it now,
So i can simple install Boefflo on my S3 international, With stock rom and ROOT, philz recovery?
If so that would be sweet ^^
As it should be more sufficient as far as battery goes, and a small overclock to like 1.6Ghz is reasonable ive heard,
1.8 is to high if i can believe those on some forums.
Since the last stable release you can overclock up to 1704 Mhz... and no more 1.5 Ghz step, I don't know the reason.
As I said, BOEFFLA works almost on every rom, but you habe to flash a different zip file for Samsung and AOSP roms.
Why can't you get a custom recovery? Are you sure to flash them reproducing properly the reported Odin guide (what to check in app, where to write file, etc.)?
It's a strange problem, rom "might" be cause by replacing the new recovery with the stock one, I think, but I'm not absolutely sure.
Simone98RC said:
Since the last stable release you can overclock up to 1704 Mhz... and no more 1.5 Ghz step, I don't know the reason.
As I said, BOEFFLA works almost on every rom, but you habe to flash a different zip file for Samsung and AOSP roms.
Why can't you get a custom recovery? Are you sure to flash them reproducing properly the reported Odin guide (what to check in app, where to write file, etc.)?
It's a strange problem, rom "might" be cause by replacing the new recovery with the stock one, I think, but I'm not absolutely sure.
Click to expand...
Click to collapse
Well like i said i've fixed that,
The standard way to flash doesnt work, As once i get booted in Samsung ROM, It fixes it, So you have to goto your Recovery immeaditly when youve flashed it, and flash it again in the custom recovery, and then it does work.
Well i will see, aint sure yet if i will do it the kernel and romming.
Thanks for the help
Dr.Luigi said:
Well like i said i've fixed that,
The standard way to flash doesnt work, As once i get booted in Samsung ROM, It fixes it, So you have to goto your Recovery immeaditly when youve flashed it, and flash it again in the custom recovery, and then it does work.
Well i will see, aint sure yet if i will do it the kernel and romming.
Thanks for the help
Click to expand...
Click to collapse
Here is also a great kernel. Check this out http://forum.xda-developers.com/gal...04-googy-max2-kernel-2-3-1-cm-camera-t2517875
Ladies and Gentlemen, I apologize if this question has already been asked. I did a quick search on the forums as well as google, and couldn't find a satisfactory answer.
Is it better to use F2FS or EXT4 on the OnePlus X?
I have done a lot of flashing of devices over the past few years, but this is one aspect I've never touched.
Opinions? Will I notice an improvement if I switch to F2FS, or will it cause more headaches than its worth?
Uhm, why couldn't you just change and see?
Well for me I don't know if a feel the change but you will get better antutu (at least 3k points more) for sure.
dgrasley said:
Ladies and Gentlemen, I apologize if this question has already been asked. I did a quick search on the forums as well as google, and couldn't find a satisfactory answer.
Is it better to use F2FS or EXT4 on the OnePlus X?
I have done a lot of flashing of devices over the past few years, but this is one aspect I've never touched.
Opinions? Will I notice an improvement if I switch to F2FS, or will it cause more headaches than its worth?
Click to expand...
Click to collapse
changed to f2fs, faced quite a lot of lags and stuttering not worth it... ext4 is buttery smooth specially after 2.1.3-X.
if you do plan on changing it however, do a backup of everything from your internal sd, it gets wiped along with the partition you are converting.
Did you guys change your system to F2FS or just the data and cache?
stu5797 said:
Did you guys change your system to F2FS or just the data and cache?
Click to expand...
Click to collapse
Only data & cache.
Sent from my ONE E1005 using Tapatalk
I'm asking myself the very same question. I don't have my opx yet but after reading through several threads I'll will first unlock bootloader, reflash oos and flash bluspark kernel but I won't Flash twrp recovery to Keep getting ota updates.
Regarding the question to Change to f2fs filesystem I'm still unsure.
The creator of boeffla kernel states this:
"This said, I will definitely NEVER implement:
•f2fs - it is known to cause various issues and compatibility problems"
I also found a post of the bluspark kernel creator:
http://forum.xda-developers.com/showpost.php?p=66047511&postcount=1390
"..There is no issues with f2fs and it's stable enough to be part of upstream stable and mainline linux kernel branches. And to be used by default by OEM like Samsung, Motorola and others.
Your problem came probably by derping the partition header/layout with all the reboots and such, since you changed fs and got the same.
It happens in other devices with other fs sometimes, nothing to do with f2fs not being stable..."
What do you guys think? Are there significant reallife benefits of f2fs in speed or other parts?
trohn_javolta said:
I'm asking myself the very same question. I don't have my opx yet but after reading through several threads I'll will first unlock bootloader, reflash oos and flash bluspark kernel but I won't Flash twrp recovery to Keep getting ota updates.
Regarding the question to Change to f2fs filesystem I'm still unsure.
The creator of boeffla kernel states this:
"This said, I will definitely NEVER implement:
•f2fs - it is known to cause various issues and compatibility problems"
I also found a post of the bluspark kernel creator:
http://forum.xda-developers.com/showpost.php?p=66047511&postcount=1390
"..There is no issues with f2fs and it's stable enough to be part of upstream stable and mainline linux kernel branches. And to be used by default by OEM like Samsung, Motorola and others.
Your problem came probably by derping the partition header/layout with all the reboots and such, since you changed fs and got the same.
It happens in other devices with other fs sometimes, nothing to do with f2fs not being stable..."
What do you guys think? Are there significant reallife benefits of f2fs in speed or other parts?
Click to expand...
Click to collapse
Are you sure you can keep OTA with a custom kernel, even when you won't flash TWRP? I do not think so, since OTAs are designed for completely unmodified systems.
I am pretty sure that Lord Boeffla means he won't implement F2FS since it's pretty unstable in general (not having any experience with it though)
and BluSpark kernel creator means that it's as stable as it gets (as "stock" with F2FS), so no disadvantages with his kernel when using it, but still not better than without it.
The only thing I would use F2FS for is cache. It can cause data corruption and using it as a filesystem can corrupt your internal SD card. It isn't safe. Stick with EXT4
mafioso16 said:
Are you sure you can keep OTA with a custom kernel, even when you won't flash TWRP? I do not think so, since OTAs are designed for completely unmodified systems.
Click to expand...
Click to collapse
Yeah..sounds logical..I just saw that there's a way to keep OTA by not flashing a custom recovery, just booting one from pc here:
http://forum.xda-developers.com/oneplus-x/general/discussion-how-to-root-oneplus-x-t3242830
Now I see he's basically restoring a previous backup of stock rom because of root. Then update and reroot without flashing a custom recovery.
ok..bluspark states one should reflash the rom before flashing kernel....
So if I want to get the latest update I'll just look here on xda for the original rom.
Flash that, flash kernel and reroot. Right? So there's also no reason not to flash twrp recovery. If an OTA update hits, I will see it on xda. Period.
Am I right?
I guess I'm making my life hard for no reason if I later will just stick to completely to a custom rom. But I want to give OxygenOS a chance. I think it's great to get a device with a stock rom that's not completely bloated and has exaggerated ui changes.
trohn_javolta said:
Yeah..sounds logical..I just saw that there's a way to keep OTA by not flashing a custom recovery, just booting one from pc here:
http://forum.xda-developers.com/oneplus-x/general/discussion-how-to-root-oneplus-x-t3242830
Now I see he's basically restoring a previous backup of stock rom because of root. Then update and reroot without flashing a custom recovery.
ok..bluspark states one should reflash the rom before flashing kernel....
So if I want to get the latest update I'll just look here on xda for the original rom.
Flash that, flash kernel and reroot. Right? So there's also no reason not to flash twrp recovery. If an OTA update hits, I will see it on xda. Period.
Am I right?
I guess I'm making my life hard for no reason if I later will just stick to completely to a custom rom. But I want to give OxygenOS a chance. I think it's great to get a device with a stock rom that's not completely bloated and has exaggerated ui changes.
Click to expand...
Click to collapse
I used the same tutorial on how to "survive" OTAs too, but that indeed comes with restoring the backup and updating normally or through stock recovery. There is no need to keep full stock OOS after you have a full backup through booted TWRP. Besides, you first flash TWRP, then root, then kernel. I do not know if this is a must but it'd the usual way to go. In summary: if you have a nandroid backup go and have fun, but don't go too crazy .
Hey Guys. I currently have CM13 and TWRP recovery. I'm slightly confused on how I should try out the latest OOS 3.1.
Can I simply flash the OOS zip through TWRP? Or will I need to flash the stock recovery, flash 3.0.2 and then flash 3.1?
Any guidance here for a quicker turnaround will be helpful.
Thanks!
You need a clean flash. The way I prefer to do it is to get the pro version of Titanium Backup, and backup all your user apps. You can do the system apps if you think you might return to CM. You can also dump the backup to your PC or an OTG USB if you want. When you're ready to flash, go into TWRP and wipe all except Storage, then flash the OOS zip. When you get back in and setup, get Titanium Backup again, and restore your backed up user apps. Only do the user apps, system apps from CM will likely fail. You may want to stay away from any OTA updates though, I think it borks TWRP so you have to re-do all of that, maybe someone else can confirm this because I'm not 100% sure. Happy flashing, let us know how it goes.
My device never goes to deep sleep mode on 3.1.0.
Please dont go to 3.1.0. Its is very very bad for battery
level5music said:
You need a clean flash. The way I prefer to do it is to get the pro version of Titanium Backup, and backup all your user apps. You can do the system apps if you think you might return to CM. You can also dump the backup to your PC or an OTG USB if you want. When you're ready to flash, go into TWRP and wipe all except Storage, then flash the OOS zip. When you get back in and setup, get Titanium Backup again, and restore your backed up user apps. Only do the user apps, system apps from CM will likely fail. You may want to stay away from any OTA updates though, I think it borks TWRP so you have to re-do all of that, maybe someone else can confirm this because I'm not 100% sure. Happy flashing, let us know how it goes.
Click to expand...
Click to collapse
Not an issue with Titanium backup. I carry the load of backups along regularly.
I was concerned about flashing it via TWRP, which you confirm shouldn't be a problem. And I guess it shouldn't overwrite my recovery too? Perfect. I will try and spend some time on this over the weekend to compare with the CM. Thanks!
Techgod said:
My device never goes to deep sleep mode on 3.1.0.
Please dont go to 3.1.0. Its is very very bad for battery
Click to expand...
Click to collapse
Did you go the OTA mode, update flash or full flash? Also, I believe if it's a big change, a clean flash would be the better option over dirty flash.
You can also try wiping cache / dalvik and turning on app optimization. Might work? Can also try custom kernel?
I'm so intrigued where I read somewhere, that the Antutu benchmark jumped upto 80k on OOS 3.1.
Thanks!
rezapatel said:
Did you go the OTA mode, update flash or full flash? Also, I believe if it's a big change, a clean flash would be the better option over dirty flash.
You can also try wiping cache / dalvik and turning on app optimization. Might work? Can also try custom kernel?
I'm so intrigued where I read somewhere, that the Antutu benchmark jumped upto 80k on OOS 3.1.
Thanks!
Click to expand...
Click to collapse
I tried the OTA update like i do for every build. Its just not my problem, my friends phone is also behaving same even after factory reset. 3.0.2 was better in terms of battery. But the performance of 3.1.0 is better than 3.0.2. Its very smooooooth.
So I might as well stay away from it? Honestly I'm fairly happy with CM13 except for the fact that double tap feature turned on makes the phone vibrate when talking on a call!
Doesn't beat the snapiness on CM13. I'm back!
Techgod said:
My device never goes to deep sleep mode on 3.1.0.
Please dont go to 3.1.0. Its is very very bad for battery
Click to expand...
Click to collapse
That's not true. I get 6 hours of SOT and over 24 hours of standby with stock 3.1.0 with no modification at all.