Develop Bugs

Moto 360 5.1.1 (LDZ22O) Root

Root For LDZ22O 5.1.1
If your moto on the latest version you need restore it to LDZ22O with RootJunky SuperTool v5
Connect via DIY USB Cable
Enable adb from developer options
If your bootloader locked unlock it with the supertool (option 2)
Restore to LDZ22O with (option 6) and pair&configure the watch
After pair&configuration you need enable again the adb on the watch from development options​
download latest TWRP 3.0.0 Here​Flash it when on bootloader (command: adb reboot bootloader ) --> from bootloader (command: fastboot flash recovery twrp-3.0.0-0-minnow.img )
you can boot to recovery with (command: fastboot boot twrp-3.0.0-0-minnow.img ) or with adb (command: adb reboot recovery )​
Download Modded Wear-SuperSU-v2.67.zip
Boot to recovery & with cmd (type: adb shell) --> (type: mount /system) then (type: exit ) --> then push Wear-SuperSU-v2.67.zip to sdcard (type: adb push Wear-SuperSU-v2.67.zip /sdcard )
from TWRP enable system partiiton modification --> then flash the Wear-SuperSU-v2.67.zip in sdcard folder (if dont see any red lines durring flash it worked)​
Finally just reboot dont wipe Anything !!IMPORTANT DONT WIPE!! (TWRP Steel Not Working Good with The partitions on moto 360) ​
open adb shell and (type: su ) if you see # you rooted
I'm working on root for the 6.0.1 version, trying get rid of the squashfs read-only /system partiiton & make same one with ext4 I Would like some help from developers ​

Thank you, this worked perfectly for me, and I've been trying to get this thing rooted for months now. I cant wait to see what you do with the 6.0.1 version.

With the latest bootloader, version 954, you can use the button to boot to different modes. One person contacted me about this issue.
How can you use the button when it ask for unlock confirmation? Doesn't it reboot instead to unlocking?

dproldan said:
With the latest bootloader, version 954, you can use the button to boot to different modes. One person contacted me about this issue.
How can you use the button when it ask for unlock confirmation? Doesn't it reboot instead to unlocking?
Click to expand...
Click to collapse
I dont sure about the new bootloader but I think it still let you confim to unlock after cmd command "fastboot oem unlock" but you need to be quick you have only couple of seconds to press the watch button

Shapi300 said:
I dont sure about the new bootloader but I think it still let you confim to unlock after cmd command "fastboot oem unlock" but you need to be quick you have only couple of seconds to press the watch button
Click to expand...
Click to collapse
i'm not sure about it, because i try as fastest i can, but power button only change the boot mode on bootloader version 954. I need to downgrade because the new version make my bluetooth stop working

Lagoone said:
i'm not sure about it, because i try as fastest i can, but power button only change the boot mode on bootloader version 954. I need to downgrade because the new version make my bluetooth stop working
Click to expand...
Click to collapse
Hi, Were you able to downgrade ?

alidsd said:
Hi, Were you able to downgrade ?
Click to expand...
Click to collapse
nope, still waiting for help

NEED HELP !!! OPPO FIND 7 stuck on boot with logo only

Tried fixing my oppo find 7
Did all those Fastboot wipe .
Fastboot flash recovery and flash LOGO and stuffs
but im still stuck on logo ... WHUT

kevzwenhao said:
Tried fixing my oppo find 7
Did all those Fastboot wipe .
Fastboot flash recovery and flash LOGO and stuffs
but im still stuck on logo ... WHUT
Click to expand...
Click to collapse
Did you unlock bootloader?
1. Connect the device to the computer through USB.
2. From a terminal on a computer, type the following to boot the device into fastboot mode (or restart pressing power+vol up):
Code:
adb reboot bootloader
3. Once the device is in fastboot mode, verify your PC sees the device by typing:
Code:
fastboot devices
4. From the same terminal, type the following command to unlock the bootloader:
Code:
fastboot oem unlock
If the device doesn't automatically reboot, reboot it from the menu. It should now be unlocked.
5. Then you can flash the recovery what you want. In fastboot mode, type in terminal:
Code:
fastboot devices
6. And flash the recovery. Type:
Code:
fastboot flash recovery your_recovery_image.img
Good luck

roi_xordo said:
Did you unlock bootloader?
1. Connect the device to the computer through USB.
2. From a terminal on a computer, type the following to boot the device into fastboot mode (or restart pressing power+vol up):
Code:
adb reboot bootloader
3. Once the device is in fastboot mode, verify your PC sees the device by typing:
Code:
fastboot devices
4. From the same terminal, type the following command to unlock the bootloader:
Code:
fastboot oem unlock
If the device doesn't automatically reboot, reboot it from the menu. It should now be unlocked.
5. Then you can flash the recovery what you want. In fastboot mode, type in terminal:
Code:
fastboot devices
6. And flash the recovery. Type:
Code:
fastboot flash recovery your_recovery_image.img
Good luck
Click to expand...
Click to collapse
Hi, is it wrong to wipe the system partition before flashing a custom rom? Coming from stock ColorOS, I've wiped all dalvik cache, cache, system, and data, then flash a custom rom but it ended up getting endless bootanimation unable to boot into the custom rom.
I did unlock the bootloader with the adb code, flashing a temporary recovery was a success but endless bootanimation happened after flashing a custom rom. The custom rom was successfully installed according to TWRP's log.
Pls advice, thanks in advanced
P.s: I was referring to my friend's device X9076

Hi, i tried in the past some roms than not works, phone stuck in boot animation. The roms wich works for me and my x9076 with r63419 are:
Omnirom (6 or 5) THE BEST
Project Spectrum
Cyanogen 13 (modified version for new panel: http://community.oppo.com/en/forum.php?mod=viewthread&tid=44907&extra=)
Miui
If you install CM13, you need to flash unified partition script for CM13 (you can find it in the same post from the forum Oppo Community)
For the other roms i dont need to flash anything else than rom and gapps.
Now i give a chance to CM13, but i think that i will get back to Omni if developers dont fix the mobile radio issue.
Cheers

Can anyone guide me please, 1st time i bought MTK phone Oppo F7, its update automatically but suddenly dead like stuck on logo and restarting again and again, i didnt ever flash MTK phone, neither i have any android tool like MRT dongle or any other flash USB or Box... Kindly guide me step by step how to flash with which tool only USB cable and PC... Thanks in advance

K5, A6020l36, Lineage OS 14.1 unrooted, Can't access TWRP, Help!

*Noob*
Lenovo K5, A6020l36, running Lineage OS 14.1 unrooted, can no longer access TWRP boot loader, how do I root the phone and access TWRP without being able to access TWRP? Thanks in advance.
BTW... ADB sees the device via my Mac for what that's worth.

[DEVICE IN BOOTLOADER] [ADB VIA PROMPT IN PC]
Code:
fastboot boot twrp.img
Inside TWRP, go to Install > Image File > twrp.img
DONE.
(twrp.img has to be in your PC, from where you are running ADB, and in your device too.)
You could also:
Code:
fastboot flash recovery twrp.img
and try to see if your recovery is fixed.

lucasdeeiroz said:
[DEVICE IN BOOTLOADER] [ADB VIA PROMPT IN PC]
Code:
fastboot boot twrp.img
Inside TWRP, go to Install > Image File > twrp.img
DONE.
(twrp.img has to be in your PC, from where you are running ADB, and in your device too.)
You could also:
Code:
fastboot flash recovery twrp.img
and try to see if your recovery is fixed.
Click to expand...
Click to collapse
Muito obrigado
When I try the commands it hangs on "Waiting for Device" even though it sees the device....
any more ideas you beautiful people?

theconkeyboy said:
Muito obrigado
When I try the commands it hangs on "Waiting for Device" even though it sees the device....
any more ideas you beautiful people?
Click to expand...
Click to collapse
Reinstall your adb/fastboot and device drivers. If you can run it in a Linux PC, it would be better. This is a common issue.
(Oh, and don't forget to enable USB debugging in Developer settings on your device, that's super important).

theconkeyboy said:
*Noob*
Lenovo K5, A6020l36, running Lineage OS 14.1 unrooted, can no longer access TWRP boot loader, how do I root the phone and access TWRP without being able to access TWRP? Thanks in advance.
BTW... ADB sees the device via my Mac for what that's worth.
Click to expand...
Click to collapse
I would suggest :
Shutdown your device
Reboot to fastboot mode via "Power" + "Volume -" for a few seconds until you reboot and see a Lenovo blank screen with "Power key long press can reboot the phone" at the bottom
Plug your device to your computer
Test fastboot via "fastboot devices" on your computer (you should see a number)
Flash TWRP via "fastboot flash recovery <the TWRP file on your computer>"
Reboot to TWRP by holding "Power" + "Volume +" and select "recovery" on the menu that will appear
Hope it will work for you

Root Armani in 2018

Method 1:-
Download Custom Recovery for armani in your pc and rename it to recovery.img
and download root zip and paste it in your sdcard
Download 15 seconds adb & fast drivers and follow the instructions....
In pc type the following commands by opening cmd from shift+right click and open command prompt here after connecting the device to pc
Code:
adb devices
after successful install of drivers you will see the device listed in that
Code:
adb reboot bootloader
After rebooting into fastboot mode type the following commands
Code:
fastboot flash recovery recovery.img
after successful flashing of recovery then type this
Code:
fastboot reboot recovery
Flash SuperSU/Koush superuser in your TWRP/CWM/Philz recovery
Method 2:- Download Kingo ROOT and root
Method 3:- Download Kingo ROOT pc version in your pc and load it and connect your device to pc and root....
Method 4:- Download KingRoot and click to root....if it fails in first attempt, try atleast 5 times...

Yes these are indeed the best methods to root this phone.
Also, note that Magisk will not work for the stock MIUI because the phone has Android 4.4 and Magisk probably requires 5.0+. So, Magisk should be used for newer custom ROMs.
HemanthJabalpuri said:
I want to root my MIUI 9 armani in 2018.....
I don't have PC
Click to expand...
Click to collapse
Also, like you had said earlier, if you don't have a PC due to some reason, you can use another phone or tablet for that purpose (to flash the custom recovery). I've read somewhere that most Android devices having 5.0 and below came preloaded with adb fastboot binaries (for newer Android phones, you can easily obtain the binaries online and add them into the /system/bin folder if it is rooted) and hence you can connect your Redmi to this other device using an OTG cable and use the shell (any terminal app) to issue the commands. The only important thing to be considered in this approach is that the other (host) device should have a big enough battery to be able to provide sufficient current to the Redmi phone such that it should not get disconnected during the process.
This method is usually ignored by people, but it really works.

Reserved

Reserved

Code:
$ fastboot reboot recovery
fastboot: usage: unknown reboot target recovery
Cannot issue the last command.
When I flash TWRP and reboot nothing happens. Same Mi Recovery is present.
I am on MIUI 9. Not rooted. I am trying to get a custom recovery but I fail. Please help.

blazzer12 said:
Code:
$ fastboot reboot recovery
fastboot: usage: unknown reboot target recovery
Click to expand...
Click to collapse
Are you sure recovery was flashed properly?
Try this while in fastboot mode :-
Code:
fastboot devices
Make sure that your device is listed properly.
Try this
Code:
fastboot erase recovery
fastboot flash recovery <path to recovery img>
Then reboot using
Code:
fastboot reboot recovery
If still doesn't work out, try to directly boot into recovery image
Code:
fastboot boot <path to recovery img>
If still doesn't work out, then there might be a problem with the fastboot binary on the PC, try to reinstall the latest version of it on the PC and try again.
---------- Post added at 22:03 ---------- Previous post was at 21:55 ----------
blazzer12 said:
When I flash TWRP and reboot nothing happens. Same Mi Recovery is present.
Click to expand...
Click to collapse
If the issue is specific to TWRP Recovery, try to flash other recoveries. For example, older version of TWRP or maybe try Philz Touch recovery as well.

Yes, the fastboot devices is being listed. Still #2 didn't work. But #3 worked perfectly.
So for me flashing recovery didn't work. I had to temporarily boot into the recovery and then again flash the recovery from there.
Thank you for the help. :good:

Now we can root with Magisk too...
https://forum.xda-developers.com/ap...v7-universal-systemless-t3473445/post78829088
Note:- Magisk v22.1 is the last version to support Android 4.4.2

Oppo A83 [CPH1729] TWRP RECOVERY

⚠Warning: This is not official TWRP, use it at your own risk!!!
Data will be erased. Back up if neccessary
This device is kind of weird so to flash twrp you need these things:
1. Prepare materials​
Install driver so as to have access to preloader (Just install automatically and no need to do anything in device manager)
This software to access to preloader -> fastboot (fastboot is somehow not available via adb methods) Enter fastboot
This tool for flashing
2. Unlock bootloader (need testpoint, python, git (optional) - you can search on google)​
Use this tool - go to this section. Follow guides to unlock bootloader (remember to use testpoint not hardware buttons)
3. Enter fastboot mode​
Use latest MTK META Ultility tool
Select Reboot Fastboot Mode in BRom section
Hold volume down button. While holding connect it to your computer
*Now your phone is in fastboot mode​4. Flash​
Open platform-tools folder in Downloads folder
Shift + Right click then "open command window here"
Input these commands into cmd
fastboot flash boot drag twrp file to cmd
fastboot flash recovery drag twrp file to cmd.
fastboot reboot. Swipe to allow modification in twrp (to make sure that stockboot wont replace twrp). After that reboot to recovery to make it installed on your device permanently.
Now your recovery is ready to flash file you can push stock image file to your root folder using adb command: "adb push. Drag the stock image file. /" (Because Decryption right now doesnt work on my device yet)
Enjoy
*Sounds crazy but it is required to make sure twrp is installed correctly​*If successful, when you power on, you will get a red section on top of your device. If you want to recover to stock recovery, flash the recovery.img below.​*Also, if you want to make your own twrp, you can try recovery.img below.​
Also thanks SebaUbuntu and Mofadal El-Tayeb (مُفَضَّل) for awesome apps
​
​​
​

Here is the PBRB version for this device

Hey I'm stuck in the third step.can you please help me?

Sorry for late reply. What problems do you have?

Is this the stock boot image you provided?

SAMIUL ISLAM 0 said:
Is this the stock boot image you provided?
Click to expand...
Click to collapse
Yes it is. I took it from OTA update

Hey friends
I want to upgrade my oppo a 83 fone to a costum rom to upgrade my androide to android 8 or higher

mahmoud2503 said:
Hey friends
I want to upgrade my oppo a 83 fone to a costum rom to upgrade my androide to android 8 or higher
Click to expand...
Click to collapse
Unfortunately, I have no custom roms available for this phone (