Hi! I have installed LineageOS with android 7.1.2 on my nexus 5 approximately one year ago. Now I've got myself a new phone and I've wanted to go back to android 6.0.1 on my nexus. I've downloaded official image from google's site flashed everything and all was looking good until I boot into the system. As soon as the standard first configuration menu pops up screen locks immediately and i can't unlock it. I've tried to install first android version on nexus 5 which is Android 4.4 and ended up with the same result. Same thing when i've installed Cyanogenmod with android 6.0. I have looked around the internet and some people say that it can be issue with the power button but i have installed LineageOS again and everything works just fine.It's not like the screen goes off itself I can accualy see the locking animation. I don't know that much because it was my first experience with rooting and custom roms.
Related
Google has issued a brand new Android 5.1.1 Factory Image file that should patch the StageFright Security bug forever. If you want to install a clean Lollipop OS on your tablet, then you should check all the info listed in this post.
The StageFright Security bug should’ve been fixed with the previous LMY48I Android 5.1.1 release, but that didn’t happen as tons of Nexus 10 users have reported that the security vulnerability was still there. If you want to be sure that this bug is fixed, then you should flash the latest LMY48M firmware version of Android 5.1.1 Lollipop OS on your tablet.
Installing a factory image on your will always remove all the data from your tablet and you should create backups before starting the flashing process. Read the following guidelines first:
use this post only with the Google Nexus 10 tablets.
– don’t try to update any other different tablets with the files that you will find in this post.
by installing this Android 5.1.1 LMY48M factory image you should know that the flashing process will remove all data from it.
– however, if your tablet is running a stock Android 5.1.1 LMY48I build that hasn’t been modified in any way, then you can use a small workaround in order to avoid the ‘factory reset’.
– more info on the update workaround can be found when you reach the tutorial instructions.
backup all the important files before starting the installation process.
enable USB Debugging for your tablet from its Developer Options menu.
– if you can’t find Developer Options under Settings menu, then you should enable it first: go to Settings> About Phone and tap 7 times on the Build Number section.
– return to Settings, scroll down, open Developer Options and find the USB Debugging option in order to enable it.
use this post only if you are an advanced user.
we cannot be blamed in case you end up losing any data in the process nor in case you brick your device.
check your Nexus 10 battery charge level and make sure that it is over 40%, it will prevent your device from powering down during installation.
read the whole tutorial and make sure that you won’t be skipping any steps, so that you will be able to complete the factory image installation at your first attempt.
I've used three different browsers to read this page in case I have some sort of content blocker active, and I see no tutorial in any of them...?
It's always nice to see people trying to help, and notifications of new ROMs are always welcome (though I installed LMY48M weeks ago), but there are already hundreds of tutorials showing how to upgrade a ROM - maybe you decided not to go ahead with the rest of your post?
With latest update 5.1.1 LMY48T my tablet powering OFF randomly. I had naver this issue before on 5.0.2 (( This update is piece of crap in my opinion
Amiga4ever123 said:
With latest update 5.1.1 LMY48T my tablet powering OFF randomly. I had naver this issue before on 5.0.2 (( This update is piece of crap in my opinion
Click to expand...
Click to collapse
I've had the same problem, plus now I have battery issues. The tablet won't fully charge and will randomly turn off after some unknown time of use.
This update has killed my battery.
Beware of this update!!!!!!!!!!!!!!!!!!!!!!!!!!!! IT TOTALLY SCREWS YOUR NEXUS 10!!!!!!!!!!!!!! I´m reverting back to LMY47V because the newer updates are bricking my Nexus 10! I have flashed and reinstalled it 10 times by now, it just can´t handle this update! I think they did it for you to buy a new Nexus device by killing the Nexus 10!
maw said:
Beware of this update!!!!!!!!!!!!!!!!!!!!!!!!!!!! IT TOTALLY SCREWS YOUR NEXUS 10!!!!!!!!!!!!!! I´m reverting back to LMY47V because the newer updates are bricking my Nexus 10! I have flashed and reinstalled it 10 times by now, it just can´t handle this update! I think they did it for you to buy a new Nexus device by killing the Nexus 10!
Click to expand...
Click to collapse
Are you referring to build lmy48m or lmy48t?
I can't get to flash anything. Even after flashing another version, the old version just stays. I've tried everything. Formatting, erasing, downgrading, nothing works. I think my Nexus 10 is officially dead. It will boot up and like 1 minute after it just crashes and reboots again. I have read that others have this problem, could be that the motherboard is shot. Since there are no motherboards available, I can't even repair it. It lasted exactly 2 years, what a waste!
Well I just spent hours going through all the ota update from original jelly bean that it came with up to the latest lollipop build lmy48t and everything is working fine thus far.
Hello.
I have a Samsung Galaxy S4 i9500. I got it about 2 years ago. About a year after purchase I rooted the phone to install a backup software, but I did not know that rooting would disable software updates and when I found out that S4 had gotten the Lolipop update but my phone wouldn't show anything for two months, I decided to install the "original" Lolipop from Samsung. I found it on a website which I do not remember anymore.
Well here's where the problem starts - Apparently my phone was from Korea and it was imported to India. As a result of me installing an OS made for India on a Korean phone, the SIM wouldn't work and the OS ran very crappily. I got the SIM unlocked by an operator but the OS just sucks really bad. It gets stuck very often, apps close randomly and they behave as if they have been relaunched every 5-10 mins. Sometimes if I'm playing music the player will stop mid-track and I have to press play again. The menu and homescreen also do the same thing, keep behaving as if they have been relaunched every few minutes or every time I unlock the screen.
Any idea what I can do to fix my phone? I'm ready to go back to a previous version of android if that means a smooth, non-annoying experience.
Check your actual version of the stock rom from sammobile.com. Download the correct stock rom and re flash through Odin
Thanks, but I just ended up installing CyanogenMod and gotta say I'm more than happy with it :3
So I just bought a Nexus 9 off ebay, works great, but it came with Android N. So I decided to downgrade it to 5.0 (I have certain apps that don't work on later OS's) I downgrading to Android 5.0 no problem. Then I went through the Android startup screen. After it forced me to log into Wi-Fi, it told me I had to update and restart the device. (Putting it back on Android N). Is there no way to get around this? At this point it is looking like a waste of $250.
devbots said:
So I just bought a Nexus 9 off ebay, works great, but it came with Android N. So I decided to downgrade it to 5.0 (I have certain apps that don't work on later OS's) I downgrading to Android 5.0 no problem. Then I went through the Android startup screen. After it forced me to log into Wi-Fi, it told me I had to update and restart the device. (Putting it back on Android N). Is there no way to get around this? At this point it is looking like a waste of $250.
Click to expand...
Click to collapse
I have fixed the issue. For anyone wanting to downgrade from 7.0 to 5.0. First downgrade to LRX21Q, then downgrade to LRX21R. It skips the force update. Then from there, root your device.
So, since the past few days my i9300 keeps randomly rebooting. At first it was not that much of an issue but today it started to go into a boot loop.
Sometimes it finishes booting but before I can go into the settings to factory reset it, it crashes.
I also tried to get into TWRP but as soon as the logo shows up, it crashes.
I can't even use the download mode because, guess what happens: it crashes.
I really don't know what to do right now. I still have a spare motherboard but I'm not able to access it for another week. It would be a shame to throw away a perfectly fine motherboard if it is just a software thing.
Currently it is running the last version of SlimKAT that was released, I don't know which version of TWRP it is running, but I updated it just a few weeks ago. It is not using the original battery fom Samsung but one from Anker which should be fine.
If anyone needs more or specific information, I'm more than happy to provide it.
Hi,
just want to ask, you're stuck in bootloop at the "samsung" Logo or where?
Because I am having bootloops, too since 2 days. Phone kept restarting one or 2 times since last 3 days and when i got home on 1. november i put my phone to the charger and got back 20min later and saw it was rebooting.
Mine is stuck in optimizing apps or if i wait long time then it is at starting android: starting apps and i see when the color temperature of the phone changes (i think of the light sensor) it gets stuck and reboots.
just for docu (even if its not the same problem):
i have a 2nd spare s3 for testing here and to test ag. hardware issue i made a twrp backup and both are dying. after facory reset and installing apps i recognized that it is dying at the installation of telegram app and after that its going to the same bootloop on both phones. i checked telegram and seems to fit in, they updated their app at 1. november. and date code of last changes before the bootloop: telegram was modified. so for my problem it seems to be caused by telegram.
I am using bliss rom 6.1 (Andoid 6 Marshmallow, CM13 based) at i9300
sorry for maybe not beeing a help. I now found out that it happens to other app installations, too. so seems to be a problem deeper in android/interfering with this specific rom - maybe its play store . So far since it happens on 2 identical s3 with this rom I will have to change the rom now. :crying: (was stable >1year)
It is stuck on the Samsung Logo. I've been testing multiple ROMs for stabillity because after some time it will randomly crash (most of the time after 2 - 3 weeks of usage) but it was never this bad. I thought it was due to the fact that newer versions of Android need stronger Hardware, so I switched back to KitKat.
But Telegram could be a reason for this. I too use it and if you say they updated it, the timeframe would match.
I know that my spare motherboard is fully functional, with stock rom, not rooted or anything. I will swap it out as soon as I can and will install Telegram to try to confirm that this could be the reason.
Niggyminator said:
It is stuck on the Samsung Logo. I've been testing multiple ROMs for stabillity because after some time it will randomly crash (most of the time after 2 - 3 weeks of usage) but it was never this bad. I thought it was due to the fact that newer versions of Android need stronger Hardware, so I switched back to KitKat.
But Telegram could be a reason for this. I too use it and if you say they updated it, the timeframe would match.
I know that my spare motherboard is fully functional, with stock rom, not rooted or anything. I will swap it out as soon as I can and will install Telegram to try to confirm that this could be the reason.
Click to expand...
Click to collapse
good luck!
But if you'r stuck at the samsung logo, sounds even worse than mine. if your having a new board could at least be an option to check if its really not a hardware issue (you mentioned that its getting again unstable after some time)
for my problem I managed to backup most things out of the nandroid image and moved to ressurection remix with android nougat. the new rom is running fast and so far without any problem - hope it stays like that .
Hello everyone
I'm bought myself an old genesis gt1230 tablet, with 10 inches, but its O.S is pretty old, actually, it is running android 4.0. I'd like to update to Android 4.3 or newer, but every time I try to reboot into bootloader, running adb reboot bootloader, it reboots normally. When I use the keys combination to recovery mode, it gets a black screen and never boot.
Inside the tablet settings, there's no developer options, and no build number. I've tried to tab several times every option in the "about" menu, but got no developer options. So I can't unlock OEM or install CWM to use a new ROM.
Someone owns this tablet, or has some experience dealing with genesis tablets? Thanks