Q&A for [Root] Root and TWRP for R
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [Root] Root and TWRP for R. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
I couldn't get TWRP to stick even with a custom kernel. When I executed a fastboot command to boot from the TWRP image it said that the image is corrupted and not bootable. Tried redownloading ~4 times all with the same error. On latest OTA update for LGGWR.
Hi,
when launch SuperSU appear this error:
"about"
application supersu crashed abnormally
Click to expand...
Click to collapse
Ok this might sound like a stupid question but I just had some problems installing TWRP + rooting and now that everything seems to be working fine I want to check that root is actually working so... is there any way to do that? How can I check that su access is available?.
good question.
I have another problem: I unlocked the bootloader, flashed TWRP but then I can't push Supersu to the watch in the bootloader mode, because the device can't be found (adb devices).
When I try to check if TWRP is on the watch and I say "adb reboot recovery" I only see the original recovery although the flashing of TWRP ran smoothly.
Can anyone help me?
Thanks in advance!!
---------- Post added at 09:57 AM ---------- Previous post was at 09:18 AM ----------
OK, sorry - It's me again.
I made the mistake that I didn't put the twrp.img into the fastboot folder
although adb always replied that the flashing was successfull.
Anyway - twrp is now installed but I had the same issue as mentioned above: Supersu can't be pushed because there is no device to be found. Then I went into twrp which prompted me that the device doesn't seem to be rooted and I affirmed to install supersu. Now when I am back into the normal mode of the watch supersu pops up but can't be installed because it crashes everytime.
---------- Post added at 10:26 AM ---------- Previous post was at 09:57 AM ----------
I flashed Supersu 2.46 by the way
Hey Kreiger1981,
I had also a lot of problems with rooting the watch., but finally it's working now using the steps described in this thread and WinDroid.
But I had to disconnect the usb wire multiple times in some steps. Than WinDroid received the signal from the watch and triggered e.g. the installation of TWRP.
Hope this helps a bit.
I also have the same issue with su not installing with the wintool (no adb drivers). Also getting the force close of su after restarting watch like the others have mentioned here. I wanted to install the wifi mod also, can't figure that out either. not to familure with adb, and was hoping the wintool would install it to the phone. No luck so far. Any suggestions would be appreciated.
Thanks.
ejl2002 said:
I also have the same issue with su not installing with the wintool (no adb drivers). Also getting the force close of su after restarting watch like the others have mentioned here. I wanted to install the wifi mod also, can't figure that out either. not to familure with adb, and was hoping the wintool would install it to the phone. No luck so far. Any suggestions would be appreciated.
Thanks.
Click to expand...
Click to collapse
I've done this multiple times and sometimes the behaviour is a little bit strange but in the end these are my steps to flash the watch
(I'm flashing everything, so be aware that every data from the watch will be deleted
1. Watch is on and home screen is visible
1. a) adb push supersu.zip /sdcard/
1.b) adb push lenok_wifi_zip-02.zip /sdcard/
2. adb reboot-bootloader
3. Check "fastboot devices" if device is available, if not, unplug cable and reconnect it (I have to do it everytime for fastboot!)
4. fastboot flash boot boot_gwr_5.1.1.img
5. fastboot flash system system_gwr_5.1.1.img
6.a) fastboot flash recovery recovery.img
6.b) fastboot flash recovery twrp-2.8.6.0-lenok.img
-> this is strange for me: If I only flash twrp, then twrp will not be started. If the original recovery.img is flashed before, then it's working!
7.) In twrp install supersu.zip
8) in twrp install lenok_wifi_zip-02.zip
Hope this helps a bit
Thanks for your help, I finally figured out how to use adb, and I was able to push the superuser file and wifi zip. All is working well, thanks again.
fastboot not finding my watch
hi all, i am trying to unlock my g watch r and install twrp the problem i have is after i reboot into fastboot, fast boot cannot find my device, it still shows in my computers device manager list as a android bootloader interface but fast boot commands all just say waiting for device, i have tried every driver i can find and have made no progress, i have also tried a factory reset and still nothing.
any ideas ?
I DL the twrp on post 1 and I got the twrp...but it has ext img.dmg. .... Not sure how to convert to img only? I tried flashing it and it gave me an error.
---------- Post added at 03:11 PM ---------- Previous post was at 02:31 PM ----------
I managed to get the right img. file....however I can't get this flashed at all. Tried changing the name...I made sure the "img" wasnt duplicated. But I keep getting and "error cannot load". BY THE WAY...I'M USING A MAC!!!DONT KNOW IF THAT MAKES A DIFFERENCE
Please help....TIA
---------- Post added at 03:28 PM ---------- Previous post was at 03:11 PM ----------
I'm curious...since I can't get Twrp to flash..... do i have to use a custom recovery to flash the su? I can get into stock recovery....can i install the su via adb in stock recovery?
Okay...with a little surfing on the information highway and making some connections....I figured out how to do use this method on Mac. If anyone has any questions about the method i used... hit reply.
Thanks to the og post.
Sent from my Nexus 6 using Tapatalk
Rooted!
Using posts #1 and #130 I successfully rooted my LG Watch R! Thanks clicked, of course!
Related
ok, i am stuck on my boot up screen. i flashed a zip file xposed arm zip. after the reboot it will not pass the boot animation screen. now on my old Motorola phone, i would do the pwr + vol keys to boot back in to recovery. well this does no work on my X. any one have any ideas. I am rooted, unlocked, twrp was installed from play store, & i did do a back up. thanks
JWACK72 said:
ok, i am stuck on my boot up screen. i flashed a zip file xposed arm zip. after the reboot it will not pass the boot animation screen. now on my old Motorola phone, i would do the pwr + vol keys to boot back in to recovery. well this does no work on my X. any one have any ideas. I am rooted, unlocked, twrp was installed from play store, & i did do a back up. thanks
Click to expand...
Click to collapse
What device do you have, XT1095, XT1097, etc? And you are not able to boot into the bootloader using vol down + power correct?
It was a 1096, now its trash. it would go into fastboot, but could not get into twrp recovery. its done. RIP
JWACK72 said:
It was a 1096, now its trash. it would go into fastboot, but could not get into twrp recovery. its done. RIP
Click to expand...
Click to collapse
If it boots to fastboot, it's not dead. Just reflash the recovery and you're good to go.
Sent from my XT1095 using Tapatalk
Was there a resolution for this? I'm having a similar problem. I'm not sure how I got to this status, but here's what I'm dealing with:
Device: XT1095
Bootloader: Unlocked
Rooted, ROM - Resurrection Remix, TWRP
Turning on the phone reaches the RR bootsplash and proceeds to bootloop.
When holding down the power and volume down, it will enter fastboot.
When I try to open TWRP recovery, it'll show the blue TWRP screen and just sit there.
I have tried to reinstall TWRP, but that has no effect. I didn't want to manually flash another ROM or go back to stock because at least now it seems USB debugging is on and if I flashed a ROM I cant be sure I'd be able to turn it on. Do any of you pros have some ideas hove I can get back into my phone? Thanks
bibbin said:
I have tried to reinstall TWRP, but that has no effect. I didn't want to manually flash another ROM or go back to stock because at least now it seems USB debugging is on and if I flashed a ROM I cant be sure I'd be able to turn it on. Do any of you pros have some ideas hove I can get back into my phone? Thanks
Click to expand...
Click to collapse
Do you have a USB-OTG device plugged in while trying to start TWRP? If so remove it, you can mount it after TWRP starts if this helps.
Have you tried a different build of TWRP? I'm currently using the one built by invisiblek, one of the CM devs for the victara. It was built and posted on December 8th and is here: http://www.invisiblek.org/twrp/twrp_2.8.7.0-0624b8bd_victara.img
Have you tried flashing the stock recovery to see if that will start? If it does, you could use the factory reset option there and then try reinstalling TWRP. (TWRP has a settings directory in /sdcard and maybe that is corrupted.)
There have been a few people posting with this problem but I've not seen a definitive fix for it.
Thank for the quick response. No, I don't have USB-OTG inserted. It is using TWRP 2.8.7.1. No, I haven't tried installing the version you mentioned. What I did do was attempt to flash the pre-installed TWRP 2.8.1.0 via MOTO X TOOLKIT. It failed. I'm not very experienced at using ADB manually. As I mentioned, I've been reluctant to flash another ROM (custom or stock) because I don't want to get stuck with USB debugging inactive with no way to get in far enough to reactivate it.
---------- Post added at 04:32 PM ---------- Previous post was at 03:40 PM ----------
If I manage to install the invisiblek TWRP and it opens properly will I then be able to restore the backups created with TWRP 2.8.7.1?
If that's the case, I need to find a tutorial on installing TWRP manually via ADB, right? I usually install TWRP via TWRP Manager.
bibbin said:
Thank for the quick response. No, I don't have USB-OTG inserted. It is using TWRP 2.8.7.1. No, I haven't tried installing the version you mentioned. What I did do was attempt to flash the pre-installed TWRP 2.8.1.0 via MOTO X TOOLKIT. It failed. I'm not very experienced at using ADB manually. As I mentioned, I've been reluctant to flash another ROM (custom or stock) because I don't want to get stuck with USB debugging inactive with no way to get in far enough to reactivate it.
---------- Post added at 04:32 PM ---------- Previous post was at 03:40 PM ----------
If I manage to install the invisiblek TWRP and it opens properly will I then be able to restore the backups created with TWRP 2.8.7.1?
If that's the case, I need to find a tutorial on installing TWRP manually via ADB, right? I usually install TWRP via TWRP Manager.
Click to expand...
Click to collapse
That's interesting, the TWRP Manager has never worked correctly for me although it's been a long time since I've tried it.
To flash manually, you actually need fastboot which is usually installed along with adb. If you open a command window, and type in fastboot and it runs, the rest is pretty easy. If it doesn't run, this thread has the 15 second ADB/Fastboot installer, select to install it system-wide: http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
Download the recovery image, rename the file to twrp.img, then open a command window in the folder where you downloaded it (type cmd then Enter in the address line at the top of the folder window.)
When the command window is open and the phone is in bootloader mode and connected to the computer with the USB cable, enter the command "fastboot device" (without the quotes) If everything is working it will list the serial number of your phone.
Then enter "fastboot flash recovery twrp.img" (without the quotes) to start the flashing process, ignore the size mismatch message. It will only take a few seconds to complete.
Use the volume down key to highlight recovery, then volume up to select it. Hopefully TWRP will boot up and you'll be good to go!
Well, reinstalling TWRP didn't fix it. Thoughts? Anyone?
bibbin said:
Well, reinstalling TWRP didn't fix it. Thoughts? Anyone?
Click to expand...
Click to collapse
Reflash stock rom from fastboot.
Sent from my XT1095 using Tapatalk
UPDATE: Thanks all. Well, after fiddling around with various methods of reinstalling TWRP, I managed to get it reinstalled and all is back to normal now.
Looking for an answer I have not been able to find as to recovering a used N6.
What I have is a used N6, with TWRP 6.8.7.1 (newest version I believe) no recovery files and does not appear to have a working system on it. The bootloader has been relocked (won't allow unlocking or reflashing of stock firmware). What I am guessing is some one unlocked it, modified it, and relocked it then somehow messed up and wiped the system ... Guessing.
It has the older 71.10 bootloader on it now, not sure if it updated beyond 5.11 or not.
Just thinking (as I write this) would it be possible to make an image of another N6 put it on a OTG thumb drive and restore that or if possible push recovery files through Fastboot or possibly ADB in recovery?
Or am I out luck?
Any know fixes?
My recommendation would be to push files through fastboot. Follow this guide: http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
As a note, I recently had to go through this process and the FLASH ALL file was failing to flash the system file. The answer was to manually flash each file myself (directions provided in the same post). It was fairly easy once I realized the issues with FLASH ALL.
As soon as you get android booting, go back and unlocked the bootloader. I don't get all these people locking their bootloaders... ESPECIALLY with a rom and custom recovery!
The above is almost the right advice, but IIRC it wont work with a locked bootloader.
Fortunately you have TWRP installed. Don't mess with your recovery partition until you get this sorted.
Just go download a rom, any will probably work... I would stick with an AOSP one and maybe download the 5.1.1
You may be able to just mount the phone as an MTP device, I think that may be supported by TWRP at this time? Or sideload/push.
Gimme a sec, I'll post some links
---------- Post added at 01:29 PM ---------- Previous post was at 01:14 PM ----------
As I said most roms will probably be OK, But to be specific I would just grab a 5.1.1 version of pure nexus... say the last 5.1.1 version
https://www.androidfilehost.com/?w=files&flid=34545
Download page for pure nexus (this does not include gapps)
Specifically I would download this one, as I said its the last 5.1.1 version. I say this because the bootloader should be fine with it whether its updated or not (I couldn't find a list of what bootloader is what version)
https://www.androidfilehost.com/?fid=24052804347817485
Boot to recovery, and see if your phone shows up under my computer. MTP transfer should be enabled by default in TWRP and is supported by TWRP version > 2.8
If you can't get it to show up as an MTP device, you should be able to see it with ADB while booted into TWRP. Use either the push command
http://stackoverflow.com/questions/...mand-to-push-a-file-on-device-without-sd-card (discussion on push)
push maybe to /sdcard if the directory exists.
I'd probably just use sideload though,
https://twrp.me/faq/ADBSideload.html
One of these should work
---------- Post added at 01:37 PM ---------- Previous post was at 01:29 PM ----------
I'll leave it to you to find gapps for 5.1.1
I don't think you would need them though as android should still load and work fine with out them. I would simply start up the phone with the rom installed, turn on allow oem unlock, boot immediately back into bootloader and unlock the boot loader. If something happens to that recovery partition the phone is a paperweight with the bootloader locked... really not worth keeping it locked.
Once you get the bootloader unlocked, update to something current and worry about gapps then?
Thank you so much guys!! Will give this run as soon as I have a chance and update the post(may take a day or so been pretty busy at work and such)
UPDATE : @scryan Hey just want to say that did the trick, had to use a thumb drive and OTG cable to load the ROM. But was in and out with an now unlocked bootloader in under 30 minutes.
Thanks again guys!!
[SOLVED] Stuck in "warning bootloader unlocked" screen. Device won't turn OFF.
Hi all,
I have a Moto G 2014 (Titan, XT1068).
I am not new to custom ROM-ing and Android hacking, had all 4 of my personal Android phones unlocked and rooted just fine - I usually know what I'm doing.
This here is my mom's phone and it's the first Moto G 2014 I attempted to unlock & root so far. I know the basics, but this particular device gives me headache...
All actions were performed on 07. October 2016 after carefully researching the latest HOW-TOs for the Moto G 2014 on XDA and other websites:
- I unlocked the bootloader using the official process from Motorola to receive the "unique key".
- I installed twrp-3.0.2-3-titan.img recovery.
- I downloaded SR1-SuperSU-v2.78-SR1-20160915123031.zip and placed it on storage.
- I booted into TWRP recovery, installed SuperSU and Wiped Dalvik+Cache, then rebooted.
Since then, I am stuck in the "warning bootloader unlocked" (WBU) screen and the device won't turn off.
If I press the power button and hold it for a few seconds, normally it turned the device off, but now it just reboots into the WBU screen, looping forever.
- I can still enter my fastboot by holding VOL-down + Power, get a adb connection with my Android SDK + platform tools on my Windows and issue adb and fastboot commands normally.
- I can still enter the recovery and do stuff with it normally.
Since this incident, I have also tried a normal Wipe (whatever the default wipe settings are) in TWRP, no change / effect.
I have no clue what to do next, other than wait for the battery to go empty that is, since I can't even turn the device off.
Some methodologically sound advice would be highly appreciated at this point. :good:
Thank you in advance.
You just can't flash the supersu file in twrp before flashing the supersu you need to flash roo.M.br.zip file in fastboot mode then you can flash the SuperSU.
The file available at stock firmware section.
---------- Post added at 09:48 AM ---------- Previous post was at 09:46 AM ----------
Flash the stock rom from fastboot mode then again root the device as i said it will solve the problem.
Prasourabha said:
You just can't flash the supersu file in twrp before flashing the supersu you need to flash roo.M.br.zip file in fastboot mode then you can flash the SuperSU.
The file available at stock firmware section.
---------- Post added at 09:48 AM ---------- Previous post was at 09:46 AM ----------
Flash the stock rom from fastboot mode then again root the device as i said it will solve the problem.
Click to expand...
Click to collapse
Is this roo.M.br.zip file included in the Stock Rom or is it the Stock Rom itself?
Or is there another general name for this roo.M.br.zip? Because I can't find it via the search function of the forum.
Anyhow ... in the meantime I will be downloading XT1068_TITAN_RETAILDSDS_5.0.2_LXB22.99-16.3_Easy_Installer.zip which is linked on the following thread:
- http://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-5-0-2-lxb22-46-t3019612
- first URL for XT1068 labeled as "***NEW*** DOWNLOAD XT1068 5.0.2 LXB22.99-16.3 RETDSDS WITH STAGE FRIGHT FIX RETAIL DUAL SIM DUAL STANDBY (EU/INDIAN/GLOBAL) 26/08/2015 BUILD ***NEW***"
But I already had a look into the archive, nowhere to find a roo.M.br.zip is even similarly named file(s).
Could you be a little more specific or provide the correct XDA thread / link?
Also, the fact that "I can't just flash SU" it must be device specific, right?
Because on my other Android phones I just installed/flashed SU via recovery mod with no problems and that was it.
EDIT: also, according to this guide here, apparently you "can just install SU", if I understand correctly and it's more or less exactly how I proceeded (unless wiping cache/dalvik after flash was harmful):
- http://forum.xda-developers.com/moto-g-2014/general/guide-root-moto-g-2nd-gen-2014-t2874245
Here is the link of the page where yiu can find the file and the rooting guide
http://forum.xda-developers.com/moto-g-2014/general/root-root-moto-g-2014-android-t3255711
Prasourabha said:
Here is the link of the page where yiu can find the file and the rooting guide
http://forum.xda-developers.com/moto-g-2014/general/root-root-moto-g-2014-android-t3255711
Click to expand...
Click to collapse
Sorry for not understanding your answer at first.
Obviously you were refering to two different things in one post and I was a little confused.
- RESTORING THE STOCK-ROM BASED ON MARSHMALLOW / ANDROID 6.0 HAS BROKEN THE BOOTLOOP IN THE UNLOCKED BOOTLOADER WARNING.
The other issue was obviously that you catched what I wanted to do originally, which was to ROOT the device.
- DOWNLOADING AND FLASHING THIS "root-titan-M-BR.zip" IN THE THREAD YOU SPECIFIED ENABLED ME TO FLASH SUPERSU AFTERWARDS WITHOUT PROBLEMS.
Obviously I can now go on doing what I initially intended, which is installing CM13 on my mom's phone.
I almost thought I had bricked the phone for good.
Thank you for your support. :good:
i have followed directions to the best of my knowledge, i had twrp already installed but i wanted to update to 20V i was running 20Q, so i used lgup and did a refurbished option. I am running windows 10, i installed minimal adb, adb recognizes my phone, my phone was unlocked and after doing lg up it stayed unlocked, so i proceed to booting into twrp from fastboot, it does boot into twrp i even installed su V279 and updated it thru google play, my problem is when i go to do fastboot flash recovery xxx.img i get writing recovery failed, even if i flashify it does not install twrp i do get root permission according to su. I havent been able to past that, when i try to reboot into twrp with buttons or application phone shuts down and instead of going to twrp lg logo blinks for a second and then phone restarts to normal operation, what am i doing wrong? i been playing on this for days now, thanks in advance
ps, i even installed the rooted 20V from here still same result, unable to flash twrp
weird but i downloaded twrp for 811-815 thru the phone ap, twrp app and i flashed it with same app and it worked, i have no clue what went on, but i tried different downloads and all fail til just now, thank God!
ok please dont do what i did, twrp did flash but it is for 815, i installed it cause app said it was for both, and it wont let me flash h811 files, will continue to work on it, starting from scratch
beto669 said:
ok please dont do what i did, twrp did flash but it is for 815, i installed it cause app said it was for both, and it wont let me flash h811 files, will continue to work on it, starting from scratch
Click to expand...
Click to collapse
use this one works for both h815-h811 thats waht am using right now..
https://forum.xda-developers.com/showpost.php?p=72468882&postcount=422
as for the recovery.. missing not sure .. but i would KDZ it again and start from scratch using the twrp i gave you in link.
---------- Post added at 09:47 PM ---------- Previous post was at 09:45 PM ----------
UPDATE
i just notice your command is worng to send twrp it should be
fastboot boot twrp.img
not
fastboot flash recovery xxx.img
---------- Post added at 09:47 PM ---------- Previous post was at 09:47 PM ----------
UPDATE
i just notice your command is worng to send twrp it should be
fastboot boot twrp.img
not
fastboot flash recovery xxx.img
Thank you for your suggestion i will try after work. I was able to use fastboot boot twrp.img and it load as it should, but my issues is i want permanent twrp, thats why i did the flash recovery
Sent from my LG-H811 using XDA-Developers Legacy app
problem solved, i tried your twrp and had same issue, it will boot but was not writing to phone, i read somewhere, after unlocking the bootloader to save twrp on the phone and then after booting into twrp with fastboot boot twr.img to use twrp file manager and copy from phone to external sd card, i tried that and it worked! now i have permanent twrp. I believe something happens when i tried to copy the file from my computer to my external sd, either my sd card is not working properly and doesnt write everything or some files just dont get transferred cause i copy and paste using file manager app from phone to sd and didnt work. I'm glad i have twrp back in my phone! Thank you raptorddd for helping
beto669 said:
problem solved, i tried your twrp and had same issue, it will boot but was not writing to phone, i read somewhere, after unlocking the bootloader to save twrp on the phone and then after booting into twrp with fastboot boot twr.img to use twrp file manager and copy from phone to external sd card, i tried that and it worked! now i have permanent twrp. I believe something happens when i tried to copy the file from my computer to my external sd, either my sd card is not working properly and doesnt write everything or some files just dont get transferred cause i copy and paste using file manager app from phone to sd and didnt work. I'm glad i have twrp back in my phone! Thank you raptorddd for helping
Click to expand...
Click to collapse
yes you need to have both files i use minimal adb so i place one in that folder and other in external sd .. or internal. then selecting install and lower it says image. then it ask you to select. then select recovery and flash install. and youll have permanent twrp.
could it be that you use USB 3.0 or win10.? i know that for KDZ and LGUP it has problems.. your welcomed you should try G5 port rom from astrako.:good:
the h811 vaariant.
I could have been usb3 as you said I was using Windows 10, I had no problems with lg up though. And sure I will try the g5 port as soon as I get a chance, thank you again!
Sent from my LG-H811 using XDA-Developers Legacy app
houston we have a problem...
5 bucks for any good idea!
I have an old xt1068 (titan) that after an (official) update it becames a small brick... (it was stock, no modded bootloader or whatevere, just stock!)
today I decided to give it a chance but then only thing I reach is the bootloader
whatever thing (official retail firmware) I try to flash it doesn't work...
so I unlocked the bootloader with success to give a try a custom rom but suddenly I get a issue...
I can't install latest twrp (I tried also a couple of older ones), I can only boot trough (latest) twrp but whatever rom I install I get error7
I noticed that when it reboots the content (/sdcard /data and /system) is untouched even if from shell I can remount rw... it seems that I can delete but in reality I don't delete anything
I tried almost everything... if I try to re-stock upon reboot I reach the dead android robot
the device is an xt1068, bootloader 48.87 (30.06.2016), unlocked (status code 3)
any (good) ideas?
O this thing is happened to me , i has on stock 5.0 and i updated to a new version ,but after i get only bootloop so i unlocked the bootloader and flash the latest twrp , and if i try to install any custom rom twrp give me some partition are corrupt. Enter in TWRP open WIPE > Advanced Wipe > (check your corrupt partition ,in my case is the data) > Repair or Change File System > Change File System > Ext3 or Ext4 > Swipe to Change (if this don't work try olso resize partition or repair partition)
HiR3x said:
O this thing is happened to me , i has on stock 5.0 and i updated to a new version ,but after i get only bootloop so i unlocked the bootloader and flash the latest twrp , and if i try to install any custom rom twrp give me some partition are corrupt. Enter in TWRP open WIPE > Advanced Wipe > (check your corrupt partition ,in my case is the data) > Repair or Change File System > Change File System > Ext3 or Ext4 > Swipe to Change (if this don't work try olso resize partition or repair partition)
Click to expand...
Click to collapse
no way... I tried but nothing changes... it seems that partitions are read-only
anyway I'm not able to flash twrp (no error it just doesn't install), I can only boot twrp but again nothing changes, I tried soon after booting twrp to gain root trought supersu/magisk, all works without error but upon reboot partitions aren't touched at all
I have the exact same issue on the exact same phone.
However, what I have noticed is the fact that after SuperSu is flashed (Booting through TWRP recovery once), it doesn't actually flash at all. But what surprised me was that after the flashing, the phone reboots instead of taking me back to the recovery.
A good idea would be that maybe the bootloader isn't actually unlocked for everything. Maybe the company making the device just doesn't want us to get a new one.
In any case, I never give. I will keep trying.
---------- Post added at 09:08 AM ---------- Previous post was at 08:37 AM ----------
The solution is simply using a different TWRP version. I had mentioned my concerned earlier and I was right. We wer einitially flashing a wrong TWRP in the device and hence the problem. I found the solution in this video here: https://www.youtube.com/watch?v=9_9vkJvzWcU
However, the TWRP and Su can be found here if the guy who uploaded the video has deleted it:
https://drive.google.com/open?id=1rSyDJoeOVVFHCbNa_jkfH9HUnDoZqBhd
I am glad to hear that it helped you to resolve your problem
ni6hant said:
I have the exact same issue on the exact same phone.
However, what I have noticed is the fact that after SuperSu is flashed (Booting through TWRP recovery once), it doesn't actually flash at all. But what surprised me was that after the flashing, the phone reboots instead of taking me back to the recovery.
A good idea would be that maybe the bootloader isn't actually unlocked for everything. Maybe the company making the device just doesn't want us to get a new one.
In any case, I never give. I will keep trying.
---------- Post added at 09:08 AM ---------- Previous post was at 08:37 AM ----------
The solution is simply using a different TWRP version. I had mentioned my concerned earlier and I was right. We wer einitially flashing a wrong TWRP in the device and hence the problem. I found the solution in this video here: https://www.youtube.com/watch?v=9_9vkJvzWcU
However, the TWRP and Su can be found here if the guy who uploaded the video has deleted it:
https://drive.google.com/open?id=1rSyDJoeOVVFHCbNa_jkfH9HUnDoZqBhd
Click to expand...
Click to collapse
I am glad to hear that it helped you to resolve your problem all the required downloading links are working fit and fine it's my channel show me some love via comments and likes on my video
mandar91 said:
I am glad to hear that it helped you to resolve your problem all the required downloading links are working fit and fine it's my channel show me some love via comments and likes on my video
Click to expand...
Click to collapse
Already commented a liked.
ni6hant said:
I have the exact same issue on the exact same phone.
However, what I have noticed is the fact that after SuperSu is flashed (Booting through TWRP recovery once), it doesn't actually flash at all. But what surprised me was that after the flashing, the phone reboots instead of taking me back to the recovery.
A good idea would be that maybe the bootloader isn't actually unlocked for everything. Maybe the company making the device just doesn't want us to get a new one.
In any case, I never give. I will keep trying.
---------- Post added at 09:08 AM ---------- Previous post was at 08:37 AM ----------
The solution is simply using a different TWRP version. I had mentioned my concerned earlier and I was right. We wer einitially flashing a wrong TWRP in the device and hence the problem. I found the solution in this video here: https://www.youtube.com/watch?v=9_9vkJvzWcU
However, the TWRP and Su can be found here if the guy who uploaded the video has deleted it:
https://drive.google.com/open?id=1rSyDJoeOVVFHCbNa_jkfH9HUnDoZqBhd
Click to expand...
Click to collapse
thank you for help but it didn't work... rebooting into recovery lands me on "dead robot" saying "no command", then after 1 minute it reboots... and reboots... and so on...
I think I tried almost everything... I'm really lost
How come!
How can it happen. It is Moto G 2?
suiller said:
thank you for help but it didn't work... rebooting into recovery lands me on "dead robot" saying "no command", then after 1 minute it reboots... and reboots... and so on...
I think I tried almost everything... I'm really lost
Click to expand...
Click to collapse
ni6hant said:
How can it happen. It is Moto G 2?
Click to expand...
Click to collapse
this is what I see from bootloader...