Hello,
On the last few days I've been facing a problem that I couldn't solve alone. As I understand, there are two different android 4.3 versions, JSS15J and JWR66V, if I understood right. I don't know what is the actual difference between them. I had the google factory image of 4.3 on my nexus 4 (that eventually I learned it's JWR66V) e flashed (through TWRP) the franco kernel (also JWR66V), but my data got almost completely lost. Then I flashed (through TWRP) the stock kernel (JWR66V), which I found here, and the problem continued. Than I flashed (also through TWRP) the AOSP kernel, which I found on that same thread, and the data problem was solved but the screen transition effect had little hickups.
After all that I didn't understand what happened and what I did wrong, could someone explain to me that diffence and what I should've done instead? It would be very apreciatted.
Thank you
Related
Hi guys,
ok so basically I asked for help on this in a thread thinking it was ROM related, but now I know it's not. I flashed cm 10.2 after stock 4.3 and what happens is that when I try to restore my backups they don't work (I mean TB installs them, but they FC as soon as I open them). Thinking it was CM related I tried another 4.3 ROM and same issue there (I tried all 4.3 ROMs on xda).
I then decided to go back to 4.2.2 thinking it was 4.3 related and again with yesterday's PAC nightly the issue is still there...
This is what I see when I reboot my phone:
"System UIDs Inconsistent
UIDs on the system are
inconsistent, you need to wipe
your data partition or your
device will be unstable.
I'm Feeling Lucky"
Any ideas guys?
Get the Fix Permissions application from the Play Store.
Sent from my Nexus 4 using Tapatalk 4 Beta
theraf90 said:
Hi guys,
ok so basically I asked for help on this in a thread thinking it was ROM related, but now I know it's not. I flashed cm 10.2 after stock 4.3 and what happens is that when I try to restore my backups they don't work (I mean TB installs them, but they FC as soon as I open them). Thinking it was CM related I tried another 4.3 ROM and same issue there (I tried all 4.3 ROMs on xda).
I then decided to go back to 4.2.2 thinking it was 4.3 related and again with yesterday's PAC nightly the issue is still there...
This is what I see when I reboot my phone:
"System UIDs Inconsistent
UIDs on the system are
inconsistent, you need to wipe
your data partition or your
device will be unstable.
I'm Feeling Lucky"
Any ideas guys?
Click to expand...
Click to collapse
you can find a solution in this post:
http://forum.xda-developers.com/showpost.php?p=9365024&postcount=4
I tried it and it worked.
Updated my Nexus 4 to 100% stock Android 4.3 JWR66V factory fresh (no data imported, except the included android backup/restore functionality), and ever since I set up the device, I've been experiencing distortion when leaving the Gallery app.
See this video: http://youtu.be/tEwQJPuc0GM
I factory reset the device after the first time I experienced it but it didn't go away. It doesn't matter if I select photos locally or from my G+ account, almost every time I'm backing out of the app all the way, the graphics distort as if there is an issue with the graphics drivers.
I never had this issue on any of the previous versions of Android on this Nexus 4.... Ideas anyone?
You should download the stock images and reinstall 4.3 through fastboot. Efrant has a great guide in general for returning to stock. If that doesn't fix it, something is wrong.
Be sure to verify the md5 of the download.
Are you using any custom kernel.Using JSS kernel on JWR rom may give you graphic distortion.
if yes,just download any JWR kernal for nexus 4 4.3 you like and flash it or you can download stock JWR kernel here http://forum.xda-developers.com/showthread.php?p=44345213
If no,just try to do what estallings15 said.
Hi. I'm having wifi issues with my Nexus. It started after flashing MIUI. I was using TWRP to flash, it took a while for the google logo to disappear and to get to the Xiaomi bootlogo. After it finally booted, the wifi was stuck to "turning on", but never ultimately firing up(couldn't get it to turn on nor off, even having turning it off). I've also noticed that I have the same EXACT issue with CyanogenMod. I completely returned to stock, i've relocked the bootloader and everything. I tried CM installer today and i'm rooted again with CM, but still I have the same exact issues as before. I don't have these issues with some other roms such as stock, official Omnirom and such, i wouldn't think it would be exactly a hardware issue, since it works just fine with certain roms. Would anyone have an idea why my phone is having this issue? It wasn't always this way. Specifically, I haven't been having issues with 4.4 roms. Does anyone think it could be something related to bootloader, or something?
Juanito216 said:
Hi. I'm having wifi issues with my Nexus. It started after flashing MIUI. I was using TWRP to flash, it took a while for the google logo to disappear and to get to the Xiaomi bootlogo. After it finally booted, the wifi was stuck to "turning on", but never ultimately firing up(couldn't get it to turn on nor off, even having turning it off). I've also noticed that I have the same EXACT issue with CyanogenMod. I completely returned to stock, i've relocked the bootloader and everything. I tried CM installer today and i'm rooted again with CM, but still I have the same exact issues as before. I don't have these issues with some other roms such as stock, official Omnirom and such, i wouldn't think it would be exactly a hardware issue, since it works just fine with certain roms. Would anyone have an idea why my phone is having this issue? It wasn't always this way. Specifically, I haven't been having issues with 4.4 roms. Does anyone think it could be something related to bootloader, or something?
Click to expand...
Click to collapse
i have a similar problem... i rooted my nexus and flashed a custom rom (PACman) when it boots wifi is disabled, also bluetooth doesnt work neither any sounds, no music, no speaker, nothing, so i flashed Paranoid android (both based on 4.3) and i had the same problem
so then i flashed stock, everything ok, then CrDroid (based en 4.4) everything ok, then OmniRom (Based on 4.4) everything ok too...
i posted it here and got no replies, hope someone could help
Yes, right now I'm running an unofficial CM 11, and no issues. I wonder if something needs to be downgraded, in order for things to be okay again. I would still like the option to be able to run 4.2/4.3 based roms. Maybe I could try flashing to stock 4.2 or 4.3, then reroot, and test my results
Sent from my Nexus 4 using Tapatalk
What radio/baseband version are you using?
Hi, I'm using AOKP last nightly builds and since 2013-10-18 Wi-Fi started to stuck, settings ui errors and other problems. So I just tried franko kernel with official AOKP releases and Wi-Fi now is working fine. But i've faced skype problems). After 4 minutes it hangs and i need to restart my phone.
Hi!
I just bought a Nexus 4 with broken touch screen which I replaced myself.
After I replaced it, I decided to start fresh and updated the device directly to stock 4.4 using fastboot commands and got stuck in bootloop (4 circles going on for hours).
Then I tried different factory images and managed to boot under official Android 4.2.2 and it worked flawlessly until I tried to update with 4.3 OTA (with radio .83)
I found out that downgrading radio from .83 to .48 (or .53) allows the device to boot under Android 4.3.
I'm now stuck at this stage because the same trick does not work after 4.4 OTA (from 4.3).
The issue seems to be acknowledged by Google but they don't seem to have an official software fix for it since they only go for a replacement.
I'm considering an RMA but since I replaced the screen myself, I'm facing the risk to be charged 200€ if my warranty gets void (if they really control the device as they say).
Anyone managed to fix this issue? It seems to be linked to the radio (can't go further than radio .48 / .53)?
Just found out that the jack/proximity/light sensor wasn't properly connected, probably after the screen replacement. It now boots under 4.4.2
Found people with the same issue on this thread : http://forum.xda-developers.com/showthread.php?t=2595283
Just ended up reading it but my researches did not drive there earlier.
To conclude, bootloop under 4.3 and 4.4 can be related to a faulty (or just disconnected) sensor.
neoantho said:
Just found out that the jack/proximity/light sensor wasn't properly connected, probably after the screen replacement. It now boots under 4.4.2
Found people with the same issue on this thread : http://forum.xda-developers.com/showthread.php?t=2595283
Just ended up reading it but my researches did not drive there earlier.
To conclude, bootloop under 4.3 and 4.4 can be related to a faulty (or just disconnected) sensor.
Click to expand...
Click to collapse
I confirm my nexus also bootloops on android version >= 4.3.0 due to faulty sensor.
Basis of conclusion:
My nexus 4 also started bootloop suddenly. I tried installing 4.4.2 and even 4.3 from factory images but everytime it stuck at boot animation. The only version currently working is 4.2. I always used a software called smart cover but it started mus-behaving. so i downloading phone tester and proximity sensor finder from play store, both the programs told me they were waiting for sensor/they did not get data from proximity and light sensor.
Question:
is there any way to update to 4.4.2 without being stuck at bootloop without replacing the sensor?
thanks in advance!
varun037 said:
I confirm my nexus also bootloops on android version >= 4.3.0 due to faulty sensor.
Basis of conclusion:
My nexus 4 also started bootloop suddenly. I tried installing 4.4.2 and even 4.3 from factory images but everytime it stuck at boot animation. The only version currently working is 4.2. I always used a software called smart cover but it started mus-behaving. so i downloading phone tester and proximity sensor finder from play store, both the programs told me they were waiting for sensor/they did not get data from proximity and light sensor.
Question:
is there any way to update to 4.4.2 without being stuck at bootloop without replacing the sensor?
thanks in advance!
Click to expand...
Click to collapse
Did you find a solution?
Not yet. I will definitely post if I am able to find one. Researching on the topic currently.
I've got the same problem with 4.3 bootloop. Could this be fixed with custom rom?
Try flashing 4.2.2 rom - custom or stock
I'm with 4.2.2... and that's not what I asked. I want 4.4.2. Is it possible to load custom kit kat with this kind of sensor problems?
Update:
I have been trying to update nexus. I tried to install radio version 98 and bootloader from 4.4.2 version to android 4.2.2 without updating system image. it works. so i think basically the issue is with the system image itself. looking for the patched system image now or a developer who can patch system image to ignore the faulty sensors.
varun037 said:
Update:
I have been trying to update nexus. I tried to install radio version 98 and bootloader from 4.4.2 version to android 4.2.2 without updating system image. it works. so i think basically the issue is with the system image itself. looking for the patched system image now or a developer who can patch system image to ignore the faulty sensors.
Click to expand...
Click to collapse
I'm on 4.3 and the sensors dont work ... the proximity, gyro... nothing works... any solution?
Hello friends, i have a similar problem.
I went to replace the glass and warmed him a lot and damaged the lcd. I bought a complete lcd with touch, but when installing it the cel came in infinite boot, Flashed the 4.2.2 and booted but sensor is working by testing q I did for an app, the problem is they do not find my network and baseband ta as unknown, been through the radio's 4.2.2 (the version I am now). the motherboard was not with the screen when I get heated to the glass, were in housing with the display flex earpiece with proximity sensor and flex usb that has the microphone and led, everything is normal, the LED only that does not work. One would like some light please. I thought about buying the flex usb to see if it resolves, but does not want to risk spending for nothing. Thank you very much!
Sorry for my english, I'm using google translator
Sorry to Disturb
Hello everyone I am very new to this area of computing (and this forum). However I have still ended up in the same hole as you guys are describing although it happened for a completely different reason. (BTW: I am rooted)
one day I tryed to play the android game NOVA 3 on my Nexus 7 on the highest graphical setting so I went and researched how to do this. I was pointed towards some kind of app called 'ChainFire 3D', Once I pressed the install button inside this app the Nexus 7 switched off and the next time I tried to turn it on I got the X logo of death (boot loop). I then tried to enter recovery and I got the annoying 'no command' error. I cant seem to remember how I rooted this thing but I do have access to the fastboot stuff ONLY (inside cmd).
if there is anyone who has any idea how to go about fixing such an issue without wiping everything on my nexus could they please get back to me ASAP.http://forum.xda-developers.com/images/smilies/fingers-crossed.gif
Gloftking said:
Hello everyone I am very new to this area of computing (and this forum). However I have still ended up in the same hole as you guys are describing although it happened for a completely different reason. (BTW: I am rooted)
one day I tryed to play the android game NOVA 3 on my Nexus 7 on the highest graphical setting so I went and researched how to do this. I was pointed towards some kind of app called 'ChainFire 3D', Once I pressed the install button inside this app the Nexus 7 switched off and the next time I tried to turn it on I got the X logo of death (boot loop). I then tried to enter recovery and I got the annoying 'no command' error. I cant seem to remember how I rooted this thing but I do have access to the fastboot stuff ONLY (inside cmd).
if there is anyone who has any idea how to go about fixing such an issue without wiping everything on my nexus could they please get back to me ASAP.http://forum.xda-developers.com/images/smilies/fingers-crossed.gif
Click to expand...
Click to collapse
You might be able to re install your android without clearing user data. Try to flash the device with Google provided factory images without the reset tag.
FEW
varun037 said:
You might be able to re install your android without clearing user data. Try to flash the device with Google provided factory images without the reset tag.
Click to expand...
Click to collapse
Thanks for the quick responce. Could you please describe in more detail what exactly you mean and how I would go about doing this because I only vagely know what you mean by flashing.http://forum.xda-developers.com/images/smilies/confused.gif
Gloftking said:
Thanks for the quick responce. Could you please describe in more detail what exactly you mean and how I would go about doing this because I only vagely know what you mean by flashing.http://forum.xda-developers.com/images/smilies/confused.gif
Click to expand...
Click to collapse
Follow this. It has the reset flag removed and will not wipe your data
http://forum.xda-developers.com/showthread.php?p=53176897
Sent from my Nexus 5 using XDA Free mobile app
Hi,
I am facing the same issue .. Nexus 4 is stuck at boot loader after screen replacement .. is there any solution that I can follow to resolve this .
Regards,
Ripu Daman
The same problem with me, i did replaced my phone screen. I didn't notice that could damaged the phone. :crying:
so, theres no way to solve ??
Only way is to downgrade the os version to 4.2.2 and stay there.
nexus 4 stuck at boot loop.
Hi guys i have the same problem as you are describing, o got a nexus 4 android 4.2.2 JQRW build I've flashed it from all different ways and i just got flash cm10.2 and carbon rom but only stuff jeallybean and as someone said here i used adb sideload to push the update 4.3 and got stuck at the boot but i flash the radio 84 to 48 and my phone boot Fine but i am stuck at jeallybean yet and i want chroma rom android 7
---------- Post added at 03:00 AM ---------- Previous post was at 02:56 AM ----------
Please we need a wise man to fix this problem. I am tired of flashing stock img and custom ron for nothing.
Hello,
I received my Nexus 6P yesterday and got my SIM card activated without any issues at Verizon. I immediately took it home, unlocked the bootloader, installed TWRP, and then flashed CyanogenMod's latest nightly. After booting in, wireless networks weren't detected, and I only had 3G (no 4G LTE as I should). I restored my backup of the stock ROM that I made in TWRP and it hung at the Google logo. I'm not sure why. I then flashed all the latest factory restore images (MTC19X) to get it working again and determined that the issues I had in CyanogenMod might have happened due to the vendor.img I had on my phone at the time not being compatible with that build of CM13.
My questions are:
1) What are the known issues that would likely occur due to vendor.img being a different version than what CM13 was based on? The concept of vendor.img is new to me. I haven't had this, as far as I know, on any of my other phones (granted I'm coming from a locked Samsung Galaxy S5 that I've had for almost 2 years)
2) How can you easily tell which vendor.img CM was based on so you know which one to flash?
3) Is there anything else I should be made aware of before attempting to flash CM13 again?
4) While using CM13, do most people recommend a custom kernel? If so, which one and how stable is it? What are the benefits of switching from the stock kernel, and how simple is it to go back if there's a problem?
Thanks!!
dude...I just got the N6P and ran CM13 within hours. This is what I did...
unlocked the bootloader
downloaded the lastest (MTC19X) image off of https://developers.google.com/android/nexus/images and unpacked it into the C:\Program Files (x86)\Android\android-sdk\platform-tools folder
ran the flash-all.bat
fastbooted TWRP
installed CM13. (didn't wipe internal storage)
installed arm64 open Gapps pico
BAM!!!
right now running stock kernel. it's cool. I'm PrivacyGuard-ing the hell out of all my apps (turned off START AT BOOT and KEEP AWAKE for almost every downloaded app), though, so battery is OK
also using Kernel Adiutor but underclocking values for the CPUs doesn't seem to stick
So it likely worked for you since you had flashed the newest vendor.img first. Apparently there are compatibility issues with certain features that cause them not to work (such as WiFi) if you're using an older one.
chaoticyeshua said:
Hello,
I received my Nexus 6P yesterday and got my SIM card activated without any issues at Verizon. I immediately took it home, unlocked the bootloader, installed TWRP, and then flashed CyanogenMod's latest nightly. After booting in, wireless networks weren't detected, and I only had 3G (no 4G LTE as I should). I restored my backup of the stock ROM that I made in TWRP and it hung at the Google logo. I'm not sure why. I then flashed all the latest factory restore images (MTC19X) to get it working again and determined that the issues I had in CyanogenMod might have happened due to the vendor.img I had on my phone at the time not being compatible with that build of CM13.
My questions are:
1) What are the known issues that would likely occur due to vendor.img being a different version than what CM13 was based on? The concept of vendor.img is new to me. I haven't had this, as far as I know, on any of my other phones (granted I'm coming from a locked Samsung Galaxy S5 that I've had for almost 2 years)
2) How can you easily tell which vendor.img CM was based on so you know which one to flash?
3) Is there anything else I should be made aware of before attempting to flash CM13 again?
4) While using CM13, do most people recommend a custom kernel? If so, which one and how stable is it? What are the benefits of switching from the stock kernel, and how simple is it to go back if there's a problem?
Thanks!!
Click to expand...
Click to collapse
1) Depends on ROM /VENDOR, sometimes nothings happens then an error message, sometimes things doesnt work
2) Just download fresh the latest snapshot, release or nightly (they are much more stable then for a few years!) and vendor image (use these ones which are recommended!)
https://wiki.cyanogenmod.org/w/Install_CM_for_angler (there is a link for the vendor)
3) If you stay close on the tutorials, i dont know what should happen (flashing a rom is normally not critical, installing a recovery can be!)
4) Custom kernels can be great, but its not a must-have. Which kernel you should use depends on your wishes: better battery, more power etc.
Hope i could have help you a little bit!
kaufikauf said:
1) Depends on ROM /VENDOR, sometimes nothings happens then an error message, sometimes things doesnt work
2) Just download fresh the latest snapshot, release or nightly (they are much more stable then for a few years!) and vendor image (use these ones which are recommended!)
https://wiki.cyanogenmod.org/w/Install_CM_for_angler (there is a link for the vendor)
3) If you stay close on the tutorials, i dont know what should happen (flashing a rom is normally not critical, installing a recovery can be!)
4) Custom kernels can be great, but its not a must-have. Which kernel you should use depends on your wishes: better battery, more power etc.
Hope i could have help you a little bit!
Click to expand...
Click to collapse
Very much so. I appreciate it!
Has anyone encountered the constant popup of the Select Sim Card message? I'm using project fi and I am still unable to find a solution to this issue.