Related
Hello there,
So, I have a Samsung Galaxy S5 G900R4 with U.S. Cellular. I've heard of rooting your phone, and I decided I'd give it a try. Now, the rooting went fine, and the phone was working like a charm, until I started to have some issues. SuperSU needed to update its binary, and I allowed it to try, but it continued to tell me that it could not update it. Hence, I let it reboot when it offered. Now, for whatever reason, the phone won't boot past the U.S. Cellular 4G logo that appears, it just sits there on that screen.
Now so far, I haven't been able to find anyone that has encountered this specific problem, as most people say their soft-bricks are bootlooping and whatnot. I'm not sure if my specific case is technically a soft brick, or something else, but I wanted to just return it to stock format. I loaded up Odin again, downloaded the 1.5g firmware file, and I got the SW REV CHECK FAIL error.
I did some research, and I searched EVERYWHERE, and the closest I could find to a solution was http://forum.xda-developers.com/showthread.php?t=2798396 <-- this thread. Which makes sense, when I read it. I'm guessing the bootloader is locked on my phone, or something. The problem is that this thread is for the Galaxy S5 G900AU, and I don't have that phone.
Maybe I'm just not searching on the web enough, or I didn't search the site well enough, but I have not been able to locate a similar set of AP, CP and CSC files for my specific model.
I would really appreciate it if someone could point me in the right direction or, if the issue I'm actually having with my phone is NOT a soft-brick and there is another solution, suggest another way for me to fix the phone.
Thank you.
First off, I'd try clearing the caches from recovery
If that fails, factory reset from recovery
If that fails, (And I'm not sure about stock firmwares with ODIN & locked bootloaders) I'd try flashing stock from ODIN also
Grab stock ROMs from here
sammobile . com / firmwares / database /SM-G900R4/
Can't link it here, as SM links are not allowed - just remove the spaces
*Detection* said:
First off, I'd try clearing the caches from recovery
If that fails, factory reset from recovery
If that fails, (And I'm not sure about stock firmwares with ODIN & locked bootloaders) I'd try flashing stock from ODIN also
Grab stock ROMs from here
sammobile . com / firmwares / database /SM-G900R4/
Can't link it here, as SM links are not allowed - just remove the spaces
Click to expand...
Click to collapse
Well last night I went ahead and used recovery to clear cache, and then I did a factory reset. I just did it again, now, but I guess I'll have to download the file from SM to try. I already have a stock ROM, but I can't remember where I downloaded it from, so it may actually be a 4.4.2 ROM or something, which would explain why it won't work. I'll wait for the 5.0 ROM to download and give it a try, should take a little more than an hour and a half, then I'll report back.
Xeretius said:
Well last night I went ahead and used recovery to clear cache, and then I did a factory reset. I just did it again, now, but I guess I'll have to download the file from SM to try. I already have a stock ROM, but I can't remember where I downloaded it from, so it may actually be a 4.4.2 ROM or something, which would explain why it won't work. I'll wait for the 5.0 ROM to download and give it a try, should take a little more than an hour and a half, then I'll report back.
Click to expand...
Click to collapse
Try this link, if it works, it won't work for long
Code:
http://am4-r1f4-stor08.uploaded.net/dl/800e713b-624b-4a91-a57c-1639c6b5071e
*Detection* said:
Try this link, if it works, it won't work for long
Click to expand...
Click to collapse
It worked, it's downloading now, just have to give it some time.
nice one
*Detection* said:
nice one
Click to expand...
Click to collapse
I really hope this works, when it finishes >.>
Any idea what's happening with the phone to cause it to stay at the U.S. Cellular screen?
I never let SuperSU reboot when I let it update the binaries
Could be a number of things, possibly just corrupted a file necessary for boot, but as SuperSU has root, it could be anything
I don't know the ins and outs of how SuperSU works, but I know a few carrier specific US S5s have a locked bootloader, Verizon, AT&T etc - not sure if rebooting to allow the binary update requires an unlocked bootloader, maybe that bricked it, half assed attempt at a root process failed maybe
*Detection* said:
I never let SuperSU reboot when I let it update the binaries
Could be a number of things, possibly just corrupted a file necessary for boot, but as SuperSU has root, it could be anything
I don't know the ins and outs of how SuperSU works, but I know a few carrier specific US S5s have a locked bootloader, Verizon, AT&T etc - not sure if rebooting to allow the binary update requires an unlocked bootloader, maybe that bricked it, half assed attempt at a root process failed maybe
Click to expand...
Click to collapse
As far as I know, though, U.S. Cellular has confirmed that this device has an unlocked bootloader. And besides that, if it were locked, wouldn't that have come up as an issue when I rooted the device? I used the CWM custom recovery tool.
On a similar note, I'm not even sure if the problem was a locked bootloader. It's just that, from what I've read with other people having the same issue, they solved it by excluding the BL file from the flash and instead only using the AP, CP and CSC files.
Xeretius said:
As far as I know, though, U.S. Cellular has confirmed that this device has an unlocked bootloader. And besides that, if it were locked, wouldn't that have come up as an issue when I rooted the device? I used the CWM custom recovery tool.
On a similar note, I'm not even sure if the problem was a locked bootloader. It's just that, from what I've read with other people having the same issue, they solved it by excluding the BL file from the flash and instead only using the AP, CP and CSC files.
Click to expand...
Click to collapse
If you can flash anything custom from ODIN, bootloader is unlocked, afaik, locked bootloaders require a right mess on to get anything flashed to them
To root with a locked bootloader, is easily possible if you're on a certain KitKat ROM, and use Towelroot - other than that, (From what I've read), you need to use specific tools, so it sounds like your bootloader is indeed unlocked - which makes this next ROM flash, much more likely to work using only ODIN
Use ODIN 3.10.6 though
My experience with the S5 is with an unlocked bootloader (G900F), so I can only quote what I know about locked from what I've read, but it sounds like that doesn't matter in your case
*Detection* said:
If you can flash anything custom from ODIN, bootloader is unlocked, afaik, locked bootloaders require a right mess on to get anything flashed to them
To root with a locked bootloader, is easily possible if you're on a certain KitKat ROM, and use Towelroot - other than that, (From what I've read), you need to use specific tools, so it sounds like your bootloader is indeed unlocked - which makes this next ROM flash, much more likely to work using only ODIN
Use ODIN 3.10.6 though
My experience with the S5 is with an unlocked bootloader (G900F), so I can only quote what I know about locked from what I've read, but it sounds like that doesn't matter in your case
Click to expand...
Click to collapse
It worked! Thank you so much for the help, I really appreciate it.
Well, my warranty is now void. Is there a safer way to root the phone, or should I just leave it be?
Xeretius said:
It worked! Thank you so much for the help, I really appreciate it.
Well, my warranty is now void. Is there a safer way to root the phone, or should I just leave it be?
Click to expand...
Click to collapse
Great
Flashing a stock ROM won't void your warranty, but if it is indeed void (KNOX 0x1), then just flash this with ODIN
http://download.chainfire.eu/404/CF-Root1/CF-Auto-Root-klteusc-klteusc-smg900r4.zip
Tripping KNOX only happens when you flash something not signed by Samsung, IE: A custom recovery, ROM or Kernel etc
I have the same issue, same phone I ended up flashing a custom ROM because I luckily flashed twrp before it bricked on the us cellular screen.. How did you fix this I just want to get back to stock remove my root completely
Guys,
I have some very noob questions about flashing that I would like to solve :
1) is normal that fastboot connection works only after setting the device for "allow own unlock" and "USB debugging"?
2) I might flashing my devices without unlocking the bootloader? And what about flashing original firmwares from Motorola?
(I ask because my bootloader is locked under status "2")
2) I tried to flash my device and, despite of several "preflashing" errors, my device still showing status 2 on bootloader, but it started showing that "unlocked bootloader warning" when it starts, is that normal? How to solve it?
3) I might flashing an older firmware (update September ) than I already have in my device (December)?
4) what is the function of recovery mode on bootloader ? I
Sent from my XT1575 using Tapatalk
Belotto said:
Guys,
I have some very noob questions about flashing that I would like to solve :
1) is normal that fastboot connection works only after setting the device for "allow own unlock" and "USB debugging"?
2) I might flashing my devices without unlocking the bootloader? And what about flashing original firmwares from Motorola?
(I ask because my bootloader is locked under status "2")
2) I tried to flash my device and, despite of several "preflashing" errors, my device still showing status 2 on bootloader, but it started showing that "unlocked bootloader warning" when it starts, is that normal? How to solve it?
3) I might flashing an older firmware (update September ) than I already have in my device (December)?
4) what is the function of recovery mode on bootloader ? I
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
OK...My first and main recommendation is DO NOT start trying to flash, mod, or do anything outside of using the phone as intended yet. These questions show that you have very limited knowledge on these subjects and if you continue as is, you will most likely get yourself into a bind you can't get out of, such as hard bricking your device.
Questions 1 and 4 are Bootloader/Fastboot/Rooting 101 topics. Until you have read up thoroughly on these, please don't think about proceeding. The rest of your questions have been answered here in the forums. I can't stress this enough: RESEARCH, READING, AND READ SOME MORE!!! No one here is obligated to help you fix any mess you get into so you need to be able to help yourself first. If you have attempted to fix an issue, and can give some details on what has been tried, you will find that most likely, there will be some who will step forward to assist, but most will not rehash a full step by step of everything.
Please do not think I am trying to blow you off. I am merely trying to prevent you from creating a problem that cannot be fixed. Having at least a basic working knowledge of how FastBoot, Bootloader, and flashing ROMs work on this device is a must. But I will answer your question 3: Do not under any circumstances try to "downgrade" your stock rom on the phone to a previous security update. This does create major issues.
@Belotto
2. Only upper/the same version of stock rom.
Status code 2 - locked by user. Did you buy used phone?
4. Recovery mode(stock, 3e) is for factory reset f.e.
dzidexx said:
@Belotto
2. Only upper/the same version of stock rom.
Status code 2 - locked by user. Did you buy used phone?
4. Recovery mode(stock, 3e) is for factory reset f.e.
Click to expand...
Click to collapse
I haven't. I have unlocked , used custom roms for a time and flashed stock and locked again before. Did it just following to guides available here.
In that time I did not have any trouble doing that lol
Sent from my XT1575 using Tapatalk
Belotto said:
I haven't. I have unlocked , used custom roms for a time and flashed stock and locked again before. Did it just following to guides available here.
In that time I did not have any trouble doing that lol
Click to expand...
Click to collapse
Just in case you are not aware, having an unlocked bootloader does not prevent you from taking OTA updates. You can just leave it unlocked. The unlocked bootloader warning doesn't bother me so I just ignore it.
If you just wanna get rid of bootloader warning then look at
https://forum.xda-developers.com/mo...o-remove-unlocked-bootloader-warning-t3201141
Make sure you are on stock(software​ status: offical)
You will recieve the ota
Thanks all you guys.
Despite of some strange things, I could take out the warning logo.
Now, its "oficial", status "2" and no warning. So I can sell it without discussion.
Hi!
I just rooted my S8 today for the first time and within 5 mins I got this: Only official released binaries are allowed to be flashed
I know what I did but not why it happened.
Installed:
TWRP
RMM State Bypass
Magisk
Samsung Antiroot removal
Cause:
I open Magisk - Accepted the prompts to update and followed whatever it asked - about 3 options if I recall.
Then it said reboot; then boom! Only official released binaries are allowed to be flashed.
Cant remember what it was but it was the third prompt - first was magisk manager v (****whatever), second I think was similar to magisk manager, third... cant remember but it had a pop up asking how to flash and I hit the "recommended" option.
Then I spent hours trying to fix it Got it after 6 beers and a few hours of screwing around.
But what causes this?
Ive been seeing a lot of XDA threads showing it can happen by a random reboot?? Is this a common thing?
I rooted after using it since launch with no issue so now I'm a little worried about trying to use the S8 rooted if this is something that can happen.
I want to play with xposed and magisk but this reboot hell is a little scary.
I have got it up and running again today - Had to spoof the date to get OEM Unlock to reshow up :good:
Rooted and on Aug 1 security update.
Is there something I should NOT do to avoid this error? I got it within 5 mins because I accepted the update promps then it flashed and reboot.
Damn... Rebooted and same error. Terrible
I think its tied to Knox... Restore and going back to stock
I believe Knox and RMM state are two different security features. The RMM state is for bootloader unlocking control.
I would say the RMM bypass zip didn't work did you allow twrp to make system modifications before flashing.
Also there is a ver 2 rmm state bypass
kingoddball said:
Damn... Rebooted and same error. Terrible
I think its tied to Knox... Restore and going back to stock
Click to expand...
Click to collapse
I've only ever seen this happen when OEM unlock is disabled, then rebooted. That will for sure cause this. But if your OEM unlock was definitely enabled then it's very strange. Aslong as you followed the steps exactly then you should be fine. Did you flash twrp, then format, then after format, copy rmm state fix zip to sd then flash? Other than I see no reason why it's happening
callumbr1 said:
I've only ever seen this happen when OEM unlock is disabled, then rebooted. That will for sure cause this. But if your OEM unlock was definitely enabled then it's very strange. Aslong as you followed the steps exactly then you should be fine. Did you flash twrp, then format, then after format, copy rmm state fix zip to sd then flash? Other than I see no reason why it's happening
Click to expand...
Click to collapse
Yes sir, I was unlocked, did the format and then installed the files.
It is a little odd. Potentially RMM v2 noted above could be the difference but unsure. Not really wanting to try again for a 3rd time
We'll see how bored I get on the weekend, maybe try again.
spawnlives said:
I believe Knox and RMM state are two different security features. The RMM state is for bootloader unlocking control.
I would say the RMM bypass zip didn't work did you allow twrp to make system modifications before flashing.
Also there is a ver 2 rmm state bypass
Click to expand...
Click to collapse
I dont know if I allowed it - I think I left it read only as it's what the instructions said to do. But it flashed magisk correctly so unsure.
Edit: Is there an XDA guide for rooting the S8? I used one from youtube which not have been the best?
kingoddball said:
I dont know if I allowed it - I think I left it read only as it's what the instructions said to do. But it flashed magisk correctly so unsure.
Edit: Is there an XDA guide for rooting the S8? I used one from youtube which not have been the best?
Click to expand...
Click to collapse
There are a few guides for this but try this guide as it incorporates everything in one :.ie installing twrp,rooting,OEM fix and data mount fix for twrp.
This would be better than giving you 3 or 4 seperate threads to look through. With twrp use latest version 3.2.3.0.
Read through the guide and comments just to make sure it suits your needs
https://forum.xda-developers.com/ga...ment/fix-data-mount-fix-s8-twrp-oreo-t3769254
kingoddball said:
I dont know if I allowed it - I think I left it read only as it's what the instructions said to do. But it flashed magisk correctly so unsure.
Edit: Is there an XDA guide for rooting the S8? I used one from youtube which not have been the best?
Click to expand...
Click to collapse
https://forum.xda-developers.com/ga...pment/recovery-twrp-galaxy-s8-exynos-t3595102
When installing twrp, swipe to allow modifications
callumbr1 said:
https://forum.xda-developers.com/ga...pment/recovery-twrp-galaxy-s8-exynos-t3595102
When installing twrp, swipe to allow modifications
Click to expand...
Click to collapse
Ok... So... I did what that page said, tried out the new file as noted, allowed modifications and... Boom - first reboot red error.
I'm trying to flash back to stock but now I'm trying to fix this: <ID:0/010> Complete(Write) operation failed.
I'll get this flashed back today and leave it there.
NOT sure if this is a consideration but I am on the September 2018 security update.
DOA: Phone is in a dead loop. Cant flash.
galaxy s8 check fail (boot loader) device 4 binary 3
If I skip the BL file I get some other crap errors. What the hell.
Smart Switch wont recognise the phone. says not unrecognised.
FINALLY FOUND A V4 bootloader image!
G955FXXU4CRI5
http://samsung-updates.com/device/?id=SM-G955F
Damn this phone is a *****!
kingoddball said:
Ok... So... I did what that page said, tried out the new file as noted, allowed modifications and... Boom - first reboot red error.
I'm trying to flash back to stock but now I'm trying to fix this: <ID:0/010> Complete(Write) operation failed.
I'll get this flashed back today and leave it there.
NOT sure if this is a consideration but I am on the September 2018 security update.
DOA: Phone is in a dead loop. Cant flash.
galaxy s8 check fail (boot loader) device 4 binary 3
If I skip the BL file I get some other crap errors. What the hell.
Smart Switch wont recognise the phone. says not unrecognised.
FINALLY FOUND A V4 bootloader image!
G955FXXU4CRI5
http://samsung-updates.com/device/?id=SM-G955F
Damn this phone is a *****!
Click to expand...
Click to collapse
Ok so what error did you get
The device 4 binary 3 error in Odin means you are flashing older firmware than what is on your phone
Software updates seem to make things harder
If still interested have a look at this thread below l think this is based on latest update (your firmware version).
https://forum.xda-developers.com/galaxy-s8/how-to/guide-how-to-root-galaxy-s8-crgh-rom-t3846009
Hi.
I just bought myself a used nexus 6p and im thinking of rooting it to get some more customization done
Before i only used Samsung phones which had this flash counter thing and then knox that kept the number of flashes to void the warranty and all. Is there this kind of measure on 6p or it's just the same as it was before {no triangles or anything) when i flash stock and lock the bootloader after i change my mind?
McXred said:
Hi.
I just bought myself a used nexus 6p and im thinking of rooting it to get some more customization done
Before i only used Samsung phones which had this flash counter thing and then knox that kept the number of flashes to void the warranty and all. Is there this kind of measure on 6p or it's just the same as it was before {no triangles or anything) when i flash stock and lock the bootloader after i change my mind?
Click to expand...
Click to collapse
No, only samjunk does stupid **** like that.
If your BL is unlocked which it should be if you are on anything other than stock, you will see a warning message each time you boot the phone. And before you act like you have ocd or something, NO that message can not be removed.
Lawlrus said:
No, only samjunk does stupid **** like that.
If your BL is unlocked which it should be if you are on anything other than stock, you will see a warning message each time you boot the phone. And before you act like you have ocd or something, NO that message can not be removed.
Click to expand...
Click to collapse
I haven't unlocked the bl yet as there was no point since I didn't want to root before I got the answer from you. I know how to read tutorials and I'm very familiar with flashing so that's no probs for me. Doesn't the message disappear after you lock the bootloader? (Just assume that I went to custom ROM didn't like it got back to stock ROM and locked the bl) will the message still be there? Because I think it says 'your phone can't be checked for corruption" but it says so only if the bl is unlocked not all the time after it's been unlocked doesn't it?
McXred said:
I haven't unlocked the bl yet as there was no point since I didn't want to root before I got the answer from you. I know how to read tutorials and I'm very familiar with flashing so that's no probs for me. Doesn't the message disappear after you lock the bootloader? (Just assume that I went to custom ROM didn't like it got back to stock ROM and locked the bl) will the message still be there? Because I think it says 'your phone can't be checked for corruption" but it says so only if the bl is unlocked not all the time after it's been unlocked doesn't it?
Click to expand...
Click to collapse
Right, it shows that message when the BL is unlocked, once you relock your BL that *should* go away, never tried it because I don't plan on even being back on stock with no root.
If you do any modifications to the device even root, or using a stock custom ROM like we have, it is suggested to NOT relock your BL, while on it. Keep that in mind.
You want to go back to full stock to lock it, then reflash the factory image
I picked up a Galaxy Tab E at a thrift shop. Got it to hard/factory reset, but can't get past the FRP screens. I tried all the YouTube guides and none of them work.
Do I need to root the entire device?
Or is there a bootloader that will do the trick instead, or do I need a new ROM?
Odin, TWRP. etc. are all new to me... it's been a while since I rooted a device...
Any guidance would be appreciated.
Kevin50seven said:
...
Any guidance would be appreciated.
Click to expand...
Click to collapse
Anyone?
If there is more information that I need to post, please let me know what you're looking for.
IGNORE THIS THREAD. (I posted in a more relevant thread after reading through it and trying some rooting processes)
Rooting by itself will not get past FRP lock. I'm not sure if its possible to flash a custom recovery via Odin without first enabling developer options and usb debugging but I would think not. ijdk. Never tried. Perhaps if you could flash TWRP you could then flash a custom rom and thus bypass FRP. (Maybe).
I was unsuccessful in every attempt I made, in spite of hours upon hours of research and attempts. Even bringing it to a local Samsung factory authorized service centre was unfruitful.
To anyone experiencing the same frustration, I finally got it unlocked for $25 USD from UnlockJunky.
Mr. JAVI said:
Rooting by itself will not get past FRP lock. I'm not sure if its possible to flash a custom recovery via Odin without first enabling developer options and usb debugging but I would think not. ijdk. Never tried. Perhaps if you could flash TWRP you could then flash a custom rom and thus bypass FRP. (Maybe).
Click to expand...
Click to collapse
You do have to enable developer options and turn on usb debugging. How you do that on a frp locked device idk