[Q] Update with root - Moto X Q&A

Do i have to unroot to update or will it just remove root in the update process

You'll have to flash back to stock because the "recovery" that was installed with the root method won't allow you to flash the OTA. Flashing back to stock will remove root.

freak4dell said:
You'll have to flash back to stock because the "recovery" that was installed with the root method won't allow you to flash the OTA. Flashing back to stock will remove root.
Click to expand...
Click to collapse
Hey bro, I rooted with PawnMyMoto and after the 3rd boot the phone went to normal screen. Was it supposed to go straight to the recovery image. And when I go into fastboot I still can't get to the recovery screen. Any clues. I'm successfully rooted but things like using blacked out apps wont stick.
Sent from my XT1060 using Xparent Cyan Tapatalk 2

Bill Idol said:
Hey bro, I rooted with PawnMyMoto and after the 3rd boot the phone went to normal screen. Was it supposed to go straight to the recovery image. And when I go into fastboot I still can't get to the recovery screen. Any clues. I'm successfully rooted but things like using blacked out apps wont stick.
Sent from my XT1060 using Xparent Cyan Tapatalk 2
Click to expand...
Click to collapse
You can't get into recovery because PwnMyMoto hijacks the recovery and makes it load Android with system write privileges enabled rather than loading a normal recovery.
The apps are probably not sticking because they're not being permanently written to the system. They get deleted on the next bootup. In order to make them stick, you have to go into the bootloader and select recovery. This will boot Android, but this time, writing to the system will be allowed. Install whatever apps you need, then reboot the phone again to get back into Android without write privileges. The apps should stick now.

freak4dell said:
You can't get into recovery because PwnMyMoto hijacks the recovery and makes it load Android with system write privileges enabled rather than loading a normal recovery.
The apps are probably not sticking because they're not being permanently written to the system. They get deleted on the next bootup. In order to make them stick, you have to go into the bootloader and select recovery. This will boot Android, but this time, writing to the system will be allowed. Install whatever apps you need, then reboot the phone again to get back into Android without write privileges. The apps should stick now.
Click to expand...
Click to collapse
awsome, thanks brudda, that did it.
Sent from my XT1060 using Xparent Cyan Tapatalk 2

Related

CWM is available to flash through Rom Manager

Rom Manager was just updated to version 5.0.2.4 and allows you to flash to CWM 6.0.1.6 recovery. Booting to recovery just gives me the Android with a red flag though. Just a FYI till it gets sorted.
Pressing and holding the pwr button will boot you back to the OS. Not a huge deal as we don't have anything to flash at the moment.
If you need to get back to the stock recovery in the meantime which can be found in this thread
http://forum.xda-developers.com/showthread.php?t=1993331
Edit:
Don't Flash this yet, you'll have to re-install the stock recovery or wait for a fix and could possibly brick your phone if you don't know what you're doing.
Is there like an easy way to root other than manually adb pushing? Flashable zip maybe?
I get the same thing as you, says flash successful then the red flag.
F4M0U569 said:
Is there like an easy way to root other than manually adb pushing? Flashable zip maybe?
Click to expand...
Click to collapse
You can use the temporary "boot" method as opposed to "flash" when using the current CWM recovery which is posted here http://forum.xda-developers.com/showthread.php?t=1993331
Don't flash the recovery yet though, it's obviously not sorted. I used the adb method to root which worked fine. I got excited when I saw the new Rom Manager which allowed me to flash recovery because Koush's G+ messages earlier today.
kchino said:
You can use the temporary "boot" method as opposed to "flash" when using the current CWM recovery which is posted here http://forum.xda-developers.com/showthread.php?t=1993331
Don't flash the recovery yet though, it's obviously not sorted. I used the adb method to root which worked fine. I got excited when I saw the new Rom Manager which allowed me to flash recovery because Koush's G+ messages earlier today.
Click to expand...
Click to collapse
I tried using the adb boot method but it doesn't work for me. After booting the insecure boot and taking me to the Android screen, I tried using the codes listed there but it says no device found.
F4M0U569 said:
I tried using the adb boot method but it doesn't work for me. After booting the insecure boot and taking me to the Android screen, I tried using the codes listed there but it says no device found.
Click to expand...
Click to collapse
i did it last night and it was quite late, but if i remember correctly i had the same problem but just had to reselect USB debugging
Sent from my Nexus 7 using xda app-developers app

Recovery Bootloop (XT1053- Unlocked Bootloader)

Hey everyone,
Got myself into an interesting situation here. I have the GSM Unlocked Moto X (XT1053) and I'm using it on T-Mobile USA.
I have unlocked the bootloader, installed TWRP (twrp-2.6.3.1-ghost-4.4), SuperSU, Xposed all that jazz. Phone ran wonderfully until I saw the 4.4.2 update zip.
Downloaded the zip, put the phone into fastboot and attempted to flash the stock recovery. I had some trouble finding it and ended up using the one I found here. After doing this the phone started to bootloop, showing the ugly white "WARNING: BOOTLOADER UNLOCKED" screen and then nothing then looped. I put the phone back into fastboot and reflashed TWRP.
Now the phone just bootloops into TWRP. To attempt to remedy this I fixed permissions, wiped cache/Dalvik but to no effect. I can actually successfully boot into Android if I go into fastboot and select the "Factory" option in the menu, however I seem to have lost my service.
So looks like I broke a pretty big rule, don't flash until you know exactly what it was you had- but I got impatient and greedy and now I'm paying the price :victory:.
How can I repair the damage I've done? I don't mind losing data (currently making a backup in Android).
INFO RECAP
XT1053
rooted, bootloader unlocked 30.B2
twrp 2.6.3.1
http://forum.xda-developers.com/showthread.php?t=2477132
[TOOL] Moto X Toolkit v1.3.4 [Backup/Restore,Drivers,Return to stock,Root,Bootani] you could use this to flash back to stock and get a fresh start
Sent from my Nexus 7 using XDA Premium 4 mobile app
sounds like you flashed something that was not a recovery i would return to stock and then follow this guide
http://forum.xda-developers.com/showthread.php?t=2603358
thanks for the replies,
using the toolkit i have more or less fixed everything. however, my stock recovery is borked- it shows no options, just the android recovery background. i am currently downloading the entire firmware here and plan to extract the stock recovery.img to flash with fastboot.
hopefully this will trigger the ota and everything will be as usual from there on.
DarK_MischieF said:
thanks for the replies,
using the toolkit i have more or less fixed everything. however, my stock recovery is borked- it shows no options, just the android recovery background. i am currently downloading the entire firmware here and plan to extract the stock recovery.img to flash with fastboot.
hopefully this will trigger the ota and everything will be as usual from there on.
Click to expand...
Click to collapse
you can't trigger the OTA even if you are root and have a custom recovery you will still get the OTA you just wont be able to install it.
DarK_MischieF said:
thanks for the replies,
using the toolkit i have more or less fixed everything. however, my stock recovery is borked- it shows no options, just the android recovery background. i am currently downloading the entire firmware here and plan to extract the stock recovery.img to flash with fastboot.
hopefully this will trigger the ota and everything will be as usual from there on.
Click to expand...
Click to collapse
Check this video for booting stock recovery it's kinda tricky yours might not be borked http://www.youtube.com/watch?v=kjNXkRtEQlo&list=PL0V3YBytQ2FudO8sUC_EHgdMqUB_tVb8d
jmcdonald58 said:
Check this video for booting stock recovery it's kinda tricky yours might not be borked http://www.youtube.com/watch?v=kjNXkRtEQlo&list=PL0V3YBytQ2FudO8sUC_EHgdMqUB_tVb8d
Click to expand...
Click to collapse
Thanks for the video, you were correct, my recovery is working as intended. To actually activate the options in the stock recovery you need to hold the Volume up button and press the Power button.
4.4.2 sideloaded successfully, nothing noteworthy for my personal use- wasn't there mention of the Google dialer in a Canadian update release notes?
DarK_MischieF said:
Thanks for the video, you were correct, my recovery is working as intended. To actually activate the options in the stock recovery you need to hold the Volume up button and press the Power button.
4.4.2 sideloaded successfully, nothing noteworthy for my personal use- wasn't there mention of the Google dialer in a Canadian update release notes?
Click to expand...
Click to collapse
I am note sure I usually just use the search feature or google now when looking I have a Nexus 5 I rarely use the dialer but it is nice to have seems like it would be available

[Q] OTA Updates on Rooted XT1095 (Stock Recovery)

I recently followed this guide to root my XT1095. All I did was unlock my bootloader and boot the image...I did not (intentionally) alter my recovery, nor did I install a custom ROM. Will I still receive OTA update notifications and, if so, are they safe to apply?
Dan Again said:
I recently followed this guide to root my XT1095. All I did was unlock my bootloader and boot the image...I did not (intentionally) alter my recovery, nor did I install a custom ROM. Will I still receive OTA update notifications and, if so, are they safe to apply?
Click to expand...
Click to collapse
If you are running a custom recovery TWRP for example, I doubt that you will get OTA updates. I believe you need the stock recovery to be able to install OTA updates.
grneyez said:
If you are running a custom recovery TWRP for example, I doubt that you will get OTA updates. I believe you need the stock recovery to be able to install OTA updates.
Click to expand...
Click to collapse
I'm a little confused by your response. As I said in my original question, I did not (intentionally) alter my recovery. Did the method that I used achieve root alter my recovery for me?
If you did not install a custom recovery than you should be able to get OTA updates. Check to see what recovery you have.
Dan Again said:
I'm a little confused by your response. As I said in my original question, I did not (intentionally) alter my recovery. Did the method that I used achieve root alter my recovery for me?
Click to expand...
Click to collapse
As long as you don't make any changes to /system, you *should* be good to go for updates. If you didn't intentionally flash a custom recovery then you still have the stock one.
If you're rooted OTAs won't work. In KitKat and lower they just performed checksums on each file before updating, so the altered root files were left untouched and the update installed. In Lollipop and up (at least for Nexus devices), it does a total checksum and if /system has been altered in any way (including for root) OTA's won't install.
grneyez said:
If you did not install a custom recovery than you should be able to get OTA updates. Check to see what recovery you have.
Click to expand...
Click to collapse
Thanks for all the responses, guys. I booted into recovery and saw this, so I think my recovery is still stock. One quick question: when I boot into fastboot and select "Recovery", I get a dead Android and a "No Command" prompt - I had to follow these steps to actually get there. Why is that?
I'd like to try out Xposed now that it's available for my device, and I see that requires a custom recovery. If I install a custom recovery (TWRP, for instance) and use it to flash Xposed, can I then revert back to stock recovery and continue to receive OTA updates?
Dan Again said:
Thanks for all the responses, guys. I booted into recovery and saw this, so I think my recovery is still stock. One quick question: when I boot into fastboot and select "Recovery", I get a dead Android and a "No Command" prompt - I had to follow these steps to actually get there. Why is that?
I'd like to try out Xposed now that it's available for my device, and I see that requires a custom recovery. If I install a custom recovery (TWRP, for instance) and use it to flash Xposed, can I then revert back to stock recovery and continue to receive OTA updates?
Click to expand...
Click to collapse
If you modified your system with Xposed you won't be able to install OTA updates. Even if you return yo stock recovery.
To install an OTA you need three things. 1. Unaltered system, 2.no root and 3. stock recovery
juliospinoza said:
If you modified your system with Xposed you won't be able to install OTA updates. Even if you return yo stock recovery.
To install an OTA you need three things. 1. Unaltered system, 2.no root and 3. stock recovery
Click to expand...
Click to collapse
Fair enough. So let's say that I install a custom recovery and then Xposed. Will there be a way that I can manually upgrade to new stock OS versions as they come out for my phone?
Dan Again said:
Fair enough. So let's say that I install a custom recovery and then Xposed. Will there be a way that I can manually upgrade to new stock OS versions as they come out for my phone?
Click to expand...
Click to collapse
You can always flash a ROM or custom ROM via fast boot, but you will loss all your settings, apps etc because you are flashing an entire new system... The OTA only patches
The only way back is to flash your stock ROM if you can get a hold of it.
floepie said:
The only way back is to flash your stock ROM if you can get a hold of it.
Click to expand...
Click to collapse
So, funny story - this weekend I accidentally wiped my OS and had to flash stock ROM to get back up and running. See: here. Good resource for others who might be looking for Moto X 2014 stock Lollipop firmware...definitely saved that on my computer
juliospinoza said:
If you modified your system with Xposed you won't be able to install OTA updates. Even if you return yo stock recovery.
To install an OTA you need three things. 1. Unaltered system, 2.no root and 3. stock recovery
Click to expand...
Click to collapse
Isn't there any way to uninstall Xposed, revert back to original recovery and remove root--all in order to install OTA without completely loosing user data and apps installed?
yurkennis said:
Isn't there any way to uninstall Xposed, revert back to original recovery and remove root--all in order to install OTA without completely loosing user data and apps installed?
Click to expand...
Click to collapse
yes
just flash via fastboot
1. recovery (stock)
2. system
if your phone is 5.0 xt1095 and you didn't flash modems you should be able to receive OTA.
Repeat of Question
I'm not sure I completely understand what I need to do to get updated to 5.1. I have an XT1095 that I only rooted, no custom recovery. I downloaded the OTA for 5.1 last night and tried to update. Got an error and it did not update. A quick google search seems to state, as well as earlier in this thread, that I can not update if I am rooted. I would prefer not completely start over on my phone (wipe) and would like to just apply the update. Can I just "unroot" my phone and apply the update or do I have to go back to the beginning (with a stock recovery) before the update will take?
I know enough about all this to have followed the directions to accomplish the root about 7 months ago. Since then not played with any system files! The only reason I rooted was so I could use the full capabilities of Greenify. Any opinions on that would be appreciated as well. Thanks!
jhworth8 said:
I'm not sure I completely understand what I need to do to get updated to 5.1. I have an XT1095 that I only rooted, no custom recovery. I downloaded the OTA for 5.1 last night and tried to update. Got an error and it did not update. A quick google search seems to state, as well as earlier in this thread, that I can not update if I am rooted. I would prefer not completely start over on my phone (wipe) and would like to just apply the update. Can I just "unroot" my phone and apply the update or do I have to go back to the beginning (with a stock recovery) before the update will take?
I know enough about all this to have followed the directions to accomplish the root about 7 months ago. Since then not played with any system files! The only reason I rooted was so I could use the full capabilities of Greenify. Any opinions on that would be appreciated as well. Thanks!
Click to expand...
Click to collapse
Try reading, the post literally before yours tells you what to do, lol.
Sent from my XT1095 using Tapatalk
AGISCI said:
Try reading, the post literally before yours tells you what to do, lol.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
I take it that flashing the recovery and the system.img files to the phone will not erase all the apps, photos, music, etc.?
summit15 said:
I take it that flashing the recovery and the system.img files to the phone will not erase all the apps, photos, music, etc.?
Click to expand...
Click to collapse
Correct, it won't erase those things.
Sent from my XT1095 using Tapatalk
so if i am just rooted, and custom recovery, could I unroot (via supersu app) and flash stock recovery and be good to go? or am i missing something?
yamahakid said:
so if i am just rooted, and custom recovery, could I unroot (via supersu app) and flash stock recovery and be good to go? or am i missing something?
Click to expand...
Click to collapse
It's more difficult with Lollipop: updates now "look for" a completely stock unmodified unrooted system. So you'll have to flash a stock image of the current build and then take the OTA.

[Q] What am i missing?

I was rooted on stock 5.0 with SuperSU with Busybox, I removed both took the OTA but still getting 'no upgrade' to 5.1.
Im on version 22.21.11 vicatara_tmo.tmo.en.US
LEX22.46-11
So what am i missing?
on top of that, i cant get back into fastboot, when using Vol down + power button
i can get to adb reboot-bootloader
Duffmantp said:
I was rooted on stock 5.0 with SuperSU with Busybox, I removed both took the OTA but still getting 'no upgrade' to 5.1.
Im on version 22.21.11 vicatara_tmo.tmo.en.US
LEX22.46-11
So what am i missing?
Click to expand...
Click to collapse
Even though you removed those 2 things, there is something else that is modified in your system. It has to be 100% unmodified or it fails. The only way to fix that is to flash the 5.0 stock image which you can download here:
http://www.graffixnyc.com/motox.php
That will put you back to 100% stock, then you can take the update.
Sent from my XT1095 using Tapatalk
AGISCI said:
Even though you removed those 2 things, there is something else that is modified in your system. It has to be 100% unmodified or it fails. The only way to fix that is to flash the 5.0 stock image which you can download here:
http://www.graffixnyc.com/motox.php
That will put you back to 100% stock, then you can take the update.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
I download that then follow the guids in the general forums. but i cant boot into stock recovery (red triangle), probably make sense since i dont have a recovery loaded (TWRP). so i cant sideload Blur_Version.22.21.11
Twrp cannot load ota's! It has to be stock recovery.
Sent from my XT1095 using Tapatalk
AGISCI said:
Twrp cannot load ota's! It has to be stock recovery.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
i knew that, i was just a newb, on the dead driod with red triangle, i had to hold power button for 2-3 seconds then tap the vol up button to get into recovery, so i just add the zip via from the internal sd card. then i finally got to 5.1 update.
I dont know why, everytime i went into adb mode from recovery, where you do adb sideload. my phone always lost connection with computer and would apply the zip. hence, why i had to put it on internal storage to update.

Nexus 6 stuck on bootup

My nexus 6 is soft bricked I'm assuming, I can't get past the 6.0.1 boot up screen it just keeps on booting . The device is unlocked with TWRP recovery but not rooted as far as I know it's not rooted. The only way I can check MTP is through twrp but it's showing an exclmation point in device mgr. I'm in wugs toolkit now under Advanced Utilities, before I got the boot logo it had the you're device is corrupt. I fixed the corrupt message by putting my device in boot loader mode and in Advanced Utilities under fastboot flash then I clicked Boot [Kernel] I flashed the stock kernel and that got rid of the corrupt device warning screen. I'm gonna try flashing a modified boot img next but I'm having trouble. I just need someone to stick with me for awhile and help me fix this thing because I gotta return it and I don't have long.
Sent from my HTC6600LVW using Tapatalk
Ok now I have the corrupt device message back again.
Sent from my HTC6600LVW using Tapatalk
mwebb34 said:
My nexus 6 is soft bricked I'm assuming, I can't get past the 6.0.1 boot up screen it just keeps on booting . The device is unlocked with TWRP recovery but not rooted as far as I know it's not rooted. The only way I can check MTP is through twrp but it's showing an exclmation point in device mgr. I'm in wugs toolkit now under Advanced Utilities, before I got the boot logo it had the you're device is corrupt. I fixed the corrupt message by putting my device in boot loader mode and in Advanced Utilities under fastboot flash then I clicked Boot [Kernel] I flashed the stock kernel and that got rid of the corrupt device warning screen. I'm gonna try flashing a modified boot img next but I'm having trouble. I just need someone to stick with me for awhile and help me fix this thing because I gotta return it and I don't have long.
Sent from my HTC6600LVW using Tapatalk
Click to expand...
Click to collapse
If TWRP is installed there's no problem. Just a matter of the pc let recognize the device. Quit the toolkits though!
Do you have google drivers installed? Once they are installed your device should be recognized and you can copy any of the fine roms that can be found here.
Droidphilev said:
If TWRP is installed there's no problem. Just a matter of the pc let recognize the device. Quit the toolkits though!
Do you have google drivers installed? Once they are installed your device should be recognized and you can copy any of the fine roms that can be found here.
Click to expand...
Click to collapse
I need a lot of help installing the drivers.
Sent from my HTC6600LVW using Tapatalk
Like I said I now have the corrupt device message back instead of the 6.0.1 boot logo. I tried flashing the stock img file and the stupid corrupt screen came back. Ok I'm just craps out luck I guess,
Sent from my HTC6600LVW using Tapatalk
Ok I have what says is the latest Google usb drivers which was Aug 2015 downloaded. On my device I'm using I'm gonna transfers the drivers to my pc now, and attempt to install them. I hope this works and fixes my device. I sat in front of my pc yesterday for 7 hrs trying to fix this stupid phone.
Sent from my HTC6600LVW using Tapatalk
the corrupt device message is only there because you have twrp and a stock kernel. flash a custom kernel.
It's fixed, everything is running as it should no boot loops or corrupt screen, now I gotta check to see if recovery is gone. I used wugs to flash stock 6.0.1
Sent from my HTC6600LVW using Tapatalk
I used to have the corrupt message also, but it would go away and boot just fine. Started when I had TWRP. As someone mentioned, if this is a really annoyance, just flash a custom kernel . Though mine went away when I rooted with SuperSU (which patches the kernel I think)
Tower1972 said:
I used to have the corrupt message also, but it would go away and boot just fine. Started when I had TWRP. As someone mentioned, if this is a really annoyance, just flash a custom kernel . Though mine went away when I rooted with SuperSU (which patches the kernel I think)
Click to expand...
Click to collapse
I used wugs toolkit to flash back to complete stock it worked my device is running as normal, but when I power of the device and power it back on the corrupt message then disappears and boots right up. When I boot into boot loader mode and boot recovery it shows the green android robot laying down. After I flashed back to stock 6.0.1 it got rid of twrp and root but I'm still unlocked . The unlocked part I'm not worried about. In order to fix this do I have to 're root and flash twrp all over again or is there an easier way. I need step by step, on how to get rid of the corrupt message. Example, like when someone says flash img to me that's about as clear as mud.....
Sent from my HTC6600LVW using Tapatalk
mwebb34 said:
I used wugs toolkit to flash back to complete stock it worked my device is running as normal, but when I power of the device and power it back on the corrupt message then disappears and boots right up. When I boot into boot loader mode and boot recovery it shows the green android robot laying down. After I flashed back to stock 6.0.1 it got rid of twrp and root but I'm still unlocked . The unlocked part I'm not worried about. In order to fix this do I have to 're root and flash twrp all over again or is there an easier way. I need step by step, on how to get rid of the corrupt message. Example, like when someone says flash img to me that's about as clear as mud.....
Sent from my HTC6600LVW using Tapatalk
Click to expand...
Click to collapse
flash twrp then when you root, flash a custom kernel as well, that will get rid of the message.
Anybody here?
Sent from my HTC6600LVW using Tapatalk
mwebb34 said:
Anybody here?
Sent from my HTC6600LVW using Tapatalk
Click to expand...
Click to collapse
me. well not here, but in nyc. here in spirit though
simms22 said:
me. well not here, but in nyc. here in spirit though
Click to expand...
Click to collapse
I'm trying to get my brain working,lol my device is stock unrooted without twrp but the corrupt message still shows up I gotta get this fixxed. It's hard for me to understand what all I need to do. All I need is the corrupt message to go away and I'll be good. At start up it shows the corrupt message, but a few seconds later it goes away and it boots up normally.
Sent from my HTC6600LVW using Tapatalk
mwebb34 said:
I'm trying to get my brain working,lol my device is stock unrooted without twrp but the corrupt message still shows up I gotta get this fixxed. It's hard for me to understand what all I need to do. All I need is the corrupt message to go away and I'll be good. At start up it shows the corrupt message, but a few seconds later it goes away and it boots up normally.
Sent from my HTC6600LVW using Tapatalk
Click to expand...
Click to collapse
i believe that your bootloader is unlocked, thats why its showing up on a non rooted n6. you can lock your bootloader(i wouldnt, you can have problems later) or you can flash twrp recovery, then a custom kernel, and you dont need to root it for that.
simms22 said:
i believe that your bootloader is unlocked, thats why its showing up on a non rooted n6. you can lock your bootloader(i wouldnt, you can have problems later) or you can flash twrp recovery, then a custom kernel, and you dont need to root it for that.
Click to expand...
Click to collapse
If I flash the kernel with twrp it's gotta be a zip? Is there anyway that you can link me to stock 6.0.1 kernel
Sent from my HTC6600LVW using Tapatalk
mwebb34 said:
If I flash the kernel with twrp it's gotta be a zip? Is there anyway that you can link me to stock 6.0.1 kernel
Sent from my HTC6600LVW using Tapatalk
Click to expand...
Click to collapse
a stock twrp flashable, then theres no zip version of it available. BUT twrp can also flash .img kernels as well. if you have the factory image available, you can unzip it and just flash the boot.img in twrp(or fastboot). but why the stock kernel?? if you just want stock, id recommend just fastboot flashing the boot.img from the factory image. boot.img is the kernel.
simms22 said:
a stock twrp flashable, then theres no zip version of it available. BUT twrp can also flash .img kernels as well. if you have the factory image available, you can unzip it and just flash the boot.img in twrp(or fastboot). but why the stock kernel?? if you just want stock, id recommend just fastboot flashing the boot.img from the factory image. boot.img is the kernel.
Click to expand...
Click to collapse
I'm gonna try to find it. My device wouldn't boot at all if I didn't have a kernel would it?
Sent from my HTC6600LVW using Tapatalk
mwebb34 said:
I'm gonna try to find it. My device wouldn't boot at all if I didn't have a kernel would it?
Sent from my HTC6600LVW using Tapatalk
Click to expand...
Click to collapse
nope. the kernel is what connects the operating system(software) to the hardware and also serves as the devices main "brain"
---------- Post added at 05:10 PM ---------- Previous post was at 05:08 PM ----------
mwebb34 said:
I'm gonna try to find it. My device wouldn't boot at all if I didn't have a kernel would it?
Sent from my HTC6600LVW using Tapatalk
Click to expand...
Click to collapse
just download the factory image, then grab the boot.img out of it. link to the 6.0.1 factory image https://dl.google.com/dl/android/aosp/shamu-mmb29k-factory-9a76896b.tgz
simms22 said:
nope. the kernel is what connects the operating system(software) to the hardware and also serves as the devices main "brain"
Click to expand...
Click to collapse
Ok, with no twrp recover when I boot into boot loader mode and then boot into recovery mode what should I see come up on the screen?
Sent from my HTC6600LVW using Tapatalk

Categories

Resources