Hi,
story first, problem below: I crashed (a while ago) the display of my Nexus 4. I changed it with some cheap chinese crap (that was offered as original, but well, China ) ... and the Nexus was stuck in endless bootloop. First I thought I did flash it wrong or did a mistake changing the display. After hours of looking for clues I gave up. Recently I found some idiot-proof flashing tool (SkipSoft) and tried it again with the oldest factory image available: occam 4.2.2 (JDQ39).
The Nexus did not only boot, but boot up faster than my none damaged Nexus 4. Ok, the display was in comparison like scaled to 90 %, but no real problem. I was kinda happy and tried to flash CM or the latest (5.1.1.) factory image available. And again, there way my problem. I did flash every factory image, except 4.2.2, and same sh**. Flashed 4.2.2. (again) - no problem at all. I did the auto upgrade to 4.3 - endless bootloop again.
Did anybody had this problem before? I think it's a driver issue, since it works with 4.2.2. but no later images. But is it Androids fault (display driver switch between 4.2.2. to 4.3)?
Btw.: pic of the original and the "oliginal" display:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Related
I bought mine the release day, everithing was fine until the last update (if I remember in november), the screen suddenly started to show this black lines only in white background (when I go to settings, opening chrome, etc.) it isn't a major problem as I can see I think it might be a software problem, but I want to be sure. It is a hw problem or a sw problem? (I want to be sure, to claim my warranty with Samsung) Somebody have had this problem?
TDrkKnight said:
It is a hw problem or a sw problem?
Click to expand...
Click to collapse
The only way to know for sure is to do a hard reset. Problems like that occurring well in to ownership are the scariest. It could be a one off defect or the start of a pandemic. Good luck.
I do the hard reset a few weeks ago but it still the same, I was thinking about a downgrade, but I don't want to be stuck and have a soft brick (it hapend when I try to downgrade my S4)... And there are links only for Terafile and Rapidgator.... and it will take 8h to download the fw (I'm not premy)
Well I learned by the hard way.... DO NOT FLASH AN OLDER FW VERSION!!!!!! if you do that you will have this in your screen
Firmware upgrade encountered an issue. Please select recovery mode in kies and try again
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The good thing is that you just need to reinstall your current FW version.
Hello everyone, I have a BIG problem on my Galaxy Nexus ("yakju maguro" (GSM/HSPA+) currently with 4.3 (JWR66Y) stock installed).
In the last few months I used AOSP Lollipop and my phone worked well. Few days ago it has restarted suddenly and contined to do it after random time... Then I flashed again the AOSP 5.1 but in the TeamWin recovery I noticed that my phone memory was more than 13 Gb, but my phone is the 8 Gb version! I checked online for a solution and I flashed the stock image to try a "reset" of the bug, but nothing happened: my phone still shows around 13 Gb. To test it, I copied up to 11 Gb of files and it worked, so the memory is really bigger than the previuos one (or at least it seems).
Now I'd like to know how can I fix this problem? If the phone will start again with freezes and reboot, what can I do?
I hope there's anyone with any suggestion... I have really no idea about what to do. Thanks to all that will try to help me, and excuse me for my poor english.
P.S.: here are 4 images that show the memory "bug":
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Update: after I deleted the folder with the 10 Gb of files, the phone freezed and after a sound like a "pop" it restarted.
My tablet seems to be messed up...
I get constant app crashes even when just browsing, watching a youtube video is almost impossible due to lag and antutu reboots the device or the app crashes and when I get a benchmark done I get this....:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
That's almost as bad as the Galaxy Y....
My device is clocked at 2.0gHz(or 1.7 or 1.5 it does not matter)
Trust me I've tried every rom... from kitkat cm11 to stock 5.1 and it's all the same
Is this thing broken?
Restore stock clock speeds, then maybe someone can help? Revert to stock kernel and ROM, replicate. That would be the first order of business.
Save your stuff and perform a factory reset: delete everything, flash the latest 5.1.1 factory image.
I guess you have dirty flashed your ROMs too often ? Some leave thrash behind and some so called "developers" like to use some tweaks which are no use anymore ( and have been made for Android 2 or even older ..)
If your device behaves like this even in a 100% Stock environment, it might be faulty indeed..
So I tried to do a root on my LG Gpad 7.0 and well I don't know what happened
this is my first time trying this so I used "KingRoot"
Now I am having a weird display issue were if the tablet is in portrait I can't see Jack but if I set it to Landscape I can see only 25ish % of my screen
Any Ideas? please
P.S. before coming here I tried using ADB and I also unrooted (I think) my tablet
another thing I forgot
darktornado23 said:
So I tried to do a root on my LG Gpad 7.0 and well I don't know what happened
this is my first time trying this so I used "KingRoot"
Now I am having a weird display issue were if the tablet is in portrait I can't see Jack but if I set it to Landscape I can see only 25ish % of my screen
Any Ideas? please
P.S. before coming here I tried using ADB and I also unrooted (I think) my tablet
Click to expand...
Click to collapse
I also tried Factory resetting the tablet [IMG="Here is what the tablet looks like now"]https://s32.postimg.org/5mqy50imd/Screenshot_2016_07_29_13_36_10_1.png
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Not sure if anyone else got this fixed with 8.1 DP, but here is what I found. After flashing the 8.1 DP firmware, the corrupted error was gone and replaced with the normal yellow/orange warning that is typical when you unlock the bootloader. As a test I flashed the Jan 2018 7.1.1 flash, and the corrupted error was still gone! Even relocked the bootloader after re-flashing 7.1.1 to stock, and it worked with no errors, just like out of box stock.
If anyone still has a corrupted error this may help you as it did me. Don't know if it works on 3UK, or other carriers, as Im using T-Mobile USA with the normal version of the razer phone from the Razer web store.
If I understand correctly, you mean this (last image)?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If that appears, with Razer logos instead of that precaution sign ofc, I understand that the system image got tampered and DM-Verity was active in the boot partition, thus cleaning the device through fastboot solved that.