Hey,
I want to root my phone and install Lineage OS. I failed once before during the TWRP install and ended up having to get another phone. Previous phone would no longer power on or even go into fastboot. Not too sure why all i know is during the installation process of twrp it failed a bunch of processes and once rebooted would not boot. I assume my last try failed due to not being root and not having either magisk or superuser? Is there a fool proof noob friendly guide to doing this? Thanks in advanced.
Related
Hi there,
Proud owner of a new Pixel XL. Unlocked version. Tried rooting last night (i've rooted all devices i've owned and am not new to this). Followed the instructions to a "t". The device won't get past the white screen and dots leapfrogging each other. Now when going back to fastboot, device isn't recognised by ADB Fastboot etc...
Please help!!!!
My guide should be able to help you get back to the OS and then install root.
Keep in mind you may lose data if you don't remove the -w from the script mentioned in the guide.
http://forum.xda-developers.com/pixel-xl/how-to/info-how-restored-to-stock-soft-t3494478
Did you unlock bootloader?
Then immediately try rooting?
That is one cause for bouncing dots.
You should: flash factory image, then boot into device before any flashing. Setup device until you are at the home screen and OS settled. Use a pattern or pin security. That is needed to make recovery work properly. You need to decrypt at recovery boot. No ask for pin? Then power off and boot TWRP again.
Follow directions in TWRP and SuperSU threads to a Capital "T"...
Versions:
Latest "Q" firmware
Boot TWRP RC1 img, then flash zip installer
Use SuperSU 2.79 SR1.
You'll have no bootloop. I found first rooted boot to take just a few minutes.
Just in case: update SDK platform tools if you haven't cos that screws people up for days too.
Thanks mate. But i get to step 9 and nothing happens. My device is no longer recognised
thanks mate, but the problem is that now the device is simply not recognised by my computer. I can't flash anything
I should clarify.
SDK is 100% up to date.
I am trying on both Windows 10 and Mac.
Device drivers worked fine prior to trying to root.
I'm really worried that i might have just bricked a $1.4k(aud) device
I unlocked my bootloader and got a bootloop when I tried to fastboot to root. Would not recognize the device either. I redownloaded SU 3 as suggested in the third post and it worked. Good Luck.
I used the fastboot to root method and did not install TWRP.
http://forum.xda-developers.com/pixel-xl/help/bootloop-t3498140
Thanks, Mike01680. trying now
When i go into sideload i can see the device listed on adb devices!
Okay. Booted into recovery, found my firmware for NMF26O. Downloaded and ADB Sideloaded it can once again boot. thanks for all of your help!!!
SOLVED!
So, after just giving up and moving on to another project of trying to flash the ARTX Kernel which didn't work (I'll update this if I find out why it's not working; my phone restarts when im flashing the zip and "2013-2015 [somename ] amurlle.com" pops up in log.) so I researched and found a zip called MrBump.zip which bumps your boot image to get rid of the secure boot check.
How to
Flash SuperSu v2.82.zip via TWRP and then flash MrBump.zip, the phone will reboot after flashing MrBump and then another time for finishing the SuperSu installation.
History
\\
So, I have recently updated from Cyanogenmod 13 to Lineage OS 14.1 as it's faster, pretty, and Xposed was recently released for Nougat.
Installing Lineage wasn't a problem nor Gapps or the su add on package from Lineage which unlocks the OS's own su management service.
I wanted to use SuperSu as it pretty, customization, and better privilege management compared to the option lagging 'Privacy Guard' Lineage uses.
So, I flashed the SuperSu v2.82 zip which gave me a "Secure Boot Error" when rebooting into the system. No partitions seemed to be corrupted or damaged but I assumed
it had to do with the boot.img file as I saw supersu patch the boot image for some stuff I don't know. I decided to research and get my team of arduino super AI's to find
something of an answer of how to fix my problem, stumbling upon an article on XDA from chainfire of a boot image signer. I used Cywgin to create an rsa key and signed my boot image
then figuring out I could use the "BootSigner.zip" to sign the boot image without me creating a rsa key, flashing the zip nothing changed just some other error of where it couldn't read
boot image or the boot image was misdirecting to the system. I then tried fastbooting the signed boot image I made, it didn't work giving me some other ****ty error of mutiny.
I then fastbooted the orginal unsigned boot image I took from my ROM which worked but when booting into the OS SuperSu was still not the active su manager.
I then gave up and am now writing this post in a last option of getting SuperSu on my phone.
I have tried SuperSu 2.78 and kingoroot from the PC hoping that I could then use SuperSuMe
//
Details of my device
\\
LG G3 D855
ARM
Lineage OS 14.1 (20170724)
Gapps 7.1 Micro (20170728)
TWRP 3.1.1-0
//
1 second after turning on the phone the error pops up (the LG logo is visible when the log is onscreen):
ERROR : boot certification verify
[640] --------------------------------------------------
[640]
[640] Secure boot Error!
[640] Cause: boot certification verify
[640]
[640] ---------------------------------------------------
2 seconds later the screen blanks and the LED on my phone blinks blue and red at half second intervals.
Any help would be appreciated, if you need any specifics of my device or screenshots just ask (I can replicate my problems and steps iv'e done if you need me to.)
Eureka!
I did the exact same thing and all the guides that I found assumed that you still had access to the system or had already wiped out download mode. There is a lot of advice out there that really just doesn't work. Anyway, I gave up and decided to do a wipe with suprising results.
boot to stock recovery by holding power+volume down
perform factory reset
phone reboots to TWRP - WHY?!?! I have no idea, but it worked
reinstall your latest lineage image from /data/data/org.lineageos.updater/app_updates/
wipe davlik/cache + reboot
profit!
I don't know why this worked and I stumbled upon this by accident.
Mileage may vary, so please share your results.
XtatX said:
I did the exact same thing and all the guides that I found assumed that you still had access to the system or had already wiped out download mode. There is a lot of advice out there that really just doesn't work. Anyway, I gave up and decided to do a wipe with suprising results.
boot to stock recovery by holding power+volume down
perform factory reset
phone reboots to TWRP - WHY?!?! I have no idea, but it worked
reinstall your latest lineage image from /data/data/org.lineageos.updater/app_updates/
wipe davlik/cache + reboot
profit!
I don't know why this worked and I stumbled upon this by accident.
Mileage may vary, so please share your results.
Click to expand...
Click to collapse
What?
You must've flashed TWRP before, and I don't understand what you mean here. Did you brick your phone trying to flash SuperSu too?
But i'm glad it worked out for you
Bump!
Saterlite said:
What?
You must've flashed TWRP before, and I don't understand what you mean here. Did you brick your phone trying to flash SuperSu too?
But i'm glad it worked out for you
Click to expand...
Click to collapse
Yeah, I had TWRP on it before and got to that point by trying to flash SuperSU on an already installed copy of Lineage. I was really trying to revert to stock and start over when TWRP came up.
So, long story short, I followed this tutorial: www . htcmania. com/showthread.php?t=1024045 (remove the spaces in w.h and .com) and it didn't go very well.
I flashed TWRP and SuperSU as told, using both download links (TWRP 2.8.7 & SuperSU 2.46), and my phone got stuck in a bootloop at LG bootloader unlocked logo. I recovered my phone by using LG Bridge and after that, when i tried to enter TWRP using the phone keys, it resulted in a factory data reset (no TWRP after recovery, didn't know that). I then followed the exact same steps but using what I thought was the lastest SuperSU archive (SR5-SuperSU-v2.82), flashed the archive and when finished, TWRP asked me to flash it again (so I did), then rebooted, passed LG bootloader unlocked logo, got into LG animation and... Bootloop again, so I recovered again with LG Bridge but I din't attempted to enter TWRP because this time i knew it wouldn't work and I ended it there, reinstalling all apps and configuring my phone as I had it before my unsuccessfull attempt. I continued using my phone as usual but sometimes, when I enter Pokemon Go, it says that it couldn't log in and that my phone's OS is not supported. As I said, the app does this sometimes whenever it wants, so I researched a bit and turns out it doesn't work with rooted android devices (I didn't know that). I knew my root attempt failed so I downloaded and app called Root Checker and checked: Root status-Not rooted; SafetyNet Status-Failed. I don't know what should I do know, last time I rooted my phone was a Sony Xperia XL and it wasn't so tricky.
I asked for advice in the forum and got no answer, so here I am, hoping for a solution. What I want is to have a permanent custom recovery, a rooted device and to have SafetyNet status passed. Any ideas, hints or whatever? Please, help
Hello,
I have been searching posts all day about this but they seem old and I've got none to work.
After following the guide from magiskroot to root my OP5T, system won't boot, it just loops to TWRP.
I have downloaded the last version of TWRP available for OP5T and the last Magisk Su.
I can go to Bootloader and TWRP.
Trying to install OxygenOS 9.0.4 shows an error.
The device was previously on OxygenOS Pie.
Does anybody have an idea ?
Edit: Well, after hard-bricking the device I succeed to reset it with the Unbrick tool found on XDA.
Problem solved I guess
Hello,
I'm quite new to custom roms so excuse any unnecessary questions.
I tried to install twrp via adb and loaded it to a and b of the booting slots. After this it says: "your device is corrupt. It cant be trust and will not boot". As it is no recognized by adb any more, I dont know how to access it to load lineage recovery again. In the end I would be ok with wiping it completely, but I struggle to make this work. So my questions:
is it even possible to load lineage recovery and hope that theres no data loss?
and if not, what is the best way to make a full wipe?
best regards and thanks in advance,
titatuto