Related
Hi,
Just a little help for me please, I try to launch some adb command with SU
In my little head, I have think translate your code with the SU call before
Code:
adb shell uname -r
become
Code:
adb shell su uname -r
With the first command, all is good I have my answer, with the su first I have
Code:
Permission Denied
I have a DESIRE (bravo) rooted and S-OFF, what did I do wrong ?
The Linux su expects a user name as parameter, not a command. As far as I can see, the Android su simply ignores this parameter. If you want su to execute a command, use the -c option, like in
Code:
su -c uname -r
This causes su to execute "uname -r" as root, after that it returns immediately, so you're back at the user level you've been before. This might not be what you expect, but that's how it works.
Your permission error: Try a single su command, without any arguments or options. If it also returns a permission error, you're not rooted. It should ask you at the mobile's display for permission if you're rooted and you are doing that for the first time.
Thx U dude, U R the one
Hey guys, today I'm going to tell you how to backup & restore few things of your phone without using a pc. So let's get started without wasting any time...
Things you gonna need:
1) Busybox installed (Stericson is recommended)
3) A SD-Card inserted to your phone with some free space to backup things
2) Any terminal emulator
3) Patience & some common sense.
First I'll say you how to backup things & later I'll say how to restore them...
How To Backup:
Code:
•Boot.img :
In terminal emulator type the following:
dd if=/dev/block/mmcblk0p7 of=/sdcard/backups/boot.img
• Logo.bin :
In terminal emulator type the following:
dd if=/dev/block/mmcblk0p11 of=/sdcard/backups/logo.bin
• Nvram.img :
In terminal emulator type the following:
dd if=/dev/block/mmcblk0p2 of=/sdcard/backups/nvram.img
• Recovery.img :
In terminal emulator type the following:
dd if=/dev/block/mmcblk0p8 of=/sdcard/backups/recovery.img
• System.img :
In terminal emulator type the following:
dd if=/dev/block/mmcblk0p14 of=/sdcard/backups/system.img
• Userdata.img :
In terminal emulator type the following:
dd if=/dev/block/mmcblk0p16 of=/sdcard/backups/userdata.img
(Proceed with caution...)
How To Restore:
Code:
•Boot.img :
In terminal emulator type the following:
dd if=/sdcard/backups/boot.img of=/dev/block/mmcblk0p7
• Logo.bin :
In terminal emulator type the following:
dd if=/sdcard/backups/logo.bin of=/dev/block/mmcblk0p11
• Nvram.img :
In terminal emulator type the following:
dd if=/sdcard/backups/nvram.img of=/dev/block/mmcblk0p2
• Recovery.img :
In terminal emulator type the following:
dd if=/sdcard/backups/recovery.img of=/dev/block/mmcblk0p8
• System.img :
In terminal emulator type the following:
dd if=/sdcard/backups/system.img of=/dev/block/mmcblk0p14
• Userdata.img :
In terminal emulator type the following:
dd if=/sdcard/backups/userdata.img of=/dev/block/mmcblk0p16
If this post helped you then please hit thanks, & feel free to ask any doubts or questions...
Reserved!!
Reserved to blame you if this goes wrong!!!
It goes without saying that dd'ing a .img to a wrong partition number (.../mmcblk0pxx) will probably brick your device, if it's some critical partition that just got overwritten with something else.
Don't mess with dd unless you must. dd doesn't ask for confirmation. Triple check the command before pressing enter when restoring, or you'll regret it.
juanchotazo99 said:
It goes without saying that dd'ing a .img to a wrong partition number (.../mmcblk0pxx) will probably brick your device, if it's some critical partition that just got overwritten with something else.
Don't mess with dd unless you must. dd doesn't ask for confirmation. Triple check the command before pressing enter when restoring, or you'll regret it.
Click to expand...
Click to collapse
I agree. You really should put some kind of warning because with dd, well...here be dragons..
THIS IS THE START THREAD FOR ANY XDA ENTHUSIAST!!keep in mind, that you do all these steps on your own and i am not responsible for any damaged or bricked phone.
So if you dont know what are you doing or are afraid of bricking your device, please dont do this!!!
!BEFORE YOU START, PLEASE READ THIS!
And don´t forget to thank Famewolf for the tutorial, because this could save your phone when something go bad!
UNLOCK BOOTLOADER:
-Get/install Alcatel USB driver if Windows. (no need for Mac). FROM HERE, or just connect your idol3 to the computer and from the phone select "cd rom" drive..it will install the drivers automatically
-download the root zip from my GOOGLE DRIVE and unzip it.
-Set USB debugging on in Developer settings (if these are not exposed, go to Settings/About Phone/Build number, and tap 7 times.)
-Plug in USB cable to phone and computer. Tap on USB icon in notifications panel; select MTP (file transfer) mode.
-After that a window on your phone should appear and ask you to allows usb debbuging connection to your attached computer (please also check the box that say something like "always from this computer")
-Open command prompt in direcotry where you have the unzipped files (when using windows in the direcotry hold shift and press the right button on the mouse, it will pop-up a window where you have to select "open command promt here"
-type "adb reboot-bootloader" to reboot into bootloader. The device should reboot to the screen showing "alcatel onetouch...powered by android". This is bootloader mode.
-Then type "fastboot -i 0x1bbb devices" should show some numbers and "fastboot" after the numbers
-Type "fastboot -i 0x1bbb oem device-info" shows device info including bootloader status (e.g. locked).
-Type "fastboot -i 0x1bbb oem unlock" to unlock the bootloader; after this you should get, for device info,
-Type "fastboot -i 0x1bbb oem device-info" and you should see "Device unlocked: true"
-To reboot normally: "fastboot -i 0x1bbb reboot"
ROOT USING CUSTOM RECOVERY:
as we have now the custom recovery (TWRP)
-So download supersu.zip from HERE
-Put it on your SD card (or internal memory)
-Flash (or just boot) the custom recovery (you can see the procedure in the thread i linked above) and in recovery install the superSU.zip
-Reboot
ROOT:
-Plug in USB cable to phone and computer. Tap on USB icon in notifications panel; select MTP (file transfer) mode.
-Run the unziped "root.bat" file and select option 1.
-The device will reboot to bootloader,then boot the boot.img which will install the SU and then the device will twice reboot
-check if you have superSU installed, if yes, then You are done.
BACKUP under windows:
-so now you have root rights and you can what ever you want, but first do not forget to backup your device
-for that occasion i made a simple BACKUP_all.bat file
-download the file and place it to the directory, where you extracted the root.zip
-run the bat file it will create a backup folder on external sd card in the phone! extract the system partitions and in the end it copies it to the subdirectory "blocks" in the dir where you ran the bat file.
BE AWARE to share the modemst and persist files because they are device specific!!!
here is the code:
PHP:
@echo BACKUP IDOL3 6045 partitions by DallasCZ
adb shell mkdir /storage/sdcard1/mybckup
echo Press any key to begin
pause >nul
adb shell su -c "dd if=/dev/block/mmcblk0p1 of=/storage/sdcard1/mybckup/modem"
adb shell su -c "dd if=/dev/block/mmcblk0p2 of=/storage/sdcard1/mybckup/tunning"
adb shell su -c "dd if=/dev/block/mmcblk0p3 of=/storage/sdcard1/mybckup/traceability"
adb shell su -c "dd if=/dev/block/mmcblk0p4 of=/storage/sdcard1/mybckup/fsc"
adb shell su -c "dd if=/dev/block/mmcblk0p5 of=/storage/sdcard1/mybckup/ssd"
adb shell su -c "dd if=/dev/block/mmcblk0p6 of=/storage/sdcard1/mybckup/sbl1"
adb shell su -c "dd if=/dev/block/mmcblk0p8 of=/storage/sdcard1/mybckup/rpm"
adb shell su -c "dd if=/dev/block/mmcblk0p10 of=/storage/sdcard1/mybckup/tz"
adb shell su -c "dd if=/dev/block/mmcblk0p12 of=/storage/sdcard1/mybckup/hyp"
adb shell su -c "dd if=/dev/block/mmcblk0p14 of=/storage/sdcard1/mybckup/modemst1"
adb shell su -c "dd if=/dev/block/mmcblk0p15 of=/storage/sdcard1/mybckup/modemst2"
adb shell su -c "dd if=/dev/block/mmcblk0p16 of=/storage/sdcard1/mybckup/simlock"
adb shell su -c "dd if=/dev/block/mmcblk0p17 of=/storage/sdcard1/mybckup/persistent"
adb shell su -c "dd if=/dev/block/mmcblk0p18 of=/storage/sdcard1/mybckup/splash"
adb shell su -c "dd if=/dev/block/mmcblk0p19 of=/storage/sdcard1/mybckup/tctpersist"
adb shell su -c "dd if=/dev/block/mmcblk0p20 of=/storage/sdcard1/mybckup/hdcp"
adb shell su -c "dd if=/dev/block/mmcblk0p21 of=/storage/sdcard1/mybckup/DDR"
adb shell su -c "dd if=/dev/block/mmcblk0p22 of=/storage/sdcard1/mybckup/fsg"
adb shell su -c "dd if=/dev/block/mmcblk0p23 of=/storage/sdcard1/mybckup/sec"
adb shell su -c "dd if=/dev/block/mmcblk0p24 of=/storage/sdcard1/mybckup/aboot"
adb shell su -c "dd if=/dev/block/mmcblk0p26 of=/storage/sdcard1/mybckup/boot"
adb shell su -c "dd if=/dev/block/mmcblk0p27 of=/storage/sdcard1/mybckup/recovery"
adb shell su -c "dd if=/dev/block/mmcblk0p28 of=/storage/sdcard1/mybckup/system"
adb shell su -c "dd if=/dev/block/mmcblk0p29 of=/storage/sdcard1/mybckup/persist"
adb shell su -c "dd if=/dev/block/mmcblk0p30 of=/storage/sdcard1/mybckup/fota"
adb shell su -c "dd if=/dev/block/mmcblk0p32 of=/storage/sdcard1/mybckup/misc"
adb shell su -c "dd if=/dev/block/mmcblk0p33 of=/storage/sdcard1/mybckup/keystore"
adb shell su -c "dd if=/dev/block/mmcblk0p34 of=/storage/sdcard1/mybckup/config"
@echo BACKUP copied partitions to hard drive
@mkdir blocks
adb pull /storage/sdcard1/mybckup %CD%/blocks/
@echo BACKUP Done!
@echo Press any key to exit
@ECHO OFF
@pause >nul
FOR LINUX USERS:
for unlocking the bootloader see THIS POST by Fankee207
for backup on linux please see THIS POST by Frankee207
and dont forget to thank him. :good:
If someone send me a linux/mac guide i will post it to this post so we have all the info in one thread.
reservation 1
reservation 2
To unlock bootloader on linux, just make sure adb and fastboot are installed
Code:
sudo apt-get install android-tools-adb android-tools-fastboot
on ubuntu based linux for example. No need to install full SDK.
just add sudo before each command
Ex:
Code:
sudo fastboot -i 0x1bbb oem unlock
Should work, but I'have not tried myself since I have not received my idol yet
No need specific drivers. Before beginning, you can run
Code:
adb devices
to make sure your device is correctly detected
Don't forget if problem with adb on linux, run
Code:
sudo adb kill-server
sudo adb start-server
Thnaks you for the backup script. May I share it on french android forum forum.frandroid.com ?
frankee207 said:
Thnaks you for the backup script. May I share it on french android forum forum.frandroid.com ?
Click to expand...
Click to collapse
Of course you can..no wait ...you must!
Awesome it works on dual sim? 6045k? I need to send my ohone to repair the microphone so i will lost the warranty right? I need to wait few months:/
DallasCZ said:
Of course you can..no wait ...you must!
Click to expand...
Click to collapse
thansk you ,I will !
Running both Linux and Windows, I converted your script for Linux usage. Please find it here.
PHP:
echo -e "#### Backup all your idol 3's partitions - DallasCZ & frankee207 @XDA ####\n\n"
echo -e "Please make sure your device is connected\n"
read -p "Press ENTER to continue"
cd ~/
echo -e "/!\ root access must be granted for using adb on linux /!\ \n"
sudo adb kill-server
sudo adb start-server
sudo adb shell mkdir /storage/sdcard1/mybckup/
sudo adb shell su -c "dd if=/dev/block/mmcblk0p1 of=/storage/sdcard1/mybckup/modem"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p2 of=/storage/sdcard1/mybckup/tunning"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p3 of=/storage/sdcard1/mybckup/traceability"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p4 of=/storage/sdcard1/mybckup/fsc"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p5 of=/storage/sdcard1/mybckup/ssd"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p6 of=/storage/sdcard1/mybckup/sbl1"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p8 of=/storage/sdcard1/mybckup/rpm"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p10 of=/storage/sdcard1/mybckup/tz"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p12 of=/storage/sdcard1/mybckup/hyp"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p14 of=/storage/sdcard1/mybckup/modemst1"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p15 of=/storage/sdcard1/mybckup/modemst2"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p16 of=/storage/sdcard1/mybckup/simlock"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p17 of=/storage/sdcard1/mybckup/persistent"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p18 of=/storage/sdcard1/mybckup/splash"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p19 of=/storage/sdcard1/mybckup/tctpersist"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p20 of=/storage/sdcard1/mybckup/hdcp"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p21 of=/storage/sdcard1/mybckup/DDR"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p22 of=/storage/sdcard1/mybckup/fsg"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p23 of=/storage/sdcard1/mybckup/sec"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p24 of=/storage/sdcard1/mybckup/aboot"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p26 of=/storage/sdcard1/mybckup/boot"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p27 of=/storage/sdcard1/mybckup/recovery"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p28 of=/storage/sdcard1/mybckup/system"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p29 of=/storage/sdcard1/mybckup/persist"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p30 of=/storage/sdcard1/mybckup/fota"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p32 of=/storage/sdcard1/mybckup/misc"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p33 of=/storage/sdcard1/mybckup/keystore"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p34 of=/storage/sdcard1/mybckup/config"
sudo mkdir blocks/
sudo adb pull /storage/sdcard1/mybckup/ ~/blocks/
echo -e "Backup done ! You can find it in ~/blocks/"
read -p "Press ENTER to exit"
exit
You can download the script here: https://mega.nz/#!QtEG3TSb!DJ8N1dVRUYNPOLk8kQj2ggZfx8o5M9whiag5WFfANtc
If you use the script for linux, don't forget to make it executable by running
Code:
sudo chmod +x backup_all_AOTI3.sh
It work on 6045k or not? Thank you for the tutorial
---------- Post added at 02:27 PM ---------- Previous post was at 02:23 PM ----------
Another question we will have problems with a next update?
during the root process, does it really "flash" a boot.img?
from the batch file, it appears we are booting a boot.img, from which we [presumably] push supersu to the system. thanks.
deepasadish said:
during the root process, does it really "flash" a boot.img?
from the batch file, it appears we are booting a boot.img, from which we [presumably] push supersu to the system. thanks.
Click to expand...
Click to collapse
my mistake, of course it only boot to the boot.img
I get device not found on adb and the drivers url isn't working i used the phone usb cd... Drivers
RodrigoIsaac said:
I get device not found on adb and the drivers url isn't working i used the phone usb cd... Drivers
Click to expand...
Click to collapse
you have to install the drivers from the phone mounted as Cd and then enable the usb debugging...
I clicked sevenntimes in debugging mode, I installed thebphone as drivers cd (on pc clicked onbsetup, install) then disconnected and connect again, open prompt in idol3_6045_root folder (shift right click...) wrote adb reboot bootloader. Then appeared not running daemon. Starting it now on pprt 5037 daemon started successfully error:device not found
But the dispositive is connected and can access the files etc... I tried in two diffdifferent pc's. Tank you for your help
you have enable usb debbuging in developer settings, then you have to switch the connect mode feom cd to PTP
Error: device not found
I think the drivers are not installed because when e conect in mtp or ptp it install the drivers again so i unistall the drivers and connect on cd again and install the drivers then i change to mtp and the pc install the drivers automatically if i change to ptp the same thing happens
reboot computer
Iagain the same error :'( i don't know what is going on.
for me worked to download pdanet software, or try to google adb drivers... will make research when i am at home, now i am drinking beer...
Ok, tank you so much, i will really happy when it's possible to use root apps, sorry my bad english ehehe
---------- Post added at 04:14 PM ---------- Previous post was at 04:02 PM ----------
Unlock worked, i activate debugging but not check ☑ on usb settings on notification bar
---------- Post added at 04:21 PM ---------- Previous post was at 04:14 PM ----------
Rooted successfully omg tank you, tank you!!!!!!
frankee207 said:
thansk you ,I will !
Running both Linux and Windows, I converted your script for Linux usage. Please find it here.
PHP:
echo -e "#### Backup all your idol 3's partitions - DallasCZ & frankee207 @XDA####\n\n"
echo -e "Please make sure your device is connected\n"
read -p "Press any key to continue"
cd ~/
echo -e "/!\ root must be granted for using adb on linux\n"
sudo adb kill-server
sudo adb start-server
sudo adb shell mkdir /storage/sdcard1/mybackup/
sudo adb shell su -c "dd if=/dev/block/mmcblk0p1 of=/storage/sdcard1/mybckup/modem"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p2 of=/storage/sdcard1/mybckup/tunning"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p3 of=/storage/sdcard1/mybckup/traceability"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p4 of=/storage/sdcard1/mybckup/fsc"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p5 of=/storage/sdcard1/mybckup/ssd"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p6 of=/storage/sdcard1/mybckup/sbl1"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p8 of=/storage/sdcard1/mybckup/rpm"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p10 of=/storage/sdcard1/mybckup/tz"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p12 of=/storage/sdcard1/mybckup/hyp"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p14 of=/storage/sdcard1/mybckup/modemst1"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p15 of=/storage/sdcard1/mybckup/modemst2"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p16 of=/storage/sdcard1/mybckup/simlock"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p17 of=/storage/sdcard1/mybckup/persistent"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p18 of=/storage/sdcard1/mybckup/splash"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p19 of=/storage/sdcard1/mybckup/tctpersist"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p20 of=/storage/sdcard1/mybckup/hdcp"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p21 of=/storage/sdcard1/mybckup/DDR"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p22 of=/storage/sdcard1/mybckup/fsg"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p23 of=/storage/sdcard1/mybckup/sec"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p24 of=/storage/sdcard1/mybckup/aboot"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p26 of=/storage/sdcard1/mybckup/boot"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p27 of=/storage/sdcard1/mybckup/recovery"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p28 of=/storage/sdcard1/mybckup/system"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p29 of=/storage/sdcard1/mybckup/persist"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p30 of=/storage/sdcard1/mybckup/fota"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p32 of=/storage/sdcard1/mybckup/misc"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p33 of=/storage/sdcard1/mybckup/keystore"
sudo adb shell su -c "dd if=/dev/block/mmcblk0p34 of=/storage/sdcard1/mybckup/config"
sudo mkdir blocks/
sudo adb pull /storage/sdcard1/mybackup/ ~/blocks/
echo -e "Backup done ! You can find it in ~/blocks/"
read -p "Press any key to exit"
exit
You can download the script here: https://mega.nz/#!E9MnGSjR!XHreY39vw7YIxFqOncDZNcBfn5LSgdhYsbcO4DGlubM
If you use the script for linux, don't forget to make it executable by running
Code:
sudo chmod +x backup_all_AOTI3.sh
Click to expand...
Click to collapse
%frankee207, there is at least one error in your backup script: you create a directory "mybackup" but then you try to write to a directory "mybckup". You will need to change one name or the other.
I will try a corrected version later today on my Mac (in general most stuff for linux should also work on Mac, though you don't need to run as root on the mac to run adb, so "sudo adb" can be replaced by "adb".)
SOLUTION: post #18
Hello,
For some reason all of my sensors are gone. See attachment.
Due to some problems i've formatted my "persist" partition. And from what i read, that partition contains all sorts of sensor parameters. So i guess i shouldn't have.
I've checked all files on the forum and original OTA's from oneplus. None of them have (working) partition for me.
Therefor i would like to ask someone with an A2003 device who has working sensors and is running OOS 3.02 or CM13 to perform the following actions and share the file with me:
(root (adb and apps) needed)
Code:
adb shell
su
su
cd /sdcard
dd if=/dev/block/bootdevice/by-name/persist persist.dd.img
exit
exit
And share the file "persist.dd.img" with me. It's on your sdcard.
Thanks very much in advance!
_HugoBoss_ said:
Hello,
For some reason all of my sensors are gone. See attachment.
Due to some problems i've formatted my "persist" partition. And from what i read, that partition contains all sorts of sensor parameters. So i guess i shouldn't have.
I've checked all files on the forum and original OTA's from oneplus. None of them have (working) partition for me.
Therefor i would like to ask someone with an A2003 device who has working sensors and is running OOS 3.02 or CM13 to perform the following actions and share the file with me:
(root (adb and apps) needed)
Code:
adb shell
su
su
cd /sdcard
dd if=/dev/block/bootdevice/by-name/persist persist.dd.img
exit
exit
And share the file "persist.dd.img" with me. It's on your sdcard.
Thanks very much in advance!
Click to expand...
Click to collapse
I uploaded it to AFH a while back - it's the stock persist.img from the OnePlus 2.2.0 Qualcomm Recovery Package. AFAIK, it's not been updated since then.
persist.img
Spannaa said:
I uploaded it to AFH a while back - it's the stock persist.img from the OnePlus 2.2.0 Qualcomm Recovery Package. AFAIK, it's not been updated since then.
persist.img
Click to expand...
Click to collapse
Hi,
Yeah, google found it for me. But sadly, it didn't work for me.
I've tryed installing it
- trough fastboot (fastboot flash persist persist.img) and also
- dd'ing it and also
- creating a flashable zip package_extract_file("persist.img", "/dev/block/bootdevice/by-name/persist");
but none of it worked.. so i was kinda hoping for a newer version.
btw..
Code:
mount | grep persist
shows that the persist partition is mounted RW.
if someone could do the following:
Code:
adb shell
su
su
cd /sdcard
mkdir persist
cd persist
rsync -av /persist .
exit
exit
then zip the content of the folder persist on your sdcard.. would like to try that too.
_HugoBoss_ said:
btw..
Code:
mount | grep persist
shows that the persist partition is mounted RW.
if someone could do the following:
Code:
adb shell
su
su
cd /sdcard
mkdir persist
cd persist
rsync -av /persist .
exit
exit
then zip the content of the folder persist on your sdcard.. would like to try that too.
Click to expand...
Click to collapse
Code:
/system/bin/sh: rsync: not found
Spannaa said:
Code:
/system/bin/sh: rsync: not found
Click to expand...
Click to collapse
instead of
Code:
rsync -av /persist .
type
Code:
cp -r /persist .
Thanks
_HugoBoss_ said:
instead of
Code:
rsync -av /persist .
type
Code:
cp -r /persist .
Thanks
Click to expand...
Click to collapse
Code:
cp: No /persist: Permission denied
Spannaa said:
Code:
cp: No /persist: Permission denied
Click to expand...
Click to collapse
Are you root?
su
su
_HugoBoss_ said:
Are you root?
su
su
Click to expand...
Click to collapse
Yes
Code:
C:\Users\spannaa\Desktop>adb shell
[email protected]:/ $ su
1|[email protected]:/ $ su
1|[email protected]:/ $ cd /sdcard
[email protected]:/sdcard $ mkdir persist
[email protected]:/sdcard $ cd persist
[email protected]:/sdcard/persist $ cp -r /persist .
cp: No /persist: Permission denied
1|[email protected]:/sdcard/persist $
Spannaa said:
Yes
Code:
C:\Users\spannaa\Desktop>adb shell
[email protected]:/ $ su
1|[email protected]:/ $ su
1|[email protected]:/ $ cd /sdcard
[email protected]:/sdcard $ mkdir persist
[email protected]:/sdcard $ cd persist
[email protected]:/sdcard/persist $ cp -r /persist .
cp: No /persist: Permission denied
1|[email protected]:/sdcard/persist $
Click to expand...
Click to collapse
use "whoami" to check if you're really root..
Code:
su
[email protected]:/ # whoami
root
Spannaa said:
Yes
C:\Users\spannaa\Desktop>adb shell
[email protected]:/ $ su
1|[email protected]:/ $ su
1|[email protected]:/ $ cd /sdcard
[email protected]:/sdcard $ mkdir persist
[email protected]:/sdcard $ cd persist
[email protected]:/sdcard/persist $ cp -r /persist .
cp: No /persist: Permission denied
1|[email protected]:/sdcard/persist $
Click to expand...
Click to collapse
You don't have root access dude, the " 1| " means that an error occurred. Furthermore, check your prompt, still " $ " instead of " # " .
Got there in the end...
Code:
C:\Users\spannaa\Desktop>adb shell
[email protected]:/ $ su
[email protected]:/ # su
[email protected]:/ # cd /sdcard
[email protected]:/sdcard # mkdir persist
[email protected]:/sdcard # cd persist
[email protected]:/sdcard/persist # cp -r /persist .
cp: product_calib_ref1.dat: Function not implemented
cp: product_calib_ref2.dat: Function not implemented
cp: product_calib_ref3.dat: Function not implemented
cp: unit_calib_ref1.dat: Function not implemented
cp: unit_calib_ref2.dat: Function not implemented
cp: unit_calib_ref3.dat: Function not implemented
cp: mixer_paths.xml: Function not implemented
cp: sw_calib.dat: Function not implemented
1|[email protected]:/sdcard/persist #
Let me know when you've grabbed the attached zip and I'll delete it
Spannaa said:
Got there in the end...
Code:
C:\Users\spannaa\Desktop>adb shell
[email protected]:/ $ su
[email protected]:/ # su
[email protected]:/ # cd /sdcard
[email protected]:/sdcard # mkdir persist
[email protected]:/sdcard # cd persist
[email protected]:/sdcard/persist # cp -r /persist .
cp: product_calib_ref1.dat: Function not implemented
cp: product_calib_ref2.dat: Function not implemented
cp: product_calib_ref3.dat: Function not implemented
cp: unit_calib_ref1.dat: Function not implemented
cp: unit_calib_ref2.dat: Function not implemented
cp: unit_calib_ref3.dat: Function not implemented
cp: mixer_paths.xml: Function not implemented
cp: sw_calib.dat: Function not implemented
1|[email protected]:/sdcard/persist #
Let me know when you've grabbed the attached zip and I'll delete it
Click to expand...
Click to collapse
Yeah, downloaded it.. thanks!
Gonna play with it. Thanks!!
Spannaa said:
Got there in the end...
Code:
C:\Users\spannaa\Desktop>adb shell
[email protected]:/ $ su
[email protected]:/ # su
[email protected]:/ # cd /sdcard
[email protected]:/sdcard # mkdir persist
[email protected]:/sdcard # cd persist
[email protected]:/sdcard/persist # cp -r /persist .
cp: product_calib_ref1.dat: Function not implemented
cp: product_calib_ref2.dat: Function not implemented
cp: product_calib_ref3.dat: Function not implemented
cp: unit_calib_ref1.dat: Function not implemented
cp: unit_calib_ref2.dat: Function not implemented
cp: unit_calib_ref3.dat: Function not implemented
cp: mixer_paths.xml: Function not implemented
cp: sw_calib.dat: Function not implemented
1|[email protected]:/sdcard/persist #
Let me know when you've grabbed the attached zip and I'll delete it
Click to expand...
Click to collapse
At least it seems to contain more data, but i can't seem to get it fully working.
Could you perhaps do the following from TWRP:
advanced -> terminal
then type
Code:
cd /sdcard
dd if=/dev/block/bootdevice/by-name/persist of=persist.dd.img
exit
Then from android, grab the persist.dd.img and share it with me?
_HugoBoss_ said:
At least it seems to contain more data, but i can't seem to get it fully working.
Could you perhaps do the following from TWRP:
advanced -> terminal
then type
Code:
cd /sdcard
dd if=/dev/block/bootdevice/by-name/persist of=persist.dd.img
exit
Then from android, grab the persist.dd.img and share it with me?
Click to expand...
Click to collapse
Done.
Spannaa said:
Done.
Again, let me know when you've downloaded it.
Click to expand...
Click to collapse
Thanks A LOT.
SENSORS WORK...
but hold your horses.. Couple of things i find right away..
First boot: it doesn't recognize SIM cards anymore.. Second boot, they are recognized.
Then: when i switch to MTP (file transfer), phone reboots.
So have to see whether it's all stable or not.
Delete the attachment for now.. i'll work on it a couple of days and let you know.
Again, thanks a lot!!
Proof:
Ok, at this point i'm not sure what is related and what is not anymore.
One thing i know for sure: simply copying the persist partition from one phone to another IS working, however the partitions holds some device- (like mac addresses) and maybe even some user-specific information. So it would not be right to start sharing that in the wild.
But while experimenting with the data, i found myself in a pretty f*cked up situation where there was no booting OS anymore and the Oneplus told me the bootloader was unlocked but refused to flash files trough fastboot anymore. Basically a dead phone.
Thank god i created a nandroid (full TWRP) backup and copied it to my laptop.
Long story short: i needed to perform a full repair of my phone and started looking for brick-guides.
The following worked for me AND magically repaired my persist partition too.
Steps to take:
- perform a full TWRP backup of your phone and copy it to your computer (don't keep it ON the phone!)
- also backup everything on your internal memory (sdcard) that is worth keeping. This process will also wipe your internal memory.
- Download the files from this guide. I've used method 3. The others may work. 3 worked for me.
- shutdown your phone
- press volume up and then connect the usb cable. Only volume up!
- the phone won't really power on, but your computer will detect a device. Use the driver you downloaded from the page above.
- When the driver is installed, start the MSM8994DownloadTool.exe as administrator (right click: run as administrator!)
- It's chinese or some language i can't uderstand. But just hit the start button. Some green text will show the progress.
- In the end, your phone will ask you if it's OK to wipe all user data. I did.
- And then it boots to Oxygen OS.
From this point on it's back to normal business
- flash custom recovery trough fastboot
- copy your TWRP backup back to the phone
- restore the backup
- Oh and don't forget: all your firmwares are OLD now. So in order to run CM13 or some other marshmellow rom, you also need to flash that "Switch_tOS3_H2OSMMv3.zip" like you did before!
- restore any other data to your internal memory (sdcard)
There ya go. Fully working system with sensors and all
Good luck!
So after you did the Qualcomm recovery does cpuz still show the sensors as uncalibrated like the screenshot in post 17. I have some issues with my screen rotation as randomly it was not switch to landscape. My cpuz shows gyroscope calibrated and uncalibrated, any way to calibrate gyroscope without that Qualcomm recovery? I had to go through that process in March.
Dude_Virus said:
So after you did the Qualcomm recovery does cpuz still show the sensors as uncalibrated like the screenshot in post 17. I have some issues with my screen rotation as randomly it was not switch to landscape. My cpuz shows gyroscope calibrated and uncalibrated, any way to calibrate gyroscope without that Qualcomm recovery? I had to go through that process in March.
Click to expand...
Click to collapse
It still says so yes. Even now, after more than a month.
However, everything still works fantastic. No issues whatshowever.
Been reading this guide here --» https://forum.xda-developers.com/v20/development/dirtysanta-h990-t3624296
despite much of a mess that it is and poorly written in some regards. I can make perfectly good sense of it all, but the commands issued most of them are pretty useless, or don't work as they're instructed to do.
Let me point out some stuff here, cuz I'm trying to work my way through the tutorial to root my LG V20 H990DS (International) btw;
ok so the first part here it explains the following;
6. Using dirtysanta's steps: Run "RUNMEFIRST.bat" <-- Do not close.
7. Run "step1.bat" <-- Wait until you can type something again.
Click to expand...
Click to collapse
in my case here I'm using Linux, not Windows to do this, so things are simpler, the RUNMEFIRST.sh executable literally does nothing, when I can see it clearly is suppose to do something, let's take a look at what that files trying to run;
Code:
#!/bin/sh
# runmefirst.sh
#
#
# Created by me2151 on 12/13/16.
#
adb logcat | grep -a dirtysanta
OK, so it's using logcat to see what the phone is doing while piping to grep to watch out for dirtysanta being written to the phone while you have step1.sh running in another terminal instance, when that command completes you're left in ADB Shell of your device. Meanwhile the first shell script doesn't report anything going on, OK that's fine, doesn't matter since it wrote the contents of the required files to the phone, so it's there, as it should and as it's described in the shell script;
Code:
#!/bin/sh
# Step1.sh
#
#
# Created by me2151 on 12/11/16.
#
adb push dirtysanta /storage/emulated/0
adb push aboot.img /storage/emulated/0
adb push dirtycow /data/local/tmp
adb push my-run-as /data/local/tmp
adb shell chmod 0777 /data/local/tmp/*
adb shell /data/local/tmp/dirtycow /system/bin/run-as /data/local/tmp/my-run-as
adb shell /data/local/tmp/dirtycow /system/bin/applypatch /data/local/tmp/dirtycow
adb shell
Now this next part, doesn't work at all, because in the tutorial guide, they said to do chmod 777 permissions on "/storage/emulated/0/*" this doesn't work because operation is not permitted by the file owner and group root, there is no write permission to change permissions of that directory structure.
Code:
chmod: chmod '/storage/emulated/0/Android' to 40777: Operation not permitted
and yes /storage/emulated/0/ is suppose to be your storage userspace of where you save your files and stuff. Your "virtualized" SD Card space, you have normal read-write access there anyways. The next part of that tutorial says to check the id output from the Terminal Emulator app on Android, and check for the response "untrusted_app", that I do get, if you're doing it through ADB Shell you'll get "context=u:r:shell:s0" instead.
Part 12 of the tutorial has misuse or incorrect command line usage for applypatch, it will not simply execute because the command line usage is incorrect like so;
Code:
applypatch /system/bin/atd /storage/emulated/0/dirtysanta
it'll just simply return the following;
Code:
usage: applypatch [-b <bonus-file>] <src-file> <tgt-file> <tgt-sha1> <tgt-size> [<src-sha1>:<patch> ...]
or applypatch -c <file> [<sha1> ...]
or applypatch -s <bytes>
or applypatch -l
Filenames may be of the form
MTD:<partition>:<len_1>:<sha1_1>:<len_2>:<sha1_2>:...
to specify reading from or writing to an MTD partition.
obviously the step2 shell script can't do anything because there is nothing to backup, since it's calling to backup the boot images off the device.
So far I haven't been able to find any comprehensive or updated rooting guide for LG V20 H990DS in particular, nothing new worked on seems to popup anywhere as of yet.
bump this
No help for this at all? Just gonna be another one of those dead-end topics with no answers?