Having successfully semi-rooting my device through pauls root i was trying to install the SDE, i followed all steps correctly and ran the batch file but when rebooting into recovery mode no such menu appeared, i have confirmed root shell access so now i'm wondering if anyone else has had a problem? really would want to get the menu installed. It just seems not to work at all and i've ran the script from both my pc and from the internal device memory but this seems not to have worked, any ideas? Thanks
I followed all paul's instruction but I can't root my 101, I tried SDE script too but I can't see any differcence in recovery
Nadrian,
could you try this for me:
start a cmd.exe, and launch the script from this cmd window.
Do a copy/paste of the execution log and post it here please ?
(to copy paste from cmd, do Alt+space, select "edit", "mark", then select text with mouse, press enter then do a paste here)
Moskiller, you problem is different if you don't have the # prompt when doing Paul's root, could you show me the log of the adb session ?
@letama i'll pm you those tomorrow and thanks for the help!
letama said:
Nadrian,
could you try this for me:
start a cmd.exe, and launch the script from this cmd window.
Do a copy/paste of the execution log and post it here please ?
(to copy paste from cmd, do Alt+space, select "edit", "mark", then select text with mouse, press enter then do a paste here)
Moskiller, you problem is different if you don't have the # prompt when doing Paul's root, could you show me the log of the adb session ?
Click to expand...
Click to collapse
If u explain to me how do it, with pleasure
Sent from my ARCHOS 101G9 using Tapatalk
Moskiller said:
If u explain to me how do it, with pleasure
Click to expand...
Click to collapse
I need all the text in the cmd window with the adb commands and the results.
you can do the copy/paste the same way I explained to Nadrian.
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb reboot
C:\Program Files (x86)\Android\android-sdk\platform-tools>enable_sde
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb push zimage /data/
local/tmp
306 KB/s (2655004 bytes in 8.450s)
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb push initrd.cpio.l
zma /data/local/tmp
314 KB/s (398045 bytes in 1.236s)
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb push abcbox /data/
local/tmp
323 KB/s (277204 bytes in 0.838s)
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell chmod 755 /d
ata/local/tmp/abcbox
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell /data/local/
tmp/abcbox kd_flasher -k /data/local/tmp/zimage -i /data/local/tmp/initrd.cpio.l
zma
Generating KD...
Updating KD (3053305 bytes)...
0
100
It worked when i executed the script through command prompt, but here's the execution log anyway, thanks for the tool and for all help!
My log (Windows XP SP3):
C:\android-sdk-windows\platform-tools>enable_sde.bat
C:\android-sdk-windows\platform-tools>adb push zimage /data/local/tmp
1999 KB/s (2655004 bytes in 1.296s)
C:\android-sdk-windows\platform-tools>adb push initrd.cpio.lzma /data/local/tmp
1776 KB/s (398045 bytes in 0.218s)
C:\android-sdk-windows\platform-tools>adb push abcbox /data/local/tmp
1925 KB/s (277204 bytes in 0.140s)
C:\android-sdk-windows\platform-tools>adb shell chmod 755 /data/local/tmp/abcbox
C:\android-sdk-windows\platform-tools>adb shell /data/local/tmp/abcbox kd_flashe
r -k /data/local/tmp/zimage -i /data/local/tmp/initrd.cpio.lzma
Generating KD...
Updating KD (3053305 bytes)...
0
100
C:\android-sdk-windows\platform-tools>
Even for me, SDE doesn't work (archos 101 G9 8gb)
EDIT: WORKS!
at the fourth attempt it worked (ext4 firmware)! After removing the root and before reboot, the only thing I changed was disconnect the USB cable from tablet (???). ciao
hitman72 said:
at the fourth attempt it worked (ext4 firmware)! After removing the root and before reboot, the only thing I changed was disconnect the USB cable from tablet (???). ciao
Click to expand...
Click to collapse
Weird!
I guess a couple of md5sum could help pinpointing adb push or flash issue.
I'll add that someday.
Thanks for the report!
Related
Hi guys, I am trying to move some files into ext partition. I want to do it via adb but ...
It came to my attention that adb shell isn't the solution for adb push or adb pull. I need to do it via windows but whenever I do adb remount or adb kill-server and adb pull or adb push . When I input and press enter it shows an arrow I press enter cuz I dont know what I could input. It just tells me "push not found" or "adb not found" if I say adb push.
Please don't ask me what I do exactly just tell me the exact steps ^^
I would like to move Htc ime mod by jonasl by example.
Hope you will help me out guys
copy tools adb.exe, AdbWinApi.dll and AdbWinUsbApi.dll to the .../windows/system32/
Thank's but doesn't seem to work
I tried doing : cd C:\Program Files\Android SDK
adb push C:\Program Files\Android SDK\tools\su-2.1-e-signed\system\xbin\su \system\xbin\
but this just gives me all adb commands.
Doing this inside adb shell gives me the adb : not found
Any idea/ workaround? (< only adb plz I dont want to install linux)
Code:
cd C:\Program Files\Android SDK
adb remount
adb push tools\su-2.1-e-signed\system\xbin\su \system\xbin\
Give that a try.
You can't use push or pull with shell.
The biggest problem you sill face is having spaces in the PC side path names, try moving the SDK to c:\Android_SDK if the above fails
Try this:
Code:
cd C:\Program Files\Android SDK\tools
adb remount
adb push C:\Program Files\Android SDK\tools\su-2.1-e-signed\system\xbin\su /system/xbin/
AH great, by removing the space beetwin android and sdk I managed to get out but now I am facing Out of memory error
Damn I have like 1.5 gb of memory on my ext2 partition
Where can I check the remaining memory?
EDIT : su is 22ko so I dont think memory is the big deal. However I would still like to know what is left
Maybe my microSD is dying... Any idea?
Mister-Tea said:
yy whatever, if you don't want to answer then don't but don't look high on me.
lol......
Click to expand...
Click to collapse
1/ he already answer your question
2/ it's android DEV section, your question if far away from DEV
3/ You have to learn how to use command-line application (Windows suck at this, so you should try on a linux OS)
BTW: a little how-to
cd: a great command, you'll be able to change directory (yes you have "adb" on your harddrive, but you have to tell your computer where is it)
cp : copy
mv: move
ls: list content of working directory
pwd: print current working directory
Now: let say "adb" (adb.exe) is located here: /home/carbonyle/androidSDK/tools/
launch a terminal (WindowsKey + r on windows host, then type "cmd")
Yyour working directory maybe "C:" , or whatever (/home/carbonye/ for me)
now use "cd"
Code:
cd /home/carbonyle/androidSDK/tools/
<. of course adapt this to your environnment
(use ls / pwd to convince you what you're doing)
Code:
./adb reboot recovery
<- for linux user
Code:
adb reboot recovery
<- for Win**** users
Of course this will reboot your phone into recovery mode, just adapt command to your need
Right, this thread has gone far enough with enough flaming for today.
To all of you, im disappointed and you should all know better.
PLease refrain from further flames, tidy up in progress. I am also moving this to QnA.
@ Mister-Tea
You are equally responsible for the flaming by flaming yourself.
@ you all, quit it or i will take further action.
THanks.
So I have mac osx and windows. I've tried rooting on both. I can follow a tutorial, that is how I've rooted my thunderbolt when it first came out. But my new thunderbolt won't root using the methods that are working for others. So I request someone to help me out as to writing a step by step setup for required prerequisites programs... Thank you. Something isnt working. I just want to enjoy perks of root again.
Sent from my ADR6400L using XDA App
Which instructions are you trying to follow, JCase's or Cap's? Also, where is the root procedure failing for you? I only ask because there is no one here who could write better step by step instructions than the ones already included in both rooting methods.
Have to agree. Any information at all regarding how its failing would be most helpful.
Okay. For windows I used the script that is a batch file because I've heard it is super easy to use... When I first was running the script it would not find the device. Now it will find it with debugging on. But when debugging is on my device won't be listed in my computer. With debugging off it will show up on my computer. Anyways with the script it says it pushes all the files then when my phone is to reboot it won't.
Sent from my ADR6400L using XDA App
Make sure that your ADB is set up properly before you start using the batch file.
A great set of instructions can be found here:
http://www.droidforums.net/forum/droid-hacks/10924-how-adb-windows-made-easy.html
The batch file is also old and some of the files included in it might be too dated to use. Try using JCase's method.
Last login: Fri Jul 29 16:53:34 on ttys000
scott-roccas-macbook:~ scott87$ cd ..
scott-roccas-macbook:Users scott87$ cd ..
scott-roccas-macbook:/ scott87$ cd and*
scott-roccas-macbook:androidsdk scott87$ cd tools
scott-roccas-macbook:tools scott87$ ./adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
HT14RS010885 device
scott-roccas-macbook:tools scott87$ ./adb push busybox /data/local/
1867 KB/s (1062992 bytes in 0.555s)
scott-roccas-macbook:tools scott87$ ./adb push psneuter /data/local/
1764 KB/s (585731 bytes in 0.324s)
scott-roccas-macbook:tools scott87$ ./adb push misc.img /data/local/
1943 KB/s (262144 bytes in 0.131s)
scott-roccas-macbook:tools scott87$ ./adb shell chmod 777 /data/local/busybox
scott-roccas-macbook:tools scott87$ ./adb shell chmod 777 /data/local/psneuter
scott-roccas-macbook:tools scott87$ ./adb shell /data/local/psneuter
mmap() failed. Operation not permitted
scott-roccas-macbook:tools scott87$
following this tutorial for my mac... http://forums.androidcentral.com/th...9-mac-procedure-how-root-htc-thunderbolt.html I have rooted my orignal TB over 6 times. Now I cannot use the same method on my new TB. Wtf. It wont let me go past the step of ./adb shell /data/local/psneuter
what is wrong?
Where did you get the exploits file that contained the psneuter file and such? Try downloading the files from http://www.multiupload.com/K4BZ22SIT5 and verify the md5 is 3b359efd76aac456ba7fb0d6972de3af and try again.
I'm kinda clueless without firmware versions and what exploits exactly are being used.
My exploits folder matches the MD5 checksum... I am on the newest possible firm. Someone please help me solve this issue...
http://forum.xda-developers.com/showthread.php?p=12785644#post12785644
http://forums.androidcentral.com/thunderbolt-rooting-roms-hacks/73211-rooting-issues.html#post782824
Both of those links showed ppl having similar problems. Try their fixes of restoring to factory defaults and trying again or re-formatting your card.
Thank you for your help. Doing a factory reset made the difference. I greatly appreciate it.
Dueces.
Sent from my ADR6400L using XDA App
Check out these videos, they helped me go through all the steps. The second time I rooted this thing was harder because I thought I had everything setup, and I did but I had to redo everything to get it to work. Start fresh by doing the drivers again, then put the contents of the exploits zip in sdk tool, (all the files but one were correct on mine, I think it was just an outdated version and that was one of my hold ups)
http://www.youtube.com/watch?v=oKPSe12YDxQ
http://www.youtube.com/watch?v=mc6EMdPpF6o
This is why you should manually root, and not do the auto crap... problems
UPDATE: See my other thread for a much easier solution that does all the hard work for you...
This assumes a factory fresh nook and a mac that hasn't previously been used. I just reset mine again (Hold Power until you get prompted, pick power off, then when it's off, press N and then turn it back on) and went through this. Works reliably.
On the NOOK
Browse to this:
http://www.launcherpro.com/apk/LauncherPro-0.8.6.apk
When it's done, click on notifications center
Press on downloaded apk file
Complete action using package installer
It should say "install blocked"
Press settings
Tick unknown sources (press ok)
Pick Development
Tick USB debugging (press ok)
Tick the other USB debugging further down
Uncheck Automount
Back/Back
On the MAC
Download Android SDK http://developer.android.com/sdk/index.html
Unzip it
Start a shell
Cd to the dir where you unzipped it
cd to tools directory
run ./android - android sdk manager launches
Tick Android SDK platform tools
Click install 6 packages - wait until it's all done. "done loading packages"
Open a new shell
See if there is .android directory in your home directory, if not "mkdir -p ~/.android" in your home directory
echo 0x2080 > ~/.android/adb_usb.ini
adb kill-server
Connect the Nook via MicroUSB to your Mac
The nook should show you notification saying usb debugging connected. If not something's wrong with the settings in the menu earlier
Download http://dl.dropbox.com/u/15069134/Nook&Zergy.zip
unzip that file
Adjust your PATH variable to include the directory containing the adb binary from the sdk, eg:
export PATH=$PATH:YOURDOWNLOADDIR/android-sdk-macosx/platform-tools/
Type which adb
This should show you the full path to the adb binary, if not your path is set wrong, assuming that is right
adb devices
You should see:
List of devices attached
[YOUR NOOKCOLOR SN] device
adb push zergrush /data/local/zergy
adb shell "chmod 755 /data/local/zergy;cd /data/local/;./zergy"
adb wait-for-device install Superuser.apk
adb remount
adb push su /data/local/tmp/
adb shell "cd /data/local/tmp;chmod 777 su;cd /;mount -o remount,rw -t rootfs rootfs /"
adb push su /system/bin/su
adb shell chmod 4755 /system/bin/su
Download http://goo-inside.me/gapps/gapps-gb-20110828-signed.zip
Unzip this file.
cd gapps-gb-20110828-signed/system/app/
rm SetupWizard.apk
adb push GoogleServicesFramework.apk /system/app
adb push Vending.apk /system/app
adb push CarHomeGoogle.apk /system/app
adb push FOTAKill.apk /system/app
adb push GenieWidget.apk /system/app
adb push GoogleBackupTransport.apk /system/app
adb push GoogleCalendarSyncAdapter.apk /system/app
adb push GoogleContactsSyncAdapter.apk /system/app
adb push GoogleFeedback.apk /system app
adb push GoogleFeedback.apk /system app
adb push GoogleFeedback.apk /system/app
adb push GooglePartnerSetup.apk /system/app
adb push GoogleQuickSearchBox.apk /system/app
adb push LatinImeTutorial.apk /system/app
adb push MarketUpdater.apk /system/app
adb push MediaUploader.apk /system/app
adb push NetworkLocation.apk /system/app
adb push Talk.apk /system/app
adb push OneTimeInitializer.apk /system/app
adb shell chmod 644 /system/app/*
Click on Notification center again, and press on the Golancher Icon again. Install the Goauncher
Reboot
After reboot, slide to unlock and it should ask "complete action using..". Pick LauncherPRO
Open Marketplace which should be on the launcher screen
Sign in with your google credentials, attach the device to your account
Install button savior from the Marketplace.
Browse to www.amazon.com/app-email
Click notifications and watch for Amazon appstore apk download
Click and install.
You should now be live with Android Market & Amazon Market.
My word I hope these kind of instructions get captured in a wiki somewhere...
Just what I was looking for, worked perfect first try. My frustrations are out the window, not my Nook Tablet!!!
Sweet. One person helped, my debt is repaid the community
Sweet Indeedie!
Thanks @t-r-i-c-k - you just helped yet another.
Note to others - I did have a problem getting my device listed with adb, I re-ran the tgps_launcher app for the debug settings and un-checked and re-checked USB Debugging lines (2 of them) and that seem to do it. I also re-plugged the USB cable a one point so that may have been part of the trick as well - not real sure. You may have to fiddle a bit.
EDIT: ok running tgps_launcher, it is the first USB Debugging checkbox to un-check then re-check.
---------- Post added at 05:48 AM ---------- Previous post was at 05:09 AM ----------
Ok, just had a bit of a scare after rooting...
I had left the NT in terminal, su'd to root and the display timed out. NOTHING would bring it back to life!! EXCEPT plugging in the USB cable and running 'adb devices' ... and it powered on!! Whew!!!!
(before this I held the power button for a good 30 seconds and tried a repower to no avail)
I tried to replicate but always got my unlock back on no matter what I did?!
Ok so here is where I am getting stuck.
t-r-i-c-k said:
See if there is .android directory in your home directory, if not "mkdir -p ~/.android" in your home directory
echo 0x2080 > ~/.android/adb_usb.ini
adb kill-server
Click to expand...
Click to collapse
I'm pasting the "mkdir -p ~/.android" command into the terminal and it doesn't seem to do anything. No such directory is created.
Perhaps I'm missing something. I'm not as used to using the terminal on my Mac as I am on Linux.
MonkeysInACan said:
Ok so here is where I am getting stuck.
I'm pasting the "mkdir -p ~/.android" command into the terminal and it doesn't seem to do anything. No such directory is created.
Perhaps I'm missing something. I'm not as used to using the terminal on my Mac as I am on Linux.
Click to expand...
Click to collapse
Nope - not the your Nook terminal - do it on your Mac
...assuming you are doing it on your mac...
if you use 'cd' (and [Enter] of course) and you'll be in your home folder ("~")
if mkdir returns an error then it probably already exists - try 'ls -a' and see if you see it.
if it exists then use the echo command again - there is no visible output - it used by adb
MonkeysInACan said:
Ok so here is where I am getting stuck.
I'm pasting the "mkdir -p ~/.android" command into the terminal and it doesn't seem to do anything. No such directory is created.
Perhaps I'm missing something. I'm not as used to using the terminal on my Mac as I am on Linux.
Click to expand...
Click to collapse
It makes a hidden directory in your home directory. ls -lart ~ to see it
Yay!!! It works!!!! It took a bit of tweaking, and a few extra steps (making sure all the directories were right) but it worked. Thanks a lot!
It all seemed to work really well except I got a force close on the google framework when I rebooted. Not sure if I should start from scratch or not. One thing I can't figure out how to do is erase apps that install from the market. Clicking settings brings up the Nook settings which doesn't have any record of the apps I installed via market.
Also, is there any way to enable USB debugging after the reboot? When I plugged in the usb cable again to try to repush the framework I just get usb storage.
Ok, I found a link to the app that lets me toggle USB debugging though I'm getting a permissions error when I try to push. Also figured out that I can uninstall apps through the market app itself.
Thanks very much for the instructions you've posted here.. very helpful!
viniosity said:
It all seemed to work really well except I got a force close on the google framework when I rebooted. Not sure if I should start from scratch or not. One thing I can't figure out how to do is erase apps that install from the market. Clicking settings brings up the Nook settings which doesn't have any record of the apps I installed via market.
Also, is there any way to enable USB debugging after the reboot? When I plugged in the usb cable again to try to repush the framework I just get usb storage.
Ok, I found a link to the app that lets me toggle USB debugging though I'm getting a permissions error when I try to push. Also figured out that I can uninstall apps through the market app itself.
Thanks very much for the instructions you've posted here.. very helpful!
Click to expand...
Click to collapse
I have seen that google services framework crash once too. I just ignored it and everything seems fine. I did notice at least one other person in the main thread who reported the same. I may wipe my device and try the process again, this time with another Launcher too. I also noticed the app store doesnt show everything either. Notably facebook seems missing. If you go right to it from a link you get a "this is not compatible with your device" at the top. Going to play around more after work. On the whole though, this is awesome!
Sent from my BNTV250 using Tapatalk
I've gotten to this spot:
adb devices
You should see:
List of devices attached
[YOUR NOOKCOLOR SN] device
I can see the serial number, but I can't get any farther. This is the error I get: cannot stat 'zergrush': No such file or directory
Any ideas people? I'm brand spanking new to terminal and commands and stuff like this. Thanks for your help.
beatlesfan01 said:
I've gotten to this spot:
adb devices
You should see:
List of devices attached
[YOUR NOOKCOLOR SN] device
I can see the serial number, but I can't get any farther. This is the error I get: cannot stat 'zergrush': No such file or directory
Any ideas people? I'm brand spanking new to terminal and commands and stuff like this. Thanks for your help.
Click to expand...
Click to collapse
You need to be in the directory where you unzipped the zip from dropbox . Do ls -l and you should see the zergrush file, su etc
Sent from my BNTV250 using Tapatalk
Ok I renamed the folder from dropbox "Nookroot" This is what I get. I'm copy pasting "adb push zergrush /data/local/zergy" from first post.
MYNAME-iMac-2:Nookroot emt1052$ ls -l
total 4048
-rwxr-xr-x 1 emt1052 staff 96256 Sep 20 2010 AdbWinApi.dll
-rwxr-xr-x 1 emt1052 staff 60928 Sep 20 2010 AdbWinUsbApi.dll
-rwxr-xr-x 1 emt1052 staff 4229 Nov 21 14:38 NookandZergy.bat
-rwxr-xr-x 1 emt1052 staff 843503 Feb 29 2008 Superuser.apk
-rwxr-xr-x 1 emt1052 staff 578611 Sep 20 2010 adb.exe
-rwxr-xr-x 1 emt1052 staff 413129 Nov 20 21:55 busyboxinstall.apk
-rwxr-xr-x 1 emt1052 staff 14175 Nov 20 13:52 debug.apk
-rwxr-xr-x 1 emt1052 staff 22228 Feb 29 2008 su
drwxr-xr-x 6 emt1052 staff 204 Nov 20 15:57 system
-rwxr-xr-x 1 emt1052 staff 23056 Nov 16 09:09 zergRush
MYNAME-iMac-2:Nookroot emt1052$ adb push zergrush /data/local/zergy
-bash: desktop/android-sdk-macosx/platform-tools/adb: No such file or directory
Sorry if I'm making some dumb mistake, and thanks for your help.
Try this
beatlesfan01 said:
...
MYNAME-iMac-2:Nookroot emt1052$ adb push zergrush /data/local/zergy
-bash: desktop/android-sdk-macosx/platform-tools/adb: No such file or directory
...
Click to expand...
Click to collapse
@beatlesfan01: I wonder if /data/local doesn't exist on your NT - or you don't have permissions...
maybe try (from your Mac shell)
Code:
mac-osx$ adb shell
$ ls /data/local
a) you should get the single '$ ' prompt after the adb cmd - this is the NT's shell
b) you should get no error from 'ls /data/local
If you get errors for /data/local, then try this (while still in the 'adb shell'):
Code:
$ mkdir /data/local
$ chmod 777 /data/local
If you get an error on the 'mkdir' do the 'chmod' anyway - actually the 'chmod ...' may be the only thing you need.
Then try stuff again.
I did the first part and got this:
MYNAME-iMac-2:~ emt1052$ adb shell
$ ls /data/local
tmp
$
beatlesfan01 said:
I did the first part and got this:
MYNAME-iMac-2:~ emt1052$ adb shell
$ ls /data/local
tmp
$
Click to expand...
Click to collapse
*** NOTE EDIT ***
Ok, try 'ls -l /data' and look for 'local'
the permissions should look like '-rwxrwxrwx' - if not try 'chmod 777 /data/local' and try your adb push cmd again.
Got this:
ls -l /data/local
drwxrwx--x shell shell 2011-11-21 16:06 tmp
$ chmod 777 /data/local
$ adb push zergrush /data/local/zergy
adb: permission denied
$
I DO appreciate your help with this.
Based on your last post - you are issuing the adb push command on the Nook.
It has to be issued on the Mac...
beatlesfan01 said:
Got this:
ls -l /data/local
drwxrwx--x shell shell 2011-11-21 16:06 tmp
$ chmod 777 /data/local
$ adb push zergrush /data/local/zergy
adb: permission denied
$
I DO appreciate your help with this.
Click to expand...
Click to collapse
Ok - weird. I did mis type and edited my previous post BUT the chmod should have looked after the permission issue anyway...
Try 'chmod 777 /data' - can you do that without an error - using the 'adb shell'?
EDIT: @rmm200 - thanks - I didn't notice that one
I accidentally formatted my phone before i installed the rom. Now i need to adp push the rom onto the phone. ADB says the following when i try.
C:\adb>adb -s emulator-5554 push dlx.zip /dlx.zip
failed to copy 'dlx.zip' to '/dlx.zip': Read-only file system
wack0jacko said:
I accidentally formatted my phone before i installed the rom. Now i need to adp push the rom onto the phone. ADB says the following when i try.
C:\adb>adb -s emulator-5554 push dlx.zip /dlx.zip
failed to copy 'dlx.zip' to '/dlx.zip': Read-only file system
Click to expand...
Click to collapse
I just got this:
C:\adb>adb push dlx.zip /sdcard/
1887 KB/s (914054797 bytes in 472.833s)
The file is 900mb. What am I doing wrong?
wack0jacko said:
I just got this:
C:\adb>adb push dlx.zip /sdcard/
1887 KB/s (914054797 bytes in 472.833s)
The file is 900mb. What am I doing wrong?
Click to expand...
Click to collapse
adb push <Rom directory> /sdcard/
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.