I have successfully rooted my LG G2 (D802).
But I can't seem to install a custom recovery (CWM, TWRP).
I tried following these steps:
Download openrecovery-twrp-2.6.3.2-g2d802.img
Save it in the IORoot folder (v25) as "recovery.img"
Download loki_flash file from Github bin folder, place in IORoot folder.
In the IORoot folder, hold shift, right click, and open terminal and type in the following lines one at a time:
Code:
adb push loki_tool /data/local/tmp/loki_tool
adb push recovery.img /data/local/tmp/recovery.img
adb shell
su
cd /data/local/tmp
chmod 777 loki_tool
./loki_tool flash recovery /data/local/tmp/recovery.img
exit
exit
adb reboot recovery
But it gave the following error:
Code:
Loki tool v2.1
[-] Loki aboot version does not match device.
1|[email protected]:/data/local/tmp # exit
1|[email protected]:/ $
So I tried another method. I installed the "freegee" app from google play, but when it opens, it says "Your devices specific software version of D80220d is not currently supported".
What do I need to do to load a custom recovery?
Going to my phone's settings > About phone shows the following:
Model number: LG-D802
Android version 4.4.2
Kernel version 3.4.0
Build number: KOT49I.D80220d
Software version: D80220d-EUR-XX
All I had to do was install AutoRec.
http://forum.xda-developers.com/showthread.php?t=2715496
Related
Mod Edit: Unstickied, placed link in wiki:http://forum.xda-developers.com/wiki/index.php?title=Nexus_One Thanks
This is an alternative approach of rooting the Nexus without touching the bootloader.
-no downgrade neccessary
-no battery modification neccessary
-no messing around with SD card slot
-you don't even have to open your phone...
Working and confirmed for ALL ROMs, including European Vodafone EPF30/FRF91, Korean FRF91, AT&T/T-Mo Stock including FRF91
-------
Credits:
-------
- The Android Exploid Crew:
http://c-skills.blogspot.com/2010/07/android-trickery.html
- Amon_RA
- cyanogen
-------
Notes:
-------
- The exploit wasn't found by me (see credits), I just implemented it as a proof of concept for the Nexus One
- Basically this method should work on all currently known ROM versions.
- I tested it on EPF30, Korean FRF91, Vodafone FRF91, US Stock FRF91.
- As usual when doing this kind of stuff: DO THIS AT YOUR OWN RISK.
- It could even work on other Android devices as long as their system partition is at
/dev/block/mtdblock3/ with yaffs2 file system and there is still some space left on the system partition (without any changes).
-------
Prerequisites:
-------
- Locked Nexus One
- Latest Android SDK incl. USB drivers
- Working ADB
- The file "freenexus.zip"
edit:
get it here:
http://multiupload.com/MVT98F5HBY
or
http://dl.dropbox.com/u/1327667/freenexus.zip
MD5: 947C20222056D7C070733E7FCF85CF15
-------
Step-by-step guide:
-------
1. install android sdk & USB drivers
2. extract the content of the zip file into the tools directory of SDK (i.e. \android-sdk-windows\tools)
-> For all Newbies: Take care that you extract the files directly to the tools folder and don't create a new subdirectory freenexus within tools!!! If you did, delete the folder and extract again!!! Check twice that there is no FOLDER freenexus in your tools directory before you continue!!!
3. open a command prompt (Windows: Start, Run, "cmd", OK; Linux: Terminal)
4. change to SDK tools directory (i.e. cd \android-sdk-windows\tools)
5. connect Nexus to USB and check if debugging mode is activated
(Settings/Application/Development/USB Debugging)
6. run "adb devices" in shell and see if there is a device listed. if not back to step 5 or reinstall USB-drivers
7a. for Windows: run "freenexus.bat" in command shell (this copies the neccessary files to /data/local/tmp)
7b. for Linux or manual installation: run the following commands
Code:
adb push freenexus /data/local/tmp/freenexus
adb push Superuser.apk /data/local/tmp/Superuser.apk
adb push su /data/local/tmp/su
adb push busybox /data/local/tmp/busybox
adb shell chmod 755 /data/local/tmp/freenexus
adb shell chmod 755 /data/local/tmp/busybox
8. run the following commands:
Code:
adb shell
(you should see a "$" prompt now)
cd /data/local/tmp
9. on your phone go to a screen where you can easily toggle wifi (widget or settings/wireless)
10. be prepared to toggle wifi immediately after you execute the next step
11. run
Code:
./freenexus
12. toggle wifi on
13. you should see something like that:
[*] Android local root exploid (C) The Android Exploid Crew
[*] Modified by ak for HTC Nexus One
[+] Using basedir=/sqlite_stmt_journals, path=/data/local/tmp/freenexus
[+] opening NETLINK_KOBJECT_UEVENT socket
[+] sending add message ...
[*] Try to invoke hotplug now, clicking at the wireless
[*] settings, plugin USB key etc.
[*] You succeeded if you find /system/bin/rootshell.
[*] GUI might hang/restart meanwhile so be patient.
13b) if you get "permission denied" error, you have most likely not followed the big red newbie hint after point 2. check this by entering "ls -l", if you see a "drwxr-xr-x" and not "-rwxr-xr-x" in front of the line where freenexus is listed you did not follow properly. Search the posts in the thread on how to correct this.
14. run
Code:
rootshell
15. if you succeeded you will be asked for a password, if not try again from step 10
16. enter the password "freenexus"
17. now you should see a "#" as a prompt -> you are root now
18. run the following commands:
Code:
./busybox cp busybox /system/bin
chmod 4755 /system/bin/busybox
busybox cp Superuser.apk /system/app
busybox cp su /system/bin
chmod 4755 /system/bin/su
rm /system/bin/rootshell
exit
exit
19. Check if you keep root rights:
Code:
adb shell
su
20. after you executed the su command the Superuser app on your device should ask you for allowance
21. you should see the "#" prompt again, if you didn't get that try su again
22. done
-------
Comments:
-------
- General
If you are not planning to wipe your data partition (what you probably will do when installing CM6 first time) you should think about deleting all the temp files still lying in /data/local/tmp (for safety reasons and to have more space on /data):
Code:
adb shell
cd /data/local/tmp
rm busybox
rm su
rm Superuser.apk
rm freenexus
rm flash_image (will only exist if you executed the steps below in recovery section)
- Installation of Custom Recovery
If you only want root rights you are done here. If you want to install custom ROMs you have to install
a custom recovery first. Easiest way would be to download "ROM Manager" from the market. There are plenty of tutorials on how to install custom recovery/ROM at xda.
Edit: It is safer to install the recovery manually. In this case or for those of you running into problems with installing custom recovery with ROM Manager (doesn't stick) you can continue with
these steps (without remount of system partition, now tested successfully):
1) Download recovery-RA-nexus-v1.7.0.1.img to the root directory of your SD-Card
- Note: UnMount your SD-Card after copying these files, but keep your phone plugged in
- or don't mount SD-Card at all and push the file via adb to /sdcard
2) Save file "flash_image" to sdk tools directory:
3) In your terminal run
Code:
adb push flash_image /data/local/tmp/flash_image
adb shell
su
- At this point, it will hang until you choose "Allow" on your phone with the SuperUser app pop-up
- $ should now be replaced with #
5) run the following commands:
Code:
[COLOR="Red"]mount -o rw,remount /dev/block/mtdblock3 /system[/COLOR]
cd /data/local/tmp
chmod 755 flash_image
[COLOR="Red"]./flash_image recovery /sdcard/recovery-RA-nexus-v1.7.0.1.img[/COLOR]
rm /system/etc/install-recovery.sh
rm /system/recovery-from-boot.p
(and if everything worked fine:)
rm flash_image
Alternatively you can continue with step 9 and then steps 16-24 from the old rooting method tutorial
to manually install Amon_RA's recovery. You will also need the file flash_image for that (link taken from HBOOT thread).
- HBOOT
If you rooted from a Korean Rom or have installed the latest Vodafone Rom via PASSIMG you probably have
HBOOT 0.35 which makes it currently difficult to install Cyanogenmod (there is an assertion failure in the install script, at least with CM6 RC1/2. Maybe future versions of CM6 will include HBOOT 0.35 in the script) or other custom ROMs. (You are still on 0.33 if you just installed the Vodafone OTA Update)
There is a tutorial to revert HBOOT here:
http://forum.xda-developers.com/showthread.php?t=726258
Instead of using the EPF30 image you can also use any other PASSIMG file (at least if it has HBOOT 0.33,
otherwise this step wouldn't make sense...)
Note that when flashing a PASSIMG with a different HBOOT version there is a reboot after the HBOOT has been flashed, then after reboot the PASSIMG will be loaded again and the rest of the image will be flashed.
To check HBOOT and Radio version: press and hold trackball while turning on the phone. To exit select Reboot with Vol+/- and press Power button.
Caution:
After you have reverted your HBOOT, you have lost your root rights and you are back on stock recovery.
But you can (or have to) repeat the above procedure to get root rights back.
Edit:
The downgrading also downgrades your radio!!! Before installing CM6 you have to flash a Froyo Radio!
Latest one can be found here:
http://forum.xda-developers.com/showthread.php?t=723839
-------
Troubleshooting:
-------
After trying to flash a custom ROM with ROM Manager one user wasn't able to boot the phone normally and also no longer able to boot to recovery. In this rare case try to download a compatible PASSIMG file:
For example EPF30 (Europe Vodafone 2.1)
http://shipped-roms.com/shipped/Pas...ogle_WWE_1.14.1700.1_EPF30_release_signed.zip
or FRF91 (Europe Vodafone 2.2):
http://shipped-roms.com/shipped/Pas...on_VF_2.15.151.5_R_FRF91_MFG_Shipment_ROM.zip (<-this one is currently a zip in zip. You have to extract it once to get the working PASSIMG.zip)
(Appropriate US-PASSIMGs can also be found on shipped-roms.com, most likely EPE76)
Rename the file to PASSIMG.zip (case sensitive, Windows users take care that the file isn't called PASSIMG.zip.zip hidden extension)
Copy it to main folder of SD card.
Boot phone into Bootloader mode (press and hold trackball when turning on the phone, until fastboot mode starts)
Select Bootloader mode by pressing power button.
The bootloader should then start to analyse the PASSIMG.zip and ask you afterwards to install it.
You're phone (not your SD) will be completely wiped after the procedure but should work again (and can be rooted again...)
sweet!! been waiting for this! will try it tomorrow as soon as i wake up! will report back then!
edit: i cant download freenexus.zip maybe use another hoster?
file section edited.
Great tutorial ! Waiting for some feedbacks
(file link doesn't work)
dolomiti7 said:
file section edited.
Click to expand...
Click to collapse
On the left I can see just an empty folder named "SmartDrive"
link doesn't work
dolomiti7 said:
-> after clicking on "Smartdrive Gastzugang starten" you might get an error message, but after klicking ok on the error message
you should be able to access the folder "nexus" on the left side of the window anyway
Click to expand...
Click to collapse
No way! Can't do anything even after i press ok on the error message
if you click on that there should be a subfolder "nexus" that should be clickable too. at least it works here... anyway. someone wants to upload the file to a hoster? rapidshare... contact me
for the early adaptors (will only work 10 times):
rapidshare.com/files/409266634/freenexus.zip
MD5: 947C20222056D7C070733E7FCF85CF15
multiple download sites!:
http://www.multiupload.com/MVT98F5HBY
or here:
http://dl.dropbox.com/u/1327667/freenexus.zip
thank you. added the link.
This worked flawlessly.
Massive thanks.
Hi, I have a Italian Vodafone Nexus One with FRF91, i have followed all the steps and now in my apps there is Superuser Permission with green light. It means that i have root rights? Can I install Cyanogen Mod now? Thanks, excuse my English.
Worked perfectly on a stock AT&T N1 with FRF91. Thanks!
Excellent tutorial step by step...great work!
Can i change the password at the end?
So once gaining root, I can flash a custom recovery with rom manager without braking/unlocking the boot loader?
@fc_themaster:
if the superuser app popped up at step 19/20 then you have root rights. you can try to install ROM Manager from the market and install a custom recovery with that porgram. it also needs root rights so superuser should pop up again at that point.
@PSeeCO: you don't need to change a password. the password was only used for the temporary rootshell which you (hopefully) deletetd with the command "rm /system/bin/rootshell" in step 18. From that point on root rights are controlled via the Superuser app. If you install an already rooted custom ROM it is obsolete anyway.
@jivemaster: yes, we can! just use ROM Manager from the market to install custom recovery.
dolomiti7 said:
@PSeeCO: you don't need to change a password. the password was only used for the temporary rootshell which you (hopefully) deletetd with the command "rm /system/bin/rootshell" in step 18. From that point on root rights are controlled via the Superuser app. If you install an already rooted custom ROM it is obsolete anyway.
Click to expand...
Click to collapse
Perfect, thank you so much!
C:\Users\Ryan>cd
C:\Users\Ryan
C:\Users\Ryan>cd\AndroidSDK\tools
C:\AndroidSDK\tools>adb devices
List of devices attached
HT02TL900527 device
C:\AndroidSDK\tools>adb shell flash_image recovery /sdcard/recov1.img
error opening /sdcard/recov1.img: No such file or directory
I keep getting this error, but the file is in the root. Any help much appreciated
Flash it via Better Terminal Emulator
Code:
$ su
# flash_image recovery /sdcard/recovery-RA-hero-v1.7.0.1.img
Its for latest recovery .. if you flashing old one then change name .Also if you flashing the new recovery then Update.zip file is available flash it via recovery menu for more info see here: - [Recovery ROM] [15-August-2010] RA-hero-v1.7.0.1
THIS IS MY FIRST THREAD IN A DEVELOPMENT SECTION - forgive me if I do something wrong, or if the subject has already been discussed.
It took me a while to figure this out, and I hope it helps others.
I SHALL DESCRIBE HOW TO LOKI ANY recovery.img FOR USE ON VERIZON SAMSUNG GALAXY S4 MDK PHONE.
Clockworkmod posts new recovery img files for our phone here:
http://www.clockworkmod.com/rommanager
However these recovery image files are not LOKI patched yet.
First one must create an aboot.img file from the phone.
This is something which must be run on the rooted phone.
It is basically two lines:
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/data/local/tmp/aboot.img
chmod 644 /data/local/tmp/aboot.im
Then once the aboot.img file has been created, it needs to be copied up to your Ubuntu-Linux PC.
One needs the "loki_patch-lilnux-x86_64" executable file available from the github:
https://github.com/djrbliss/loki
Then the command to read a recovery.img file and create a loki version is:
./loki_patch-linux-x86_64 recovery aboot.img recovery.img recovery_loki.img
The following is a shell file for performing the above work with ample comments about the procedure:
# run_getAboot.sh
# Purpose: create a aboot.img file on the Verizon S4 phone
# to then be copied back to the linux PC
# so a kernel or recovery can be loki patched.
#
# This shell file must be:
# Copied to the Verizon S4 into folder /data/local/tmp
# for example from linux pc : adb push run_getAboot.sh /data/local/tmp
# Give it executable priviledges - I did this using ES File Explorer
# Run it from "Terminal Emulator"
# su
# ./run_getAboot.sh
#
#
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/data/local/tmp/aboot.img
chmod 644 /data/local/tmp/aboot.im
#
# After this, the aboot.img file should be copied back to the linux pc
# for example from linux pc: adb pull /data/local/tmp/aboot.img aboot.img
# One then gets the loki_patch-linux-x86_64 file from the loki-doki github
# The github is located here: https://github.com/djrbliss/loki
# look under the "bin" folder.
# Now a recovery can be loki-doki modified.
# We now have the aboot.img created from the Verizon S4 phone,
# and we have a recovery.img which needs to be loki modified.
# The following command will create the recovery_loki.img file:
# ./loki_patch-linux-x86_64 recovery aboot.img recovery.img recovery_loki.img
#
# The recovery_loki.img file can be installed on the Verizon S4 phone.
#
Now, I also wanted to make a ZIP file which a custom recovery can run to LOKI and install a non-loki recovery.img file.
The LOKI operation will be performed while the ZIP file is being installed.
I used the following loki-doki.zip file as an example found here:
http://rootzwiki.com/topic/41841-lo...tom-boot-image-on-att-and-verizon-galaxy-s-4/
I added CWM touch version 6.0.4.4 recovery.img file, and modified the script to LOKI the recovery.img file rather than the currently installed kernel/boot.
Here is my completed sample zip file: https://db.tt/xLi6c4dd
When a new version of a recovery becomes available, one just renames it recovery.img and replaces the recovery.img file which is in the zip file. Then one can flash to the new version of the recovery.
The script in this zip file will only work on I337UCUAMDB, I337UCUAMDL, and I545VRUAMDK bootloaders.
Credits to: attn1 at rootzwiki for the ZIP file which I modified.
and of course to drjbliss's LOKI github https://github.com/djrbliss/loki
Rom Manager app also does it. GooManager only does TWRP
loonie01 said:
Rom Manager app also does it. GooManager only does TWRP
Click to expand...
Click to collapse
Last time I checked, Rom Manager will not LOKI and install the touch version for free - even though the unLoki'd img file is available for free from the website.
Yeah not for free
Sent from my SCH-I545 using Tapatalk
HowardZ said:
THIS IS MY FIRST THREAD IN A DEVELOPMENT SECTION - forgive me if I do something wrong, or if the subject has already been discussed.
It took me a while to figure this out, and I hope it helps others.
I SHALL DESCRIBE HOW TO LOKI ANY recovery.img FOR USE ON VERIZON SAMSUNG GALAXY S4 MDK PHONE.
Clockworkmod posts new recovery img files for our phone here:
http://www.clockworkmod.com/rommanager
However these recovery image files are not LOKI patched yet.
First one must create an aboot.img file from the phone.
This is something which must be run on the rooted phone.
It is basically two lines:
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/data/local/tmp/aboot.img
chmod 644 /data/local/tmp/aboot.im
Then once the aboot.img file has been created, it needs to be copied up to your Ubuntu-Linux PC.
One needs the "loki_patch-lilnux-x86_64" executable file available from the github:
https://github.com/djrbliss/loki
Then the command to read a recovery.img file and create a loki version is:
./loki_patch-linux-x86_64 recovery aboot.img recovery.img recovery_loki.img
The following is a shell file for performing the above work with ample comments about the procedure:
# run_getAboot.sh
# Purpose: create a aboot.img file on the Verizon S4 phone
# to then be copied back to the linux PC
# so a kernel or recovery can be loki patched.
#
# This shell file must be:
# Copied to the Verizon S4 into folder /data/local/tmp
# for example from linux pc : adb push run_getAboot.sh /data/local/tmp
# Give it executable priviledges - I did this using ES File Explorer
# Run it from "Terminal Emulator"
# su
# ./run_getAboot.sh
#
#
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/data/local/tmp/aboot.img
chmod 644 /data/local/tmp/aboot.im
#
# After this, the aboot.img file should be copied back to the linux pc
# for example from linux pc: adb pull /data/local/tmp/aboot.img aboot.img
# One then gets the loki_patch-linux-x86_64 file from the loki-doki github
# The github is located here: https://github.com/djrbliss/loki
# look under the "bin" folder.
# Now a recovery can be loki-doki modified.
# We now have the aboot.img created from the Verizon S4 phone,
# and we have a recovery.img which needs to be loki modified.
# The following command will create the recovery_loki.img file:
# ./loki_patch-linux-x86_64 recovery aboot.img recovery.img recovery_loki.img
#
# The recovery_loki.img file can be installed on the Verizon S4 phone.
#
Now, I also wanted to make a ZIP file which a custom recovery can run to LOKI and install a non-loki recovery.img file.
The LOKI operation will be performed while the ZIP file is being installed.
I used the following loki-doki.zip file as an example found here:
http://rootzwiki.com/topic/41841-lo...tom-boot-image-on-att-and-verizon-galaxy-s-4/
I added CWM touch version 6.0.4.4 recovery.img file, and modified the script to LOKI the recovery.img file rather than the currently installed kernel/boot.
Here is my completed sample zip file: https://db.tt/xLi6c4dd
When a new version of a recovery becomes available, one just renames it recovery.img and replaces the recovery.img file which is in the zip file. Then one can flash to the new version of the recovery.
The script in this zip file will only work on I337UCUAMDB, I337UCUAMDL, and I545VRUAMDK bootloaders.
Credits to: attn1 at rootzwiki for the ZIP file which I modified.
and of course to drjbliss's LOKI github https://github.com/djrbliss/loki
Click to expand...
Click to collapse
Thanks for this. Came in handy today.
The following guide should work for all loki-locked bootloaders, but I can only confirm that it worked on my D800. The problem I was having, was that loki_flash has been replaced with loki_tools, and there arent any guides out for loki_tools.
The right way to flash CWM requires you to generate your own recovery.lok from the aboot.img, and recovery.img (CWM) which you need to use loki_tools for.
PREREQUISITES
Device must be rooted
Device must be in Developer Mode
USB Debugging turned ON
Debugging RSA Signature must be accepted
Download CWM HERE
Download loki_tool HERE
Download ADB HERE
STEP 1 (Getting Files)
Follow this GUIDE to install ADB and FASTBOOT, once its complete, you will have adb installed to C:\adb
Download CWM, rename the file to 'recovery.img' (so its easier to work with) and move it to C:\adb
Download loki_tool and extract the file 'loki_tool' from the bin folder and place it in C:\adb
STEP 2 (Preparing for the Procedure)
Plug in your phone to the computer
In Windows Explorer, navigate to C:\
Shift+Right Click on the 'adb' folder, select 'Open command window here'
Type "adb devices" you should see:
Code:
C:\adb>adb devices
List of devices attached
<devid> device
If not, go back and turn on Develper Mode, USB Debugging, and accept the RSA Signature
STEP 3 (Flashing process)(note: I copied everything from the cmd prompt and edited it as a text file before thinking to post my procedure here, thats why it looks different)
In ADB type the following commands each step is commented out with what it does (someone could make it into a bat, but I'm too lazy.
Code:
// Sending recovery.img to device
C:\adb>adb push recovery.img /data/local/tmp/recovery.img
---------------
3456 KB/s (10510336 bytes in 2.969s)
---------------
// Sending loki_tool to device
C:\adb>adb push loki_tool /data/local/tmp/loki_tool
---------------
2777 KB/s (379248 bytes in 0.133s)
---------------
// entering Android Linux environment
C:\adb>adb shell
// sudo
[email protected]:/ $ su
// generating aboot.img
[email protected]:/ # dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/data/local/tmp/aboot.img
---------------
2048+0 records in
2048+0 records out
1048576 bytes transferred in 0.072 secs (14563555 bytes/sec)
---------------
// changing permissions on aboot.img
[email protected]:/ # chmod 644 /data/local/tmp/aboot.img
// exiting Android Linux environment
[email protected]:/ # exit
[email protected]:/ $ exit
// saving aboot.img locally in case you need it again.
C:\adb>adb pull /data/local/tmp/aboot.img
---------------
2992 KB/s (1048576 bytes in 0.342s)
---------------
// entering Android Linux environment
C:\adb>adb shell
// changing directory
[email protected]:/ $ cd /data/local/tmp
// ls should list the following 3 files, if not, you are missing them and need to push them, or generate another aboot.img
[email protected]:/data/local/tmp $ ls
---------------
aboot.img
loki_tool
recovery.img
---------------
// changing the permissions of the files so loki_tool can use them
[email protected]:/data/local/tmp $ chmod 755 /data/local/tmp/loki_tool
[email protected]:/data/local/tmp $ chmod 755 /data/local/tmp/recovery.img
// executing loki_tool to generate the recovery.lok file
[email protected]:/data/local/tmp $ ./loki_tool patch recovery aboot.img recovery.img recovery.lok
---------------
Loki tool v2.1
[+] Detected target AT&T LG G2 build D80010o
[+] Original kernel address: 00008000
[+] Original ramdisk address: 05000000
[+] Writing device tree.
[+] Output file written to recovery.lok
---------------
// exiting Android Linux environment
[email protected]:/data/local/tmp $ exit
// Saving recovery.lok locally in case you need it again
C:\adb>adb pull /data/local/tmp/recovery.lok
---------------
2939 KB/s (10512384 bytes in 3.493s)
---------------
// entering Android Linux environment
C:\adb>adb shell
// sudo
[email protected]:/ $ su
// changing directory
[email protected]:/ $ cd /data/local/tmp
// flashing recovery.lok with loki_tool
[email protected]:/data/local/tmp # /data/local/tmp/loki_tool flash recovery /data/local/tmp/recovery.lok
---------------
Loki tool v2.1
[+] Loki validation passed, flashing image.
[+] Loki flashing complete!
---------------
// exiting Android Linux environment
[email protected]:/data/local/tmp # exit
[email protected]:/ $ exit
// reboot device into recovery
C:\adb>adb reboot recovery
---------------------------------
At this point your device should reboot into CWM, Congrats!
I know it's been 7 years, but this helped me get Magisk working on a locked bootloader. Thanks!
Platypus Enthusiast said:
I know it's been 7 years, but this helped me get Magisk working on a locked bootloader. Thanks!
Click to expand...
Click to collapse
I'm getting a "
Platypus Enthusiast said:
I know it's been 7 years, but this helped me get Magisk working on a locked bootloader. Thanks!
Click to expand...
Click to collapse
I keep getting "failed to find function to patch" error. Any thoughts?
Jackspsychosis said:
I'm getting a "
I keep getting "failed to find function to patch" error. Any thoughts?
Click to expand...
Click to collapse
I can do it for you if you like. I just need the aboot.img and the boot.img (or recovery.img) you're trying to patch.
Could I use this method to put a recovery on my lg g2 d802 (lollipop) on which it seems not to be any recovery (no command, when I press power+vol. down buttons) ?
TapaSte said:
Could I use this method to put a recovery on my lg g2 d802 (lollipop) on which it seems not to be any recovery (no command, when I press power+vol. down buttons) ?
Click to expand...
Click to collapse
I'm not sure if this is a good source, but maybe this might work:
Recovery Mode LG D802 G2, how to - HardReset.info
The Recovery mode it is the hidden feature which will enable a lot of useful operation.
www.hardreset.info
Platypus Enthusiast said:
I'm not sure if this is a good source, but maybe this might work:
Recovery Mode LG D802 G2, how to - HardReset.info
The Recovery mode it is the hidden feature which will enable a lot of useful operation.
www.hardreset.info
Click to expand...
Click to collapse
Like said, I've not recovery and if I press volume down + power I get "no command" screen.
Fastboot don't recognize the device in linux, to work follow the steps above (root required):
1. Download the fastboot binary compiled to chipset intel in http://www.mediafire.com/download/pbr4b2x2ig9b2m5/fastboot
2. Save binary in internal ou external location in phone
3. Enter ADB
- adb shell
- su
4. Save old fastboot binary
cp /usr/bin/fastboot /usr/bin/fastboot.old
3. Put saved binary in /usr/bin
- cp [...]/fastboot /usr/bin
- chmod 755 /usr/bin/fastboot
4. Enjoy adb and fastboot working in linux
5. Credits for fastboot binary to TK. (https://software.intel.com/en-us/user/1068033)
noRetail said:
Fastboot don't recognize the device in linux, to work follow the steps above (root required):
1. Download the fastboot binary compiled to chipset intel in http://www.mediafire.com/download/pbr4b2x2ig9b2m5/fastboot
2. Save binary in internal ou external location in phone
3. Enter ADB
- adb shell
- su
4. Save old fastboot binary
cp /usr/bin/fastboot /usr/bin/fastboot.old
3. Put saved binary in /usr/bin
- cp [...]/fastboot /usr/bin
- chmod 755 /usr/bin/fastboot
4. Enjoy adb and fastboot working in linux
5. Credits for fastboot binary to TK. (https://software.intel.com/en-us/user/1068033)
Click to expand...
Click to collapse
This is what it says when i try to copy it, any fixes ?
can't stat '/usr/bin/fastboot': No such file or directory
skyplane1 said:
This is what it says when i try to copy it, any fixes ?
can't stat '/usr/bin/fastboot': No such file or directory
Click to expand...
Click to collapse
You probably do not have the fastboot installed in / usr / bin, copy the new fastboot and change the permissions as described in the post and test if working well.