Hi,
if i am on CM9 and i want to restore a back up of a sense rom, will i then have to flash the corresponding fastboot.img again or will that be restored automatically?
/regards
Sent from my HTC One X using xda premium
Hapsnykel said:
Hi,
if i am on CM9 and i want to restore a back up of a sense rom, will i then have to flash the corresponding fastboot.img again or will that be restored automatically?
/regards
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
if you already have the backup then the answer is no..you do not need to flash the corresponding boot.img restored many times my custom rom which is based on sense and never needed to flash a boot.img
Wrong.
You need to flash the correct boot.img for the ROM you are using. It isn't flashed in a nandroid restore.
nobnut said:
Wrong.
You need to flash the correct boot.img for the ROM you are using. It isn't flashed in a nandroid restore.
Click to expand...
Click to collapse
then how comes i never had any problem then..flashed from Leedroid back to my old Ivysaur which i restored and did not needed to flash the boot.img
I don't know and don't really care
I didn't say it wouldn't work. I said that they should match. If the ROM chef provides a specific boot.img, you should use it... otherwise flash the stock boot.img.
Plus you have overlooked the part about nandroid being unable to flash a boot.img.
nobnut said:
I don't know and don't really care
I didn't say it wouldn't work. I said that they should match. If the ROM chef provides a specific boot.img, you should use it... otherwise flash the stock boot.img.
Click to expand...
Click to collapse
then the best thing for the OP is to try himself and he can tells us then. and always the happy delight that you are i see..and i go by what i know and tried. i restore my backup and never once had to flash a boot.img afterwards.
Those words make no sense. Maybe you could rearrange the order.
Anyway, I'm done here.
nobnut said:
Those words make no sense. Maybe you could rearrange the order.
Anyway, I'm done here.
Click to expand...
Click to collapse
Adios...Nice to see we have some happy campers here today
---------- Post added at 04:24 PM ---------- Previous post was at 04:20 PM ----------
and it is simple. he can restore his backup sense rom he has. now if he restores it and it does not bootloop then we have a winner. if he faces bootloops then he goes to thread of the rom he restored he gets the boot.img stick the phone in bootloader turn on the fastboot usb mode and flash the boot.img and job done. Nice to see we have some real happy people today here.
Tried restoring, ended up in loops - downloaded the corresponding boot.img and applied it through fastboot.
Thanks for your help.
Hapsnykel said:
Tried restoring, ended up in loops - downloaded the corresponding boot.img and applied it through fastboot.
Thanks for your help.
Click to expand...
Click to collapse
i must have a super smart phone honestly i restored a nandroid and did not had to restore the boot.img hence why i advised that in the start..anyways it was two ways and you sorted it...glad to have helped..not like some
Hapsnykel said:
Hi,
if i am on CM9 and i want to restore a back up of a sense rom, will i then have to flash the corresponding fastboot.img again or will that be restored automatically?
/regards
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Yes, you will need to. Unless you're S-OFF, recovery can't write to the boot partition. Which means when you restore your backup your boot.img won't be restored. And a Sense ROM with a cm9 kernel/ramdisk most definitely will not work. Your nandroid backup folder will contain a boot.img, you can just flash that via fastboot when you've restored the ROM.
Goku80 said:
then how comes i never had any problem then..flashed from Leedroid back to my old Ivysaur which i restored and did not needed to flash the boot.img
Click to expand...
Click to collapse
Because all of the Sense ROMs on here at the minute are all modifications of the same base, so unless the dev has done something drastic to their boot.img you shouldn't see too many problems using one with a different ROM (although you'll miss out on any tweaks specific to that ROM). So when you restored your Ivysaur, you've been using it with Leedroid's boot.img - potentially missing out on anything that Ivysaur has in the ramdisk which Leedroid doesn't, but that probably isn't enough to cause bootloops or other major issues. You need to manually restore the boot.img from the backup you made in order to use the ROM as it was intended.
Everyone happy?
nobnut said:
Those words make no sense. Maybe you could rearrange the order.
Anyway, I'm done here.
Click to expand...
Click to collapse
Did someone set fire to your Tampon? Cos' you seem a little grumpy..
Related
hello.
so, if I recently flashed a custom kernel (franco) by installing from .zip through cwm, and I wanted to restore the stock jb kernel,
do i just restore the boot.img on cwm or do i have to restore system.img (or any other image) as well?
thanks!
Only boot.img
Sent from my Galaxy Nexus using xda premium
zephiK said:
Only boot.img
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
thanks! i was just confused because there were other files in franco's .zip besides the boot.img and was wondering what those were for? do they change anything else?
or reflash your JB rom
maatae said:
thanks! i was just confused because there were other files in franco's .zip besides the boot.img and was wondering what those were for? do they change anything else?
Click to expand...
Click to collapse
they are apart of the modifications that franco did (such as the sdcard binary)
but +1 to what acloh said... best thing to do is just reflash the base ROM. if gapps are needed then flash gapps right after you flash the ROM as well.
zephiK said:
they are apart of the modifications that franco did (such as the sdcard binary)
but +1 to what acloh said... best thing to do is just reflash the base ROM. if gapps are needed then flash gapps right after you flash the ROM as well.
Click to expand...
Click to collapse
I see. Thanks! Stupid question...how do you reflash stock rom? I tried installing the original ota zip i used updating takju to jb but got a status 7 error. As of now I've just done a full restore of a cwm backup I did right before flashing Franco. Help?
maatae said:
I see. Thanks! Stupid question...how do you reflash stock rom? I tried installing the original ota zip i used updating takju to jb but got a status 7 error. As of now I've just done a full restore of a cwm backup I did right before flashing Franco. Help?
Click to expand...
Click to collapse
You should always look inside the kernel zip and see what files it's going to modify. Then back up those files before flashing it.
If you've restored your nandroid (pre-franco), then you should be good to go for the OTA (assuming you didn't change anything else...)
efrant said:
You should always look inside the kernel zip and see what files it's going to modify. Then back up those files before flashing it.
If you've restored your nandroid (pre-franco), then you should be good to go for the OTA (assuming you didn't change anything else...)
Click to expand...
Click to collapse
so even if I'm already on the version I want (4.1.1) after the restoration, I should still reinstall the takju4.0.4 ->4.1.1 OTA.zip?
Also, are there any recommended caches I should clear after changing kernels?
Thank you.
maatae said:
so even if I'm already on the version I want (4.1.1) after the restoration, I should still reinstall the takju4.0.4 ->4.1.1 OTA.zip?
Also, are there any recommended caches I should clear after changing kernels?
Thank you.
Click to expand...
Click to collapse
?? Not sure I understand. If you restored 4.1.1, then you obviously do not need any update.
No, you don't have to wipe any caches.
efrant said:
?? Not sure I understand. If you restored 4.1.1, then you obviously do not need any update.
No, you don't have to wipe any caches.
Click to expand...
Click to collapse
Ok, thank you. I guess my main question was whether or not I have to wipe caches in between kernel switches. Again, Thanks!
I have a few questions so be kind and help.
1.Im on stock kernel 2.6.3.9.4.
I want to now if that kernel is the latest stock kernel and is there a thread here where i can look if any new ones come out for europe. Because i couldnt find any.
2.Im on viper rom.
I have a nandriod backup of this rom and my stock rom.
I want to know can go back via rom manager or recovery to my stock rom to see if the stock rom got any new updates?
a)if yes,some say if i install this new update i will have to unlock my bootloader again?
b)does the new update also contain a new kernel or did it remain the same?
3.After im finished with the above problems can i go back to viper via restore or do i need to flash the boot.img first and then do a restore?
I have another question on the same topic (rather nooby question ^^)
If you restore a backup from CWM, will you have all the apps and launcher settings and in-app settings/content the way it was by then? Or is it just like going back to factory reset (the os is back to normal and the apps and setting are all lost)....?
Many thanks in advance, and in case you have solution to achieve the goal set in my first question, please share!!
_ice_man_ said:
I have a few questions so be kind and help.
1.Im on stock kernel 2.6.3.9.4.
I want to now if that kernel is the latest stock kernel and is there a thread here where i can look if any new ones come out for europe. Because i couldnt find any.
2.Im on viper rom.
I have a nandriod backup of this rom and my stock rom.
I want to know can go back via rom manager or recovery to my stock rom to see if the stock rom got any new updates?
a)if yes,some say if i install this new update i will have to unlock my bootloader again?
b)does the new update also contain a new kernel or did it remain the same?
3.After im finished with the above problems can i go back to viper via restore or do i need to flash the boot.img first and then do a restore?
Click to expand...
Click to collapse
1. That is the latest kernel you have there. There is a custom kernel from kholk which is 3.4. There is no real place to look for the update. You will immediately know when the new kernel arrives. The news will be all over the hox thread.
2. You can go back via recovery, but you'll need to install that boot.img in the backup folder first via fastboot. You'll first need to clear cache before flashing boot.img and then you can recover via recovery. It is in the backup and restore option in cwm.
2a) if there is a update, you won't need to worry about unlocking the bootloader again.
b) Might contain new kernel, depends on which update you were last. Probably not new kernel totally, but rather a few improvements.
Yes you can go back again. Just do the same procedure you did with number 1.
Sent from my HTC One X using xda premium
highjack42 said:
I have another question on the same topic (rather nooby question ^^)
If you restore a backup from CWM, will you have all the apps and launcher settings and in-app settings/content the way it was by then? Or is it just like going back to factory reset (the os is back to normal and the apps and setting are all lost)....?
Many thanks in advance, and in case you have solution to achieve the goal set in my first question, please share!!
Click to expand...
Click to collapse
You will have everything like it was when you backed up. Not sure if you'll get you're messages back or not. Settings and everything should be in together with the backup.
Sent from my HTC One X using xda premium
timlambo said:
1. That is the latest kernel you have there. There is a custom kernel from kholk which is 3.4. There is no real place to look for the update. You will immediately know when the new kernel arrives. The news will be all over the hox thread.
2. You can go back via recovery, but you'll need to install that boot.img in the backup folder first via fastboot. You'll first need to clear cache before flashing boot.img and then you can recover via recovery. It is in the backup and restore option in cwm.
2a) if there is a update, you won't need to worry about unlocking the bootloader again.
b) Might contain new kernel, depends on which update you were last. Probably not new kernel totally, but rather a few improvements.
Yes you can go back again. Just do the same procedure you did with number 1.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
How do i get a boot.img from my stock? i didnt have it in the first place. I just did a backup in recovery when i unlocked the bootloader. Do you mean i have to flash boot.img when i want to go back to viper rom?
_ice_man_ said:
How do i get a boot.img from my stock? i didnt have it in the first place. I just did a backup in recovery when i unlocked the bootloader. Do you mean i have to flash boot.img when i want to go back to viper rom?
Click to expand...
Click to collapse
It should be in your backup folder. Look under clockwork on you're SD card and then look at your first(earliest) backup date. Open that folder, there should be a zip file and in the zip should be a boot.img file.
Sent from my HTC One X using xda premium
My HOX is stuck on the HTC logo.
I tried to install the ICJ rom based on Android 4.2.1 and followed the instructions. But failed...
I can still get into the recovery and reflash. My own backup didn't change anything so I also tried to download a nandroid from:
http://forum.xda-developers.com/showthread.php?t=1975140
matching the information from this command.
$ ./fastboot.exe getvar version-main
version-main: 3.14.401.31
I have used 'fastboot flash boot boot.img' with the boot.img from whatever ROM/nandroid I tried to install. Both before and/or after the rom is flashed.
I have also tried to flash other roms like: CM10, CM10.1 and VipertX_2.6.0. I have tried with both CWM and TWRP.
The only thing I can think of that I have not tried is RUU, but those are hard to come by...
Anyone have any idea how to proceed with this? Or am I screwed?
Have you full wiped before flashing ROM?
Sent from my One X
Yes.
In CWM I did factory reset, wipe dalvik and format everything except sdcard. Everything I could find. Battery stats too.
Just in case I also copied everything from the sdcard and reformated that one too.
Just try another rom.
But do not forget to flash also the corresponded boot. Img.
Regards.
BLADE Team Member
Can you recommend a rom with a higher success rate in these situations?
I've already tried three roms, my own nandroid and a stock nandroid.
do you tried stock by revolution?
Not yet. Downloading now...
BTW, which one do I install? odexed or de-odexed?
your nandroid restore failed ? did you flash the boot.img from the nandroid ? i recommend flashing the boot.img from original rom.zip
EDIT: Your phone might be affected by the read-only partition problem, caused by one of Trip's kernel/rom.
Yes, my nandroid failed. No error message, just stuck at boot logo when I reboot.
And yes, I always extract the boot.img from the rom/nandroid I want to install and use fastboot to flash it.
I've seen different suggestions on when to use fastboot. Some say before and some say after the installation of the rom. I've tried both variants with no luck...
I never downloaded Trips ROM. The download links were already removed when I started to look for roms.
How do I check if I have that problem? Shouldn't I have seen some read only error message in that case?
what i meant you shouldn't use boot.img from nandroid backups(they dont work for some reason), only use from rom.zip
Edit: they dont work for me (stock sense roms)
Vcek said:
what i meant you shouldn't use boot.img from nandroid backups(they dont work for some reason), only use from rom.zip
Edit: they dont work for me (stock sense roms)
Click to expand...
Click to collapse
Good to know. Thanks!
I just assumed I needed to do it the same way for the nandroids. Strangely enough i did'n use fastboot the first time I tried to restore from nandroid. That time it also failed....
WOW!! Something happened!
Thanks Sensitivity! You made my day! After flashing the stock rom you referred to my HOX came to life again!
Thanks everyone for your help!!:laugh::laugh:
Hi All,
Yesterday I took my Tegra 3 (International) One X back to Stock ICS using RUU. Everything went smoothly after I relocked my bootloader and ran the RUU.
Then I proceeded to get all the OTA updates until I had JellyBean (3.14.707.24) with no further updates pending. Yay for Jellybean! The next thing I did was install CWM recovery and perform a nandroid backup (which didn't seem to restore later, although was created correctly).
At this point, I thought I would try using a CM10 rom to remove sense and I went ahead and installed it, flashing over the boot.img as one normally would, but it wouldn't boot. I later discovered that I needed a modded-boot.img (for new hboot 1.36), but not before I tried running the 3.14.707.24 RUU.
This RUU got stuck at sending.... and did not finish. I didn't leave it more than 20 minutes and tried twice. I also tried my ICS RUU to no avail.
Right now I have no Rom installed (from what I can tell), but I have full fastboot access and would like to know how I should proceed:
1) should I install the CM10 rom again with proper modded-boot.img (for hboot 1.36) and see if it boots? That would at least get me functional.
2) should I try another copy of the RUU for 3.14.707.24 JB? (i found one)
3) should I try a rom like Android Revolution HD which is OK to work with my new HBoot 1.36?
I don't want to do too much too fast since I know what I've done, and used to be really into this. The phone has been sitting a while since I upgraded my device and I'd like to get it working for travelling purposes. I'd be happy with a Stock Rom at this point...
Thanks for any willingness to help me
Adam
Ofcourse if you want CM flash the boot.img that is made for CM..And then flash .zip file..And ofcourse after flashing use
"fastboot erase cache"
Sometimes if you dont clear cache your phone won't boot..
Sent from my Endeavor
As you already said the old boot.img wont work with the new hboot. Just install cm10.1 as usually. Or any other JB Rom that is out there for the One X.
Sent from my HTC One X using xda app-developers app
Thanks for answering
big noob said:
Ofcourse if you want CM flash the boot.img that is made for CM..And then flash .zip file..And ofcourse after flashing use
"fastboot erase cache"
Sometimes if you dont clear cache your phone won't boot..
Sent from my Endeavor
Click to expand...
Click to collapse
Thank you very much for your response!
This brings me to a next question...
Marc199 said:
As you already said the old boot.img wont work with the new hboot. Just install cm10.1 as usually. Or any other JB Rom that is out there for the One X.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Thanks for your answer!! Now I'm curious if I want to use some other ROM, but without any system, how do I get the .zip file for the rom onto my SD card for flashing.
Should I use CWM recovery and enable usb storage, or is there another way?
Thanks again,
Adam
Correct, use the recovery
Yes just mount usb storage in CWM.
Sent from my ProBam by codexc @xda using xda app-developers app
Thanks!
Marc199 said:
Yes just mount usb storage in CWM.
Sent from my ProBam by codexc @xda using xda app-developers app
Click to expand...
Click to collapse
I'll try this later when I have the time. Thanks to everyone who responded. I was nervous I was on the bad road. Seems I'm in healthy shape, just lacking a rom.
Two more questions:
1) Can I still revert to stock? If so, how since RUU seems to get stuck at sending and not actually restore?
2) Any idea why when I tried to restore my stock nandroid backup just after installing CWM (which backed up successfully) it would restore but not boot (hung on One splash screen)? Should I have to wait a seriously long time for it to boot (I never used to have to?)
Thanks in advance!
Adam :angel:
THANKS!
Mr Hofs said:
Correct, use the recovery
Click to expand...
Click to collapse
Thanks so much. I'll see what happens and get back to the thread.
ALL GOOD!!
Thanks Everyone again. I'm Up and Running!
I think I was more freaked out by the RUU not working than just thinking that my phone is fine. Turned out CWM Recovery was still onboard so I just flashed a new rom using USB mounted storage. :good::good::good::cyclops:
adampollack said:
I'll try this later when I have the time. Thanks to everyone who responded. I was nervous I was on the bad road. Seems I'm in healthy shape, just lacking a rom.
Two more questions:
1) Can I still revert to stock? If so, how since RUU seems to get stuck at sending and not actually restore?
2) Any idea why when I tried to restore my stock nandroid backup just after installing CWM (which backed up successfully) it would restore but not boot (hung on One splash screen)? Should I have to wait a seriously long time for it to boot (I never used to have to?)
Thanks in advance!
Adam :angel:
Click to expand...
Click to collapse
1. You just need to find a RUU that will work..
2. Did you flash boot.img from sdcard/CWM/backup/ backup name folder?
Sent from my Endeavor
Hmmm....
big noob said:
1. You just need to find a RUU that will work..
2. Did you flash boot.img from sdcard/CWM/backup/ backup name folder?
Sent from my Endeavor
Click to expand...
Click to collapse
Hey, Thanks for responding!
1. I figured. Thanks for validating. :good:
2. I did not use the boot.img from the nandroid backup. I've never sent a separate boot.img when restoring from Nandroid. Is that something I need to do going forward/have been lucky not having to do until now? Perhaps the ICS builds of roms had a more similar boot.img?
Adam
Yes sir, always flash the corresponding boot.img file :thumbup:
Appreciate the help
Mr Hofs said:
Yes sir, always flash the corresponding boot.img file :thumbup:
Click to expand...
Click to collapse
:highfive:
Thanks! I'm just confused because I've literally NEVER had to do this and have flashed countless roms when I was on ICS builds.
Great tip :highfive::good::highfive:
Hi all. I just got a Verizon Htc One M7. I bought it used and it was already updated to 4.4.2 Kit kat and sense 5.5. I am new to rooting and unlocking and I am running into issues I am hoping someone can help me with. I successfully unlocked, rooted, and got S-off. A am trying to get a custom kernel on the phone so I can have tap to wake and swipe to wake. I installed TWRP recovery 2.7.0.0. Everything appears to be working I boot into bootloader mode and it say unlocked and s-off on top of the screen. I started recovery and it appears to be working fine. I created a backup and that works. So I tried 2 different kernels elementalx and elite lunar. Both appear to install fine but when I reboot the phone gets stuck in a boot loop on the HTC screen. I then have to go back into recovery and revert back to my saved backup. The phone will then boot up fine. Not sure if I'm doing something wrong or what. I am running the stock ROM. Any help will be greatly appreciated.
Forgive and help a noop!!!!
No one knows? I also just noticed that on the bootloader screen there is no numbers after OS. Which would appear to mean i have no OS. But the phone boots and operates just fine. Any suggestions? Thinking I should get it back to factory and start over and flash the NuSenseSIX rom. If anyone could please help me out here it would be greatly appreciated!!!! I attached a picture of what my bootloader screen looks like.
Reubster24 said:
No one knows? I also just noticed that on the bootloader screen there is no numbers after OS. Which would appear to mean i have no OS. But the phone boots and operates just fine. Any suggestions? Thinking I should get it back to factory and start over and flash the NuSenseSIX rom. If anyone could please help me out here it would be greatly appreciated!!!! I attached a picture of what my bootloader screen looks like.
Click to expand...
Click to collapse
it's the rom you are on, if you go back to stock build you will see the OS-build number correctly displayed. if you are on a custom rom, and its not built correctly, it will not display properly.
you dont need to worry about it. all the info in hboot is for diagnostic purpose and wont effect you in any way.
synisterwolf said:
it's the rom you are on, if you go back to stock build you will see the OS-build number correctly displayed. if you are on a custom rom, and its not built correctly, it will not display properly.
you dont need to worry about it. all the info in hboot is for diagnostic purpose and wont effect you in any way.
Click to expand...
Click to collapse
Ok I appreciate the response. I am still on the stock ROM. Just have it rooted, unlocked and s-off with twrp custom recovery installed. Any ideas as to why I'm not able to get it to boot after installing a custom kernel? Can I just try to flash the NuSenseSIX ROM in the phones current state or should I start over?
Reubster24 said:
Ok I appreciate the response. I am still on the stock ROM. Just have it rooted, unlocked and s-off with twrp custom recovery installed. Any ideas as to why I'm not able to get it to boot after installing a custom kernel? Can I just try to flash the NuSenseSIX ROM in the phones current state or should I start over?
Click to expand...
Click to collapse
if you would like to try NuSense i would make sure you have a good backup or do one before. you'll need to wipe system - data - cache - dalvik in twrp and then install the rom.
---------- Post added at 01:36 PM ---------- Previous post was at 01:29 PM ----------
After some discussion with fellow dev's, i think you havent flash the insecure boot.img that allows you to write to /system. this should stop the kernel bootlooping you.
ok, here we go.
Flash the attached zip in recovery.
wipe dalvik and cache (2x for good measure)
reboot the phone.
then try to flash a custom kernel and see if you boot loop. Let me know what happens. please have a working backup before trying any of this.
(credit to @buckmarble and @brymaster5000)
kernel source
synisterwolf said:
if you would like to try NuSense i would make sure you have a good backup or do one before. you'll need to wipe system - data - cache - dalvik in twrp and then install the rom.
---------- Post added at 01:36 PM ---------- Previous post was at 01:29 PM ----------
After some discussion with fellow dev's, i think you havent flash the insecure boot.img that allows you to write to /system. this should stop the kernel bootlooping you.
Click to expand...
Click to collapse
I have everything backed up google drive with titanium backup as well as backed up in TWRP. When I wipe it doesn't remove the TWRP backup right? I have not flashed any boot.img. I am new to this and don't really know what that is. How would I find the boot.img I need. I think I'll just move forward with the NuSense Rom. Can I just download the zip for the NuSense ROM then wipe and flash it using TWRP and I'm good to go or is there other stuff I need to do?
Reubster24 said:
I have everything backed up google drive with titanium backup as well as backed up in TWRP. When I wipe it doesn't remove the TWRP backup right? I have not flashed any boot.img. I am new to this and don't really know what that is. How would I find the boot.img I need. I think I'll just move forward with the NuSense Rom. Can I just download the zip for the NuSense ROM then wipe and flash it using TWRP and I'm good to go or is there other stuff I need to do?
Click to expand...
Click to collapse
the boot.img zip above will allow you to write to the /system part of the phone.
TWRP will not wipe your backup. that is stored in a location its not allowed to wipe unless you do a "factory reset"
flash the zip above first. let it boot then flash NuSense. I'm not to familiar with that rom so i cant for sure say it will have said insecure boot.img.
Ok I flashed that file and the phone boots up fine. But it has a weird N flashing at the top of the screen now. I'll try a kernel this evening and see what happens. Any idea what the N is? Attached a zipped video of what its doing.
Reubster24 said:
Ok I flashed that file and the phone boots up fine. But it has a weird N flashing at the top of the screen now. I'll try a kernel this evening and see what happens. Any idea what the N is? Attached a zipped video of what its doing.
Click to expand...
Click to collapse
That icon is for NFC. idk why its flashing but make sure its off if you dont use it.
its under settings.
synisterwolf said:
That icon is for NFC. idk why its flashing but make sure its off if you dont use it.
its under settings.
Click to expand...
Click to collapse
Ok. It is off in settings. Tried to turn it on and it won't let me. I'll flash a kernel later and see what happens and if it stops doing it. Is there another insecure boot.img I can try?
Reubster24 said:
Ok. It is off in settings. Tried to turn it on and it won't let me. I'll flash a kernel later and see what happens and if it stops doing it. Is there another insecure boot.img I can try?
Click to expand...
Click to collapse
only need to do it once. flash any kernel that is meant for your rom or switch roms. you should be good to go.
synisterwolf said:
only need to do it once. flash any kernel that is meant for your rom or switch roms. you should be good to go.
Click to expand...
Click to collapse
Awesome thanks for all your help. I think I'm gonna flash a Rom. Any suggestions? I would like something close to the stock Rom.
Thank you for all your help!! I successfully installed the NuSense Rom.
Reubster24 said:
Thank you for all your help!! I successfully installed the NuSense Rom.
Click to expand...
Click to collapse
congrats man, you can PM me if you have anymore questions or post in the Q/A thread and i will try to help
:highfive: