I got my brand new, shiny Verizon SGS4 yesterday and proceeded to root it via the published method (flash the old kernel etc.) and had no trouble at all. I then got a little daring and used GOO manager to download and install a custom TWRP recovery. After that my phone rebooted and gave me a screen that other Verizon users may be accustomed to with a "Samsung" and a picture of a lock and a nifty message saying that unauthorized software had been installed and the phone should be brought to the nearest Verizon store (I am a longtime ATT user who just switched to Verizon so I am thinking Verizon folks with older Samsung phones and locked bootloaders would know what this is about).
Long story short, rebooting of course didn't help. I went to ODIN and reflashed the newer boot image/kernel that I flashed after rooting the phone and when I rebooted I got the same Samsung and lock picture but to my surprise and happiness, the phone booted normally after that and was usable again.
Apologies for not giving the exact terminology for this but since I couldn't find this problem posted yet I thought I'd give everybody with a new Verizon SGS4 a heads up. Don't know about CWM but I suspect there isn't a compatible CWM recovery yet either and I can say I'm not going to be trying anything else fancy since we don't have an ODIN system dump yet to my knowledge with which to recover.
If anybody has any useful comments about Verizon and recoveries etc. please post away.
Related
Hi everyone,
Before blasting away with comments as to why I would do this, here's my story,
I live in Canada and just brought home a i9508, a China variant of the S4. It belonged to my dad and he didn't want it so I just took it. The i9508 doesn't have Play Store, and it doesn't work on Canadian 3G network.
So to me, the phone is useless right off the start (don't intend on selling it either, who wants it?) So I had 2 options:
1) Leave the phone as it is, and probably use it once every 1-2 years when I visit HK
2) Flash custom roms on it fully aware of the risk it will have so that there's a possibility I can make it more usable
So in the end I went with option 2.
I followed a guide and flashed TWRP for i9505 using Odin onto the phone, and used TWRP to install chainfire SU, and it actually worked (but SU wouldn't open because some sort of security on the phone is blocking it)
Next step, I downloaded the CM version for i9505 and flashed onto the phone, and that worked too. Only problem I've encountered was that the phone would only boot after a fresh install. If I installed CM, turned the phone off after the initial start up, the phone wouldn't boot pass the Samsung logo.
Up until this point, I didn't make a backup, because of my arrogance, cause I have available a copy of the official firmware, in case anything happens.
So I figured at this point, maybe if I restore the original firmware, and try the whole process again, the custom rom would work. So I went into Odin, flash the firmware with PDA, and failed. It just wouldn't work. After retrying it a couple of times, and downloading different updates of the firmware, nothing worked. Only thing working right now is, I can get into Download mode, and I can get into TWRP recovery (but for some reason, I can't flash the zips that I've adb pushed onto the phone, zip can't open)
For me, if it can't be fixed, then it's really SOL. But if there's a way to fix it, I'm open to testing anything people have in mind, cause afterall, this phone is paper weight either way. I'm interested in seeing if I could enable 3G by flashing a i9505 radio, despite warnings, although, I've never actually came across a thread where someone had actually tried it before.
Either way, if someone has any idea on how to fix the phone, and wouldn't mind sharing it, that'll be greatly appreciated.
Working
I can get into Download mode, but Odin is failing (if you need the error please let me know and I'll post it)
I can get into TWRP recovery, but can't flash files
I can get into adb
This isnt the correct forum for your phone. XDA don't follow clones
Unfortunately a section for i9508 doesn't exist, so I figure the closest one would be i9505.
Anyhow, if someone has an idea of how to fix it, I'm more than happy to do testing on it, like flashing other roms or radios.
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 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?
I've rooted and replaced the ROM on 3 other Android devices. I've spent two or three nights on this. Googling and reading page after page to try to get this right. I know I'm seriously lacking in knowledge, but I just can't stand the bloatware and lack of control over an OEM ROM. I knew I was taking a risk, but I did my best to be diligent without spending an excessive amount of time. All that said, I appreciate, in advance any help anyone can offer me. Whether that's direct advice or directing me to proper resources that I can't seem to find.
Samsung S5 SM-G900P (kltespr)
I had rooted it. I replaced the Sprint stock ROM (5.0.1 I think) with CM12.1 (which just got an OTA). I had TWRP 2.8.7 on it.
Unfortunately, I needed my research suggested I needed a Touchwiz ROM in order to activate phone service on the cell provider I'd chosen (Ting).
So I selected MOAR v7 and started following the directions here:
at galaxys5root.com/sprint-galaxy-s5-custom-roms/moar-lollipop-rom-for-sprint-galaxy-s5-w-2-8ghz-oc
I made a backup. I wiped the system/cache/davlik/etc.
I installed the Android 5.0 Bootloader TAR (G900P NDK Lollipop) per the instructions via Odin and using the Bootloader option. The flash failed. I can repeat the failure (ran Odin as admin, tried multiple USB ports, restarted the computer etc). I've since tried to send several recovery ROMS or OS ROMS (pardon if I'm using the wrong terminology here) to the device, but all I can get is download mode or a screen that says Samsung Galaxy S5 powered by Android (with Kernel is not Seandroid enforcing at the top). Sending TWRP via Odin has worked with a PASS, but still can't startup the device.
I can provide more detailed logs or information about where I'm stuck and how, but on the off chance that this is an obvious thing I'm going to stop here unless more detail would be useful.
Again, I'm grateful in advance for any help.
Moshker
Follow up and how I fixed my brick
This post is intended as a follow up in case anyone runs into a similiar problem and stumbles onto my post.
After trying several different bootloaders, including the stock ones from Samsung (multiple download attempts, very slow speeds, some didn't pass md5 check), and full ROM efforts via Odin 3.10.7 I was finally able to get one ROM to take.
G900PVPU3BOG1_G900PSPT3BOG1_SPR from androidfilehost.com/?fid=24052804347794921
After getting the phone activated on Ting I used Odin to push Chainfire Auto Root (408). I verified root after restart. Used Nandroid to make a new backup. I used Flashify to install TWRP 2.8.7. I restarted to recovery and DID NOT use TWRP to wipe the system/data/etc and instead loaded the MOAR7.0.OA6 ROM. During the ROM install process it asked if I'd like to wipe system/cache/davlik/etc. I did. The ROM installed successfully. I ran a Nandroid restore to bring back my apps and data. Most restored properly.
I still don't really understand what went wrong, why my efforts to fix it failed, and why the last thing I tried worked.
Really loving MOAR. I'm using the Numix theme and it's just incredibly clean and fast. CM12.1 had intermittent micro-freezes/lags that were driving me a little nuts and MOAR is really smooth and quite fast. I was pretty disappointed in CM as I had it a long time ago on an original DInc (7.2!).
Anyway, if you're phone is bricked, keep on fighting the good fight.
Hello all,
I recently discovered that my S5 was only running KitKat despite Marshmallow having been released for it. I checked for OTA updates and it found nothing, so I decided to flash a custom 6.0 ROM onto it (and for some reason I ended up deciding not to make a backup of the phone beforehand, the ultimate mistake).
The problem became that it didn't recognize Tracfone for my service provider and wouldn't connect to the mobile network. I then downgraded it to a 5.0 ROM, and it no longer even recognized the SIM card, saying there was none.
So I tried to flash the original stock ROM a few times, but every time either got errors from ODIN, the phone itself, or the TWRP bootloader.
Long story short, I seem to have screwed up multiple times trying to install a ROM to get around KitKat and now my phone appears to be softbricked. I can get into the TWRP menu and the "download" mode, but when trying to start the phone, it sits on the "Samsung Galaxy S5" screen with the "Set Warrenty Bit : kernel" text at the top left.
I'm just wondering if there's a way to fix it at this point, or if I've completely trashed the phone.
If anybody has suggestions or experience with this, all help is welcome!
Thanks!
MevNav said:
Hello all,
I recently discovered that my S5 was only running KitKat despite Marshmallow having been released for it. I checked for OTA updates and it found nothing, so I decided to flash a custom 6.0 ROM onto it (and for some reason I ended up deciding not to make a backup of the phone beforehand, the ultimate mistake).
The problem became that it didn't recognize Tracfone for my service provider and wouldn't connect to the mobile network. I then downgraded it to a 5.0 ROM, and it no longer even recognized the SIM card, saying there was none.
So I tried to flash the original stock ROM a few times, but every time either got errors from ODIN, the phone itself, or the TWRP bootloader.
Long story short, I seem to have screwed up multiple times trying to install a ROM to get around KitKat and now my phone appears to be softbricked. I can get into the TWRP menu and the "download" mode, but when trying to start the phone, it sits on the "Samsung Galaxy S5" screen with the "Set Warrenty Bit : kernel" text at the top left.
I'm just wondering if there's a way to fix it at this point, or if I've completely trashed the phone.
If anybody has suggestions or experience with this, all help is welcome!
Thanks!
Click to expand...
Click to collapse
Are you sure you have the stock firmware for the 902l and not the 903vl? The reason you didn't get the update for 6.0 is you have the 902l model. If you had the 903vl model you'd have 6.0. Straight talk never released it for the 902l model. No idea why being both models are very similar. Im not sure but if you make it back to stock on kitkat. I think you can use safestrap from the Verizon s5 to use some custom roms that run kitkat. If your bootloader is in fact unlocked and you can install a custom recovery other then safestrap. I believe you can install pretty much anything but I'm pretty sure straight talk ships the phones with the Toshiba chip so the bootloader isn't unlockable