Related
Hi all,
The day before yesterday I decided to move from my GNex to the new N4, but my time with it was short, because I have managed to accomplish an incredible feat: brick a N4 just 12hours after purchase :laugh:.
Now, I'm not creating this topic to moan about it, I'm fully aware that bricking is a possibility for every flash, and the phone is already sent back to LG. I just want to tell you all what I did, so we can, possibly, find what I did wrong and help other people to avoid it :highfive:. And a little bit of background, I got Gnex for a year, before that is a G1, with flashing almost become a daily job (not so with the Gnex, as I prefer the stock experience, but still a lot of rom switching and kernel flashing every few months).
My N4, right of the bat, I put it into fastboot unlock, root (the usual thingies). It's still working as normal, but the battery life is not so stellar, so I decided to try franco's kernel. I flashed r53 to my phone, it boot up normally, I feel the performance is too slow compare to stock, so I flashed the latest test version r61, too. It's still working without a hitch, abeit not as smooth as stock.
So I decided to get back to stock. I'm too lazy to do fastboot with stock image, so I download the stock kernel CWM package from this topic, and just to be safe, I flashed faux's kernel reset from here before that. The flashing was succeed, no error, but when I reboot, the phone failed to boot up, just black screen. If I plug it into my computer, it show up as qhsusb_dload, which is a telltale sign of a corrupt internal memory aka definite brick.
To put it short, the sequel is: stock -> unlock -> root -> franco r53 -> franco r61 -> faux reset -> stock kernel flash -> brick.
I guess I did something wrong between the faux reset and stock kernel flashing. can anyone tell me what I did wrong? I did happen to flash wrong kernel build on my Gnex before but the worst I got is a boot loop, not straight up brick like this. And I'm very surprised that a core part of the phone (fastboot) can be corrupted that easy.
And, flash safely :good:
interesting, ive been having problems with my kernel, and used faux reset plenty of times. hopefully someone can chime in for you. Mine is still up and running with faux kernel too
I swear this phone is getting bricked a lot more than a y other nexus
Sent from my Nexus 4 using Tapatalk 2
italia0101 said:
I swear this phone is getting bricked a lot more than a y other nexus
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I swear you are a complete moron.
As for the OP's problem download nexus tool kit , Put the phone in bootloader mode and flash stock factory image.
italia0101 said:
I swear this phone is getting bricked a lot more than a y other nexus
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Are u serious Every phone has a chance of that alot of times
Soon To Be A Nexie
berz said:
I swear you are a complete moron.
As for the OP's problem download nexus tool kit , Put the phone in bootloader mode and flash stock factory image.
Click to expand...
Click to collapse
Yea ... im a complete moron.. iv not seen this " red light " problem with any other Nexus device, have you? of course i know theres a chance of bricking with anything , but iv never seen a nexus device die so easily just by running a benchmark ?!? thats all im saying
i know this isnt the problem the op is having , but its just strange..
either way , maybe chill out a bit before you start pulling out the names yea...
I want to chime in ^_^
I think the kernel reset screwed everything up IMO. I think there was maybe some left over files on the ram disk that didn't get wiped out 100% (I'm assuming you didn't wipe completely, regardless of a kernel reset) and when you flashed stock kernel it couldn't rearrange them correctly and you ended up with a bricked device.
Just my thoughts.
Sent from my Nexus 4 using xda app-developers app
when going back to stock just flash the factory image. it is very easy once you have the files and learn how to do it and always work,
juliano_q said:
when going back to stock just flash the factory image. it is very easy once you have the files and learn how to do it and always work,
Click to expand...
Click to collapse
Bricking Nexus? lol? this is a joke? just reinstall the stock firmware and you're done.
as long as u didnt fscked up the bootloader or the partition scheme then you shall be not affraid and its fairly easy to recover.
Adam
Any chance you flashed N7 kernel? Read somewhere that the kernel partition of N7 has same id as bootloader partition of N4. So what happens is kernel overwrites the bootloader resulting in brick.
Sent from LG Google Nexus 4 using XDA Premium
AdamLange said:
Bricking Nexus? lol? this is a joke? just reinstall the stock firmware and you're done.
as long as u didnt fscked up the bootloader or the partition scheme then you shall be not affraid and its fairly easy to recover.
Adam
Click to expand...
Click to collapse
I still dont have my N4 but I always thought this. Coming from previous devices the only reason Ive seen a true brick is someone screwing up flashing radios or dicking with the boot-loader. I didn't think you could actually brick a device with ROMS/Kernels.
linh1987 said:
Hi all,
The day before yesterday I decided to move from my GNex to the new N4, but my time with it was short, because I have managed to accomplish an incredible feat: brick a N4 just 12hours after purchase :laugh:.
Click to expand...
Click to collapse
Power off. Hold "volume down" and press power button. This should get you to the bootloader. If it does, your phone is not bricked and there's loads of info on here to put it right again (stock factory image would be my first call here). If it doesn't work, I'd be tempted to remove the battery (IIRC, quite easy once you remove the screws at the bottom) and repeat the above instructions. (if you can get to the bootloader one way or another, your phone is most certainly not bricked!)
If this doesn't work, it's probably dead and you'll need to send back.
Daern
---------- Post added at 01:34 PM ---------- Previous post was at 01:27 PM ----------
berz said:
I swear you are a complete moron.
Click to expand...
Click to collapse
Didn't your mother ever teach you - "If you can't say anything nice, say nothing at all"?
This is not a site for trolling. Please go away.
I flashed different kernels many many times.
Never a problem.
OP should check for human error instead of blaming the device.
Sent from my Nexus 4 using xda premium
atulalvenkar said:
Any chance you flashed N7 kernel? Read somewhere that the kernel partition of N7 has same id as bootloader partition of N4. So what happens is kernel overwrites the bootloader resulting in brick.
Sent from LG Google Nexus 4 using XDA Premium
Click to expand...
Click to collapse
Sorry but i don't know what are you talking about ? what the same ID as bootloader? erm?
partition name in case of bootloader is bootloader, for case of kernel is boot
Adam
linh1987 said:
Hi all,
The day before yesterday I decided to move from my GNex to the new N4, but my time with it was short, because I have managed to accomplish an incredible feat: brick a N4 just 12hours after purchase :laugh:.
Now, I'm not creating this topic to moan about it, I'm fully aware that bricking is a possibility for every flash, and the phone is already sent back to LG. I just want to tell you all what I did, so we can, possibly, find what I did wrong and help other people to avoid it :highfive:. And a little bit of background, I got Gnex for a year, before that is a G1, with flashing almost become a daily job (not so with the Gnex, as I prefer the stock experience, but still a lot of rom switching and kernel flashing every few months).
My N4, right of the bat, I put it into fastboot unlock, root (the usual thingies). It's still working as normal, but the battery life is not so stellar, so I decided to try franco's kernel. I flashed r53 to my phone, it boot up normally, I feel the performance is too slow compare to stock, so I flashed the latest test version r61, too. It's still working without a hitch, abeit not as smooth as stock.
So I decided to get back to stock. I'm too lazy to do fastboot with stock image, so I download the stock kernel CWM package from this topic, and just to be safe, I flashed faux's kernel reset from here before that. The flashing was succeed, no error, but when I reboot, the phone failed to boot up, just black screen. If I plug it into my computer, it show up as qhsusb_dload, which is a telltale sign of a corrupt internal memory aka definite brick.
To put it short, the sequel is: stock -> unlock -> root -> franco r53 -> franco r61 -> faux reset -> stock kernel flash -> brick.
I guess I did something wrong between the faux reset and stock kernel flashing. can anyone tell me what I did wrong? I did happen to flash wrong kernel build on my Gnex before but the worst I got is a boot loop, not straight up brick like this. And I'm very surprised that a core part of the phone (fastboot) can be corrupted that easy.
And, flash safely :good:
Click to expand...
Click to collapse
If you took the same amount of time to search that you took to write this terrible OP you would have already fixed your phone....
tweaked said:
If you took the same amount of time to search that you took to write this terrible OP you would have already fixed your phone....
Click to expand...
Click to collapse
Hey tweaked, thanks for your contribution, but if you take 5 secs to search for a black screen issue with qhsusb_dload show up in windows, you will know that I went to a dead end.
@all: yes it's 100% my fault, I just double check and I DID flash grouper (aka N7) kernel to my N4, but I just feel it's so much easier to flash N7 kernel to N4 without any error. And again, I just want to repeat that I'm not moaning about it, it's totally my fault. I just want to help other people to avoid it :highfive:
atulalvenkar said:
Any chance you flashed N7 kernel? Read somewhere that the kernel partition of N7 has same id as bootloader partition of N4. So what happens is kernel overwrites the bootloader resulting in brick.
Sent from LG Google Nexus 4 using XDA Premium
Click to expand...
Click to collapse
Hey atulalvenkar, yes, I just did what you say. How stupid I'm. Guess we learn new thing every day
linh1987 said:
Hey atulalvenkar, yes, I just did what you say. How stupid I'm. Guess we learn new thing every day
Click to expand...
Click to collapse
You are the first person I heard that flashed a wrong KERNEL.
Congratz.
Sent from my Nexus 4 using xda premium
linh1987 said:
Hey atulalvenkar, yes, I just did what you say. How stupid I'm. Guess we learn new thing every day
Click to expand...
Click to collapse
Saw couple of posts on reddit where many people did the same thing. The problem is franco develops for both N7 and N4 and his XDA thread subject doesn't have any indication of the device. Because of this it's easy to get pointed to the wrong thread and download wrong kernel.
My phone bricked spontaneously. I had installed CM 10.1, with the stock kernel, about 12 hours earlier and was actually browsing facebook when the phone spontaneously rebooted. I could get into fastboot, but no matter what I tried, I couldn't flash a stable recovery or full image. Constant boot loops with the occasional successful system boot, only to reboot within a few seconds.. starting the whole process over again.
Flashed and formatted every accessible partition, followed every "how to" I could find. Absolutely no success. Luckily Google sent me a replacement and I had a new phone in 2 days. Running the same CM 10.1/stock kernel now, no issues.
My first phone (a Rev_11) always ran somewhat hot, and the battery wouldn't last a day. The replacement phone (also a Rev_11) runs much cooler and the battery lasts for 2 days easy, with the exact same software. I'm thinking the old phone just somehow toasted itself. Just speculation. Oh, the old phone was also a "slow" binned CPU.
Anyway, the point of my story is that is ISN'T entirely true that the ability to boot into bootloader/fastboot will guarantee you success when trying to resurrect a dead phone.
So after 8 hours my battery still said 100% and even shut off due to dead battery and it still said 100% full. In TWRP it also shows 100% full. Any ideas? I have it on the turbo charger now, since it died, and will wait about 2 hours then try to reset battery stats. Not sure what else to try. Nothing new installed, phone is stock other than rooted and TRWP.
This is why I stopped rooting phones. One feature breaks 2-3 things and end up flashing daily update zips.
Ian B
Mr Ian B said:
This is why I stopped rooting phones. One feature breaks 2-3 things and end up flashing daily update zips.
Ian B
Click to expand...
Click to collapse
huh?
The phone was rooted the day I got it, Nov 9th, and it just started doing it today. So how does root automatically cause the issue?
Anyway, any ideas would be great I think resetting the batterystats has worked just curious what may have started it.
Mr Ian B said:
This is why I stopped rooting phones. One feature breaks 2-3 things and end up flashing daily update zips.
Ian B
Click to expand...
Click to collapse
I've never had issues from just rooting. Rooting a phone doesn't cause issues but rather installing root apps and changing things causes issues. I would try to flash back to stock (backup data first) and then root it again to see of that fixes it.
Also did you use CF-Autoroot or one of the tool kits?
I fixed the issue, after that battery died I let it charge for about 4 hours with the quick charger and then reset the battery stats by using an app that deletes the batterystats.bin file. Then did a reboot and now the battery level is no longer stuck on 100%.
Same happened to me, phone is on for over 20hrs and battery is still 100%.
Waiting for it to shut off.
lifeisfun said:
Same happened to me, phone is on for over 20hrs and battery is still 100%.
Waiting for it to shut off.
Click to expand...
Click to collapse
You can also try the bootloader trick, though not sure if it will work here.
Boot to bootloader, change to logs menu. Hold power until reboot.
FYI, batterystats is not related to what % battery shows is left.
Mr Ian B said:
This is why I stopped rooting phones. One feature breaks 2-3 things and end up flashing daily update zips.
Ian B
Click to expand...
Click to collapse
root has nothing to do with breaking your phone. all root does is give you superuser permission. what breaks phones are dirty hacks that you yourself chose to use.
danarama said:
You can also try the bootloader trick, though not sure if it will work here.
Boot to bootloader, change to logs menu. Hold power until reboot.
FYI, batterystats is not related to what % battery shows is left.
Click to expand...
Click to collapse
I'm shocked, that worked fine!
THANKS!
Is there explanation for this happening?
lifeisfun said:
I'm shocked, that worked fine!
THANKS!
Is there explanation for this happening?
Click to expand...
Click to collapse
I would just put it down to "OS Confusion "
danarama said:
I would just put it down to "OS Confusion "
Click to expand...
Click to collapse
But that's strange, since it reported 100% in TWRP as well, looks more like firmware problem no?
lifeisfun said:
But that's strange, since it reported 100% in TWRP as well, looks more like firmware problem no?
Click to expand...
Click to collapse
Yeah maybe battery firmware confusion. I don't know where TWRP gets its reading from.
Still Works!
danarama said:
You can also try the bootloader trick, though not sure if it will work here.
Boot to bootloader, change to logs menu. Hold power until reboot.
FYI, batterystats is not related to what % battery shows is left.
Click to expand...
Click to collapse
Thanks.
So it seems like since i updated everything to 5.1 (radio etc) ive been having issues with my phone hot rebooting and also losing data. Ill have lte for hours and then all of a sudden i still have full bars but there is a "!" instead of 3G or LTE. Currently im on Temaseks latest nightly but it was happening on chroma also. My Baseband says "MDM9625_104446.01.02.95R". Any idea what could be causing this? (Im also not flashing anything crazy when I flash these roms. I flashed Temaseks nightly about 2 hours ago with the recommended banks gapps, and I just got a hotboot and lost datasignal).
HaiKaiDo said:
So it seems like since i updated everything to 5.1 (radio etc) ive been having issues with my phone hot rebooting and also losing data. Ill have lte for hours and then all of a sudden i still have full bars but there is a "!" instead of 3G or LTE. Currently im on Temaseks latest nightly but it was happening on chroma also. My Baseband says "MDM9625_104446.01.02.95R". Any idea what could be causing this? (Im also not flashing anything crazy when I flash these roms. I flashed Temaseks nightly about 2 hours ago with the recommended banks gapps, and I just got a hotboot and lost datasignal).
Click to expand...
Click to collapse
Did you clear cache? Clean flash or dirty?
Evolution_Freak said:
Did you clear cache? Clean flash or dirty?
Click to expand...
Click to collapse
Hey There. I'm a fan of never dirty flashing. I always wipe a few times before I flash anything. I dont do any type of titanium backup or anything either. I even deleted everything on my storage except for the TWRP backup folder and my roms folder so theres nothing weird left behind. Other than the baseband there was nothing else I needed to flash right?
HaiKaiDo said:
Hey There. I'm a fan of never dirty flashing. I always wipe a few times before I flash anything. I dont do any type of titanium backup or anything either. I even deleted everything on my storage except for the TWRP backup folder and my roms folder so theres nothing weird left behind. Other than the baseband there was nothing else I needed to flash right?
Click to expand...
Click to collapse
Thanks for clarifying that for me. No, I don't think you've missed anything. Before trying anything too drastic, I'd suggest flashing the factory image, if you can, and see if it continues to happen. I know that can be a hassle but it also could fix whatever might be broken.
Evolution_Freak said:
Thanks for clarifying that for me. No, I don't think you've missed anything. Before trying anything too drastic, I'd suggest flashing the factory image, if you can, and see if it continues to happen. I know that can be a hassle but it also could fix whatever might be broken.
Click to expand...
Click to collapse
hmm ill give it a try. Seemslike googles dev site is having problems at the moment and the download is going really slow...of course heh. ill report back when im on stock.
HaiKaiDo said:
So it seems like since i updated everything to 5.1 (radio etc) ive been having issues with my phone hot rebooting and also losing data. Ill have lte for hours and then all of a sudden i still have full bars but there is a "!" instead of 3G or LTE. Currently im on Temaseks latest nightly but it was happening on chroma also. My Baseband says "MDM9625_104446.01.02.95R". Any idea what could be causing this? (Im also not flashing anything crazy when I flash these roms. I flashed Temaseks nightly about 2 hours ago with the recommended banks gapps, and I just got a hotboot and lost datasignal).
Click to expand...
Click to collapse
adjust your voltages so that its best for your device. raise or lower your voltages until the reboots stop.
simms22 said:
adjust your voltages so that its best for your device. raise or lower your voltages until the reboots stop.
Click to expand...
Click to collapse
Wouldnt that mean theres something wrong with my phone? I havnt messed (and really dont ever) mess with OC or Voltages.
HaiKaiDo said:
Wouldnt that mean theres something wrong with my phone? I havnt messed (and really dont ever) mess with OC or Voltages.
Click to expand...
Click to collapse
no. the nexus 6 has 15 different pvc bin numbers. that means 15 different voltage charts to follow, depending on your devices bin number. and for each bin number, each individual device will vary. so, it might be alright, but most likely you would have to adjust slightly for best voltage for your personal device.
Evolution_Freak said:
Thanks for clarifying that for me. No, I don't think you've missed anything. Before trying anything too drastic, I'd suggest flashing the factory image, if you can, and see if it continues to happen. I know that can be a hassle but it also could fix whatever might be broken.
Click to expand...
Click to collapse
+1! Fastboot factory image. That's what I'd do. :thumbup:
Hi, I bought a s5 g900a from at&t with android 5.0 about 6 months ago in USA (i am from argentina). Everything was fine untill one day it started rebooting, not in loop, first once a day, then 3 or 4 for times a day, and finally almost every time I opened an app it got reboot.
First of all I want to say that I never installed any 3er party app or any rom, I just had the most common apps like fb, tw, instagram, etc. So I decided to do a factory reset thinking that would fix the problem, but It didnt, after factory and cache reset I used the phone for about 5 minutos and rebooted...
So, second attempt, I looked in sammobile for offcial roms and found v5.01... installed it with odin, no luck, still rebooting...
3er attempt, new rom, now v5.1.1, same problem, it worked almost a day fine and then it started rebooting. Right now my phone is completely useless, it keeps rebooting very often. When I installed the roms I had some problems, I got de "custom" message in the samsung screen, and some others, but I could fix them. My phone is now with android 5.1.1 but not working. Any ideas??? anything else I can try? can it be a hardware problem?
Thanks a lot for your help, and sorry for my lousy english
I notice you say that you got a 5.01 lollipop update from sammobile for the att sm-g900a. Could it be you have mistaken the device I'd and flashed another firmware not compatible with your device. Also sammobile does not have a firmware file other than the 4.4.2 for the att variant. Yet if you did flashed an incompatible firmware and managed to get it to boot, it would mean we might just have a way to switch firmwares. As for your random reboots it might be your phone has some sort of malfunction. Try the guides posted here on the forums restoring your device to 5.1.1 att official firmware. Also please post the exact files you used from sammobile for flashing your device.
Sent from my SAMSUNG-SM-G900A using Tapatalk
evildeaddc said:
I notice you say that you got a 5.01 lollipop update from sammobile for the att sm-g900a. Could it be you have mistaken the device I'd and flashed another firmware not compatible with your device. Also sammobile does not have a firmware file other than the 4.4.2 for the att variant. Yet if you did flashed an incompatible firmware and managed to get it to boot, it would mean we might just have a way to switch firmwares. As for your random reboots it might be your phone has some sort of malfunction. Try the guides posted here on the forums restoring your device to 5.1.1 att official firmware. Also please post the exact files you used from sammobile for flashing your device.
Sent from my SAMSUNG-SM-G900A using Tapatalk
Click to expand...
Click to collapse
You are right, I didnt get the roms from sammobile, only the 4.4.2 to try a downgrade, but didnt work, I dont remember where I got the other files, but they are suppose to be at&t version.
Right now I have installed android 5.1.1, I installed it through odin with the file G900AUCU4COI5. The phone works for a while and then reboots. Now it doesnt have any app installed, its clean and it is still working bad, It also gets too hot and sometimes before freeze it makes a very wear noise!
Yeah it seems the most logical explanation here would be the hardware going bad. As that would explain the device becoming hot from no usage. Try using another battery and taking the SD and Sim card off to se if it becomes stable, other than that you might need to have it repaired.
Sent from my SAMSUNG-SM-G900A using Tapatalk
evildeaddc said:
Yeah it seems the most logical explanation here would be the hardware going bad. As that would explain the device becoming hot from no usage. Try using another battery and taking the SD and Sim card off to se if it becomes stable, other than that you might need to have it repaired.
Sent from my SAMSUNG-SM-G900A using Tapatalk
Click to expand...
Click to collapse
I already changed the battery and the phone is with no sim and no SD, but still not working. I guess the only explanation is that it is a hardware problem.
Basically, I had to do a battery pull on my LG D415, after the better pull, I booted up the device like I normally would. After starting the device, I am now experiencing an issue where I am unable to get past the CM13 boot logo, where it will continue the booting animation with the CM13 logo, and then the device will just shut down. Attached is a video of this happening.
Is this essentially the inevitable bootloop that is found in many Android devices? If so, how can I go about fixing the issue? I had a lot of stuff on the device and would prefer to not have to reflash anything, as I spent already hours setting up the device in the first place.
Here is the video: https://www.youtube.com/watch?v=1kgh-DFxKBg&feature=youtu.be
darkgiant said:
Basically, I had to do a battery pull on my LG D415, after the better pull, I booted up the device like I normally would. After starting the device, I am now experiencing an issue where I am unable to get past the CM13 boot logo, where it will continue the booting animation with the CM13 logo, and then the device will just shut down. Attached is a video of this happening.
Is this essentially the inevitable bootloop that is found in many Android devices? If so, how can I go about fixing the issue? I had a lot of stuff on the device and would prefer to not have to reflash anything, as I spent already hours setting up the device in the first place.
Here is the video:
&feature=youtu.be
Click to expand...
Click to collapse
Usually a bootloop restarts your phone or doesn't pass the CM (in this case) logo.. I think u can classify as bootloop nevertheless.. u can try reflashing the same version of cm13 on top of that.. you maybe won't loose anything important but I don't know what you had done in your device.. it's just my opinion..
Warimation said:
Usually a bootloop restarts your phone or doesn't pass the CM (in this case) logo.. I think u can classify as bootloop nevertheless.. u can try reflashing the same version of cm13 on top of that.. you maybe won't loose anything important but I don't know what you had done in your device.. it's just my opinion..
Click to expand...
Click to collapse
So if I were to flash CM13 (without wiping anything) I should be safe in terms of not wiping anything? Would I also need to flash GAPPS again?
darkgiant said:
So if I were to flash CM13 (without wiping anything) I should be safe in terms of not wiping anything? Would I also need to flash GAPPS again?
Click to expand...
Click to collapse
I don't know.. again it's your decision.. but if your going to flash, try 1st without Gapps.. if they don't stay then flash Gapps.. btw I saw u want to download cm13.. that's a bummer because cyanogen is over.. they closed CyanogenMod OS. So no more cm's for anyone. Instead u have lineage OS that's made by CM team and we don't have official. It's the same with changed brand.. I don't know if you will succeed downloading a cm13 version but search here in L90 forums.. maybe you find a solution..
Warimation said:
I don't know.. again it's your decision.. but if your going to flash, try 1st without Gapps.. if they don't stay then flash Gapps.. btw I saw u want to download cm13.. that's a bummer because cyanogen is over.. they closed CyanogenMod OS. So no more cm's for anyone. Instead u have lineage OS that's made by CM team and we don't have official. It's the same with changed brand.. I don't know if you will succeed downloading a cm13 version but search here in L90 forums.. maybe you find a solution..
Click to expand...
Click to collapse
Oh yeah, I totally forgot that CyanogenMod closed down its OS. This is a huge bummer, as this essentially means I need to find a new ROM anyways...
Any suggestions? Anything super stable, and runs fast is what I was looking for. If not, I might just go back to the stock ROM and stay rooted or something.
darkgiant said:
Oh yeah, I totally forgot that CyanogenMod closed down its OS. This is a huge bummer, as this essentially means I need to find a new ROM anyways...
Any suggestions? Anything super stable, and runs fast is what I was looking for. If not, I might just go back to the stock ROM and stay rooted or something.
Click to expand...
Click to collapse
I'm currently using Aicp os. Its super fast and it's working good.. it's nougat so expect a better battery life but still have some bugs.. It's going to become official.
forum.xda-developers.com/lg-l90/development/rom-android-ice-cold-project-12-1-t3559656/page3
Warimation said:
I'm currently using Aicp os. Its super fast and it's working good.. it's nougat so expect a better battery life but still have some bugs.. It's going to become official.
forum.xda-developers.com/lg-l90/development/rom-android-ice-cold-project-12-1-t3559656/page3
Click to expand...
Click to collapse
Thanks for the advice, I'll go ahead and take a look at it! As long as it's stable, and good to use as a daily driver, it works for me.
Though, I am currently having an issue with booting into TWRP to flash the ROMs, as I keep trying the volume up + power button steps to get into recovery, but it's just sending me directly to the CM13 loading logo. And because I can't even get into CM13 because of the boot issue, I am not sure if I can connect the device to a computer... Any advice on how I can fix this issue?
darkgiant said:
Thanks for the advice, I'll go ahead and take a look at it! As long as it's stable, and good to use as a daily driver, it works for me.
Though, I am currently having an issue with booting into TWRP to flash the ROMs, as I keep trying the volume up + power button steps to get into recovery, but it's just sending me directly to the CM13 loading logo. And because I can't even get into CM13 because of the boot issue, I am not sure if I can connect the device to a computer... Any advice on how I can fix this issue?
Click to expand...
Click to collapse
Its power button and volume down.. I read that ur going to give your L90 To another person.. I think u should not flash nougat Roms yet.. they are still "beta ish" Roms.. Instead try this https://www.androidfilehost.com/?fid=673368273298925163
Its a unofficial build of lineage 13 made by @slimshadys and is basically cm13 last nightly made.. should be very stable.. doesn't bring root by default but just flash SuperSU 2.79 (last version I think) and will work ok
Warimation said:
Its power button and volume down.. I read that ur going to give your L90 To another person.. I think u should not flash nougat Roms yet.. they are still "beta ish" Roms.. Instead try this https://www.androidfilehost.com/?fid=673368273298925163
Its a unofficial build of lineage 13 made by @slimshadys and is basically cm13 last nightly made.. should be very stable.. doesn't bring root by default but just flash SuperSU 2.79 (last version I think) and will work ok
Click to expand...
Click to collapse
Haha silly me, yes volume down + power did the trick. I always get confused with that because it seems to be different for many devices. Yeah as I posted in my other thread, this phone is meant for a friend who uses it daily, it sounds like that lineage 13 is pretty much fit for the task? Would it receive updates in the future? I am always open for trying other ROMS of course, as long as they are 100% working and have no issues/
darkgiant said:
Haha silly me, yes volume down + power did the trick. I always get confused with that because it seems to be different for many devices. Yeah as I posted in my other thread, this phone is meant for a friend who uses it daily, it sounds like that lineage 13 is pretty much fit for the task? Would it receive updates in the future? I am always open for trying other ROMS of course, as long as they are 100% working and have no issues/
Click to expand...
Click to collapse
As it is now lineage 13 is the best option for stable.. But dont expect updates on 13.. Later you can use 14.1 but now it have some issues..
Warimation said:
As it is now lineage 13 is the best option for stable.. But dont expect updates on 13.. Later you can use 14.1 but now it have some issues..
Click to expand...
Click to collapse
Oh okay, thanks! I'll go ahead and just do a fresh install since I forgot this phone has an SD card, so the majority of the data needed is already there. Thanks for your help! I'll keep looking at 14.1 and rest of the Nougat ROMs, and consider flashing it if they become stable soon.
Warimation said:
Its power button and volume down.. I read that ur going to give your L90 To another person.. I think u should not flash nougat Roms yet.. they are still "beta ish" Roms.. Instead try this https://www.androidfilehost.com/?fid=673368273298925163
Its a unofficial build of lineage 13 made by @slimshadys and is basically cm13 last nightly made.. should be very stable.. cumps
Click to expand...
Click to collapse
So I installed lineage OS, but for some reason can't provide root access to apps? Attached a screenshot, not sure why it's not allowing me to select apps, and only showing ADB...
EDIT: No idea how, but the SIM card reader stopped working... I tried flashing another ROM just to see if it was lineage, but it wasn't. The phone is still under warranty, but I assume if I send it back it'd have to be unrooted... any idea how I can go about that?
darkgiant said:
So I installed lineage OS, but for some reason can't provide root access to apps? Attached a screenshot, not sure why it's not allowing me to select apps, and only showing ADB...
EDIT: No idea how, but the SIM card reader stopped working... I tried flashing another ROM just to see if it was lineage, but it wasn't. The phone is still under warranty, but I assume if I send it back it'd have to be unrooted... any idea how I can go about that?
Click to expand...
Click to collapse
https://forum.xda-developers.com/lg-l90/general/guide-flash-stock-kdz-offline-lg-l90-t2803479
Do this and you have a warranty covered phone.
Warimation said:
https://forum.xda-developers.com/lg-l90/general/guide-flash-stock-kdz-offline-lg-l90-t2803479
Do this and you have a warranty covered phone.
Click to expand...
Click to collapse
Oh great, thanks! I used to have the old myTouch 4G, and unrooting that phone was such a pain, I nearly spent 6 full hours because of all the steps needed and it was so easy to mess up. This looks pretty straight forward. On the bright side, I now know once I get the phone back I can flash lineage OS and should be good to go.
darkgiant said:
Oh great, thanks! I used to have the old myTouch 4G, and unrooting that phone was such a pain, I nearly spent 6 full hours because of all the steps needed and it was so easy to mess up. This looks pretty straight forward. On the bright side, I now know once I get the phone back I can flash lineage OS and should be good to go.
Click to expand...
Click to collapse
Before you flash kdz maybe the problem was bootstack.. Dont really know if that was the problem because its supposed to work if you still have a KitKat bootstack installed but try changing that.. Just be carefull to choose the right one..
https://forum.xda-developers.com/lg-l90/development/bootstack-kk-l-l90-t3118632/page7