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.
Related
Hello there.
Somebody please HELP!!
Okay I have a serious problem, I'm on CheckROM V6 and lately I'm facing this problem when I change batteries, I charge them on a wall charger the original one from SAMSUNG.
When I remove the battery and put a fully charged one the date and time changed to 2:00AM , Feb-1-2000 and the device becomes laggy plus I keep getting security warnings on every web page I go to.
The problem last 5-10 minutes and then the time and date return to the network preset, I tried to uncheck the network settings, changed modems, kernels, wiping everything possible and fixing permissions..
Nothing happened.
Thank you in advance.
Reflash stock rom & see if you can reproduce the problem.
If you don't have the problem with stock, then it's a problem with the rom you're using. In that case, do a completely clean reinstall of the rom (do a factory reset first) & do not restore system apps & in particular do not restore system data. Ideally, you'd do a clean install of all your apps too.
MistahBungle said:
Reflash stock rom & see if you can reproduce the problem.
If you don't have the problem with stock, then it's a problem with the rom you're using. In that case, do a completely clean reinstall of the rom (do a factory reset first) & do not restore system apps & in particular do not restore system data. Ideally, you'd do a clean install of all your apps too.
Click to expand...
Click to collapse
Thanks, will try that.. But I did a full wipe and re-installed the same custom ROM I'm on and nothing changed!
I understand that. And the reason you need to test it out on stock is to see if it's a problem with that custom rom or possibly something else.
Chamillikawi said:
Thanks, will try that.. But I did a full wipe and re-installed the same custom ROM I'm on and nothing changed!
Click to expand...
Click to collapse
Would like some help. I have flashed CM 11 and can't make calls. It says mobile network not available. Tried flashing AOKP rom as well and same thing. Mobile data works fine, although i have gotten a popup twice that says 'Google Play Services not supported by your device, please contact your manufacturer' (no noticible issues from this, google stuff i've tried so far works). I have included a screenshot so you can see my baseband and rom version, etc.
Now, i had a great deal of trouble getting a rom flashed to start with, CWM put me into a bootloop and TWRP wouldn't flash anything because it said it couldn't mount /storage when i tried. Used Philz advanced CWM (love it btw, will be using it from now on). Still wouldnt flash the hltespr specific CM11 version so had to use the unified hlte version (it gave me the status 7 asserts issue, but editing the asserts out just gave me a bad file error when flashing). I wiped data/cache/dalvik between each flashing. I don't know if any of that would have bearing on this problem, just including any details i can. Any advice?
Verilin said:
Would like some help. I have flashed CM 11 and can't make calls. It says mobile network not available. Tried flashing AOKP rom as well and same thing. Mobile data works fine, although i have gotten a popup twice that says 'Google Play Services not supported by your device, please contact your manufacturer' (no noticible issues from this, google stuff i've tried so far works). I have included a screenshot so you can see my baseband and rom version, etc.
Now, i had a great deal of trouble getting a rom flashed to start with, CWM put me into a bootloop and TWRP wouldn't flash anything because it said it couldn't mount /storage when i tried. Used Philz advanced CWM (love it btw, will be using it from now on). Still wouldnt flash the hltespr specific CM11 version so had to use the unified hlte version (it gave me the status 7 asserts issue, but editing the asserts out just gave me a bad file error when flashing). I wiped data/cache/dalvik between each flashing. I don't know if any of that would have bearing on this problem, just including any details i can. Any advice?
Click to expand...
Click to collapse
Have you upgraded your bootloader to NH7? I know most of the newly-updated CM-based ROMs require you to be on NH7 before flashing. That's most-likely why you weren't able to flash the htlespr ROMs. The unified ROMs no longer include the correct APNs for Sprint, so that's why you don't get service on it. I don't know why mobile data works on it.
topherk said:
Have you upgraded your bootloader to NH7? I know most of the newly-updated CM-based ROMs require you to be on NH7 before flashing. That's most-likely why you weren't able to flash the htlespr ROMs. The unified ROMs no longer include the correct APNs for Sprint, so that's why you don't get service on it. I don't know why mobile data works on it.
Click to expand...
Click to collapse
No, didnt realize that i needed to do that. I'll do some research on it because i don't have any idea how to update the bootloader. If you have a link to a good tutorial that would be wonderful! Thanks!
Ok so i tried that, found this tutorial, followed it, no luck. Tried full wipe/reset after that to see if it would let me install the hltespr versions, still no dice. Same situation, mobile data works, calls don't. Will have to wait till daylight to try texting so i don't wake anyone up but i suspect that texting won't work either. Has anyone experienced this and fixed it? Lol i really didn't drop $100 on a phone to be saddled with all the Samsung and Sprint baloney that it comes with, don't wanna unroot....
Bump
Anyone have ideas on this? Have continued to try fooling around with the udater-script file to resolve the status 7 problem so I can install the hltespr variant, still no dice. Please someone help!
Bump!
Sorry, I typically don't have access to XDA forums on the weekend, so couldn't answer your question till now.
You flashed only the baseband/modem, not the Bootloader. If you want to update the Bootloader, you need to use ODIN to flash the Complete OTA NH7 Update.
In order to update the Bootloader, you need to make sure that you use the PC ODIN (not the mobile one) and that you completely power off the phone before you enter download mode (don't access download mode by using the extended power menu when shutting down the phone). I don't think you need to do the battery pull that Freeza had in his instructions (I didn't do it when I ODIN-flashed the NH7 OTA update), but it wouldn't hurt to do it.
Thanks for that, I will try it as soon as I get home tonight! The next thing I had decided to try was to unroot, to back to stock, then try flashing that before I start with the custom recovery and ROM. Do you think I should do that first before doing the whole thing or could that work just flashing that with my phone as-is?
Verilin said:
Thanks for that, I will try it as soon as I get home tonight! The next thing I had decided to try was to unroot, to back to stock, then try flashing that before I start with the custom recovery and ROM. Do you think I should do that first before doing the whole thing or could that work just flashing that with my phone as-is?
Click to expand...
Click to collapse
Well, I always recommend a full wipe (data, system, cache, dalvik) when flashing ROMs. I haven't wiped my internal storage or external storage since I got the phone, so that's not really necessary.
I don't think that unrooting your current ROM is necessary. Flashing the ODIN OTA update will automatically remove root access, so that's not an issue. Here's the steps I took when I updated to NH7 and installed my current ROM (see my sig):
Make a Nandroid backup.
I always do this just so I have a "record" of what I left behind. It also allows me to have all of my app data that I can restore via Titanium Backup (you have to buy the Pro version in order to restore specific apps from a Nandroid backup). I always store a copy on my ext. storage and on dropbox.
Do a full wipe
As I mentioned above, I always wipe data, system, and the caches when flashing ROMs. While I have to take some time to get the new ROM exactly as I like it, it minimizes any potential FCs and errors that some people get when dirty flashing.
Install NH7 all-in-one via ODIN
I installed the NH7 via ODIN. Please note that this is the fully stock, unrooted ROM and will also install the stock recovery.
Let the phone boot and connect to Sprint. Update Profile and PRL.
I do this periodically whenever I go back to stock (from AOSP). I rarely have connection issues, but updating the PRL an profile can help with those.
Install a custom recovery using ODIN.
My recovery of choice is TWRP, but others have found just as much success with CWM and Philz. Just make sure that you're installing the correct version of the recovery (4.4.X version, not the 4.2.X version). I always reboot to the main system after installing a recovery, but that's up to you. In the rest of this post, I'll say "TWRP," but I really mean "custom recovery."
[OPTIONAL] Make a Nandroid backup of the stock ROM
I always do this, but I recognize that it's not necessary, especially since we can just ODIN back to this image at any time. I just like having the option of having a stock backup on the device (in case catastrophe strikes while I'm away from a computer).
Use TWRP to flash your AOSP ROM of choice.
If you haven't installed any apps or messed around with the settings, you shouldn't have to wipe before flashing, but (in case you haven't noticed by now), I tend to err on the side of caution, specifically: wiping everything (data, system, and the caches) before I flash anything.
Set up the ROM how you like it and [OPTIONAL] make one last Nandroid Backup
Whenever I set up a new ROM to the exact way I like it (statusbar settings, accounts set up, apps installed and configured, etc), I make a nandroid backup of my device. This allows me to go back to that "fresh" image whenever something happens to the device and I don't have to muddle around fixing those minor tweaks. Again, I tend to err on the side of wiping the phone too often and taking too many backups, but I've rarely had issues with my phone and ROMs because of it (to the point where I can spend most of my XDA time helping others with their phones), so it might be prudent to follow the advice.
Anyways, that's how I upgraded to NH7 and installed a custom ROM. Others may take a less conservative approach and you're welcome to adjust any of the optional steps.
Hope this helps!
-Topher
OK, did all that successfully, when it went back to stock stiil had the same issue. Mobile data functions, mobile network for calls/SMS doesn't. Did the whole update prl/profile and even tried reactivating from settings, still nothing. Was able to install custom recovery (Philz) and the hltespr CM11 variant instead of the unified generic version. Still has the same problem, mobile network not available. Everything else works perfectly. I did verify in settings that it still wound up as the NH7 after everything I did. Note I did a full reset before each thing that got flashed in this process, and one more for good measure after. Let it boot to the system between steps too.
Lol I've been rooting and switching between ROMs for years and have never encountered anything like this. I'm stumped....
Verilin said:
OK, did all that successfully, when it went back to stock stiil had the same issue. Mobile data functions, mobile network for calls/SMS doesn't. Did the whole update prl/profile and even tried reactivating from settings, still nothing. Was able to install custom recovery (Philz) and the hltespr CM11 variant instead of the unified generic version. Still has the same problem, mobile network not available. Everything else works perfectly. I did verify in settings that it still wound up as the NH7 after everything I did. Note I did a full reset before each thing that got flashed in this process, and one more for good measure after. Let it boot to the system between steps too.
Lol I've been rooting and switching between ROMs for years and have never encountered anything like this. I'm stumped....
Click to expand...
Click to collapse
Dumb question but are you a Verizon customer or Sprint?
Sent from my SM-G900P using Tapatalk
Sprint, I've had big red before but when they did away with unlimited data it wasn't worth paying their high rates.
Bump!
Anyone have any ideas on this? I am just confounded as to why this continues even after being reset to stock.
Same Issue!!!
I have the exact same issue and have been trying to resolve it for the last 2 days... Did you find a solution?
I have the same problem on a Samsung Mega. LTE and 3G data work but phone won't dial if LTE is active. It WILL voice dial if only 3G is active. Sprint. CM11.
I had this problem after flashing ROMs as well, but went into Settings>Connections>More Networks>Mobile Networks>Network Mode and selected LTE/CDMA....no network had been selected. That fixed me right up. Weird part is, I could still avcess the web without WiFi....but couldn't make calls or ise my bluetooth headset until I had performed the above steps. Hope that helps.
thanks forget the little things reset wifi and sprint cell extender
GAPO said:
I had this problem after flashing ROMs as well, but went into Settings>Connections>More Networks>Mobile Networks>Network Mode and selected LTE/CDMA....no network had been selected. That fixed me right up. Weird part is, I could still avcess the web without WiFi....but couldn't make calls or ise my bluetooth headset until I had performed the above steps. Hope that helps.
Click to expand...
Click to collapse
I was using miui 8 the past month and wanted to try something new. So I flashed.a MM.Rom, CM13 from this forum. I did a system backup before. I am using twrp 3022.
After trying the Rom i decided to restore my miui backup, but when i try that I get an error saying:
extractTarFork() process ended with ERROR=255
I tried it several times but i always get this error after 85-87% of the restoring progress.
Is it because one rom is based on LP and one on MM? I never changed the twrp 3022.
I've read somewhere that it can be because of not having enough space but it's a system backup, so doesn't it mean, that it restores the whole system and data i had on that phone?
Please help
Edit
Restoring the cm backup works but the miui dies not work
Download and clean install Vova's AOSP rom first, let it boot, restart into recovery and try to restore your backup again. I've face this problem before, and this method works. Good luck mate ?
Jordan Jacob said:
Download and clean install Vova's AOSP rom first, let it boot, restart into recovery and try to restore your backup again. I've face this problem before, and this method works. Good luck mate
Click to expand...
Click to collapse
The Lollipop Rom?
Yups..
http://forum.xda-developers.com/redmi-note-2/development/cm-aicp-mokee-resurrection-bliss-t3383140
Jordan Jacob said:
Yups..
http://forum.xda-developers.com/redmi-note-2/development/cm-aicp-mokee-resurrection-bliss-t3383140
Click to expand...
Click to collapse
ok thanks i will try it
I still get the error 255 at 87%. I wiped the data and installed that aosp rom but it didn't help
gasperoni said:
I still get the error 255 at 87%. I wiped the data and installed that aosp rom but it didn't help
Click to expand...
Click to collapse
Did you wipe the data partition or did you format it? Try doing the latter ...
First i wiped cache+dalvik+data+system, everything but intern storage. I thought that must be enough. My last chance was wiping internal storage as well. I tried that and now it works. It really seems that it was a problem of space. I want to go back to a CM13 based Rom, when it's getting more stable.
Glad to hear your problem solved..
Jordan Jacob said:
Glad to hear your problem solved..
Click to expand...
Click to collapse
thanks bro, me too :good:
I've had this problem too - exact same error message, with the last two versions of TWRP.
I originally made a backup of my Nexus 7 2012 3G (Tilapia) with the modified KOT49H ROM installed, with TWRP (3.0.2.0, I think). I installed one of the Lollipop ROMs (I forget which) then restored that KOT49H based backup with no problem. Then I tried a different Lollipop ROM (Resurrection Remix, something) then tried to restore the same KOT49H based backup as before, and got this error.
I went from there to the Nougat ROM I'm currently using - an AOSP one by AndDiSa, and made a backup of that installation shortly after. After making some changes, I tried to restore that backup and got the same error (see OP).
I deleted as much stuff as I reasonably could, updated TWRP to 3.1.0.0 via fastboot and tried the restore again - same error. Also, my tablet then wouldn't boot, though that might be an unrelated problem. I took the battery out, which possibly I didn't need to, put it back, and noticed it was charging. It eventually booted, and seemed to have restored the backup, though I cant' be sure. Since it was the same ROM, it's possible all it restored was the data partition.
My main question is, if this is related to free storage, just how much is needed, to be able to restore a backup? I don't see wiping internal storage as much of a solution, on the Nexus 7, because there isn't a microSD slot, so that's the only place I can put the backup I'm trying to restore.
Hello. Can you please give me the twrp nvram backup or just the protect_f.img and protect_s. Thank you
Had same error, went back to old twrp ,all problems fixed
Steveromingagain said:
Had same error, went back to old twrp ,all problems fixed
Click to expand...
Click to collapse
what version TWRP to fixed problems ? i use TWRP version 3.0.2.2 always Error...
I'm so lost and confused over this since yesterday...
so 2 days ago my phone started lagging and hanging and freezing until i realized i have got this issue with data encryption
i have a rooted sony z2 with TWRP Custom recovery
first i didn't know it was with data encryption failure so i literally factory reset and installed all my apps and data again and again!!!
On both rooted and non rooted rom ....
after every time my phone started to lag !!
after one whole day of trying everything i finally realized its actually with the data encryption and i should change my ex4 to something else... so here again i wiped the phone and changed to ex3 and installed and all my data and apps all over again
but after a couple hours...same problem again.....
im literally so tired of not knowing what to do ! my head hurts so much due this ugh....
Please help me get rid of this issue thanks ...!
Hey, i would flash the full stock rom without root and twrp and look. I think it is a problem with the twrp recovery.
On my V30 with Oreo we should flash a zip that disable data encryption after some modification in Recovery.
Just try for a week the full stock rom.
Nemeziz 56th said:
Hey, i would flash the full stock rom without root and twrp and look. I think it is a problem with the twrp recovery.
On my V30 with Oreo we should flash a zip that disable data encryption after some modification in Recovery.
Just try for a week the full stock rom.
Click to expand...
Click to collapse
Well i have already tried using the stock ROM without any root or recovery !!
and its still the same
however im not sure whats the zip file u r talking about and where i can get it for my Sony z2 D6502...
By the way i just thought it might be another reason that my device is lagging so much after installing like 30/40 apps.
i have overclocked my CPU with root and even after flashing the stock rom i feel like CPU settings hasn't been reset? is it possible?
its always on end MAX and less Min value on both stock/pre root rom my CPU gets very hot on TWRP specially, its more than 70Celcious so i thought maybe its a hardware issue and my CPU is overheating bcuz its old or something... and i should prolly change my CPU ?
i really don't understand whats wrong with my phone and im so confused about what to do
I had here a Z1 and Z2 both was my previous phones.
I didnt experienced such problems except i backup or restore anything in TWRP.
My questions for you are:
On which Version are you now?
What do you done exactly before the problem starts?
Get a Monitor App from Playstore and look what cause this high load. Or you take a look in the Developers Option for this.
We got here a not tasty problem, maybe you backup your whole data and reset all to stock and don't install any apps, after a while installing step by step your apps.
Nemeziz 56th said:
I had here a Z1 and Z2 both was my previous phones.
I didnt experienced such problems except i backup or restore anything in TWRP.
My questions for you are:
On which Version are you now?
What do you done exactly before the problem starts?
Get a Monitor App from Playstore and look what cause this high load. Or you take a look in the Developers Option for this.
We got here a not tasty problem, maybe you backup your whole data and reset all to stock and don't install any apps, after a while installing step by step your apps.
Click to expand...
Click to collapse
I dont think if its even about TWRP because i even installed the stock rom with Flashtool and started installing my apps one by one and after a couple hrs device started lagging and freezing and odd how Wifi gets soooo slow ! (like everything gets slow in it) and also when i reboot the phone it oddly takes long time on boot menu to load .
im not sure if i did anything to cause it tbh...
it just happened on a normal day...
it gets soooo slow and leaves no other way for me but factory reset option...
i have the latest rom 23.5.A.1.291
the only time i can get it temporary fixed is when i backup the rom on TWRP and factory reset the Rom and Restore it back!
and everything is working fast and fine again only for like 6 or less hours...
and while data is restoring TWRP shows the CPU Temp on +80C !! Is this normal?
Btw i have a unlocked bootloader.
do u have any idea what i should do?
Yes i do! You need a structure by fixing a problem, my plan is:
You must explorer the problem why your phone get so laggy.
Perform a factory reset and use your phone for 1 Day with this stock setup. (Dont restore your old apps or data)
Look often into the Task Manager to show what cause the cpu load.
Nemeziz 56th said:
Yes i do! You need a structure by fixing a problem, my plan is:
You must explorer the problem why your phone get so laggy.
Perform a factory reset and use your phone for 1 Day with this stock setup. (Dont restore your old apps or data)
Look often into the Task Manager to show what cause the cpu load.
Click to expand...
Click to collapse
man i kinda feel like its my CPU that is messsed up and idk why
cpu usage doesnt show any app, no app is taking more than 1%.
i think ,my system is overclocking...
and if it is how can i reset or stop it smh?
Hey, I am using a redmi note 4 Snapdragon version,and I installed custom rom on my device,the installation was successful but hardware components are not accessible to me now.Like, wifi,bluetooth is not turning on, camera app is not present and even flashlight icon in notification shade is blurred out.
I installed resurrection remix and aex ROMs,I know they are fine cause i have installed them before(same versions) in the same phone,but now they are showing problems.And gapps are not installing either twrp recovery shows corrupt file even though its not for sure.
I think i messed up while wiping data ,I wiped the internal storage and formatted the phone too, that is the only thing i did that was different this time.
Please help if there is a link to any thing that i deleted and need to replace please provide that,
Thank You
Sounds like a firmware problem, get latest firmware here, and flash it from recovery.
RogueMoon said:
Sounds like a firmware problem, get latest firmware here, and flash it from recovery.
Click to expand...
Click to collapse
It worked!, Thank you man.
Also I have a problem with the same device that it charges in recovery or switch off mode but it does not charge while in system.Thinking of starting a new thread but if you can answer ,no need to do that.Again Thanks.
Weird. First I would make sure that the device indeed doesn't charge in system (install Ampere app, or use a USB power meter if you have one) - otherwise it might be a UI problem. Other than that, if that's indeed the case I would do a clean reflash, starting with flashing a latest stable MIUI in fastboot, then recovery again, factory reset (DONT format system) and ROM (which one are you using?) again. Maybe others could chime in. Good luck!
RogueMoon said:
Weird. First I would make sure that the device indeed doesn't charge in system (install Ampere app, or use a USB power meter if you have one) - otherwise it might be a UI problem. Other than that, if that's indeed the case I would do a clean reflash, starting with flashing a latest stable MIUI in fastboot, then recovery again, factory reset (DONT format system) and ROM (which one are you using?) again. Maybe others could chime in. Good luck!
Click to expand...
Click to collapse
Thanks i will try that.?