[Q] D802 - Can not acces download mode - G2 Q&A, Help & Troubleshooting

Hi, I need to downgrade to 4.2.2 but I can not acces download mode. It just says "download mode" and nothing else happens so I cant flash the .kdz file. I can boot recovery (TWRP). I cant find a working solution anywhere.
Thanks

Turn off the device, press volume up, plug in the cable at the same time, it will enter download mode.

I tried it many times. It wont. As I said, it just says "download mode" but it wont continue to the "firmware update" part..

What is your current firmware version?4.4.2 ?

Same thing here buddy

Yes. I had 4.2.2 but I tried ported kitkat. Then I flashed the old recovery, tried to restore the backup and nothing is working. So I need to unroot it but I cannot
get to that mode. What a mystery.

Here you need to do is write in detail. I've solved this issue by examining. Your solution is here.LG has closed since way back.
http://forum.xda-developers.com/showthread.php?t=2432476
---------- Post added at 01:00 AM ---------- Previous post was at 12:56 AM ----------
I've given subject solves your problem.

Im not sure if I understand. I was already aware of that guide. Thats why I need to boot "download mode" which I cant. I cant find there the solution. I also cant boot the system.

I just tried to connect flash disk via OTG and the phone does not see it in recovery. In other phone it works. So another way is out. I either need to get the download mode working or push .zip into the phone but I have no idea how since the OTG is not working.

adb push g2_security /sdcard/
adb root
adb push loki_patch /data/local/tmp
adb push loki_flash /data/local/tmp
adb push recovery.img /data/local/tmp
adb shell "dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/data/local/tmp/aboot.img"
adb shell "chmod 644 /data/local/tmp/aboot.img"
adb shell "chmod 755 /data/local/tmp/loki_patch"
adb shell "chmod 755 /data/local/tmp/loki_flash"
adb shell "/data/local/tmp/loki_patch recovery /data/local/tmp/aboot.img /data/local/tmp/recovery.img /data/local/tmp/recovery.lok"
adb shell "/data/local/tmp/loki_flash recovery /data/local/tmp/recovery.lok"
adb shell "rm /sdcard/g2_security"
adb shell "dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/fota-backup.img"
adb shell "dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota"
adb shell sync
adb reboot recovery
i will post the file soon
---------- Post added at 05:27 PM ---------- Previous post was at 05:22 PM ----------
mastercut said:
adb push g2_security /sdcard/
adb root
adb push loki_patch /data/local/tmp
adb push loki_flash /data/local/tmp
adb push recovery.img /data/local/tmp
adb shell "dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/data/local/tmp/aboot.img"
adb shell "chmod 644 /data/local/tmp/aboot.img"
adb shell "chmod 755 /data/local/tmp/loki_patch"
adb shell "chmod 755 /data/local/tmp/loki_flash"
adb shell "/data/local/tmp/loki_patch recovery /data/local/tmp/aboot.img /data/local/tmp/recovery.img /data/local/tmp/recovery.lok"
adb shell "/data/local/tmp/loki_flash recovery /data/local/tmp/recovery.lok"
adb shell "rm /sdcard/g2_security"
adb shell "dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/fota-backup.img"
adb shell "dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota"
adb shell sync
adb reboot recovery
i will post the file soon
Click to expand...
Click to collapse
here: http://rg.to/file/1d38237a286593c5385f2a2108c021c8/fixg2.7z.html

Thank you so much. A will try it immediately.

SOLVED!!! Thanks very much..

Related

adb shell from recovery

Is it possible to obtain adb shell in recovery for DHD ?
I am trying to chmod /data/data/ to fix an error I made.

[Q] Flash_image file?

Does anyone have the flash_image file. My rom is new and doesn't have it.
here you go
to install it is
Code:
adb remount
adb push flash_image /system/bin/flash_image
adb shell chown 755 /system/bin/flash_image

Hungover Root [Roots latest version without flashing anything]

Well, I know it's not particularly important since Zergrush still works but I've found an exploit of file permissions on the latest update.
This root causes things to break until you undo it due to it drops you into emulator mode on your phone. This isn't doing anything bad but a lot of things crash and only a few things really work...like ADB. So this is when you install su / superuser.apk and then you just undo it and reboot. Then you'll have superuser installed on your device. This should theoretically work for all samsung Galaxy S devices (Captivate, Vibrant, Epic 4G, etc) so feel free to try and link to this in those forums.
Story behind the root: I was drunk and bored, a friend had the Captivate, and I decided to look and find this.
Instructions! (The fun part!)
Download the .zip file and run the following commands:
Code:
adb push Hungover.sh /data/local/tmp/Hungover.sh
adb shell chmod 755 /data/local/tmp/Hungover.sh
adb shell ./data/local/tmp/Hungover.sh --recovery
After it reboots into recovery hold vol down+vol up + power and it should reboot. After its back up and running do this:
Code:
adb shell ./data/local/tmp/Hungover.sh --setup
after it reboots again, press Volume+, Volume- and Power at the same time, and reboot the system.
One more time with feeling:
Code:
adb shell ./data/local/tmp/Hungover.sh --root
****
After it reboots, run:
adb remount
adb push SuperUser.apk /system/app/
adb push su /system/xbin/su
adb shell "chmod 04755 /system/xbin/su ; chmod 755 /system/app/SuperUser.apk ; ./data/local/tmp/Hungover.sh --undo"
Then you will have root! Do whatever the hell you want at this point! :)
Download:
https://dl.dropboxusercontent.com/u/15069134/Hungover.zip
Changelog:
[code] Initial release 1.0
Credits:
Me for finding the exploit.
mechapanda for letting me potentially break his phone.
This post is mine for ****s and giggles.
It was fun watching my fun go through qemu, although i can't say i'd feel the same if i wasn't doing this on purpose.
Fails on Karbonn A37
Fails on Karbonn A37 with the following error.
C:\android-sdk\platform-tools>adb push Hungover.sh /data/local/tmp/Hungover.sh
486 KB/s (1993 bytes in 0.004s)
C:\android-sdk\platform-tools>adb shell chmod 755 /data/local/tmp/Hungover.sh
C:\android-sdk\platform-tools>adb shell ./data/local/tmp/Hungover.sh --recovery
/system/bin/sh: ./data/local/tmp/Hungover.sh: No such file or directory
dockers said:
Fails on Karbonn A37 with the following error.
C:\android-sdk\platform-tools>adb push Hungover.sh /data/local/tmp/Hungover.sh
486 KB/s (1993 bytes in 0.004s)
C:\android-sdk\platform-tools>adb shell chmod 755 /data/local/tmp/Hungover.sh
C:\android-sdk\platform-tools>adb shell ./data/local/tmp/Hungover.sh --recovery
/system/bin/sh: ./data/local/tmp/Hungover.sh: No such file or directory
Click to expand...
Click to collapse
're read the OP mate... It's for Galaxy S phones ! So it won't work for your phone
Sent from my SGH-I897 using Tapatalk 2

Manual method of adbd Insecure

This method is similar to Chainfire's adbd Insecure, I tried Chainfire method, adb wireless didn't work for me, so I made my own, I needed to use adb wireless on some devices.
I made this adbd for my BLU Studio 5.0 C Cell phone, but I am sure it will work for other arm devices.
Anyway long story short, you need a rooted device, you push a script and an adbd file to /system/xbin then you add a line to /etc/install-recovery.sh to load the script each boot.
To install download replace_adbd.zip
extract zip place all three files on sdcard, and use rooted file manager to copy them to to their correct places, or use adb.
adb shell
mount -o rw,remount /system
adb push adbd /system/xbin/adbd
adb push adbd-Insecure /system/xbin/adbd-Insecure
adb push install-recovery.sh /system/etc/install-recovery.sh
adb shell
chmod 755 /system/xbin/adbd
chmod 755 /system/xbin/adbd-Insecure
chmod 755 /system/etc/install-recovery.sh
reboot
Or use file manager like ES File Explorer File Manager to copy files from sdcard to correct place and set permission then reboot.
https://www.androidfilehost.com/?fid=24052804347763661
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=1
ro.allow.mock.location=0
persist.mtk.aee.aed=on
ro.debuggable=0
ro.adb.secure=1
persist.sys.usb.config=mtp,adb
persist.service.acm.enable=0
ro.mount.fs=EXT4
ro.persist.partition.support=no
[email protected] STUDIO 5.0 C:/ #
credits
@carliv for CarlivScreenshot
http://forum.xda-developers.com/android/development/tool-carlivscreenshot-screenshots-t3075992
@Chainfire for the ideal of making adbd insecure
http://forum.xda-developers.com/showthread.php?t=1687590
Download link didn't sync correctly, file was corrupt first link, I have now changed the link, this one should now work correctly.
Thanks, I will test on my device and report back. I've always wanted some manual way instead of using the app.
@vampirefo
Is it possible to integrate in your batch the latest version of adbd demon get from adb insecuere 2.0.apk?
Is it possible to check the adbd version? How to?
Is it possible to create a dos batch with all need commands via adb commands? Like
adb shell mount -o rw,remount /system
adb push adbd /system/xbin/adbd
adb push adbd-Insecure /system/xbin/adbd-Insecure
adb shell cp /system/etc/install-recovery.sh /system/etc/install-recovery.sh.old
adb push install-recovery.sh /system/etc/install-recovery.sh
adb shell chmod 755 /system/xbin/adbd
adb shell chmod 755 /system/xbin/adbd-Insecure
adb shell chmod 755 /system/etc/install-recovery.sh
adb reboot
Thanks.
bovirus said:
@vampirefo
Is it possible to integrate in your batch the latest version of adbd demon get from adb insecuere 2.0.apk?
Is it possible to check the adbd version? How to?
Is it possible to create a dos batch with all need commands via adb commands? Like
adb shell mount -o rw,remount /system
adb push adbd /system/xbin/adbd
adb push adbd-Insecure /system/xbin/adbd-Insecure
adb shell cp /system/etc/install-recovery.sh /system/etc/install-recovery.sh.old
adb push install-recovery.sh /system/etc/install-recovery.sh
adb shell chmod 755 /system/xbin/adbd
adb shell chmod 755 /system/xbin/adbd-Insecure
adb shell chmod 755 /system/etc/install-recovery.sh
adb reboot
Thanks.
Click to expand...
Click to collapse
Yes, one can use the adbd binary from adb insecure 2.0.apk.
There isn't any version number to check, we both just build the adbd binary from source, mine was built from CM 12.1 source, not sure about chainfire's.
Chainfire's may have used AOSP source.
Yes one can create a Windows batch file, to execute the adb commands, or create a flashable zip, provided the devices has a custom recovery.
Sent from my Venue 8 3830 using Tapatalk

[6045*] [GUIDE] unlock bootloader

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".)

Categories

Resources