Related
Hey guys!
This is my first post on the Nexus 7 forum so if this is the incorrect place to ask such a question, please tell me!
Basically, I wanted to make sure that I'm flashing my roms correctly. Specifically, I've been on a flashing binge and installed Smooth Rom, Paranoid Android and Liquid Smooth all after one another in the same sitting. My flashing process, using clockwork mod, begins by wiping all of my data and cache -> Rewiping the cache (this probably isn't needed) -> Flashing the Rom -> and lastly flashing gapps. I'd be very thankful if someone could tell me if this is a clean flash.
Also, I've noticed from other users on the boards for these roms that they're getting much higher benchmarks. For example, Smooth Rom with the Motley Kernel, one user mentioned that he got around 4800 on the quadrant benchmark which is much higher than what I've gotten even by fully overclocking. That's one of the reasons I wanted to make sure I was flashing correctly. Incidentally, I also seem to create a new set of folders on the Nexus 7 after flashing each Rom. For example, I have on my internal storage the usual set of folders (Alarm, Android, DCIM, etc...) but then I also have folders named legacy and 0. Within 0, there is a whole new set of Alarm, Android, DCIM, Downloads, etc... And within that subset of folders is another 0 folder with more of the same folders. So you get the picture. That doesn't seem right to me since eventually I'll have an outrageous amount of folders, haha.
So yeah! If anyone could tell me whether I flashed correctly and maybe why I seem to have those problems, I'd very much appreciate it!
Also, I'd like to note that coming from the HTC Vivid forums, it's a breath of fresh air to see such a dedicated and organized forum! Thank you!
darkwolfx24678 said:
Hey guys!
This is my first post on the Nexus 7 forum so if this is the incorrect place to ask such a question, please tell me!
Basically, I wanted to make sure that I'm flashing my roms correctly. Specifically, I've been on a flashing binge and installed Smooth Rom, Paranoid Android and Liquid Smooth all after one another in the same sitting. My flashing process, using clockwork mod, begins by wiping all of my data and cache -> Rewiping the cache (this probably isn't needed) -> Flashing the Rom -> and lastly flashing gapps. I'd be very thankful if someone could tell me if this is a clean flash.
Also, I've noticed from other users on the boards for these roms that they're getting much higher benchmarks. For example, Smooth Rom with the Motley Kernel, one user mentioned that he got around 4800 on the quadrant benchmark which is much higher than what I've gotten even by fully overclocking. That's one of the reasons I wanted to make sure I was flashing correctly. Incidentally, I also seem to create a new set of folders on the Nexus 7 after flashing each Rom. For example, I have on my internal storage the usual set of folders (Alarm, Android, DCIM, etc...) but then I also have folders named legacy and 0. Within 0, there is a whole new set of Alarm, Android, DCIM, Downloads, etc... And within that subset of folders is another 0 folder with more of the same folders. So you get the picture. That doesn't seem right to me since eventually I'll have an outrageous amount of folders, haha.
So yeah! If anyone could tell me whether I flashed correctly and maybe why I seem to have those problems, I'd very much appreciate it!
Also, I'd like to note that coming from the HTC Vivid forums, it's a breath of fresh air to see such a dedicated and organized forum! Thank you!
Click to expand...
Click to collapse
if your roms are flashing, then youre flashing correctly. generally you want to wipe data only if going from one rom to a different rom. but if only updating the same rom, just flash your rom without wiping anything. no need to wipe dalvik as it gets wiped when you flash the rom.
what recovery are you using? i thonk its only cwm recovery that keeps adding a 0 folder every time, no such issue with twrp recovery.
benchmarks, its about how you set up your device, and how you actually benchmark. you should benchmark at highest cpu/highest cpu, as to not allow your device to scale. if you allow your device to scale, you dont actually know what cpu speed is being benchmarked. btw, 4800 on a quadrant is low. anyways, benchmarks shouldnt matter to you(to a developer they might matter though), what should matter is how it feels and runs for you.
I follow that same routine, but have only been successful in one flash, and after trying to go to P.A., now I can't get any to boot correctly. I have maybe 4 ROMs to try from, but all day, only the one worked. LiquidJB , I think. I really wanted PA though, cause thats whats on my phone.
Sent from my PG8600 using xda app-developers app
ShifterX2 said:
I follow that same routine, but have only been successful in one flash, and after trying to go to P.A., now I can't get any to boot correctly. I have maybe 4 ROMs to try from, but all day, only the one worked. LiquidJB , I think. I really wanted PA though, cause thats whats on my phone.
Sent from my PG8600 using xda app-developers app
Click to expand...
Click to collapse
did you wipe data before flashing the new rom?
Yes. I always wipe cache and dalvik, before flashing, and I flash the rom then gapps using twrp. At this point, I'm stuck at the Google screen with one, and PA says setup stopped when I load it.
Sent from my PG8600 using xda app-developers app
Man I had at least a half dozen good responses to this topic - but my better judgement stopped me.
ShifterX2 said:
Yes. I always wipe cache and dalvik, before flashing, and I flash the rom then gapps using twrp. At this point, I'm stuck at the Google screen with one, and PA says setup stopped when I load it.
Sent from my PG8600 using xda app-developers app
Click to expand...
Click to collapse
not cache and dalvik, did you wipe data(factory reset)?
simms22 said:
not cache and dalvik, did you wipe data(factory reset)?
Click to expand...
Click to collapse
Yes. Factory reset. Unfortunately, I've now wiped the sd card (internal) so I'm trying to flash AP using a zip on my laptop with Nexus Root Toolkit v.1.5.5, but now that I tried, iss that the rom I managed to boot still has an error that the setup program stopped, and the error keeps coming up, keeping me from entering debugging mode... guess i have to do a flash stock + unroot and start fresh....
Sent from my PG8600 using xda app-developers app
ShifterX2 said:
Yes. Factory reset. Unfortunately, I've now wiped the sd card (internal) so I'm trying to flash AP using a zip on my laptop with Nexus Root Toolkit v.1.5.5, but now that I tried, iss that the rom I managed to boot still has an error that the setup program stopped, and the error keeps coming up, keeping me from entering debugging mode... guess i have to do a flash stock + unroot and start fresh....
Sent from my PG8600 using xda app-developers app
Click to expand...
Click to collapse
you redownloaded it? maybe you have a corrupt download. try a different rom insteadcif stock, unroot, reroot.
simms22 said:
you redownloaded it? maybe you have a corrupt download. try a different rom insteadcif stock, unroot, reroot.
Click to expand...
Click to collapse
Well, mean, I had downloaded something like 5 Roms. Might it be that rooting changed my boot version or something? Not sure what the boot version changes with the N7, on my phone it's pretty important.
Sent from my PG8600 using xda app-developers app
So, is there any fix for this strange folders "legacy" ans "0"?
Hey!
Sorry for not responding sooner. University applications can be so time consuming. Thanks a lot Simms22! You've been a great help. Since then, I've cared less about benchmarks and more on the fact that the Nexus is freakishly fast with SmoothRom.
I haven't fixed the legacy problem but I'm assuming (and I could definitely be wrong with this) I could just delete the extra folders seeing as they technically don't have anything inside of them and afterwards just switch to TWRP. Shouldn't be that difficult.
So I used the Auto CF root and all went well. Next, I went back into recovery and installed the TWRP Recovery though odin. It installed fine. After that I noticed I no longer had root and I can't figure out how to get it back. Supersu was still installed, it just wouldn't work.
At this point, i've tried redoing the root process a couple of times and it says that it worked fine, but doesn't do the job. Anyone got any ideas on what to do?
If anyone's curious, I started on totally stock OTA MF9.
Thanks
Just flash one of the stock rooted mf9 ROMs in the development thread pic one with no data wipe so you don't have to set everything up again.
SGS4 Sent
ifly4vamerica said:
Just flash one of the stock rooted mf9 ROMs in the development thread pic one with no data wipe so you don't have to set everything up again.
SGS4 Sent
Click to expand...
Click to collapse
Thanks for the tip. Downloading the odexed version of this. Slow download so almost 2 hrs left.
[ROM][ZIP]Stock Rooted Deodexed/Odexed MF9 with SuperSU/Busybox 1.20.2
Hopefully it works. I tried wiping cache and dlvik cache and now when i turn the phone on it just keeps giving errors that this and that app can't open so the phone is essentially unusable. Didn't think wiping cache would do that.
Yeah sometimes things just go screwy. Have you tried fixing permissions? While you wait for a download you can wipe cache davlik and fix permissions its in the advanced menu of twrp. The odexed with no data wipe should fix you up I would recommend wiping cache davlik and system before you flash it. If it still gives errors you may have to wipe the data also and start fresh. You can also try TWRP version 5.0.2 if you aren't on it there is a flashable in the dev forum also. Some people have reported issues with the newer version. I think you will be fine flashing that stock odexed ROM though.
SGS4 Sent
Out of curiosity, would there be any danger in installing a custom rom while my phone is in this state? Downloading Blu Kuban Rom and it's going to finish much earlier than the stock rom. I know I would lose all my apps and need to reinstall those.
iivisionii said:
Out of curiosity, would there be any danger in installing a custom rom while my phone is in this state? Downloading Blu Kuban Rom and it's going to finish much earlier than the stock rom. I know I would lose all my apps and need to reinstall those.
Click to expand...
Click to collapse
Nope no danger at all. In fact I recommend blu Kuban. Its a nice ROM. Just do a full wipe of system data cache davlik and preload before flashing to avoid issues. All the custom ROMs have root built into them so you should be good to go.
SGS4 Sent
ifly4vamerica said:
Nope no danger at all. In fact I recommend blu Kuban. Its a nice ROM. Just do a full wipe of system data cache davlik and preloaded.
SGS4 Sent
Click to expand...
Click to collapse
Thanks. I'll have an update soon. Either that or a panic attack and a question in roughly 30-45 minutes.
Did you try to install super SU from the market. Maybe super user is acting up on you.
Sent from my SPH-L720 using Tapatalk 4 Beta
daniel4653 said:
Did you try to install super SU from the market. Maybe super user is acting up on you.
Sent from my SPH-L720 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I tried installing supersu from the market. Next I even tried downloading it to my phone and loading the zip in recovery. No go both ways. I hoped wiping cache and delvick cache would help, but instead the phone is pretty much unusable now. It's really weird.
iivisionii said:
I tried installing supersu from the market. Next I even tried downloading it to my phone and loading the zip in recovery. No go both ways. I hoped wiping cache and delvick cache would help, but instead the phone is pretty much unusable now. It's really weird.
Click to expand...
Click to collapse
Here goes that frantic post. I installed the rom, worked fine. I did one of the updates for the status bar, now whenever it goes to boot it gets stuck at the samsung galaxy s4 screen. I've tried doing a full wipe, wiping cache and delvick cache and even trying to install the stock rooted rom or the blu rom on top of itself and i still get the same thing. Any ideas? I'm trying not to be too flash happy because I don't want a brick.
iivisionii said:
Here goes that frantic post. I installed the rom, worked fine. I did one of the updates for the status bar, now whenever it goes to boot it gets stuck at the samsung galaxy s4 screen. I've tried doing a full wipe, wiping cache and delvick cache and even trying to install the stock rooted rom or the blu rom on top of itself and i still get the same thing. Any ideas? I'm trying not to be too flash happy because I don't want a brick.
Click to expand...
Click to collapse
Have you tried the battery pull trick once frozen?
ObrienDave said:
Have you tried the battery pull trick once frozen?
Click to expand...
Click to collapse
I finally got out of the boot logo. I looked around the forums and found someone with a similar problem. Seems the recovery wasn't deleting all the files for him so he deleted everything manually instead of just wiping. I did the same and installed triforce rom and it's booted now.
Just for future reference though, would you mind explaining or pointing me to where I can read about the battery pull trick?
iivisionii said:
I finally got out of the boot logo. I looked around the forums and found someone with a similar problem. Seems the recovery wasn't deleting all the files for him so he deleted everything manually instead of just wiping. I did the same and installed triforce rom and it's booted now.
Just for future reference though, would you mind explaining or pointing me to where I can read about the battery pull trick?
Click to expand...
Click to collapse
Basically, quite a few people have recommended pulling the battery once frozen.
Even when you do a power off, you are NOT completely removing power from the system.
Disconnecting the power is the only way to accomplish this.
ObrienDave said:
Basically, quite a few people have recommended pulling the battery once frozen.
Even when you do a power off, you are NOT completely removing power from the system.
Disconnecting the power is the only way to accomplish this.
Click to expand...
Click to collapse
Ah ok. Good tip to know. I had tried that and it didn't work. Seems to be working ok now. I'm gonna be careful not to screw it up cuz its already 1 am, hehe. Thanks for everyone's tips.
Hello,
So out of nowhere, everytime I open a LG app, such as the dailer,quickremote,launcher and even the gallery, it syas "App updates has stopped".
Also, when I opened Whatsapp, it said that my messasging files where damaged, luckily I could restore them...
Whats is happening and how can I solve this problem??
I'm to afraid to reboot my device, because I'm scared that It will end up in a bootloop...
If you're using an original stock ROM, than copy all your important files to your PC, and factory wipe.
If you're on a custom ROM, copy all your important files to your PC, than get a copy of your custom ROM zip file and Gapps onto your phone, than do the following (using TWRP, I don't use CWM):
1) Go to Advanced Wipe, and wipe everything except for Internal Storage.
2) Install ROM and Gaps.
3) Wipe Cache, Dalvik Cache, and Internal Storage.
4) Reboot.
palaczu said:
If you're using an original stock ROM, than copy all your important files to your PC, and factory wipe.
If you're on a custom ROM, copy all your important files to your PC, than get a copy of your custom ROM zip file and Gapps onto your phone, than do the following (using TWRP, I don't use CWM):
1) Go to Advanced Wipe, and wipe everything except for Internal Storage.
2) Install ROM and Gaps.
3) Wipe Cache, Dalvik Cache, and Internal Storage.
4) Reboot.
Click to expand...
Click to collapse
Okay, so I'm on the stocks ROM, but rooted, with x posed and TWRP.... What do I have to do??
pottemans said:
Okay, so I'm on the stocks ROM, but rooted, with x posed and TWRP.... What do I have to do??[/QUOTE
Go to the post where you got your KDZ file, and ask the DEV quoting my second method, if using it will require re-rooting or re-flashing SuperUser again.
I don't think it does, but, better to be safe than sorry.
I personally always use plain stock (d80220a currently), or I use an AOSP, CM, or PA, and using the above methods during installation of a custom ROM, always prevented system ui or other FCs, which did sometimes happen when I didn't wipe cache, dalvik, and internal.
Just double check with the dev of your ROMs OP.
Click to expand...
Click to collapse
palaczu said:
pottemans said:
Okay, so I'm on the stocks ROM, but rooted, with x posed and TWRP.... What do I have to do??[/QUOTE
Go to the post where you got your KDZ file, and ask the DEV quoting my second method, if using it will require re-rooting or re-flashing SuperUser again.
I don't think it does, but, better to be safe than sorry.
I personally always use plain stock (d80220a currently), or I use an AOSP, CM, or PA, and using the above methods during installation of a custom ROM, always prevented system ui or other FCs, which did sometimes happen when I didn't wipe cache, dalvik, and internal.
Just double check with the dev of your ROMs OP.
Click to expand...
Click to collapse
Ok thanks.... But the weird thing is, is that it just appears out of nowhere! I'm using the stock rom, with root and Xposed since I got my LG and never had a problem with it! Don't you think a simple reboot will fix this?
Click to expand...
Click to collapse
I assumed you've already rebooted your phone and cleared data and cache for the affected apps, and it hasn't solved your problem, that's why I provided the solutions above.
palaczu said:
I assumed you've already rebooted your phone and cleared data and cache for the affected apps, and it hasn't solved your problem, that's why I provided the solutions above.
Click to expand...
Click to collapse
Thanks! What I'll do tomorrow is I'll backup my files with MyBackup, Backup my foto's and move those files to my computer... After I've done that, I'll try to reboot, but I'm just too afraid that I will get in a bootloop.... But I'll wait for tomorrow, since it's Kingsday were i live (The Netherlands)
palaczu said:
I assumed you've already rebooted your phone and cleared data and cache for the affected apps, and it hasn't solved your problem, that's why I provided the solutions above.
Click to expand...
Click to collapse
Welp, I just noticed vibration is not working either....
Yeah, I tried a few various ROMs, like CM, PA, Mahdi, SlimKat, PAC, etc, and because of all the bugs, I always endup going back to stock.
The only thing I don't like in the stock ROM, is the way the calling and massaging apps UI look. Other than that, I'm satisfied.
I used Sony phones before, and they didn't have so many bugs in the custom ROMs.
LG G2 ROMs seem to plagued by bugs, which is evident from all the beta releases, and hardly any STABLE versions. Even the so called stable releases are plagued by bugs. I think all the good devs are gone. They probably got real jobs, and don't have time to tinker with all these ROMs, especially that the LG G2 has so many variants.
Personally, I'd go back to Sony, especially that the Z2 has 3GBs of RAM, but, it's just so much bigger than the G2, and the performance vs price, compared to the G2, is just not worth it.
Anyway. Good luck with your problem.
palaczu said:
Yeah, I tried a few various ROMs, like CM, PA, Mahdi, SlimKat, PAC, etc, and because of all the bugs, I always endup going back to stock.
The only thing I don't like in the stock ROM, is the way the calling and massaging apps UI look. Other than that, I'm satisfied.
I used Sony phones before, and they didn't have so many bugs in the custom ROMs.
LG G2 ROMs seem to plagued by bugs, which is evident from all the beta releases, and hardly any STABLE versions. Even the so called stable releases are plagued by bugs. I think all the good devs are gone. They probably got real jobs, and don't have time to tinker with all these ROMs, especially that the LG G2 has so many variants.
Personally, I'd go back to Sony, especially that the Z2 has 3GBs of RAM, but, it's just so much bigger than the G2, and the performance vs price, compared to the G2, is just not worth it.
Anyway. Good luck with your problem.
Click to expand...
Click to collapse
Thanks! Yesterday Quickremote and Apps-update radomly started to work again, so basically everything is fine now.... Only 2 things are still doing weird....
1) Notification LED not working. It's working with Knock-On though, not with Lightflow....
2) Vibration isn't working at all... not in system apps, games and/or vibrate mode....
Hi,
I want to install the ROM here on my Samsung Galaxy S4 (GT-I9505). I rooted and installed CM on it about 4 months ago, but since have forgotten anything about the process except for towelroot lol. My phone is currently running jflte snapshot M10 ROM for CM. Unfortunately, I have grown quite sick of it as I find I have to restart my phone once, maybe twice a day for everything to run smoothly. I run into problems where the WiFi likes to get stuck saying 'Turning on..'. Ive also been having problems with Google Maps and GPS lately and havent been able to rely on it, possibly its an issue its having with CM. I want to have the fresh Lollipop feel on my phone without any problems if possible. The only trouble is I dont know how to get there. Can anyone help me? Ive completely forgotten the process needed and when I try to look for it on here I am overwhelmed with things I need to do, which version I need to use etc etc. If anyone would be able to help me achieve this it would be greatly appreciated. In the end I just want a nice Lollipop android phone that doesn't have problems on my current S4 (Id rather not have to get a new phone at least until December ) I'm pretty sure I dont have a custom kernel or anything like that as it mentioned in some pages that I will need to get one I think? I also have philz CWM installed.
You have Philz installed, so you don't need to root again. Download the ROM and follow the instructions on the page.
Strephon Alkhalikoi said:
You have Philz installed, so you don't need to root again. Download the ROM and follow the instructions on the page.
Click to expand...
Click to collapse
It also mentioned to make sure I have the latest modem for my variant, how do I check/update that?
In regards to the kernel (which has a link on the same page), what do I do with that?
I don't have the latest modem for my I9505 and that ROM works perfectly fine. Where you've been on a custom ROM for a while finding out which modem you're supposed to use may be difficult. That's also why I recommend not worrying about it, unless you need to.
Strephon Alkhalikoi said:
I don't have the latest modem for my I9505 and that ROM works perfectly fine. Where you've been on a custom ROM for a while finding out which modem you're supposed to use may be difficult. That's also why I recommend not worrying about it, unless you need to.
Click to expand...
Click to collapse
Ok thanks. In regards to the kernel that is linked on the page, I guess I would be at an advantage if I downloaded and installed that too. How do I install it?
If' we're talking the same GPE ROM, and I think we are, the kernel is included in the ROM download. You'll be prompted to select a kernel when you run the install through the recovery.
Strephon Alkhalikoi said:
If' we're talking the same GPE ROM, and I think we are, the kernel is included in the ROM download. You'll be prompted to select a kernel when you run the install through the recovery.
Click to expand...
Click to collapse
Ok thanks a lot!
So process:
Backup data/photos etc
Nandroid backup
Full wipe using philz?
Flash ROM
Done?
You've got it.
When you are prompted to select the kernel, use the Googy Max kernel. The stock kernel sometimes causes random reboots. Also, on first boot the S4 will sit for a fair amount of time before prompting you to set a language. THIS IS NORMAL. It's because Android 5.0.x uses Art instead of Dalvik, and has to compile the apps the first time around.
In other words, after rebooting, just be patient.
Strephon Alkhalikoi said:
You've got it.
When you are prompted to select the kernel, use the Googy Max kernel. The stock kernel sometimes causes random reboots. Also, on first boot the S4 will sit for a fair amount of time before prompting you to set a language. THIS IS NORMAL. It's because Android 5.0.x uses Art instead of Dalvik, and has to compile the apps the first time around.
In other words, after rebooting, just be patient.
Click to expand...
Click to collapse
Ok, thanks a lot for the help! Greatly appreciated. Hope I dont run into any problems
I installed that ROM on Sunday, so what I did is still fresh in my mind. If you have problems, just use this thread and quote me. I'll do my best to help.
Strephon Alkhalikoi said:
I installed that ROM on Sunday, so what I did is still fresh in my mind. If you have problems, just use this thread and quote me. I'll do my best to help.
Click to expand...
Click to collapse
All installed, was quite easy! Looks bloody beautiful, love it already. Thanks a heap!
Strephon Alkhalikoi said:
I installed that ROM on Sunday, so what I did is still fresh in my mind. If you have problems, just use this thread and quote me. I'll do my best to help.
Click to expand...
Click to collapse
I made and error when backing up and didnt back up my photos onto a computer Is there any way that my nandroid recovery or titanium backup have saved my photos and how could I recover them?
jc258 said:
I made and error when backing up and didnt back up my photos onto a computer Is there any way that my nandroid recovery or titanium backup have saved my photos and how could I recover them?
Click to expand...
Click to collapse
No, they are gone forever.
How is that even possible that you wiped them? Wiping in the custom recovery never touches your internal storage by default. So you have done it yourself. You probably did a factory reset from within android itself. Never do that again. Use the custom recovery for wiping only and you never will have this problem again.
Lennyz1988 said:
No, they are gone forever.
How is that even possible that you wiped them? Wiping in the custom recovery never touches your internal storage by default. So you have done it yourself. You probably did a factory reset from within android itself. NEVER DO THAT AGAIN. Use the custom recovery for wiping only and you never will have this problem again.
Click to expand...
Click to collapse
Are you sure about that? It happened the first time I flashed a ROM. Wiped cache, wiped Dalvik through CWM. Never did a factory reset. No need for caps.
jc258 said:
Are you sure about that? It happened the first time I flashed a ROM. Wiped cache, wiped Dalvik through CWM. Never did a factory reset. No need for caps.
Click to expand...
Click to collapse
No it's not possible for it to happen without you doing so. Unless you encrypted your phone or something.
ps removed the caps
The rom he installed has an aroma installer which offers the option to do a simple wipe (Dalvik, cache and data), no wipe (Dirty flash) and a factory reset (which also wipes the internal storage).
By default it is set on factory reset option.
It also says in red letters that this option is recommended.
So maybe he left it on factory reset (since it was also recommended) , instead of changing it to simple wipe, and that wiped the whole phone, including the internal storage.
Will a software that recovers deleted files not work? Since the phone wasn't encrypted.
It would if Windows saw the internal storage as a drive. Due to MTP it doesn't. He'll have to do a search, but there was another S4 owner who lost his photos and was trying to get them back. I don't know if a solution was ever found.
GDReaper said:
The rom he installed has an aroma installer which offers the option to do a simple wipe (Dalvik, cache and data), no wipe (Dirty flash) and a factory reset (which also wipes the internal storage).
By default it is set on factory reset option.
It also says in red letters that this option is recommended.
So maybe he left it on factory reset (since it was also recommended) , instead of changing it to simple wipe, and that wiped the whole phone, including the internal storage.
Will a software that recovers deleted files not work? Since the phone wasn't encrypted.
Click to expand...
Click to collapse
If that's the case then shame on the developer. A factory reset in a custom recovery should leave the internal storage intact.
Strephon Alkhalikoi said:
It would if Windows saw the internal storage as a drive. Due to MTP it doesn't. He'll have to do a search, but there was another S4 owner who lost his photos and was trying to get them back. I don't know if a solution was ever found.
Click to expand...
Click to collapse
No it's impossible. Once it's gone the files are permanently gone. Not even a professional company can restore them. That's because of TRIM that Android has from version 4.3.
Lennyz1988 said:
If that's the case then shame on the developer. A factory reset in a custom recovery should leave the internal storage intact.
Click to expand...
Click to collapse
It's not in the recovery. It's in the aroma installer. Those are 2 different things.
Besides, there is a description, under each setting, of what each one does.
@Lennyz1988: Perhaps you should bring this up with the developers of the ROM and see what they say. I suspect they have a very good reason for wiping the internal storage, and my gut instinct tells me it has to do with the Android folder on there.
On the flip side, thanks for the homework you gave me. I have to look into what TRIM is all about, as my last device was powered by Gingerbread.
Hello xda community!
I received the nexus 6p christmas and after a few hours playing with it, I unlocked, installed twrp and installed cm13. I then installed ak kernal. My phone installs both fine and runs as normal without any FC. Then this is where it gets weird. When I had my new rom and kernal all set up. I go into TWRP and create a backup. I restart and I'm bootlooping. It tells me my device is corrupt. It did this with the original backup of stock rom, cm13, with and without ak kernal installed... and then sometimes my phone will soft-brick (gets stuxk on google logo) I really love cm engine as I habe a theme. But I'm unsure what is happening to my phone.
Any help is appreciated! - thanks.
Info
Xtra-arrow said:
Hello xda community!
I received the nexus 6p christmas and after a few hours playing with it, I unlocked, installed twrp and installed cm13. I then installed ak kernal. My phone installs both fine and runs as normal without any FC. Then this is where it gets weird. When I had my new rom and kernal all set up. I go into TWRP and create a backup. I restart and I'm bootlooping. It tells me my device is corrupt. It did this with the original backup of stock rom, cm13, with and without ak kernal installed... and then sometimes my phone will soft-brick (gets stuxk on google logo) I really love cm engine as I habe a theme. But I'm unsure what is happening to my phone.
Any help is appreciated! - thanks.
Click to expand...
Click to collapse
Wipe everything > Advance Wipe Phone in recovery
Reinstall CM13 through Recovery and don't flash another kernel
:good:
Geeks Empire said:
Wipe everything > Advance Wipe Phone in recovery
Reinstall CM13 through Recovery and don't flash another kernel
:good:
Click to expand...
Click to collapse
Whoa! Don't tell him to wipe everything in the advanced wipe menu, that'll wipe the internal storage too which is completely unnecessary.
Xtra-arrow said:
Hello xda community!
I received the nexus 6p christmas and after a few hours playing with it, I unlocked, installed twrp and installed cm13. I then installed ak kernal. My phone installs both fine and runs as normal without any FC. Then this is where it gets weird. When I had my new rom and kernal all set up. I go into TWRP and create a backup. I restart and I'm bootlooping. It tells me my device is corrupt. It did this with the original backup of stock rom, cm13, with and without ak kernal installed... and then sometimes my phone will soft-brick (gets stuxk on google logo) I really love cm engine as I habe a theme. But I'm unsure what is happening to my phone.
Any help is appreciated! - thanks.
Click to expand...
Click to collapse
Which partitions are you backing up when creating the nandroid with TWRP?
Heisenberg said:
Which partitions are you backing up when creating the nandroid with TWRP?
Click to expand...
Click to collapse
System, data, boot - Installing the kernel made no difference, the device still corrupted on reboot. and then sometimes at least twice it has soft-bricked
Geeks Empire said:
Wipe everything > Advance Wipe Phone in recovery
Reinstall CM13 through Recovery and don't flash another kernel
:good:
Click to expand...
Click to collapse
Already tried it mate, a number of times. no joy.
Xtra-arrow said:
Hello xda community!
I received the nexus 6p christmas and after a few hours playing with it, I unlocked, installed twrp and installed cm13. I then installed ak kernal. My phone installs both fine and runs as normal without any FC. Then this is where it gets weird. When I had my new rom and kernal all set up. I go into TWRP and create a backup. I restart and I'm bootlooping. It tells me my device is corrupt. It did this with the original backup of stock rom, cm13, with and without ak kernal installed... and then sometimes my phone will soft-brick (gets stuxk on google logo) I really love cm engine as I habe a theme. But I'm unsure what is happening to my phone.
Any help is appreciated! - thanks.
Click to expand...
Click to collapse
The bootloader message won't go away until you lock the bootloader. Its just there as a warning to you in case you did not unlock your phone. As for CM I'm sure there are still many bugs to be worked out. I know I'm going to wait before Flashing it until I see people enjoying it as a daily driver. There are some great devs here in the n6p forums though so I recommend checking out some other ROMs too.
XxMORPHEOUSxX said:
The bootloader message won't go away until you lock the bootloader. Its just there as a warning to you in case you did not unlock your phone. As for CM I'm sure there are still many bugs to be worked out. I know I'm going to wait before Flashing it until I see people enjoying it as a daily driver. There are some great devs here in the n6p forums though so I recommend checking out some other ROMs too.
Click to expand...
Click to collapse
i understand the boot message and CM - i have tried other roms too. i'm not the only one who is getting bootloops on every rom. not sure what to do mate. it says corrupted then boot loops upon restart
Xtra-arrow said:
i understand the boot message and CM - i have tried other roms too. i'm not the only one who is getting bootloops on every rom. not sure what to do mate. it says corrupted then boot loops upon restart
Click to expand...
Click to collapse
Maybe this will be helpful. I think you have the red level warning like this user. Seems like the exact same situation.
http://forum.xda-developers.com/showthread.php?p=64403982
Turns out it isn't bootlooping. Its taking at least 3 minutes to turn on. It looks like bootlooping. BUt if finally loaded. After doing my uninstalling of aomw system apps. Its rebooted and keeps optimising apps. 2-4 then restarts and does same
Info
Heisenberg said:
Whoa! Don't tell him to wipe everything in the advanced wipe menu, that'll wipe the internal storage too which is completely unnecessary.
Click to expand...
Click to collapse
It s necessary to Wipe everything when don't know which modification cause the problem.
+ Recovering the backup also not working for this situation.
@Xtra-arrow
Can u explain step-by-step what u did so far
more detail = better help
:good:
Geeks Empire said:
It s necessary to Wipe everything when don't know which modification cause the problem.
+ Recovering the backup also not working for this situation.
@Xtra-arrow
Can u explain step-by-step what u did so far
more detail = better help
:good:
Click to expand...
Click to collapse
No it isn't necessary to wipe the userdata partition. No modifications are stored in the userdata partition. It would only be necessary to wipe system, data, cache, and dalvik cache. And probably flash the vendor partition too. Not userdata though.
I had a similar problem when I botched a SU flash, same warning then it would take forever to boot, then the rom would degrade over the next several minutes. I know its not fun to start over, but it was the only thing that cleared all the problems. I didn't want to take more time finding another solution when going back to stock is so simple with this device. Follow the instructions in step #11 of Heisenberg's guide (great guide, I link it to friends a lot). Then start again, I know, not what you wanted to hear. Hope this helps!
I am also in agreement with Heisenberg in regards to the userdata partition.
Geeks Empire said:
It s necessary to Wipe everything when don't know which modification cause the problem.
+ Recovering the backup also not working for this situation.
@Xtra-arrow
Can u explain step-by-step what u did so far
more detail = better help
:good:
Click to expand...
Click to collapse
Thank you very much for replying. I have found the root of the cause but no solution. Uninstalling or disabling system apps will cause my phone to go into a "optimising apps" boot loop on the next restart. What do you think? ++ every restore I make on twrp either soft bricks or bootloops. Crazy!
Info
Xtra-arrow said:
Thank you very much for replying. I have found the root of the cause but no solution. Uninstalling or disabling system apps will cause my phone to go into a "optimising apps" boot loop on the next restart. What do you think? ++ every restore I make on twrp either soft bricks or bootloops. Crazy!
Click to expand...
Click to collapse
If you are sure about reason Forget ur Backups.
you should completely install Stock Kernel, Rom, Boot.img >> Back to Stock
But If I remember correctly u did this before...
I just have to say Retry Also Install and use Nexus Root Toolkit
:good:
I have reinstalled original stock files from google. I've wiped everything numerous times. Installed ROMs just after. It took me a while but I think it comes down to the system apps. I'm running a custom ROM, cm13 and my phone is running fine. I know if I was to delete all the unwanted apps off my phone, on next reboot it will try and optimise apps, finish. Says starting apps... Then reboots. Follows the same process.
Xtra-arrow said:
I have reinstalled original stock files from google. I've wiped everything numerous times. Installed ROMs just after. It took me a while but I think it comes down to the system apps. I'm running a custom ROM, cm13 and my phone is running fine. I know if I was to delete all the unwanted apps off my phone, on next reboot it will try and optimise apps, finish. Says starting apps... Then reboots. Follows the same process.
Click to expand...
Click to collapse
Can I ask what gapps are you using? Are you using your google account to recover your apps, or are starting fresh each time?
Sent from my Nexus 6P using Tapatalk
Thanks for your reply. I've actually now narrowed itnright down to a few apps, maybe gapps. Sound recorder, voice recorder app and the google app. Either one or more of these cause my optimising apps bootloop.