So i just got my x727 and unlocked the bootloader and installed twrp. Everything went great. I wiped the data on the stock 21's rom and it booted just fine. Then I went back into twrp and flashed supersu. After I wiped the dalvik and cache. Now the phone just sits at the
eui" booting screen. Is there a special version of supersu that needs to be flashed? I used the current zip file from the official site.
Any suggestions?
hunter99507 said:
So i just got my x727 and unlocked the bootloader and installed twrp. Everything went great. I wiped the data on the stock 21's rom and it booted just fine. Then I went back into twrp and flashed supersu. After I wiped the dalvik and cache. Now the phone just sits at the
eui" booting screen. Is there a special version of supersu that needs to be flashed? I used the current zip file from the official site.
Any suggestions?
Click to expand...
Click to collapse
You could try installing GalacticStryder's lambda kernel. I used that with Magisk and it was just fine.
same
exact same problem here! I can still boot up twrp but idk what the best fix is. I only unlocked bootloader so i cant root cause i cant reboot the system
I figured my issue out. I was using an old version of supersu which was on their website. Use the current version which is v2.82
Related
Hey, so I rooted my D802 a while ago, and installed TWRP using autorec, and all was going well.
today I received an ota, and against my better judgment , I clicked install, so of course it booted into TWRP and not stock recovery, and it couldn't flash the update, I rebooted the phone and it still booted back in TWRP!!, formatted, system, data, dalvik, and cache, then reboot, same thing, the phone keeps going back to recovery, apparently the command to update (boot into recovery) has been issued to the bootloader, and I have no idea how to cancel it, any ideas?
does anyone know where to find the temporary downloaded file from OTA? maybe flashing it manually through TWRP will fix the issue
thanks
this page helped, I typed the code and viola ,it works, thanks guys
http://forum.xda-developers.com/showthread.php?t=2694530
I rooted my phone installed twrp via autorec--> http://forum.xda-developers.com/showthread.php?t=2715496 . Then I backed up my phone through twrp and then I rebooted and put the newest cm11 stable build --> http://download.cyanogenmod.org/?type=snapshot&device=vs980 on my phone. (I put it in the download file of my phone if that makes any difference), then I went to twrp and wiped everything but internal storage and proceeded to flash cm11 which i found in my download file where I put it (it was a zipped file) and I flashed it, then it went into a boot loop! Currently installing the recovery in twrp that I just made. I do not know what I did wrong could someone please enlighten me? This is the first time doing this sorry if its a noob question.
Thanks.
FYI the recovery worked my phone booted up fine. Also it is a VS980. I do have the verizon variant.
UPDATE:
Tried flashing again, this time with gapps as well (forgot to the first time) same results, flashing the recovery again rn. I AM CLUELESS!!!!
bobberserker said:
FYI the recovery worked my phone booted up fine. Also it is a VS980. I do have the verizon variant.
UPDATE:
Tried flashing again, this time with gapps as well (forgot to the first time) same results, flashing the recovery again rn. I AM CLUELESS!!!!
Click to expand...
Click to collapse
Would uninstalling autorec do anything?
flash the latest recovery from here. Then afterwards check if you have the right version for your variant and check the md5
Krenol said:
flash the latest recovery from here. Then afterwards check if you have the right version for your variant and check the md5
Click to expand...
Click to collapse
Again this is my first time getting this far so here are some noob questions: Would I just flash the zipped folder in twrp? Would I need to wipe anything? Would I need to create another recovery? Would it delete my old recovery?
Thanks.
EDIT:
Also why would updating twrp make such a big difference?
Just Flash the zip File for your variant then Reboot the recovery and go to settings and hit restore default. Don't wipe anything for changing the recovery. And this will just update the rec nothing else
I just reloaded oxygen 3.1.0 on my device, unlocked and flashed recovery. Everything works fine to this point but as soon as I flash superSu my phone stops booting. I have tried clearing the cache and checked for the recommended version of the superSU zip with the same result. Anyone have any suggestions?
rompup said:
I just reloaded oxygen 3.1.0 on my device, unlocked and flashed recovery. Everything works fine to this point but as soon as I flash superSu my phone stops booting. I have tried clearing the cache and checked for the recommended version of the superSU zip with the same result. Anyone have any suggestions?
Click to expand...
Click to collapse
Which recovery ? Which superSu version ?
SuperSU 2.79
TWRP 3.0.2-2
rompup said:
SuperSU 2.79
TWRP 3.0.2-2
Click to expand...
Click to collapse
There shouldn't be a problem as I've used these versions without any problems.
Try a clean flash (wipe data + cache + dalvik cache) with latest superSu beta(2.79 SR1).
Search for supersu in oneplus forums for oxygen 3.1.0 since normal supersu will break boot.
rompup said:
I just reloaded oxygen 3.1.0 on my device, unlocked and flashed recovery. Everything works fine to this point but as soon as I flash superSu my phone stops booting. I have tried clearing the cache and checked for the recommended version of the superSU zip with the same result. Anyone have any suggestions?
Click to expand...
Click to collapse
Scherzengel said:
To succesfully install the newest Versions of SuperSU you have to install it in systemless mode. If you flash the ZIP it will install it in /system mode, so you have to force the systemless install.
Before you flash the newest Beta SuperSU.zip go to the TWRP terminal and write:
echo SYSTEMLESS=true>>/data/.supersu
Then flash the ZIP.
SuperSU will be installed in systemless mode and your Phone will boot up fine.
Click to expand...
Click to collapse
I found this in another thread and it worked for me. all credit goes to Scherzengel
Hi!
EDIT: Never mind, problem solved. Sorry.
I have finally decided to root my G900F (6.0.1). I flashed TWRP through Odin without problems, booted to TWRP to make it permanent, booted normally to check that all is well. After that I made a full backup in TWRP and flashed the BETA-SuperSU-v2.49.zip. After that, my phone no longer boots (hangs on the Galaxy S5 screen with a blue indicator LED).
I can still boot to TWRP.
How can I fix my phone? Please help. What did I do wrong?
I did try wiping the cache partition but nothing else.
Hopefully the solution does not require a full wipe.
EDIT: I see what I did wrong. I have accidentally flashed an old SuperSU.
Can I use a backup I made with a TWRP?
EDIT2: Luckily the restore did work! Will try to flash a more recent SuperSU.
flash it again but with latest version of supersu. It will work
Spawnknight said:
flash it again but with latest version of supersu. It will work
Click to expand...
Click to collapse
Yup, it did work beautifully. Lucky for me that I remembered to make a backup before rooting.
I've decided to unlock bootloader, get a custom recovery and root my new LG G6 H870, so I've downloaded Melina TWRP v321 and Magisk v16.
Unlocking went well, then I downloaded drivers, unlocked debugging, "adb reboot bootloader" -> "fastboot flash recovery twrp.img" -> unplug usb -> boot into twrp by pressing volume down + power (with a tap) -> some weird screen about encryption popped up, but I clicked through -> and then I proceeded to install Magisk straight away, cause this guide said it'd not let TWRP stick if I didn't. After that I tried to boot into system and start the real fun. But it booted me back into TWRP. Again and again.
From there, I've tried Wipe -> Factory Reset, Wipe -> Advanced Wipe -> Repair File System for Data and System, Wipe -> Format Data, Advanced -> Fix Contents, but it all ends with twrp boot... I'm completly lost at this point. I've flashed/rooted a few phones before, but this one... it's a real nightmare.
I've also tried flashing a stock kdz (the filename is "H87011i_00_EEO_GB_OP_0108.kdz" for anyone wondering) through LGUP and redoing this stuff, but I end up with the same result. Please advise how to get it working.
Did you use uppercut when you flashed the kdz file? This is needed to successfully flash back to stock.
Seems it didn't work correctly.
basicreece said:
Did you use uppercut when you flashed the kdz file? This is needed to successfully flash back to stock.
Seems it didn't work correctly.
Click to expand...
Click to collapse
Yes, I did flash through Uppercut (v1).
Since this thread started I flashed it once again, but this time I tried installing official TWRP v321. There was no weird encryption screen, but there were a lot of msgs (when installing magisk or doing a backup, for example) about being unable to unmount /system because it was being used. I did manage to install Magisk though and boot up the phone, but then when I tried installing Xposed, the phone went into another weird loop... but this time, it would get stuck on LG screen and it'd start heating up very fast. It stops heating when I restart using volume down + power into recovery. But I'm once again stuck... this is incredibly annoying, are aall LG phones like that?
How you installing xposed?
Install it via magisk module.
I had no issue.
Unlocked BL
Flashed Zefie TWRP (most stable and backups work)
Flashed fulmics
Flashed Magisk
Wiped cache and dalvik.
Reboot.
Works fine and flashed this over 15 times now no issues ever.
basicreece said:
How you installing xposed?
Install it via magisk module.
I had no issue.
Unlocked BL
Flashed Zefie TWRP (most stable and backups work)
Flashed fulmics
Flashed Magisk
Wiped cache and dalvik.
Reboot.
Works fine and flashed this over 15 times now no issues ever.
Click to expand...
Click to collapse
Did you also have that weird encryption message when flashing Zefie TWRP? Could you be more specific about your way? As in, you wiped cache/dalvik only once or after every flash? Did you wipe anything else? And yeah, I've just downloaded Fulmics and I'm at the installation screen, but I clicked System Information and it says my Storage Size is 5417MB with 104MB free... it reads SDCard Size correctly though. Should I be worried?
Starting from fresh, out the box.
Unlocked bootloader.
Installed Zefie TWRP.
Then added fulmics zip to sdcard.
Flashed zip, followed on screen instructions.
Wiped dalvik and cache.
Rebooted.
Takes a few minutes.
Boots up and done.
Magisk was packed into fulmics when installed.
I do NOT touch xposed. Too many issues plus I need safetynet for Google pay.
Yeah, I pretty much flashed stock firmware back and then followed basicreece instructions, along with flashing Fulmics, but I've got the 'official' Twp (v321). And everything's working so far, but I didn't touch Xposed so far though since Fulmics had pretty much all I wanted from Xposed. Word of advice for future readers though: don't bother staying on stock, too many problems. Fulmics is basically stock, but with some really neat options, and a ton of bugs and problems less.