Develop Bugs

Rooted, No Gapps and can't access TWRP (V500)

So basically I flashed TWRP and it worked. Then, I installed pure AOSP ROM (forgot which one) without the gapps. And that's when I realize, I haven't really root the ROM and when I try to get to TWRP via buttons, it didnt work. It shows that secure booting error and cause : boot certification verify.
Can anyone please write the procedure to boot to TWRP again? Thanks in advance.
(Please note that I don't have root and GAPPS, so no flashify etc. Also, I have an unlocked bootloader)

Enable USB debugging and try ADB:
Code:
adb reboot recovery

Another way with the hardware keys:
http://forum.xda-developers.com/showthread.php?t=2712647
I just tried it and you can confirm the factory reset 3 times as described without having a real factory reset. Instead of a factory reset it just starts TWRP after a short while.

Please help - locked out of my device

I disabled encryption on my nexus 5x following this thread http://forum.xda-developers.com/nexus-5x/general/guide-how-to-install-custom-recovery-t3231143
I tried flashing a custom ROM, Chroma, and it did not work. After booting the ROM, it started showing numerous apps errors (saying the apps couldn't start). I reflashed my backed up stock ROM using TWRP, but now I can't get into the phone because my PIN isn't working (I know I'm typing it correctly, it just isn't working). I tried connecting my phone to my PC to use ADB to delete the password, but it says I'm unauthorized and will not let me delete anything.
I'm currently unable to do anything with my phone. Can someone please help me get this working? This is my only phone, and without it I'm unable to make any calls.

Have you tried booting into fastboot and flashing the stock image or trying to mount storage in twrp, adding a new rom and flashing?

bdivs11 said:
Have you tried booting into fastboot and flashing the stock image or trying to mount storage in twrp, adding a new rom and flashing?
Click to expand...
Click to collapse
I was able to download this ROM - http://forum.xda-developers.com/nex...-optimized-stock-rom-aroma-installer-t3285805 - and push it to the phone using ADB, after enabling USB debugging in the Chroma ROM. The phone is still telling me there "is an internal problem with my device, contact the manufacturer". Thankfully, I had another ROM on my internal storage - if I hadn't, I'm not sure how I would have been able to get into my phone, since my PIN had been lost and I couldn't enable USB debugging.
Have you ever seen the "there is an internal problem with your device, contact the manufacturer" error?

This is a problem on the 5x and 6p, where restoring backups doesn't restore the correct pin. It's recommended you simply remove phone lock security before making a backup. Here is what I found on fixing it:
srnoth said:
After restoring the Nandroid, open ADB and:
rm /data/system/locksettings.db
rm /data/system/*.key
This should remove the pattern/pin completely, you'll have to re-secure your phone after
Click to expand...
Click to collapse
Sent from my Nexus 5X using Tapatalk

I'm about ready to throw this phone away. I can't seem to flash anything on it without it going into a boot loop and forcing me to restore. I never had any problems flashing ROMs on my Galaxy Nexus.
I just tried flashing CM 13 on it and it went into a boot loop for some reason. I'm also getting a screen on boot up that says my device can't be checked for errors, please lock the bootloader. Any way to disable that error? And I'm still getting the "your device has internal problems" after my ROM boots.

Is it possible to have a rooted AND encrypted device?

I have tried several ROMs (Genesys, Imperial, RR, CM, stock) and can not seem to be able to encrypt my phone. I have done the
Code:
su
pkill -KILL daemonsu
exit
thing and the phone reboots but does not encrypt. I have even gone as far as installing the unrooted stock ROM and setting it up, then encrypting it, THEN rooting it. However, I get tons of FC's and can not enter in the password to decrypt the device.
Does anyone have any ideas on getting encryption working with a rooted device? And no, running pure unrooted stock is not an option.

It can be tricky. Very tricky. Try disabling/freezing SuperSU. Also try going into safemode, then try. I've done it before, it just took a ton of trying. Hold the power off button until you get to the menu. Then press and hold the off option. You should see an option for safe mode in a second or two.

Since SuperSU is a system app, I believe it still starts in SAFE MODE. Also, I couldn't find SuperSU in Titanium Backup even when "System" apps were checked so I couldn't freeze it.
I think I might have succeeded. Here's how I did it:
Download Genisys 3.8 & Genisys Theme 3.6
Reboot to recovery
Wipe system, data, cache, and dalvik (3 times)
Flash Genisys 3.8
Boot up and sign in
*OPTIONAL* Reboot to recovery and flash Genisys Theme 3.6 and reboot system
Open SuperSU and under Settings ---> Full Unroot (should reboot automatically, if not reboot manually)
Encrypt phone ---> Full encryption ---> set pin (DO NOT set boot up pin/password, only unlock pin/password/knock/pattern)
Verify encryption by going to Settings --> Security ---> Encrypt Phone (Should say "Encrypted")
*OPTIONAL* Encrypt SD Card
Reboot to recovery and flash UPDATE-SuperSU-v2.46.zip.
Reboot System
No guarantees, but this worked for me. Remember, DO NOT set the boot up pin because there are tons of FC's preventing you from entering your pin/password on this screen. Just set the lockscreen pin/password/knock/pattern.

Galaxy Note 8 (GT-N5110) PC Connection Problems - Boot Loop - SOLVED by ME

NO ONE?????
ODIN --> Flash Stock Recovery (AP) with NAND Erase All Option Checked (because it seemed to make sense) + Auto Reboot + F. Time Reset --> Reboots to Stock Recovery (did not work before) --> Reboot into Recovery --> Wipe Data/Cache and Dalvik just to be safe (this crashed it before) --> Reboot. THE END
TL/DR: I am currently stuck on recovery/update mode. Any attempt to wipe data or clear dalvik crashes it. any attempt to access data through TWRP crashes it. Flashing stock rom or custom rom does not help. Somethings wrong with /data? It thinks it has root from the CF Auto Root, but does not really? Something wrong with partitions? Should I wipe the nand with ODIN 3.10? Repartition? ugh ... Please help ...
I have searched the forums and found nothing that describes this issue precisely. I have also tried to apply various suggestions to repair, which, for the most part seems to have made it worse. I am hoping that people still look at this forum.
PC - Windows 7
Initially @4.2.2 ---> Touchwiz debloated stock ROM which I rooted. It worked for a couple years, but the device crashed frequently. I do not recall much about the installation, but believe that I used CWM/TWRP at the time. After installing the ROM, I ran triangle away (out of the box, it had 4.1.2, i recall)
I decided to upgrade to the most recent stock ROM (4.4.2). In order to do so, I used an easy installer I found else where on XDA. (http://forum.xda-developers.com/showthread.php?t=2773712 ---ODIN One Click exe). The device was not initially recognized, so I reinstalled the official driver package (said that they already existed, but I installed again anyway). Ran 1-click and it appeared to work.
Initially, the device booted (long startup) and seemed to function. It also preserved all data and programs (presumably did not touch the internal memory - 16 GB) and possibly root /data.
I then tried to root through most recent ODIN with CF auto root. This appeared to work and rebooted (again, showing the updating android apps screen before fully booting).
The only thing that i could find that had changed was the wallpaper (showed on lock screen but not on home screen). I could no longer find the image, so tried to go to /data/data to find it with root explorer equivalent. This is where it started to act weird.
NOTE: I did not clear anything (system cache, etc. at any point)<--a lie (see below)
It showed the root folder fine, but when I clicked on /data it took a while and could not access it. It either rebooted itself or I rebooted, but this time it was stuck in a boot logo loop. I entered download mode and flashed TWRP through ODIN. I set it to not reboot automatically so that the bootloader was not overwritten automatically (thus losing recovery). TWRP came up. The computer recognized it as a Media Device after I mounted USB storage. Just in case, I copied all of the important files from the internal SD Card to my computer. I then tried to go to the file explorer to copy the wall paper and it forced a reboot. At this point it was stuck on a logo screen boot loop again. I was able to enter Download mode and reflash TWRP. This allowed me to enter recovery again, however, now it would only boot directly into recovery (or Download mode if I did the button combo). The interesting thing was that it would reboot two or three times before successfully entering TWRP.
I believe I tried to reflash the stock ROM at this point, which might have worked but made no difference.
I was also having a lot of problems getting Windows to properly recognize the device. I had to reinstall the drivers a couple times. I tried Kies after the problems started and it tried to connect by failed. The diagnose connection did not work either. I was not able to get Kies to connect though I tried several times throughout the attempted repair
I downloaded a stock-rooted 4.4.2 ROM from here and tried to flash it. It failed.
I also tried to flash via Heimdall, but initially could not find any stock ROMs for Heimdall for the Galaxy 8. (The driver utility that is included helped to get the phone recognized by Windows sporadically).
I decided to switch over to CWM touch recovery, which I flashed via ODIN (I was having issues with TWRP again and also could not get windows to recognize the device as a media device when I mounted USB storage). This worked after a couple tries and I was able to enter CWM. I attempted to flash the stock ROM but it failed. Either at that point or when I tried to mount data it returned an error that device did not have root. Again, it would only boot into CWM (on its own) or Download mode (with key combo). At some point around here I cleared the cache and dalvik (error) after it returned an error saying insufficient space when trying to flash ROM.
I dissected the .exe from the autoflash used in the beginning (stock unrooted 4.4.2) and used the contents (system.img, cache.img, hidden.img, tz.img, recovery.img and one other I do not remember) in Heimdall to create a Heimdall package. At this point I figured out I did not need to create the package, but just specify the individual files. I flashed. It appeared to complete System.img successfully and then failed. Tried again with the same result.
Now when I rebooted, it would enter download mode with the Key combo, but otherwise it booted instantly to an error screen to the effect that a firmware installation had failed and to use the repair function in Kies to fix. Kies still did not recognize it.
At this point, I figured I should stop. Currently I can get to the download screen or the error screen. The computer recognizes it but intermittently fails to install driver. Zadig.exe sees it as Gadget Serial. Sometimes Windows just sees it as SAMSUNG_Android, in which case drivers fail. Once or twice I got it to recognize it as Samsung USB Composite Device, but Kies would still not work.
That's all i have for now. If more information is needed, let me know and I will update the post when I get home from work tonight (this is from memory).
Thank you
UPDATE: last night I went home and was able to get it back to the point where I could flash TWRP or CWM recovery. If I try to flash Stock Recovery, it fails. A minor problem is that I cannot turn it off - it just turns it self on again, so the battery keeps running down.

Question Stuck on "Pixel is starting"

Had to do a factory reset, and all was good. Using LSposed with Magisk and reinstalled several mondules. Upon reboot, the screen hangs at "Pixel is starting." So I rebooted into safe mode, knowing the Magisk modules would be disabled, but the same thing happens, even in safe mode. Booted again. I can access all my settings, and adb works fine. But I'm clueless as to what I should do, even with adb and settings access.
Will appreciate any help. Everything is backed up, I'm just trying to avoid the nuisance of having to factory reset again and all that entails.
Thanks.

You can try Official Google Android Flash Tool and uncheck the wipe data option (and don't force flash all partitions, either, which will also wipe), and don't forget to uncheck the option to re-lock the bootloader.
That official site has solved many weird issues where even manually flashing the full factory image hasn't solved the problem. Good luck, let us know if that's what you do and how it goes.

my old go-to for boot issues was last_kmsg. I recentlky found abou about boot-chart, which logs what happens during boot, and may log an error for you. You will have to run this in recovery if yopu are in a non-booting state
To enable it:
Code:
mkdir -p /data/bootchart;
touch /data/bootchart/enabled;
try a reboot, which fails. Reboot to recovery and retrieve the logs
init/grab-bootchart.sh - platform/system/core - Git at Google
I havent had to use it "in anger" yet, but it will be my tool of choice.