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!
Related
As the title says, I'm getting notifications to upgrade my Nexus 7 to 4.2 even though I have 4.2 already. If it were the 4.2.1 update that it wanted me to update to, wound't it say 4.2.1 instead of 4.2?
Info on the device:
Rooted
Bootloader Unlocked
Stock ROM
I went ahead and tried installing the update many times and while it shutdown to do its dirty work, it eventually error-ed out (while the little Android guy is on his back). I have even done a factory reset and I still get the prompts to update to 4.2... from 4.2. Errors are there as well. Thank you for your help.
John J
P.S There are pics
jjimenezjj said:
As the title says, I'm getting notifications to upgrade my Nexus 7 to 4.2 even though I have 4.2 already. If it were the 4.2.1 update that it wanted me to update to, wound't it say 4.2.1 instead of 4.2?
Info on the device:
Rooted
Bootloader Unlocked
Stock ROM
I went ahead and tried installing the update many times and while it shutdown to do its dirty work, it eventually error-ed out (while the little Android guy is on his back). I have even done a factory reset and I still get the prompts to update to 4.2... from 4.2. Errors are there as well. Thank you for your help.
John J
P.S There are pics
Click to expand...
Click to collapse
This has been posted about before.
Yes, the 4.2.1 upgrade says "4.2" in the update screen. Your device is trying to go from 4.2->4.2.1.
The upgrade however seems to be failing. Since you are using a stock recovery, there is no indication on what part is stopping it. It could just be a glitch or, more likely, you modified something. Did you install any mods or root and modify any system apps? Freezing them in TiBu/etc. will break it too.
phonic said:
This has been posted about before.
Yes, the 4.2.1 upgrade says "4.2" in the update screen. Your device is trying to go from 4.2->4.2.1.
The upgrade however seems to be failing. Since you are using a stock recovery, there is no indication on what part is stopping it. It could just be a glitch or, more likely, you modified something. Did you install any mods or root and modify any system apps? Freezing them in TiBu/etc. will break it too.
Click to expand...
Click to collapse
I did read other posts but they didn't seem to help.
After I rooted the device, I went ahead and pasted the original browser.apk in the System/App folder and installed it from there. From what I read, that was most likely my problem. I deleted it but still got the error. After that I said "screw this" and applied a data factory reset thinking that would solve my problems
Thank you for your reply.
John J
jjimenezjj said:
I did read other posts but they didn't seem to help.
After I rooted the device, I went ahead and pasted the original browser.apk in the System/App folder and installed it from there. From what I read, that was most likely my problem. I deleted it but still got the error. After that I said "screw this" and applied a data factory reset thinking that would solve my problems
Thank you for your reply.
John J
Click to expand...
Click to collapse
Yes, that modification would certainly break the OTA update.
Doing a factory wipe won't help. That won't revert the old system apk back to stock. Nor will deleting it.
Your best bet is to download the full 4.2.1 image and flash that. Or, you could find and restore the original browser.apk.
This should serve as another reminder to people who make tweaks - always backup the original file!
phonic said:
Yes, that modification would certainly break the OTA update.
Doing a factory wipe won't help. That won't revert the old system apk back to stock. Nor will deleting it.
Your best bet is to download the full 4.2.1 image and flash that. Or, you could find and restore the original browser.apk.
This should serve as another reminder to people who make tweaks - always backup the original file!
Click to expand...
Click to collapse
It's not that bad. Everything works fine except for updating the thing. As for the restoring the original browser.apk, if you mean Chrome, I never touched it so it is there.
My guess is that I didn't install the CWM Recovery correctly because I can't boot into Recovery Mode. It just hangs and stays in a loop. I will re-install CWM and see if that helps.
John J
Re-installed CWM Recovery and flashed 4.2.1 from there. Lost everything but I had anything important backup already. All is good
Well, my first venture into rom flashing hasn't been the most successful one as it's caused a really strange issue that a couple people on another thread have tried to help me solve, but I figure I had hijacked that thread long enough so this issue deserved it's own thread.
I rooted, unlocked bootloader, and installed TWRP v2.4.0.0 on Stock Android 4.1.1. Everything worked great. Until I flashed a rom. Now, I have been through wiping Cache, Dalvik Cache, Factory Reset, Flashing the rom (I've tried 4 with the same exact issue), flashing Gapps... All seems to go well and it says "success" when I flash, and I reboot into system. Run the setup of Google. Everything seems great and working fine. Here's where the problem is. When Google Play Store starts downloading for restore, and I'm on a solid wifi connection, nothing downloads. I have also tried stopping the downloads and installing apps individually. When I do that, I receive the same error message over and over for any app:
Unknown error code during application install: "-24"
I've rebooted, wiped cache, dalvik cache. Nothing installs. Same error. I did somehow, some way, get Titanium backup to install after numerous tries... when I try to restore any of that backup it just hangs on the first app. It does not restore anything. No batch apps. No single apps. No app data.
The odd thing is, the first time I flashed a rom, it seemed to load up fine. Stupidly, when I was running Titanium Backup for a restore I was not paying attention to what I was restoring. I was restoring all apps and app data... It caused an issue and a bunch of force closes, as you can probably imagine. So I rebooted into recovery and wiped and reinstalled rom and gapps. And virtually nothing has installed since. I have wiped and reinstalled AOKP, PACman, Carbon, and CM to no avail. Nothing seems to solve my issue. I'd love to at the very least be able to regularly install apps from the Play Store. At this point I'm not even concerned with restoring app data if that's too much to ask. I just want to be able to use my phone normally again as this is my "daily driver". If I have to go back to 4.1.1, that would be fine with me. I just want to get back to normal. And I'll do whatever it takes to get there. Any help at all would be appreciated.
Here is the original thread that some people have been giving me great advice on as to what to do, but none of it has fixed the issue yet unfortunately:
http://forum.xda-developers.com/showthread.php?t=2341470
Jersey846 said:
Well, my first venture into rom flashing hasn't been the most successful one as it's caused a really strange issue that a couple people on another thread have tried to help me solve, but I figure I had hijacked that thread long enough so this issue deserved it's own thread.
I rooted, unlocked bootloader, and installed TWRP v2.4.0.0 on Stock Android 4.1.1. Everything worked great. Until I flashed a rom. Now, I have been through wiping Cache, Dalvik Cache, Factory Reset, Flashing the rom (I've tried 4 with the same exact issue), flashing Gapps... All seems to go well and it says "success" when I flash, and I reboot into system. Run the setup of Google. Everything seems great and working fine. Here's where the problem is. When Google Play Store starts downloading for restore, and I'm on a solid wifi connection, nothing downloads. I have also tried stopping the downloads and installing apps individually. When I do that, I receive the same error message over and over for any app:
Unknown error code during application install: "-24"
I've rebooted, wiped cache, dalvik cache. Nothing installs. Same error. I did somehow, some way, get Titanium backup to install after numerous tries... when I try to restore any of that backup it just hangs on the first app. It does not restore anything. No batch apps. No single apps. No app data.
The odd thing is, the first time I flashed a rom, it seemed to load up fine. Stupidly, when I was running Titanium Backup for a restore I was not paying attention to what I was restoring. I was restoring all apps and app data... It caused an issue and a bunch of force closes, as you can probably imagine. So I rebooted into recovery and wiped and reinstalled rom and gapps. And virtually nothing has installed since. I have wiped and reinstalled AOKP, PACman, Carbon, and CM to no avail. Nothing seems to solve my issue. I'd love to at the very least be able to regularly install apps from the Play Store. At this point I'm not even concerned with restoring app data if that's too much to ask. I just want to be able to use my phone normally again as this is my "daily driver". If I have to go back to 4.1.1, that would be fine with me. I just want to get back to normal. And I'll do whatever it takes to get there. Any help at all would be appreciated.
Here is the original thread that some people have been giving me great advice on as to what to do, but none of it has fixed the issue yet unfortunately:
http://forum.xda-developers.com/showthread.php?t=2341470
Click to expand...
Click to collapse
2 suggestions:
1) i think others have reported having issues with TWRP 2.4, so try 2.5 or 2.3.2.3
2) I think the error could be a lack of internal storage, so certainly try the "wipe internal storage" in TWRP (after making sure that your ROM/GApp files, backups (including Tibu) are saved to your external folder
jco23 said:
2 suggestions:
1) i think others have reported having issues with TWRP 2.4, so try 2.5 or 2.3.2.3
2) I think the error could be a lack of internal storage, so certainly try the "wipe internal storage" in TWRP (after making sure that your ROM/GApp files, backups (including Tibu) are saved to your external folder
Click to expand...
Click to collapse
Ok giving this a shot. I did notice that you had mentioned a different version of TWRP than I had. I will try the wiping internal storage before I install a different TWRP then if that doesn't work, TWRP. Gotta find the external folder. Unless you just mean anything that is on the actual SD card.
Jersey846 said:
Ok giving this a shot. I did notice that you had mentioned a different version of TWRP than I had. I will try the wiping internal storage before I install a different TWRP then if that doesn't work, TWRP. Gotta find the external folder. Unless you just mean anything that is on the actual SD card.
Click to expand...
Click to collapse
i would actually recommend installing TWRP 2.5 first.
never wipe external SD card.
if you have an app called Root Explorer, that works best.
jco23 said:
i would actually recommend installing TWRP 2.5 first.
never wipe external SD card.
if you have an app called Root Explorer, that works best.
Click to expand...
Click to collapse
Ok I'll try 2.5 then. And I wasn't gonna wipe the card, just was wondering if when you said external folder you were talking about the SD card. Root explorer works great.. if i could install it.
EDIT: Since I am away from my computer, I tried the multiple wipe method. Didn't change anything. So I will be changing TWRP versions later and will post an update.
Jersey846 said:
Ok I'll try 2.5 then. And I wasn't gonna wipe the card, just was wondering if when you said external folder you were talking about the SD card. Root explorer works great.. if i could install it.
EDIT: Since I am away from my computer, I tried the multiple wipe method. Didn't change anything. So I will be changing TWRP versions later and will post an update.
Click to expand...
Click to collapse
You never mentioned using TWRP 2.4. DEFINITELY replace that. Also, just a thought. If you haven't already done so, try using the option to fix permissions. I'm fairly sure its an option in TWRP.
Sent from my XT907 using xda premium
Back in business! Wow thank you all so much! What a pain it's been but without the help I'd have never guessed how to get this running as perfectly as it is now. Here's what worked for me:
Installed TWRP 2.5 (Instead of what I had, 2.4)
Then followed jco23's precise directions:
jco23 said:
- I use TWRP 2.3.2.3 (SS has been uninstalled via it's own app, not Tibu or the system awhile ago) - but TWRP 2.5 works just fine for others
- after downloading the ROM and GApps (or any file that I intended to flash for that matter), I always place the file on the mnt/external1 directory. I
m not sure if this will make a difference, but I recall it being an issue back on my Droid Charge days
- after flashing the files, does TWRP say successful?
- perhaps you do need to a double wipe of everything prior to flashing:
1) mount everything
2) wipe cache
3) wipe dalvik cache
4) wipe system
5) factory reset/wipe data
6) wipe internal storage (if you do this, make sure to change your TiBu backup folder to your external1 directory, or this will be gone too!!!!! also make sure that the system backup you made is on the external1 directory as well
7) reboot recovery
8) install ROM
9) install GApps
Click to expand...
Click to collapse
And it's working flawlessly. Able to download or restore anything from Gapps. Was able to restore some specific app data from Titanium Backup (did not want to ruin the phone again and do that full restore so I selected specific apps that I really wanted the data on).
Thanks to everyone who took the time to assist me and a special thanks to jco23 and netizenmt who were with me through this whole debacle, leading me through every possible fix they could think of. As for those of you that may be wondering which ROM I settled on... AOKP.
Good for you bro! That stinking TWRP 2.4.0 is such a menace! Wish there was a way to have it yanked from circulation. Glad you're up and running!
Sent from my Droid Razr M using xda premium
Jersey846 said:
Back in business! Wow thank you all so much! What a pain it's been but without the help I'd have never guessed how to get this running as perfectly as it is now. Here's what worked for me:
Installed TWRP 2.5 (Instead of what I had, 2.4)
Then followed jco23's precise directions:
And it's working flawlessly. Able to download or restore anything from Gapps. Was able to restore some specific app data from Titanium Backup (did not want to ruin the phone again and do that full restore so I selected specific apps that I really wanted the data on).
Thanks to everyone who took the time to assist me and a special thanks to jco23 and netizenmt who were with me through this whole debacle, leading me through every possible fix they could think of. As for those of you that may be wondering which ROM I settled on... AOKP.
Click to expand...
Click to collapse
glad you finally got it working - this is just the first step in becoming a crack-flasher....
jco23 said:
glad you finally got it working - this is just the first step in becoming a crack-flasher....
Click to expand...
Click to collapse
Yeah, I've got it bad. I have had CM 10.1, Slimbean, Carbon AND AOKP on my phone all in the last 2 days. Carbon is on it right now. No telling what will be on it by tonight.
Sent from my XT907 using xda premium
netizenmt said:
Yeah, I've got it bad. I have had CM 10.1, Slimbean, Carbon AND AOKP on my phone all in the last 2 days. Carbon is on it right now. No telling what will be on it by tonight.
Sent from my XT907 using xda premium
Click to expand...
Click to collapse
funny, and the goal is to find a ROM that you're happy with and don't need to flash.
but I've been on Carbon since 7/5, and very happy.
Hi everyone! I recently decided to install the 4.4.2 rom on my Galaxy Note 3 N9005 and I didn't like it because it obviously was buggy as ,entioned in the thread. So I wanted to go back to my nandroid backup which I had made before installing the rom. It all went right in CWM and no errors, so I rebooted my phone and got stuck at the glowing samsung logo, so after many fixes and things I tried which didn't work I flashed a pre-rooted stock rom for it and it all went well. I managed to restore to my nandroid finally and then I unlock my phone to find a "com.google.process.gapps has been stopped" message which wont go away when I tap "OK". It just comes back and gives me one second untill it comes back again. I really need help since I need my phone for work, I have tried reinstalling all the gapps, wont work, I have tried reflashing the stock rom and restoring my nandroid again, I have tried deactivating "Downloads" in the app manager but that wont fix it either and finally I have tried clearing the "app data" for all my apps but again, no luck. If anyone would be able to help me I would appriciate it very much. Thanks in advance!
You're probably gonna have to go back to complete stock. Grab your stock image and flash via odin, boot it up and see if it gives you the error without installing custom recovery and your backup. That way you'll know where the error lays.
Sent from my SM-N9005 using XDA Premium 4 mobile app
radicalisto said:
You're probably gonna have to go back to complete stock. Grab your stock image and flash via odin, boot it up and see if it gives you the error without installing custom recovery and your backup. That way you'll know where the error lays.
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Forgot to mention but when I return to complete stock there isn't such a message, only when I restore to my nandroid. I also tried restoring from an older backup which I had made like 2 months ago and the same problem remains, "com.google" message is still there. Any suggestions or should I just start over?
mikey429 said:
Forgot to mention but when I return to complete stock there isn't such a message, only when I restore to my nandroid. I also tried restoring from an older backup which I had made like 2 months ago and the same problem remains, "com.google" message is still there. Any suggestions or should I just start over?
Click to expand...
Click to collapse
Sounds like a dodgy backup or it somehow got corrupted, I'd start over to save any headaches for future reference -- It's a headache I know, but safer I think. You could hang five, see if anyone else chimes in with any other ideas though
radicalisto said:
Sounds like a dodgy backup or it somehow got corrupted, I'd start over to save any headaches for future reference -- It's a headache I know, but safer I think. You could hang five, see if anyone else chimes in with any other ideas though
Click to expand...
Click to collapse
Yeah i'm probably gonna have to start over from scratch, thank you so much for te super fast reply, I appriciate your answer and help. As you suggested I will keep staying on this thread to see if anyone has the fix. If not i'm just gonna reflash this thing again.
And again, thank you so much for the fast reply I appriciate it alot.
mikey429 said:
Hi everyone! I recently decided to install the 4.4.2 rom on my Galaxy Note 3 N9005 and I didn't like it because it obviously was buggy as ,entioned in the thread. So I wanted to go back to my nandroid backup which I had made before installing the rom. ...
Click to expand...
Click to collapse
A nandroid backup is simple but monolithic. Most people also use Titanium Backup for the ability to restore selective stuff, or to restore to a completely different model of phone.
I had same issue
Bith titanium and nandroid restore.
Well only way to save your self. Completing wizard of first startup with feeling google..
And just restore user apps and data with titanium except google stuff..
This is the only healthy restore method so far i know that gapss.com keeps kool
Sent from my SM-N900 using xda app-developers app
So I somehow managed to go to settings and disable Play Services with the one second time line that I had before the message appears again, and the message stopped. So it must be something with Play Services. Since i'm new to android (and the Note 3 is my first android phone) I want to ask if there is a way to maybe reinstall Plaay Services?
mikey429 said:
Hi everyone! I recently decided to install the 4.4.2 rom on my Galaxy Note 3 N9005 and I didn't like it because it obviously was buggy as ,entioned in the thread. So I wanted to go back to my nandroid backup which I had made before installing the rom. It all went right in CWM and no errors, so I rebooted my phone and got stuck at the glowing samsung logo, so after many fixes and things I tried which didn't work I flashed a pre-rooted stock rom for it and it all went well. I managed to restore to my nandroid finally and then I unlock my phone to find a "com.google.process.gapps has been stopped" message which wont go away when I tap "OK". It just comes back and gives me one second untill it comes back again. I really need help since I need my phone for work, I have tried reinstalling all the gapps, wont work, I have tried reflashing the stock rom and restoring my nandroid again, I have tried deactivating "Downloads" in the app manager but that wont fix it either and finally I have tried clearing the "app data" for all my apps but again, no luck. If anyone would be able to help me I would appriciate it very much. Thanks in advance!
Click to expand...
Click to collapse
Hi, there! I just got almost the same issue like you. Once update to custom 4.4.2, any nandroid backups which worked right before getting GAPPS' FC constantly. :crying: Try double wipes, flash 4.3 gapps full package, stop&restart android download, uninstall google play store update, etc. nothing can fix it. Only way stop the popup error, is flash stock rom. But, consequently, lose root access, even with the same method that rooted the stock rom before. I'll heard some guy said the 4.4.2 has different partition from 4.3 or older android rom. But don't mention how to restore the old partition way. So, hope anyone can help us out, thanks a lot.
Hello,
I've had my SGS4 for a year and a half now, and rooted it with cf-auto-root through odin 3.07 3 months ago. I didn't flash custom firmwares though. i've had CWM recovery 6.0.xxx flashed and installed, made a nandroid backup using it (did it today before installing cerebrus, i'll explain later, and after tweaking the boot animation, i'll also explain later), and installed some (Above 25) root applications, from wich i'll have to cite: online nandroid backup, rom toolbox pro, rom installer... and many more i can't recall because of the incapability of accessing my phone right now :silly:
Today, i thought i can give him some little tweaks, to my s4 running 4.4.2 android version. i've gone to rom toolbox pro and used the replace animated boot or whatever it is called feature, that didn't work (probably because i have stock firmware), so i went to another app (excuse me for not remembering the name, but it may be rom installer) and downloaded the recommended "cerebrus" rom, that provides the ability to track my device, lock it, unlock it, and take pictures/recordings from their website (yes i know that this is risky), through CWM recovery. When i rebooted the device, 256 apps were updated, then, after entering the pin, "Cerebrus has stopped working". i then rebooted the device into recovery, from wich i restored my phone to a previous state (no i didn't wipe anything, from dalvik to data). Then came the endless boot... not knowing what to do, i became "flash happy"... kind of... i flashed the recovery many times, wiped data many times, wiped dalvik many times... nothing, same result. i finally wiped everything that can be deleted from the "advanced" menu in CWM... it softbricked my device... dunno how i did it, but i managed to enter odin mode and flashed the PIT file... it worked... only to recovery though, still can't get in... i then re-did the steps of wiping dalvik, data, cache, doing factory resets, reflashing PIT.... NOTHING. Of course, i was here all the time, searching for solutions... but nothing worked for me... So i had to create this thread on a problem that was resolved a thousand times, sorry. I hope that someone will be able to help me, or else, i'm off to the nearest samsung store...
I also have a request, if it's not a burden ofc, can i, after making my device work again, restore system and data from the backup or is it too risquy?
And Thank you for your support!
If you wiped /system then there is nothing to boot up. You basically deleted the android OS from your device.
I'd suggest finding the original stock rom for your device and flash it with Odin.
GDReaper said:
If you wiped /system then there is nothing to boot up. You basically deleted the android OS from your device.
I'd suggest finding the original stock rom for your device and flash it with Odin.
Click to expand...
Click to collapse
but i then restored it through the "advanced" menu of CWM (or doesn't it restore the OS?), from the nandroid backup.
Anyway, I'm downloading the OS right now but... it's gonna take a while: 1.5GB through 25kB/s internet is hard lol...
Thanks for your Advice!
Arz98 said:
Hello,
I've had my SGS4 for a year and a half now, and rooted it with cf-auto-root through odin 3.07 3 months ago. I didn't flash custom firmwares though. i've had CWM recovery 6.0.xxx flashed and installed, made a nandroid backup using it (did it today before installing cerebrus, i'll explain later, and after tweaking the boot animation, i'll also explain later), and installed some (Above 25) root applications, from wich i'll have to cite: online nandroid backup, rom toolbox pro, rom installer... and many more i can't recall because of the incapability of accessing my phone right now :silly:
Today, i thought i can give him some little tweaks, to my s4 running 4.4.2 android version. i've gone to rom toolbox pro and used the replace animated boot or whatever it is called feature, that didn't work (probably because i have stock firmware), so i went to another app (excuse me for not remembering the name, but it may be rom installer) and downloaded the recommended "cerebrus" rom, that provides the ability to track my device, lock it, unlock it, and take pictures/recordings from their website (yes i know that this is risky), through CWM recovery. When i rebooted the device, 256 apps were updated, then, after entering the pin, "Cerebrus has stopped working". i then rebooted the device into recovery, from wich i restored my phone to a previous state (no i didn't wipe anything, from dalvik to data). Then came the endless boot... not knowing what to do, i became "flash happy"... kind of... i flashed the recovery many times, wiped data many times, wiped dalvik many times... nothing, same result. i finally wiped everything that can be deleted from the "advanced" menu in CWM... it softbricked my device... dunno how i did it, but i managed to enter odin mode and flashed the PIT file... it worked... only to recovery though, still can't get in... i then re-did the steps of wiping dalvik, data, cache, doing factory resets, reflashing PIT.... NOTHING. Of course, i was here all the time, searching for solutions... but nothing worked for me... So i had to create this thread on a problem that was resolved a thousand times, sorry. I hope that someone will be able to help me, or else, i'm off to the nearest samsung store...
I also have a request, if it's not a burden ofc, can i, after making my device work again, restore system and data from the backup or is it too risquy?
And Thank you for your support!
Click to expand...
Click to collapse
Maybe read this first my friend
http://forum.xda-developers.com/showthread.php?t=2265477
Already read that in my desperate search
speedwayfan72 said:
Maybe read this first my friend
http://forum.xda-developers.com/showthread.php?t=2265477
Click to expand...
Click to collapse
Hi, Thank you for taking the time to help me with this issue!
i read that thread before, and was downloading the firmware through the night... but the download failed, now i don't have enough time to redownload it again, especially if it's gonna make errors.
bottom line, do you have any trusted torrent link for the firmware? it would be easier to do download since that it won't give me errors...
Thanks again!
Arz98 said:
Hi, Thank you for taking the time to help me with this issue!
i read that thread before, and was downloading the firmware through the night... but the download failed, now i don't have enough time to redownload it again, especially if it's gonna make errors.
bottom line, do you have any trusted torrent link for the firmware? it would be easier to do download since that it won't give me errors...
Thanks again!
Click to expand...
Click to collapse
Hi, I always donwload with JDownloader, and in this link explain how to enable resume for Sammobile. http://forum.xda-developers.com/showthread.php?t=2765456
Interface23 said:
Hi, I always donwload with JDownloader, and in this link explain how to enable resume for Sammobile. http://forum.xda-developers.com/showthread.php?t=2765456
Click to expand...
Click to collapse
Thank you for those tips! it will undoubtly help me in redownloading the firmware (undergoing right now)
Arz98 said:
Thank you for those tips! it will undoubtly help me in redownloading the firmware (undergoing right now)
Click to expand...
Click to collapse
Glad I have helped you.
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.