Guide to go straight to TWRP 2.7.0.0 - Verizon LG G2

My new phone shipped with 12B and my first attempt to TWRP it failed resulting in very odd behavior in recovery mode (black screen and if connected to a PC with usb, I would get dozens of drive letters showing up). I recovered stock (11A) following the excellent guide here on xda (http://forum.xda-developers.com/showthread.php?t=2432476) and figured out a slightly different way to install TWRP 2.7.0.0 directly than anything I've read on xda (granted I've not read every post of every forum on the topic so I apologize if this exists somewhere already).
I've only tested this on a vs980 LG G2 as this is the only phone I have available to me.
Prerequisites:
You will need adb working, have a rooted phone. (see the first post of this forum)
Download TWRP 2.7.0.0 (http://teamw.in/project/twrp2/197)
Expand the TWRP 2.7.0.0 zip (expanded it into the folder twrp2)
adb push twrp2\tmp\loki\loki_flash /data/local/tmp/loki_flash
adb push twrp2\tmp\loki\loki_patch /data/local/tmp/loki_patch
adb push twrp2\recovery.img /data/local/tmp/recovery.img
adb shell (make sure you are at the root # prompt, otherwise su)
cd /data/local/tmp
chmod 777 loki_flash
chmod 777 loki_patch
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/data/local/tmp/aboot.img (stop if you see errors)
./loki_patch recovery ./aboot.img ./recovery.img ./recovery.lok (stop if you see errors)
./loki_flash recovery ./recovery.lok (stop if you see errors)
exit
adb reboot recovery

Followed your steps all the way to step 11, and got error message 'Unsupported aboot image.' This is on rooted 12B stock firmware.
[email protected]:/data/local/tmp # dd if=/dev/block/platform/msm_sdcc.1/by-name/aboo
t of=/data/local/tmp/aboot.img
rm/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.083 secs (12633445 bytes/sec)
[email protected]:/data/local/tmp # ll
ll
-rw------- root root 1048576 2014-04-24 00:43 aboot.img
-rwxrwxrwx root root 67020 2008-02-29 02:33 loki_flash
-rwxrwxrwx root root 67688 2008-02-29 02:33 loki_patch
-rw-rw-rw- root root 8828928 2008-02-29 02:33 recovery.img
[email protected]:/data/local/tmp # ./loki_patch recovery ./aboot.img ./recovery.img ./recovery.lok
aboot.img ./recovery.img ./recovery.lok <
[+] loki_patch v2.1
[-] Unsupported aboot image.

Same Issue
I had the same issue, that's why I went back to 11a stock, then forward to root/twrp/rom and now flashed the 12b radio. There appears to be something with the aboot.img in the 12b stock that loki doesn't like/doesn't support.
zw6233 said:
Followed your steps all the way to step 11, and got error message 'Unsupported aboot image.' This is on rooted 12B stock firmware.
[email protected]:/data/local/tmp # dd if=/dev/block/platform/msm_sdcc.1/by-name/aboo
t of=/data/local/tmp/aboot.img
rm/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.083 secs (12633445 bytes/sec)
[email protected]:/data/local/tmp # ll
ll
-rw------- root root 1048576 2014-04-24 00:43 aboot.img
-rwxrwxrwx root root 67020 2008-02-29 02:33 loki_flash
-rwxrwxrwx root root 67688 2008-02-29 02:33 loki_patch
-rw-rw-rw- root root 8828928 2008-02-29 02:33 recovery.img
[email protected]:/data/local/tmp # ./loki_patch recovery ./aboot.img ./recovery.img ./recovery.lok
aboot.img ./recovery.img ./recovery.lok <
[+] loki_patch v2.1
[-] Unsupported aboot image.
Click to expand...
Click to collapse

I guess I'm curious, why go to all that trouble? I used flashify to install 2.7 and it worked just fine.

idrift said:
I guess I'm curious, why go to all that trouble? I used flashify to install 2.7 and it worked just fine.
Click to expand...
Click to collapse
Some just prefer using ADB. Especially those coming from Nexus devices where Fastboot is available. Doing it this way usually ensures the recovery will push successfully. Unless of course you mistype a command. Although I've personally never had a hiccup with Flashify, I've seen some who have.

idrift said:
I guess I'm curious, why go to all that trouble? I used flashify to install 2.7 and it worked just fine.
Click to expand...
Click to collapse
I just tried flashify and I reboot into stock recovery...?
Sent from my VS980 4G using Tapatalk

0331 said:
I just tried flashify and I reboot into stock recovery...?
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
Depends on what you are trying to do. If you are trying to load a custom recovery you need
You can back up your current kernel and recovery first with flashify which is never a bad idea.
Then you would need to flash TWRP if that is what you are trying to do. I flashed a zip as that's
the format TWRP was in for me. It replaces your stock recovery then. Warranty gone....
Make sure this is what you want to do. As previously posted some have had problems doing this.
For me it worked flawlessly. Do at your own risk.

Related

[Q] Restoring stock Recovery Image on Sprint

Hey all,
I had the sense to use the Rotobackup method on my new Sprint Tab after rooting it with the Z4root package. I then proceeded with the ( now outdated ) CWM Flash process adapted from the Epic 4g. Now, I can get into CWM and the process appears to be functional, but I can't get the "Wipe Data/Factory Reset" to work. It all goes well, but when I boot back into android, all the junk is still there.
Now, I know this wouldn't normally be a big deal... However.. In set'n up for my Rotobackup, I punched in a spare Gmail account in case someone wanted a copy of the backup for dissection,etc... Now, since I can't get the factory wipe to work ( neither from the Privacy menu, nor CWM ), I can't get that acct off my Tab so I can get to all my purchased apps on my main account.
Since I have the Rotobackup, I'm thinking that I can just restore one of those packages and get the stock recovery image back in place. I just want to verify which one I should restore before I move forward.
My expectation is that I need to restore the 'boot.bin' file. Can someone confirm this?
For the record, these are the files I have saved:
Code:
-rw-r--r--. 1 root root 262144 Dec 22 19:00 boot.bin
-rw-r--r--. 1 root root 32768000 Dec 22 19:00 cache.rfs
-rw-r--r--. 1 root root 25620093 Dec 22 19:23 data.tgz
-rw-r--r--. 1 root root 86507520 Dec 22 19:00 dbdata.rfs
-rw-r--r--. 1 root root 6553600 Dec 22 19:00 efs.rfs
-rw-r--r--. 1 root root 336068608 Dec 22 19:00 factoryfs.rfs
-rw-r--r--. 1 root root 16777216 Dec 22 19:00 modem.bin
-rw-r--r--. 1 root root 1310720 Dec 22 18:58 param.lfs
-rw-r--r--. 1 root root 262144 Dec 22 19:00 pit.pit
-rw-r--r--. 1 root root 1310720 Dec 22 19:00 Sbl.bin
-rw-r--r--. 1 root root 7864320 Dec 22 18:59 zImage
Thanks in advance,
LK
Or, can I simply do an rm -rf /data/* to get the effect of a factory wipe?
Thanks,
LK
Ok, I figured it out..
So, the thought of flashing the recovery image came from my root experiences on Evo. I decided while waiting for a response to do more digging through the CWM installation routine and noticed that it made a backup of the original recovery file ( since on Epic and Tab, it's a redirector method instead of an image on the Evo ). AND.. it had a 'Remove root/CWM' option!
I modified the run.sh script to NOT remove root on that option and only put the original CWM in place, ran it.. and VIOLA!
Hope this may help someone else.
LK
are you saying you have a working CWM running on your Sprint-flavored tab?
Hello Zoinks,
Nope... the CWM wasn't working properly on my Samsung Tab. I reverted to the stock recovery on my Tab to regain the ability to wipe it.
Thanks,
LK
and you were so close to being my new best friend
which modem are you using? we have not been able to properly export the factory modem
I'm afraid neither of us are that lucky.
I'm still using the original modem. Nothing has actually been flashed to the device aside from what it took to root it.
Nothing to see here...
LK
ok, so I also just rooted my new sprint tab. using the z4root method. I also have learned about rooting through my evo. I have not however got as far as you have as in getting a recovery image. If i understand what I have tried to absorb on this from the board, is that A) I should have gone with tmobile for the tab!!!! lol and B) this aint no EVO!!!!!
So could you point me in the right direction/advice with what I should do now, because I am lost!!!!
thanks in advance
I'd install bash with the 'Bash Installer' app from the market, and then any other goodies you like for rooted devices ( Adfree Android is a personal fav ).
Aside from that, hang tight and watch for more advancements in alternative ROMS and Recovery managers. Don't install any recovery manager at this time as they are too buggy for normal use and don't really have much in the way of usable features yet.
Clockwork Mod is the closest, but still doesn't support nandroid backup and the like.
Oh, also.. you should check into creating a 'Rotobackup' of your device per the instructions found in another thread of this sub-form.
Enjoy!
LK
linuxkidd said:
Ok, I figured it out..
So, the thought of flashing the recovery image came from my root experiences on Evo. I decided while waiting for a response to do more digging through the CWM installation routine and noticed that it made a backup of the original recovery file ( since on Epic and Tab, it's a redirector method instead of an image on the Evo ). AND.. it had a 'Remove root/CWM' option!
I modified the run.sh script to NOT remove root on that option and only put the original CWM in place, ran it.. and VIOLA!
Hope this may help someone else.
LK
Click to expand...
Click to collapse
I'm having the same problem, can you tell me how to do that? Where's the run.sh file?
Thanks.
Hello zephyrd,
The problem I had was because I used the CWM process outlined in this thread. The 'run.sh' script is the one included with the downloads in that thread.
I edited the run.sh file as follows:
* FInd the section that starts with 'function remove {'
* Inside that section, find the following two sub-sections:
- echo Running root file cleaner on device
- echo Removing remount binary
* Comment out the lines under those sections with # so that the final 'function remove {' section looks like this:
Code:
function remove {
clear
echo +++++++++++++++++++++++++++++++++++++++++++++++++++++
echo "Simple Root and ClockworkMod Uninstaller 2.01";
echo +++++++++++++++++++++++++++++++++++++++++++++++++++++
echo Bash Scripts by DRockstar and Firon
echo exploit by joeykrim, original uninstaller by noobnl
echo
echo REMOVES ALL ROOTS AND CLOCKWORKMOD REDIRECTOR
echo MODIFIED FOR USE WITH GALAXY TAB
chooser
startserver
checkroot
echo Mount device RW
$adb shell mount -t rfs -o remount,rw /dev/block/stl9 /system
#echo Running root file cleaner on device
#$adb push rclean /system/xbin/rclean
#$adb shell chmod 755 /system/xbin/rclean
#$adb shell /system/xbin/rclean
#$adb shell rm /system/xbin/rclean
#echo Removing remount binary
#$adb shell rm /system/bin/remount > /dev/null 2>&1
#$adb shell rm /system/xbin/remount > /dev/null 2>&1
echo Removing ClockworkMod redirector
$adb shell rm /system/bin/recoveryfiles/*
$adb shell rmdir /system/bin/recoveryfiles
$adb shell rm /system/bin/recoveryres/images/*
$adb shell rmdir /system/bin/recoveryres/images
$adb shell rm /system/bin/recoveryres/*
$adb shell rmdir /system/bin/recoveryres
$adb shell rm /system/bin/recovery
echo Restoring original recovery file
$adb push recovery /system/bin/recovery
$adb shell chmod 755 /system/bin/recovery
echo Rebooting phone
$adb reboot
checkboot
echo
echo SIMPLE ROOT UNINSTALLER COMPLETED.
end
}
When you run the 'run.sh' command, pick the 'Simple Root and ClockworkMod Uninstaller' option. This will restore your recovery manager back to the stock one, while leaving your Tab rooted.
NOTE: This same logic can be applied to the 'run.bat' file. The sections that need to be commented out are the same. Instead of using a # to comment the lines, place the word 'REM ' in front of them.
The run.bat 'remove' function will look as follows when done:
Code:
:remove
cls
echo +++++++++++++++++++++++++++++++++++++++++++++++++++++
echo Simple Root and ClockworkMod Uninstaller 2.01
echo +++++++++++++++++++++++++++++++++++++++++++++++++++++
echo Batch Scripts by DRockstar and Firon
echo exploit by joeykrim, original uninstaller by noobnl
echo.
echo REMOVES ALL ROOTS AND CLOCKWORKMOD REDIRECTOR
echo MODIFIED FOR USE WITH GALAXY TAB
call :chooser
if "%a%"=="m" goto :menu
call :startserver
call :checkroot
echo Mount device RW
adb shell mount -t rfs -o remount,rw /dev/block/stl9 /system
rem echo Running root file cleaner on device
rem adb push rclean /system/xbin/rclean
rem adb shell chmod 755 /system/xbin/rclean
rem adb shell /system/xbin/rclean
rem adb shell rm /system/xbin/rclean
rem rem echo Removing remount binary
rem adb shell rm /system/bin/remount > nul
rem adb shell rm /system/xbin/remount > nul
echo Removing ClockworkMod redirector
adb shell rm /system/bin/recoveryfiles/*
adb shell rmdir /system/bin/recoveryfiles
adb shell rm /system/bin/recoveryres/images/*
adb shell rmdir /system/bin/recoveryres/images
adb shell rm /system/bin/recoveryres/*
adb shell rmdir /system/bin/recoveryres
adb shell rm /system/bin/recovery
echo Restoring original recovery file
adb push recovery /system/bin/recovery
adb shell chmod 755 /system/bin/recovery
echo Rebooting phone
adb reboot
call :checkboot
echo.
echo SIMPLE ROOT UNINSTALLER COMPLETED.
goto :end
If you have any questions, please let me know. It's better to ask now than screw up your tab.
Hope this helps!
LK
linuxkidd said:
Hello zephyrd,
The problem I had was because I used the CWM process outlined in this thread. The 'run.sh' script is the one included with the downloads in that thread.
I edited the run.sh file as follows:
* FInd the section that starts with 'function remove {'
* Inside that section, find the following two sub-sections:
- echo Running root file cleaner on device
- echo Removing remount binary
* Comment out the lines under those sections with # so that the final 'function remove {' section looks like this:
When you run the 'run.sh' command, pick the 'Simple Root and ClockworkMod Uninstaller' option. This will restore your recovery manager back to the stock one, while leaving your Tab rooted.
NOTE: This same logic can be applied to the 'run.bat' file. The sections that need to be commented out are the same. Instead of using a # to comment the lines, place the word 'REM ' in front of them.
The run.bat 'remove' function will look as follows when done:
If you have any questions, please let me know. It's better to ask now than screw up your tab.
Hope this helps!
LK
Click to expand...
Click to collapse
Thanks so much for the help! However, this doesn't solve my problem, which is outlined in this thread.
I think my factory setting is modified somehow and can not be removed.
I don't expect any solutions any time soon but if you think you can help I can provide more info on the problem.
Thanks again!
Copy of stock recovery
Think you could post of a copy of the stock recovery file?
wolfson292 said:
Think you could post of a copy of the stock recovery file?
Click to expand...
Click to collapse
yea i could really use that right now too
Recovery process
Can you give me a guide to follow to
A. Return to stock: titanium back up on sd card. Unfortunately no way to get titanium bac on tab as market has disapeared. Unless I can down load .apk and then install from card.
B. Replace voodoo kernal with different one that restores screen rotation, market etc.
Will make generous donation to coffee/beer funds.
Any help for a noob in trouble?
[email protected] for mail, gtalk and pm's
can any one tell me how to make a copy of the original recovery image or send me a link to where i could find that information i searched the net but couldnt find an answer
plz help or email me at [email protected]

[GUIDE] Steps to root stocked Nexus One android without flashing(unlocked bootloader)

Disclaimer 1 : I tried to look for something like this but I did not found it. Then I tried to achieve it. Sorry if they are well known steps
This guide allows to root a Nexus One with unlocked bootloader with NO need to flash recovery
USE THAT INFORMATION AT YOUR RISK!!
Updated: Added a line to work with Gingerbread
That steps are for Ubuntu. If you are any interested windows user, please let me know.
Prerequisites:
Unlocked bootloader
adb working properly
1. Download fastboot
Code:
wget --referer=http://developer.htc.com/adp.html http://dl4.htc.com/RomCode/ADP/fastboot.zip
unzip fastboot.zip
chmod u+x fastboot
rm fastboot.zip
2. Obtain busybox (anyone have any direct link?) - NOT GOING TO FLASH CM, JUST GETTING busybox from a trusted place
Code:
wget http://download.cyanogenmod.com/get/update-cm-7.0.0-N1-signed.zip
unzip update-cm-7.0.0-N1-signed.zip system/xbin/busybox
rm update-cm-7.0.0-N1-signed.zip
3. Download su
-- UPDATE: that link broken, you have to donwload it from Google Play
Code:
wget http://dl.dropbox.com/u/6408470/su-releases/su-2.3.6.1-ef-signed.zip
unzip su-2.3.6.1-ef-signed.zip system/app/Superuser.apk system/bin/su
rm su-2.3.6.1-ef-signed.zip
4. Download recovery-RA - NOT GOING TO FLASH IT, DON'T WORRY!!!
Code:
wget -O recovery-RA-passion-v2.2.1.img http://files.androidspin.com/files/amon_ra/RECOVERY/recovery-RA-passion-v2.2.1.img
md5sum recovery-RA-passion-v2.2.1.img
echo ... Validate md5sum is 3def709ab1c9e051a92a1c8b1504a36a
5. Reboot to bootloader - JUST BOOTING WITH, NO FLASHING
Code:
adb devices
adb wait-for-device
adb reboot-bootloader
fastboot boot recovery-RA-passion-v2.2.1.img
echo ... Waiting for recovery image load
while [ -z `adb shell pwd 2> /dev/null` ]
do
sleep 1
done
6. Root it!
Code:
adb shell mount /system
adb push system/xbin/busybox /system/bin/busybox
adb shell chmod 4755 /system/bin/busybox
adb push system/bin/su /system/bin/su
adb shell chmod 4755 /system/bin/su
adb push system/app/Superuser.apk /system/app/Superuser.apk
adb shell chmod 4755 /system/app/Superuser.apk
7. Reboot and enjoy rooting
Code:
adb shell reboot
Will this work on stock Gingerbread?
If you are running Nexus One with Gingerbread, as I understand, it can work. I've not tried, you can try.... at your risk ;-)
Helleqn said:
Will this work on stock Gingerbread?
Click to expand...
Click to collapse
If you have an unlocked bootloader, yes, it will work. If you have an unlocked bootloader, you can install pretty much anything you want, whenever you want...
Sent from my Nexus One using XDA Premium App
Helleqn said:
Will this work on stock Gingerbread?
Click to expand...
Click to collapse
I've added a adb command (mount /system) to work with Gingerbread. It works on mine.
It also works on 2.3.4
Yep. Worked great for me. But with all due respect, it seemed a little fishy to me that your directions have users pull busybox from Cyanogenmod but then have them pull su and Superuser.apk from a random file on a Dropbox account especially since both files are available in the already trusted Cyanogenmod download that was used for busybox. And even more so because the Superuser.apk file using your instructions is a larger file than the one included with Cyanogenmod. So I only used the files from CM and it worked like a charm.
Not accusing you or anything. I'm just pointing that out.
The easier way is to do step 5, then flash the su zip from step 3, and you're pretty much done. You can install busybox through the Market app...
Don't worry for the link, I toke it from the original post for that su release:
http://forum.xda-developers.com/showthread.php?t=682828
I agree it's enough with CM but I intend to get the last version... may be it's not the best option...
Thanks for your comments.

[HOWTO] Root any Atrix after .sbf flash

See 2nd post for International users and Fastboot rooting.
For ATT users only:
What this is:
This is a full clean SBF of 2.3.4 or 1.8.3 WITH the BL unlock and rooting built in to /preinstall.
Flashable SBF: Full 2.3.4 with preinstall root and pudding bootloader unlock, full sbf
Flashable SBF: Full 1.8.3 with Bootloader unlock and preinstall root. It's over 9000 (600mb DL service sbf)
1. Flash with RSDLite 5.3.1 or sbf_flash
2. Root your phone from adb
Code:
adb shell
/preinstall/restoresu
3. If you don't have superuser.apk do this as well
Code:
/preinstall/restoresu all
Apparently I am a terrible scripter, so follow eval-s instructions from here:
type in adb ("adb shell") or terminal emulator, exactly:
Code:
/preinstall/dosu
/bin/mount -o remount,rw /system
cp /preinstall/su /system/bin/
chmod 6755 /system/bin/su
PATH=/system/bin:$PATH pm install /preinstall/Superuser.apk
The last step is optional (and next-to-last *should* be unnecessary), as you can install Superuser however you like. In fact, if you've installed it, simply typing "/preinstall/su" is another way to root, and you could then mount /system read-write and copy it into /system/bin.
Click to expand...
Click to collapse
4. Enjoy
Lastly, you can make your own preinstall pretty easily, include any kind of mod you want P_ROM etc. For instance when I reinstall I always want to install wget and crond, turn off tomoyo permissions and disable the usb plugin sound. You can put apps in /preinstall/app then make a md5sum file in /preinstall/md5 and apks will get loaded on reboot every time you flash. This is more of a fyi for those of you out there cooking up sbfs. you've got a huge partition to play with so I'm sure people out there can come up with creative ways of using it.
Hi guys.. here is a useful little /preinstall for you (attached)
Put phone in fastboot mode, then:
Code:
fastboot flash preinstall preinstall.img
fastboot reboot
(older versions maybe need "fastboot -i 0x22b8")
after fastboot & reboot, type in adb ("adb shell") or terminal emulator, exactly:
Code:
/preinstall/dosu
/bin/mount -o remount,rw /system
cp /preinstall/su /system/bin/
chmod 6755 /system/bin/su
PATH=/system/bin:$PATH pm install /preinstall/Superuser.apk
The last step is optional (and next-to-last *should* be unnecessary), as you can install Superuser however you like. In fact, if you've installed it, simply typing "/preinstall/su" is another way to root, and you could then mount /system read-write and copy it into /system/bin.
Many thanks to Brandon & The2d for brainstorming this out in a crazy "there's no way it could be possible" rooting session. There were a lot of harder ways... who knew we'd be so lucky! And thanks to Edgan for the great "dosu" =)
You can find fastboot here: http://forum.xda-developers.com/showthread.php?t=1138092
Woohoo! 10 char!
Love you long time! Congrats on figuring this out!
i just unlocked my phone and wanted to root, i installed the img but when i try to enter /preinstall/dosu it gives me file path not found. do i need to reboot or something after flashing the img?
Worked a treat with gingerbread! Thanks a lot guys!
For some reasons, could not adb to go, so had to do it with the terminal but it's all good!
neotekz said:
i just unlocked my phone and wanted to root, i installed the img but when i try to enter /preinstall/dosu it gives me file path not found. do i need to reboot or something after flashing the img?
Click to expand...
Click to collapse
I am having the same problem, path not found. What can i do?
bump
Anyone else figure out how to root? Is this only for gingerbread?
-eval, would we just push that SuperUser app to our phone through ADB if we already have Gingerbread on it? Or do we just flash that through fastboot?
airbillion said:
bump
Anyone else figure out how to root? Is this only for gingerbread?
Click to expand...
Click to collapse
This will work for any firmware version
neotekz said:
i just unlocked my phone and wanted to root, i installed the img but when i try to enter /preinstall/dosu it gives me file path not found. do i need to reboot or something after flashing the img?
Click to expand...
Click to collapse
Using linux?
Sent from my MB860 using XDA Premium App
LancerV said:
Using linux?
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
I used fastboot from windows.
eval- said:
Hi guys.. here is a useful little /preinstall for you:
http://www.multiupload.com/A9X3718TXK
Put phone in fastboot mode, then:
Code:
fastboot flash preinstall preinstall.img
(older versions maybe need "fastboot -i 0x22b8")
steps:
Code:
/preinstall/dosu
/bin/mount -o remount,rw /system
cp /preinstall/su /system/bin/
PATH=/system/bin:$PATH pm install /preinstall/Superuser.apk
http://forum.xda-developers.com/showthread.php?t=1138092
Click to expand...
Click to collapse
You still need to set the permissions on SU after you copy it from preinstall.
chmod 06755 /system/bin/su
rjohnstone said:
You still need to set the permissions on SU after you copy it from preinstall.
chmod 06755 /system/bin/su
Click to expand...
Click to collapse
In adb shell when I enter the 2nd command:
adb shell
$
cd /preinstall/dosu
cd: can't cd to /preinstall/dosu
this is my output.
airbillion said:
I used fastboot from windows.
Click to expand...
Click to collapse
You have to use the linux version
Sent from my MB860 using XDA Premium App
LancerV said:
You have to use the linux version
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
Ill give it a shot. thanks
airbillion said:
In adb shell when I enter the 2nd command:
adb shell
$
cd /preinstall/dosu
cd: can't cd to /preinstall/dosu
this is my output.
Click to expand...
Click to collapse
cd /preinstall
then...
dosu
HTH
the2dcour said:
cd /preinstall
then...
dosu
HTH
Click to expand...
Click to collapse
that is what I keep on trying, but it says:
can't dosu
airbillion said:
that is what I keep on trying, but it says:
can't dosu
Click to expand...
Click to collapse
might have to wait till tomorrow when I'm done with the sbf with a 1 command install then ^^;
this worked:
Code:
adb shell
cd /preinstall
su
/bin/mount -o remount,rw /system
cp /preinstall/su /system/bin/
reboot

[Q] Booting to recovery with ADB

Good morning guys,
I potentially have a couple of hundred of these to update with an AOSP ROM. I dont have any problems with the update, all smooth sailing, but I'm trying to script as much as possible to automated the process - Unlock bootloader, get root, push all the files then install the ROM.
For some reason though the command 'adb reboot recovery' doesn't work as expected. It just reboots the phone back to the normal OS.
Has anyone else encountered this? or a work around?
I can issue 'adb reboot-bootloader' and it will reboot into the bootloader correctly where I can issue fastboot commands but not to the recovery (Which is CWM latest as of today, which I think is 6.1.1?)
Thanks in advance!
Code:
adb shell
su
echo "boot-recovery" | /system/bin/dd of=/dev/block/mmcblk0p5 bs=1 count=13
reboot / reboot recovery
Adam77Root said:
Code:
adb shell
su
echo "boot-recovery" | /system/bin/dd of=/dev/block/mmcblk0p5 bs=1 count=13
reboot / reboot recovery
Click to expand...
Click to collapse
Your a genius.
As a side note this didn't require root access.
Adam77Root said:
Code:
adb shell
su
echo "boot-recovery" | /system/bin/dd of=/dev/block/mmcblk0p5 bs=1 count=13
reboot / reboot recovery
Click to expand...
Click to collapse
Maybe you can help me out a little futher. What I'm trying to do is automate the superuser install.
From the look of that, is that writing to one of the recovery commands located under /cache/recovery ? Perhaps the command file?
If it is or not, perhaps you know of a way to write the /cache/recover/command file to run an update ZIP immediately on rebooting into the recovery? My reading seems to be going in circles.
From my reading what I would need to do is:
* Copy the superuser.zip to the sdcard
* write 'boot-recovery' to 'a' file as you mentioned above
* write '--update_package=/sdcard/superuser.zip' to the file /cache/recovery/command
Obviously without root already I cant just write to that file so I thought it might be possible to use 'dd' as above?
Then rebooting into recovery should automatically run the update zip? Or am I mad?
You do need root to write into the command file. 'dd' tool also needs root.

[G920A/G925A/G928A] Kernel auto Root Android 5.1.1 Galaxy S6/S6e/S6e+ AT&T

Kernel support auto Root Android 5.1.1
Galaxy S6 AT&T G920A, Galaxy S6 edge AT&T G925A & Galaxy S6 edge+ G928A AT&T​
Download Kernel Root G920A Android 5.1.1
File: G920A_Kernel_Root_5.1.1_SamFirm.NET.tar.md5
MD5: FCAA9182 - 7015BA72 - AD583332 - D34CAD87
Download Kernel Root G925A Android 5.1.1
File: G925A_Kernel_Root_5.1.1_SamFirm.NET.tar.md5
MD5: CA8612FB - 7F8A6EFC - A540E84E - 29200775
Download Kernel Root G928A Android 5.1.1
File: G928A_Kernel_Root_5.1.1_SamFirm.NET.tar.md5
MD5: BA904163 - 18B28E36 - F3C29CFD - B6BA2E92
How to Root G920A Android 5.11. & Root G925A Android 5.1.1:
- Download Kernel support Root Android 5.1.1 for G920A or G925A
- On your phoen, into Download mode
- Connect to PC
- Open Odin 3.10.7, click AP & choose Kernel file
- Click Start to flash Kernel
- Reboot, your devices have Root access now !
How to use ?
Use adb shell or Terminal command for mount and modified system,... without su binary !!!
Example:
Code:
adb root
adb shell
mount -o remount,rw /system
rm -fR /system/app/*Knox*
...
tried this method and the phone hangs on boot. i was able to flash the kernel but nothing else.
Anybody else try this ?
Could you please assist in finding a stock image to unbrick our phones? Instructions would be appreciated too. Thanks!
Hold volume down plus power and home key. Get into download mode and flash stock Odin files located in the general section. I'll just wait till s6 gets marshmallow.
Anybody found some more progress with this in other locations ?
This doesn't work.
Capt said:
This doesn't work.
Click to expand...
Click to collapse
Try use adb shell mount and edit system
adb root
adb shell
mount -o remount,rw /system
Manh_IT said:
Try use adb shell mount and edit system
adb root
adb shell
mount -o remount,rw /system
Click to expand...
Click to collapse
Still doesn't work.
already a thread on these files. this is not root and really shouldnt be flashed as they do nothing for our 920A s6. unless a dev can use these to get full root then these will not benifit anyone right now thats needs root for root apps or anything else really.
Worked for me. I have adb root but can't do much. I tried to perform a manual install of supersu, but no luck in getting it working fully.
From a directory that has the arm64 and common files from SuperSU zip flle I tried the following:
Code:
adb shell mount -o rw,remount /
adb shell mount -o rw,remount /system
adb shell mkdir /system/bin/.ext
adb shell chmod 0777 /system/bin/.ext
adb push arm64\su /system/bin/.ext/.su
adb shell chmod 06755 /system/bin/.ext/.su
adb push arm64\su /system/xbin/su
adb shell chmod 06755 /system/xbin/su
adb push arm64\su /system/xbin/daemonsu
adb shell chmod 06755 /system/xbin/daemonsu
adb shell mkdir /system/app/SuperSU
adb shell chmod 0755 /system/app/SuperSU
adb push common\superuser.apk /system/app/SuperSU/SuperSU.apk
adb shell chmod 0644 system/app/SuperSU/SuperSU.apk
adb shell adb shell SYSTEMLIB=/system/lib64
adb shell LD_LIBRARY_PATH=$SYSTEMLIB /system/xbin/su --install
adb shell /system/xbin/su --install
adb shell rm /system/bin/app_process
adb shell ln /system/xbin/daemonsu /system/bin/app_process
adb shell rm -r /data/dalvik-cache
adb reboot
i am a user of S6 active,does the thread work on mine?please~
通过我的 SM-G890A 上的 Tapatalk发言
G890A is private still.
Apexseal said:
G890A is private still.
Click to expand...
Click to collapse
oh,it is disappointing
通过我的 Nexus 4 上的 Tapatalk发言
Succeed after installing kingroot. Trying to figure out how to make Supersu work.
dreamyy5 said:
Succeed after installing kingroot. Trying to figure out how to make Supersu work.
Click to expand...
Click to collapse
This image is a copy from the OP, beware this could soft brick your phone. Test this method with caution.
metalcated said:
This image is a copy from the OP, beware this could soft brick your phone. Test this method with caution.
Click to expand...
Click to collapse
I also tried to push the files to following place, supersu still cannot work properly. Couldn't figure out why.
/system/etc/init.d/99SuperSUDaemon
/system/etc/install-recovery.sh
/system/bin/install-recovery.sh
/system/xbin/supolicy
/system/lib64/libsupol.so
Can get it working on first boot. But retaining it is an issue. Still need more time. Anyone else who's good here can PM me and I'll provide my steps. Please only someone who's familiar with rooting on a technical level. ROM devs etc. Thanks
So what I have figured at this point is that SeLinux needs to be set to permissive from kernel cmdline and unfortunately without an unlocked BL or a Kernel that is flashable that already has Selinux set to permissive, I am stuck running this manually through adb shell each boot and the boot itself takes about 5 minutes before adb responds again. I can provide this method but its not 100% working obviously due to lacking the ability to run kernel cmdline. I am open to suggestions.
Root method Q&A = http://forum.xda-developers.com/att-galaxy-s6/general/root-5-1-1-qa-oj7-root-snag-t3334546

Categories

Resources