Related
I was on 4.2.1, rooted, and with TWRP as recovery.
I wanted to get the OTA to 4.2.2 so I did full Titanium backup and then used the WugFresh toolkit to flash stock 4.2.1.
After flashing, I was offered the OTA which I allowed to install.
When finished, I got root back with Rootkeeper and restored all Apps and Data (not System data) with Titanium.
Everything was working, but on every reboot I got the message :
"System UIDs Inconsistent. UIDs on the system are inconsistent, you need to wipe your data partition or your device will be unstable."
I also found that My Phone Explorer would no longer connect via USB so I decided to go back to 4.2.1.
I again flashed it with the toolkit and did another restore with Titanium. Again, everything seems to be working, but I still get this message on every boot.
I thought using Titanium Backup was a standard way of restoring apps and data.
How do I get rid of this message without wiping and reinstalling all my Apps individually, which means losing all my game scores, etc?
I also see that in Bootloader there is a line
"Signing - not defined yet".
I do not know if that was there before flashing back to stock.
same problem
system UIDs inconsistent, it keeps showing up after every boot.
i have nexus 7 GSM 32 gb rooted using nexus 7 toolkit with clockworkmod recovery, android version 4.2.1 build number JOP40D
i tried Rom manager fix permission the same problem, i don't like resetting it any suggestion
thank you
windwhisper said:
system UIDs inconsistent, it keeps showing up after every boot.
i have nexus 7 GSM 32 gb rooted using nexus 7 toolkit with clockworkmod recovery, android version 4.2.1 build number JOP40D
i tried Rom manager fix permission the same problem, i don't like resetting it any suggestion
thank you
Click to expand...
Click to collapse
I found the answer in another thread. I used TWRP (Advanced - Fix Permissions). It was instantly fixed.
I took a full backup before trying this, but didn't need it.
devra1 said:
I found the answer in another thread. I used TWRP (Advanced - Fix Permissions). It was instantly fixed.
I took a full backup before trying this, but didn't need it.
Click to expand...
Click to collapse
it took me time and I did it using clockwork mod recovery
advanced then fix permissions
but nothing happen , still the same.
should I try flashing TWRP recovery then..
if yes. could u help me with a simple guide
much appreciated
thank you
Sent from my Nexus 7
windwhisper said:
it took me time and I did it using clockwork mod recovery
advanced then fix permissions
but nothing happen , still the same.
should I try flashing TWRP recovery then..
if yes. could u help me with a simple guide
much appreciated
thank you
Sent from my Nexus 7
Click to expand...
Click to collapse
You can boot any recovery you want without hard-flashing it to the device (so long as the boot loader is unlocked).
With the device in bootloader/fastboot mode,
Code:
fastboot boot name-of-recovery-image-file.img
So download TWRP and give it a roll.
Hello,
I got the same "System UIDs Inconsistent" problem. I like to solve my problems myself but I've got no way out this time, so I'm asking for your kind help.
I'm on the SGS III, i9300, I rooted it then went to Omega ROM, and then to Paranoid Android. Everything went well until I got a battery problem (when charging the phone, it was not sufficient to bear with it functionning, so it powered out while charging). After that, the phone restarted and the UID problem appeared. Maybe it's just a coincidence.
So far, I : fixed permissions, did at least 10 factory resets with TWRP, changed ROM (went to CM and came back to PA as nothing changed).
I read the 6 first post about this in xda forum, and other forums too, but nothing came out as an evidence.
Last thing I did was upgrade my PA ROM : the phone couldn't even go beyond the booting process, failed to initiate the phone "first settings" app.
So I came back to the previous version of PA, and was able to use my phone again, but apps like Gmail, Color Note, won't work.
I want to get rid of that, and I wish someone told me, step by step, the things I could do to eradicate the problem. I will do what's necessary to achieve that, I only need someone who knows what to do, and how to do it. I saw some tricks that maybe could do the job but I don't have the knowledge to choose one.
That's my first message here so I hope I didn't break the rules of the forum ^^ If you want any informations about my device to help me, just ask
Thanks a lot, and I hope my english is not too bad ! Have a good day.
Thanks
I got this message too without having any other problem with this TWRP version or Hairy Bean 2.2
The message appeared after flashing the new 4.2.1 (?) modded bootloader for Hairy Bean and the ROM itself.
I'm not sure whether the ROM or bootloader are causing it but mine got fixed by fixing the permissions via TWRP.
Thanks for the tip! :good:
In my case only re-partitioning helped.
for me uninstalling quadrant did the trick
That did it
devra1 said:
I found the answer in another thread. I used TWRP (Advanced - Fix Permissions). It was instantly fixed.
I took a full backup before trying this, but didn't need it.
Click to expand...
Click to collapse
Quick and easy. Worked for me. Thanks
devra1 said:
I found the answer in another thread. I used TWRP (Advanced - Fix Permissions). It was instantly fixed.
I took a full backup before trying this, but didn't need it.
Click to expand...
Click to collapse
This worked for me, too. Thank you.
My situation was a little bit different:
- Flashed Paranoid Android 3.99
- everything was fine (for a few reboots) until I made a nandroid back up with CWM 6.0.3.6 ( which was surprisingly slow, almost 1,5h)
- rebooted
- UID consistency problem
- tried to boot temporary into TWRP - NOT POSSIBLE!
- flashed TWRP 2.6.0.0 permanently
- TWRP: advanced - fix permissions: SUCCESSFUL!
Maybe I'll keep TWRP, but I'm used to CWM for years now.
CWM has removed "fix permissions" since 6.0.3.5 (http://review.cyanogenmod.org/#/c/45945/ )
Fix Permissions
For me worked fixing permissions through TWRP on CM 10.2 latest nightly (10082013).
edbertin said:
For me worked fixing permissions through TWRP on CM 10.2 latest nightly (10082013).
Click to expand...
Click to collapse
Me too! TWRP on SlimRom 4.3
Thanks
I am also having this issue after I flashed SlimBean Beta 4 Weekly-409 on my i9300 (wipe data/cache/dalvik and clean install with gapps) and tried restoring a couple of apps like Any do and Temple Run 2 with Titanium Backup.
Is the TWRP being referred here mean the TWRP manager? I installed it from play store but I don't find 'fix permissions' option anywhere in it.
I remember of seeing it in SuperSU but I am unable to install that as well as it says the binary needs to updated.
Could someone please help me here?
Thanks!
--IH
Confirmed. Get into the TWRP n do a fix cache wipe/dalvik wipe/fix permission
Thank you for clarifying this fix
polarfrz said:
Quick and easy. Worked for me. Thanks
Click to expand...
Click to collapse
I just updated my S4 to 10.1 Hyperdrive and experienced this very same issue. Rebooting into safestrap and fixing permissions cleared up this very annoying issue on my phone.
I flashed gummy V4.4 yesterday works great. I went into rom toolbox and changed LCD density to 361 and rebooted, got the UID inconsistent message.
found this thread, fix permissions in TWRP, all fixed. bing bang boom.
thanks all, I also fixed with TWRP latest version, and try to roll back to CWM
I installed a new ROM and I got the System UIDs inconsistent error, then my S Planner FC. I went to find the txt file and it stated that the problem is related to Calendar Storage. I deleted the apk and placed a new one back in. Problem persists, I scratched my head for so long and then I found this thread.
THANK YOU, fixing permission for the Calendar Storage did the trick! Thank God I found this thread!
Hi guys,
I tried to update my Nexus 4 to 4.4 when Google pushed the update out for it yesterday, I forgot I had unlocked the phone (I don't have any custom ROMs on it, just SuperSU.)
Every time I try and power it on, the loading screen is endless, although I can hold power and volume down to enter recovery mode, nothing seems to be working.
I am a bit of a novice so any help or suggestions would be really appreciated!
Thanks.
The first few pages of the forum is littered with posts like this, i was in the same situation.
What i did was download the 4.3 rom from google, and flash /boot and /system onto the phone. I suspect the 4.4 rom would also work.
This got the phone booting without harming (most of) my data, but much of the UI was mangled and didnt work properly. I tried to backup my images over USB but it didnt work, you might have a better result. I also wanted to backup my SMS but they had all vanished.
I rebooted the phone to recovery (TWRP) and used adb to backup the sdcard (adb pull /sdcard sdcard) then did a full flash using the 4.4 rom downloaded from google and that got it working again. Then i reflashed the latest version of TWRP recovery and SuperSU.
Hope that helps.
That's really helpful, thanks! Is there ANY chance of a step-by-step? I'm a complete 'noob' probably a mistake to root in the first place :crying:
If you're busy don't worry, just don't want to **** things up more than I have haha.
Thanks, appreciate it.
GeorgeAmodio said:
That's really helpful, thanks! Is there ANY chance of a step-by-step? I'm a complete 'noob' probably a mistake to root in the first place :crying:
If you're busy don't worry, just don't want to **** things up more than I have haha.
Thanks, appreciate it.
Click to expand...
Click to collapse
Look here http://forum.xda-developers.com/showthread.php?t=2010312 for flashing a factory image guide.
gee2012 said:
Look here http://forum.xda-developers.com/showthread.php?t=2010312 for flashing a factory image guide.
Click to expand...
Click to collapse
Got stuck in google screen, tried to flash factory images but my pc won't detect the phone anymore. Any advice?
Edit: Solved.
arffrhn said:
Got stuck in google screen, tried to flash factory images but my pc won't detect the phone anymore. Any advice?
Edit: Solved.
Click to expand...
Click to collapse
Cheers guys, a lot more helpful than the bloke from Google. Will try it in the morning!
This will surely help
If somebody is facing boot loop after kitkat update on nexus 4 and no data backup can try to go to safe mode and backup their data. To goto safe mode on boot screen just keep pressing up and down volume button for some time phone will get into safe mode and can be backed up.
Hi,
It also happened to me, dont know if it is related to having ROOT or not, but i had to manually flash factory image (4.4) and it worked. I flashed everything except userimage.img but on first boot it took like 15 minutes to reboot and then all my personal data (photo, music...) was gone....
So just be cautious before upgrading!
Hi,
It also happened to me, dont know if it is related to having ROOT or not, but i had to manually flash factory image (4.4) and it worked. I flashed everything except userimage.img but on first boot it took like 15 minutes to reboot and then all my personal data (photo, music...) was gone....
So just be cautious before upgrading!
gee2012 said:
Look here http://forum.xda-developers.com/showthread.php?t=2010312 for flashing a factory image guide.
Click to expand...
Click to collapse
Yeah that is pretty much what I did to fix mine except that I did not flash the userdata (step 10 in chapter D) so that I would't loose my data.
arffrhn said:
Got stuck in google screen, tried to flash factory images but my pc won't detect the phone anymore. Any advice?
Edit: Solved.
Click to expand...
Click to collapse
What did you end up doing for your PC to detect your phone?
iamj00 said:
What did you end up doing for your PC to detect your phone?
Click to expand...
Click to collapse
I had sideloaded a rom in recovery so that it will replace the lost system.img on my phone. Then, it booted up and I flashed back factory images the usual way. Everything is running smoothly again.
arffrhn said:
I had sideloaded a rom in recovery so that it will replace the lost system.img on my phone. Then, it booted up and I flashed back factory images the usual way. Everything is running smoothly again.
Click to expand...
Click to collapse
I don't know what any of that means or how to do it...
iamj00 said:
I don't know what any of that means or how to do it...
Click to expand...
Click to collapse
This is sideload guide. And the is the rom I used to sideload before: Purity. After I had successfully booted into the system. I flashed 4.4 factory images using this awesome noob friendly guide for a clean kitkat update.
arffrhn said:
I had sideloaded a rom in recovery so that it will replace the lost system.img on my phone. Then, it booted up and I flashed back factory images the usual way. Everything is running smoothly again.
Click to expand...
Click to collapse
iamj00 said:
What did you end up doing for your PC to detect your phone?
Click to expand...
Click to collapse
Installing the driver. Refer to this thread http://forum.xda-developers.com/showthread.php?t=1992345
Boot to bootloader and connect to your PC, usually Windows will find the driver automatically
My device:
SPH-L720
Android 4.4.2
Baseband L720VPUFNAE
Kernel Version [email protected] #2 Mon Feb 24 14:19:28 EST 2014
Carbon Version: CARBON-KK-SHINYSIDE-EDITION-20140224-140
Build Number: carbon-jfltespr-userdebug 4.4.2 KVT49L e71e225082 test-keys
SELinux status
Enforcing
Interal space/free: 9.59/8.84
I have formatted my phone completely. There was no rom on it, nothing installed on the SD card. Formatted the system, data, cache, preload, etc. I installed the stock firmware NAE with odin, and it went fine. I booted the device, and it boots into a encrypted screen. When I try to press enter, it says failed. When I type in a previous password of mine, it fails. I shut down the phone, boot into download mode. I install root with CF-root via odin, and flash the NAE modem. I shut down the phone, and put it back into download mode. I install philz-touch recovery, and i install a stock, rooted Deodexed rom. It installs, and reboots. Once it boots, i get an ecnrypted screen.
If i install a different rom, anything Cyanogenbased (hellkat, cyanogen, carbon) then I do not have this problem. Does anyone know what's going on? I have formatted my phone 4 times now. The device was once encrypted, but I have removed that several roms ago.
Can someone tell me what's going on?
edit/
I'm seeing stuff about knox security. Is this what i'm seeing?
edit-fixed!
Alright, thanks to a user suggestion in this thread this is what I have done.
1) Install Unofficial Carbon and complete the initial setup.
2) Encrypt the device. Your phone must be plugged in, and at least 80% battery.
3) Then rebooted into Philz Touch recovery, and cleaned to install a new rom.
4) Installed 4.3 stock(ish) rom
5) I was then able to boot, and the device did not ask for an encryption password.
The only conclusion I can come up with is that since I re-encrypted the data, that it deleted it and the old partition when I cleared my system/data. I have no idea to be honest, but now the phone works.
I was not able to get any stock rooted firmware other than Stock(ish) to work with the modem. I flashed it, I used CDMA to write the PRL..but nothing. I may try to do that later, but for now i'm on an essentially stock 4.4 ROM with an NAE modem.
Sorry, but if your phone was encrypted before, you may be out of luck with out a password. If it was as easy as a factory reset to defeat encryption than your data would never be safe. You may need to take it into Sprint and see if the tool they use to force a firmware install can fix it. Also, if you have an sdcard installed remove it and try to odin the stock tar again and boot up. It may just be that your sdcard has been encrypted and without it in your phone it will work.
cruise350 said:
Sorry, but if your phone was encrypted before, you may be out of luck with out a password. If it was as easy as a factory reset to defeat encryption than your data would never be safe. You may need to take it into Sprint and see if the tool they use to force a firmware install can fix it. Also, if you have an sdcard installed remove it and try to odin the stock tar again and boot up. It may just be that your sdcard has been encrypted and without it in your phone it will work.
Click to expand...
Click to collapse
The Sdcard isn't in when I am experiencing the problem. The encryption before shouldn't matter, as it's been formatted and i've installed countless roms since.
Looking for a better answer
Nobody has had this issue or knows someone that has? A google search hasn't returned anything useful other than what i've already done.
Encryption has nothing to do with SD cards. You can encrypt your phone data. And without that password, no amount of flashing with get you back in.
Sounds like you need a visit to a Sprint store to help. They have tools that can get you back in to your phone.
Sent from my XT1080 using XDA Premium 4 mobile app
VandyCWG said:
Encryption has nothing to do with SD cards. You can encrypt your phone data. And without that password, no amount of flashing with get you back in.
Sounds like you need a visit to a Sprint store to help. They have tools that can get you back in to your phone.
Sent from my XT1080 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I don't see how me encrptying the device won't bring the storage area back. If i format an encrypted flash drive, i get all of my storage back?
I visited the spring store today, and they told me they couldn't help me..so i'm here again.
could it be possible that re-encrypting while your runnin on cyanogenmod rom would either over-ride or over write the previous encryption? (i have little knowledge of encryption, but just a thought)
bioshocked said:
could it be possible that re-encrypting while your runnin on cyanogenmod rom would either over-ride or over write the previous encryption? (i have little knowledge of encryption, but just a thought)
Click to expand...
Click to collapse
That's an interesting idea..will give it a go later.
backdown said:
I don't see how me encrptying the device won't bring the storage area back. If i format an encrypted flash drive, i get all of my storage back?
I visited the spring store today, and they told me they couldn't help me..so i'm here again.
Click to expand...
Click to collapse
I think the issue is, once you encryrpt your device, its encrypted. Have you tried to ODIN back to stock firmware. You would probably lose your data, but you would get your phone back.
That's a guess. But this highlights a reason why encypting devices can be bad.
VandyCWG said:
I think the issue is, once you encryrpt your device, its encrypted. Have you tried to ODIN back to stock firmware. You would probably lose your data, but you would get your phone back.
That's a guess. But this highlights a reason why encypting devices can be bad.
Click to expand...
Click to collapse
I have already flashed it to a 4.4.2 firmware. The problem only exists with stock firmware and stock rooted ROMs, not custom ROMs like CyanogenMod.
An update..
So I encrypted my device using the Carbon-rom, and rebooted into recovery. I wiped my device, and installed the Stock(ish) ROM. I was able to boot into the device, without any kind of encryption screen.
I am going to try a fully stock rooted 4.4.2 app and update this post.
backdown said:
So I encrypted my device using the Carbon-rom, and rebooted into recovery. I wiped my device, and installed the Stock(ish) ROM. I was able to boot into the device, without any kind of encryption screen.
I am going to try a fully stock rooted 4.4.2 app and update this post.
Click to expand...
Click to collapse
Definitely let us know how this plays out.
Like the other guy said though this certainly highlights the reason a lot of people are scared to encrypt. their phones. I hope you get it going again!
Sent from my SCH-I545 using Tapatalk
I was able to encrypt my phone while running carbon. Upon completion, I rebooted into recovery and wiped to install a new ROM. I installed the stock(ish) ROM running 4.3. I then updated my profile and the device activated. Everything works as it should.
I tried installing a stock rooted NAE ROM and it installed fine. The handset was taking ages to update though. I flashed the NAE modem, but that doesn't work either. All in all I'm still happy.
edit/
I have updated the original post with more information about what I did. If anyone faces this problem, let me know and I will try to help you the best I can.
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.
My Nexus 4 had been running Cyanogenmod (cm-12.1-20151007-SNAPSHOT-YOG4PAO334-mako) correctly for months. Two days ago, the screen failed to auto-rotate when I tilted the phone so I decided to reboot and see if that worked. Not only did it not work, the device went into a bootloop. It would boot, ask for my encryption password, accept the password but the OS would never start (I waited over 2 hours).
I'm able to use adb, fastboot, and access TWRP.
I tried reflashing CM12 to no avail. I've also tried going back to stock by reformatting all partitions in fastboot and flashing stock bootloader, radio, and system image (also in fastboot). That's where I'm at right now. I have everything stock except for the recovery partition where I have TWRP.
Here's the TWRP log: http://pastebin.com/MCKD73G0
Here's the dmesg log: http://pastebin.com/BdVjV2vz
Here's the last kernel message log: http://pastebin.com/DBQQBFQv
Any ideas?
I have a very strong hunch that this problem has got something to do with the sensors.
I flashed Android 4.2.2 and, to my surprise, the phone booted correctly into Android. No other ROM (stock or otherwise) would boot correctly. As I mentioned in the OP, screen auto-rotation isn't working so I downloaded an app to test other sensors. The proximity sensor, pressure sensor, light sensor, and the gyroscope don't work. I strongly doubt this is a software issue but I'm not ruling it out yet. I will try to open the phone case later tonight and move the sensor around, it might be stuck.
Just had a pro take a look at my phone. He said there's nothing wrong with the sensors so it must be a software problem. I've been trying to fix this for days now.
Any ideas would be greatly appreciated.
I just noticed that my phone does not have the /sys/class/sensors/ or /sys/devices/virtual/sensors/ folders, is this normal? If not, how can I solve this?
Feareilo said:
I just noticed that my phone does not have the /sys/class/sensors/ or /sys/devices/virtual/sensors/ folders, is this normal? If not, how can I solve this?
Click to expand...
Click to collapse
I had this issue twice.. flashing an old version of Frank ROM (in L preview times).. all my sensors got screwed... and trying to flash other roms or factory resetting the phone didn't work!
So I downloaded latest factory image and flashed it with the flashall.bat script
Voilà! All the sensors started to work again!! And they still work! So... some very deep part of the system can be wiped only by the stock recovery factory reset.. I don't know why though.. but that's it!
bart.found said:
I had this issue twice.. flashing an old version of Frank ROM (in L preview times).. all my sensors got screwed... and trying to flash other roms or factory resetting the phone didn't work!
So I downloaded latest factory image and flashed it with the flashall.bat script
Voilà! All the sensors started to work again!! And they still work! So... some very deep part of the system can be wiped only by the stock recovery factory reset.. I don't know why though.. but that's it!
Click to expand...
Click to collapse
Thanks for your input. Unfortunately, that didn't work. Flashing stock ROMs didn't work and neither did doing the factory reset.
Feareilo said:
Thanks for your input. Unfortunately, that didn't work. Flashing stock ROMs didn't work and neither did doing the factory reset.
Click to expand...
Click to collapse
Sad to hear that... did you already factory reset from the stock recovery?
bart.found said:
Sad to hear that... did you already factory reset from the stock recovery?
Click to expand...
Click to collapse
Yeah