Develop Bugs

[Q] Need help ASAP! CWM problem.

Hey guys, this is my first post on XDA forum.
So I've recently bought a nexus 7, I used wugfresh's root kit to root my nexus but then it didn't work... so I've tired the auto root by chainfire. Then I was able to get root. So then I went to playstore and downloaded rom manager to install CWM. I went to recovery then I get this message:
E : Cant mount /cache/recovery/log etc.....
I've tried everything I can do such as researching, changing recovery, and watching a youtube tutorial but nothing helped.
Thanks.

I would start over from scratch using fastboot to flash a factory image and stock recovery. If your bootloader isn't unlocked already, unlock it.

nhizzat said:
I would start over from scratch using fastboot to flash a factory image and stock recovery. If your bootloader isn't unlocked already, unlock it.
Click to expand...
Click to collapse
I tried to format using wugfresh couple times but still not working...

DO NOT USE TOOLKITS. They cause too many problems. Learn to do things the proper way using fastboot. I agree with the poster above, you should flash a factory image to start over. Download the system image from here- https://developers.google.com/android/nexus/images
You need to unlock your bootloader-
Code:
fastboot OEM unlock
Then run the flash_all.bat. That will automatically wipe and reflash everything to get you back to square one.
Then you need to flash TWRP (don't use CWM)
Code:
fastboot flash recovery recoveryname.img
TWRP will automatically prompt you to flash SU when you reboot. Choose yes, reboot, then install SuperSU from play store, update the SU binaries, reboot again, and then you're done.

_MetalHead_ said:
DO NOT USE TOOLKITS. They cause too many problems. Learn to do things the proper way using fastboot. I agree with the poster above, you should flash a factory image to start over. Download the system image from here- Link Removed
You need to unlock your bootloader-
Code:
fastboot OEM unlock
Then run the flash_all.bat. That will automatically wipe and reflash everything to get you back to square one.
Then you need to flash TWRP (don't use CWM)
Code:
fastboot flash recovery recoveryname.img
TWRP will automatically prompt you to flash SU when you reboot. Choose yes, reboot, then install SuperSU from play store, update the SU binaries, reboot again, and then you're done.
Click to expand...
Click to collapse
I tried to flash TWRP but its still the same error code

z3r0c311 said:
I tried to flash TWRP but its still the same error code
Click to expand...
Click to collapse
I highly advise you start from scratch so do what I told you to do in my last post. I promise if you do it the correct way (ie. without using toolkits) it will work.

_MetalHead_ said:
I highly advise you start from scratch so do what I told you to do in my last post. I promise if you do it the correct way (ie. without using toolkits) it will work.
Click to expand...
Click to collapse
It would be great if u could tell me the commands, im nubby with this fastboot thing.

z3r0c311 said:
It would be great if u could tell me the commands, im nubby with this fastboot thing.
Click to expand...
Click to collapse
I gave you the commands in my first post in this thread.
Here's a guide to get you started-
http://forum.xda-developers.com/showthread.php?t=2277112

Sorry for another nubby question but how do I get flash_all.bat?

z3r0c311 said:
Sorry for another nubby question but how do I get flash_all.bat?
Click to expand...
Click to collapse
It's in the file that you should have downloaded from the link I posted in my first post. The instructions are at that link as well.

_MetalHead_ said:
It's in the file that you should have downloaded from the link I posted in my first post. The instructions are at that link as well.
Click to expand...
Click to collapse
Hey I tried the following:
oem lock
oem unlock
flash-all/flash_all.bat
flash recovery(TWRP)
but then when I reboot into TWRP I don't get a message saying you to install SU... And when I go to 'Install' in TWRP I don't see any internal storage available(0mb). With this error I cant install any roms which is boring.

z3r0c311 said:
Hey I tried the following:
oem lock
oem unlock
flash-all/flash_all.bat
flash recovery(TWRP)
but then when I reboot into TWRP I don't get a message saying you to install SU... And when I go to 'Install' in TWRP I don't see any internal storage available(0mb). With this error I cant install any roms which is boring.
Click to expand...
Click to collapse
Hmm... Can you even boot into the stock ROM at this point? Try formatting /data (done in TWRP). Did the system image flash successfully?

_MetalHead_ said:
Hmm... Can you even boot into the stock ROM at this point? Try formatting /data (done in TWRP). Did the system image flash successfully?
Click to expand...
Click to collapse
I can boot into my stock rom which is 5.0.2, when I try to format /data the error codes comes out...

z3r0c311 said:
I can boot into my stock rom which is 5.0.2, when I try to format /data the error codes comes out...
Click to expand...
Click to collapse
Did the system image flash successfully?

_MetalHead_ said:
Did the system image flash successfully?
Click to expand...
Click to collapse
using flash-all command, yeah

z3r0c311 said:
using flash-all command, yeah
Click to expand...
Click to collapse
Well then I don't know what to tell you at this point. I know Lollipop has been causing issues for some N7 users, but I also know that wugs toolkit causes problems too so honestly I'm not sure what the root of your issue is. I think someone with more experience with Lollipop is gonna have to chime in here, I'm still on 4.4.4 on all of my devices. Sorry I couldn't be of more help.

_MetalHead_ said:
Well then I don't know what to tell you at this point. I know Lollipop has been causing issues for some N7 users, but I also know that wugs toolkit causes problems too so honestly I'm not sure what the root of your issue is. I think someone with more experience with Lollipop is gonna have to chime in here, I'm still on 4.4.4 on all of my devices. Sorry I couldn't be of more help.
Click to expand...
Click to collapse
Thanks for helping me I appreciate it. I hope someone else can help me with this problem... btw can I flash roms with the stock recovery? The stock recovery seems to be working fine...

z3r0c311 said:
Thanks for helping me I appreciate it. I hope someone else can help me with this problem... btw can I flash roms with the stock recovery? The stock recovery seems to be working fine...
Click to expand...
Click to collapse
No, you can only flash custom ROMs if you have a custom recovery.

[GUIDE] [HOWTO] Return to stock for Huawei Watch

Hi guys, since the development is started i think that we also need a way to restore the watch to the stock FW.
HOWTO:
- download from the following links the boot, recovery and system image;
- reboot to fastboot and:
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
and then go to recovery and do a wipe data / factory reset.
EDIT:
For some strange reason the system img flash didn't work properly on a device i could test. Here is the workaround:
1- First of all download the TWRP from the other thread and fastboot boot it:
Code:
fastboot boot TWRP2.8.7.0-Sturgeon.img
2 - Then push the system.img in the sdcard so:
Code:
adb push system.img /sdcard/
3 - Now flash it:
Code:
adb shell
dd if=/sdcard/system.img of=/dev/block/platform/msm_sdcc.1/by-name/system
4 - reboot
Link:
https://mega.nz/#!rgRQHRrb!lgQCvqH-qkuqitPRRXfCad29MdmJ6ynaUHJDr0hjeLM
https://mega.nz/#!ahgjxA4R!y8Hb0CBVBRwUr0tA3HeFrrqh0ALAiMyqJu0pLsBsAD8
https://mega.nz/#!2pYVBDpA!wQJT8LDcffk7uxEmrsqna6MKWIODD-FqBO_k4Poml7g

What would be really awesome is TWRP.

brizey said:
What would be really awesome is TWRP.
Click to expand...
Click to collapse
My build pc is broken and on my macbook i dont have enought free space to build the twrp.

brizey said:
What would be really awesome is TWRP.
Click to expand...
Click to collapse
ok i compiled from my daughter's pc.... pls test it http://forum.xda-developers.com/hua...overy-twrp-build-huawei-watch-tester-t3222675

Skin1980 said:
ok i compiled from my daughter's pc.... pls test it http://forum.xda-developers.com/hua...overy-twrp-build-huawei-watch-tester-t3222675
Click to expand...
Click to collapse
Will try to get to it today. I am booted up on your kernel now as a test (just fastboot booted it). Will do the same to test the recovery once I get a chance.
Edit: btw...when I have pulled images before, I had always done something like
cat /dev/mtd/mtd2 > /sdcard/boot.img (or wherever the boot image is mounted).
in an ADB shell. Do these things even have an sdcard location to temporarily store the images? Just curious on how you pulled them.

brizey said:
Will try to get to it today. I am booted up on your kernel now as a test (just fastboot booted it). Will do the same to test the recovery once I get a chance.
Click to expand...
Click to collapse
Nice, thank you

Updated OP

return from what?

Motawa88 said:
return from what?
Click to expand...
Click to collapse
Having su installed. When you install skin1980's kernel, it uses chainfire's autoroot method, which modifies your system partition. So to make sure OTAs work, this is a way to get back to a clean system image that will pass the hash checks done by the OTA script.

I tried this and for some reason every reboot goes straight back to recovery. Did I do something wrong or am I screwed haha. everything seems to work correctly but then just reboots to recovery.
edit:
Now I just get an icon of an android on floor with chest open haha

Njzkrish said:
I tried this and for some reason every reboot goes straight back to recovery. Did I do something wrong or am I screwed haha. everything seems to work correctly but then just reboots to recovery.
edit:
Now I just get an icon of an android on floor with chest open haha
Click to expand...
Click to collapse
That's the stock recovery.

restore back to stock
question, did bootloader unlock flash twrp then immediately backup my watch before flash the kernel. if i restore this backup file will it get back to stock?
Thanx

vinny.1967 said:
question, did bootloader unlock flash twrp then immediately backup my watch before flash the kernel. if i restore this backup file will it get back to stock?
Thanx
Click to expand...
Click to collapse
If you flash the recovery (twrp) and reboot into twrp to backup then you are backing up the stock boot, system and data.
Flashing the kernel will replace the boot.img only so restoring the twrp backup prior to this will restore your stock boot, system and data. At this stage your recovery is still custom (twrp)

So I want to return to stock to sideload the LCB43B update. However, I'm having issues following the directions listed. The recovery img and boot img flash fine but when I try to flash the system img, I get:
Code:
target reported max download size of 63963136 bytes
Invalid sparse file format at header magi
So I follow the steps to boot into twrp and it boots fine but adb push and shell gives error no device found. I unlocked my bootloader and flashed your kernel so idk if that is causing the errors.

Kingdavid7 said:
So I want to return to stock to sideload the LCB43B update. However, I'm having issues following the directions listed. The recovery img and boot img flash fine but when I try to flash the system img, I get:
Code:
target reported max download size of 63963136 bytes
Invalid sparse file format at header magi
So I follow the steps to boot into twrp and it boots fine but adb push and shell gives error no device found. I unlocked my bootloader and flashed your kernel so idk if that is causing the errors.
Click to expand...
Click to collapse
You should check your drivers

Skin1980 said:
You should check your drivers
Click to expand...
Click to collapse
Nvm I got it

Skin1980 said:
You should check your drivers
Click to expand...
Click to collapse
Hi,
I have the same problem.... As it has solved ?

I'm uploading a zip file that can be flashed with twrp. It might restore stock system, boot and recovery so, after the flash, you should only relock bootloader anda you are good to go.
It's untested so only people that know how to restore the watch should try it.
Like i said, i dont own this watch so i can't test for you. Sorry.
https://mega.nz/#!vkBSCR4C!hZzbAMe7PZPBG88Bfm3mBi6hAfDHCpLMArIwpY6xhHc

Does anybody could be able to tall me what is the reason to root this watch? What are the benefits?
Sent from my SM-N920C using XDA Free mobile app

Skin1980 said:
I'm uploading a zip file that can be flashed with twrp. It might restore stock system, boot and recovery so, after the flash, you should only relock bootloader anda you are good to go.
It's untested so only people that know how to restore the watch should try it.
Like i said, i dont own this watch so i can't test for you. Sorry.
https://mega.nz/#!vkBSCR4C!hZzbAMe7PZPBG88Bfm3mBi6hAfDHCpLMArIwpY6xhHc
Click to expand...
Click to collapse
Has anyone thus far tried to relock the bootloader? I usually don't unlock any of my device until using them for a couple weeks to make sure I don't have a lemon. I'm curious if it's unlocked if Huawei would check, or if their system would show it was being previously unlocked.

TWRP recovery loop, what should I do?

Hey all. I got my mi6 recently. and I installed twrp on it, and flashed magisk. I was trying to install atmos in recovery mod, then I remembered that I hadn't already downloaded the file. For some damn reason I decided to wipe my device. however that didn't go well, and now I'm stuck on a twrp load loop.
I've already tried this command unsuccessfully.
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1 conv=notrunc
Also in desperation, I flashed my phone, rebooted it and etc.
What else can I try?

you can re-flash Twrp in fastboot mode, then boot to twrp, connect to you pc, it will recognize your phone as usb storage.
Down load you rom, copy it to your phone, then install rom by Twrp.

demonntl said:
you can re-flash Twrp in fastboot mode, then boot to twrp, connect to you pc, it will recognize your phone as usb storage.
Down load you rom, copy it to your phone, then install rom by Twrp.
Click to expand...
Click to collapse
I just tried that. Didn't work. Also, nothing changed.

amirography said:
I just tried that. Didn't work. Also, nothing changed.
Click to expand...
Click to collapse
have you tried to flash global rom with Miflash? in bootloader mode?

amirography said:
I just tried that. Didn't work. Also, nothing changed.
Click to expand...
Click to collapse
Can you boot to TWPR ?
- Yes: you can connect to PC and copy your rom, then install
- No: flash fastboot rom: download from Xiaomi site, use Miflash to flash in fastboot, then flash TWPR again.

Xiaomi download site is down
xdauser2018 said:
have you tried to flash global rom with Miflash? in bootloader mode?
Click to expand...
Click to collapse
demonntl said:
Can you boot to TWPR ?
- Yes: you can connect to PC and copy your rom, then install
- No: flash fastboot rom: download from Xiaomi site, use Miflash to flash in fastboot, then flash TWPR again.
Click to expand...
Click to collapse
The Xiaomi download site is down. Does anyone have a copy of the Fastboot ROM by any chance that they can share?

thewholuver94 said:
The Xiaomi download site is down. Does anyone have a copy of the Fastboot ROM by any chance that they can share?
Click to expand...
Click to collapse
http://bigota.d.miui.com/V9.5.6.0.O...FA_20180410.0000.00_8.0_global_2a2234e1c5.tgz

xdauser2018 said:
have you tried to flash global rom with Miflash? in bootloader mode?
Click to expand...
Click to collapse
Haven't tried that. But it worth a shot.
demonntl said:
Can you boot to TWPR ?
- Yes: you can connect to PC and copy your rom, then install
- No: flash fastboot rom: download from Xiaomi site, use Miflash to flash in fastboot, then flash TWPR again.
Click to expand...
Click to collapse
didn't use miflash. The simple flashing didn't work however. I also tried reinstalling twrp.
thewholuver94 said:
The Xiaomi download site is down. Does anyone have a copy of the Fastboot ROM by any chance that they can share?
Click to expand...
Click to collapse
you may need to use a mobile browser. But there are mirrors.

I managed to fix the problem, by accident.
I just wiped Dalvik cache and data using the wiping tool in twrp.
after the reboot, TWRP was gone, and a fresh rom was installed with all my data, gone. However, that already has happened. So it wasn't a great loss.
I'm not technical, so I don't really know what made caused the loop, or how another wipe fixed it. So if anyone can explain it better, the floor is yours.
Thanks for the support.

amirography said:
I managed to fix the problem, by accident.
I just wiped Dalvik cache and data using the wiping tool in twrp.
after the reboot, TWRP was gone, and a fresh rom was installed with all my data, gone. However, that already has happened. So it wasn't a great loss.
I'm not technical, so I don't really know what made caused the loop, or how another wipe fixed it. So if anyone can explain it better, the floor is yours.
Thanks for the support.
Click to expand...
Click to collapse
Have you enabled phone encryption before? It could be this.. After manual wipe of data partition you were able to boot again..

xdauser2018 said:
Have you enabled phone encryption before? It could be this.. After manual wipe of data partition you were able to boot again..
Click to expand...
Click to collapse
i have the same problem .... how can i disable encryprion?

rovaris said:
i have the same problem .... how can i disable encryprion?
Click to expand...
Click to collapse
Boot in Twrp, wipe, advanced wipe, format data

Need help manually flashing factory image

Due to limitations with my chromebook i am force to flash a factory image manually. flash all causes an I/O error. can someone list all the commands to flash it all manually. was on dp3 and tried to boot a custom rom.
i would like to go back to most current june update if possible.
everything i have found online is for older devices

motcher41 said:
Due to limitations with my chromebook i am force to flash a factory image manually. flash all causes an I/O error. can someone list all the commands to flash it all manually. was on dp3 and tried to boot a custom rom.
i would like to go back to most current june update if possible.
everything i have found online is for older devices
Click to expand...
Click to collapse
How did you get to DP3? Did you enroll in the beta program?

Badger50 said:
How did you get to DP3? Did you enroll in the beta program?
Click to expand...
Click to collapse
yes and weirdly using a factory image on my Mi A1 gave no error

motcher41 said:
yes
Click to expand...
Click to collapse
Then just unenroll from the beta program. You'll then get an OTA that will wipe your phone, and put you back on 8.1 :good:

Badger50 said:
Then just unenroll from the beta program. You'll then get an OTA that will wipe your phone, and put you back on 8.1 :good:
Click to expand...
Click to collapse
i would but i am currently soft bricked. have access to bootloader only

even tried to sideload an ota image but no luck there either. either have to flash it all manually or buy a real pc

motcher41 said:
even tried to sideload an ota image but no luck there either. either have to flash it all manually or buy a real pc
Click to expand...
Click to collapse
Oh boy, your in pickle then! Then I suppose you'll have to....
fastboot format userdata
Then fastboot each image, which I think there are 21 of them if memory serves.
The command lines aren't that hard, just a lot of them. Start with the bootloader, then radio, then just start going down the list, ie.......
fastboot flash bootloader bootloaderxxxxx.img
fastboot reboot bootloader
fastboot flash radio radioxxxxxxx.img
fastboot reboot bootloader
Then just start flashing all the images from the secondary zip you'll find in the factory image.

but are they all the same target as the .img name

Badger50 said:
Oh boy, your in pickle then! Then I suppose you'll have to....
fastboot format userdata
Then fastboot each image, which I think there are 21 of them if memory serves.
The command lines aren't that hard, just a lot of them. Start with the bootloader, then radio, then just start going down the list, ie.......
fastboot flash bootloader bootloaderxxxxx.img
fastboot reboot bootloader
fastboot flash radio radioxxxxxxx.img
fastboot reboot bootloader
Then just start flashing all the images from the secondary zip you'll find in the factory image.
Click to expand...
Click to collapse
wow that actually worked....the flashing of everything to slot by name except the system_other
format userata command gave an error too

motcher41 said:
wow that actually worked....the flashing of everything to slot by name except the system_other
format userata command gave an error too
Click to expand...
Click to collapse
Hey, as long as it worked your good. Welcome :good:
Yeah my format userdata may have been off. I was going by memory from my 6p. P2XL might be different. Sorry.

Unable to flash OTA update

Hi all, I have TWRP + Magisk on my device and I am attempting to update from PQ1A.181205.006 to PQ2A.190205.001.
Steps taken
1. Downloaded the OTA from here: https://developers.google.com/android/ota#crosshatch
2. Moved the OTA to phone storage.
3. Checked SHA256 checksum matches.
4.
Code:
adb reboot recovery
5.
Code:
fastboot boot twrp-3.2.3-3-crosshatch.img
6. From TWRP > Install > OTA zip file
Fails with the attached error. I have also tried sideloading through TWRP with the same result. Has anyone hit this error or successfully flashed the OTA update through TWRP?

I have not heard of anyone successfully loading an OTA through TWRP. Either restore stock recovery (install boot.img to both slots) and sideload with the Google instructions or run the flash-all (remove the -w) to use the factory image. Either way, you ere going to be reverting to stock recovery.
P.S. Your message doesn't make sense since you say you have TWRP on your device but then are showing that you used fastboot boot to run the TWRP .img file. If TWRP was on your device, you wouldn't have to use that command. You would just have entered TWRP with the adb reboot recovery command. I am guessing you are rebooting into the bootloader screen where either you run the TWRP .img or run the flash-all.

I also thought I saw a previous post somewhere that said you cannot skip an update, so going from December to February may not work.....not sure...
But definitely you need to load the OTA via regular Recovery using adb not TWRP....

Can you install a OTA?
I thought you had to perform an ADB sideload of an OTA.
Even then I am not aware that ADB sideload works for Pixel 3xl yet.
I have been flashing the factory image with -w removed.

parakleet said:
Can you install a OTA?
I thought you had to perform an ADB sideload of an OTA.
Even then I am not aware that ADB sideload works for Pixel 3xl yet.
I have been flashing the factory image with -w removed.
Click to expand...
Click to collapse
ADB sideload works fine for the OTAs in stock recovery. That's how I've been doing mine.
On a side note, the Essential phone is the only phone I've come across so far that TWRP will flash the factory OTAs.

spotmark said:
ADB sideload works fine for the OTAs in stock recovery. That's how I've been doing mine.
On a side note, the Essential phone is the only phone I've come across so far that TWRP will flash the factory OTAs.
Click to expand...
Click to collapse
The P2XL and Nexis 6p can flash OTA's via twrp as well. Hopefully Team Win will get it sorted out for you guys as well :good:

Badger50 said:
The P2XL and Nexis 6p can flash OTA's via twrp as well. Hopefully Team Win will get it sorted out for you guys as well :good:
Click to expand...
Click to collapse
Flash them or sideload them? I never had a P2XL, but I had a Nexus 6p and I don't remember being able to flash that with the factory zips. That doesn't mean my memory isn't shot either.

spotmark said:
Flash them or sideload them? I never had a P2XL, but I had a Nexus 6p and I don't remember being able to flash that with the Factory zips. That doesn't mean my memory isn't shot either.
Click to expand...
Click to collapse
Yeah, it was possible, just not many people knew about it, but it definitely works :good:
Flashing them that is.

I went from dec to feb update no problem

hilla_killa said:
I went from dec to feb update no problem
Click to expand...
Click to collapse
Sideloading or factory image method?

I am trying to do an OTA update on my Pixel 3xl. I have TWRP installed and need to get back to stock recovery. I have the stock boot.img file and have attempted to flash with adb fastboot but I keep getting this error
writing 'recovery'...
FAILED (remote: Not allowed to flash (recovery))
Bootloader is unlocked
USB debugging is on
Any help would be appreciated.

Badbrad17 said:
I am trying to do an OTA update on my Pixel 3xl. I have TWRP installed and need to get back to stock recovery. I have the stock boot.img file and have attempted to flash with adb fastboot but I keep getting this error
writing 'recovery'...
FAILED (remote: Not allowed to flash (recovery))
Bootloader is unlocked
USB debugging is on
Any help would be appreciated.
Click to expand...
Click to collapse
Did you first extract the secondary zip file inside the factory image, and then placed the boot.img in your platform-tools folder, and the used the command..fastboot flash boot boot.img....??

Badger50 said:
Did you first extract the secondary zip file inside the factory image, and then placed the boot.img in your platform-tools folder, and the used the command..fastboot flash boot boot.img....??
Click to expand...
Click to collapse
Yes that is what I did.

Badbrad17 said:
Yes that is what I did.
Click to expand...
Click to collapse
Okay, and you are in fastboot mode and not adb from the OS as well I take it? Have you tried a different USB cable and port? If all else fails, you can flash the boot.img in twrp as well.

Badger50 said:
Okay, and you are in fastboot mode and not adb from the OS as well I take it? Have you tried a different USB cable and port? If all else fails, you can flash the boot.img in twrp as well.
Click to expand...
Click to collapse
OH I di not know I could do it in TWRP. Will try that first. thanks

Badbrad17 said:
OH I di not know I could do it in TWRP. Will try that first. thanks
Click to expand...
Click to collapse
Just make sure you flash it to the boot partition :good:

raphytaffy said:
Hi all, I have TWRP + Magisk on my device and I am attempting to update from PQ1A.181205.006 to PQ2A.190205.001.
Steps taken
1. Downloaded the OTA from here: https://developers.google.com/android/ota#crosshatch
2. Moved the OTA to phone storage.
3. Checked SHA256 checksum matches.
4.
Code:
adb reboot recovery
5.
Code:
fastboot boot twrp-3.2.3-3-crosshatch.img
6. From TWRP > Install > OTA zip file
Fails with the attached error. I have also tried sideloading through TWRP with the same result. Has anyone hit this error or successfully flashed the OTA update through TWRP?
Click to expand...
Click to collapse
I've installed 3 latest updates from twrp ...
Download the latest OTA, you have to be in stock Rom and Kernel stock ... and have last twrp on your phone... Flash OTA and twrp installer to keep twrp ... restart in twrp for magisk or restart system ... benefits
sorry for my bad english.

Badger50 said:
Just make sure you flash it to the boot partition :good:
Click to expand...
Click to collapse
How do I make sure of this? Sorry I'm a bit of a noob.

Badbrad17 said:
How do I make sure of this? Sorry I'm a bit of a noob.
Click to expand...
Click to collapse
Tap install on the twrp home screen. Then go to where you have the boot.img on your internal storage and tap image on the bottom right. Then select the "boot" partition, and swipe to install. This will return you back to stock recovery and kernel :good:

Badger50 said:
Tap install on the twrp home screen. Then go to where you have the boot.img on your internal storage and tap image on the bottom right. Then select the "boot" partition, and swipe to install. This will return you back to stock recovery and kernel :good:
Click to expand...
Click to collapse
Well I managed to do that, but now when my phone rebooted the touch screen no longer responds. Very strange. It all loads fine and I can see my screen but nothing works. I tried to go back into recovery and I get the little dead Android guy laying on his back with a red exclamation point and "No Command" below it.
Any ideas?