Database Develop

quick question

I currently am running an older version of jf's recovery image and would like to upgrade to Cm recovery 1.4.
I have looked through the fourms and can't find any help on installing a new recovery image over the old one. I was just wondering if I would have to install it like I did with the first one, downgrade my phone and all that or is there a way I can insatll it with out having to do all those steps over again.
Thanks for you help in advance
Ps. Didn't really know where to post this thread sorry if it is in the wrong area..

Hi,
This should really be in the Q&A section.
To answer your question, save the .img on to your SD card, do not rename it, go to your terminal emulator and type flash_image recovery /sdcard/cm-recovery-1.4.img
As long as you did not rename the file, and you spell the commands right, then you should be golden.

QUESTION !!!!!!!!!! >>>> Q&A Section !!!

don't forget the su. also you will want to do reboot recovery so you can see your pretty new recovery image.

thanks
Thanks for all the help guys

ps
And I guess I brain farted not putting it in the Q&A section, my bad

still not working
ironnius said:
Hi,
This should really be in the Q&A section.
To answer your question, save the .img on to your SD card, do not rename it, go to your terminal emulator and type flash_image recovery /sdcard/cm-recovery-1.4.img
As long as you did not rename the file, and you spell the commands right, then you should be golden.
Click to expand...
Click to collapse
I did what you said it it didn't work, it gave me the message, this was all done in terminal emulator.
"error writing recovery : Permission denied"
Is there something i have to do to allow this?

do the following in terminal emu
su
flash_image recovery /sdcard/cm-recovery-1.4.img

Put the recovery img on the root of your ad card
Installing the CyangenMod Recovery IMG
1. Open up the Terminal App on your phone
2. Type in su then press on "Always Allow"
3. Type in the following:
Code:
cd /sdcard
wget http://n0rp.chemlab.org/android/cm-recovery-1.4.img
flash_image recovery /sdcard/cm-recovery-1.4.img4. Done! Easy as Pie

Fingerlickin said:
do the following in terminal emu
su
flash_image recovery /sdcard/cm-recovery-1.4.img
Click to expand...
Click to collapse
thank you that worked

1sickat said:
Put the recovery img on the root of your ad card
Installing the CyangenMod Recovery IMG
1. Open up the Terminal App on your phone
2. Type in su then press on "Always Allow"
3. Type in the following:
Code:
cd /sdcard
wget http://n0rp.chemlab.org/android/cm-recovery-1.4.img
flash_image recovery /sdcard/cm-recovery-1.4.img4. Done! Easy as Pie
Click to expand...
Click to collapse
yes please download the recovery image and put it on the sdcard, THEN download the recovery image AGAIN using the wget command and replace the first one. THEN use the flash_image command which requires su permissions WITHOUT getting those permissions first.
Sorry, in a bad mood today.

[WIP] [REQUEST] Misc partition dumps

Hey all,
A few of us are attempting to put together a solution to unlock the bootloader of the N4 without wiping, and we need your help.
We need dumps of the misc partition of the N4 both in a bootloader locked and unlocked state. I've explained below what we need and how to do it.
Note, this will require you to re-lock and unlock your bootloader, (which will cause your data to be wiped) so do a nandroid and copy it off your device for a later restore.
Novice instructions:
1) You need to start off with an unlocked bootloader.
2) Boot into fastboot mode and plug into your PC.
3) If you don't have ADB and fastboot on your PC, download the attachment from this post and extract the contents to a directory.
4) If you don't have CWM or TWRP flashed, download CWM from here and save as cwm.img in the same directory as in step 3.
5) Open a command prompt in the same directory as in step 3 (i.e., hold the shift key and right click in a blank space in that folder).
6) Flash CWM: fastboot flash recovery cwm.img
7) On your phone, navigate with the volume buttons to "recovery mode" and select with the power button.
8) Once CWM is booted, type the following commands into the command prompt:
Code:
adb shell
dd if=/dev/block/mmcblk0p19 of=/sdcard/misc-unlocked.img
exit
adb pull /sdcard/misc-unlocked.img
adb reboot bootloader
fastboot oem lock
fastboot reboot-bootloader
9) On your phone, navigate with the volume buttons to "recovery mode" and select with the power button.
10) Once CWM is booted, type the following commands into the command prompt:
Code:
adb shell
dd if=/dev/block/mmcblk0p19 of=/sdcard/misc-locked.img
exit
adb pull /sdcard/misc-locked.img
11) Now you have two files (misc-unlocked.img and misc-lock.img) in the directory you created in step 3. Zip them up and upload them in this thread.
12) Your bootloader is now locked. If you want it unlocked, unlock it using the normal method of "fastboot oem unlock" which will wipe your data, but all you have to do is restore your nandroid, and you will be back to where you started.
Advanced user instructions:
1) Start with an unlocked bootloader
2) Dump the misc partition: dd if=/dev/block/mmcblk0p19 of=/sdcard/misc-unlocked.img
3) Lock your bootloader
4) Dump the misc partition again: dd if=/dev/block/mmcblk0p19 of=/sdcard/misc-locked.img
5) Upload the files to this thread.
For advanced users only (this has not yet been tested), if you want, you can try flashing the unlocked misc partition:
Code:
adb shell "dd if=/sdcard/misc-unlocked.img of=/dev/block/mmcblk0p19"
to see if it will unlock your device without wiping. But as I said, this has not been tested yet, so do the last step at your own risk.

Edit: nvm
Here is the dump. Thanks for your work.

KyraOfFire said:
Does it wipe sdcard? It need to know if I have to copy everything to the computer.
Thanks,
Click to expand...
Click to collapse
To be safe, you should copy everything to your computer.
Our theory is, once you lock your bootloader with "fastboot oem lock", you should be able to unlock it again without wiping anything just by flashing the misc partition that you dumped when your device was unlocked.
So, the steps themselves will not wipe anything. But, if you use "fastboot oem unlock" to unlock your bootloader (once you have completed all the steps), then it will wipe everything including /sdcard. If you use the command in the "advanced users instructions", the idea is that it won't wipe anything.

KyraOfFire said:
Edit: nvm
Here is the dump. Thanks for your work.
Click to expand...
Click to collapse
Great thanks!
Did you try re-flashing the unlocked misc.img (while you were locked) to see if it unlocked?

I can't flash the misc-unlocked.img
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell "dd if=/sdca
rd/misc-unlocked.img of=/dev/block/mmcblk0p19"
dd: can't open '/sdcard/misc-unlocked.img': No such file or directory
Click to expand...
Click to collapse
What is the command prompt code to flash it from my computer?
Edit: I did boot to Android and copy the file to SDcard, but I still got the error above.

KyraOfFire said:
I can't flash the misc-unlocked.img
What is the command prompt code to flash it from my computer?
Edit: I did boot to Android and copy the file to SDcard, but I still got the error above.
Click to expand...
Click to collapse
Try this:
1) Copy the file to /sdcard
2) Reboot into CWM
3) Type in the command

I still got the same error.
Also, the directories seem to be messed up again, the classic orphaned back up folders in that CWM/system doesn't seem to recognized anymore....

KyraOfFire said:
I still got the same error.
Also, the directories seem to be messed up again, the classic orphaned back up folders in that CWM/system doesn't seem to recognized anymore....
Click to expand...
Click to collapse
Not sure why your directories are messed up.
Find where the file is saved, and use that path for the "if" part of the command. For example, if it is saved in /storage/emulate/0, then use this command:
adb shell "dd if=/storage/emulate/0/misc-unlocked.img of=/dev/block/mmcblk0p19"

Confirmed!
Flashing misc-unlocked.img unlocked my bootloader.
Note: I copy the file to /system, mounted /system in CWM then
adb shell "dd if=/system/misc-unlocked.img of=/dev/block/mmcblk0p19"
Click to expand...
Click to collapse
I have no idea why /sdcard or /storage/emulate/0/ doesn't work. But I think you should take a look into this when you cook up the new root method

KyraOfFire said:
Confirmed!
Flashing misc-unlocked.img unlocked my bootloader.
Note: I copy the file to /system, mounted /system in CWM then
I have no idea why /sdcard or /storage/emulate/0/ doesn't work. But I think you should take a look into this when you cook up the new root method
Click to expand...
Click to collapse
Great, thanks for the confirmation.
Very strange that /sdcard did not work. It worked fine on mine, but we will certainly look into it.
Thanks again.

Glad I could help. Now folks have less things to worry about when they decide to root

KyraOfFire said:
Edit: nvm
Here is the dump. Thanks for your work.
Click to expand...
Click to collapse
After looking at your dumps, it seems like you are running an old version of Android. Is it possible that you are still on JVP15Q? If so, I don't think that will help us too much. I dumped mine when I was on JOP40C (and I will do so again with JOP40D). If you do upgrade, then new dumps would be appreciated.
By the way, could you list the following from your device:
ROM version:
Bootloader:
Radio:
Thanks.
EDIT: If you want to follow the progress, you can have a look at this thread.

efrant said:
After looking at your dumps, it seems like you are running an old version of Android. Is it possible that you are still on JVP15Q?
Click to expand...
Click to collapse
Well that is totally weird
Build Number:JOP40D
Baseband version:M92615A-CEFWMAZM-2.0.1700.33
Bootloader version:MAKOZ101
is there anything look wrong?
When I get some wifi later today, I'll return to stock and dump the misc partition for JOP40C, possibly redo JOP40D too.

KyraOfFire said:
Well that is totally weird
Build Number:JOP40D
Baseband version:M92615A-CEFWMAZM-2.0.1700.33
Bootloader version:MAKOZ101
is there anything look wrong?
When I get some wifi later today, I'll return to stock and dump the misc partition for JOP40C, possibly redo JOP40D too.
Click to expand...
Click to collapse
Hmm. Thanks for the offer, but don't bother going through the hassle. If you are already running JOP40D, then it should be ok. Weird that your dump had JVP15Q in it. I'll wait until a couple of the other guys have a look at it (in this thread).

For science

KyraOfFire said:
For science
Click to expand...
Click to collapse
Thanks! Still mentions JVP15Q for some reason but I don't think that's a big deal. Found some interesting stuff already so we might be on to something. You've been very helpful.

osm0sis said:
Thanks! Still mentions JVP15Q for some reason but I don't think that's a big deal. Found some interesting stuff already so we might be on to something. You've been very helpful.
Click to expand...
Click to collapse
I have a feeling that it has something to do with history/logging. My N4 came with JOP40C out of the box, and I would bet that KyraOfFire's came with JVP15Q out of the box.

[D950] LG G Flex: How to get out of CWM Boot-loop

Having trouble with your G Flex? Does it keep booting into cwm recovery? Here is a potential solution to this problem. ATT [D950] model only!!
Thanks to mrksbrd and this forum post.
1. Download this file to your adb directory
cd to your adb folder and push this file using
Code:
adb push laf.img /sdcard/laf.img
2. Then, in cmd, type
Code:
adb shell
enter, then type
Code:
dd if=/sdcard/laf.img of=/dev/block/platform/msm_sdcc.1/by-name/laf
3. If your flex doesn't show the AT&T boot image, try typing
Code:
adb reboot download
If you still go to recovery, continue with 4.
4. Still in cmd, type
Code:
dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/laf.img
enter, then type
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
You might get an error that there is no more space left, it should still work. I got that same error.
5. Your flex should immediately show the AT&T boot screen. If that doesn't work, I would wait until AT&T releases it's zipped rom and adb push then flash it.

zNiiC said:
Having trouble with your G Flex? Does it keep booting into cwm recovery? Here is a potential solution to this problem. ATT [D950] model only!!
Thanks to mrksbrd and this forum post.
1. Download this file to your adb directory
cd to your adb folder and push this file using
Code:
adb push laf.img /sdcard/laf.img
2. Then, in cmd, type
Code:
adb shell
enter, then type
Code:
dd if=/sdcard/laf.img of=/dev/block/platform/msm_sdcc.1/by-name/laf
3. If your flex doesn't show the AT&T boot image, try typing
Code:
adb reboot download
If you still go to recovery, continue with 4.
4. Still in cmd, type
Code:
dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/laf.img
enter, then type
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
You might get an error that there is no more space left, it should still work. I got that same error.
5. Your flex should immediately show the AT&T boot screen. If that doesn't work, I would wait until AT&T releases it's zipped rom and adb push then flash it.
Click to expand...
Click to collapse
Very, Very Thanks man. This save my phone.

fbfortes said:
Very, Very Thanks man. This save my phone.
Click to expand...
Click to collapse
You're welcome! Glad I could help.

the fife is deleted.someone upload the file.please

LAF.IMG
dancemaster said:
the fife is deleted.someone upload the file.please
Click to expand...
Click to collapse
did you ever find the file, i need it badly

Hey guys. I've found another laf.img from another post and changed the link here.

zNiiC said:
Hey guys. I've found another laf.img from another post and changed the link here.
Click to expand...
Click to collapse
As I noted earlier, laf. img, aboot.img and other boot partition files are not the same as every model of G Flex??? Or is it just the case for aboot.img and laf. files?
Freedom flex app has aboot.img I would say the same for all models!??

Triad79 said:
As I noted earlier, laf. img, aboot.img and other boot partition files are not the same as every model of G Flex??? Or is it just the case for aboot.img and laf. files?
Freedom flex app has aboot.img I would say the same for all models!??
Click to expand...
Click to collapse
Yes they aren't the same. There was a topic about getting laf.img for ATT G Flex, and so I posted this here, in the topic about fixing the D950 (ATT) G Flex.

nice work bro

eZdubzitmk4 said:
nice work bro
Click to expand...
Click to collapse
keep getting device not found error in cmd

Jmaserang said:
keep getting device not found error in cmd
Click to expand...
Click to collapse
just unplug and replug then type adb devices and see if it pops up. should say recovery in cmd
Sent from my LG-D950 using Tapatalk

eZdubzitmk4 said:
just unplug and replug then type adb devices and see if it pops up. should say recovery in cmd
Sent from my LG-D950 using Tapatalk
Click to expand...
Click to collapse
got it thanks guys

just unplug it and plug it back in
i tried that and adb still doesnt recognize it in recovery mode or any mode

Just had this happen to me, d950g (rogers).
Worked like a champ. Still had root, even after factory reset/wipe.

This is a good resource if I get the nerve to update my rooted D950 4.2.2. Thanks OP.

Recovery problem

Hey
My phone is LG L90 410
I was trying to install cm 12.1 -i'm on official lg lolipop rom-
first i tried to install CWM .. i used Flashify
then after try enter the recovery menu it says "secure booting error cause boot certification"
then enter a purple screen asking for something like RAM dump
any help please to fix this ?

KareemWaheed said:
Hey
My phone is LG L90 410
I was trying to install cm 12.1 -i'm on official lg lolipop rom-
first i tried to install CWM .. i used Flashify
then after try enter the recovery menu it says "secure booting error cause boot certification"
then enter a purple screen asking for something like RAM dump
any help please to fix this ?
Click to expand...
Click to collapse
Did you unlock the bootloader before install the recovery?
Can you still boot to android?

same problem here too... device is rooted ... tried to install twrp but when I want to enter into recovery this problem appears
Yes, in my case I can boot into android ... just when pink screen ram dump appears need to hold power button to restart and it boot android like normal

@KareemWaheed @gjurosi
Follow this guide: http://forum.xda-developers.com/lg-l90/general/guide-unlock-bootloader-flash-custom-t2839690
This should fix your phones.

neverdies said:
@gjurosi
Follow this guide: http://forum.xda-developers.com/lg-l90/general/guide-unlock-bootloader-flash-custom-t2839690
This should fix your phones.
Click to expand...
Click to collapse
tried but nothing,extract aboot.bin to external storage and in terminal when I tried to tipe commands it says unallowed user

gjurosi said:
tried but nothing,extract aboot.bin to external storage and in terminal when I tried to tipe commands it says unallowed user
Click to expand...
Click to collapse
Did you grant root permision, after typing "su" in terminal?

neverdies said:
Did you grant root permision, after typing "su" in terminal?
Click to expand...
Click to collapse
last time I had that option ... now this situation,dont know anymore why I cant ...? I'll make factory reset then everything from the begining ... one question..when I downloaded this aboot.bin with unlock bootloader,I only need to extract it on external storage?
I cant see any (original) aboot.bin in external storage when I enter phone

gjurosi said:
last time I had that option ... now this situation,dont know anymore why I cant ...? I'll make factory reset then everything from the begining ... one question..when I downloaded this aboot.bin with unlock bootloader,I only need to extract it on external storage?
I cant see any (original) aboot.bin in external storage when I enter phone
Click to expand...
Click to collapse
As you can see at that guide, you need to put the patched aboot.bin on your external sd (/storage/external_SD/aboot.bin) then run the following commands on your phone's terminal.
Code:
su
dd if=/storage/external_SD/aboot.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot
After the su command you've to accept the root request.
Be sure to download and flash the right version of aboot for your phone variant, a wrong version of aboot will brick your phone.

@neverdies ....
in terminal I run the following commands ,but it says "cannot open for read:no such file or directory" ... I put aboot.bin on external storage ...dont know anymore wtf ?!? and I cant do factory reset !!!! again its security boot error and pink screen...
dont know why now... really annoying

gjurosi said:
@neverdies ....
in terminal I run the following commands ,but it says "cannot open for read:no such file or directory" ... I put aboot.bin on external storage ...dont know anymore wtf ?!? and I cant do factory reset !!!! again its security boot error and pink screen...
dont know why now... really annoying
Click to expand...
Click to collapse
Are you sure that your aboot.bin file is in /storage/external_SD?
You can put the aboot.bin in your internal memory instead, or anywhere else, just change command according to your aboot.bin file location.
Exemple if you put your aboot.bin file in /storage/internal_SD run the following command:
Code:
su
dd if=[B]/storage/internal_SD/aboot.bin[/B] of=/dev/block/platform/msm_sdcc.1/by-name/aboot

neverdies said:
Are you sure that your aboot.bin file is in /storage/external_SD?
You can put the aboot.bin in your internal memory instead, or anywhere else, just change command according to your aboot.bin file location.
Exemple if you put your aboot.bin file in /storage/internal_SD run the following command:
Code:
su
dd if=[B]/storage/internal_SD/aboot.bin[/B] of=/dev/block/platform/msm_sdcc.1/by-name/aboot
Click to expand...
Click to collapse
finally , it work ... aboot.bin were on external_sd ..but I dont know why the first time it didnt work ... I tryed again and it worked
flashed rom and everything now works ... thnxxx for help me solving the problem :good:

no recovery, no download mode, no micro usb, but root?

hello dears,
i have very big problem with my c6603. i installed first lollipop hongkong version to my c6603. every function works but i want to install mods and other roms but; my phones usb port doesnt let the pc recognize as "phone". it is not driver problem ; it is hardware failure definetly. the port just charging my phone. And on the phone there is no recovery and download mode. But phone has root. i tried a few things to install custom recovery but couldnt be success. unlocked bootloader but no recovery as i said. i really appreciate if there is a solution. many thanks

mca1 said:
hello dears,
i have very big problem with my c6603. i installed first lollipop hongkong version to my c6603. every function works but i want to install mods and other roms but; my phones usb port doesnt let the pc recognize as "phone". it is not driver problem ; it is hardware failure definetly. the port just charging my phone. And on the phone there is no recovery and download mode. But phone has root. i tried a few things to install custom recovery but couldnt be success. unlocked bootloader but no recovery as i said. i really appreciate if there is a solution. many thanks
Click to expand...
Click to collapse
How did you install that Hong Kong lollipop?

mca1 said:
hello dears,
i have very big problem with my c6603. i installed first lollipop hongkong version to my c6603. every function works but i want to install mods and other roms but; my phones usb port doesnt let the pc recognize as "phone". it is not driver problem ; it is hardware failure definetly. the port just charging my phone. And on the phone there is no recovery and download mode. But phone has root. i tried a few things to install custom recovery but couldnt be success. unlocked bootloader but no recovery as i said. i really appreciate if there is a solution. many thanks
Click to expand...
Click to collapse
Hi there.If you have root access and unlocked bootloader,you can install TWRP even without pc connection.
first you should download a terminal emulator app from google play.
then you should download the latest version of TWRP image file from here https://dl.twrp.me/yuga/.
Place it in the root of your /sdcard folder and rename it to twrp.img
Run the following commands in terminal app
Code:
su
and then we write recovery image file to FOTA with dd command.
Code:
dd if=/sdcard/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
and it's done.
press thanks if it was helpful.

i installed hk lollipop zip from my custom twrp recovery. and when rom istall has finished ; recovery gone.

mrp1375 said:
Hi there.If you have root access and unlocked bootloader,you can install TWRP even without pc connection.
first you should download a terminal emulator app from google play.
then you should download the latest version of TWRP image file from here https://dl.twrp.me/yuga/.
Place it in the root of your /sdcard folder and rename it to twrp.img
Run the following commands in terminal app
Code:
su
and then we write recovery image file to FOTA with dd command.
Code:
dd if=/sdcard/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
and it's done.
press thanks if it was helpful.
Click to expand...
Click to collapse
thank you mrp1375 but i tried this method and when i want to go recovery phone only restarts. because phone has no stock recovery.

mca1 said:
thank you mrp1375 but i tried this method and when i want to go recovery phone only restarts. because phone has no stock recovery.
Click to expand...
Click to collapse
Below are 2 solutions to get a properly working recovery
Preperation:
1. Download Dual recovery installer: XZ-lockeddualrecovery2.8.23-RELEASE.combined.zip
2. Install NDRUtils
Next up we will test if the TWRP you installed works or not
-open NDRUtils and choose to boot into TWRP recovery.
Now unhide the result that you got to continue with the installation:
OK: I am now in TWRP
flash XZ-lockeddualrecovery2.8.23-RELEASE.combined.zip and reboot.
Everything will work normally now.
Not OK: I am not in TWRP
Reboot the phone if you have to (hold power until you feel 3 vibrations and then turn the phone back on)
You need to download this: http://nut.xperia-files.com/path/XZDualRecovery/Kernel_Builder
To get the right file make sure to selec the xperia z c6603 and select the rom version you are using, you can view what you have in settings, about phone, build number.
it will be much easier for you if you install this: X-plore File Manager The reason i recommend this application is that it automatically makes sure the file rights are correct.
Go into the settings and enable superuser +mount root mode
Now you can browse to the folder where you downloaded the zip in the left pane.
go into the zip and and then into tmp
Select the boot.img
now move to the right pane and browse to the root of your SD card like the comment above
go back to the left pane and with boot.img still checked click copy.
Now follow the original instructions mrp1375 gave you, but notice the different filename
Open terminal
Type : su
Type: dd if=/sdcard/boot.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
Now you can reboot and if it worked the phone will vibrate twice and show a green led meaning you can press the down button to enter TWRP recovery.
Go into the recovery and now flash XZ-lockeddualrecovery2.8.23-RELEASE.combined.zip so you get a proper installation
Now remember this very important fact:
Whenever you flash or wipe anything you MUST reinstall recovery and root again.
This is a failsafe strategy you can NEVER ignore becaus of your usb issues.
Keep SuperSu installer and XZ-lockeddualrecovery installer on your device at all times!

thank you

mca1 said:
thank you
Click to expand...
Click to collapse
Does that mean it worked?

tetsuo55 said:
Does that mean it worked?
Click to expand...
Click to collapse
Yes it worked, thank you much. :good:

tetsuo55 said:
Below are 2 solutions to get a properly working recovery
Next up we will test if the TWRP you installed works or not
-open NDRUtils and choose to boot into TWRP recovery.
Now unhide the result that you got to continue with the installation:
OK: I am now in TWRP
flash XZ-lockeddualrecovery2.8.23-RELEASE.combined.zip and reboot.
Everything will work normally now.
Not OK: I am not in TWRP
Reboot the phone if you have to (hold power until you feel 3 vibrations and then turn the phone back on)
You need to download this:
To get the right file make sure to selec the xperia z c6603 and select the rom version you are using, you can view what you have in settings, about phone, build number.
it will be much easier for you if you install this: The reason i recommend this application is that it automatically makes sure the file rights are correct.
Go into the settings and enable superuser +mount root mode
Now you can browse to the folder where you downloaded the zip in the left pane.
go into the zip and and then into tmp
Select the boot.img
now move to the right pane and browse to the root of your SD card like the comment above
go back to the left pane and with boot.img still checked click copy.
Now follow the original instructions mrp1375 gave you, but notice the different filename
Open terminal
Type : su
Type: dd if=/sdcard/boot.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
Now you can reboot and if it worked the phone will vibrate twice and show a green led meaning you can press the down button to enter TWRP recovery.
Go into the recovery and now flash XZ-lockeddualrecovery2.8.23-RELEASE.combined.zip so you get a proper installation
Now remember this very important fact:
Whenever you flash or wipe anything you MUST reinstall recovery and root again.
This is a failsafe strategy you can NEVER ignore becaus of your usb issues.
Keep SuperSu installer and XZ-lockeddualrecovery installer on your device at all times!
Click to expand...
Click to collapse
Hey! I have the same problem as the OP here. I followed the instructions like 5 times and still couldnt get it to work. The terminal is saying that "No space left on device" when i type "dd if=/sdcard/boot.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel"
any way to fix this? Thanks!

comcastic08 said:
Hey! I have the same problem as the OP here. I followed the instructions like 5 times and still couldnt get it to work. The terminal is saying that "No space left on device" when i type "dd if=/sdcard/boot.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel"
any way to fix this? Thanks!
Click to expand...
Click to collapse
That error sounds like either you dont have root or you have a typo, can you make a screenshot?

tetsuo55 said:
That error sounds like either you dont have root or you have a typo, can you make a screenshot?
Click to expand...
Click to collapse
snag. gy/gi8Ji. jpg
sorry i cant post links yet

comcastic08 said:
snag. gy/gi8Ji. jpg
sorry i cant post links yet
Click to expand...
Click to collapse
That doesnt look quite right it should look like this:
Code:
[email protected]:/ $
Then you type "su" (without the quotes) and press enter
The display then changes to:
Code:
[email protected]:/ #
Now you type "dd if=/sdcard/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel" (without the quotes) and press enter
And then it should work properly.

tetsuo55 said:
That doesnt look quite right it should look like this:
Code:
[email protected]:/ $
Then you type "su" (without the quotes) and press enter
The display then changes to:
Code:
[email protected]:/ #
Now you type "dd if=/sdcard/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel" (without the quotes) and press enter
And then it should work properly.
Click to expand...
Click to collapse
i typed su before that code and the same error occured sadly
why did my usb port had to break ugh

comcastic08 said:
i typed su before that code and the same error occured sadly
why did my usb port had to break ugh
Click to expand...
Click to collapse
Can I have another screenshot of that?

tetsuo55 said:
Can I have another screenshot of that?
Click to expand...
Click to collapse
snag .gy/AekHa. jpg

comcastic08 said:
snag .gy/AekHa. jpg
Click to expand...
Click to collapse
In that screenshot i see again the same mistake i mentioned before
please do this
Just type only su and enter
and then send me the screenshot of that.

tetsuo55 said:
In that screenshot i see again the same mistake i mentioned before
please do this
Just type only su and enter
and then send me the screenshot of that.
Click to expand...
Click to collapse
snag. gy/aWyCY .jpg

comcastic08 said:
snag. gy/aWyCY .jpg
Click to expand...
Click to collapse
All i can think of is that you have the wrong boot.img

tetsuo55 said:
All i can think of is that you have the wrong boot.img
Click to expand...
Click to collapse
i downloaded the one you said XZ-lockeddualrecovery2.8.23-RELEASE.combined.zip and renamed it to boot.img
even the twrp.img doesnt work ugh