So my old phone had to get warranty replaced and I got sent a refurbished phone already with boe1. Is it rootable? I can't downgrade to kitkat and use that method cause Odin fails. Read too many threads with bad info so I'm just making one here if it's possible what's the tutorial.
For now OE1 is unrootable and can't be downgraded. Once the full tar is released it might be possible to root, but possibly not.
Take it back to them and say you dont like this version, its worth a try
Well I already quoted myself and this post once already so why not do it again? lol
Dudash said:
I'm starting to wonder if Verizon pulled the OE1 update..
Source
Notice the date of the official software update PDFs:
OD5: benefits-galaxy-s5-6-10-15.pdf
OE1: benefits-galaxy-s5-6-29-15.pdf
OD5: benefits-galaxy-s5-7-7-15.pdf
For some reason, they are saying the newest software available is OD5 again. This would explain why the OE1 .tar hasn't surfaced yet.
This doesn't really help people that already updated using the OE1 OTA because they're locked on it now. I'd recommend that those people call verizon and complain because they may send you another phone.
Click to expand...
Click to collapse
So MuminMohamed's idea may not be a bad one.
Is the OE1 stilll Un rootable? - NEVERMIND.. found the answer to my DUMB ASS question.
Related
EDITED - an XT1095 owner on the 60.16 bootloader from a 5.1 soak bricked when he downgraded to 4.4.4 then took the 5.0 OTA. Several Brazilian XT1097 owners have done the same on the 60.14 or 60.16 bootloader.
THERE IS NO REASON TO DOWNGRADE TO 4.4.4 AFTER TAKING THE 5.1 SOAK IF THE 5.0 STOCK IMAGES ARE AVAILABLE FOR YOUR DEVICE!!!! Just flash the 5.0 stock images instead (system, kernel, modems, baseband, recovery - but not bootloader (motoboot) or partition table (gpt)).
Quite a few posters on the Q&A forum have hard bricked by taking the 5.1 soak, then downgrading to 4.4.4 then taking the 5.0 OTA. And unfortunately, the files that are necessary to restore their bootloaders are not available.
Obviously, taking an OTA after downgrading is dangerous. I would only flash the firmware myself or use Motorola Device Manager to upgrade if you have downgraded in the past.
Update - a poster on reddit is claiming that they did in fact take the brazilian 5.1 soak OTA, then downgraded to the chilean 4.4.4 then took the chilean 5.0 OTA without bricking. If this is true (and I have no way of knowing if it is true or not), what it could mean is that the OTA updater scripts are supposed to have checks in them that when your bootloader is not the right version, they prevent a brick.
From all that is posted on the Q&A forum, it looks like the Brazilian 5.0 OTA updater script did not have adequate checks in it to prevent bricking. IOW, human error in writing the brazilian 5.0 OTA updater script.
None of us can know which OTA updater script will be properly written and which ones will be defective until people start bricking. My advice is that you don't take the chance, because even if the chilean 5.0 OTA updater script was properly written, the brazilian one was not. Who knows what others were defective.
I would not take the chance myself (and I have MotoCare so it would only be $39 for me to get a new device if I brick) and don't see why anyone would. The Brazilians whose devices were bricked by the 5.0 OTA updater script are being denied warranty service for their devices due to having rooted in the past. They can tell they rooted in the past by the qe (root checker).
There is nothing to be gained by doing this and clearly at least one 5.0 OTA updater script does not prevent bricks if you have previously updated to the 5.1 soak.
I've flashed the the soak and down graded twice in the past couple of months. What is happening to cause hard bricks?
The bricks are caused when doing OTA after a downgrade. Not when flashing.
Sent from my XT1095
eqjunkie829 said:
I've flashed the the soak and down graded twice in the past couple of months. What is happening to cause hard bricks?
Click to expand...
Click to collapse
It happens when they downgrade to 4.4.4 then take the 5.0 OTA as stated in the OP.
AGISCI said:
The bricks are caused when doing OTA after a downgrade. Not when flashing.
Click to expand...
Click to collapse
Right, so I would never take an OTA after downgrading - I would only flash the firmware or use MDM (which is the same as flashing but has checks in it).
,,,
wolfu11 said:
There has to be a reason some of us can downgrade and take the OTA without issues.
Maybe part of the problem is people trying it with a modified software status ?
I've gone back and forth a few times on my 1095 and the one thing I notice is my software status always says official.
Click to expand...
Click to collapse
I responded in the other thread.
wolfu11 said:
There has to be a reason some of us can downgrade and take the OTA without issues.
Maybe part of the problem is people trying it with a modified software status ?
Click to expand...
Click to collapse
The issue is with taking the 5.1 soak, downgrading to 4.4.4 then taking the 5.0 OTA. The OTAs are supposed to fail if your system and recovery are not stock. I am sure the issue is taking the 5.0 update with the 5.1 bootloader and partition table - the OTA updater script does not adequately protect you from a hard brick when you have a higher version BL and PT than the system/recovery version you are running.
You simply cannot downgrade the bootloader despite what some people are saying here - it doesn't happen. Neither fastboot nor mfastboot will downgrade your bootloader. If people were on 5.0 system and then went back to 4.4.4 system and they are still on the 4.4.4 bootloader, then it is because they never successfully flashed the 5.0 bootloader. If they had successfully flashed the 5.0 bootloader, their bootloader would not flash back to the 4.4.4 bootloader using either fastboot or mfastboot.
What is going on with the OTAs that I have seen is that once you upgrade to 5.1 via the soak OTA, you flash back to 4.4.4, which will flash your system/kernel/ramdisk/modems/baseband/recovery back to 4.4.4 but not your bootloader or partition table. Then when they take the 5.0 OTA, which is a patch, the OTA updater script is trying to patch the 5.1 bootloader and partition table as if they were the 4.4.4. This should never happen - it is totally a Motorola mistake. The 5.0 updater script should detect that the person is on a different version bootloader and partition table than 4.4.4 and it should fail rather than hard brick the phone. But it doesn't.
It is infuriating that these people are hard bricking due to Motorola's bad coding and they are being denied warranty service due to having rooted. Root has nothing to do with it - the OTA updater scripts should be coded to fail if the person is on the wrong bootloader and partition table.
wolfu11 said:
The one thing I notice is my software status always says official.
Click to expand...
Click to collapse
Your qe however will show you have rooted in the past if you have ever rooted before.
[,,,
wolfu11 said:
Okay but when I've down graded before and after I sign into kitkat I get a message in the status bar saying to downgrade the firmware I click okay and it reboots. What is that downgrading?
Click to expand...
Click to collapse
Not the bootloader and partition table. I explained that in my other thread.
,,,
wolfu11 said:
That doesn't answer the question, which was what does it downgrade? Anyone know ?
Click to expand...
Click to collapse
Yeah, it does - I answered your question in my other thread multiple times. Just read the thread.
JulesJam said:
Yeah, it does - I answered your question in my other thread multiple times. Just read the thread.
Click to expand...
Click to collapse
Actually you didn't nor did anyone else, I'll just downgrade again and see what that Motorola firmware thing is all about.
No big deal since my phone doesn't seem to brick anyway.
wolfu11 said:
Actually you didn't nor did anyone else,
Click to expand...
Click to collapse
Yeah I did, but I am not repeating it b/c I am tired of spoonfeeding people who don't know basic things yet want to argue with me. You can read the thread or don't. No sweat off of my back either way.
wolfu11 said:
No big deal since my phone doesn't seem to brick anyway.
Click to expand...
Click to collapse
Because you aren't downgrading your BL or PT, lol!
Anyhow, please stop cluttering this thread. I suggest you read and learn what you are flashing then you will know. And please don't encourage other people to do dangerous things with their device when you don't even know what it is that you did with yours.
,,,
wolfu11 said:
Was just curious if you actually downgraded yourself
Click to expand...
Click to collapse
Why would I do something stupid?
wolfu11 said:
or was going by hearsay.
Click to expand...
Click to collapse
OK, you don't know what hearsay is. It is a rule of evidence. It has nothing at all to do with anything other than what is admissible evidence in a court of law. Completely irrelevant to anything being discussed here.
But if what you are trying to say is that I haven't done it myself so how could I possibly know - well I haven't thrown my body in front of a speeding train before but I know if I do, the chances are high I will die, lol! No, I don't have to brick my phone myself to know what could cause a brick.
I simply do not believe that all of the people on the Q&A forum who are begging for the blankflash files to be released are liars and/or making up false bricking stories out of boredom. I believe them when they say they bricked their devices and are desperate for some help.
wolfu11 said:
I won't clutter your thread any longer
Peace
Click to expand...
Click to collapse
Thanks.
JulesJam said:
Why would I do something stupid?
OK, you don't know what hearsay is. It is a rule of evidence. It has nothing at all to do with anything other than what is admissible evidence in a court of law. Completely irrelevant to anything being discussed here.
But if what you are trying to say is that I haven't done it myself so how could I possibly know - well I haven't thrown my body in front of a speeding train before but I know if I do, the chances are high I will die, lol! No, I don't have to brick my phone myself to know what could cause a brick.
I simply do not believe that all of the people on the Q&A forum who are begging for the blankflash files to be released are liars and/or making up false bricking stories out of boredom. I believe them when they say they bricked their devices and are desperate for some help.
Thanks.
Click to expand...
Click to collapse
That clears up a lot .
Thanks
FYI - a poster on reddit is claiming that they did in fact take the brazilian 5.1 soak OTA, then downgraded to the chilean 4.4.4 then took the chilean 5.0 OTA without bricking. If this is true (and I have no way of knowing if it is true or not), what it could mean is that the OTA updater scripts are supposed to have checks in them that when your bootloader is not the right version, they prevent a brick.
From all that is posted on the Q&A forum, it looks like the Brazilian 5.0 OTA updater script did not have adequate checks in it to prevent bricking. IOW, human error in writing the brazilian 5.0 OTA updater script.
None of us can know which OTA updater script will be properly written and which ones will be defective until people start bricking. My advice is that you don't take the chance, because even if the chilean 5.0 OTA updater script was properly written, the brazilian one was not. Who knows what others were defective.
I am not taking the chance myself (and I have MotoCare so it would only be $39 for me to get a new device if I brick) and don't see why anyone would. The Brazilians whose devices were bricked by the 5.0 OTA updater script are being denied warranty service for their devices due to having rooted in the past. They can tell they rooted in the past by the qe (root checker).
There is nothing to be gained by doing this and clearly at least one 5.0 OTA updater script does not prevent bricks if you have previously updated to the 5.1 soak.
Heads up peeps - the XT1095 5.1 soak OTA updater script does not have adequate checks in it to prevent a hard brick if you have downgraded and then attempt to upgrade again.
http://forum.xda-developers.com/showpost.php?p=60941697&postcount=132
So this is just like the Brazilian XT1097 5.0 OTA.
Please read the edit to the OP!!!
This happened to me and I'm so frocking pissed I didn't see this thread beforehand!! Does anyone know if a JTAG service could fix this or how Mich Motorola would charge to repair?
Hi,
In my possession i have the following firmwares:
...BOC4
...BOD5
and my phone is installed on the ...BOG5 firmware.
I wanted to know out of the above three which firmwares can be rooted, if any? So that i can flash the rootable firmware on my S5 verizon and root the phone.
thanks.
smn216 said:
Hi,
In my possession i have the following firmwares:
...BOC4
...BOD5
and my phone is installed on the ...BOG5 firmware.
I wanted to know out of the above three which firmwares can be rooted, if any? So that i can flash the rootable firmware on my S5 verizon and root the phone.
thanks.
Click to expand...
Click to collapse
Your question has already been answered in a previous thread you started. Your phone is on BOG5 firmware therefore the only firmware you can flash onto your phone is BOG5. BOC4 and BOD5 can be rooted, but you cannot flash either onto your phone. Your phone cannot be rooted.
Ouch! Frosty are we? Must have been a bad day as usual for you..
Anyway, FYI: I didn't ask that question before, I asked about downgrading ans this is about replacing current 5.0 firmwares with other 5.0 firmwares.
Lighten up man, take it easy with life and you won't be so bitter all the the time.
smn216 said:
Ouch! Frosty are we? Must have been a bad day as usual for you..
Anyway, FYI: I didn't ask that question before, I asked about downgrading ans this is about replacing current 5.0 firmwares with other 5.0 firmwares.
Lighten up man, take it easy with life and you won't be so bitter all the the time.
Click to expand...
Click to collapse
The problem is this question has been asked many times and the answer will never change. If you are on OG5, you cannot downgrade, you cannot flash backwards, and you cannot root. Period. Sorry, but you can thank Verizon and Samsung for that.
Any likely root to come out in the near future then? For example when this version of firmware gets old and they get another update firmware released.
Not unless someone finds a usable exploit. Possible, but not looking very good.
smn216 said:
Any likely root to come out in the near future then? For example when this version of firmware gets old and they get another update firmware released.
Click to expand...
Click to collapse
Do everyone here a favor and search before you post. It is rule#1, and your questions have all been answered countless times. Maybe YOU should give it a rest instead.
When I first got my Version s5 I learned I could not root. I noticed a update this morning and don't want to install because I have been waiting to root. In hopes some one has figured it out? My phone is "BOG5" build and last I checked it was unrootable. Just making sure I don't miss out on rooting finally. And if there is no root should I still not install the update?
Update note: I looked and could not root "bog5", so I updated now my phone is running android 5.0 with build "Bok3". Is this rootable?
Thanks
RichThePoor said:
When I first got my Version s5 I learned I could not root. I noticed a update this morning and don't want to install because I have been waiting to root. In hopes some one has figured it out? My phone is "BOG5" build and last I checked it was unrootable. Just making sure I don't miss out on rooting finally. And if there is no root should I still not install the update?
Update note: I looked and could not root "bog5", so I updated now my phone is running android 5.0 with build "Bok3". Is this rootable?
Thanks
Click to expand...
Click to collapse
OG5 wasn't rootable, what makes you think OK3 would be? Sorry to be snide, but it's not.
ldeveraux said:
OG5 wasn't rootable, what makes you think OK3 would be? Sorry to be snide, but it's not.
Click to expand...
Click to collapse
I thought the same thing. I didn't think it would hurt to ask. I was looking into the update and it's been sent out since the end of last year. I was hoping someone found something in the new build that they could exploit to root. Also there is word that the s5 is rootable but it's not available. Idk but I hope some figures out the root. If I knew how or even enough about it I would try. Stupid company's locking the bootloader make me angery. Lol
RichThePoor said:
I thought the same thing. I didn't think it would hurt to ask. I was looking into the update and it's been sent out since the end of last year. I was hoping someone found something in the new build that they could exploit to root. Also there is word that the s5 is rootable but it's not available. Idk but I hope some figures out the root. If I knew how or even enough about it I would try. Stupid company's locking the bootloader make me angery. Lol
Click to expand...
Click to collapse
It is rootable <OE1. Not above. There's rumor that the bootloader can be unlocked, not that higher firmwares are rootable. Regardless, still a rumor.
ldeveraux said:
It is rootable <OE1. Not above. There's rumor that the bootloader can be unlocked, not that higher firmwares are rootable. Regardless, still a rumor.
Click to expand...
Click to collapse
Okay, thanks for the help an info Ideveraux.
I have the G900A (Unlocked) but I'm on the T-Mobile Network and I'd like to update from 4.4.4 to lollipop
From what I understand AT&T and T-Mobile have both shipped the lollipop updates but I can't seem to find a way to update my phone.
Going through settings->About->Software Updates tells me there are no updates.
How can I go about updating?
Thanks.
You can look on sammobile for the latest firmwares, but as far as i know the latest for G900A is 4.4.2
In the att s5 section there's threads with the files for it, I think you get the official update and do it through the stock recovery, I've never done it myself so I can't help, sorry :s
Sent from my SAMSUNG-SM-G900A using Tapatalk
ozymandius95 said:
I have the G900A (Unlocked) but I'm on the T-Mobile Network and I'd like to update from 4.4.4 to lollipop
From what I understand AT&T and T-Mobile have both shipped the lollipop updates but I can't seem to find a way to update my phone.
Going through settings->About->Software Updates tells me there are no updates.
How can I go about updating?
Thanks.
Click to expand...
Click to collapse
You could try this
http://forum.xda-developers.com/showpost.php?p=65234333&postcount=28
But bear in mind, once you are on LP, you can not downgrade to KK again afaik
So things like root might be an issue (Haven't had enough coffee yet to remember 100%) do some reading up first
*Detection* said:
You could try this
http://forum.xda-developers.com/showpost.php?p=65234333&postcount=28
But bear in mind, once you are on LP, you can not downgrade to KK again afaik
So things like root might be an issue (Haven't had enough coffee yet to remember 100%) do some reading up first
Click to expand...
Click to collapse
Yikes.
I've never cared for rooting before, but I like to keep current on the latest firmware.
So if I understand this correctly I'll be stuck at LP when I get there, even after marshmallow rolls out, yes?
ozymandius95 said:
Yikes.
I've never cared for rooting before, but I like to keep current on the latest firmware.
So if I understand this correctly I'll be stuck at LP when I get there, even after marshmallow rolls out, yes?
Click to expand...
Click to collapse
No, you can upgrade firmwares, so MM will be fine, but from what I remember with that model, and a few other S5s, you can not downgrade due to the bootloader being locked once you update to Lollipop
If you read the whole thread (Link top right) of that link I posted - you'll see me trying to help another G900A member with the same problem
I have a g930a with the basband version G930AUCS4APK1 and I have done all OTA updates.
Is it still rootable? Am I on the new bootloader?
Root???
FreshIce21 said:
I have a g930a with the basband version G930AUCS4APK1 and I have done all OTA updates.
Is it still rootable? Am I on the new bootloader?
Click to expand...
Click to collapse
THAT is an EXCELLENT question...
FreshIce21 said:
I have a g930a with the basband version G930AUCS4APK1 and I have done all OTA updates.
Is it still rootable? Am I on the new bootloader?
Click to expand...
Click to collapse
go to the root thread, follow the instructions and give it a shot. That's really the best way to find out...just make sure you have the APK1 firmware on standby in case it doesn't turn out well.
SantinoInc said:
go to the root thread, follow the instructions and give it a shot. That's really the best way to find out...just make sure you have the APK1 firmware on standby in case it doesn't turn out well.
Click to expand...
Click to collapse
Pretty much this. Backup files you don't want to lose, download the stock Odin files, and give rooting a shot. Worst case, you just gotta flash stock back via Odin. You may be able to flash an earlier firmware via Odin and root from there. Though I doubt Odin would let you. If I were you, I'd download all the applicable files, backup my data, wait until I've got a good chink of time ithat I don't need my phone and start playing around with it. I had all sorts of complications rooting mine s{ I was phone-less for like an hour
SantinoInc said:
go to the root thread, follow the instructions and give it a shot. That's really the best way to find out...just make sure you have the APK1 firmware on standby in case it doesn't turn out well.
Click to expand...
Click to collapse
where can i find the apk1 firmware?
FreshIce21 said:
where can i find the apk1 firmware?
Click to expand...
Click to collapse
Sammobile.com
Just search by your phones model #.
SantinoInc said:
Sammobile.com
Just search by your phones model #.
Click to expand...
Click to collapse
They don't have any firmware for the att model just USB drivers
Any way to extract the firmware from my phone??
Update 12/6/16
I downgraded to the U firmware (G930UUEU4API3) following the steps here: http://forum.xda-developers.com/att-galaxy-s7/how-to/g930uueu4api3-firmware-download-t3481159
I then rooted using Max Lee's directions and I have root! Haven't tried rooting directly from APK1 firmware
I successfully rooted my G930AUCS4APK1 using princecomsy how to.
http://forum.xda-developers.com/att-galaxy-s7/how-to/root-s7-att-g930a-g935a-t3410538
I'm still trying to learn the nomenclature....so, i'm assuming by the PK1 one part of the version that it is new than PI3?
Just wasn't sure about UUE part. Sorry, noob in this dept.
But, wanted to at least share that I had successful root with OP baseband.
Now to figure out how to make the battery last more than 10hrs and respond a little quicker.
The V15 fix hasn't seem to do much in comparison to stock OTA.
Hope this helps.
bweegn said:
I'm still trying to learn the nomenclature....so, i'm assuming by the PK1 one part of the version that it is new than PI3?
Just wasn't sure about UUE part. Sorry, noob in this dept.
Click to expand...
Click to collapse
(for the others that may not know too)
The last three characters of the release are the ones that matter.
* The P indicates the year (P=16th letter of the alphabet, 2016)
* The K indicates the month (K=11th letter of the alphabet, November)
* The 1 represents the release number (to allow for more than one release each month)
Keep in mind that once you flash a newer firmware on the S7, you cannot go back to an older one. Odin will not let you flash it. Even if you could, it would most likely trip the KNOX flag.