Database Users

[Q] Root Problems

I'm having a strange time with my phone, I rooted the phone, by the guides on xda, everything went well, superSu was installed,
then I tried to flash a new recovery and a new kernel, but nothing worked, after some searching I found this AutoRec tool, it worked
the recovery changed to TWRP, so I tried to flash dorimanx again, and again nothing changed, the flashing was done, but after reboot still
no change with the kernel.
So I checked if the device is rooted, I did this on the begining of the process and it was, now, it showed that the device isn;t rooted.
Now I have a TWRP recovery, without root, and when I try to root, I have to press "apply update from adb..." but I dont have thing option anymore,
Thanks a lot for your help!

maxwellz said:
I'm having a strange time with my phone, I rooted the phone, by the guides on xda, everything went well, superSu was installed,
then I tried to flash a new recovery and a new kernel, but nothing worked, after some searching I found this AutoRec tool, it worked
the recovery changed to TWRP, so I tried to flash dorimanx again, and again nothing changed, the flashing was done, but after reboot still
no change with the kernel.
So I checked if the device is rooted, I did this on the begining of the process and it was, now, it showed that the device isn;t rooted.
Now I have a TWRP recovery, without root, and when I try to root, I have to press "apply update from adb..." but I dont have thing option anymore,
Thanks a lot for your help!
Click to expand...
Click to collapse
You can still root with custom recovery the difference is you need to go to advanced and sideload to be able to apply the root.zip, you can also look for the flashable supersu.zip and flash it from recovery and that will root your device
Sent from my LG-D800 using XDA Premium 4 mobile app

Thanks for your reply, I gained back the root.
Downloaded from PlayStore some app called Rebooted - went to recovery [TWRP if it has any influence] and flashed Dorimanx kernel,
the flashing is over, but nothing new... it just doesnt install nothing... so strange..

Anyone please?

maxwellz said:
Anyone please?
Click to expand...
Click to collapse
I suggest you start over. Not sure if you performed wipes(wipe all except internal).
But
1. flash kdz
2. root
3. autorec
4. wipe wipe wipe(except internal)
5. install
6. profit

[Q] Cannot re root after 4.4.3 upgrade

Hi,
I previously had purity rom on my nexus 10. I decided to back to stock and use the xposed framework. So with 4.4.3 I flashed the stock images (manualy so it didn't wipe my sdcard partition), wiped data, cache and dalvick.
Stock 4.4.3 works fine, no issues here, but in acquiring root by flashing supersu update (both 93 and 99r3) root doesn't seem to stick. I can adb in and su from terminal, but when booting android supersu days it couldn't acquire root. I have tried other clockworkmod recovery and team win recovery so see if it was a bug with recovery, but no dice. Clockwork did occasionally say it lost root and press Yes to put it back, it did this on my nexus 5 and I still kept root.
I have even tried the universal nexus toolkit but that didn't work either. All methods I have tried have run the zip output fine, saying success.
Any ideas what's wrong. I assume I have done something wrong but can't find much information about root not working like this.

Did you try chainfire 2.00?
Link to Chainfire page

Hi,
Some time ago I've faced the same issue as you, what worked for me was using an older supersu flashable zip and after flashing it I flashed the latest. Don't know if it was placebo or something, but always worked for me .
~Lord

I did the exact same couple days ago after running Omnirom. I used this odex stock image http://forum.xda-developers.com/showthread.php?t=2529492
After the initial factory wipe I wiped dalvik,cache,data, and flashed SU after flashing the ROM but before reboot. Using latest TWRP. Hope this helps.

Acquiring root after Temasek's CM 13 marshmallow install

Hello, I've recently installed Temasek's CM 13 nightly marshmallow build to my bootloader unlock note 3. I'm having a difficult time acquiring root after the install. I've flashed SuperSu to no avail. I've even tried the Aramaic tool method with no luck. Is there anything I can do to get root back on this phone or am I screwed?

Look for SuperSU in the settings menu.
Not sure if you need to turn on developer options for it to appear there or not.
[Edit]Did you install CM with a custom recovery, or with flashfire?
Your post doesn't say one way or another, but if you have an unlocked bootloader you can flash a custom recovery using Odin... meaning that you always have root, so long as you preserve the unlocked bootloader.
Having only a single root (locked bootloader and no custom recovery) and using FlashFire to install a ROM puts you at constant risk of root loss.
.

Thanks for your reply. I have TWRP 3.0.2 installed. I didn't check to see if it was installed under settings but I have since restored back to my stock rooted ROM. I will reinstall CM again and let you know if SuperSu shows up in settings.

cblendz said:
Thanks for your reply. I have TWRP 3.0.2 installed. I didn't check to see if it was installed under settings but I have since restored back to my stock rooted ROM. I will reinstall CM again and let you know if SuperSu shows up in settings.
Click to expand...
Click to collapse
Hey.
Just to make sure I'm being clear - you do have to flash SuperSU along with the ROM flash - root is not "baked in" to CM.
For some reason CM "hides" the SuperSU app so that it only shows up in the Settings menu and not in the app drawer.
It wasn't clear from the way you described things if that's what was going on, but I remember having the same (?) experience ... I thought the install of SuperSU was somehow missing due to the fact it didn't show up in the app drawer.
.

bftb0 said:
Hey.
Just to make sure I'm being clear - you do have to flash SuperSU along with the ROM flash - root is not "baked in" to CM.
For some reason CM "hides" the SuperSU app so that it only shows up in the Settings menu and not in the app drawer.
It wasn't clear from the way you described things if that's what was going on, but I remember having the same (?) experience ... I thought the install of SuperSU was somehow missing due to the fact it didn't show up in the app drawer.
.
Click to expand...
Click to collapse
I've just tried reinstalling the cm13 ROM again and this time I checked to see if SuperSu was installed in settings. It didn't show up there either. I don't know what's going on with it. I wipe everything then flashed the ROM then wiped dalvik and cache. Then flashed open Gapps. Wiped dalvik and cache and flashed 2.78 SuperSu and reboot to system.

cblendz said:
I've just tried reinstalling the cm13 ROM again and this time I checked to see if SuperSu was installed in settings. It didn't show up there either. I don't know what's going on with it. I wipe everything then flashed the ROM then wiped dalvik and cache. Then flashed open Gapps. Wiped dalvik and cache and flashed 2.78 SuperSu and reboot to system.
Click to expand...
Click to collapse
I don't know if this would make a difference, but somewhere in that thread trader418 mentioned that you had to flash the ROM after the Gapps to take care of an issue with some init.d scripts. As in the sequence: wipe - ROM - gapps - ROM - supersu - first_boot.
I'm not sure if that's related or not. It's been long enough ago that I can't remember the exact details, but I remember thinking "hey, where did it go, I know I flashed it!".
Maybe it would be best to ask this question in that thread.
.

bftb0 said:
I don't know if this would make a difference, but somewhere in that thread trader418 mentioned that you had to flash the ROM after the Gapps to take care of an issue with some init.d scripts. As in the sequence: wipe - ROM - gapps - ROM - supersu - first_boot.
I'm not sure if that's related or not. It's been long enough ago that I can't remember the exact details, but I remember thinking "hey, where did it go, I know I flashed it!".
Maybe it would be best to ask this question in that thread.
.
Click to expand...
Click to collapse
Thanks a lot that was it. Finally got root. I wish CM would bake root in their Roms but all is good now. Thanks.

x720 partial unlocked bootloader? [SOLVED]

So I got my 6GB/64GB x720 yesterday. It had Google Play Store already installed (ordered it from HonorBuy) and asked me to install a 7MB OTA, so it seems it had a recent version of EUI on it. My idea was to put LineageOS 14.1 on it or if it wasn't stable enough for me, at least a debloated and rooted stock. So searched XDA and followed this HowTo. No Errors, flashboot oem device-info said, bootloader unlocked, perfekt. Installed TWRP, downloaded recent LineageOS and followed the guides to flash (wipe, ...). Unfortunately flashing never finished, I always had a full progress-bar and it stayed there without doing anything (ok, the device got hot). Thinking of a broken download, I redownloaded the ROM but same problem. So I started downloading other ROMs from XDA: Resurection Remix and OmniROM. Flashing-process went thru, but couldn't flash gapps and ROMs didn't boot at all. I was always only getting to the LeEco-Bootlogo with the chinese writings. So next thought was, maybe for some reason I can't install Lineage-based ROMs, let's figure out later and get a debloated stock ROM. So I downloaded MAURO V2.2_Free and gave it another try. Looked more promising, as the bootlogo was a little different, no more chinese writing but english. Unfortunately this was all I could see of MAURO as I only got a bootloop... so again reflashed MAURO and this time a single line in TWRP-output came to my eye "boot.img could not be written". I checked flashboot oem device-info after every flash and it always told me, bootloader is unlocked, but there seems to be something else that I'm missing that obviously still keeps the bootloader locked. I wiped the phone several times, even sdcard... nothing helped. The only method that worked for me to get a working rom running was by this guide, manualy flashing every bit of stock ROM with flashboot. With MAURO-ROM, I also tried to flash boot.img manually with flashboot, but that didn't work, either.
Anyone of you experienced the same? What am I missing? Or is this some new protection implemented by LeEco for the most recent devices? Any help really appreciated!
regards
CDFS

I have the same phone from Honorbuy, I flashed twrp using the tool by Mauronofrio and from the twrp wiped all and flashed the custom rom, all went ok, no errors at all! Glad to see you have solved anyway!

Thanks for the answer... no, it's not solved for me... still a lot of bloat on the phone I can't get rid of. Do you have a link for the tool you mentioned? Could be worth a try...

Hi! I've used this tool installing it on a Windows 7 64 system:
https://forum.xda-developers.com/le-pro3/development/tool-tool-one-mauronofrio-t3580611
Then turned ON the (original LeEco stock rom) usb debug option by the rom's developer options, then downloaded the LineageOS 14.1 by Team Superluminal in the phone's internal SD (the only SD it have!) + Arm64 nano Gapps, then with the tool gave a reboot in sideload mode. Then flashed the twrp recovery by the tool, restarted in recovery mode then executed a backup of ALL the "backupable" stuff (all the original rom and data and efs), then in wipe/advanced options I wiped dalvik, system, cache, data. Then in Advanced/file manager I wiped all the SD files with a dot ( . ) at the beginning of their names, then flashed the custom rom + gapps, reboot system, wait some minutes, done!

No luck with this tool, it doesn't even find my device. Any other ideas? I've read something for the x727, where they had to flash a 19s bootloader first, but I don't want to fiddle with flashing files that are not 100% meant for the x720...
CDFS

Solved! As I could install TWRP I just went the next step and installed SuperSU (rooted the phone) in order to at least debloat stock rom. During the installation of SuperSU I saw, that SuperSU obviously patches somehow the bootloader. After checking that SuperSU worked in the ROM, I was curious if this could be the missing part I was searching for. I tried to install a LineageOS-based ROM and BINGO! it just went straight through! From my previous phones I was used to just install TWRP, wipe anything and flash desired ROM. This seems to be different on this device... so the proper procedure to be able to flash any ROMs is: Install TWRP, root stock ROM, reboot so SuperSU is fully functional, then go back into TWRP, wipe, flash what you want.
CDFS

I hate to say it, but it's still not solved. After testing Resurrection Remix, I wanted to test turbos ROMs, so went to TWRP, wiped and flashed... and got the same behaviour as before, ROM not booting. Also installing SuperSU via TWRP again didn't help, so brought back the phone to stock 023S manualy with the guide by Presterin, installed TWRP again and also SuperSU. No Errors, but flashing a different ROM didn't worked. So for now I'm back to stock, rooted it and tried to debloat it by myself. The only difference between the successful flashing and the failed was the stock version: I had the 026S-update when I rooted the phone and successfuly could flash another ROM. My guess would be that LeEco changed something in the bootloader, but I have no chance to verify this. Anyone from the devs maybe who could look into this? If you need dumos, logs or anything like that, I would be happy to help.
CDFS

This seems unrelated to bootloader.
Anyway:
1. Make sure you got the latest firmware, if not sure:
1.1. Download latest OFFICIAL ROM
1.2. Rename the rom to a 'update.zip' and place it on phone's root directory.
1.3. Reboot to fastboot and flash STOCK RECOVERY
1.4. Reboot to recovery and flash, also check wipe data.
DO NOT FLASH STOCK ROM WITH TWRP! THIS WILL NOT WORK!
That's it, you should have the latest firmware now.
After booting to stock rom, reboot a few times is recommended.
2. Download latest OFFICIAL TWRP
2.1. Flash TWRP with fastboot.
2.2. Reboot to TWRP.
2.3. Download any custom rom of your choice.
2.4. Wipe.
2.5 Flash.
Done.

You can try to flash a stock, old rom using the "Qfil/FlashOne" way as suggested by Tryzex (read his thread and other related threads), then once you have got a stable, full working phone, you can (hopefully!) wait for a LeEco OTA automatic update that can "repair" the file system/partition structure (also bootloader I hope!).
Btw, to debloat it isn't necessary to root the phone, you can keep the phone unrooted & debloated using the file manager embedded in twrp recovery to delete/replace any file/app you want. I'm sorry I can't help you better, cheers and... good luck!
PS
I see now the post from Voron00, it's a good hint!

@voron00 thx for the steps described. I'm using the most recent, official TWRP (3.1.1). Latest Official Stock seems to be 023S on their site, even though there is a 026S update. However, I did this 026S-update and rooted again, but was to cusious if flashing would work now... so I tried flashing turbos MIUI... guess what? It worked. So for whatever reason I seem to have trouble when flashing from a 023S, but no problems when flashing from 026S. I don't quite understand why you think that my problem is not related to the bootloader? As mentioned in the OP, I could see in the logs that while flashing, some roms had thrown errors regarding writing the bootpartition.
CDFS

Seems as I found the culprit, somehow. At least I could flash two other ROMs without any problems. Obviously I mixed and partly missinterpreted some steps found in different threads and howtos. I had "rm -rf for formating" ticked all the time in TWRP. My flashing procedure is now as follows:
1. in TWRP settings check that "rm -rf instead of format" is NOT ticked
2. wipe Cache, System and Data
3. repair filesystem for Cache, System and Data and check that no errors occur
4. in TWRP settings tick "rm -rf instead of format"
5. flash ROM
6. wipe Dalvik
CDFS

"rm -rf" clears all the files and directories without formatting the partition. If your partition is damaged you need a real format to obtain a reliable partition (if the "disk" isn't faulty). Perhaps in your case a real format was required to solve the problem! I always used the real format and assumed other users even so. I see you finally solved the problem!

Mi 9T goes in boot loop when trying to install magisk generated boot image

I had custom rom Evolution 4.5 and the phone was rooted and working well. but then I updated to Evolution 5.1.
Now I have TWRP but no root. Also TWRP cannot decrypt data even when entering correct password.
I read on this forum that i need magisk modified boot image and need to be installed using fastboot. I took out boot.img from Evolution 5.1 rom & patched using magisk. but when i installed it using fastboot the phone went in boot-loop. Had to reinstall rom (thank god for twrp) again to make it work. but my phone is unrooted. How do i root it?
Thanks XDA community.

emailme0909 said:
I had custom rom Evolution 4.5 and the phone was rooted and working well. but then I updated to Evolution 5.1.
Now I have TWRP but no root. Also TWRP cannot decrypt data even when entering correct password.
I read on this forum that i need magisk modified boot image and need to be installed using fastboot. I took out boot.img from Evolution 5.1 rom & patched using magisk. but when i installed it using fastboot the phone went in boot-loop. Had to reinstall rom (thank god for twrp) again to make it work. but my phone is unrooted. How do i root it?
Thanks XDA community.
Click to expand...
Click to collapse
FIXED.
A few things have changed with new versions of everything (evolution 5.1 is Android 11, new TWRP, new Magisk version etc) so things needed doing differently from the usual tutorials (for Android 10).
Formatted data + wiped data, cache & system using twrp.
Flashed the ROM (Evolution 5.1) and booted into it.
Added pattern unlock (not password) - so twrp can work (twrp's current version cant decrypt files using password)- reboot to recovery..
Now, installed MagiskR.zip using TWRP + reboot to rom (to make sure it still boots) - reboot to recovery.
now installed Magisk v21.0.zip & rebooted. - check using root checker- phone is rooted.
Installed root checker application & checked if the phone is rooted. - it was.
Hope this helps someone.