[6045*] [GUIDE] unlock bootloader - Onetouch Idol 3 General
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".)
Related
is this the right way to root?
adb devices adb push asroot2 /data/local adb shell chmood 0755 /data/local/asroot2 adb shell $ /data/local/asroot /system/bin/sh $ mount -o remount,rw -t yaffs2 /dev/block/mtdblock /system (or is it -zero) $ cd /system/bin $cat sh > su $ chmod 4775 su (or 4755?) $exit adb push recovery-RA-heroc-v1.2.3.img adb shell $ su # flash_image recovery recovery-RA-heroc-v1.2.3.img then boot to recovery by typing: reboot recovery while pressing volume down and the when it boots to screen press home? is this how to do it? help please
Code: adb devices adb push asroot2 /data/local adb push recovery-RA-heroc-v1.2.3.img /data/local adb shell Code: chmod 0755 /data/local/asroot2 /data/local/asroot2 /system/bin/sh mount -o remount,rw -t yaffs2 /dev/block/mtdblock /system cd /system/bin cat sh > su chmod 4755 su flash_image recovery /data/local/recovery-RA-heroc-v1.2.3.img reboot recovery corrected some stuff for ya make sure asroot2 and recovery-RA-heroc-v1.2.3.img is in same directory as adb.exe and that's good to go UPDATE: no longer requires a sd card to root + recovery image + made copy/pasteable
fullgrown said: adb devices adb push asroot2 /data/local adb shell chmood 0755 /data/local/asroot2 adb shell $ /data/local/asroot /system/bin/sh $ mount -o remount,rw -t yaffs2 /dev/block/mtdblock /system (or is it -zero) $ cd /system/bin $cat sh > su $ chmod 4775 su (or 4755?) $exit adb push recovery-RA-heroc-v1.2.3.img adb shell $ su # flash_image recovery recovery-RA-heroc-v1.2.3.img then boot to recovery by typing: reboot recovery while pressing volume down and the when it boots to screen press home? is this how to do it? help please Click to expand... Click to collapse Up to the exit is the rooting part, yes. After that you can shell in and type "su" and have root access. The rest of it is installing a custom recovery image.
thank you!!! now i'm rooted!!!
ADB Backup
Hi All, I've backed up my device using ADB with the following commands: mkdir backup cd backup adb shell su -c "dd if=/dev/block/bml1 of=/sdcard/boot.bin bs=4096" adb shell su -c "dd if=/dev/block/bml2 of=/sdcard/pit.pit bs=4096" adb shell su -c "dd if=/dev/block/stl3 of=/sdcard/efs.rfs bs=4096" adb shell su -c "dd if=/dev/block/bml4 of=/sdcard/Sbl.bin bs=4096" adb shell su -c "dd if=/dev/block/stl6 of=/sdcard/param.lfs bs=4096" adb shell su -c "dd if=/dev/block/bml7 of=/sdcard/zImage bs=4096" adb shell su -c "dd if=/dev/block/stl9 of=/sdcard/factoryfs.rfs bs=4096" adb shell su -c "dd if=/dev/block/stl10 of=/sdcard/dbdata.rfs bs=4096" adb shell su -c "dd if=/dev/block/stl11 of=/sdcard/cache.rfs bs=4096" adb shell su -c "dd if=/dev/block/bml12 of=/sdcard/modem.bin bs=4096" adb shell su -c "tar -czvf /sdcard/data.tar.gz /data" adb pull /sdcard/param.lfs . adb pull /sdcard/zImage . adb pull /sdcard/factoryfs.rfs . adb pull /sdcard/dbdata.rfs . adb pull /sdcard/cache.rfs . adb pull /sdcard/modem.bin . adb pull /sdcard/efs.rfs . adb pull /sdcard/boot.bin . adb pull /sdcard/Sbl.bin . adb pull /sdcard/pit.pit . adb pull /sdcard/data.tar.gz . And I would like to give the backup to some of my friends, but I would like to verify there are no "personal data" on the backup (I did a factory reset before the backup and there was no contacts \ data that was mine), I don't know what type of data should I delete from the files, (like IMEI and serial data..). Please help me find out what shouldn't be on the backup, Thanks, AYahoo.
No one? Sent from my GT-I9000 using XDA App
[Q] Rooting U8800 with Linux, is there a recommended and safe way?
Hi all, I want to root my U8800 under a Linux-OS. Is there a recommended and safe way to do that? Currently my phone ist flashed with V100R001C00B528G001. I know these threads, but I am unsure if the described methods in these threads are act up on my Linux-System. http://forum.xda-developers.com/showthread.php?t=1420728 http://forum.xda-developers.com/showthread.php?t=1423422 Many thanks in advance, Ponder
So, after some days of reading helpfull threads in this forum I found a way to root my u8800 under my favorite OS archlinux To get access to the smartphone it's important to install some packages previously:
Install some packages from the ArchLinux reposities:
pacman -S abs
pacman -S base-devel
pacman -S jdk7-openjdk
pacman -S openal
pacman -S swt
pacman -S libstdc++5
pacman -S libmtp
Download some files from the AUR "ArchLinux User-Community Repository":
(Don't do this as root, do this as normal user and save the packages in ~/android)
android-sdk
android-sdk-platform-tools
android-udev
Create packages (via makepkg) from the three files above and install them via pacman.
https://wiki.archlinux.org/index.php/AUR
After installing the three packages put your user to the group adbusers
Code:
gpasswd -a <your user> adbusers
Figure out the device IDs from u8800:
lsusb
Code:
Bus 001 Device 002: ID 12d1:1037 Huawei Technologies Co., Ltd. Ideos
Adding udev rules for the u8800 device:
There is a template file called "51-android.rules" in the folder "android-udev". Search for the String "Huawei" and replace [VENDOR ID] and [PRODUCT ID] with yours. Copy these rules into /etc/udev/rules.d/51-android.rules:
Code:
# Huawei
SUBSYSTEM=="usb", ATTR{idVendor}=="12d1", MODE="0666", GROUP="adbusers"
SUBSYSTEM=="usb", ATTR{idVendor}=="12d1", ATTR{idProduct}=="1037", SYMLINK+="android_adb"
SUBSYSTEM=="usb", ATTR{idVendor}=="12d1", ATTR{idProduct}=="1037", SYMLINK+="android_fastboot"
Then, to reload your new udev rules, execute:
Code:
# udevadm control --reload-rules
Does It Work? After you have setup the udev rules, unplug your device and replug it. After running:
Code:
$ adb devices
you should see something like:
Code:
List of devices attached
404D8E65F146 device
Download B528_ROOT.rar. I found it in this thread (#7):
http://forum.xda-developers.com/showthread.php?t=1533922
Prepare your phone for rooting:
1) Dial: *#*#2846579#*#*
2) Go to projectmenu > background settings > log settings > log switch > set Log on
3) Reboot Phone
4) Switch USB Debugging ON
5) Download B528_ROOT.rar (not SuperOneClick v2.3.3).
6) Plug your U8800 into your computer but DO NOT mount SD Card.
http://forum.xda-developers.com/showthread.php?t=1420728
7) Extract B528_ROOT.rar and open the file "B528_root.bat" with an editor.
8) Open a terminal as normal user and change into the directory with the file "B528_root.bat".
9) Copy the following commands step by step into the terminal.
Code:
adb wait-for-device
adb reboot-bootloader
fastboot boot boot.img
fastboot reboot
adb wait-for-device
at this point it seems the procedure get stuck. Try the next commands... :-)
adb remount -t yaffs2 /dev/block/mtdblock3 /system
adb push busybox /data/local/tmp/.
adb shell "chmod 755 /data/local/tmp/busybox"
adb shell "/data/local/tmp/busybox mount -o remount,rw /system"
adb push makespace /data/local/tmp/.
adb shell "chmod 777 /data/local/tmp/makespace"
adb shell "./data/local/tmp/makespace"
adb shell "dd if=/data/local/tmp/busybox of=/system/xbin/busybox"
adb shell "chown root.shell /system/xbin/busybox"
adb shell "chmod 04755 /system/xbin/busybox"
adb shell "/system/xbin/busybox --install -s /system/xbin"
adb shell "rm -r /data/local/tmp/busybox"
adb push su /system/bin/su
adb shell "chown root.shell /system/bin/su"
adb shell "chmod 06755 /system/bin/su"
adb shell "rm /system/xbin/su"
adb shell "ln -s /system/bin/su /system/xbin/su"
adb push Superuser.apk /system/app/.
adb shell "cd /data/local/tmp/; rm *"
adb reboot
Now, your smartphone should be rooted.
Some helpfull threads:
http://forum.xda-developers.com/showthread.php?t=1321582
http://forum.xda-developers.com/showthread.php?p=20869699
http://forum.xda-developers.com/showthread.php?p=18615502
http://forum.xda-developers.com/showthread.php?t=1423422
https://wiki.archlinux.org/index.php/Android
adb command as a single line? (with Ubuntu touch on Nexus 4)
How can I call adb command as a single line from cmd.exe? Here is what I am executing when I run it regularly. Code: adb shell ubuntu_chroot shell cd /home/phablet/test nohup ./test2.sh I am able to run this: Code: adb shell "ubuntu_chroot shell" Can I make all that I am trying to do (start execution of test2.sh script from ubuntu_chroot shell) with one single command?
kdar1987 said: How can I call adb command as a single line from cmd.exe? Here is what I am executing when I run it regularly. Code: adb shell ubuntu_chroot shell cd /home/phablet/test nohup ./test2.sh I am able to run this: Code: adb shell "ubuntu_chroot shell" Can I make all that I am trying to do (start execution of test2.sh script from ubuntu_chroot shell) with one single command? Click to expand... Click to collapse Solved. I called adb shell < scriptfile.txt, whith scriptfile.txt having Code: ubuntu_chroot shell cd /home/phablet/test nohup ./test2.sh
Fire TV Stick 2/4K Launcher replacement ROOT
Store and Voice input will be lost. 1, Install Launcher of your choice. ( adb install 123launcher.apk ) 2, adb shell su -c "pm disable-user --user 0 com.amazon.tv.launcher" wait 5 seconds 3, adb shell su -c "pm disable-user --user 0 com.amazon.firehomestarter" wait 5 seconds 5, adb shell reboot 6, adb install com.markus.firetools-1.2.apk (to access Settings "allow Root" ) ######### Disable OTA Updates: adb shell "su -c pm disable com.amazon.tv.forcedotaupdater.v2" adb shell "su -c pm disable com.amazon.device.software.ota" adb shell "su -c pm disable com.amazon.device.software.ota.override" adb shell "pm clear com.amazon.device.software.ota" ######## to restore the Amazon Launcher adb shell su -c "pm enable com.amazon.firehomestarter" wait 4 seconds adb shell su -c "pm enable com.amazon.tv.launcher"
Update
New Settings APK in 1st Post
0815hoffi said: After Tests i found out , you can replace amazon launcher without other Tools. Please test if you want. 1 install launcher of your choice. Boot twrp. adb shell mount -o rw /system Backup Apps adb shell "cp /system/priv-app/com.amazon.firehomestarter/com.amazon.firehomestarter.apk /sdcard/" adb shell "cp /system/priv-app/com.amazon.tv.launcher/com.amazon.tv.launcher.apk /sdcard/" Delete amazon launcher. adb shell "rm -r /data/app/com.amazon.tv.launcher-1/" adb shell "rm -r /data/app/com.amazon.firehomestarter/" adb shell "rm -r /data/data/com.amazon.tv.launcher/" adb shell "rm -r /data/data/com.amazon.firehomestarter/" adb shell "rm /system/priv-app/com.amazon.firehomestarter/com.amazon.firehomestarter.apk" adb shell "rm /system/priv-app/com.amazon.tv.launcher/com.amazon.tv.launcher.apk" adb push NewSettingsRoot.apk /sdcard/NewSettingsRoot.apk adb shell "mkdir /system/priv-app/NewSettingsRoot/" adb shell "chmod 0775 /system/priv-app/NewSettingsRoot/" adb shell "chown root:root /system/priv-app/NewSettingsRoot/" adb shell "cp /sdcard/NewSettingsRoot.apk /system/priv-app/NewSettingsRoot/NewSettingsRoot.apk" adb shell "chmod 644 /system/priv-app/NewSettingsRoot/NewSettingsRoot.apk" adb shell reboot Workaround : The Settings app. Requires root Click to expand... Click to collapse Works great! I'm really glad to see the last of the Amazon launcher screen. Thanks for your hard work.
TWRP Flashable Zip 1st Post. Install launcher of your choice. Then flash the zip.
Modified Leanbacklauncher with FireTvSettings. Needs Root for Settings.
Will this work on the 2nd Gen sticks?
Yes it should.
Would it not be easier to just freeze pm disable com.amazon.firehomestarter and com.amazon.tv.launcher instead of deleting it? I'm using leanback launcher 1.18. I found it here on xda but I don't have the link anymore.
mrxtc89117 said: Would it not be easier to just freeze pm disable com.amazon.firehomestarter and com.amazon.tv.launcher instead of deleting it? I'm using leanback launcher 1.18. I found it here on xda but I don't have the link anymore. Click to expand... Click to collapse You can try it. I haven't tested Deleted some more on my Stick. See delete.txt MarkusOnFire.apk is based on leanback launcher 1.19 . Org. Leanback Launcher you can find here. https://github.com/tsynik/LeanbackLauncher/releases/
Next step is to try using the stick without an amazon account and Initial Setup maybe
This is what worked for me on a fire stick 2nd gen NewSettingsRoot.apk adb push NewSettingsRoot.apk /sdcard/NewSettingsRoot.apk adb shell su -c mount -o remount,rw /system adb shell su -c mkdir /system/priv-app/NewSettingsRoot/ adb shell su -c chmod 0775 /system/priv-app/NewSettingsRoot/ adb shell su -c chown root:root /system/priv-app/NewSettingsRoot/ adb shell su -c cp /sdcard/NewSettingsRoot.apk /system/priv-app/NewSettingsRoot/NewSettingsRoot.apk adb shell su -c chmod 644 /system/priv-app/NewSettingsRoot/NewSettingsRoot.apk adb shell su -c mount -o remount,ro /system adb shell su -c rm /sdcard/NewSettingsRoot.apk adb shell pm grant com.markus.firetools android.permission.WRITE_SECURE_SETTINGS adb shell pm grant com.amazon.tv.leanbacklauncher android.permission.WRITE_SECURE_SETTINGS
On a rooted FireTV2 (sloane) the Settings App doesn't work If I select anything it goes back to the Home Screen! I Flashed the zip with TWRP and also tried that Method which is discribed above, any Idea whats wrong?
Try this commands in adb shell. su -c am start -a com.amazon.device.settings.action.APPLICATIONS -n com.amazon.tv.settings.v2/.tv.applications.ApplicationsActivity su -c am start -a com.amazon.device.settings.action.APPS -n com.amazon.tv.settings/.tv.BuellerApplicationsSettingsActivity su -c am start -a com.amazon.device.settings.action.MANAGE_APPLICATIONS -n com.amazon.tv.settings/com.amazon.tv.settings.tv.applications.ApplicationsActivity su -c am start -a com.amazon.device.settings.action.MANAGE_APPLICATIONS -n com.amazon.tv.settings/com.amazon.tv.settings.tv.applications.ApplicationsActivity Is one of them working? If yes, i Think that i must make a New settings apk for firetv2. This one is for 4k.
0815hoffi said:
Try this commands in adb shell.
su -c am start -a com.amazon.device.settings.action.APPLICATIONS -n com.amazon.tv.settings.v2/.tv.applications.ApplicationsActivity
su -c am start -a com.amazon.device.settings.action.APPS -n com.amazon.tv.settings/.tv.BuellerApplicationsSettingsActivity
su -c am start -a com.amazon.device.settings.action.MANAGE_APPLICATIONS -n com.amazon.tv.settings/com.amazon.tv.settings.tv.applications.ApplicationsActivity
su -c am start -a com.amazon.device.settings.action.MANAGE_APPLICATIONS -n com.amazon.tv.settings/com.amazon.tv.settings.tv.applications.ApplicationsActivity
Is one of them working?
If yes, i Think that i must make a New settings apk for firetv2.
This one is for 4k.
Click to expand...
Click to collapse
The first one works for me.
[[email protected] firestick]$ adb shell
-n com.amazon.tv.settings.v2/.tv.applications.ApplicationsActivity <
Starting: Intent { act=com.amazon.device.settings.action.APPLICATIONS cmp=com.amazon.tv.settings.v2/.tv.applications.ApplicationsActivity }
amazon.tv.settings/.tv.BuellerApplicationsSettingsActivity <
Starting: Intent { act=com.amazon.device.settings.action.APPS cmp=com.amazon.tv.settings/.tv.BuellerApplicationsSettingsActivity }
Error type 3
Error: Activity class {com.amazon.tv.settings/com.amazon.tv.settings.tv.BuellerApplicationsSettingsActivity} does not exist.
mantis:/ $
.settings/com.amazon.tv.settings.tv.applications.Application sActivity <
Starting: Intent { act=com.amazon.device.settings.action.MANAGE_APPLICATI pkg=ONS }
Error: Activity not started, unable to resolve Intent { act=com.amazon.device.settings.action.MANAGE_APPLICATI flg=0x10000000 pkg=ONS }
.settings/com.amazon.tv.settings.tv.applications.Application sActivity <
Starting: Intent { act=com.amazon.device.settings.action.MANAGE_APPLICATI pkg=ONS }
Error: Activity not started, unable to resolve Intent { act=com.amazon.device.settings.action.MANAGE_APPLICATI flg=0x10000000 pkg=ONS }
mantis:/ $
---------- Post added at 09:27 PM ---------- Previous post was at 09:20 PM ----------
0815hoffi said:
Try this commands in adb shell.
su -c am start -a com.amazon.device.settings.action.APPLICATIONS -n com.amazon.tv.settings.v2/.tv.applications.ApplicationsActivity
su -c am start -a com.amazon.device.settings.action.APPS -n com.amazon.tv.settings/.tv.BuellerApplicationsSettingsActivity
su -c am start -a com.amazon.device.settings.action.MANAGE_APPLICATIONS -n com.amazon.tv.settings/com.amazon.tv.settings.tv.applications.ApplicationsActivity
su -c am start -a com.amazon.device.settings.action.MANAGE_APPLICATIONS -n com.amazon.tv.settings/com.amazon.tv.settings.tv.applications.ApplicationsActivity
Is one of them working?
If yes, i Think that i must make a New settings apk for firetv2.
This one is for 4k.
Click to expand...
Click to collapse
Just noticed a couple of extraneous spaces in #3 & #4. Removing the spaces results in a different error.
mantis:/ $
.settings/com.amazon.tv.settings.tv.applications.Application sActivity <
Starting: Intent { act=com.amazon.device.settings.action.MANAGE_APPLICATI pkg=ONS }
Error: Activity not started, unable to resolve Intent { act=com.amazon.device.settings.action.MANAGE_APPLICATI flg=0x10000000 pkg=ONS }
MANAGE_APPLICATIONS -n com.amazon.tv.settings/com.amazon.tv.settings.tv.applic*
Starting: Intent { act=com.amazon.device.settings.action.MANAGE_APPLICATIONS cmp=com.amazon.tv.settings/.tv.applications.ApplicationsActivity }
Error type 3
Error: Activity class {com.amazon.tv.settings/com.amazon.tv.settings.tv.applications.ApplicationsActivity} does not exist.
.settings.action.MANAGE_APPLICATIONS -n com.amazon.tv.settings/com.amazon.tv.s*
Starting: Intent { act=com.amazon.device.settings.action.MANAGE_APPLICATIONS cmp=com.amazon.tv.settings/.tv.applications.ApplicationsActivity }
Error type 3
Error: Activity class {com.amazon.tv.settings/com.amazon.tv.settings.tv.applications.ApplicationsActivity} does not exist.
mantis:/ $
Yes the 1st one is for mantis an Stick2 an should work in this devices. This command style is used for my app. I not have a FireTV2 to test what is the correct am start command for this device So i need any one Who can test it.
Edit: Sry hatte das eben nur überflogen! Also bei jedem der Befehle kommt der gleiche Fehler raus, Nr 3 und 4 sind gleich, hab dann nochmal einen Versuch gemacht ohne die 2 Leerzeichen aus 3/4, aber wieder der selbe Fehler Code: [email protected]:~/Downloads$ adb connect 192.168.2.51 already connected to 192.168.2.51:5555 [email protected]:~/Downloads$ adb shell su -c am start -a com.amazon.device.settings.action.APPLICATIONS -n com.amazon.tv.settings.v2/.tv.applications.ApplicationsActivity Error type 2 android.util.AndroidException: Can't connect to activity manager; is the system running? at com.android.commands.am.Am.onRun(Am.java:299) at com.android.internal.os.BaseCommand.run(BaseCommand.java:47) at com.android.commands.am.Am.main(Am.java:97) at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method) at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:256) [email protected]:~/Downloads$ adb shell su -c am start -a com.amazon.device.settings.action.APPS -n com.amazon.tv.settings/.tv.BuellerApplicationsSettingsActivity Error type 2 android.util.AndroidException: Can't connect to activity manager; is the system running? at com.android.commands.am.Am.onRun(Am.java:299) at com.android.internal.os.BaseCommand.run(BaseCommand.java:47) at com.android.commands.am.Am.main(Am.java:97) at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method) at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:256) [email protected]:~/Downloads$ adb shell su -c am start -a com.amazon.device.settings.action.MANAGE_APPLICATI ONS -n com.amazon.tv.settings/com.amazon.tv.settings.tv.applications.Application sActivity Error type 2 android.util.AndroidException: Can't connect to activity manager; is the system running? at com.android.commands.am.Am.onRun(Am.java:299) at com.android.internal.os.BaseCommand.run(BaseCommand.java:47) at com.android.commands.am.Am.main(Am.java:97) at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method) at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:256) [email protected]:~/Downloads$ adb shell su -c am start -a com.amazon.device.settings.action.MANAGE_APPLICATIONS -n com.amazon.tv.settings/com.amazon.tv.settings.tv.applications.ApplicationsActivity Error type 2 android.util.AndroidException: Can't connect to activity manager; is the system running? at com.android.commands.am.Am.onRun(Am.java:299) at com.android.internal.os.BaseCommand.run(BaseCommand.java:47) at com.android.commands.am.Am.main(Am.java:97) at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method) at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:256) So with each of the commands the same error comes out, No. 3 and 4 are the same, then I tried again without the 2 spaces from 3/4, but again the same error
0815hoffi said: You can try it. I haven't tested Deleted some more on my Stick. See delete.txt MarkusOnFire.apk is based on leanback launcher 1.19 . Click to expand... Click to collapse @0815hoffi I would be interested in how and from where you execute start the delete.txt file, thank you
Akki67 said: @0815hoffi I would be interested in how and from where you execute start the delete.txt file, thank you Click to expand... Click to collapse On your Windows PC folder where the adb.exe is located. Download cleanup.cmd.txt, rename to cleanup.cmd and run.
Hi thank you first. Unfortunately, nothing is deleted for me, see log. Code: C:\adbLink>adb devices List of devices attached G070VM1600230K52 device C:\adbLink>cleanup.cmd Wait for TWRP Drücken Sie eine beliebige Taste . . . Debloating Amazon Apps... rm: can't remove '/system/priv-app/android.amazon.perm': No such file or directory rm: can't remove '/system/priv-app/com.amazon.android.marketplace': No such file or directory rm: can't remove '/system/priv-app/com.amazon.awvflingreceiver': No such file or directory USB cable from the PC goes directly to the FireTV4K, without a USB hub. Or do I have to enter or install something in TWRP?