My device is a local re-branded and enhanced Xolo a500s/it's like a karbon a5 a think. After successfully updated my device via OTA and after my device rebooted. My screen started to flicker randomly. My phone is not rooted and im still using the official stock rom. I found a temporarily solution by doing a Factory Reset, the flickering would be gone but it will come back after my phone screen goes off and on. Anyway to fix this?
I suspect that the new lockscreen bloatware system app that comes with the update causes this, but hey I only suspect it and i'm new to the android community. I can't disable it(googled already, and the only way to freeze/remove it is to root.) I can't root my device for something like a hunch. I'm waiting for a software update that would fix my device's touchscreen collide bug.
Appreciate all of your thoughts.
Try to start your phone in Safe Mode or try to start in Recovery (if your phone has available) and do a Factory Reset
UltraWelfare said:
Try to start your phone in Safe Mode or try to start in Recovery (if your phone has available) and do a Factory Reset
Click to expand...
Click to collapse
Thanks for the reply, I really appreciate it. I was able to disable the bloatware new systapp lock the came with it and it didn't solve the problem. I will try your method. Again thank you very much. I will check in later to post the result, hopefully this fixes it all
*edit
I successfully managed to boot in safe mode, the flickering has stopped but it return right after the screen goes back from sleep. Then I do a factory reset then after that the phone starts up and the result is still the same.
I will try the recovery mode though.
*edit
okay, i've managed to enter recovery menu. the one where you use the volume buttons to move. Is it really safe to select Wipe Data/Factory Reset there? Is that what you're prompting me to do in your post?
drckml said:
Thanks for the reply, I really appreciate it. I was able to disable the bloatware new systapp lock the came with it and it didn't solve the problem. I will try your method. Again thank you very much. I will check in later to post the result, hopefully this fixes it all
*edit
I successfully managed to boot in safe mode, the flickering has stopped but it return right after the screen goes back from sleep. Then I do a factory reset then after that the phone starts up and the result is still the same.
I will try the recovery mode though.
Click to expand...
Click to collapse
Report back if something new happens
UltraWelfare said:
Report back if something new happens
Click to expand...
Click to collapse
The results are still the same... your method do work yes. The flickering is gone after rebooting but as soon as you know press the power button and screen goes off then press the power button again and the screen turns on again from standby, the flickering returns.
Before doing some OTA updates my device is like v7 or v8 and now it's v9.1
and I didn't have any screen flickering problems before updating to v9.1 so I can safely assure that it's not in the hardware. It really just happened right after updating my device.
Another question, will installing a custom rom fix this software bug? But I really don't want to install those yet at the moment.
Any, Thank you very much. I really really really really appreciate it all man. I'm really at loss now. This is my first android phone that's why.
drckml said:
The results are still the same... your method do work yes. The flickering is gone after rebooting but as soon as you know press the power button and screen goes off then press the power button again and the screen turns on again from standby, the flickering returns.
Before doing some OTA updates my device is like v7 or v8 and now it's v9.1
and I didn't have any screen flickering problems before updating to v9.1 so I can safely assure that it's not in the hardware. It really just happened right after updating my device.
Another question, will installing a custom rom fix this software bug? But I really don't want to install those yet at the moment.
Any, Thank you very much. I really really really really appreciate it all man. I'm really at loss now. This is my first android phone that's why.
Click to expand...
Click to collapse
First of all try factory data reset.Secondly if it doesn't work try a custom rom(if you really want to)and check if the bug has gone.If it doesn't then there is something fault with your device
UltraWelfare said:
First of all try factory data reset.Secondly if it doesn't work try a custom rom(if you really want to)and check if the bug has gone.If it doesn't then there is something fault with your device
Click to expand...
Click to collapse
So the only is custom rom/original stock rom before update(which is impossible because I haven't backed up one before updating)
is the only solution eh.
The reason that I held back from installing a custom rom is because I'm waiting for the touchscreen bug fix for my device iva OTA. Will I still able to get it after installing a custom rom?
Again many thanks. Is there a way to give you a thanks on every posts?
drckml said:
So the only is custom rom/original stock rom before update(which is impossible because I haven't backed up one before updating)
is the only solution eh.
The reason that I held back from installing a custom rom is because I'm waiting for the touchscreen bug fix for my device iva OTA. Will I still able to get it after installing a custom rom?
Again many thanks. Is there a way to give you a thanks on every posts?
Click to expand...
Click to collapse
If there is a way to restore back to your stock version or find a way to get back to stock version then yes .
If you had a Sony Device then you could restore it with SEUS.Now with a Xolo I really dont know.Ask to the specific device forum
UltraWelfare said:
If there is a way to restore back to your stock version or find a way to get back to stock version then yes .
If you had a Sony Device then you could restore it with SEUS.Now with a Xolo I really dont know.Ask to the specific device forum
Click to expand...
Click to collapse
Thanks a lot man. I've flashed a stock rom and my device got fixed from screen flickering. Really looks like a firmware bug. So I've just downgraded.
Again thanks a million
Related
Hi!
I have a huge problem. Sometimes the touchscreen is dont work, but its doesnt matter now. So i want to bring back i heard they fix it in warrantly.
But I rooted, run gingerbread rom, with changed kernel, and radio... so i dont want to break the warrantly (but i heard sometimes they dont care with this but its risky)
Today i started to reset the phone, i want to downgrade it but when i started to install the RUU it says: customer id error...
Whats the problem? please help i want to over the way as soon as possible
thanks.
Extract ROM.zip and try manual flashing using hboot.
tenke said:
Hi!
I have a huge problem. Sometimes the touchscreen is dont work, but its doesnt matter now. So i want to bring back i heard they fix it in warrantly.
But I rooted, run gingerbread rom, with changed kernel, and radio... so i dont want to break the warrantly (but i heard sometimes they dont care with this but its risky)
Today i started to reset the phone, i want to downgrade it but when i started to install the RUU it says: customer id error...
Whats the problem? please help i want to over the way as soon as possible
thanks.
Click to expand...
Click to collapse
Hi
Had the same problem when I installed cronos gingerbread with jumping screens and keyboard buttons not working , same thing happened when flashed other roms
It just unrooted by unstall the new official rom from the htc website.. updated it with the 2.1 ota and was good to go no more screen problems.
also try pressing down the screen a bit on the edges that helped as well
I have ADB installed so unrooting was a breeze
Have install Elelinux's gingerbread and is super smooth now
tfn said:
Hi
Had the same problem when I installed cronos gingerbread with jumping screens and keyboard buttons not working , same thing happened when flashed other roms
It just unrooted by unstall the new official rom from the htc website.. updated it with the 2.1 ota and was good to go no more screen problems.
also try pressing down the screen a bit on the edges that helped as well
I have ADB installed so unrooting was a breeze
Have install Elelinux's gingerbread and is super smooth now
Click to expand...
Click to collapse
"also try pressing down the screen a bit on the edges that helped as well" if it works, that means its a hardwer fault. i downloaded an untouched rom, with radio, flashed it, and i play with radiant, and another games, ,and facebook for two hour and no problem...
otherwise... Super one click works with hero? i have offical rom, and offical radio. i only have to unroot the device, and they dont realise it at the service.
edit: another interesting thing: after the touchscreen problem the touchscreen is stoped working, i restart the phone, and after when it starts the phone was felt my fingers from 3-4 centimeters! iam stunned! now the touchscreen is working correct with the original rom/radio
Solved
tenke said:
Hi!
I have a huge problem. Sometimes the touchscreen is dont work, but its doesnt matter now. So i want to bring back i heard they fix it in warrantly.
But I rooted, run gingerbread rom, with changed kernel, and radio... so i dont want to break the warrantly (but i heard sometimes they dont care with this but its risky)
Today i started to reset the phone, i want to downgrade it but when i started to install the RUU it says: customer id error...
Whats the problem? please help i want to over the way as soon as possible
thanks.
Click to expand...
Click to collapse
so i format my sd card with my computer (no quick format) and the problem is solved! thx all
Hellybean is by far the best ROM I've used yet on my Note. It runs almost perfectly. I did have to reboot because my bluetooth wouldn't come on (reboot always fixes that). However, when I rebooted it, the phone tried to restart, I saw the Samsung SGH-I717 screen, and then it went black. It never brings up the Hellybean ring of fire. If I pull the battery I see the ring of fire for about 5 seconds, then it reboots, then black screen.
At this point, the only thing I can do is force the phone into TWRP and restore a previous backup. Does anyone have any idea what could cause the phone to not want to reboot back into the system?
I was on the latest Hellybean build and TWRP is up-to-date as well. I had to revert back to the October 10 build though. I just tried rebooting it after a restore and the same thing happens (so it's not specific to a certain date of ROM). As long as I don't reboot I don't have a problem.
Thanks
Chris
MI_SS_IL said:
Hellybean is by far the best ROM I've used yet on my Note. It runs almost perfectly. I did have to reboot because my bluetooth wouldn't come on (reboot always fixes that). However, when I rebooted it, the phone tried to restart, I saw the Samsung SGH-I717 screen, and then it went black. It never brings up the Hellybean ring of fire. If I pull the battery I see the ring of fire for about 5 seconds, then it reboots, then black screen.
At this point, the only thing I can do is force the phone into TWRP and restore a previous backup. Does anyone have any idea what could cause the phone to not want to reboot back into the system?
I was on the latest Hellybean build and TWRP is up-to-date as well. I had to revert back to the October 10 build though. I just tried rebooting it after a restore and the same thing happens (so it's not specific to a certain date of ROM). As long as I don't reboot I don't have a problem.
Thanks
Chris
Click to expand...
Click to collapse
have you tried any other roms?
I have ran every update of Hellybean since its arrival here. I had made a backup and flashed another rom, didn't like so I went to install back up.
it would not install, just kept looping in the boot screen. had to fresh flash the rom. didn't matter which, just had to reflash. screen never went black though. you issue sounds more similar to a stuck power button, which is why I ask if you have had same problem with another rom.
I find it hard to believe this rom wont restore a back up. others have not chimed in with that specific issue. but you and I may just be 2 that have voiced the issue. wasn't that big of issue for me as I thought it more an oddity. my back up wouldn't install at all in 3 attempts, so again, whyi question your power button.
try another rom real quick if you can. don't have to like or want it, but this is a test right?
let us know what happens
captemo said:
have you tried any other roms?
I have ran every update of Hellybean since its arrival here. I had made a backup and flashed another rom, didn't like so I went to install back up.
it would not install, just kept looping in the boot screen. had to fresh flash the rom. didn't matter which, just had to reflash. screen never went black though. you issue sounds more similar to a stuck power button, which is why I ask if you have had same problem with another rom.
I find it hard to believe this rom wont restore a back up. others have not chimed in with that specific issue. but you and I may just be 2 that have voiced the issue. wasn't that big of issue for me as I thought it more an oddity. my back up wouldn't install at all in 3 attempts, so again, whyi question your power button.
try another rom real quick if you can. don't have to like or want it, but this is a test right?
let us know what happens
Click to expand...
Click to collapse
Let me clarify ... I'm not having a problem restoring or installing Hellybean or any other ROM. It's after I install or restore and the ROM is running fine (for days even) ... at some point I have to reboot for some reason and it's then that it won't boot back into the ROM. In other words I can't reboot my system because it never comes back to the ROM. I have to then boot to TWRP, restore something else and then that will boot to the ROM. If I reboot again after the ROM is up and running, I get the same thing, it won't boot back into the ROM, I have to restore again. That rules out a power button ... if it was stuck I would never get back in.
I've tried most of the ROMs out there, but since Hellybean I haven't tried any others (because this is the best one). You think there's any possibility dirty flashing all of the Hellybean builds over top of each other could cause it? Maybe I'll try installing the latest one from a full wipe.
Thanks
Chris
MI_SS_IL said:
Let me clarify ... I'm not having a problem restoring or installing Hellybean or any other ROM. It's after I install or restore and the ROM is running fine (for days even) ... at some point I have to reboot for some reason and it's then that it won't boot back into the ROM. In other words I can't reboot my system because it never comes back to the ROM. I have to then boot to TWRP, restore something else and then that will boot to the ROM. If I reboot again after the ROM is up and running, I get the same thing, it won't boot back into the ROM, I have to restore again. That rules out a power button ... if it was stuck I would never get back in.
I've tried most of the ROMs out there, but since Hellybean I haven't tried any others (because this is the best one). You think there's any possibility dirty flashing all of the Hellybean builds over top of each other could cause it? Maybe I'll try installing the latest one from a full wipe.
Thanks
Chris
Click to expand...
Click to collapse
I have dirty flashed every one. the only thing I try to do when gong dirty is to still give it that 10 settle time. no particular reason other than my OCD
Okay, thanks for the replies. I'll play around with it some more, maybe try a fresh install and see if that changes anything. I'll let you know if I figure it out.
Chris
I figured it out. Not Hellybean at all. It was TWRP. I reverted back to an early build and then reinstalled 2.6.3.0 and now it reboots fine.
Chris
I guess I can't edit the title to reflect the correct issue? Thread can be deleted if the moderators want. Hellybean is running strong ... it's the first ROM I get 0 random reboots.
Thanks for the help captemo and to the makers of Hellybean.
Chris
beanstalk
I got exactly same problem with beanstalk 4.3.
I tried reinstall recovery but no luck. Every time powering off or rebooting need a fully wipe and restore.
Do you think other or older recovery will work?
hotgly said:
I got exactly same problem with beanstalk 4.3.
I tried reinstall recovery but no luck. Every time powering off or rebooting need a fully wipe and restore.
Do you think other or older recovery will work?
Click to expand...
Click to collapse
Same issue. Any of the 4.3 ROMS.
MI_SS_IL said:
I figured it out. Not Hellybean at all. It was TWRP. I reverted back to an early build and then reinstalled 2.6.3.0 and now it reboots fine.
Chris
Click to expand...
Click to collapse
So did you:
1- restore a stable backup
2- boot to recovery and flash TWRP (which version?)
3- Boot back into recovery
3- wipe and flash HellyBean
Is this correct?
This is my first time posting for help so if I left something out please tell me and I will provide anything needed.
Problem :
My phone keeps randomly rebooting since I did a OTA update this morning. I have a Verizon S4 and the baseband 1545VRUFNG6. The reboot happens pretty much anytime I use the phone.
Is anyone else having this problem or is it just me?
- Kody
Kodman262 said:
This is my first time posting for help so if I left something out please tell me and I will provide anything needed.
Problem :
My phone keeps randomly rebooting since I did a OTA update this morning. I have a Verizon S4 and the baseband 1545VRUFNG6. The reboot happens pretty much anytime I use the phone.
Is anyone else having this problem or is it just me?
- Kody
Click to expand...
Click to collapse
I'm having the same problem. Hope there is a fix, this sucks.
Also having this problem. Going from NC5 to NG6 seems to have caused unexpected rebooting issues. Was your phone rooted by chance? My phone was rooted via Towelroot and had safestrap installed as the recovery bootloader. Now neither work.
Just trying to see if maybe there's some further similarities in the environments that cause the rebooting, more than just jfltevzw Galaxy S4.
Looking forward to finding a fix.
Jvstrange said:
Also having this problem. Going from NC5 to NG6 seems to have caused unexpected rebooting issues. Was your phone rooted by chance? My phone was rooted via Towelroot and had safestrap installed as the recovery bootloader. Now neither work.
Just trying to see if maybe there's some further similarities in the environments that cause the rebooting, more than just jfltevzw Galaxy S4.
Looking forward to finding a fix.
Click to expand...
Click to collapse
Also rooted with Towelroot, unable to reroot.
Jvstrange said:
Also having this problem. Going from NC5 to NG6 seems to have caused unexpected rebooting issues. Was your phone rooted by chance? My phone was rooted via Towelroot and had safestrap installed as the recovery bootloader. Now neither work.
Just trying to see if maybe there's some further similarities in the environments that cause the rebooting, more than just jfltevzw Galaxy S4.
Looking forward to finding a fix.
Click to expand...
Click to collapse
I was rooted as well. I used towelroot I believe as well. Root is gone as well.
Has anyone tried a factory reset? Did it fix the problem?
---------- Post added at 03:06 PM ---------- Previous post was at 03:00 PM ----------
Has anyone tried a factory reset? Did it fix the problem? I sent the Towelroot dev an email asking for a possible fix, will keep you posted.
Nacho2217 said:
Has anyone tried a factory reset? Did it fix the problem?
---------- Post added at 03:06 PM ---------- Previous post was at 03:00 PM ----------
Has anyone tried a factory reset? Did it fix the problem? I sent the Towelroot dev an email asking for a possible fix, will keep you posted.
Click to expand...
Click to collapse
I'm planning on doing a factory reset today to see if it doesn't fix it. Unfortunately, due to the randomness of the reboots, I may not necessarily know right away whether the issue is fixed. But if I can save a few others from having to factory reset, hooray
Jvstrange said:
I'm planning on doing a factory reset today to see if it doesn't fix it. Unfortunately, due to the randomness of the reboots, I may not necessarily know right away whether the issue is fixed. But if I can save a few others from having to factory reset, hooray
Click to expand...
Click to collapse
Please keep us posted if it works. I hate doing resets, especially for nothing, but if it works, then it is well worth it.
Nacho2217 said:
Please keep us posted if it works. I hate doing resets, especially for nothing, but if it works, then it is well worth it.
Click to expand...
Click to collapse
Alright, I've just finished the factory reset and reinstalled my apps from before. I have noticed that some of the other small bugs I was experiencing after the OTA update appear to be gone, however as the random reboots don't necessarily happen that often, I'll update again at the end of the day and consider it a success if the phone doesn't reboot at all during the rest of today. That leaves about 10 hours to see if there are any reboots.
Will keep you guys posted
I too am facing this issue. Phone was fine prior to this update.
ecksreturns said:
I too am facing this issue. Phone was fine prior to this update.
Click to expand...
Click to collapse
Did you also root your phone using towelroot? Everyone else in the thread so far had rooted their phone before the update, so this information will help others in the future determine if this thread is relevant to them or not
I had rooted it once before , but then had returned to stock. OTA received after going back to Stock.
I have the same issue. Never rooted the phone. I have not try master reset yet. Called verizon and was offered a replacement phone. They also told me that many people complain about this issue and the fix should be available in December. I am not sure how the replacement phone would solve the issue unless it has NC5 version.
Here is the cure!!!
To fix the problem... Turn phone off.....turn the phone on while holding the home, volume up, and the power button.... Release the power button once the phone vibrates, but continue holding the volume up and home until you reach the boot loader screen..... Use the volume rocker the highlight the wipe cache partition.....select it by using the power button......once it is finished highlight reboot system now.
amcasper said:
To fix the problem... Turn phone off.....turn the phone on while holding the home, volume up, and the power button.... Release the power button once the phone vibrates, but continue holding the volume up and home until you reach the boot loader screen..... Use the volume rocker the highlight the wipe cache partition.....select it by using the power button......once it is finished highlight reboot system now.
Click to expand...
Click to collapse
Thanks a lot for the hint. Hopefully it works. I just did cache wipe, will comment on performance.
Regards
Read here:
http://forum.xda-developers.com/showthread.php?t=2901463
I just cleared the Cache partition. I will report back tomorrow after a night of using it.
No such luck...
As stated in my post above, I cleared my Cache partition. However this did not fix the random reboot problem for me. I've found that it reboots sometimes when I listen to Pandora, but this is not the only time it reboots. It also tends to reboot during a call or right after as well. Is there some sort of error log that I can post from my phone to help better define what is going on?
It's been almost 24 hours since my factory reset and the phone hasn't rebooted at all. Of course, this could have potentially be solved by simply wiping the /cache partition instead of both data and cache. It's hard to say now that I've already done the factory reset.
Just got a refurbished phone yesterday with NC5 loaded on it. Made the mistake of taking the NG6 update. Phone started random reboots after the update. This was on a perfectly stock phone, never rooted. Think the problem must be with the NG6 update. I just rooted the NG6 and still getting random reboots. I'm going to try wiping cache and see if that works.
Problem occur in stock fw(3.2.4), Nexus 2.01 and even after rollback to .3.1.0
My HDX when lying on the table goes on and off every minute(clock resets to 0:00 after each reboot), but when I start to use it, it's working fine without auto reboot...
At first when I flashed Nexus everything was ok but then I was busy and haven't used my tab for few weeks and now I have this annoying problem.
Because of this battery goes low very fast.
Is this hardware or software problem?
Hope for your help.
Clock reset to 0.00 is normal with your Nexus Rom after reboot; when wifi is on while you reboot time setting is ok...
It has been fixed with 2.05
I would install and use stock for a day to try if the problems still are there...
(maybe 13.3.2.3, because after that you can install TWRP and a custom rom straight away...; but disable OTA or disable wifi while on stock, otherwise you will get an update)
Maybe a complete new installation (stock -> twrp -> custom rom) will fix it
futzmaster said:
Clock reset to 0.00 is normal with your Nexus Rom after reboot; when wifi is on while you reboot time setting is ok...
It has been fixed with 2.05
I would install and use stock for a day to try if the problems still are there...
(maybe 13.3.2.3, because after that you can install TWRP and a custom rom straight away...; but disable OTA or disable wifi while on stock, otherwise you will get an update)
Maybe a complete new installation (stock -> twrp -> custom rom) will fix it
Click to expand...
Click to collapse
I'm now on 13.3.2.3.2 and problem is still there... I get clock reset on stock fw not nexus, is this normal too?
I also did factory reset...
Long shot - try a forced shutdown via long press of power button. On rare occasions I have found this corrects device weirdness. Really should have the same effect as soft powering off but for some reason it seems to work. Worst case you've lost 2-3 min trying.
Also check if same behavior occurs while booted into recovery. If so almost certainly a hardware issue, possibly when CPUs throttle down or some other 'idle' state kicks in.
Davey126 said:
Long shot - try a forced shutdown via long press of power button. On rare occasions I have found this corrects device weirdness. Really should have the same effect as soft powering off but for some reason it seems to work. Worst case you've lost 2-3 min trying.
Also check if same behavior occurs while booted into recovery. If so almost certainly a hardware issue, possibly when CPUs throttle down or some other 'idle' state kicks in.
Click to expand...
Click to collapse
Did hardware reset, unfortunately without success...
What do you mean with "booted into recovery"? Fastboot or another fw slot with safestrap?
Flashed cm11 and still got this issue! I'm done...
I think you don't need to test custom roms yet...
Your goal should be to have a clean stock rom with no errors.... (no safestrap and stock custom recovery)
If you still have errors you need to contact amazon anyway i guess....
futzmaster said:
I think you don't need to test custom roms yet...
Your goal should be to have a clean stock rom with no errors.... (no safestrap and stock custom recovery)
If you still have errors you need to contact amazon anyway i guess....
Click to expand...
Click to collapse
alright, what's the steps to recover to clean stock from twrp with cm11?
Hey, guys. Searched around this forum for this topic but didn't see anything, apologize if it's a duplicate.
Basically my tablet has been freezing constantly since the nougat update. It wasn't happening all that often to begin with but over time it turned into something like once a day to a few times a day. It doesn't follow any usage patterns as far as I can tell (i.e. I use chrome mostly but if I'm on something like one of the regular google apps it might still happen). Once it freezes I have to force shutdown via power button. Every now and then it will freeze and restart itself without my having to force shutdown.
It's stock ROM, with virtually stock apps (dropbox is the only downloaded app). I read about some solutions which I've already tried, and so I wiped the cache, did a factory reset, have about 5gb free storage space, and the issues are still the same.
Any suggestions? Thanks
nickhx2 said:
Hey, guys. Searched around this forum for this topic but didn't see anything, apologize if it's a duplicate.
Basically my tablet has been freezing constantly since the nougat update. It wasn't happening all that often to begin with but over time it turned into something like once a day to a few times a day. It doesn't follow any usage patterns as far as I can tell (i.e. I use chrome mostly but if I'm on something like one of the regular google apps it might still happen). Once it freezes I have to force shutdown via power button. Every now and then it will freeze and restart itself without my having to force shutdown.
It's stock ROM, with virtually stock apps (dropbox is the only downloaded app). I read about some solutions which I've already tried, and so I wiped the cache, did a factory reset, have about 5gb free storage space, and the issues are still the same.
Any suggestions? Thanks
Click to expand...
Click to collapse
YAY!!! someone else!
Can you try something for me. Flash this kernel FIRE-ICE N K10.5.3 (K10.5.4 seems to be having problems ATM)
i think your problem will be fixed.... please let me know! :highfive:
Hi, thanks for replying. I absolutely can do that but I literally have no experience flashing kernels. I assume it's same as flashing a rom but If you could provide some instructions for me I'd appreciate that. It's been a long time since I've even done that and I'd want to make sure I don't screw anything up.
nickhx2 said:
Hi, thanks for replying. I absolutely can do that but I literally have no experience flashing kernels. I assume it's same as flashing a rom but If you could provide some instructions for me I'd appreciate that. It's been a long time since I've even done that and I'd want to make sure I don't screw anything up.
Click to expand...
Click to collapse
Simply... Flash TWRP
Flash kernel like any other ROM.
Reboot done!
ok, thanks. will let you know how it goes.
do i need necessarily need twrp to flash? or can i just use whatever recovery i currently have on there?
nickhx2 said:
ok, thanks. will let you know how it goes.
do i need necessarily need twrp to flash? or can i just use whatever recovery i currently have on there?
Click to expand...
Click to collapse
Yes TWRP
Question did you unlock your bootloader?
honestly i don't remember. some time ago my n9 got stuck in some weird bootloop. i had to run the RUU (i think that's what it was) to restore everything back to completely normal. so if me having to do that meant i unlocked the bootloader then yes i did. if not, then i wouldn't have done it.