Database Users

[SOLVED] Suddenly G2 boots only into recovery mode (loop)

Sometime last night, my AT&T G2 (D800) decided to go from being powered on and idling, to going into TWRP recovery mode. All by itself. I saw this, unplugged it from USB, and tried to reboot into system mode. But it simply won't do anything except boot into recovery. Powering off, trying to get to the bootloader, none of that works.
This is not a custom ROM, it's 4.2.2 stock from LG. I only rooted the phone, which was several weeks ago, and haven't had any problems, aside from TWRP not wanting to back up anything. I've been using Android since the original TMO G1 with JesusFreke's ROM, so I have a pretty good idea of what I'm doing, hopefully.
The only recent changes I've made are:
I updated busybox about 3 days ago (but have rebooted fine since)
I grabbed several legit apps from the market last night
Last night I also DL'ed, but did not apply, a ~50MB OTA update that has been pending. I don't think that would install without explicit permission anyway, which I didn't give it?
This phone was encrypted from the start. Maybe that;'s what prevents TWRP backups,, but right now I'm seeing TWRP errors/logs saying something like "Unable to mount \data". And yet I can browse to other folders, and see filenames in \etc for example. However, I don't see any files at all in \boot.
Since this phone has no external memory, and it's customized and has numerous configured apps, I really really don't want to have to wipe it. Although at this point, that may not even fix the problem? Even if it did, since I haven't been able to make backup images, it would be a Bad Thing™ either way. (Yes, I do have a secondary plan with Titanium, with backups going to cloud storage, but these are tedious and now a few weeks old. And wouldn't restore the ROM & system en masse.)
Please help.

Solved?
I'm not sure what caused this to occur, but I found somewhat of a solution after digging deep into my Google-fu.
I followed the instructions in this XDA thread and it actually worked. I didn't have adb access, but I was able to use dd successfully. It allowed me to boot into the device, unencrypt it, then arrive at the lock screen.
However, when I put in the lock code, it went apesh!t and played multiple notification sounds, with a blue circular wait symbol. It also flashed the LED from green to blue, as it normally only does during boot. Once I pressed the power button, I was back back into TWRP.
So then I followed Step 2 again, and once in the phone, I used terminal to run the dd command from inside the OS. This might be what it ultimately needs, because the prior attempt in TWRP had an error to the effect of "no space left on device".
I can't call it Solved yet, but it looks good to at least be able to get in and use the phone. I'm backing up with Titanium before I do anything else and will reboot and test its permanency later.

I'm gonna close this thread now that I think I have a handle on what is going on. The fix does survive a reboot, so I believe it's possible to repair the issue permanently per the instructions above. I also ran the phone for 3 hours with heavy app usage and no problems.
I believe what may have happened is my OTA decided to override my choice to NOT update the ROM, as some have reported in this Reddit thread. There's a lot of good info in that one, including how to stop getting nagged by turning the OTA notifications off, or to freeze it entirely with Titanium Backup if rooted.
Anyway, what apparently happens is that when the OTA/upgrade goes to reboot, and encounters a custom recovery, it gets confused... when you try to power cycle or reboot again, it sees the stock recovery still hasn't run whatever it wanted, so it starts recovery again Lather, rinse, repeat.
Fun times.

[Q] [SOLVED] Adventures in CM11, still can't connect to T-Mobile USA.

Hello,
I have a MB525 that I purchased retail in the United States so it was never locked to any carrier. Currently I'm a T-Mobile customer and have no interest in changing that. I have to say I love this phone, mainly because it seems indestructible. Even years later the battery life is still good, but the stock 2.2.2 Froyo has become something of a problem because many of the Apps I would like to use have started requiring newer versions of Android.
I can't stay in the past forever, but I'm not quite ready to give up on this device so I started looking around at my options, and would you believe I found lots of other people who have this device and have worked very hard to produce updated Android OSes for it, and who have reported reasonably good success updating the device. I figured, Its already out of warranty, so I can't void a warranty I don't have. I also figured I'm a reasonably intelligent individual and have enough experience with Unix like operating systems that even if I get in trouble, I'll be able to ask the right questions to get out of trouble. Guess what point I have gotten to?
I started following the guide wikiDOTcyanogenmodDOTorg/w/Install_CM_for_jordan The Framaroot Gimli exploit worked great. I installed bootmenu 6.1 and Clockwork Mod Recovery. Fantastic. At this point, I was able to enter CMR and backup my mostly still factory ROM. If I understand correctly this is a nandroid backup. I copied that backup off of my SD Card to my PC. From this point I felt reasonably confident I could try things and in a worst case scenario restore to this backup.
Now I happen to have a stock ROM that seems to be a bit rare online, Blur_Version.34.4.806.MB525.Latam.en.01, so I figured at this point I'd do a service and create a backup using CWM after having done a factory reset. So I booted into the stock recovery, did a factory reset, restarted, and the OS was in a like new state. Perfect. Rebooted into CWM, and made a second backup of the factory reset state. I copied this off the SD Card to the PC. Now I figured I was ready for real fun.
I figured, I might as well put the most recent Android version I could find that people were reporting success with. This appeared to be @quarkx Kitkat build. The thread is almost a year old and has 500+ replies and so I guessed that most of the major kinks would have been worked out by now. I followed the directions on quarx2kDOTru and installed cm-11-20141015-NIGHTLY-mb52x.zip from Quarx2k.ru, and low and behold it worked. CM11 booted and everything looked great. WiFi worked. Gapps worked. Play store started installing my apps.
There was one small problem. The phone refused to connect to T-Mobile at all. So I did the reasonable thing. I searched and learned about base band switching, and consulted T-Mobile on what would be the correct APN settings. Occasionally it would connect to AT&T for emergency calling, but it never connected to T-Mobile no matter what I did. From my home I was normally getting excellent signal on the stock ROM, so I am reasonably certain that the actual signal in the area was not the problem, and that this had to be some kind of configuration or software issue. A wiser person probably would have gotten on the forum and asked for help, but wisdom be damned, I wanted to do it for myself.
So more research and at some point I thought, Well, I'll go back to the Stock ROM so the phone will be usable again, and I'll take another crack at CM11 again later. It was at this point that I realized that CMR had been replaced with Team Win Recovery Project. This recovery looked to be more feature rich and easier to use, so I accepted that. I backed up my CM11 install. then went to restore my original backup. Well you might have guessed by now that TWRP and CMR don't use exactly the same backup formats. I saw no obvious way to get back to my backup and couldn't find information that would allow reinstalling CMR. This was the first warning signal I foolishly ignored.
At this point I started looking around for slightly earlier builds of CM11 that might not have had the the problem connecting to T-Mobile. Here is where things get fuzzy about how things got into this state, since the work was spread over two days at this point. Somehow between all the flashing backing up and restoring, the device got to a state where the OS never actually finished could do here is yank the battery and reboot into TFRP.
At this point, attempting to restore would just result in the messages 'E: Unable to mount '/cache' and 'E: Unable to mount '/data' in the terminal. So After searching around I learned that I probably needed to format /cache and /data because somehow they were broken. Terminal commands, I can handle this. I start reading up and find the correct command and parameters for the format, and I type into the terminal inside TWRP and low any behold format can't be found. I start looking around the directories in my file system from inside TWRP and I've got a complete directoty structure, but no files in any directories other than on /sdcard. Well fuuuu.
Not sure what made me even try, but copying any file from my sdcard into /data somehow put /data into a state where a TWRP restore would work. So at this point I was able to restore the CM11 backup, and my phone now boots into CM11, 11-20141007-NIGHTLY-mb526. But.... the cellular network still doesn't work.
But now I am wiser and I am back to the point where a wiser person would have asked for help. So... Help?
Is 11-20141007-Nightly-mb526 the best rom an appropriate rom for my device? I'm guessing I missed something because other discussions on this forum mention newer builds, and also, my device is definitely a 525 not a 526.
Is my baseband version EPU93_U_00.60.03 right? The baseband selector allows me to pick from three T-Mobile settings: 3.4.2.-107-4, 3.4.2.-107-9, and 6.xx.0, none of which seems to allow me to connect to the cell network.
Thanks in advance for any assistance offered.
Sorry for the long potato.

Here is what I did to fix my problem.
I started with the original backup of my stock rom, and I used the unyaffs.exe from this thread: http://forum.xda-developers.com/showthread.php?t=1199416 to convert my CMR backup into individual files. I then went into those files, and found \system\etc\motorola\bp_nvm_default\ and pulled out the original radio firmware from my device. From there I used advice from several pages to create my own update.zip, copied it to my SD card and I booted into TWRP and installed the zip there. Reboot and Voila, It connected right at startup to T-Mobile with the normal speeds I get from my home.
Bonus, I attached my zip in case anyone else comes across this and needs it.
My Device has an FCC ID of IHDP56LC1 if that helps anyone match their hardware.

Nexus 6P stopped booting, nothing I do is now working. PLEASE HELP ME.

At this point I have completely run out of options. I AM CALLING UPON THE XDA COMMUNITY TO PLEASE HELP ME. Little bit of background info, nexus 6p was rooted and modified through xposed. Had some modules installed, mostly quality of life and visual/theme modules, as well as the latest version of SuperSU.
These past few days my Nexus 6P has completely stopped responding at times. Extremely laggy and could not do **** with it, systemui kept restarting over and over and over again for no reason. Had to keep force rebooting (holding down the power button for 10 seconds) multiple times over and over again, to the point where it suddenly stopped booting into the OS, it just kept giving me the boot animation loop, i could only access the TWRP recovery i had installed. Before all of this **** went down, I had created a TWRP backup because it would be my safety net if i could somehow miraculously get it to work. Now i have a backup of my TWRP BACKUP FILE on my desktop.
I have wiped caches more times than i can count, have tried factory restoring and formatted the data, and tried flashing the stock google image (the same one that i originally flashed at the time that I got the phone when i started to root) as well as flashed the old TWRP version i had, as well as the current latest version of TWRP, and then transferred the backup i made back onto the phone's internal storage. Tried restoring the old backup from TWRP, and each time it restores, it just reboots without reaching 100% and once it reboots, it still gives me a bootloop, this time, no boot animation, it just gets stuck at the Google text with a little "unlocked" logo at the bottom. I have completely run out of options, and have A LOT of EXTREMELY IMPORTANT information i have saved on the phone.
I will say it again. I am EXTREMELY DESPERATE to get my data back, to the point where i am even willing to offer a cash reward for any help to get my phone working back to the way it used to, or even at least to extract the information through the backup, if at all possible.
Additional information about the files and images I used:
angler-mdb08k is the name of the google image i had back when i had the phone and have flashed again
twrp-2.8.7.2-angler is the TWRP version i had back when i had the phone originally at the time
I had flashed and followed guides online through adb method.

[Nexus6P][TWRP][SuperSu] Dubts on Updating and backups

So, I am new to the community and just recently created an account to make a new topic because something happened:
I have a N6P and I was disappointed with the whole "Pixel exclusives" thing, so I decided to root and flash some of the new features into the phone. Everything I wanted I could find in the threads of this forum and it was nice and easy. I did get to a nice point where I had all the features I wanted, and then, I saw that there was a beta update for the new android version 7.1.1. From there I realized how little I know about the android system, and for that reason I want to ask a few questions. First, I'll describe the steps I took and the result i got:
1 - Backed Up data with TWRP (Boot, System, System Image, Vendor, Recovery)
2 - Updated to 7.1.1 through the phone settings
3 - Reboot
4 - Checked everything (all working fine until here), I had lost my root and TWRP because the new system took place.
5 - Reflashed TWRP
6 - Patched again the Pixel Launcher and SuperSu through TWRP
7 - Reboot
From that time on, the phone did boot, but the default launcher didn't start and a system app presented errors: Everythime I closed the error box, if popped again, blocking me from doing anything.
After the inicial problem, I promptly went to TWRP and tried to restore the backup I made. Now the phone became unable to start the OS, it runs the boot animation forever and nothing happens.
Now I am downloading a Stock ROM to flash through fastboot and do everything again.
Now to the questions:
1 - What did I do wrong? Why didn't the Backup work? What should I do differently from now on to have a reliable restore point of my device(just in case I screw up again)
2 - What can I do (besides flashing stock room) in order to recover my system? It is annoying to have to start from zero again thinking i had a backup made just to prevent that.
3 - Where can I learn more about the Android filesystem and OS architecture? (I am a developer, but I'm also lazy as ****, so i'd appreciate "explain like i'm 5" links)
Thank you all.

7.0 Update Crashed my Device. Custom Roms won't take. Stock Rom crashes, too

I received an update push from Motorolla that installed Nougat. After that, my phone would crash every 3-10 minutes. I did all the troubleshooting I could find online. I contacted support and they wanted me to spend $150 to get it "refurbished." Of course, it sure seems like a software problem, so that wouldn't help me anyways...
I turned to custom. After rooting, installing SuperSU and TWRP, I couldn't get several versions of AICP or Lineage to ever boot (stuck on loading screens). I also tried all the advice from this thread.
I went back and installed the stock Rom using f2fs , and the phone would get to the "hello moto" part of the boot up, then crash and reboot. I tried again using EXT4, and it worked, but just like before I ever begun, my phone was crashing every 3-10 minutes. However, the first crash wasn't until after I made a phone call, and my phone had been crash free for about 20 minutes before that call.
I'm a I.T. guy, but I'm not a "phone" guy. But it seems to me that there must be some other software that was modified during the update that is causing the problems that isn't part of ROMs. Something in the Kernal, or a driver folder or something?
Also, is there a way to get crash reports? So maybe if I at least go back to the default ROM and wait for it to crash, I have some info to work with?
Any help is greatly appreciated, thanks!

Flash full stock 6.0x for your model/region.
Important:
Without bootloader, gpt. Don't try locking BL.
Links you can find in my signature.
Try normal boot and after success any custom.
You cannot allow any ota update after it.
Some customs are only for Nougat modem/radio - don't flash it. @Kaivian

Ok, I got most of that, except I don't know what gpt refers to and am not getting any hits on search.

My signature - flashing stock - without bootloader & gpt.

So, I installed a 6.0 stock ROM and got tons of errors. I tried a 2nd time, still got tons of errors. Needless to say, stock 6.0 didn't boot. I decided, "The heck with it" and tried installing Lineage 7.1 again... and it worked! It finally booted up entirely. However, now I get a "Sim card missing" notification. Can I just reinstall part of something... like the modem? so I can keep this "working" lineage boot? Or am I starting over yet again?

Repeat
from
fastboot flash modem ...
to
...fsg.

dzidexx said:
Repeat
from
fastboot flash modem ...
to
...fsg.
Click to expand...
Click to collapse
This caused it to not boot.
I went back to 6.0 and turned off auto-updates. I'll try again sometime when I have time. I did like the custom rom a lot, just couldn't use it as a phone xD