Wiped ALL partitions! Cant boot! NO adb permission! - One (M7) Q&A, Help & Troubleshooting

-cut-
It seems to be that I've found a solution to formatting EVERYTHING off of your phone, with no adb permissions.
The top answer from stack overflow helped out a LOT (cant post links)
Windows users I guess just ignore sudo and "./"
1. sudo ./adb kill-server
2. sudo ./adb start-server
3. sudo ./adb devices
Click to expand...
Click to collapse
then I ran the commands:
./adb shell
mount data
ctrl+c
./adb push /home/zach/romname.zip /data/ (wait patiently)
adb shell
recovery --update_package=DATA:romname.zip
Click to expand...
Click to collapse
after that last command all I had to do was install it from the data folder in recovery and im done!

Related

Help With ADB...please

Hey guys, i'm having a bit of a problem here. It might be a stupid problem that i am over looking, but i just cant seem to figure it out. I dont use ADB often, but i just installed cyanogens newest rom and it no longer comes with the advanced launcher. which i absolutely love. so heres my issue, I am trying to follow these directions:
Installation
- Plug your USB cable into the phone and your computer
- Make a backup of your original launcher: "adb pull /systemapp/Launcher.apk LauncherBAK.apk"
- Remount the /system filesystem: "adb remount"
- Unzip the advanced launcher "unzip Launcher_update_x.zip"
- Push the advanced launcher "adb push Launcher.apk /system/app/Launcher.apk"
- Remove the odex file "adb rm /system/app/Launcher.odex"
- Reboot your phone.
This is whats happening:
cd C:\android-sdk-windows-1.5_r3\tools
C:\android-sdk-windows-1.5_r3\tools> adb shell
#adb pull /system/app/Launcher.apk LauncherBAK.apk
adb: not found
#
I tried moving forward without backing up. this is what i get:
adb: not found
#adb remount
adb remount
#adb: not found
#
This is where im at. can sombody please point me int he right direction of whats going on here? thank you
As I understand it, when you type adb shell, youre in the android shell, and no longer use the adb commands, but you use the commands that youd use in console. ADB has different commands, which you can list by just typing adb.
SO,
plug it in
adb remount
adb pull /system/app/Launcher.apk LauncherBAK.apk
unzip Launcher_update_x.zip
adb push Launcher.apk /system/app/Launcher.apk
adb rm /system/app/Launcher.odex
reboot
That should work. Dont use the shell. The pros can feel free to correct me.
Hummeroid said:
As I understand it, when you type adb shell, youre in the android shell, and no longer use the adb commands, but you use the commands that youd use in console. ADB has different commands, which you can list by just typing adb.
SO,
plug it in
adb remount
adb pull /system/app/Launcher.apk LauncherBAK.apk
unzip Launcher_update_x.zip
adb push Launcher.apk /system/app/Launcher.apk
adb rm /system/app/Launcher.odex
reboot
That should work. Dont use the shell. The pros can feel free to correct me.
Click to expand...
Click to collapse
As far as I know this is right. Don't try to pull when you're in adb shell.
Hummeroid said:
As I understand it, when you type adb shell, youre in the android shell, and no longer use the adb commands, but you use the commands that youd use in console. ADB has different commands, which you can list by just typing adb.
SO,
plug it in
adb remount
adb pull /system/app/Launcher.apk LauncherBAK.apk
unzip Launcher_update_x.zip
adb push Launcher.apk /system/app/Launcher.apk
adb rm /system/app/Launcher.odex
reboot
That should work. Dont use the shell. The pros can feel free to correct me.
Click to expand...
Click to collapse
Right on! thanks so much Hummeroid.
Okay so I tried to do it without the shell and this is what i'm getting. So I'm stuck...Btw, I really appreciate all the help everyone's giving me.
C:\>cd androidsdk\tools
C:\AndroidSDK\tools>adb devices
List of devices attached
HT96LLV00999 recovery
C:\AndroidSDK\tools>adb remount
remount failed: Invalid argument
C:\AndroidSDK\tools>
Why are you doing in recovery, try it with the phone on.

Can't push HELP!

Why can't I push or even mount, I'm trying to install the Signature in Exchange issue with this
http://jvance.com/blog/2010/04/14/EmailSignatureInAndroidFixed.xhtml
I can adb shell but I can't get any farther than that.
djorijun said:
Why can't I push or even mount, I'm trying to install the Signature in Exchange issue with this
http://jvance.com/blog/2010/04/14/EmailSignatureInAndroidFixed.xhtml
I can adb shell but I can't get any farther than that.
Click to expand...
Click to collapse
commands should be revised as
Code:
adb remount
adb push download/Email.apk /system/app/Email.apk
problem solved
Mods, please move this to general section (or make a Q/A Section).
darchstar said:
commands should be revised as
Code:
adb remount
adb push download/Email.apk /system/app/Email.apk
problem solved
Mods, please move this to general section (or make a Q/A Section).
Click to expand...
Click to collapse
Thanks but not solved and please move as needed.
C:\android-sdk-windows\tools>adb shell
/ # adb remount
adb remount
/sbin/sh: adb: not found
djorijun said:
Thanks but not solved and please move as needed.
C:\android-sdk-windows\tools>adb shell
/ # adb remount
adb remount
/sbin/sh: adb: not found
Click to expand...
Click to collapse
.... don't adb shell.
darchstar said:
.... don't adb shell.
Click to expand...
Click to collapse
when I don't this is what happens
C:\android-sdk-windows\tools>adb remount
remount failed: Invalid argument
djorijun said:
when I don't this is what happens
C:\android-sdk-windows\tools>adb remount
remount failed: Invalid argument
Click to expand...
Click to collapse
It looks like you are in recovery.. when you type adb shell it should look like this
adb shell
#
NOT
adb shell
/ #
Type the command when the phone is booted up and running.

[Guide][Root] Rooting the LG Revolution 4G Using Linux

This Guide is to root the LG Revolution 4G with system builds V7 and lower using only linux. Not many people use linux, but I do and figured someone may need a hand if they are just starting out with linux. I have tested this on 2 phones and 2 different distros. If you have problems let me know.
Android is based off from linux so let's do it in linux.
Disclamer
Do This at your OWN risk. Nothing is my responsibility if you brick your phone or damange anything in frustration. If you follow this guide to the "T" you should have no problems what-so-ever.
This is not MY exploit, only a guide on how to do it in a linux environment.
Things you will ABSOLUTELY need:
1) Root privliges on your linux-box
2) The exploit from mtmichaelson's post HERE
3) The Android SDK for linux HERE
4) Your LG Revolution, Duh!
5) Patience, and a brain
To start things off you need to setup the SDK, if you already have the SDK up and working skip down to the preparation section.
Setting up the SDK:
1) Go to your downloads folder and extract your android-sdk_xxx-linux.tgz
2) I recommend moving that extracted folder to your Desktop for easy access and rename the folder android-sdk.
3) Next you must download the proper platform-tools, so open terminal and type
Code:
cd /home/[your username]/Desktop/android-sdk/tools
sudo ./android
4) This should popup the SDK Manager, click on the checkmark for the tools folder then click "install _ packages"
5) Next go to your android-sdk folder and make sure you have the folder platform-tools. If not go back to "Setting up the SDK".
Preparation:
1) Make sure you turn USB debugging 'on' from Settings>applications>development>USB Debugging => This should be checked!
2) Make sure you have internet connection selected from Settings>Connectivity => select always ask or choose the default connection as internet connection.
Rooting:
1) Extract the exploit you downloaded above and I would recommend moving it to the Desktop for easy access.
2) Now connect your phone via USB, and choose internet connection when you click on the USB icon in your notifications pull-down menu; open up a terminal and type:
Code:
cd /home/[your username]/Desktop/android-sdk/platform-tools
sudo ./adb kill-server
sudo ./adb devices
3) This should give you a "List of the devices attached" to your computer with adb. Make sure you see numbers/letters and "device" like so...
Code:
99999B9999ECB9999 device
Note: if you do not get any devices listed, don't , do:
i) Disconnect your phone
ii) Pull the battery for 10 sec.
iii) Restart your computer
iv) go back to step #2
4) Now push the exploit and start it by typing:
Code:
sudo ./adb push /home/[your username]/Desktop/LGRevolutionRoot/zergrush /data/local/tmp/zergrush
sudo ./adb shell "chmod 755 /data/local/tmp/zergrush"
sudo ./adb shell "./data/local/tmp/zergrush"
5) This should start the exploit and you should see the activity in the terminal. When its done you should be prompted with a #.
a) if it is successful, simply click ctrl+Z. This should bring you back to a $ prompt.
b) if it fails
i) Disconnect your phone
ii) Backup ANYTHING you need with mybackup from the android market
iii) Perform a factory reset of your phone in Settings>Privacy>Factory Data Reset
iV) go back to step #2
6) Next we must push the proper files to run the root so type in terminal:
Code:
sudo ./adb shell /data/local/tmp/sh -c "mkdir /system/tmp"
sudo ./adb shell /data/local/tmp/sh -c "chmod 777 /system/tmp"
Code:
sudo ./adb push /home/[your username]/Desktop/LGRevolutionRoot/su /system/tmp/su
sudo ./adb push /home/[your username]/Desktop/LGRevolutionRoot/busybox /system/tmp/busybox
sudo ./adb push /home/[your username]/Desktop/LGRevolutionRoot/Superuser.apk /system/tmp/Superuser.apk
sudo ./adb push /home/[your username]/Desktop/LGRevolutionRoot/RevoToolkit-1.0.apk /data/local/tmp/RevoToolkit-1.0.apk
Code:
sudo ./adb shell /data/local/tmp/sh -c "mv /system/tmp/su /system/xbin/su"
sudo ./adb shell /data/local/tmp/sh -c "mv /system/tmp/Superuser.apk /system/app/Superuser.apk"
sudo ./adb shell /data/local/tmp/sh -c "mv /system/tmp/busybox /system/xbin/busybox"
sudo ./adb shell /data/local/tmp/sh -c "mv /data/local/tmp/RevoToolkit-1.0.apk /data/app/RevoToolkit-1.0.apk"
sudo ./adb shell /data/local/tmp/sh -c "chown root /system/xbin/su"
sudo ./adb shell /data/local/tmp/sh -c "chmod 4755 /system/xbin/su"
sudo ./adb shell /data/local/tmp/sh -c "ln -s /system/xbin/su /system/bin/su"
sudo ./adb shell /data/local/tmp/sh -c "chmod 755 /system/xbin/busybox"
sudo ./adb shell /data/local/tmp/sh -c "/system/xbin/busybox --install /system/xbin/"
7) Everything should be in order now cleanup; type:
Code:
sudo ./adb shell /data/local/tmp/sh -c "rmdir /system/tmp"
sudo ./adb shell "rm /data/local/tmp/* 2>/dev/null"
8) Just left to do is reboot the phone so type:
Code:
sudo ./adb reboot
sudo ./adb kill-server
Congrats! now you should reboot and be completely rooted and have the RevoToolkit to install the CWM recovery.
To install the recovery just start the RevoToolkit app and check for stock recovery and then install CWM.
Then you are free to install proper ROMs/Kernels.
If anyone has any questions please tell me your distro and if you are running virtually or not.
Hope this helps!
Special Thanks:
mtmichaelson for posting the inital thread for the download of his repackaged exploit.
The The Revolutionary Guys for the exploit
djrbliss for the initial script and port
thecubed for RevoToolkit
MikesTooLz for coordinating
While I will probably never use my Linux box to root a phone (one clicks are so easier ) You are my hero for putting this together. A "thanks' to you sir!!
Anytime glad to see someone here uses Linux!
Sent from my SCH-I500 using XDA App
Zoookle said:
Anytime glad to see someone here uses Linux!
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
We all do every day
VS910 4G Kangwich
Lol yes we do, our phones

Onemsomic's ICS 3.1RC no GPS lock!

I wanted to ask this in the actual thread but 10 post limit...
Anyway,
I can't get any GPS lock on my I9000, Onemsomic's ICS RC3.1, JVU modem.
I tried changing the NetworkLocation.apk by following this post http://forum.xda-developers.com/showthread.php?p=21351809#post21351809
but since I have absolutely no idea how to use ADB I couldn't do the "change mode to 0644" step.
Someone help a noob?
Thanks.
Well, first off, download the *.apk provided in that post and place it on the sdcard.
adb is a command line tool, so you must insert those commands on a terminal emulator (maybe you got one installed, if not, download one from the market, I can recommend "Android Terminal Emulator").
So, open your terminal emulator and go to the directory where you placed your *.apk. this example has been wrote with the *.apk in the sdcard folder:
Code:
su
cd /mnt/sdcard
adb start-server
adb remount
adb push NetworkLocation.apk /system/app/NetworkLocation.apk
adb chmod 0644 /system/app/NetworkLocation.apk
adb reboot
Note: I wrote this example following my common sense, so I'm not completely sure if this will work!
Cheers!
AurosGamma said:
Well, first off, download the *.apk provided in that post and place it on the sdcard.
adb is a command line tool, so you must insert those commands on a terminal emulator (maybe you got one installed, if not, download one from the market, I can recommend "Android Terminal Emulator").
So, open your terminal emulator and go to the directory where you placed your *.apk. this example has been wrote with the *.apk in the sdcard folder:
Code:
su
cd /mnt/sdcard
adb start-server
adb remount
adb push NetworkLocation.apk /system/app/NetworkLocation.apk
adb chmod 0644 /system/app/NetworkLocation.apk
adb reboot
Note: I wrote this example following my common sense, so I'm not completely sure if this will work!
Cheers!
Click to expand...
Click to collapse
I get a "device not found" error after adb remount. What should I do?
hadar.shamir said:
I get a "device not found" error after adb remount. What should I do?
Click to expand...
Click to collapse
Well I have been looking here and there, and I found that adb doesn't work directly on the phone, you must use adb from your pc. So, this is what you should do from now on:
Install Java SDK
Install Android SDK
Turn on "USB Debugging" in your SGS settings
Connect the Device to the PC
And finally, use the following commands (from the PC):
Code:
// Go to the folder where you put the *.apk
cd C:\users\exampleuser\Documents\ // or /home/exampleuser/Documents/ if you're using linux
adb start-server
adb remount
adb push NetworkLocation.apk /system/app/NetworkLocation.apk
adb chmod 0644 /system/app/NetworkLocation.apk
adb reboot
Note:
The text after the double-slash ( // ), must not be written in the console, they are just comments
You need to install the SDK's because there it is where the adb tool (and tools needed by adb) is found, so, good luck!

Question Mounting system R/W

Hi,
did anybody successfully mount system R/W?
I tried https://forum.xda-developers.com/t/script-android-10-universal-mount-system-read-write-r-w.4247311/
but it did not work.
Regards,
Hyper
I used https://forum.xda-developers.com/t/...ake-partitions-rw-in-super-partition.4120963/
for stock rom.
NisseGurra said:
I used https://forum.xda-developers.com/t/...ake-partitions-rw-in-super-partition.4120963/
for stock rom.
Click to expand...
Click to collapse
Just forgot, I also tried this one. How did you do it?
I could not find super.sin.
Also when trying to unpack the super image, the Tools says, it would not be a proper super image :-/
You need root and usb debugging
Place the superrepack.arm64_pie in your adb folder and then open an cmd shell:
adb push superrepack.arm64_pie /data/local/tmp
adb shell
su
cd /data/local/tmp
mv superrepack.arm64_pie superrepack
chmod 755 superrepack
stop
Then i used for a-active:
./superrepack /dev/block/bootdevice/by-name/super system_a
./superrepack /dev/block/bootdevice/by-name/super system_ext_a
./superrepack /dev/block/bootdevice/by-name/super product_a
sync
reboot
Can i ask why you want to mount system as RW?
morpheus302 said:
Can i ask why you want to mount system as RW?
Click to expand...
Click to collapse
Without a proper debloating it is not possible to get MicroG running without issues :-/
NisseGurra said:
You need root and usb debugging
Place the superrepack.arm64_pie in your adb folder and then open an cmd shell:
adb push superrepack.arm64_pie /data/local/tmp
adb shell
su
cd /data/local/tmp
mv superrepack.arm64_pie superrepack
chmod 755 superrepack
stop
Then i used for a-active:
./superrepack /dev/block/bootdevice/by-name/super system_a
./superrepack /dev/block/bootdevice/by-name/super system_ext_a
./superrepack /dev/block/bootdevice/by-name/super product_a
sync
reboot
Click to expand...
Click to collapse
Thank you! Gonna try this again.
//EDIT
Unfortunately after reboot I have ramdump. This never happpend before
I exceuted the scripts until all errors were gone.

Categories

Resources