Database Users

[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.

Might have soft-bricked my Exy S7 Edge for good. Need help/confirmation.

So... let's get this straight, i am an idiot. I played with fire and lost to it. I did some things i should not have done with my basic Android/root experience.
Here's what happened: Rooted my Exy S7 Edge today and everything went fine. I had hopes of somehow fixing SD-Card write permissions, which annoy the hell out of me in Marshmallow, but nothing really worked. I then stumbled upon a tutorial to modify the platform.xml located in /system/etc/permissions/ adding permissions. I made a backup of the file and started adding things suggested by the tutorial, restarting my phone several times. Nothing changed anything about the SD-Card permissions, so i gave up, didn't go back to the backed up platform.xml though.
Shortly after, i wanted to copy some files onto my device via usb and my Windows machine suddenly saw no files on the device. Nothing in the "phone" directory, and nothing in the "card" directory. I managed to copy the files via the FX file explorer web access feature and went on to connect a bluetooth device to my phone. I wasn't able to turn bluetooth on.
Rebooted the device and still had the exact same issue with bluetooth. I fired up FX with root access and went back to the backed up platform.xml, because it started dawning to me that something went majorly wrong there. I deleted the modified one, renamed the backup back to platform.xml and rebooted.
After the reboot, nothing worked anymore. I was able to get past the lockscreen and see the launcher (Apex Launcher) but i kept getting crash popups from basically every single app and service on the device. I wasnt able to run a single app, except for the "my files" app from samsung which showed nothing on the device and, and nothing on the sd card and the settings app. I then factory resetted the device in recovery mode (data wipe; cache wipe), because factory resetting it from settings just gave me a samsung service crash popup.
Rebooted the device and still have the exact same problems. It gives me the samsung startup wizard, but i cant get past accepting the license, because as soon as i agree, i get multiple crash popups and it goes back to the license page.
I assume this must mean that i somehow disabled read (and/or write?) accesss to pretty much every partition on the phone, is that right? Is there anything i can do, or have i softbricked the device for good? I don't really know a lot about using adb, and also enabling usb debug mode in the settings is pretty much impossible right now.
I am very thankful for any help saving my baby.

I would try downloading a stock image for your specific decice and flashing through odin.

I soft bricked my phone trying to flash the UK firmware. I fixed it with Kies, under Tools > Firmware Upgrade. It gave me a warning but I ignored it.

Just flash a new rom, u'd be fine !

Phew, thanks a lot guys Just reflashing stock worked perfectly fine. Didn't think it would be that simple.

Point to note - soft brick is usually something you can come back from providing you can get in to download and recovery modes. It also implies a device won't boot to the OS at all. So saying you ate soft brick permanently would imply a hard brick.
Hard brick is a non bootable device with no access to download our recovery mode without the use of a jig.

Normal (rooted) phone, went full retard all of a sudden. Need help extracting data

Hello all,
I have a Nexus 6P, stock, rooted, with Xposed installed. The phone is completely functional for the better part of its life time since I bought it at release -probably first or second batch- (except for random reboots once daily on average, deemed by my investigation and exhausting all options to be a hardware issue or Xposed related).
Today, out of nowhere, the phone randomly rebooted itself and surprisingly it launched the "Android is starting..." dialogue which, if I'm not mistaken, optimize apps for ART. The battery was at 19% before it randomly rebooted, so when it started that optimize apps it went down to 0 (I assume) and it turned off. The charger wasn't connected correctly so that happened. Now the phone keeps restarting itself up to before it gives me the boot up decryption phase of the Data partition and reboots again. I assumed it can't decrypt Data for some reason, so I launched TWRP recovery to try and decrypt data and take a backup copy of my Titanium Backup folder on storage... Unfortunately, TWRP reports "failed to decrypt data" even though I'm 100% positive that the pattern is correct because I'm literally inputting it almost 10-20 times a day for the past two years...
Note: there seems to be a red blinking LED in the top left corner of the the phone. I never even knew this existed.
WHAT I WILL DO
I'll reflash everything system-wise.. I'm ok with that. I'll reflash the factory images, root it, install Xposed, no problem.
WHAT I NEED HELP WITH
I need to extract some folders from my phone storage, namely the Titanium Backup folder. I know the pattern protection of the encryption.
How do I go about doing this?
UPDATE:
Help is urgently needed now indeed: The phone doesn't even turn on to bootloader mode anymore now. It was able to, just half an hour ago. Now all I see it the red blinking LED.
UPDATE2: https://support.google.com/nexus/troubleshooter/3337561?hl=en-GB#ts=3337942
I'll try in 30 minutes.
Meanwhile, please help me with my original problem; extracting data.
I was thinking, if I boot into bootloader mode, can I use adb to pull any folder? If so, will that work in my case with decryption fails or Data partition doesn't seem to mount correctly?
Relevent:
Reviewing some other threads:
TWRP: 3.0.2-2
Bootloader: UNLOCKED
I did NOT upgrade to Android 7.0 nor was I planning to, until Xposed is available.
I did NOT flash anything **new** recently. However, Installed an Xposed module yesterday which caused a bootloop. I rebooted into TWRP, uninstalled Xposed, rebooted into system (which looped once, out of the ordinary) and I uninstalled that module, back to TWRP installed Xposed, and rebooted back into system. It worked for 12 hours and then what I wrote this post for happened as stated above.
UPDATE3:
15 minutes into charging... NOT EVEN A RED BLINKING LED ANYMORE.
Last? UPDATE:
Almost 1 and a half hour into charging and there is no longer ANYTHING. Is it hard-bricked now?
How the **** is this possible? I'm very much capable of solving any sof-brick but not a hard-brick...

Thats a really crappy scenario. Im a little busy right now (not that I can get you out of this regardless) but I sort of skimmed through your post. Are you able to connect adb? If so you might be able to use "adb pull" to get that data.
On my 6p TB is located at:
/storage/emulated/0/TitaniumBackup/
Itll probably be the same location on your phone. Good Luck

KLit75 said:
Thats a really crappy scenario. Im a little busy right now (not that I can get you out of this regardless) but I sort of skimmed through your post. Are you able to connect adb? If so you might be able to use "adb pull" to get that data.
On my 6p TB is located at:
/storage/emulated/0/TitaniumBackup/
Itll probably be the same location on your phone. Good Luck
Click to expand...
Click to collapse
I was indeed able to connect to a PC after I saw the problem (the bootloop essentially)... But I didn't at the time as I didn't have a plan of action as to how to get my data, so I turned it off. After sometime, I couldn't do anything with the phone... Not able to boot into bootloader, not recovery, the phone is essentially not turning on to anything, not even the splash screen; like a hard-brick. I'm not sure if this indeed is a hard brick as I've never seen any.. and don't currently know what to try next.

Is the LED still showing? if so, do the bootloader boot combo, and see if fastboot devices gets a response in a command prompt - or terminal if you're a linux guy.
if so, you can boot to twrp, decrypt data - try default_password -, and browse the phone's files from your computer's file browser, the phone will show up as Nexus 6P. That's my suggestion, wish you luck.

TnT_ said:
Is the LED still showing? if so, do the bootloader boot combo, and see if fastboot devices gets a response in a command prompt - or terminal if you're a linux guy.
if so, you can boot to twrp, decrypt data - try default_password -, and browse the phone's files from your computer's file browser, the phone will show up as Nexus 6P. That's my suggestion, wish you luck.
Click to expand...
Click to collapse
I honestly declared it hard-bricked.
Will Fastboot show any devices if the phone didn't show bootloader screen?
I'll try again today.
Update:
Didn't work.

check out my post
[Guide] Fool/Noob proof way to do clean installs on Nexus Devices
http://forum.xda-developers.com/nexus-6p/general/guide-fool-noob-proof-to-clean-installs-t3518311

Note 3 remote media control problem

Hello everyone
It has been a while since I last started anything here.
I have had a few problems with my galaxy note 3, it freezes, sensors go crazy from time to time, things like that, but most of them I have been able to resolve or work around.
Now I have a new one that I was not able to resolve despite going for the last resort fixes. I have a galaxy gear 2 (not s2, just 2) that has this media control app. After using it, I found out that the app stops working a few hours after the device boots up. Right now all I know is this:
1. Everything works fine once system had a few minutes to load after start.
2. After unknown amount of time, the phone stops responding to gear, bluetooth headphones and cord headphones media control attempts.
3. Bug persisted after I flashed a new ROM and then rooted and used TWRP to get back my data partition (nothing else). Than I wiped cache and dalvik and booted up.
4. Currently trying to do the same but without rooting to see if that helps.
My phone before any attempts:
SM-N9005
4.4.2 Kitkat root stock ROM
TWRP
Ultimate kernel
Xposed framework (a few youtube modules xtorch and wanam)
I would appreciate any advice you have for me. I will update this if not rooting fixes the issue. If it does not I will root and reinstall xposed and others
UPDATE: Even no root no xposed system did not help. Flashing back my TWRP backup.

Wipe phone flash stock rom and test first .

I probably will, just not right now, it takes quite a long time to get phone into working order after a flash with no backup. Also if it helped I would have to wipe my gear too because of how pairing system works...

Computer doesn't recognize phone.

I started having issues with my phone and tried to fix them. The problem was simple. The sensors stoped working. First I tried a hard reset (didn't work). Installed Lineage OS. Didn't fix the issue and made some errors form the install. Tried the stock ROM. I tried two of them with the first one I discovered that it was a problem with the firmware of the sensors. The I tried an older version thinking that the firmware wouldn't be compatible and that it would work better. (I'm not entirely sure but I think it was this version MPD24.65-18.1)
The installation went well without problems. The firmware was (again) downgraded (and later upgraded without asking permission). The big issue is that my phone now is unable to connect with the computer. When I plug it it starts to charge but nothing more happens. The computer isn't aware that it has anything plugged (according to the ports). So I cannot run adb and cannot change anything on the phone. I tried to install from a SD card on the recovery mode but I think I'm not doing it as it should. I plug the card and run the updater from the SD. The first thing that is odd is that it actually displays the internal memory. And then when I run either a OTA.zip or a compress of a build named PG86IMG.zip I get a verification error.
I do not know what to do. I would like either to have working sensors or the 7.1.1 version.
Phone:XT1563 16 gb
Computer:Mac