History:
I bought a Motoroi X (the name for Droid X at Mexico) and the very same day the Gingerbread leak came out, so I installed it, sadly, it came with lot of bloadware so I wanted to delete it but I had no root to do it. Few hours later Gingerbread rooted came out and I wanted to install it but I needed root, so I loaded 340 SBF of Verizon, then updated to Gingerbread. The problem of this is that I can't program my phone anymore to work with the 3G (my carrier uses BP_C_02.02.00P baseband) and I got BP_C_01.09.07P.
The only SBF of my carrier available is quite old, so I can't load it on my phone since it becomes blicked after it (main't req'), I tried loading NANDroid backups, configure the phone manually with QPST to work with 3G but with no luck. I have a dataplan with a Blackberry but it ends next week and I need having internet for the work, help will be appreciated. Thanks in advance.
Question:
Theres anyway to install an old SBF after installing 340 with bootloader 340?
Or there is a way to downgrade the baseband?
Hello all!
I just got the push for the 4.4 upgrade on my phone but I wanted clear a few things up before I commit. I'm currently on a rooted 4.3 with a modded radio for LTE. Is it safe to just run the OTA update from my phone? Or is there another proper way to prevent bricking? How should I go about this?
Thanks guys!
There are a lot of variables such as programs and versions installed, but I tried the OTA under similar conditions as you (In my case I was rooted, hybrid 27/84 radio, unlocked bootloader, TWRP, Koush's superuser, and otherwise stock 4.3) and it just didn't work. I even reverted back to the old radio before I tried it, but it might be the modified build prop or LTE activation that caused the problem. The OTA did not brick my phone or cause any other problems, it just didn't change anything on my 4.3 install. I could see while the update was running that it failed right after examining my existing install, so it didn't like something with my existing system config. I then did the following from the advice on this forum and my upgrade to 4.4 went flawlessly (Post #13):
http://forum.xda-developers.com/showthread.php?t=2542998&page=2
I just flashed the entire image of the os on top and didn't lose data. On twtp, LTE back, unlock boot loader from 4.3.
Sent from my Nexus 4, while driving in my Evo9.
Hey all,
Having a small issue with my Verizon LG G2.
When I first got it on launch, I rooted it, installed loki (to bypass the locked boot loader) and have been running custom ROMs.
This is the way I ahve been running it since, on 12B, with loki and CM11.
Before I installed custom roms I did a image backup using Clockwork.
Yesterday I bought a Droid Turbo, so it was time to restore the G2 in preparation for sale.
I attempted to restore my original backup of the stock image, but it failed (stating something about an inability to restore/system, resulting in a soft bricked phone.
I fixed this by downloading the LG Flash tool, and the stock 24A .kdz image, putting the phone in download mode and flashing it.
The LG flash tool seemed a bit buggy, complaining about not finding servers, but eventually flashed the phone with the .kdz.
Everything seems to have worked well. Root is gone, clockwork is gone, (and I assume loki is gone as well, but I can't tell) but now I can not do the latest OTA updates, and am stuck on 24A.
It's not that it downloads the OTA, and then fails to install it, but rather it complains that it is unable to download the updates at all.
I was thinking this might have something to do with the fact that the CDMA radio is now unactivated (since I got a new phone) and it somehow needs to verify with the Verizon network prior to downloading, so I grabbed a working SIM and popped it it in. Even with 4G via the SIM, the OTA downloads don't succeed.
Does the CDMA radio need to be activated in order for a phone to receive OTA updates? If not, I ahve something else wrong going on, and would appreciate any suggestions regarding fixing it.
The plan was to sell the LG G2 to pay for my Droid Turbo upgrade, but I don't want to sell the phone to someone if I think it may be having issues.
I would appreciate any thoughts and suggestions from you guys!
I have a Motorola Droid Razr M (XT907) that upon last reboot decided to stop at the Motorola Logo and won't continue the boot process. I can get into Fastboot and Recovery, but so far, neither has been helpful. I have read several threads concerning similar issues, but have not found a solution yet. This phone has not been previously rooted or unlocked and to my recollection the latest OTA has been installed.
When in Fastboot, it says Device is locked. Status code 0.
I'm working on a Windows 7 PC. I have installed Motorola Device Manager and the Motorola USB drivers. When the phone is in Fastboot, it is recognized in my device manager as Mot Single ADB Interface. When I run Motorola Device Manager it replies:
There are no updates for your device at this time.
Current Version:
98.12.4.xt907.verizon.en.us
I have also installed RSD Lite version 6.1.5. When I run it, it shows my connected device, however all of the fields look so:
ESN: N/A
Technology: N / A
Software Version: N / A
Flex Version: N / A
Bootloader Version: N / A
DRM Version: N / A
I have not been able to find the correct FXZ image to repair the phone and fear it may well be lost. I'm only 12 days away from phone upgrade eligibility and it's cost prohibitive to upgrade early, so I'd like to repair the phone enough to use it for the next 12 days.
Any and all suggestions would be great.
Thanks
Go through this threadhttp://forum.xda-developers.com/showthread.php?t=2869432 thoroughly. It contains everything you need to know. In short, flash your phone to stock KitKat 4.4.2 the .10 build, not the .15 build, unlock your bootloader and then it's up to you whether you continue on stock or flash a custom ROM. Do check (http://forum.xda-developers.com/showthread.php?t=3042687) that you have the latest drivers and the latest version of RSD Lite installed and if you have trouble with flashing check to make sure you're using the correct cable...
I just swapped from my Amaze 4g, to a used Note 3, and I'm a little lost as far as where I should start.
It says that it's on 4.4.2, and that I cannot update due to a modified system.
Basically, I would like to get updated to 5.1.1 (or as close as is official for the Note 3), and root it.
I'm afraid I'm not familiar with Samsung devices, and because I purchased this from ebay, I don't know how to tell the exact state that the former user put it in (I expected they would return it to stock prior to selling).
It's currently a T-Mobile branded, SM-N900T, on 4.4.2, build is KOT49H, security software MDF v1.0 release 2. Kernel is 3.4.0-660648.
It is supposedly unlocked for carriers, though I have not attempted a SIM card use yet, until I can tell that what I have is a valid device and the IMEI is checked out.
Any thoughts on how to validate the IMEI, and sort out how to get my new phone up to date would be appreciated. As I stated, I expected the vendor would have returned it to stock, but that is clearly not the case, so I don't want to accidentally boot loop it by doing something I shouldn't. I have not owned a Samsung before, so I want to be careful on how it differs from my Nexus 7, Amaze 4g, and Droid X, as they're all obviously very different in the OS area.
Thank you for the help1
Download tbe stock 4.4.2 rom and use odin to install. Then you will get the OTA updates.
Sent from my SM-N900P using Tapatalk
There is no stock 5.1.1 for note 3, only cm12.1/ aosp. Latest is 5.0 and you can use odin to flash. Maybe it's rooted that's why you can't update.
bladebarrier said:
I just swapped from my Amaze 4g, to a used Note 3, and I'm a little lost as far as where I should start.
It says that it's on 4.4.2, and that I cannot update due to a modified system.
Basically, I would like to get updated to 5.1.1 (or as close as is official for the Note 3), and root it.
...
Thank you for the help1
Click to expand...
Click to collapse
Some apps to install from Play Store...
Phone INFO Samsung - this will tell you all about your phone and the firmware etc.
Root Checker Basic - tells you if you are rooted or not.
SuperSU - this is so valuable you should buy the Pro licence. Chainfire does some great work for our phones.
TWRP - I have the zip version on my extSDCard and an Odin version on PC in case I have to rebuild from a Stock firmware. CWN works OK but most ROM builds seem to be for TWRP I think and a backup from one will not work on the other.
I don't know your previous phone so you probably need Odin v3.09 - this sits on PC and lets you flash firmware to the phone. (connected by USB)
For which you need Samsung USB drivers so the PC will recognise the phone. Install on PC before connecting phone.
Then do some browsing and find the processes to root your phone and install the ROM you want. If you just want Stock and access to all your phone, you can root it after flashing the original v5.0 download (from Sammobile or similar site - note on Sammobile you need a free account to DL) and then install Custom recovery (if wanted - it WILL trip the Knox flag but that may not matter given it's 2nd hand and might already be tripped anyway)
Read, make SURE you understand what is being said BEFORE you do anything - ask if you don't.
Good luck...
N9005 Lollipop brick
Hi All, just need a huge help here, a friend of mine has been using a N9005 which was auto restarting, she went online and downloaded this firmware...N900AUCUEOC1_N900AATTEOC1_N900AUCUEOC1_HOME.tar.md5....2.5GB in size...and flashed it, but the phone is stuck in boot loop even after recovery wiping data and cache, the phone can boot into download mode but re flashing the firmware always fails.....is there a solution for this.....please help
Thank you all for the info, especially the detailed info from Journyman16. I checked, and it is flagged as custom, which is fine, so I'm going to go ahead and try to return to mostly stock, update it, and root it.
Ok, everything went well. I had to do two attempts at rooting, but I think it's just one of those things where sometimes it doesn't restart into the process every time.
All seems good. I'm on 5.0, rooted, busyboxed, and smooth sailing.
Thank you all, again, for the tips. The Note 3 is running very well. Thank you to all of the devs that have made this process so refined. I've donated to you before, and did so again today. It's outstanding to have such well versed coders, on XDA, helping out the community.
mjmbirige said:
Hi All, just need a huge help here, a friend of mine has been using a N9005 which was auto restarting, she went online and downloaded this firmware...N900AUCUEOC1_N900AATTEOC1_N900AUCUEOC1_HOME.tar.md5....2.5GB in size...and flashed it, but the phone is stuck in boot loop even after recovery wiping data and cache, the phone can boot into download mode but re flashing the firmware always fails.....is there a solution for this.....please help
Click to expand...
Click to collapse
You have never learned not to ask in others posts? What does your problem has to do with this topic at all?
When you need help. Just click on Q&A then Create a new thread. How hard is it?