Related
Hi guys,
The question is as above. How do I update my paranoid android rom through goo manager?
I downloaded the new rom files but I ain't sure what to do under the flahs rom section. Do i have to do a factory reset or do i have to wipe the cache?
I tried updating once without any of these options. In the end, i lost my google apps. When I reinstore it, the expanded desktop function went missing. So I am hoping that someone can tell me the proper way of flashing it to avoid this problem in the future. Thank you!
Go read the first post of the paranoid android rom under android original development. Don't flash things until you read the instructions. Cache is wiped by the rom, and you need gapps with a new install.
Sent from my Nexus 7 using xda app-developers app
delonicdevil said:
Hi guys,
The question is as above. How do I update my paranoid android rom through goo manager?
I downloaded the new rom files but I ain't sure what to do under the flahs rom section. Do i have to do a factory reset or do i have to wipe the cache?
I tried updating once without any of these options. In the end, i lost my google apps. When I reinstore it, the expanded desktop function went missing. So I am hoping that someone can tell me the proper way of flashing it to avoid this problem in the future. Thank you!
Click to expand...
Click to collapse
as mentioned, you should always read the ROM thread completely before you flash.
the correct procedure is to download the updated zip, optionally check the md5 sum to make sure it did not get corrupted in transit [but if it got corrupted, I think CWM will tell you, and fail to even try to flash the zip], then flash the rom, and then flash gapps before rebooting. [if you reboot before flashing gapps, you will have to re-login, and re-authenticate apps like Google Voice, etc].
mvmacd said:
as mentioned, you should always read the ROM thread completely before you flash.
the correct procedure is to download the updated zip, optionally check the md5 sum to make sure it did not get corrupted in transit [but if it got corrupted, I think CWM will tell you, and fail to even try to flash the zip], then flash the rom, and then flash gapps before rebooting. [if you reboot before flashing gapps, you will have to re-login, and re-authenticate apps like Google Voice, etc].
Click to expand...
Click to collapse
and one more thing, flash a new kernel ONLY after the first reboot.
Billchen0014 said:
and one more thing, flash a new kernel ONLY after the first reboot.
Click to expand...
Click to collapse
thanks alot!
Billchen0014 said:
and one more thing, flash a new kernel ONLY after the first reboot.
Click to expand...
Click to collapse
OH..I didn't knew it. Thanks!
I am not getting on how to do that
Hi,
Can any one post link to forum?
I am using paranoid android and in goomanager its showing new update available..!
after downloading zip what to do next?
If any one can put screenshot or list step it would be much helpful..
Thanks in advance...
Balaji_NEXUS said:
OH..I didn't knew it. Thanks!
Click to expand...
Click to collapse
Billchen0014 said:
and one more thing, flash a new kernel ONLY after the first reboot.
Click to expand...
Click to collapse
This actually makes no difference, aside from making the process more time consuming. The few and far between anecdotes that led to this practice are a cum hoc ergo propter hoc fallacy. Without a doubt, it does not hurt anything, but it also yields no real benefit over flashing in the same recovery session.
Billchen0014 said:
and one more thing, flash a new kernel ONLY after the first reboot.
Click to expand...
Click to collapse
This doesn't really matter, apart from making you have to "Android is Upgrading" 2x.
The process I follow which never fails me is (there may be a quicker way, but I know this will always work):
1 - Download ROM / Kernel / GAPPS etc
2 - Move all downloaded files to a single folder named "Flashing" or something
3 - Reboot to Recovery
4 - Wipe Cache and Dalvik Cache
5 - Flash ROM
6 - Flash GAPPS
7 - Flash Kernel
8 - Wipe Cache / Dalvik
That is the process for updating Paranoid android
Updating to a completely different ROM would require a Factory reset and Format
Wilks3y said:
This doesn't really matter, apart from making you have to "Android is Upgrading" 2x.
The process I follow which never fails me is (there may be a quicker way, but I know this will always work):
1 - Download ROM / Kernel / GAPPS etc
2 - Move all downloaded files to a single folder named "Flashing" or something
3 - Reboot to Recovery
4 - Wipe Cache and Dalvik Cache
5 - Flash ROM
6 - Flash GAPPS
7 - Flash Kernel
8 - Wipe Cache / Dalvik
That is the process for updating Paranoid android
Updating to a completely different ROM would require a Factory reset and Format
Click to expand...
Click to collapse
You can safely leave off steps 2, 4, & 8
Anything you download using goo goes into a folder called goo manager. Just flash from there.
Wiping cache and dalvik is an old wives tale so to speak. You aren't doing a damn bit of good doing that. You can skip it
Sent from my Galaxy Nexus
Pirateghost said:
You can safely leave off steps 2, 4, & 8
Anything you download using goo goes into a folder called goo manager. Just flash from there.
Wiping cache and dalvik is an old wives tale so to speak. You aren't doing a damn bit of good doing that. You can skip it
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
I know about the Goo Folder, however I like to keep all my stuff in the same place, and I download my Kernels from browser so I made my own for Flashing
Why is it a wives tale?
Thanks
Wilks3y said:
I know about the Goo Folder, however I like to keep all my stuff in the same place, and I download my Kernels from browser so I made my own for Flashing
Why is it a wives tale?
Thanks
Click to expand...
Click to collapse
Because when you flash a new ROM to /system, it has to rebuild the dalvik for the signature on the new ROM. Android handles this on its own. I haven't checked but I bet the updater-script wipes cache for you also. I have never manually wiped cache and dalvik for a ROM update on my nexus devices.
Sent from my Galaxy Nexus
Pirateghost said:
Because when you flash a new ROM to /system, it has to rebuild the dalvik for the signature on the new ROM. Android handles this on its own. I haven't checked but I bet the updater-script wipes cache for you also. I have never manually wiped cache and dalvik for a ROM update on my nexus devices.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Thanks for the advice bud
I'm guessing its still necessary if going to a whole new ROM?
Wilks3y said:
Thanks for the advice bud
I'm guessing its still necessary if going to a whole new ROM?
Click to expand...
Click to collapse
When going from one rom to another the only thing that you should do is run factory reset in recovery
Sent from my Galaxy Nexus
Pirateghost said:
When going from one rom to another the only thing that you should do is run factory reset in recovery
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Ok great.
Appreciate that
Can anyone help me please, I have posted this on the PA thread but have had no response
I am unable to install PA on my nexus.
I have rooted and unlocked my device via the nexus root kit, downloaded the latest TWRP and installed this on my device. Moved PA and GAPPS to my storage and flashed PA first and then GAPPS, wiped dalvik and reboot the device. All that happens is the ROM doesnt appear to want to flash on the device as it reset my nexus back to factory settings but never installed the ROM.
I have also attempted this with goomanager but get stuck in a bootloop after install
However, I have been able to download and install CWM and CM10 so I know there is no issue with the device.
Can anyone provide any insight as to why this may be happenening
Have you verified the md5 of your download?
Also, patience is a virtue. Believer or not, some questions aren't always answered in mere minutes, as most folks have lives outside of the forum. I know waiting can seem unreasonable at times, but the timespan between you asking in the PA thread and then starting this completely new thread asking the same question was less than twenty minutes.
Sent from my Nexus 7 using Tapatalk HD
You left out the most important step in switching from one ROM to another... As mentioned in several tutorials and posts:
WIPE DATA/FACTORY RESET before flashing ROM...
Sent from my Galaxy Nexus
Pirateghost said:
You left out the most important step in switching from one ROM to another... As mentioned in several tutorials and posts:
WIPE DATA/FACTORY RESET before flashing ROM...
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
It helps but for the last 3 different roms I've thrown onto my n7 I haven't done that, All I've had to do was wipe my caches.
Eagle1337 said:
It helps but for the last 3 different roms I've thrown onto my n7 I haven't done that, All I've had to do was wipe my caches.
Click to expand...
Click to collapse
Wiping caches is unnecessary. New cache is built upon first boot.
You might have gotten away without wiping data if the bases for your ROMs were similar. Paranoid requires a wipe coming from most other ROMs.
Also you run the risk of corrupting your settings and app databases when you don't wipe data between different ROMs
Sent from my Galaxy Nexus
Hi,
I flashed the Google 4.3 S4 Rom and used TWRP 2.5.0.2 and Goo with instructions I found on the boards.
- I am a Canadian (Rogers/FIDO) S4
- I used the 4.3 ROM Deodexed
So now the problems:
1) I originally installed it and it was constantly stuck on 'Samsung Galaxy S4' Screen, couldn't proceed barely got into recovery and reflashed; this worked and it booted google and i realized why this happened is because i accidentally erased my data.
2) The second time, I simply turned off my phone and turned it back on, again i was stuck on 'Samsung Galaxy S4' Screen, no way of doing anyhing except turnging off the phone and trying again and again to get to recovery, I then flashed to 4.3 again off the external.
3) I simply tried to open facebook and the phone booted and went on to the 'Samsung Galaxy S4' Screen and is stuck again! Even when I reboot through Team Win Recovery v2.5.0.2 to System I get the same boot loop.
I am super frustrated with this, what can I do and at this point I'm getting to the point where I would like some help to go back to stock. I would also like some input as to why this is happening if anyone has any suggestions or help it would be greatly appreciated.
Thank You.
notorious99 said:
Hi,
I flashed the Google 4.3 S4 Rom and used TWRP 2.5.0.2 and Goo with instructions I found on the boards.
- I am a Canadian (Rogers/FIDO) S4
- I used the 4.3 ROM Deodexed
So now the problems:
1) I originally installed it and it was constantly stuck on 'Samsung Galaxy S4' Screen, couldn't proceed barely got into recovery and reflashed; this worked and it booted google and i realized why this happened is because i accidentally erased my data.
2) The second time, I simply turned off my phone and turned it back on, again i was stuck on 'Samsung Galaxy S4' Screen, no way of doing anyhing except turnging off the phone and trying again and again to get to recovery, I then flashed to 4.3 again off the external.
3) I simply tried to open facebook and the phone booted and went on to the 'Samsung Galaxy S4' Screen and is stuck again! Even when I reboot through Team Win Recovery v2.5.0.2 to System I get the same boot loop.
I am super frustrated with this, what can I do and at this point I'm getting to the point where I would like some help to go back to stock. I would also like some input as to why this is happening if anyone has any suggestions or help it would be greatly appreciated.
Thank You.
Click to expand...
Click to collapse
Have you try using Odin to go back to stock?
shizs14 said:
Have you try using Odin to go back to stock?
Click to expand...
Click to collapse
I am not sure what that is, but I can try to search it, could you point me in the right direction as to how to do that?
notorious99 said:
I am not sure what that is, but I can try to search it, could you point me in the right direction as to how to do that?
Click to expand...
Click to collapse
Rule #1. Learn Odin before attempting anything on Samsung phones
notorious99 said:
I am not sure what that is, but I can try to search it, could you point me in the right direction as to how to do that?
Click to expand...
Click to collapse
You need to read these threads and make sure to read the threads linked in these threads that have to do with your phone...
http://forum.xda-developers.com/showthread.php?t=2301762
and
http://forum.xda-developers.com/showthread.php?t=2312444
You can use the forum's search function to help you find specific information. Good luck.
agreed, odin should be the first thing any noob should learn.
Scott, you da man...
scott14719 said:
You need to read these threads and make sure to read the threads linked in these threads that have to do with your phone...
http://forum.xda-developers.com/showthread.php?t=2301762
and
http://forum.xda-developers.com/showthread.php?t=2312444
You can use the forum's search function to help you find specific information. Good luck.
Click to expand...
Click to collapse
So I flashed a different rom (4.2.2 google) and I tested turning my phone off and then on again, and SAME issue, it boot loops at the S4 screen, what is the deal with that specifically? does anyone have any ideas?
notorious99 said:
So I flashed a different rom (4.2.2 google) and I tested turning my phone off and then on again, and SAME issue, it boot loops at the S4 screen, what is the deal with that specifically? does anyone have any ideas?
Click to expand...
Click to collapse
Which google rom 4.2.2? there are a few, meaning where did you get the rom?
Which kernel did you use?
you say you have this...both roms require a certain kernel. Depending on whose rom you flashed.
I am a Canadian (Rogers/FIDO) S4
- I used the 4.3 ROM Deodexed
TheAxman said:
Which google rom 4.2.2? there are a few, meaning where did you get the rom?
Which kernel did you use?
you say you have this...both roms require a certain kernel. Depending on whose rom you flashed.
I am a Canadian (Rogers/FIDO) S4
- I used the 4.3 ROM Deodexed
Click to expand...
Click to collapse
THE ROM
Google Edition 4.2.2 - v1.3 - http://d-h.st/Lm8
posted here: http://forum.xda-developers.com/showthread.php?t=2341376
MY KERNEL as it is on my phone currently is:
Baseband: 1337MVLUAMDJ
Kernel: 3.4.0-Google-Edition, [email protected]#1,
Build Number: JDQ39.1337
AND I'm using TWRP Custom
-----------------------------------------
notorious99 said:
THE ROM
Google Edition 4.2.2 - v1.3 - http://d-h.st/Lm8
posted here: http://forum.xda-developers.com/showthread.php?t=2341376
MY KERNEL as it is on my phone currently is:
Baseband: 1337MVLUAMDJ
Kernel: 3.4.0-Google-Edition, [email protected]#1,
Build Number: JDQ39.1337
AND I'm using TWRP Custom
-----------------------------------------
Click to expand...
Click to collapse
Ok, now we're cooking, thanks for the info...
I haven't tried that rom yet, I am going to d/l it and give it a shot. Be back shortly.
ODIN back to stock, and start over from there, and take care to flash/erase properly. backup user apps/data if you can (there are non-root options) and restore when you finish flashing 4.3 and are sure its stable.
Ok..back...I flashed this rom I booted with the kernel supplied in rom. Hmm..it is kernel related for sure. Have you posted the issue in that roms thread? May want to give that a shot.
I'm on canadian S4 aswell and I also flashed the 1.3 Google edition but flashed faux kernel. Works like a charm.
Sent from my SGH-I337 using Tapatalk 4 Beta
Thank you to all you guys. I successfully used odin to get back to stock. I still have no idea why I had so many problems but will try the Google Rom again when I feel more comfortable.
Thanks again!
notorious99 said:
Thank you to all you guys. I successfully used odin to get back to stock. I still have no idea why I had so many problems but will try the Google Rom again when I feel more comfortable.
Thanks again!
Click to expand...
Click to collapse
Proper wiping steps is key when changing ROM bases. Do a factory reset, wipe both caches, format /system, and if coming from TW, format the internal also.
Here is a post by TeamWin on wiping for Roms. Formatting Data is not part of "normal" wipe process. It wipes your internal sd.
http://teamw.in/whattowipe
These guys are far above me. But my preferred method is to "Wipe" System/Data/Both Caches. I actually do it twice. I know many say no need, but I do. I did this for many years on previous phones and never had issues. If on Nightlies or incremental updates did not wipe unless OP said to.
rugmankc said:
Here is a post by TeamWin on wiping fro Roms. Formatting Data is not part of "normal" wipe process. It wipes your internal sd.
http://teamw.in/whattowipe
These guys are far above me. But my preferred method is to "Wipe" System/Data/Both Caches. I actually do it twice. I know many say no need, but I do. I did this for many years on previous phones and never had issues. If on Nightlies or incremental updates did not wipe unless OP said to.
Click to expand...
Click to collapse
The internal wiping isn't necessary, but it does get rid of TW folders that you don't need if switching to AOSP.
I think you could delete them individually as opposed to formatting entire internal with other rom backups/kernels/gapps etc. I also have music/pics on internal too. Also, I like some will go back and forth btwn aosp and tw. So, I would want to keep them. I never did that, but read about some having issues after Formatting Data
All IMHO--
rugmankc said:
I think you could delete them individually as opposed to formatting entire internal with other rom backups/kernels/gapps etc. I also have music/pics on internal too. Also, I like some will go back and forth btwn aosp and tw. So, I would want to keep them. I never did that, but read about some having issues after Formatting Data
All IMHO--
Click to expand...
Click to collapse
You're right, it's an overkill. Just my OCD nature kicks in sometimes.
+1
I understand OCD hence my wiping twice--hey sometimes 3x
Monk has nothing on me, If you are familiar with that tv show--
I am OCD thru and thru--
Hello everyone it is unfortunate that this has to be my first post on this forum but I need some help . I have a Samsung galaxy s4 SGH i337m **Canadian version** It has been rooted and I have installed team win recovery project ... However I cannot seem to get any of the Roms I want to flash onto my device .. I HAVE managed to flash Cyanogen mod 4.4 KitKat to my s4 but I notice it is very laggy and also it will not allow me to over clock my device it just resets and goes back to standard CPU settings ... I would Either like to flash Gummy ROM 4.4 KitKat or stock ROM KitKat but it will not work for me ... The process I do is this ... 1 Go to the webpage and download the correct ROM for the Canadian S4 and I also download the Gapps ... 2 once the download is complete I reboot into recovery .... 3 I create a backup ... 4 I factory reset and wipe cache and delvik... 5 I go to the ROM and I swipe to install it ... and it FAILS every time it also fails for PAC ROM ... When this happens I restore my backup and connect the device to my PC and I go and delete the ROMs and Gapps that failed to install... I do not understand what I'm doing wrong this is nearly making me regret getting rid of my nexus 4 I never had ANY problems with it .... Can someone please tell me how to fix my problem.... Also if my problem is fixed I WILL be donating to XDA for all the help and support. Thank you.
You need to do a factory reset after your backup. Wiping just the cache and dalvik will fail 99% of the time.
Sent from my SGH-I337 using XDA Premium 4 mobile app
graydiggy said:
You need to do a factory reset after your backup. Wiping just the cache and dalvik will fail 99% of the time.
Sent from my SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ok so i just did that i created a backup ... Wiped cache and delvik .... Factiory reset and went to flash the ROM and it says failed so i read it it says this file is for JfLteCan .... I have no idea what that means but I do know I am downloading the ROM for the SGH i337m Canadian Version
OK so I'm not sure if I stumbled across the problem myself or not ... After Rooting and installing team win recovery .. My model number appears to have been changed to SGH M919 is it normal for this to change? I'm downloading the ROM for the SGH M919 hopefully it makes a difference . if not I'll repost .
This Did not work . still said failed
Timtim1234321 said:
This Did not work . still said failed
Click to expand...
Click to collapse
Did you get the correct twrp for your device. Also get the latest version should be something like 2.6.3.4. Then in twrp do the default wipe, the one where you use the slider. Then flash the rom. Then flash gapps if the rom needs it. Then boot.
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.