Kernel Flasher - AT&T Galaxy Note 3 Android Development

This app allows you to use safestrap on certain devices running 4.4.4 and 5.0.
It basically runs
Code:
dd if=kernel.img of=/dev/block/platform/msm_sdcc.1/by-name/boot
I am not responsible for anything that may happen to your device.
Post stack trace/logcat in this thread if it crashes.
If you get errors when updating, uninstall first.
Source code: https://github.com/benwaffle/AT-T-Note-3-Kernel-Flasher
AT&T Note 3 - NC2: this post
AT&T Galaxy S 4 - NC1
AT&T Galaxy S 5 - NCE
If you want to modify for your device, you can edit strings.xml
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

What exactly does this do?

Flash the NC2 kernel image without Odin (to access SS). To get back to nj5 or nl1 you still need odin or a flashable zip.

Is there a flashable zip for us? And does that work via safe strap , flashing a kernel?

Installed this but it force closes everyone I open it
---------- Post added at 07:22 PM ---------- Previous post was at 07:22 PM ----------
Everytime*

Can you give me a stack trace? Via 'adb logcat' or if there's a report button, there should be a stack trace section at the very bottom

Never mind it worked somehow

If safestrap doesn't allow you to flash kernels then this is an even worse idea. Use at your own risk.

Almost certain it doesn't but mostly just because we've always been stuck with one and never had this kind of option.. But I'm pretty sure we can't flash any non signed kernels with our locked boot loader.

benwaffle said:
If safestrap doesn't allow you to flash kernels then this is an even worse idea. Use at your own risk.
Click to expand...
Click to collapse
Not safestrap it's bootloader preventing kernel lnstall

carl1961 said:
Not safestrap it's bootloader preventing kernel lnstall
Click to expand...
Click to collapse
no, it's the bootloader preventing custom kernels from actually booting
i can flash them though

benwaffle said:
no, it's the bootloader preventing custom kernels from actually booting
i can flash them though
Click to expand...
Click to collapse
we can flash modems with safestrap this. is your app? It would have been nice to have this to boot safestrap, and safestrap to install NJ5 kernel, then we would not need a computer all the time.
I will try and see if adb will install a kernel, if it fails then I would sat the bootloader is blocking any kernel

carl1961 said:
we can flash modems with safestrap this. is your app? It would have been nice to have this to boot safestrap, and safestrap to install NJ5 kernel, then we would not need a computer all the time.
I will try and see if adb will install a kernel, if it fails then I would sat the bootloader is blocking any kernel
Click to expand...
Click to collapse
I can make the app reboot to safestrap on flashing if you tell me how.

benwaffle said:
I can make the app reboot to safestrap on flashing if you tell me how.
Click to expand...
Click to collapse
@benwaffle you were absolutely right bootloader did not stop kernel install
putting nc2boot.img on internal sdcard then using adb
adb shell
su
dd if=/sdcard/nc2boot.img of=/dev/block/mmcblk0p14
reboot
it installed ns2 kernel and it booted to safestrap
here is the cmd windows readings
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\carl>adb shell
[email protected]:/ $ su
su
[email protected]:/ # dd if=/sdcard/nc2boot.img of=/dev/block/mmcblk0p14
dd if=/sdcard/nc2boot.img of=/dev/block/mmcblk0p14
20624+1 records in
20624+1 records out
10559760 bytes transferred in 1.450 secs (7282593 bytes/sec)
[email protected]:/ # reboot
reboot
your NC2Flasher.apk does FC and then Supersu popped so app has root
rebooted phone and app still FC
let me know what I can do to help

carl1961 said:
@benwaffle you were absolutely right bootloader did not stop kernel install
putting nc2boot.img on internal sdcard then using adb
adb shell
su
dd if=/sdcard/nc2boot.img of=/dev/block/mmcblk0p14
reboot
it installed ns2 kernel and it booted to safestrap
here is the cmd windows readings
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\carl>adb shell
[email protected]:/ $ su
su
[email protected]:/ # dd if=/sdcard/nc2boot.img of=/dev/block/mmcblk0p14
dd if=/sdcard/nc2boot.img of=/dev/block/mmcblk0p14
20624+1 records in
20624+1 records out
10559760 bytes transferred in 1.450 secs (7282593 bytes/sec)
[email protected]:/ # reboot
reboot
your NC2Flasher.apk does FC and then Supersu popped so app has root
rebooted phone and app still FC
let me know what I can do to help
Click to expand...
Click to collapse
obviously `dd` works, that's what my app does
can you give me a stack trace?

ok how do I grab that "stack trace?"
here is log cat
line 69
01-20 06:53:18.221: V/ApplicationPolicy(1048): isApplicationStateBlocked userId 0 pkgname com.uubmub.nc2flasher
line 208
01-20 06:53:19.461: E/AndroidRuntime(27406): FATAL EXCEPTION: AsyncTask #1
01-20 06:53:19.461: E/AndroidRuntime(27406): Process: com.uubmub.nc2flasher, PID: 27406
01-20 06:53:19.461: E/AndroidRuntime(27406): java.lang.RuntimeException: An error occured while executing doInBackground()

benwaffle said:
obviously `dd` works, that's what my app does
can you give me a stack trace?
Click to expand...
Click to collapse
Got a idea. When you get your app to work I want to try and put nc2 on slot 1 run slot 1 which is nc2 to use your app to install nh1 kernel then hopefully it boots stock slot. If that works then we have a way to do things without odin. I already know that nc2 runs fine on Nl1 firmware except for kernel.
All attempts to install kernel from NC2 running on safestrap failed, and installing NH1 4.4.4 kernel with odin did not ignore safestrap being on slot1, so I had to use safestrap to set phone on stock slot to boot 4.4.4 rom
so even if you did a app to install NH1 successfully ,being in slot1 won't allow 4.4.4 rom to boot

@benwaffle
Awesome app. Thank you so much for creating it for us. One of my biggest problems with 4.4.4 was having to be tied to a computer for anything i wanted to flash. This has made life so much better.
One suggestion I would have is...I wonder if it would be possible to have your reboot method automatically boot into SS instead of having to choose it. I know that @RErick had created an option for the ATTNote 3 that when reboot to recovery was chosen from the Power Options that it automatically went to SS. Maybe you and he can get that together.

I'll be working on that with my update

Should be trivial

Related

fastboot on our L9 with omap4boot

First of all, the thread about omap4boot: http://forum.xda-developers.com/showthread.php?t=1971014
I didn't create this tool, I just found out a way to make it works with our phone, and maybe I'm not the first (tested under Windows 7 Ultimate 32-bit).
What do you need:
omap4boot, get it from original thread.
Extract omap4boot archive somewhere like C:\omap4boot (I will use this path in the tutorial).
Power off your phone and remove the battery.
Connect your phone (still without the battery) to the PC.
You will hear the sound of a new driver, then the sound of a driver when it disconnects continiusly.
Start -> Right click on "Computer" -> "Manage".
On the left column, click on "Device manager".
You will see a device that appear and disappear under "Other/Unknown Devices".
You must right click on the unknown device before it disappear, once clicked select "Driver Update". (You can use this tip to make the process easier http://forum.xda-developers.com/showthread.php?p=51019004).
Click on the second button (manually install driver) and insert the "usb_drv_windows" path (C:\omap4boot\usb_drv_windows) and install the driver.
Disconnect the phone from the PC and power it off.
Open a command prompt (Win+R, type cmd and press Enter).
Type the following command in the command prompt:
Code:
cd C:\omap4boot
start-fastboot.bat
Now input 3 (Prada 3.0 P940) and press enter.
Plug the phone without battery to the PC, when the tool says "Wait 5 seconds" put the battery in your phone.
(The first time that you do this, you have to install the drivers again. Repeat step 9)
At the other prompts answer always "N", this could be important.
Now you can use fastboot on L9 Next times you can start from step 12.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(the red rettangle isn't important here )
Sorry for my english, if someone wants to review the tutorial just send me a PM.
I test it when I do recovery.img (we need to sign it, I will try with prada keys).
Has anyone tried to flash something?
Do you think it won't brick our phone. It flashes new u-boot.
On W8 x64 when I install driver I get Not signed INF.
What FW have you got? 10g or other?
artas182x said:
I test it when I do recovery.img (we need to sign it, I will try with prada keys).
Has anyone tried to flash something?
Do you think it won't brick our phone. It flashes new u-boot.
On W8 x64 when I install driver I get Not signed INF.
What FW have you got? 10g or other?
Click to expand...
Click to collapse
I flashed some stock partitions (recovery, boot) on ITALIAN WIND 10D but I can't confirm if the security error appear or not now.
When i tried to flash system.img fastboot said something like "file too large".
At the step 15 I said to answer N, otherwise the tool should flash new u-boot and I'm not sure if it works on our L9.
Maybe on a 64-bit system you have to disable the driver signature check, the bad thing is that (on Windows 7) you have to do it manually at every boot.
Odp: fastboot on our L9 with omap4boot
I try this today. Maybe it's a way to soft unbrick our l9 (without kdz).
Wysyłane z mojego LG-P760 za pomocą Tapatalk 2
artas182x said:
I try this today. Maybe it's a way to soft unbrick our l9 (without kdz).
Wysyłane z mojego LG-P760 za pomocą Tapatalk 2
Click to expand...
Click to collapse
Yes this should make the phone unbrickable (i think a backup is needed), but as I said I got problems flashing the system.img.
Also, if we get a security error flashing a custom recovery/boot.img we can restore the original recovery/boot.img in seconds without LG Support Tool.
R: fastboot on our L9 with omap4boot
Se need to try u boot from Prada..maybe work!
Inviato dal mio LG-P760 con Tapatalk 2
Bootloader is LK MAY-2012 in Prada 3.0 and our L9. It can work.
artas182x said:
Bootloader is LK MAY-2012 in Prada 3.0 and our L9. It can work.
Click to expand...
Click to collapse
I can try but how to restore the stock u-boot if things won't going well?
I think we can restore with kdz, but I'm not sure.
artas182x said:
I think we can restore with kdz, but I'm not sure.
Click to expand...
Click to collapse
Looking in the omap4boot's files seems that it dumps "x" and "u" partitions (when it dumps the locked loader).
I will backup those partitions to have a possibility of restore with fastboot.
Should I follow the procedure for Prada P940?
i think as same as you,if you can get into recovery, in theory you could install kdz rom.
Maybe I did something wrong but it didn't work..
What I've done:
Start fastboot
When the tools asked for u-boot replace, I said "Y".
fastboot replaced u-boot, then I ran "fastboot reboot".
Black screen. Removed battery and USB, polugged in battery and press power, still black screen.
Started fastboot again and ran "fastboot flash u-boot u.img" (u.img was my backup of u partition)
Then the phone restarted normally with "fastboot reboot".
I was on 10D Wind ITA. The black screen is scary :silly: but this confirms that with fastboot we can restore every partition.
I tried to restore system and phone restarted like in your phone.
artas182x said:
I tried to restore system and phone restarted like in your phone.
Click to expand...
Click to collapse
How did you restore system? fastboot said to me "remote: data too large" or similar.
I didn't restore system beacuse it reboot phone. Have you got good system dump. I did correct system dump using dd if= of=.
artas182x said:
I didn't restore system beacuse it reboot phone. Have you got good system dump. I did correct system dump using dd if= of=.
Click to expand...
Click to collapse
These are the commands that I used some time ago to restore the phone (without the recovery):
Code:
#adb shell su -c busybox dd if=/sdcard/BACKUP/boot.img of=/dev/block/mmcblk0p3
#adb shell su -c busybox dd if=/sdcard/BACKUP/cache.img of=/dev/block/mmcblk0p12
#adb shell su -c busybox dd if=/sdcard/BACKUP/divxkey.img of=/dev/block/mmcblk0p5
#adb shell su -c busybox dd if=/sdcard/BACKUP/fota.img of=/dev/block/mmcblk0p8
#adb shell su -c busybox dd if=/sdcard/BACKUP/misc.img of=/dev/block/mmcblk0p6
#adb shell su -c busybox dd if=/sdcard/BACKUP/mlt.img of=/dev/block/mmcblk0p14
#adb shell su -c busybox dd if=/sdcard/BACKUP/nv.img of=/dev/block/mmcblk0p7
#adb shell su -c busybox dd if=/sdcard/BACKUP/persist.img of=/dev/block/mmcblk0p13
#adb shell su -c busybox dd if=/sdcard/BACKUP/recovery.img of=/dev/block/mmcblk0p4
#adb shell su -c busybox dd if=/sdcard/BACKUP/reserved.img of=/dev/block/mmcblk0p9
#adb shell su -c busybox dd if=/sdcard/BACKUP/u.img of=/dev/block/mmcblk0p2
#adb shell su -c busybox dd if=/sdcard/BACKUP/x.img of=/dev/block/mmcblk0p1
#adb shell su -c busybox dd if=/sdcard/BACKUP/userdata.img of=/dev/block/mmcblk0p11
#adb shell su -c busybox dd if=/sdcard/BACKUP/system.img of=/dev/block/mmcblk0p10
I obtained the imgs with the inverse command.
Anyway you mean you got a black screen?
Has anyone had any luck restoring system.img?
Ive been thinking of different theories on how to save those who updated to 10G on P769BK. One of which is making a system.img dump from a phone that was able to preserve root with Voodo OTA restore and using this tool to flash onto phones that lost it.
I'm not too familiar with fastboot commands but if anyone can help me with how to pull the system partition and reflash to another phone I'll gladly guinea pig...got a couple of these suckers lying around
Jrkoffjonson said:
Has anyone had any luck restoring system.img?
Ive been thinking of different theories on how to save those who updated to 10G on P769BK. One of which is making a system.img dump from a phone that was able to preserve root with Voodo OTA restore and using this tool to flash onto phones that lost it.
I'm not too familiar with fastboot commands but if anyone can help me with how to pull the system partition and reflash to another phone I'll gladly guinea pig...got a couple of these suckers lying around
Click to expand...
Click to collapse
It seems that system partition is too big to flash with fastboot, the only way to restore is with dd but a rooted phone is needed.
sguerrini97 said:
It seems that system partition is too big to flash with fastboot, the only way to restore is with dd but a rooted phone is needed.
Click to expand...
Click to collapse
Well that stinks, so much for that idea :'[
System dump file
After downloading the zip linked in the OP I found a dump batch file called 'dump_prada.bat' in the zip.
Took a look into it and modified it to work with our device to do an easy system wide dump.
It works, but only if you have an external sd card as our internal storage is too small to hold the files before transferring to the computer.
I'm attaching it as a .txt file- just rename it to full_dump.bat and run as admin.
Not taking any credit for the original script..

[rom] [01.07.14] Desire X DEODEXED Stock ROM 2.20.401.6 Jelly Bean Sense 4+

Anyone can use this ROM as his base for Custom ROMs without asking for permission as long as they include credits wherever it is posted​
DEODEXED Stock Jelly Bean with Sense 4+ build 2.20.401.6 for Desire X​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
neXus PRIME for the JB TWRP Recovery
Chainfire for the SuperSU
doiutzu for testing the updater-script and other tests
And anyone directly / indirectly contribute for this ROM​
DEODEXED stock ROM
hTC update build 2.20.401.6 (with Heartbleed fix)
Android Jelly Bean 4.1.1 (JRO03C)
Sense 4+
Kernel: 3.4.0-g2b619a5
rooted with SuperSU
Pre-installed Busybox
init.d support
Unlocked bootloader & Custom Recovery fixed for Jelly Bean
Recommended TWRP Recovery by neXus PRIME (http://forum.xda-developers.com/showpost.php?p=36714573&postcount=2)
For hboot 1.25.0002 (JB hboot)
Put the 2.20.401.6_Dodexed.zip on your sdcard
Make sure you already have the TWRP for JB hboot installed (NOT the stock recovery)
fastboot flash the attached boot.img for S-On DX (which comes with init.d feature)
Reboot to recovery
Make a full wipe is recommended but you can always try a dirty flash if your current ROM is stock (odex or deodexed)
Install the 2.20.401.6_Deodexed.zip as how you normally install a custom ROM
Reboot once completed and you are done
Old version 2.20.401.5_Deodexed.zip
http://sourceforge.net/projects/others/files/DX/2.20.401.5_Deodexed.zip/download
*DELETED*
*DELETED*
I still can't remove apps from system.I think something's wrong with my phone.
CrysiZ said:
I still can't remove apps from system.I think something's wrong with my phone.
Click to expand...
Click to collapse
Use Aroma File Manager. I've removed almost all google aps successfully. Rebooted several times and they do not appear again
CrysiZ said:
I still can't remove apps from system.I think something's wrong with my phone.
Click to expand...
Click to collapse
Which ROM ?
As mentioned before, you need a ROM with a properly installed busybox, root and init.d support.
See Part 1 : http://forum.xda-developers.com/showpost.php?p=40359126&postcount=250
See Part 2 & 3 : http://forum.xda-developers.com/showpost.php?p=40359148&postcount=251
And still can't edit build.prop
secthdaemon said:
And still can't edit build.prop
Click to expand...
Click to collapse
On my Deodexed ROM ?
ckpv5 said:
On my Deodexed ROM ?
Click to expand...
Click to collapse
Yes. Made changes via Build Prop Editor app, allowed changes via SuperSU, rebooted and no changes been applied
secthdaemon said:
Yes. Made changes via Build Prop Editor app, allowed changes via SuperSU, rebooted and no changes been applied
Click to expand...
Click to collapse
Here are the screenshots of build.prop editing that I made on a fresh installed deodexed ROM
I made changes to "ro.config.htc.enableCOTA=1" to "ro.config.htc.enableCOTA=0" with Root Explorer (you can see build.prop.bak is created after saving the changes.
And make a reboot, after reboot the "ro.config.htc.enableCOTA" still show 0 and the build.prop.bak is still there
Init.d seems not to be working
C:\Android>adb reboot recovery
C:\Android>adb push 12_test /system/etc/init.d/12_test
27 KB/s (57 bytes in 0.002s)
C:\Android>adb shell chmod 0755 /system/etc/init.d/12_test
C:\Android>adb reboot
C:\Android>adb shell cat /data/local/tmp/test.log
/system/bin/sh: cat: /data/local/tmp/test.log: No such file or directory
You can try this one.
hm...tried to to make changes with root explorer, rebooted, and all changes are gone and no bak file
secthdaemon said:
Init.d seems not to be working
C:\Android>adb reboot recovery
C:\Android>adb push 12_test /system/etc/init.d/12_test
27 KB/s (57 bytes in 0.002s)
C:\Android>adb shell chmod 0755 /system/etc/init.d/12_test
C:\Android>adb reboot
C:\Android>adb shell cat /data/local/tmp/test.log
/system/bin/sh: cat: /data/local/tmp/test.log: No such file or directory
You can try this one.
Click to expand...
Click to collapse
init.d is working fine... you can find zipalign.log in /data
BTW.. which boot.img that you are using ? the one that you posted ?
I gotta go now... will check later and update post #3 when I'm home.
ckpv5 said:
init.d is working fine... you can find zipalign.log in /data
BTW.. which boot.img that you are using ? the one that you posted ?
I gotta go now... will check later and update post #3 when I'm home.
Click to expand...
Click to collapse
Nope, I'm using your boot.img
secthdaemon said:
Nope, I'm using your boot.img
Click to expand...
Click to collapse
It works for me and others too that helped me.... so no idea why it is not working for you
So.. you don't have zipalign.log in /data folder ?
I'm gonna reflash your rom and boot.img just in case, I'll write about results.
secthdaemon said:
Use Aroma File Manager. I've removed almost all google aps successfully. Rebooted several times and they do not appear again
Click to expand...
Click to collapse
I can remove system apps and edit build.prop with aroma without disabled wp. So what? Why do i need this boot.img?
Sent from my HTC Desire X using xda premium
micu13 said:
I can remove system apps and edit build.prop with aroma without disabled wp. So what? Why do i need this boot.img?
Sent from my HTC Desire X using xda premium
Click to expand...
Click to collapse
You don't have to and you don't need the boot.img when you are comfortable doing all these stuff in recovery
Most people prefer to do things not in recovery as most people use recovery just to do nandroid backup/restore and flashing zips. That is why flar2 comes out with a workaround not only for DX but also on other devices such as
HTC One - http://forum.xda-developers.com/showthread.php?t=2235085 & http://forum.xda-developers.com/showthread.php?t=2233665
secthdaemon said:
I'm gonna reflash your rom and boot.img just in case, I'll write about results.
Click to expand...
Click to collapse
Let us know the result... as I'm afraid it is the JB hboot thing as I can't test it as I'm on ICS hboot.
If yes.. then we may need the kernel source then only Dev like neXusPRIME and atis112 can do their magic.
Ahh... how I wish I am on JB hboot then I can test a lot of things
ckpv5 said:
Which ROM ?
As mentioned before, you need a ROM with a properly installed busybox, root and init.d support.
See Part 1 : http://forum.xda-developers.com/showpost.php?p=40359126&postcount=250
See Part 2 & 3 : http://forum.xda-developers.com/showpost.php?p=40359148&postcount=251
Click to expand...
Click to collapse
Yes,on your deodex rom

[KERNEL][ROOT] Stock kernel Rogers/AT&T

Disclaimer: I am not responsible for anything that happens to your device.
This requires an unlocked bootloader.
- Stock kernel
- Roots device + installs SuperSU on first boot
- Tested on Rogers Moto X
Download Rogers image: http://d-h.st/cFB
Download ATT image: http://d-h.st/1XI
Rogers kernel version:
3.4.42-xline-gfd1a699-00157-gfb2f8fc
[email protected] #1
Thu Jul 18 20:25:42 CDT 2013
ATT kernel version:
3.4.42-xline-gfd1a699-00158-g8990abb
[email protected] #1
Sat Jul 20 14:29:07 CDT 2013
Install:
reboot to bootloader
fastboot flash boot <image file name>
reboot device
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
rob43 said:
Disclaimer: I am not responsible for anything that happens to your device.
This requires an unlocked bootloader.
- Stock kernel
- Roots device + installs SuperSU on first boot
- Tested on Rogers Moto X
Download: http://d-h.st/btV
Install:
reboot to bootloader
fastboot flash boot ghost-boot.img
reboot device
Click to expand...
Click to collapse
This Is great! Now to apply it to att!
Sent from my MB886 using XDA Premium 4 mobile app
What kernel version is this?
Thanks ! I will wait the version where you don t need to unlock bootloader...
Sent from my XT1058 using XDA Premium 4 mobile app
pixeldrew said:
What kernel version is this?
Click to expand...
Click to collapse
Added to OP
rob43 said:
Added to OP
Click to expand...
Click to collapse
Cheers.
doh... only temporarily booted into the image so it reverted back to secure=1.
All good now.
rob43 said:
Disclaimer: I am not responsible for anything that happens to your device.
This requires an unlocked bootloader.
- Stock kernel
- Roots device + installs SuperSU on first boot
- Tested on Rogers Moto X
Kernel version:
3.4.42-xline-gfd1a699-00157-gfb2f8fc
[email protected] #1
Thu Jul 18 20:25:42 CDT 2013
Download: http://d-h.st/btV
Install:
reboot to bootloader
fastboot flash boot ghost-boot.img
reboot device
Click to expand...
Click to collapse
Correct me if I am wrong, but I thought the Rogers' Moto-X has unlocked bootloader? As in, no unlocking required?
You still have to unlock it via the Motorola website to assert that you voided your warranty.
Sent from my XT1058 using xda app-developers app
pixeldrew said:
You still have to unlock it via the Motorola website to assert that you voided your warranty.
Sent from my XT1058 using xda app-developers app
Click to expand...
Click to collapse
Gotcha. Too bad I went ahead and 'bricked' the device. Fastboot Reason: Flash Failure.
;P
All is well. I had to unlock the bootloader, reflash.
Edit 2: I can't update the SuBinary. It throws a generic error message, stating to contact the developer.
hidea said:
Gotcha. Too bad I went ahead and 'bricked' the device. Fastboot Reason: Flash Failure.
;P
All is well. I had to unlock the bootloader, reflash.
Edit 2: I can't update the SuBinary. It throws a generic error message, stating to contact the developer.
Click to expand...
Click to collapse
I got this as well, you're best off finding the superuser.zip from cyanogenmod's site and installing that by hand via adb.
Code:
[email protected] $ unzip superuser.zip
[email protected] $ adb push superuser/armabi/su /sdcard/
[email protected] $ adb shell
[email protected] $ su
[email protected] # mount -o rw,remount /system
[email protected] # copy /sdcard/su /system/xbin/
pixeldrew said:
You still have to unlock it via the Motorola website to assert that you voided your warranty.
Sent from my XT1058 using xda app-developers app
Click to expand...
Click to collapse
pixeldrew said:
I got this as well, you're best off finding the superuser.zip from cyanogenmod's site and installing that by hand via adb.
Code:
[email protected] $ unzip superuser.zip
[email protected] $ adb push superuser/armabi/su /sdcard/
[email protected] $ adb shell
[email protected] $ su
[email protected] # mount -o rw,remount /system
[email protected] # copy /sdcard/su /system/xbin/
Click to expand...
Click to collapse
Cheers! Any particular Superuser.zip you used?
Cyanogenmod's https://github.com/koush/Superuser
pixeldrew said:
Cyanogenmod's https://github.com/koush/Superuser
Click to expand...
Click to collapse
My wit ends here. I've never used Github. Truth revealed, I'm just a hobbyist!
hidea said:
Cheers! Any particular Superuser.zip you used?
Click to expand...
Click to collapse
The SU binary + Superuser.apk are both from the newest SuperSU (1.51). Where are you seeing the "su requires updating" message? SuperSU is already installed for you.
If you install CM's Superuser, you will get this error. I first tried CM's su + Superuser but the apk was not cooperating.
Nonetheless, you will be able to use su from the terminal and do any update you please. Trying to get CWM recovery working at the moment so this is no longer necessary.
rob43 said:
The SU binary + Superuser.apk are both from the newest SuperSU (1.51). Where are you seeing the "su requires updating" message? SuperSU is already installed for you.
If you install CM's Superuser, you will get this error. I first tried CM's su + Superuser but the apk was not cooperating.
Nonetheless, you will be able to use su from the terminal and do any update you please. Trying to get CWM recovery working at the moment so this is no longer necessary.
Click to expand...
Click to collapse
Cheers, I managed to get Terminal to work. But TIBackup still can't get root access. No popups that I'd normally get with CM/other rooted ROMs.
hidea said:
Cheers, I managed to get Terminal to work. But TIBackup still can't get root access. No popups that I'd normally get with CM/other rooted ROMs.
Click to expand...
Click to collapse
Not sure why that would be. Uninstall CM's Superuser if you downloaded it from the market. Only SuperSU worked for me.
Titanium Backup works without a problem here.
I would suggest deleting both su + Superuser.apk and rebooting, if you modified either in /system. Upon startup, it will reroot your device with the latest SuperSU + su binary.
rob43 said:
Not sure why that would be. Uninstall CM's Superuser if you downloaded it from the market. Only SuperSU worked for me.
Titanium Backup works without a problem here.
Click to expand...
Click to collapse
I never installed CM's Superuser. But I did try installing SuperSU ;P. Do I need to reflash everything again?
hidea said:
I never installed CM's Superuser. But I did try installing SuperSU ;P. Do I need to reflash everything again?
Click to expand...
Click to collapse
Updated my reply above.
rob43 said:
Updated my reply above.
Click to expand...
Click to collapse
Sorry, I'm confused!
After flashing the fastboot image, what do I do? The image came with Superuser pre-installed?

FireTV 2 (sloane) Recovery [v6] - 3.0.0-5

It's finally here! Recovery for the Fire TV 2. This is based off of TWRP and the way versions will work is I will increment the last digit in the version as I make updates. So 3.0.0-1 is my first release based off of 3.0.0. The downloads will be numbered starting at v1, and at the bottom of the post it will explain what is contained within each version.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As usual, this WILL void your warranty and I am NOT responsible for anything you do with this. Installing it properly won't brick your Fire TV, but doing stupid things with it might.
Installing this requires root. If you are not rooted, please see my FireTV 2 Recovery Installer page.
Installation
You can copy the files to /sdcard, a USB storage device, or an sdcard. I will be using /sdcard in the instructions, but you can replace it with /storage/usbotg for USB or /storage/sdcard1 for an sdcard.
Copy the zip file to your destination.
Connect adb
Code:
adb connect IPADDRESS
Open an adb shell
Code:
adb shell
Run the zip file (replace vX with the actual version you downloaded). This will automatically run su, so make sure to accept the prompt if necessary.
Code:
sh /sdcard/firetv2_recovery_vX.zip
Reboot
Upgrade
You may repeat this to upgrade to a newer version, or you can install an updated pre-rooted rom, as I will be uploading new versions of those with every version of recovery.
Notes
This includes bootmenu. For everyone that loved the old FireTV 1 bootmenu with Comic Sans, I'm sorry to disappoint you, but the Comic Sans is gone. When the FireTV boots, it will present you with the bootmenu where you can leave it alone and it will boot normally or you can select recovery and it will boot in to recovery. You do need a USB keyboard to interact with the bootmenu. To force it to boot in to Recovery, you can create a file /cache/bootmenu_recovery.
DHCP for Ethernet is enabled, and if there is enough demand I may add in wifi at some point. The IP address should show up in the top left corner.
USB storage, USB keyboard/mice, and sdcards should all work. Hotplugging works, so you should be able to plug and unplug devices as needed.
You can use a USB keyboard, mouse, or the mouse emulator to interact with it. To use a keyboard, you can use the arrow keys to move the cursor and the enter key to select buttons. Sliders don't require sliding, so you can just hit enter/click on them. To use the mouse emulator, use adb shell and then run the program mouse and follow the instructions.
ROMs
Recovery must be included in all ROMs. If you want to develop a ROM, please contact me about including recovery in it.
Kernels
The bootloader is locked and you cannot flash kernels. If you do attempt to flash a kernel, you will brick it.
Installing zips
You can push zips to /sdcard, put it on a USB storage, put it on an sdcard, or use adb sideload. Do note you need adb version 1.0.32 to use adb sideload.
Stuck in a loop?
If you cannot boot normally and keep going back to the bootmenu, wipe Cache from Wipe -> Advanced Wipe.
If that doesn't work, ensure Cache is not mounted from in the 'Mount' menu and run this from an adb shell:
Code:
mke2fs /dev/block/platform/mtk-msdc.0/by-name/cache
Source Code
You can find the source code here:
https://github.com/androidrbox/sloane-2ndinit
https://github.com/androidrbox/android_bootable_recovery
WARNINGS
It is extremely important you never reboot after a failure. This will most likely lead to a brick. If recovery is hung, you can use adb shell to run
Code:
killall recovery
to restart it
It is also extremely important to never reboot after wiping /system.
If you wind up bricking, you must use the Unbrick Image to unbrick.
Finally, thanks to everyone who has donated to me and those that helped to get me my FireTV 2.
Changelog and Downloads:
April 8, 2016 - v6 (md5sum: 79c1a3efbac86618fa2cdbb4901fbd77)
This should prevent auto flashing amazon updates.
This includes 2ndinit version dee776 and TWRP version 3.0.0-5.
February 14, 2016 - v5 (md5sum: 16c957c86f1f61160e14a55819610707)
This should fix the problems certain keyboard were having in recovery.
This includes 2ndinit version dee776 and TWRP version 3.0.0-4.
February 12, 2016 - v4 (md5sum: 15c6d375607839cac4b186a2b68b8b0d)
This includes 2ndinit version 743aa4 and TWRP version 3.0.0-3.
These are just changes related to the unbricking image. No other functional changes.
February 8, 2016 - v3 (md5sum: b39a4dbe0c19080a97f602f37fda63ec)
This includes an updated script. You can now just run the zip instead of needing the zip and the script.
This includes TWRP 3.0.0-2.
Added a reboot recovery option in addition to reboot system. Now reboot system will reboot straight in to Android. Reboot recovery will reboot to the bootmenu.
Fixed restoring backups.
This includes the same version of 2ndinit.
February 7, 2016 - v2 (md5sum: 762621104d158d7ce4010bea725f7181)
This includes an automated script.
This has the same versions of 2ndinit and recovery as v1.
February 6, 2016 - v1 (md5sum: 7be673dd24489080eacdd0ad00feda51)
This comes with 2ndinit version fe3362 and recovery version 3.0.0-1
Awesome work!
Will try immediately! Thanks for posting this on weekend
Thankyou Rbox, i just saw this & its put a smile on my face. Just one question do you need to reblock the updates after recovery & root have been installed? Thanks
deanr1977 said:
Thankyou Rbox, i just saw this & its put a smile on my face. Just one question do you need to reblock the updates after recovery & root have been installed? Thanks
Click to expand...
Click to collapse
As long as you don't wipe data, updates remain blocked.
rbox said:
As long as you don't wipe data, updates remain blocked.
Click to expand...
Click to collapse
I downloaded both the zips from the Github, im already rooted on the previously rooted software & updates are blocked, im not sure if to wait for AFTV News to do a guide or not, im clued up but not to ADB or Terminal savey so i gonna look at the readme & see if i should try it tonight? I rooted with the video guide before & it was a breeze, i know it sounds easy but want to do it right. Can you give me a little more info on connecting the ADB or Terminal please if you arnt busy?
deanr1977 said:
I downloaded both the zips from the Github, im already rooted on the previously rooted software & updates are blocked, im not sure if to wait for AFTV News to do a guide or not, im clued up but not to ADB or Terminal savey so i gonna look at the readme & see if i should try it tonight? I rooted with the video guide before & it was a breeze, i know it sounds easy but want to do it right. Can you give me a little more info on connecting the ADB or Terminal please if you arnt busy?
Click to expand...
Click to collapse
If you don't want to deal with adb, use the installer.
rbox said:
If you don't want to deal with adb, use the installer.
Click to expand...
Click to collapse
Thanks mate, looking at this now. Will it delete any data on the system? Kodi, Amazon apps or External Sd card? Thanks in advance
deanr1977 said:
Thanks mate, looking at this now. Will it delete any data on the system? Kodi, Amazon apps or External Sd card? Thanks in advance
Click to expand...
Click to collapse
Installing recovery and roms does nothing to data.
rbox said:
It's finally here! Recovery for the Fire TV 2. This is based off of TWRP and the way versions will work is I will increment the last digit in the version as I make updates. So 3.0.0-1 is my first release based off of 3.0.0. The downloads will be numbered starting at v1, and at the bottom of the post it will explain what is contained within each version.
As usual, this WILL void your warranty and I am NOT responsible for anything you do with this. Installing it properly won't brick your Fire TV, but doing stupid things with it might.
Installing this requires root. If you are not rooted, please see my FireTV 2 Recovery Installer page.
Installation
Copy the contents of the zip to /sdcard on your FireTV.
Remount /system as read-write
Code:
mount -o remount,rw /system
Make the /system/recovery directory
Code:
mkdir /system/recovery
Copy 2ndinitstub
Code:
cp /sdcard/2ndinitstub /system/bin/ext4_resize
Copy 2ndinit
Code:
cp /sdcard/2ndinit /system/recovery/
Copy the recovery ramdisk
Code:
cp /sdcard/ramdisk-recovery.cpio /system/recovery/
Remount /system as read-only
Code:
mount -o remount,ro /system
Upgrade
You may repeat this to upgrade, but it is easier to just install a new pre-rooted rom. Every update for recovery I will make a new rom.
Notes
This includes bootmenu. For everyone that loved the old FireTV 1 bootmenu with Comic Sans, I'm sorry to disappoint you, but the Comic Sans is gone. When the FireTV boots, it will present you with the bootmenu where you can leave it alone and it will boot normally or you can select recovery and it will boot in to recovery. You do need a USB keyboard to interact with the bootmenu. To force it to boot in to Recovery, you can create a file /cache/bootmenu_recovery.
DHCP for Ethernet is enabled, and if there is enough demand I may add in wifi at some point. The IP address should show up in the top left corner.
USB storage, USB keyboard/mice, and sdcards should all work. Hotplugging works, so you should be able to plug and unplug devices as needed.
You can use a USB keyboard, mouse, or the mouse emulator to interact with it. To use a keyboard, you can use the arrow keys to move the cursor and the enter key to select buttons. Sliders don't require sliding, so you can just hit enter/click on them. To use the mouse emulator, use adb shell and then run the program mouse and follow the instructions.
ROMs
Recovery must be included in all ROMs. If you want to develop a ROM, please contact me about including recovery in it.
Kernels
The bootloader is locked and you cannot flash kernels. If you do attempt to flash a kernel, you will brick it.
Installing zips
You can push zips to /sdcard, put it on a USB storage, put it on an sdcard, or use adb sideload. Do note you need adb version 1.0.32 to use adb sideload.
Source Code
You can find the source code here:
https://github.com/androidrbox/sloane-2ndinit
https://github.com/androidrbox/android_bootable_recovery
Finally, thanks to everyone who has donated to me and those that helped to get me my FireTV 2.
Changelog and Downloads:
Februrary 6, 2016 - v1 (md5sum: 7be673dd24489080eacdd0ad00feda51)
This comes with 2ndinit version fe3362 and recovery version 3.0.0-1
Click to expand...
Click to collapse
the commands are entered through adb correct......Also, once recovery is installed can I flash either of your pre-rooted roms or do I have to flash the version I'm currently on....i.e. if I'm on 5.0.4 I can only flash 5.0.4
thanks again for your great work!
dk1keith said:
the commands are entered through adb correct......Also, once recovery is installed can I flash either of your pre-rooted roms or do I have to flash the version I'm currently on....i.e. if I'm on 5.0.4 I can only flash 5.0.4
thanks again for your great work!
Click to expand...
Click to collapse
Yes adb shell. You can flash either version.
rbox said:
Yes adb shell. You can flash either version.
Click to expand...
Click to collapse
Awesome thanks rbox
Not working for me. everything is copied over and after reboot there is no menu. Amazon white logo for 5 seconds, than the colored logo and system is booted in less than 15 seconds.
aboshi said:
Not working for me. everything is copied over and after reboot there is no menu. Amazon white logo for 5 seconds, than the colored logo and system is booted in less than 15 seconds.
Click to expand...
Click to collapse
Same here. No boot menu. Reboot to recovery brings up the stock recovery as well.
dk1keith said:
Awesome thanks rbox
Click to expand...
Click to collapse
first command: mount -o remount,rw /system
in adb shell returns a mountermission denied
aboshi said:
Not working for me. everything is copied over and after reboot there is no menu. Amazon white logo for 5 seconds, than the colored logo and system is booted in less than 15 seconds.
Click to expand...
Click to collapse
retyre said:
Same here. No boot menu. Reboot to recovery brings up the stock recovery as well.
Click to expand...
Click to collapse
Both of you please run:
Code:
ls -lZ /system/bin/ext4_resize /system/recovery
dk1keith said:
first command: mount -o remount,rw /system
in adb shell returns a mountermission denied
Click to expand...
Click to collapse
You need to be root...
rbox said:
Both of you please run:
Code:
ls -lZ /system/bin/ext4_resize /system/recovery
You need to be root...
Click to expand...
Click to collapse
you mean by typing su?
dk1keith said:
you mean by typing su?
Click to expand...
Click to collapse
Yes, by typing su.
Code:
-rwxr-xr-x root shell u:object_r:system_file:s0 ext4_resize
-rw------- root root u:object_r:system_file:s0 2ndinit
-rw------- root root u:object_r:system_file:s0 ramdisk-recovery.cpio
aboshi said:
Code:
-rwxr-xr-x root shell u:object_r:system_file:s0 ext4_resize
-rw------- root root u:object_r:system_file:s0 2ndinit
-rw------- root root u:object_r:system_file:s0 ramdisk-recovery.cpio
Click to expand...
Click to collapse
Hrm... can you run
Code:
ls -l /system/bin/ext4_resize /system/recovery
also?

[RECOVERY] TWRP 3.0.0.0 for D605

Team Win Recovery Project v3.0.0.0 for D605
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
HOW TO INSTALL:
Flash from old recovery:
Reboot to your current recovery.
And flash the archive.
Flash recovery.img without custom recovery:
Extract contents on your PC
Copy loki_flash and recovery.img to you phone's SD card via MTP connection
Download and start Android Terminal Emulator from Play Store
From terminal emulator type: $ su
Then type (assuming files from zip were copied to external SD card root) :
# cp /storage/external_SD/loki_flash /storage/external_SD/recovery.img /data/local/tmp
# cd /data/local/tmp
# chmod 777 loki_flash
# ./loki_flash recovery recovery.img
# reboot recovery
DOWNLOAD:
Link to flash from recovery:
https://mega.nz/#!fo8DCDbb!wvN9GTN7xzuTGnNMBfu4UwmAo7culclt88qb-qJoZLI
Link to flash without recovery:
https://mega.nz/#!y1dk0KwS!HAwU-Pi6jgfQPe3c1yID9WmX76X_afdNpTpToPbfqSA
STATUS:
Stable (but I have not tested)
Nice work, thx (will you end cm12?)
I Have problem: Loki aboot version does not match device. (LG D605 kitkat 4.4.2) Root:yes
Downgrade to jb
@JackPOtaTo try with another version of windows, i had the same on win7, no problem in win8
Sent with my CM11 Lg D605
Ag0n1a said:
@JackPOtaTo try with another version of windows, i had the same on win7, no problem in win8
Sent with my CM11 Lg D605
Click to expand...
Click to collapse
I have win 10. And i bricked (Hard) LG l9 II
As far as I know this device is not possible to hardbrick.
Again, if your problem is "Loki aboot version does not match device" then your device is not bricked probably
Ag0n1a said:
As far as I know this device is not possible to hardbrick.
Again, if your problem is "Loki aboot version does not match device" then your device is not bricked probably
Click to expand...
Click to collapse
I don't know where you guys get your information from but stop saying phones are not possible to hard brick and spread this word around. It is very easy to hardbrick any phone with root.
I will go just in a little bit of detail to show you.
How does your computer boot?
The hardware you have (CPU, GPU, Memory etc) are searched for (physical addresses) by the motherboard by the BIOS. Delete or erase the BIOS and I bet you any sum that your computer will stop doing anything (starts and sits idle just fans spinning).
With this analogy the BIOS of any mobile device is the bootloader. In the bootloader, that is located on the eMMC (embedded Multi Media Controller; like an SSD but with the controller of memory in the silicon die). eMMC is partitioned like a hard disk.
Your phone has an integrated Primary Loader in the CPU (this is what Qcom 9008 is). By shorting pins you change the boot order. If you short correct pins you can send data into memory (RAM) from the CPU and then write it on the eMMC (if you have the correct communication). This is where the HEX programmer comes in. This is how Qualcomm tools know how to communicate with the SOC.
The 2nd loader is on the eMMC. By default all CPU's boot from eMMC. SBL1->aboot and so on is the bootchain. Where hardware is initialized and recognized. Destroy and of those partitions and you will have a hardbrick (either fallback to 9008 automatically because eMMC is empty or not recognized at all).
Well I ended up giving you kind of a full information. Just stop trowing around this thing "phones can't be hardbricked". Hardbrick describes the state where a phone can't enter the last emergency mode provided by the manufacture (Emergency in this case). And generally buttons don't work, screen isn't either and so on.
Never said that phones cannot be hardbricked....
I said that installing this rom will not hardbrick your phone, cuz only contain kernel and syspartition... plus, if the software prevents u from make changes because the aboot version doesn't match, how can u hardbrick it?
Thanks for the explanation though, learned couple of spec terms...
Ag0n1a said:
Never said that phones cannot be hardbricked....
I said that installing this rom will not hardbrick your phone, cuz only contain kernel and syspartition... plus, if the software prevents u from make changes because the aboot version doesn't match, how can u hardbrick it?
Thanks for the explanation though, learned couple of spec terms...
Click to expand...
Click to collapse
If you flash an aboot version that does fail the check of the bootchain you have a hardbrick.
A
neutrondev said:
If you flash an aboot version that does fail the check of the bootchain you have a hardbrick.
Click to expand...
Click to collapse
With this method you can not, the moment it says the aboot version is different it doesn't allow the copy of it. I had this error 5-6 times before I could successfully change the aboot and all those times in between my phone was always turning on as normal...
If then you are able to flash an aboot version that doesn't match then u r unlucky...
Anyway I'm for sure not as expert as you, but I'm just reporting my experience
Ag0n1a said:
A
With this method you can not, the moment it says the aboot version is different it doesn't allow the copy of it. I had this error 5-6 times before I could successfully change the aboot and all those times in between my phone was always turning on as normal...
If then you are able to flash an aboot version that doesn't match then u r unlucky...
Anyway I'm for sure not as expert as you, but I'm just reporting my experience
Click to expand...
Click to collapse
Yeah you are right. That is just a message it will not flash it for you. But if you see that message and try to flash a lower aboot without flashing full KDZ you are in big trouble.
Can someone "Loki-fy" or something on TWRP because i am in need to use cwm 6.0.5.1 by varcian
AWESOME1092387456 said:
Can someone "Loki-fy" or something on TWRP because i am in need to use cwm 6.0.5.1 by varcian
Click to expand...
Click to collapse
For me the installation works but don't install it... i've installed cm12 and it sayed secure booting failed
and backup/restore doesn't work, it corrupted /data partition but i resolved it.
Kaszke said:
Downgrade to jb
Click to expand...
Click to collapse
How? I couldn't find a working link for a stock jb.
Cristi73 said:
How? I couldn't find a working link for a stock jb.
Click to expand...
Click to collapse
http://lg-phone-firmware.com/index.php?id_mod=37
Find the kdz that coresponds to your region/carrier.
goooooooooD!!!! amazing job ))))
JackPOtaTo said:
I Have problem: Loki aboot version does not match device. (LG D605 kitkat 4.4.2) Root:yes
Click to expand...
Click to collapse
hey here is the solution body
II Flash
GOTO D605 RECOVRY (folder) hold shift and right click on the mouse then open window command here
then copy the commands on the cmd
you need to have adb driver installed and here the download link http://www.mediafire.com/download/u6pdpy77sonjyqh/D605+RECOVRY.rar
1 adb push aboot.img /data/local/tmp
2 adb shell
3 su
4 dd if=/data/local/tmp/aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
4 exit
5 exit
6 adb push loki_flash /data/local/tmp
7 adb push recovery.img /data/local/tmp
8 adb shell
9 su
10 cd /data/local/tmp
11 chmod 777 loki_flash
12 ./loki_flash recovery recovery.img
13 reboot recovery
Hi all! I followed the procedure in terminal emulator from JB with root (through impactor)and I installed successfully twrp.
Then I installed CM11 by Varcain but the phone gives me the message "Secure booting Error! Cause: boot certification verify" .. I really can't figure out the problem after hours of search... can someone help me please?
Now I have to use kdz to reinstall JB?
EDIT: Sorry, The solution is easy, I must unlock the bootloader before flashing cm11... I forgot it! So the problem is not related to twrp
sedi21 said:
Hi all! I followed the procedure in terminal emulator from JB with root (through impactor)and I installed successfully twrp.
Then I installed CM11 by Varcain but the phone gives me the message "Secure booting Error! Cause: boot certification verify" .. I really can't figure out the problem after hours of search... can someone help me please?
Now I have to use kdz to reinstall JB?
EDIT: Sorry, The solution is easy, I must unlock the bootloader before flashing cm11... I forgot it! So the problem is not related to twrp
Click to expand...
Click to collapse
but how did you unlock it? because i don't know how to unlock mine and i don't think its possible

Categories

Resources