I am on a verizon galaxy s5. it was rooted, running freedom rom. i wanted to flash anew rom, but found out I lost my recovery somehow, and reflashed with the twrp app. I rebooted and got the message that I needed verizon tech support. I was going back to stock, but flashed a 6.0.1 stock image via odin. it boots, but I cant get my wifi on to get past the samsung security. should I just fl;ash another version? also, my phone in android recovery says 6.0.1/mmb29/g900vvru2dpd1. when I start the phone up it says "due to an abnormal factory reset you will not be able to use this phone until you sign into you samsung acct to erify it is yours" the wifi isn't on nor can i get to it. also, i had a stroke and haent been able to pay my bill, and im disconnected, but will pay on fri....i know this has nothing to do with it but thought the more info the better
thanx inadvance for your help
Related
I have a Samsung Galaxy S4, the Sprint version. I wasn't able to send or receive picture messages and I thought it might have something to do with my APN being wrong (I bought the phone on eBay and had it flashed to nTelos, my provider) but I wasn't able to edit the APN and nTelos was, as usual, no help. So I figured I'd just root it and be able to edit it then!
It was at that moment I stuck my shovel into the soft dirt and started digging.
Essentially, I believe my phone is without an OS at this point. I have tried using ODIN to put a recovery on there so I can at least do something, but now even ODIN is freezing up when I try and flash the Clockwork recovery. I am stuck on the Samsung S4 logo screen and while I can enter download mode I don't think I can enter recovery mode - at least, it hasn't been working tonight. I don't remember everything I've done to my poor phone, but it has to be hurting after the beating I've put it through. I originally tried to root it though I don't think I was successful because the Root Checker said I wasn't, though I'm not sure what I was doing wrong then. Things went downhill from there.
I've read through thread after thread hoping for something that would work, but I've given up trying to use other people's problems to solve my own. This is me saying "Uncle". I require assistance. Let me know what you need from me to provide me with the help I need.
Also - I have ADB on my computer and I think I have a basic understanding of how to use it, but since I can't enter recovery mode I can't do anything other than pat myself on the back for figuring it out. I think my first problem at this point is ODIN. I uninstalled KIES so that's not interfering (and don't even get me started on KIES - I installed KIES and it told me to install KIES3 which told me my device wasn't supported... which is crap because it's running Android 4.3 - or was before I got to it).
Thanks,
If you're sure the phone was on 4.3, then your options are limited thanks to Knox. You can only restore a 4.3 (MJA) based ROM to the phone via Odin, whether it is stock or custom. Easiest giveaway is if you see a line for "Knox" on the Download Mode screen.
At this point you should look in the ROM directory here for a full ROM (xxxxx.tar.md5), either MF9 (4.2.2) if it doesn't have Knox or MJA (4.3) if it does. If you cannot use Odin to put a full ROM on there, then you will need some more serious help.
Odin the stock 4.3 MJA OEM. Will return your phone to a stock unrooted state.
http://forum.xda-developers.com/showthread.php?t=2522810
I have tried everything I can possibly think of in a short period of time, and need an answer in a hurry. The phone (Verizon Samsung Galaxy Note 3 N-900V) was rooted back when kitkat was the main OS using geohot's towelroot (or possibly kingo root I can't remember which i used after I got the phone and upgraded from ICS). I have 2 of these exact same phones, used the exact same rooting method, and unrooted by uninstalling the superuser app, rebooted, and installed the OTA update to lolipop. My phone works fine, (the one I'm typing from) however, my other phone decided to take a dump. It's a software bug between the samsung firmware and the new lolipop OS. It was working for several months, then all the sudden it wouldn't recognize/register the APN. Now it doesn't see anything just about with the phone. Not even the IMEI from the phones serial number. The sim card has been replaced twice and has worked for a matter of a few hours, however, upon restarting the phone, it goes back to no service, and nothing is registered or recognized. I reflashed the phone with the stock 5.0 Lolipop using Odin several times to no avail. My phone (one I'm using now) once did this months ago, and I was able to access the service menu and reregister the SIM card and phone has worked fine since. With this other phone, I can't get into the service menu at all because nothing is registering. So, after reflashing 4 or 5 times, factory reseting from both the OS and from recovery booting, it still has the same issue. Here is my question. It used to be when I reflashed, the custom padlock would disappear. I'm getting a new phone tomorrow, and I need to get rid of the custom padlock before I return the old phone. I can use Odin, or whatever but it has to be something, I can do while it stays stock. The knox counter has not been tripped, and the flash counter is not tripped nor showing anything on the download mode. Everything lools, and feels stock, except that custom padlock. Is there a way to get rid of that custom padlock unrooted, by reflashing? I even used a pit file to repartition, but that didn't work either. Need help A.S.A.P.!
I would just hard brick the phone just before returning it...they will just throw it out at that point and your secret will be safe.
Hard Brick
xxperrin said:
I would just hard brick the phone just before returning it...they will just throw it out at that point and your secret will be safe.
Click to expand...
Click to collapse
You thinking maybe a NAND erase?
Hard Brick
I've thought about flashing the wrong rom too but dunno if that will work 100%. I either need to fix it, or make it 100% unrecoverable. Any advice?
I had a rooted BOG5 with TWRP, used Odin to apply stock BOG5 to sell after buying Nexus 6P.
It booted and I was able to skip setup wizards etc to show person who I sold it to it was working.
They couldn't get voice working on it so they wanted give it back to me.
In troubleshooting, I told them to do factory reset from within the phone and from within stock recovery.
I got the phone back and now I have the locked due to abnormal factory reset, my Samsung Account gives 'Processing Failed' message. Either I forgot to turn off the reactivation lock or they hosed something up. I tried their Samsung Account as well and get invalid password.
How do I get out of this lock out? Odin back to OC4? I tried to call Samsung and got a run around but they mentioned a Samsung Authorized Repair shop or something like that.
Any help would be appreciated. Thanks.
joegard said:
I had a rooted BOG5 with TWRP, used Odin to apply stock BOG5 to sell after buying Nexus 6P.
It booted and I was able to skip setup wizards etc to show person who I sold it to it was working.
They couldn't get voice working on it so they wanted give it back to me.
In troubleshooting, I told them to do factory reset from within the phone and from within stock recovery.
I got the phone back and now I have the locked due to abnormal factory reset, my Samsung Account gives 'Processing Failed' message. Either I forgot to turn off the reactivation lock or they hosed something up. I tried their Samsung Account as well and get invalid password.
How do I get out of this lock out? Odin back to OC4? I tried to call Samsung and got a run around but they mentioned a Samsung Authorized Repair shop or something like that.
Any help would be appreciated. Thanks.
Click to expand...
Click to collapse
try reflash BOG5?
Try with a different email account, that happened to me as well.
buhohitr said:
try reflash BOG5?
Click to expand...
Click to collapse
Yup and with other versions but once you go to BOG5, you cannot go back.
Hey guys,
I could use your expertise and help.
After updating my stock Note 4 Att variant from 5.1.1. to 6.0.1, I came back to my phone powered off. After turning it back on it freezes at the Att logo screen. Trying to boot into safe mode was a no go so I tried booting into recovery. Everything looked go for a second, I was greeted with an installing updates animation but that quickly was shut down and I got the "dm-verity verification failed..." error.
I tried wiping the cache and doing a factory reset. Talking with att technical support was no help at all. They basically told me if wiping the cache and factory reset didn't work I would have to get the phone replaced and pay a $150 deductible. I'm not paying them another dime when their update bricked my phone
So I'm here heart in hand hoping you guys could help me out. I did root my note 2 back in the day but forgot most of what it entails and was pretty bummed when I found out there was no root for the note 4. So I'm not a total noob but bear with me.
I did try Kies 3 but my phone wont connect. I tried off, on and in recovery still nothing.
Searching online it seems like most of the solutions require root access which this phone doesn't have. It also looks like it needs the stock firmware but most of the links I found here and elsewhere are dead, and sammobile doesn't have them either.
So what should I do? Am I out of options? Should I junk it cause Att sucks? Any sort of direction would be a big help! :highfive:
Mal-0 said:
Hey guys,
I could use your expertise and help.
After updating my stock Note 4 Att variant from 5.1.1. to 6.0.1, I came back to my phone powered off. After turning it back on it freezes at the Att logo screen. Trying to boot into safe mode was a no go so I tried booting into recovery. Everything looked go for a second, I was greeted with an installing updates animation but that quickly was shut down and I got the "dm-verity verification failed..." error.
I tried wiping the cache and doing a factory reset. Talking with att technical support was no help at all. They basically told me if wiping the cache and factory reset didn't work I would have to get the phone replaced and pay a $150 deductible. I'm not paying them another dime when their update bricked my phone
So I'm here heart in hand hoping you guys could help me out. I did root my note 2 back in the day but forgot most of what it entails and was pretty bummed when I found out there was no root for the note 4. So I'm not a total noob but bear with me.
I did try Kies 3 but my phone wont connect. I tried off, on and in recovery still nothing.
Searching online it seems like most of the solutions require root access which this phone doesn't have. It also looks like it needs the stock firmware but most of the links I found here and elsewhere are dead, and sammobile doesn't have them either.
So what should I do? Am I out of options? Should I junk it cause Att sucks? Any sort of direction would be a big help! :highfive:
Click to expand...
Click to collapse
Make sure samsung kies or samsung usb drivers are installed on your pc.
Download stock marshmallow firmware and flash through odin .this method does not require root.
After flashing dont let the phone boot just go to recovery and wipe cache+wipe data factory reset then reboot.
Wait 10 to 15 minutes.
Stock rom link.
https://www.androidfilehost.com/?fid=24651430732238073
Extract file and choose AP tab in odin.
Upload firmware file then connct device via usb cable to pc.
Hit start in odin.
You're the man! Not only did you save my phone, you stuck it to Att's money grubbing hands in one fell swoop. People will write songs about you, you'll go down in the history books as the man, the myth, the legend! People will swoon in your presence!
In all seriousness though you're awesome! Thank you!
One last question, will I be able to use the ota updates from here? Not that I would be too comfortable using them after this debacle, just wondering if they should work.
Mal-0 said:
You're the man! Not only did you save my phone, you stuck it to Att's money grubbing hands in one fell swoop. People will write songs about you, you'll go down in the history books as the man, the myth, the legend! People will swoon in your presence!
In all seriousness though you're awesome! Thank you!
One last question, will I be able to use the ota updates from here? Not that I would be too comfortable using them after this debacle, just wondering if they should work.
Click to expand...
Click to collapse
Thanks for the compliment. you just made me feel like i am a Hercules :victory:
If you want my advice dont ever take ota updates.
Just go to www.sammobiles.com/firmwares and grab latest rom for your model and flash in odin as you did.
Latest rom comes with the same security patch update the 1 comes in ota.
I personally do this way all the time.
Hope that helps and have a good day.
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