Earlier this week, AT&T (United States) pushed an Android update to my phone - wonderful I thought. About halfway through the upgrade it hung-up literally for about 1-1/2 hours.
I had to reboot after making sure I was fully charged and voila! I owned a brick.
I *MAY* have rooted this phone about a year ago, but I'm not really sure.
I've downloaded 6 root image and restore files. Every time I try to download them to my phone, I get a "SW REV CHECK FAIL - FUSED 3 > binary 0" error. When I use Odin, I get a CRC failure.
HELP.
I need my phone to be a phone, not a brick.
Thanks all.
-Frank
Was your phone rooted when you took the update? If it was, this may have caused the issue. I have an s3 from Bell Canada and I had to unroot it to get the installation to complete.
Which update was being installed? Do you have the 4.3 bootloader on your phone?
The swrev failure is a protection measure to keep you from truly bricking it by downgrading the bootloader. You need to push a custom recovery via Odin (if you don't already have one installed) and use that to flash the modified 4.4.2 ota or custom rom of your choice. The ota is in the general section, custom ROMs are in the development section. Just make sure to read and follow the instructions on the rom installation.
Sent from my SAMSUNG-SGH-I747 running TMS3KK-2.0
I wouldn't flash the ota in attempt at fixing a brick. I believe enewman17 has the recovery flashable firmware available in one of his threads.
I'm really frustrated. I've been trying to update this Galaxy S3 for days now with no success. Currently I am running on Slimkat 7.0. It's sometimes slow and buggy and needs some updating.
For reference, this is the phone at its current state:
- Bootloader: i747ucalh9 (literally taken from the fail message when trying to update to any other bootloader)
- Modem/firmware (?): I747UCLH9
Here's what has happened, greatly summarized (note I'm using CM6.0.4.7 for all of these operations, and when I say "update", I mean "flash"):
- I tried updating to Slimkat 9 but received no signal. I gave up on it entirely for a while
- I tried installing various LP ROMs, including CM12.1.
- I had 12.1 running for a bit, but I had no connectivity. LTE, 3G,H+ nothing.
- I tried installing a newer modem (this thread. Finally at MJB, I could actually get connectivity in some of the newer ROMs (including Slimkat 9)... but it was very erratic. It would just randomly oscillate between LTE and 3G and H+. This also broke CM12.1 entirely.
- Again, the above problem was always present. Most of the LP ROMs would just bootloop me, though. The only one that worked was Cyanide L... which I didn't really like.
- I thought maybe the issue was the bootloader. My bootloader is still i747ucalh9. So I tried updating it to various bootloaders from here, but none of the updates will work. Literally, they give me error 6 or 7 and pretty much essentially tell me that I can't do it.
- So after repeating the cycle of "let me try to update this" several times and having the update fail on me, I'm still stuck at Slimkat 7 as the only thing that worked on LTE (note the past tense). Worse yet, I tried simply downgrading my modem to match my current bootloader version, but that made things worse than better. I am now stuck at 3G... which just recently went back to LTE. Talk about erratic.
- I also tried going full stock by flashing this: http://forum.xda-developers.com/showthread.php?t=2363882 But it expects 5 arguments for format, and got 3... or something. Failed hard.
So, I'm pretty much at the end of my rope here. I really might just go and grab a new phone at this point. I just really don't want to because this thing still works fine.... I guess I got unlucky and am at a version of the bootloader that is difficult to update from. I can't seem to go anywhere with this thing. Anyone have any ideas? Do I need to use a different recovery?
Thanks...
First and foremost, verify your bootloader. Install the Samsung phone info app, or in a terminal app or adb shell enter:
Code:
getprop ro.bootloader
If you're on any of the older bootloaders (the ones that do not end in MJB, NE4, or NJ1) there are two ways you can go (you probably will be given the age of your modem). If you're on any of the ones that end in MJB, NE4, or NJ1 you've got to be a lot more careful because downgrading them will hard brick your phone (Odin back to stock is not an option anymore).
Option 1: If you're on the older bootloaders, you can go to sammobile.com, grab the 4.1.1 firmware from there and flash it with Odin. Do not do this if your bootloader ends in MJB, NE4, or NJ1 (can't stress that enough). This will reset your phone completely to stock. You should now start getting OTA updates. They will be incremental updates, you'll have to take at least three or four to get up to date on bootloader and modem and they're big downloads. They will come every 24 hours, but you can cheat that by setting your system time forward 1 day to make them a little more rapid fire. This is a nice, safe way to get your firmware current. Once you're up to NJ1 firmware you can use Odin to flash a custom recovery and get back to custom ROMs; I'd recommend TWRP 2.8.6 if you're going to be flashing newer ROMs as CWM and Philz aren't as up to date and sometimes give problems with newer ROMs.
Option 2: I'm pretty sure your version of CWM is a big part of your problem. If you're going to be flashing lollipop you ought to update your recovery to TWRP 2.8.6; easiest way to get it is just use the Flashify app. I'd get that recovery up to date before messing with bootloaders too. Next get your firmware up to date. If your bootloader version is before MJB, then you have to start with MJB. Then update to NE4. Then update to NJ1. It has to be done incrementally, and the bootloader and modem must match on the newer firmwares, or you'll hard brick. This thread has recovery flashable MJB and NE4 bootloaders/modems; the bootloader and modem are packaged together in the same zip so you can't get out of sync. This thread has recovery flashable NJ1 bootloader/modem. This will get your firmware all up to date, and data should start behaving on newer kitkat and lollipop ROMs. This route is a lot more risky than the OTA route described above because of all the manual steps you have to take, but you could get it done quite a bit faster if you're confident in your abilities. Just read those linked threads very, very carefully and make certain you understand.
Good luck.
jason2678 said:
First and foremost, verify your bootloader. Install the Samsung phone info app, or in a terminal app or adb shell enter:
Code:
getprop ro.bootloader
If you're on any of the older bootloaders (the ones that do not end in MJB, NE4, or NJ1) there are two ways you can go (you probably will be given the age of your modem). If you're on any of the ones that end in MJB, NE4, or NJ1 you've got to be a lot more careful because downgrading them will hard brick your phone (Odin back to stock is not an option anymore).
Option 1: If you're on the older bootloaders, you can go to sammobile.com, grab the 4.1.1 firmware from there and flash it with Odin. Do not do this if your bootloader ends in MJB, NE4, or NJ1 (can't stress that enough). This will reset your phone completely to stock. You should now start getting OTA updates. They will be incremental updates, you'll have to take at least three or four to get up to date on bootloader and modem and they're big downloads. They will come every 24 hours, but you can cheat that by setting your system time forward 1 day to make them a little more rapid fire. This is a nice, safe way to get your firmware current. Once you're up to NJ1 firmware you can use Odin to flash a custom recovery and get back to custom ROMs; I'd recommend TWRP 2.8.6 if you're going to be flashing newer ROMs as CWM and Philz aren't as up to date and sometimes give problems with newer ROMs.
Option 2: I'm pretty sure your version of CWM is a big part of your problem. If you're going to be flashing lollipop you ought to update your recovery to TWRP 2.8.6; easiest way to get it is just use the Flashify app. I'd get that recovery up to date before messing with bootloaders too. Next get your firmware up to date. If your bootloader version is before MJB, then you have to start with MJB. Then update to NE4. Then update to NJ1. It has to be done incrementally, and the bootloader and modem must match on the newer firmwares, or you'll hard brick. This thread has recovery flashable MJB and NE4 bootloaders/modems; the bootloader and modem are packaged together in the same zip so you can't get out of sync. This thread has recovery flashable NJ1 bootloader/modem. This will get your firmware all up to date, and data should start behaving on newer kitkat and lollipop ROMs. This route is a lot more risky than the OTA route described above because of all the manual steps you have to take, but you could get it done quite a bit faster if you're confident in your abilities. Just read those linked threads very, very carefully and make certain you understand.
Good luck.
Click to expand...
Click to collapse
Thanks a lot for the help! I actually did/tried a majority of this an hour or two before you posted that, except the latest firmware update link you supplied. I knew it existed and I had seen that thread before, but I couldn't dig up the link again before I had to go to work. Thing is I kind of wanted to avoid Odin for some reason but I finally gave up and used it. And yeah I already knew my bootloader version. The phone told me when it failed to update the bootloader lol.
Here's what happened thus far:
- I used Odin to flash the sammobile 4.1.1. The flashing worked just fine, but booting into it did not. It hung on the Samsung logo. So, OTA updates were out the window.
- I have no idea why, so I just used Odin to flash TWRP onto it afterwards (from here)
- I tried one of the ROMS. Data still didn't work.
- I used the thread you linked to update to MJB bootloader and whatnot. The update went fine.
- Tried another few ROMs. Data worked, but LTE was still erratic.
- Updated to NE4 and then grabbed the deoxed stock ROM.
- The deoxed stock rom failed to boot (stuck at ATT globe logo). For some reason my phone can't use stock ROMs.
- So again used Odin to put TWRP onto the phone
- Installed various LP ROMS. Again the data was erratic and plus the battery life was horrid.
- Tried getting the ktoonsez kernel. My service was murdered.
- Gave up on LP. Tried Slim 9.0. Erratic data.
- Tried Liquidsmooth 4.4.4 instead.
Currently that's kind of where I'm at. The LTE data works fine (takes a bit to get up and running after reboot though) and thus far everything is okay (though that can quickly change considering I haven't done much of anything), so I don't even know if I want to mess with it anymore. It looks like this specific ROM includes a custom kernel. So I'm guessing it's an incompatibility between the kernel and the firmware version on the other ROMs. It seems like most of the LP roms have horrible battery life (back of my phone feels like a furnace on them), so I'm not even sure if I want to do that last firmware update to use them.
It'd be kind of nice to use the OTA but apparently my ability to go stock in any form or fashion is just totally borked.
Thanks for the post though, that's pretty gold. I'm sure someone in a situation like me where they have a super old firmware will find this thread of some use as it has actual instructions and links to what you need to do to get up and running. Before you posted that, I had to go digging around pretty much everywhere figuring out what and where was going wrong.
Glad you've got it mostly working.
You might have been able to get that stock ROM to boot if you had booted into the stock recovery and run a full wipe. Touchwiz ROMs can be tough to get running after being on AOSP. As a general progression try to format internal storage with TWRP (the wipe where you have to type "yes" to confirm), if that doesn't work try a wipe with Philz, and if that doesn't work nothing, not even Odin, is effective as a wipe in the stock recovery.
Thanks for typing all this out I believe it will help me put cm12.1 official on a friends phone.
Are these the steps?
1) verify latest software
2) twrp via Odin
Alt 2) root via apk then use rashr or similar to flash twrp
3)wipe
4)In twrp install official d2att from cm website
5) install current gapps
6) profit
I'm not new to this at all but I've never even touched an att gs3 and I know most devices have their quirks and I don't want to brick.
Also does towel root work on this? I don't mind Odin but I can do this on the fly I think if I can attain root.
Sent from my DROID RAZR M using XDA Free mobile app
mrkhigh said:
Thanks for typing all this out I believe it will help me put cm12.1 official on a friends phone.
Are these the steps?
1) verify latest software
2) twrp via Odin
Alt 2) root via apk then use rashr or similar to flash twrp
3)wipe
4)In twrp install official d2att from cm website
5) install current gapps
6) profit
I'm not new to this at all but I've never even touched an att gs3 and I know most devices have their quirks and I don't want to brick.
Also does towel root work on this? I don't mind Odin but I can do this on the fly I think if I can attain root.
Sent from my DROID RAZR M using XDA Free mobile app
Click to expand...
Click to collapse
Yep. You've got it. If you're on the latest and greatest firmware I think the towelroot exploit has been patched, unless geohot has retaken the lead in that arms race.
Easiest way to root on this phone since the bootloaders are unlocked is to just use Odin to flash a custom recovery then use the custom recovery to flash SuperSU. There's just a little trick to it. Store SuperSU.zip somewhere on your phone before flashing the custom recovery. Uncheck everything but f.reset time when you use Odin; don't let it auto reboot. Upon success pull battery. Replace battery and boot straight into recovery with vol up + home + power. If you mess up and boot into unrooted stock ROM with a custom recovery it will get overwritten with a stock recovery and you'll have to Odin custom recovery back onto it and try again.
I would do this to root your stock ROM just to execute this command in a terminal app or adb shell before any more serious flashing:
Code:
su
reboot nvbackup
That fixes a derp and gives you a working efs backup on a few backup partitions built into your phone instead of a blank one. Highly recommended before doing any ROM flashing. This will just look like a pretty normal reboot. You might see a quick flash of tiny blue text if you're watching for it.
Then you're ready to make a nandroid backup (just in case), wipe, and flash away. Take a look at LiquidSmooth if you're looking for a good lollipop ROM.
Nice... So the recovery partition gets rewritten every boot up until a custom ROM is installed and the efs can disappear... This is why you always ask questions.
Thanks for the suggestion on the ROM but I think I'll stick to official cm12.1 it's not my phone and that should be a nice readily updatable bland flavor of lollipop.
Sent from my DROID RAZR M using XDA Free mobile app
mrkhigh said:
Nice... So the recovery partition gets rewritten every boot up until a custom ROM is installed and the efs can disappear... This is why you always ask questions.
Click to expand...
Click to collapse
At the Android 4.3 update it was noticed that flashing a custom recovery would be overwritten by the stock recovery on the initial reboot unless following the method Jason described. Another solution was to delete two lib or .so files. On devices still on stock recovery, stock recovery does not overwrite itself.
There is a blank EFS partition on the device intended for a backup. The nvbackup command populates that partition with an image which will rebuild your EFS if it is lost during a modem update or ROM flash. The loss of EFS does happen. I believe wanam, of the xposed module fame, created an EFS backup tool for Samsung devices. I don't believe he updates it any longer because he rolled the functionality into a partition backup tool, the later is in the PlayStore listed under a different creator name, yet it's still him.
So I'm finally going to take the plunge, and update my boot loader/modem.. I never messed with it because all the Roms I used always worked.. I want to try lollipop, but due to old bootloader my phone won't boot with those Roms..
I'm on UCDLK3 bootloader/modem.. I know I have to upgrade to MJB, NE4, then NJ1 in that order in increments..
So my question: can I upgrade from LK3 straight to MJB with out any problems?? Or is there something I need to flash before I can get to MJB?? I think I can go straight to MJB, but better safe then sorry..
I know downgrading after upgrade most likely will brick.. Any information is appreciated... Oh, its an ATT I747..
coolwhipp420 said:
So I'm finally going to take the plunge, and update my boot loader/modem.. I never messed with it because all the Roms I used always worked.. I want to try lollipop, but due to old bootloader my phone won't boot with those Roms..
I'm on UCDLK3 bootloader/modem.. I know I have to upgrade to MJB, NE4, then NJ1 in that order in increments..
So my question: can I upgrade from LK3 straight to MJB with out any problems?? Or is there something I need to flash before I can get to MJB?? I think I can go straight to MJB, but better safe then sorry..
I know downgrading after upgrade most likely will brick.. Any information is appreciated... Oh, its an ATT I747..
Click to expand...
Click to collapse
Since you are on LK3 you may want to considr applying the free sim/carrier unlock method before upgrading; that is if you are on stock LK3 and you have not previously carrier unlocked your device.
There was an OTA release for the MG2 stock ROM, I believe that was 4.1.2. You may want to go to that before MJB. Did you make the nvbackup suggested by Jason?
Why would I do a carrier unlock, if I'm not switching carriers?? And if I do it, will I be able to use the same carrier?? Just seems like a waisted step for me.. But idk..
Jason's first post, option 2 is how I was planing to update.. And no, I haven't done the nvbackup yet.. How would I apply that backup if things go wrong? Not really sure what a nvbackup is..
Any information is appreciated..
coolwhipp420 said:
Why would I do a carrier unlock, if I'm not switching carriers?? And if I do it, will I be able to use the same carrier?? Just seems like a waisted step for me.. But idk..
Jason's first post, option 2 is how I was planing to update.. And no, I haven't done the nvbackup yet.. How would I apply that backup if things go wrong? Not really sure what a nvbackup is..
Any information is appreciated..
Click to expand...
Click to collapse
There is a command to manually trigger the restore routine. I think it's
Code:
reboot nvrestore
but don't hold me to that. I'd never execute that command except if in dire need. The problem with this phone is there is an automatic routine that can be triggered in the event of a bad flash that will overwrite your nvram with the backup, even if the backup is blank. I don't think the backup stores anything modem specific, but I've never been able to confirm that. So I've always done it again after updating modems (only had to once).
Having the phone sim unlocked can be nice if you plan on traveling internationally. Otherwise, potential future carrier hopping or added resale value are the only reasons to do it.
coolwhipp420 said:
Why would I do a carrier unlock, if I'm not switching carriers?? And if I do it, will I be able to use the same carrier?? Just seems like a waisted step for me.. But idk..
Jason's first post, option 2 is how I was planing to update.. And no, I haven't done the nvbackup yet.. How would I apply that backup if things go wrong? Not really sure what a nvbackup is..
Any information is appreciated..
Click to expand...
Click to collapse
If you will never be switching carriers, nor ever sell/give/trade the phone to someone who will switch, then it is an unecessary step to do the carrier unlock.
I see Jason beat me to answering both of your questions.
I'm going out of my mind. I have two T-Mobile phones, a Galaxy s4 SGH-M919 and a Galaxy S5 SM-G900T, that are locked and I have been trying to unlock them. I paid for unlock codes from three on line services and all three said they could not provide the unlock codes.
Then I looked into some of the procedures that claimed to be able to unlock both phones. Again very much confusion as to what worked and what did not and mostly where the actual starting point was. To the best of my memory, only one of the procedures stated that the phone had to be at the baseline (Android revision level when released) in order for the procedures to work but I found this our rather quickly when the initial code entered brought me nowhere or to the wrong screen.
Next step was to downgrade to the baseline. I tried the S4 first downloading the OEM 4.2.2 version, the 4.4.2 version and the 4.4.4 version currently on my phone. Using Odin (never could get Kies to work) I flashed the 4.2.2 version and got an error right after the boot file was flashed. When I booted the system I got an error message indicating the flash had borked the OS. Then I found out that it is not possible to download from the 4.4.4 version, even though I found some listing stating that it is possible, but I was able to flash it using Odin and restore the phone.
A few months ago when doing a wipe in TWRP I decided to wipe the data, system and Internal Storage folders, only to find that it would not boot up. I was able to restore using Odin.
My question here is, if I have the 4.4.4 version and install TWRP, delete the data, system and Internal Storage folders as I accidentally did previously, will I be able to flash the 4.4.2 or 4.2.2 versions? It seems like a possibility that at least deleting the folder the boot stuff is in might work. Comments please......
Hey guys it's been a long time since I've done anything rather than run the stock os so im a bit out of practice...
This is the version I am looking to install:
ROM][SM-P605][9.0] Unofficial LineageOS 16.0 for lt03lte
It states: "-Be sure you are on 5.1.1 Bootloader and Modem (Flash 5.1.1 firmware via Odin) !"
And I am not sure how to confirm this...
If anyone could give me a hand I have attached "screenshots" of the about page.
Thanks
Jonathan
I have found a couple ways to verify this. First you can root your device and install Root Checker Pro (and maybe others). There is a tab in RCP that is called build info and it has the bootloader listed.
You second option is to install a terminal application and run the command getprop ro.bootloader and you will see your versions listed as well. Please note you must make sure you use the right ROM for your system. For example the version 9 you linked above will not work on my tablet due to my CPU.
In my case the boot version is P600UEUC0B1.
I flashed this version 7.1 ROM and use it on my Galaxy Note 2014 Edition (The Exynos processor) but it requires a 5.1.1 boot loader (per the page) and my version works but it is not LL.
https://forum.xda-developers.com/ga...0-cyanogenmod-14-0-unofficial-builds-t3457898
You can look at this post to try and download the bootloader. I had issues with the link to get the file and used another forum post to download it. This post has the version as P600XXUDPL1 once updated but this will not install on my device.
https://forum.xda-developers.com/showpost.php?p=71355516&postcount=1247
My steps
I rooted my device (used the proper tools, set USB debugging, etc... per the root method I used)
I installed the recovery manager (TWRP in my case)
Went through the process to update my bootloader per the ODIN link above
Factory Reset my device
Booted into recovery
Used the ADB sideload to get the ROM on my device
Used ADB sideload to install Google apps
Set up device
Installed SPenCommand to get my pen functions back (may be other options out there)
Hello!
Been studying forums for a couple days but can't seem to get to a definitive answer.
Here's all I want - get android 9.0 on my phone - I don't care about saving data, unlocking bootloader or not, etc. It can be a custom ROM as long as it's stable. Ideally I'd like to put the stock RETAIL version on it. There are so many posts and many of them end of last year when PIE dropped but I can't find something that really summarizes for this model.
1. How to unlock bootloader and root if need be (https://gist.github.com/eexit/e6d5fc0984e1c7f25376d3dafa819792)
2. How to flash stock PIE on this phone
3. How to install custom recovery
(How does Magisk play into all this)
4. Stable custom ROM if needed?
If I'm missing something obvious, I'm ok taking the heat, but, if not and someone has this phone and has some answers, I'd be grateful!
Thanks.
----------------------------------------------------------------------
UPDATE:
1. I unlocked my bootloader following moto's website - easily googleable
2. Then I just flashed the retail OEM via fast boot using commands - i.e., I downloaded the retail for 9.0, extracted in in adb folder (which has fastboot), booted phone into fastboot mode and flashed it all manually. So far it's working fine. It complains at boot about unlocked bootloader and I can't get OTA updates. I know I can still root it via guide above.
I'll post any updates as I have them.
MrRedPants said:
Hello!
Been studying forums for a couple days but can't seem to get to a definitive answer.
Here's all I want - get android 9.0 on my phone - I don't care about saving data, unlocking bootloader or not, etc. It can be a custom ROM as long as it's stable. Ideally I'd like to put the stock RETAIL version on it. There are so many posts and many of them end of last year when PIE dropped but I can't find something that really summarizes for this model.
1. How to unlock bootloader and root if need be (xx)
2. How to flash stock PIE on this phone
3. How to install custom recovery
(How does Magisk play into all this)
4. Stable custom ROM if needed?
If I'm missing something obvious, I'm ok taking the heat, but, if not and someone has this phone and has some answers, I'd be grateful!
Thanks.
----------------------------------------------------------------------
UPDATE:
1. I unlocked my bootloader following moto's website - easily googleable
2. Then I just flashed the retail OEM via fast boot using commands - i.e., I downloaded the retail for 9.0, extracted in in adb folder (which has fastboot), booted phone into fastboot mode and flashed it all manually. So far it's working fine. It complains at boot about unlocked bootloader and I can't get OTA updates. I know I can still root it via guide above.
I'll post any updates as I have them.
Click to expand...
Click to collapse
Can you elaborate on what retail version you used?
I have the same (XT1710-01 albus_C RETUS...... which actually says "albus_retail/albus" in recovery mode) and currently on 8.0.0/OPSS27.76-12-28-20/19.
When I try to side load via adb "ALBUS_RETAIL_9.0_PPS29.133-30_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip" I get an error saying: "footer is wrong", "signature verification failed" and "error 21".
Trying to load "Blur_Version.29.11.30.albus.retail.en.US" I got a version mismatch (albus vs albus_c).
You have to flash in via fastboot. Not in recovery.