Database Info

[q] is there a way to access system files through recovery/bootloader?

whenever i turn my phone, i get an error that says the com.android.sdksetup application failed or something like that and when forced to close, it would just show up again.
as a result, i'm stuck in that infinite loop, i can only access recovery (3e) and the bootloader. I've tried a factory reset but that only erases user data. Since it runs on 3e recovery, I get signature verification errors when trying to flash to a different rom. I was wondering if there's any way I can access the system files through any of these two modes? the phone is the Gooapple 3g

I dont know about your specific phone, but i managed to get a bit of info from a google search
I believe what yo want to be doing is flashing a recovery that allows you ADB write access to /system (if your recovery doesnt already - try 'adb remount' or 'adb shell mount -o remount,rw /system')
You may need the PdaNetA302.exe file from http://www.alcatel-mobilephones.com/...iew/full/25287 to use USB ADB
This thread may be useful: http://forum.xda-developers.com/showthread.php?t=1252195
the clockworkmod recovery section may be useful as cwm allows read/write access to the /system partition via ADB:
INSTALL CLOCKWORK RECOVERY (orange lantern recovery)
Flashing custom recovery image:
{Non ADB method}
1) Download flash_image and place it on the root of your SD card: http://db.tt/flHRxiG
2) Download recovery.img to the root of your SD card: http://db.tt/uy56zhj
3) Open Terminal Emulator and issue these commands:
Code:
$ su
# cp /sdcard/flash_image /system/bin
# chmod 747 /system/bin/flash_image
# flash_image recovery /sdcard/recovery.img
4) If you see a bunch of successful on your screen then it has flashed properly.
{ADB method}
1) Open up command prompt and issue these commands:
Code:
C:\Users\Your_Name> cd ..
C:\Users> cd ..
2) Navigate to your installed Android SDK (Mine is under the Program Files (x86) folder):
Code:
C:\> cd Program Files (x86)
C:\Program Files (x86)> cd Android/android-sdk/platform-tools
3) Connect your device to your computer and make sure you have USB Debugging enabled on your phone.
4) Issue this command to verify that your computer recognizes your phone:
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools> adb devices
5) If you see your phones serial then it is connected.
6) Download flash_image and place it in the platform-tools folder: http://db.tt/flHRxiG
7) Download the recovery.img and place it on the root of your SD card: http://db.tt/uy56zhj
8) Issue these commands in command prompt:
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools> adb push flash_image /system/bin
C:\Program Files (x86)\Android\android-sdk\platform-tools> adb shell chmod 747 /system/bin/flash_image
C:\Program Files (x86)\Android\android-sdk\platform-tools> adb shell
# flash_image recovery /sdcard/recovery.img
9) If you see a bunch of successful on your screen then it has flashed properly.
boot into recovery, hold home whilst powering on, after 5 long seconds, let go of home and then push home again, you will need to put the volume/menu-back toggle to "volume" mode and according to deepakpitrola333, you need to cycle the list 3 times using volume to allow selection.
Video by mayiandjay;
http://www.youtube.com/watch?v=B_dX9Ruoljo

LG Viper Root

So this is probably the wrong place, but I don't see anywhere more applicable, so please move if necessary.
Bought a LG Viper for the wife today, so had to root it
I found a post elsewhere (can't post URLs yet, but it's on androidcentral) that stated how using SuperOneClick, but personally I'm a CLI kind of guy, so this is for anyone using linux (probably could easily be used on Windows, I think you'd need the "LG Universal Drivers", but )
Getting right to the point, you must have adb installed and working.
Notes: Make sure you've got USB Debugging enabled at this point. Might as well make sure "Unknown Sources" are allowed as well.
Go ahead and plug your phone in to your computer now.
Step 1) Find the device on your computer
In /etc/udev/rules.d/51-android.rules add the following (editing as root):
* Note: I had recently rooted a Kindle Fire and had other config in this file, if you do to you can just prefix the lines with a "#" and it will be ignored. You can find the vendor ID by running 'lsusb'
SUBSYSTEM=="usb", SYSFS{idVendor}=="1004", MODE="0666", OWNER="YOUR-USERNAME", GROUP="YOUR-USERNAME"
Reboot at this point (or restart udev and logout/in)
Step 2) Grab a copy of "rageagaintthecage" and do the following
adb push rageagainstthecage /data/local/tmp
Step 3) Shell time
adb shell
Once you're in the prompt:
chmod 755 /data/local/tmp/rageagainstthecage
/data/local/tmp/rageagainstthecage
* Note: You'll be kicked out out the prompt at this point, as expected.
Step 4) You've got temporary root (if that's all you want, stop now), otherwise let's make it permanent
adb kill-server
adb start-server
adb shell
su
mount -o remount,rw /dev/block/mmcblk0p27 /system
adb push su /system/bin
adb shell chmod 755 /system/bin/su
Step 5) Install tools
On your phone, download "Superuser" and "Busybox Installer"
Run Busybox Installer
Step 6) Enjoy
Post up any questions, glad to help if possible

Which version of su did you use to push to the device?
The temp root has worked but when I go to install Superuser and update I get this error:
Getting exe path failed with 13: Permission denied
Any ideas? Thank.
-Shaun

When I run RATC, how long do I leave it running? I see the adb shell prompt ($) come up, but then the console feeds a line, and doesn't respond. I eventually press ^C to get back to the windows cmd prompt, but I don't know if I'm doing that too soon (it hasn't spawned all the proc it needs to yet) or if it just doesn't work.
when I type "su" into the adb shell after restarting the server, I get
[email protected]:/ $ su
su
/system/bin/sh: su: not found
I pushed a copy of su into /data/local/tmp and made it executable, but that doesn't work.
127|[email protected]:/ $ /data/local/tmp/su
/data/local/tmp/su
reloc_library[1285]: 15938 cannot locate '_mktemp'...
CANNOT LINK EXECUTABLE
255|[email protected]:/ $
Any suggestions?

[Q] 2.20 root on mac?

sorry for the noob question, but i am new to android and new to rooting. is there a way to do this on a mac that isnt running a windows partition? if so is there an explanation?

jasonr803 said:
sorry for the noob question, but i am new to android and new to rooting. is there a way to do this on a mac that isnt running a windows partition? if so is there an explanation?
Click to expand...
Click to collapse
1. Make sure you have installed ADB and FASTBOOT command line tools first. You can install them from here: http://code.google.com/p/adb-fastboot-install/
2. Download djrbliss's exploit files. You can find it here: http://forum.xda-developers.com/showthread.php?t=1952038
3. Extract the entire zip file.
4. Connect your device via USB, ensure USB debugging mode is enabled.
5. Open Terminal and enter into the folder that you extract that zip file.
6. Just type the following command lines step by step:
1. adb wait-for-device
May be you will see this information in your terminal
=======================================
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
=======================================
2. adb restore backup1.ab
3. adb shell "rm /data/data/com.android.providers.telephony/databases/a/b 2>/dev/null"
4. adb shell "ln -s /dev/diag /data/data/com.android.providers.telephony/databases/a/b 2>/dev/null"
5. adb restore backup2.ab
6. adb push pwn /data/local/tmp
After this you can see some information in your terminal like this:
========================================
1180 KB/s (64526 bytes in 0.053s)
========================================
7. adb shell "chmod 755 /data/local/tmp/pwn"
8. adb shell "/data/local/tmp/pwn"
After this if you see this in your terminal that means you are close to success:
========================================
[+] Set CID!
========================================
9. adb reboot bootloader
In this step, just keep waiting until your phone enter into fastboot mode, then excute step 10.
10. adb kill-server
11. fastboot oem readcid
If you see the cid like this you are success!!!
========================================
...
(bootloader) cid: 11111111
OKAY [ 0.010s]
finished. total time: 0.010s
========================================
12. fastboot oem get_identifier_token
Finally you can get your own identifier token.

For some reason the adb commands dont work for me. Is there something I'm missing?
Edit: Figured it out but now I get a "Failed." error when I type adb shell "/data/local/tmp/pwn"

jasonr803 said:
sorry for the noob question, but i am new to android and new to rooting. is there a way to do this on a mac that isnt running a windows partition? if so is there an explanation?
Click to expand...
Click to collapse
instructions have been updated and there is now a script for mac you can execute in terminal
http://forum.xda-developers.com/showpost.php?p=33178597&postcount=1

h1m said:
For some reason the adb commands dont work for me. Is there something I'm missing?
Edit: Figured it out but now I get a "Failed." error when I type adb shell "/data/local/tmp/pwn"
Click to expand...
Click to collapse
I also encounter this problem. Try to factory reset your phone first. I do this then it works fine.

Teclast Tbook 16 Power (M5F8) root

I want to get root.
Does not work.
Turn on USB debugging
Bootloader unlock:
Code:
adb reboot bootloader
fastboot flashing unlock
Erase and flash recovery:
Code:
fastboot erase recovery
fastboot flash recovery TWRP_2_8_7.img
Reboot recovery.
TWRP - Install zip - SuperSU.zip
E:Unable to mount 'factory'
Rebood system.
SuperSU - not installed
Root - not installed
Go to fastboot:
Code:
adb reboot fastboot
Erase and flash recovery:
Code:
fastboot erase recovery
fastboot flash recovery TWRP_3_0_2.img
Reboot recovery.
TWRP - Install zip - SuperSU.zip
Is installed without errors.
Rebood system.
SuperSU - not installed
Root - not installed
---
ADB install:
Code:
adb root
adb remount
adb shell mkdir /system/bin/.ext
adb shell chmod 777 /system/bin/.ext
adb push su /system/bin/.ext/.su
adb shell chmod 6755 /system/bin/.ext/.su
adb push su /system/xbin/su
adb shell chmod 6755 /system/xbin/su
adb push busybox /system/bin/busybox
adb shell chmod 6755 /system/bin/busybox
adb shell mkdir /system/app/SuperSU
adb shell chmod 755 /system/app/SuperSU
adb push SuperSU.apk /system/app/SuperSU/SuperSU.apk
adb shell chmod 644 /system/app/SuperSU/SuperSU.apk
adb reboot
SuperSU - installed, but error on run: "SU Binary occupied"
Root - not installed
Help me please!

Root teclast tbook 16 power (m5f8)
First off, I take no responsibility for bricked devices!
Things you need before you start: charged tbook 16 power (M5F8)
!! usb mouse or keyboard dock, since touch in twrp is NOT working!!
usb-c cable
minimal adb and fastboot https://forum.xda-developers.com/showthread.php?t=2317790
usb drivers https://software.intel.com/en-us/android/articles/intel-usb-driver-for-android-devices
isoc drivers https://androiddatahost.com/te67m
1. Start your tablet and navigate to developer settings. Check usb debugging, oem unlock and uncheck analyse apps through usb
2. download latest magisk.zip to your tablet and put it in the root of the sd card
3. download attached twrp img(https://www.dropbox.com/s/rrngzwq2uvaq05l/TWRP-2.8.7.0_teclast_Tbook16Power-beta03.img?dl=0) and put it in the same folder where adb and fastboot is located
4. Connect the tablet with pc through usb-c cable
5. install minimal adb and fastboot
6. Sart a command prompt in the folder where adb is located (shift + right click)
7. type -adb reboot fastboot- and click enter (tablet enters fastboot mode)
8. type -fastboot flashing unlock- (!!! caution !!! USERDATA of android will be ERASED, like factory reset) and click enter
9. type -fastboot boot TWRP-2.8.7.0_teclast_Tbook16Power-beta03.img- and click enter
10. on twrp swipe right(mouse or keyboard dock needed!) to allow modifications, if it aksks you to root your device click no
11. click install and navigate to the magisk.zip file located on the tablet. click install, magisk will be installed and your device will be rooted
12. click reboot, first reboot takes about 5 minutes. Voilà!

It works!
Very good!
Thank you!

Thank you very much!!!

easy way, thank you.

Hi, I tried this guide just a teclast tbook 16 power, but it doesn't work for me, I don't install Magisk-v18.1.zip, from compatibility errors.
Why?

[HELP] Need help running command 'fastboot erase modemst1' on Pixel 5

After the March security update my Pixel 5 is not receiving any mobile network and i am not able to turn on radio power via the *#*#4636#*# command.
After googling for a solution i found similar posts which suggested resetting the modemst1 and 2 partitions
Tried running the following commands in adb but was unable to
Code:
adb shell 'dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1'
adb shell 'dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2'
For fastboot I used the following commands
Code:
fastboot erase modemst1
fastboot erase modemst2
which gave me an error
Code:
FAILED (remote: Not allowed to erase (modemst1))
I'm also not able to boot into adb root but i am able to run adb shell su
I tried installing adbd insecure which was unable to patch adbd and also installed an adb_root module in magisk which still failed to initialize adb root
Currently I'm running ProtonOS on my Pixel 5. I thought running a custom rom might help but the problem still persists
Please help

Hi.
I would suggest making a back up before you erase a partition in case you need to restore it.
Make sure to name the backup clearly so you know what it is.
Since you do not have adb root, you need to run the command as root using su -c "NameOfCommand".
If you boot into a custom recovery, you generally have adbd and do not need to use the su -c option.
Also double check your path, you should be able to call it from /dev/block/by-name.
or list by-name, ls -la /dev/block/by-name/ and call it from the true partition number.
Example of making a backup.
Dump the partition(s) into an image.
Code:
adb shell su -c "dd if=/dev/block/by-name/modemst1 of=/sdcard/redfin-modemst1.img"
adb shell su -c "dd if=/dev/block/by-name/modemst2 of=/sdcard/redfin-modemst2.img"
Copy the image(s) to computer.
Code:
adb pull /sdcard/redfin-modemst1.img
adb pull /sdcard/redfin-modemst2.img
Delete the image(s) from the device.
Code:
adb shell rm /sdcard/redfin-modemst1.img
adb shell rm /sdcard/redfin-modemst2.img
You need to be in fastbootd to modify critical partitions.
adb reboot bootloader will reboot into fastboot.
adb reboot fastboot will reboot into fastbootd.
You can do the same in fastboot/fastbootd
fastboot reboot bootloader will reboot into fastboot.
fastboot reboot fastboot will reboot into fastbootd.
Be Careful.
There are always risks involved when you start messing around with a device.
If something goes wrong, you may end up with a non-working "bricked" device.
This is especially true when you start modifying partitions.
Good luck.
Cheers.

ipdev said:
Hi.
I would suggest making a back up before you erase a partition in case you need to restore it.
Make sure to name the backup clearly so you know what it is.
Since you do not have adb root, you need to run the command as root using su -c "NameOfCommand".
If you boot into a custom recovery, you generally have adbd and do not need to use the su -c option.
Also double check your path, you should be able to call it from /dev/block/by-name.
or list by-name, ls -la /dev/block/by-name/ and call it from the true partition number.
Example of making a backup.
Dump the partition(s) into an image.
Code:
adb shell su -c "dd if=/dev/block/by-name/modemst1 of=/sdcard/redfin-modemst1.img"
adb shell su -c "dd if=/dev/block/by-name/modemst2 of=/sdcard/redfin-modemst2.img"
Copy the image(s) to computer.
Code:
adb pull /sdcard/redfin-modemst1.img
adb pull /sdcard/redfin-modemst2.img
Delete the image(s) from the device.
Code:
adb shell rm /sdcard/redfin-modemst1.img
adb shell rm /sdcard/redfin-modemst2.img
You need to be in fastbootd to modify critical partitions.
adb reboot bootloader will reboot into fastboot.
adb reboot fastboot will reboot into fastbootd.
You can do the same in fastboot/fastbootd
fastboot reboot bootloader will reboot into fastboot.
fastboot reboot fastboot will reboot into fastbootd.
Be Careful.
There are always risks involved when you start messing around with a device.
If something goes wrong, you may end up with a non-working "bricked" device.
This is especially true when you start modifying partitions.
Good luck.
Cheers.
Click to expand...
Click to collapse
Hello, I hope you will see this text. As you have mentioned, I have rebooted my Pixel 5 to fastbootd but I cannot erase any critical partition. for example, when i run fastboot erase cache OR fastboot erase modemst1, i get the same error message saying FAILED (remote: 'Partition doesn't exist'). Would you mind helping me? I would appreciate it a lot. Thank you.