Hi Forum,
I was running Indie ROM 4.3, v19. I did the 3 wipes and installed Indie ROM, v20. After installation,
I got this message( "UIDs on the system are inconsistent, you need to wipe your data partition or your device will be unstable."
with a button that stays "I'm Feeling Lucky).
I research XDA , some stated to reflash the ROM using TWRP, and then fix permission. I am using Phil Touch CWM, which has fix permission. However, I still get the same message.
The phone is usable, but certain Google app wont install.
Anyone has an idea how to fix this? Would flashing a ROM from another Dev fix this problem?
Thank you for looking, and then some.... for your helpful suggestion.
OK, I got tired to flashing. Used TWRP to repartition the whole drive. This fixed all the issue.
I solved the problem. I install TWRP, wipes and fix permission. However, TWRP reported that fix permission has failed. I let the phone reboot. ROM start up with out problem. Guess I will be using TWRP from now on.
I spoke to soon. I was not able to install many of Google apps. Reinstall ROM again and now getting the the same message ...UID..
Anyone have any idea?
What does this mean - it's solved, but it ends with a question?
Okay. So I use philz 6.26.6 and never had an issue. I've had UID issue before, but only when dirty flashing roms. A factory reset (in the settings menu) always resolved it.
Probably the cleanest solution HERE
Related
my galaxy grand continue to reboot, i even flash the stock 4.1.2 and 4.2.2 firmware but still the phone reboots, it only reaches the wifi setup, then it restarts, please help.
chrowley said:
my galaxy grand continue to reboot, i even flash the stock 4.1.2 and 4.2.2 firmware but still the phone reboots, it only reaches the wifi setup, then it restarts, please help.
Click to expand...
Click to collapse
The information provided by you is not sufficient.There are some points i would like to know about.
Have u rooted your device?
Are you flashing through ODIN?
ROM version?
Did you make data wipe/ cache wipe before flashing over a previous firmware?
There are many threads associated with this.So please take a look over that.If you don't find answer then we are here to help you
ashwin77sgg said:
The information provided by you is not sufficient.There are some points i would like to know about.
Have u rooted your device?
Are you flashing through ODIN?
ROM version?
Did you make data wipe/ cache wipe before flashing over a previous firmware?
There are many threads associated with this.So please take a look over that.If you don't find answer then we are here to help you
Click to expand...
Click to collapse
yes sir rooted, i flash the firmware through odin, then i figured out that i have a backup so i restore it and its a yes it starts, , but the problem is sometimes it reboots and the screen is blinking sometimes, any solution for this sir? thanks in advance
chrowley said:
yes sir rooted, i flash the firmware through odin, then i figured out that i have a backup so i restore it and its a yes it starts, , but the problem is sometimes it reboots and the screen is blinking sometimes, any solution for this sir? thanks in advance
Click to expand...
Click to collapse
Thanks for Calling me "Sir". But seriously no need to say it. Say it to real developers.
Now coming to the topic,
For your information,keep in mind that when u flash the Official firmware through ODIN, You loose the root access.
Don't restore any backup. Just flash through ODIN. After flashing Wipe Cache and Data wipe is recommended too.
To gain the root access again you need to flash recovery from ODIN.
Other members looking at this this thread please correct me if i am wrong .I still not getting which backup the guy is talking about.
ashwin77sgg said:
Thanks for Calling me "Sir". But seriously no need to say it. Say it to real developers.
Now coming to the topic,
For your information,keep in mind that when u flash the Official firmware through ODIN, You loose the root access.
Don't restore any backup. Just flash through ODIN. After flashing Wipe Cache and Data wipe is recommended too.
To gain the root access again you need to flash recovery from ODIN.
Other members looking at this this thread please correct me if i am wrong .I still not getting which backup the guy is talking about.
Click to expand...
Click to collapse
oh sorry sir, i'll make it clear, my last firmware is 4.2.2 and my rom is GENNEXT, but when i encounter the problem, i tried to go back and flash the 4.1.2 stock firmware, then later i discovered that i have a backup from my previous rom(GENNEXT running 4.2.2 firmware) so i flash again the 4.2.2 stock firmware and flash the philz touch recovery, wipe data/factory reset, wipe cache and wipe dalvik cache then restore the back up, then my phone is restored but theres another problem sometimes the screen blinks and the phone reboots in a few minutes after the startup.
chrowley said:
oh sorry sir, i'll make it clear, my last firmware is 4.2.2 and my rom is GENNEXT, but when i encounter the problem, i tried to go back and flash the 4.1.2 stock firmware, then later i discovered that i have a backup from my previous rom(GENNEXT running 4.2.2 firmware) so i flash again the 4.2.2 stock firmware and flash the philz touch recovery, wipe data/factory reset, wipe cache and wipe dalvik cache then restore the back up, then my phone is restored but theres another problem sometimes the screen blinks and the phone reboots in a few minutes after the startup.
Click to expand...
Click to collapse
OK. Then it may be the problem with your GENNXT ROM cause the problem occured after restoring Backup.Try the fresh install of latest build of GENNXT rom.
ashwin77sgg said:
OK. Then it may be the problem with your GENNXT ROM cause the problem occured after restoring Backup.Try the fresh install of latest build of GENNXT rom.
Click to expand...
Click to collapse
i already tried it sir but it didnt solve the problem, it passes the setup but after a few minutes the phone reboots.
You might want to try one of the AOSP-based ROMs (CM11/Slimkat/Carbon/Omni/ProBAM) and see if it fixes the issue. If it still reboots even after installing one of those ROMs, then you probably has a faulty hardware. If it stops rebooting,then you probably has a corrupted installation of stock firmware...
Faulty hardware = get it to a service center, but be prepared to pay some bucks because you have already lost your warranty...
Corrupted stock firmware = try to flash the firmware again via Odin but DON'T RESTORE ANY BACKUP. If it still reboots, redownload the firmware package and reflash.
I'm not an expert, but I figured that your phone is already unusable by constant rebooting... let's just solve it by trial and error.
naufalhadyan said:
You might want to try one of the AOSP-based ROMs (CM11/Slimkat/Carbon/Omni/ProBAM) and see if it fixes the issue. If it still reboots even after installing one of those ROMs, then you probably has a faulty hardware. If it stops rebooting,then you probably has a corrupted installation of stock firmware...
Faulty hardware = get it to a service center, but be prepared to pay some bucks because you have already lost your warranty...
Corrupted stock firmware = try to flash the firmware again via Odin but DON'T RESTORE ANY BACKUP. If it still reboots, redownload the firmware package and reflash.
I'm not an expert, but I figured that your phone is already unusable by constant rebooting... let's just solve it by trial and error.
Click to expand...
Click to collapse
This is probably the best explained and most direct definition of what to do and what may be happening with our ever-rebooting Grands.... Thank you!!!
Had to create an account to thanks naufalhadyan
I was running on LineAgeOS 13.0 for a while until yesterday, when I went to install some random play store app and it crashed then went on a infinite rollercoaster with absolutely no fun making loops every time it got of the boot animation, did a factory reset, on the 2nd or 3rd app it crashed and looped, flashed another .zip with the rom, same, installed an RRemix on the same version (I like the 6) and when installing another random playstore it crashed the same way, now i'm on a AOSP 6.0 flashed from the recovery and so far i've been downloading the entire play store (just for kicks) and its smooth.
I don't use come to this troubleshooting section but on the last 24 hours there were some major bugs regarding endless loops, maybe a play store update came bugging our grand duos'? Is that even possible?
victorsmarotta said:
Had to create an account to thanks naufalhadyan
I was running on LineAgeOS 13.0 for a while until yesterday, when I went to install some random play store app and it crashed then went on a infinite rollercoaster with absolutely no fun making loops every time it got of the boot animation, did a factory reset, on the 2nd or 3rd app it crashed and looped, flashed another .zip with the rom, same, installed an RRemix on the same version (I like the 6) and when installing another random playstore it crashed the same way, now i'm on a AOSP 6.0 flashed from the recovery and so far i've been downloading the entire play store (just for kicks) and its smooth.
I don't use come to this troubleshooting section but on the last 24 hours there were some major bugs regarding endless loops, maybe a play store update came bugging our grand duos'? Is that even possible?
Click to expand...
Click to collapse
Even iam facing the same issue
phone reboots automatically and doesnt even start... infinite bootloop. Was working fine and suddenly this issue came up from nowhere(past 2 weeks) ..
Iam using Resurrection rom 5.7.4 (Marshmallow)
Damn I was on AICP 11, when this exact strange bootloop problem occurred for no rhyme and reason. I know the hardware is fine, the issue arises from installing apps from playstore, the moment it goes beyond a certain app limit in the device, it will start endless bootloop, I am sure this is Google's doing. Anyways this is not a hardware issue and I know more people will be coming here looking for answer to this issue. I have tried both the opengapps and deltagapps, same behaved this way, it never happened before and lately google have introduced one other app which is google's android instant app that will sit in your device, even though you need it not not. very well google for using our precious internal data to around 500Mb to 1Gb.
formating data partition solves this issue, temporarily but you lose your apps and data.
I had successfully avoided this issue when I stopped installing more apps on my device, It took me 2 tries and I found a perfect balance of 4-5 apps, it came crashing again when I tried installing the 7th app.
I don't know if other ROMs will be able to handle this bug, but I know it's time for me to look for another ROM, I was happy with AICP 11, for more than a year. Sad.
Reading about this issue, I came to know this is prevalent on all CM marshmallow based ROMs. So, going to flash Nougat or kitkat or the stock ROM should probably fix this.
Try a new battery.
Hey, so I have a rooted stock Jellybean (4.3 I believe? the last Jellybean before KitKit).
I have CWM Recovery 6.0.1.9.
I'm a complete n00b but have been surviving with this for a while now but just today I did a casual update of some apps the last being SuperSU. It updated binaries then asked to reboot. I rebooted and it asked if I wanted to fix permissions or something, which it's done before. In the past whether I hit yes or no, it boots up normally. I think I hit yes this time? Not sure, but either way, I keep boot looping into my recovery and can't boot up normally.
What can I do now? I NEED MY PHONE FOR WORK! I had no idea this would happen (as with most problems).
Would flashing a different recovery work? Or what about flashing SU through adb, if that's possible? If so, where do I get the latest apk on my computer? I really only know flashing and adb and stuff as far as technical things go. If it'll take more, I'd really appreciate a Skype talk to something.
EDIT: I can't even get my computer to recognize my phone, so that I could try installing the zip of the latest SuperSU.
I read somewhere that I can reinstall my same ROM and I will not lose anything, is this true? If so, I still have that zip on my sdcard. Should I just reinstall the ROM and will that work? Seems to be the only option I can see atm.
EDIT 2: So in my desperation I reinstalled the same ROM I have on my sdcard. This got me back to my phone. Now it said SuperSU needs to be updated, I did it, it said it needs to reboot, I said OK... then back at the same issue.
So what now? Am I getting a faulty update of SuperSU? How can I fix this?
EDIT 3: So it seems to be an issue with SuperSU's update today. I basically reinstalled my ROM and am using my phone. But I can't reboot or turn it off or I'm stuck all over again, unless I install my ROM AGAIN from sdcard. Really annoying. I'm hoping Chainfire fixes the issue and hopefully this fixes the reboot problem. Is it possible that SuperSU cause this issue?
I'm writing because I found no solution to this or someone to address this. are there not many having this problem?
After 7.0 update my alarm is not ringing and if I go in the settings to change the alarm sound the app fc, also the YouTube app says "something went wrong" when trying to play a video.
After restart the sound is back for some time, then bug repeats.
I activated touch sound so I get a warning when I need to reboot, but the touch sound is not affected, also the music app is working, but no alarm or notification.
Whipped cash, installed Oos 4.0.3 via recovery (stock, locked bl, no root)
Currently on 7.1.1 Oos 4.1.3
Someone please help
Starting to think that I will have to sent the phone back to OnePlus...
get the full 4.1.3 zip, and on stock recovery wipe everything not just cache...
then back to the main menu on recovery and select install via USB (or something liket hat) and sideload the full rom from computer , after sideload boot to system and for good measures do a factory reset.
theduke7 said:
get the full 4.1.3 zip, and on stock recovery wipe everything not just cache...
then back to the main menu on recovery and select install via USB (or something liket hat) and sideload the full rom from computer , after sideload boot to system and for good measures do a factory reset.
Click to expand...
Click to collapse
Thanks for the reply ! - I will try your suggestion tomorrow if I get the time -
Maybe it's a stupid question but: is there ever a need to wipe internal storage? or wipe everything means just system data ?
plus: could the encryption mess things around ?
marius88cc said:
Thanks for the reply ! - I will try your suggestion tomorrow if I get the time -
Maybe it's a stupid question but: is there ever a need to wipe internal storage? or wipe everything means just system data ?
plus: could the encryption mess things around ?
Click to expand...
Click to collapse
Encryption may cause issues, but I don't think your problem is related to that, something in the update process went wrong I think so you got something corrupted on the either the system.or data partition , so Everytime you install a new ROM it does but the issue stays, the only way to know for sure is a clean install, and the easiest way to that is what I told you, it can also be done by fastboot where you wipe everything with fastboot then sideload , but to be safe better stick with the recovery method... I don't thing internal storage could cause an issue, but I personally from 7.0 to 7.1.1 I did wipe it , better safe than sorry, and it elemenates any possibilities so if you can do that it's better
theduke7 said:
Encryption may cause issues, but I don't think your problem is related to that, something in the update process went wrong I think so you got something corrupted on the either the system.or data partition , so Everytime you install a new ROM it does but the issue stays, the only way to know for sure is a clean install, and the easiest way to that is what I told you, it can also be done by fastboot where you wipe everything with fastboot then sideload , but to be safe better stick with the recovery method... I don't thing internal storage could cause an issue, but I personally from 7.0 to 7.1.1 I did wipe it , better safe than sorry, and it elemenates any possibilities so if you can do that it's better
Click to expand...
Click to collapse
Thank you for the reply!
Weirdest thing, I did not get the chance to reinstall the system yet, but since I posted this the bug did not reaper. I suspect an app was misbehaving and it got updated...I will wait and see.
Just sideloaded, will report how it goes if anyone faces the same problem
New OTA Out, should solve this, it seems
So i had a official rom installed but wanted to try something different. I started with "Pixel Experience Rom" but i immediately faced the issue with decryption unsuccessful and found out that i have to change the data partition to EXT4 and i did that. Then i proceed to install the rom all went well, i did root the rom with magisk and add all my usual apps. Then i had to do a restart and this was the issue when i restarted the rom i faces the same Issue with the same " Decryption Unsuccessful " error i tried to get the partition back to normal and then change it to EXT4 but nothing worked, so i did fasboot install of the original rom. Then i decided this could be a rom issue and then i proceed to install different oreo rom, i again changed the partition to EXT4 and installed Cardinal Oreo rom, everything was great again i did root the phone install all my apps. Then i had to restart the phone and again i faced the exact same issue "Decryption Unsuccessful" error i checked to see if my partition is at EXT4 and it is still i keep on getting this issue. Anyone know what might cause this issue ? I have no problem doing the new install and all but at some point i will need to restart and i will surely get the same issue until i found out what is the cause of it. I have TWRP custom recovery the latest version, i have root the phone with magisc .... please if anyone know the reason help!
Maybe Magisk could be the issue?
Pretty Sure it Magisk didn't have anything to do with that error. There were some others that had the same error with Pixel Experience.
Look at my detailed comment on another thread: https://forum.xda-developers.com/lenovo-p2/help/incredible-story-encrypt-phone-t3799057
You can skip the steps that you already know, but just try and follow those i mentioned. And then flash your Oreo Rom.
I can pretty much assume that that is a fail-safe mini guide.
If i'm wrong, correct me and give more details so that we can help you.
The issue was caused of magisk. Apperently when you install an oreo rom you have to plash the rom, then GApps and then magisk then restart the device. It should not have restarts in between. After doing this right I haven't had any problems. I hope this helps someone
....
Hello, guys. I just ran into an error I had never seen before while flashing a new firmware on my T320. After searching around, I found more people have reported it as well on many devices and I've tried most solutions, to no avail.
When installing a zip for a lineage 16 rom, I got an error 7 message, which implies a mismatch between the rom and the device being flashed. I'm sure they should be a match, so I proceeded with the most common solution (when you know it's a match), which is to remove the device-checking code from within the zip. That didn't work, I got a "invalid zip file format" error.
I haven't tried many different roms after this in order to exclude the possibility this being actually a incompatibility issue but I'm worried because, when first flashing, I wiped the device quite carelessly. I'm afraid I might have "over-wiped" something important. I have TWRP installed, version 3.1.1.0, and did the wiping using it's built in tools.
Is there something I should never wipe, risking breaking it beyond repair? Is there a special procedure to perform or option to choose when zipping the rom back after removing the device-checking code?
Thanks for any advice,
Horácio.
horaciosalles said:
Hello, guys. I just ran into an error I had never seen before while flashing a new firmware on my T320. After searching around, I found more people have reported it as well on many devices and I've tried most solutions, to no avail.
When installing a zip for a lineage 16 rom, I got an error 7 message, which implies a mismatch between the rom and the device being flashed. I'm sure they should be a match, so I proceeded with the most common solution (when you know it's a match), which is to remove the device-checking code from within the zip. That didn't work, I got a "invalid zip file format" error.
I haven't tried many different roms after this in order to exclude the possibility this being actually a incompatibility issue but I'm worried because, when first flashing, I wiped the device quite carelessly. I'm afraid I might have "over-wiped" something important. I have TWRP installed, version 3.1.1.0, and did the wiping using it's built in tools.
Is there something I should never wipe, risking breaking it beyond repair? Is there a special procedure to perform or option to choose when zipping the rom back after removing the device-checking code?
Thanks for any advice,
Horácio.
Click to expand...
Click to collapse
A Slimroms file just made it through, so it's not destroyed, it's a matter of compatibility, somehow.
update the TWRP to 3.3.1.0
I have the same problem with T320 and was using TWRP 3.3.1.0, lineage-16.0-20191211-UNOFFICIAL-mondrianwifi.zip . I was able to install RR-N-v5.8.10-20190128-mondrianwifi-Unofficial.zip.
Any idea why?
Thanks
thro14 said:
I have the same problem with T320 and was using TWRP 3.3.1.0, lineage-16.0-20191211-UNOFFICIAL-mondrianwifi.zip . I was able to install RR-N-v5.8.10-20190128-mondrianwifi-Unofficial.zip.
Any idea why?
Thanks[/Q]
I got it working now. I downloaded 16.0 again. In TWRP- Factory reset, Advance wipe-chose Dalvick, Data, System & Cache.
This time I did not "Format Data". Not sure which did it (download or not format data).. Hope it helps.
Click to expand...
Click to collapse
having this same problem says "this package is for mandrainwifi , this device is . "
Trevorlay said:
having this same problem says "this package is for mandrainwifi , this device is . "
Click to expand...
Click to collapse
Make sure you have the latest twrp. If it still doesn't work, you could try messing with wiping/not wiping.