Develop Bugs

[Q] Assistance in recovering

Hi, I have foolishly (possibly?) wiped Android off of my OneX
I was attempting to apply the Tegra tweak and well things went downhill.
I successfully unlocked the bootloader from HTCdev.
I proceeded to apply Interim ClockworkMod to gain root access
This is where things started to go wrong. Any new reboot would only take me to Clockworkmod screen.
I tried http://forum.xda-developers.com/showthread.php?t=1599748
clear cache, davik cache... relocking the bootloader - This results in the device constantly rebooting.
I attempted to apply the RUU ROM's ( from: http://forum.xda-developers.com/showthread.php?t=1543604)
From within ClockworkMod I was then able to:
adb push One_X_1.26.401.2_odexed.zip /sdcard/
Once there I used ClockworkMod to apply an update zip (which I was hoping was the Stock ROM).
A reboot just brought me back to Clockwork.
I then locked the bootloader ( fastboot oem lock. ) hoping it would then proceed to boot as expected.
It didn't just going to HBOOT or an attempted recovery (isometric view of a phone with a green arrowed circle -> RED triangle).
Please someone help, starting to panic a bit. The fact I can upload, the fact that there is some basic interactions should imply this is fixable, but how?

The boot to recovery sounds like you have the same problem that I had.
Perhaps you followed the same incorrect instructions as I did. See here for a solution.

mwhincup said:
The boot to recovery sounds like you have the same problem that I had.
Perhaps you followed the same incorrect instructions as I did. See here for a solution.
Click to expand...
Click to collapse
This may help.
with the locked bootloader you will only be able to run a proper ruu so before even attempting the instruction above unlock your bootloader again and proceed from there.
I might start working on some core .IMG files that can be flashed through fastboot to get you going again tomorrow
Sent from my HTC One X using XDA

THANKS!!!
booted back to the lovely ICS desktop
It looks like I did end up flashing RUU since none of the Vodafone branding is present (and it is actually better!)
No idea what went wrong but probably flashed over the boot as hinted at in the other thread.
The provided img files assisted. just need to get this Tegra thing working (not showing up as a running/registered process but thats another story)
Thanks all

[Q] Help Unrooting!

Please don't refer me to any more threads or forums........
I'm sure this has been done and done and talked about but I've been reading the **** out of forums and comments for a few hours now and trying to unroot my Sprint LG G2.
I had it running stock like a champ. rooted it. worked great. then I was attempting to flash lollipop and it required a recovery update (No Problem) I downloaded the correct files and bam! it says your phone is not rooted this requires a root (or something like that) I was already rooted SuperSU installed and root checker said I was fine. so what the hell I swipe to root while inside recovery and it goes to some black screen with tiny text saying fastboot: processing commands and won't leave the screen. I tried booting into recovery and same thing happens. Tried to reboot normal and I'm stuck on the LG logo with my led flashing between blue and green slowly. I CAN boot into download mode and I'm following this
http://pastebin.com/WTm1xFXz
and this
http://forum.xda-developers.com/showthread.php?t=2687929
to unbrick but having this error "Failed PreviousLoad()
Did I not get the right .dll file? I doubt it cause I only saw one...or is it the wrong .tot file? there was 3 or so
http://downloads.codefi.re/autoprime/LG/LG_G2/LS980/Stock_Firmware
Please help!
When i'm in download mode the phone does say I am rooted. is there a way to just re-flash recovery and restore from my backups I did before all this? if I have to wipe this thing clean and start over I don't really mind I just need to get my phone back haha this is the first time this has ever happened to me and I consider myself tech savvy so idk what I did here (except re rooting in recovery like an idiot) thanks so much!

First question, is the download mode you see with a small status bar or the big one?
If you have the big one, download mode should work. The f flash software will verify the tot file. If that goes through you should be golden.
When it asked you in TWRP to root, that is a message telling you system or ROM file did not take.
If you want cm12, use zv8 tot. Root, auto-rec, update TWRP with blastgator bumped TWRP 2.5.1. Flash cm ROM or aosp, then gapps. And go

help please bricked op3

i screwed up i unlocked my bootloader and installed twrp that worked fine reboted into android relocked my bootloader (stupid i know now) phone didnt reboot so i ran the fastboot reboot command now system wont boot stuck on the your password was correct but my data is corrupt screen and when i go to rest the phone it wont boot into recovery just a yellow line flashes and the led comes on white im pretty sure my recovery has been deleted and also running anything in fastboot gives some error about my bootloader being locked

fixed it using the mega unbrick guide

future reference before posting research and try to fix yourself and if issues still persist you can ask specific questions. This is xda there is a thread for whatever question you want to ask

Lineage OS 7.1.2 SuperSu Secure Boot Error [SOLVED]

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.

"Your device is corrupted and cannot be trusted" error. Nothing happens when connecting to PC

Please need urgent help. I had unlocked bootloader. While trying to update Magisk, my phone rebooted and got stuck on fastboot loop. Then while trying to flash TWRP using fastboot this "Your device is corrupted and cannot be trusted" error occured. I can't go into recovery, it just loops into this message. And my PC can't recognise the phone now at all. Please I need help. I have been trying to resolve this issue for hours now.

This is for Google Pixel 2 XL.

SonyXperiaSP said:
Please need urgent help. I had unlocked bootloader. While trying to update Magisk, my phone rebooted and got stuck on fastboot loop. Then while trying to flash TWRP using fastboot this "Your device is corrupted and cannot be trusted" error occured. I can't go into recovery, it just loops into this message. And my PC can't recognise the phone now at all. Please I need help. I have been trying to resolve this issue for hours now.
Click to expand...
Click to collapse
As long as you can get into the bootloader you're not dead in the water. Download the last factory image - NOT OTA image - from Google and flash it while in bootloader mode using ADB and Fastboot. That will return your device to its factory state. From there you can boot - NOT install - TWRP and install a custom ROM as well as root.

Strephon Alkhalikoi said:
As long as you can get into the bootloader you're not dead in the water. Download the last factory image - NOT OTA image - from Google and flash it while in bootloader mode using ADB and Fastboot. That will return your device to its factory state. From there you can boot - NOT install - TWRP and install a custom ROM as well as root.
Click to expand...
Click to collapse
First of all thank you for the reply. I don't know but I left the phone alone for couple of hours and right before seeing your post got into bootloader by pressing volume down and power key. Tried to flash TWRP and as soon as it flashed I got the exact same error like last time. I will now be following your method and install factory image. "NOT install - TWRP and Install a custom ROM", so I will not be installing TWRP this time.
I will post updates on what goes and hopefully will be able to flash the factory image without errors.

Thank you very much for the help Strephon. Really, really appreciate it. I am now able to boot into the OS and hopefully installing custom rom or rooting afterwards won't be an issue, Again, thank you very much.