Generally I am able to get some help on the forum but today must not be my day. I have a g935p sprint edge. I was able to root it in a couple different ways without issue but when it comes to putting twrp on it I am not able to. I was able to flash twrp with odin but then when i switch into odin i get a blue screen that says that the recovery is blocked due to custom stuff. Does anyone have any suggestions? I know its late but i want to get this thing going before tomorrow
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
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.
So, before I begin, I'd like to point out that I'm an idiot. I don't know how or why, but I'm an idiot.
I've been running danv's ROM for the longest time without issues (galaxy s4 on Rogers) and then decided to update the ROM today. After making my titanium backups and everything like that, (haven't made a ROM backup in a while though - again, idiot) I decided it was time to flash the ROM.
Well, I went and did a full wipe, and then all of a sudden when my phone rebooted, it rebooted into download mode with the whole "could not do normal boot" in the top left corner.
I was able to get into my phone by doing volume up/home/power and then canceling when it said to install new OS or not. So I do have access to my phone, but anytime it restarts it goes into download mode, I can't even get into recovery mode to flash the ROM.
Any ideas what to do to be able to flash this ROM? I have a rom backup from March of this year, would that fix the issue and then just try to flash the new ROM again once I was able to get into recovery mode?
Any help anyone can provide me would be much appreciated. I'm currently downloading the stock firmware from sammobile to see if that would fix the issue since I can install that over odin.
Thanks in advance.
*Edit* So recovering from a ROM backup didn't work either. I've done some researching and I think trying to flash through odin is my only option unless I've missed something. I'm running firmware NE3, so does that mean I should get the stockfirm ware for my device (S4 Rogers NI2) or get the firmware for the same NE3 that I have on my phone (In this case it would be Puerto Rico firmware)?
If someone could let me know if this would work, I would very much appreciate it.
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.
so heres the situation, a couple weeks ago my sammy a5 meet a horrible end and ive been without a phone. My buddy gave me his old s7 edge, its got cracked screen and has been sitting inn a drawer(hes rocking a pixel xl instead). so got it home charged it up turn it on and it got this blue sceen says there was a problem updating.
so longer story short got the stock 6.0.1 for bell 935w8 but i only run ubuntu, now while im able to flash smaller tars or img files flashing all stock at once wont work with either heimdall or Jodin3.
thought i could maybe flash twrp and go straight into custom roms i cant flash anything onto the device because of FAP lock in download mode.
Can anyone help me out? i know this would be easier with a windows comp but i dont have one.
can anyone help me