Hey all, I need some help. I bricked my phone, and I can only get into download mode and recovery. Flashing through odin fails each time, and so does flashing through recovery. Gives me a status 7 error. Ive made sure I'm downloading all the proper files, but Im stumped here. My phone also isnt recognized in Kies. Ive uninstalled and reinstalled the drivers multiple times now. Im too nervous to go to an AT&T store because theyll see I voided my warranty from the recovery (using philz recovery).
Anyone got any clue on what Im doing wrong? Any help would be much appreciated.
Syst3m Deadlock said:
Hey all, I need some help. I bricked my phone, and I can only get into download mode and recovery. Flashing through odin fails each time, and so does flashing through recovery. Gives me a status 7 error. Ive made sure I'm downloading all the proper files, but Im stumped here. My phone also isnt recognized in Kies. Ive uninstalled and reinstalled the drivers multiple times now. Im too nervous to go to an AT&T store because theyll see I voided my warranty from the recovery (using philz recovery).
Anyone got any clue on what Im doing wrong? Any help would be much appreciated.
Click to expand...
Click to collapse
EDIT: In your sig, it says you have an S2? this is the S3 section.
What happened exactly to soft-brick?
The software you're flashing with Odin might not be good, try another one. Also, since you can get in recovery, you can try clean flashing the ROM you had running previous to the brick.
BWolf56 said:
EDIT: In your sig, it says you have an S2? this is the S3 section.
What happened exactly to soft-brick?
The software you're flashing with Odin might not be good, try another one. Also, since you can get in recovery, you can try clean flashing the ROM you had running previous to the brick.
Click to expand...
Click to collapse
I have an S3 now, just havent updated my sig.
And I was trying to root. I was on the latest stock 4.4.2 and flashed the wrong file by mistake. Forgot what it was. So now I cant flash any files in recovery or odin. It just fails each and every time. I know all these files cant be bad
So root wasnt successful and now I cant even revert back to stock
Kies interferes with odin. Uninstall it from your computer and try odin again.
DocHoliday77 said:
Kies interferes with odin. Uninstall it from your computer and try odin again.
Click to expand...
Click to collapse
Still didnt work. Odin let me install a recovery file, but it just wont let me install files to restore back to stock. Same with recovery, I'm still getting the status 7 error. It doesnt make any sense. Ive downloaded and redownloaded from different places, so I highly doubt that all these files are bad
Are you running the latest Philz? Sometimes, the status 7 error occurs with an outdated recovery. Have you tried flashing a custom ROM with TWRP?
audit13 said:
Are you running the latest Philz? Sometimes, the status 7 error occurs with an outdated recovery. Have you tried flashing a custom ROM with TWRP?
Click to expand...
Click to collapse
I'm running 6.0.5 - no I haven't tried TWRP
What rom were you running before? What do you want to be running now?
And what is your current firmware/bootloader version? Not sure about philz recovery, but status 7 errors usually occur when you dont have the required firmware build.
Also, at least for the T999, cm roms updater-scripts are outdated. So if we have the newest available, it still gives the status 7 errors because the new builds haven't been added. Just thought I'd mention this in case you're updated to the new kk firmware and are trying to flash a cm rom.
DocHoliday77 said:
What rom were you running before? What do you want to be running now?
And what is your current firmware/bootloader version? Not sure about philz recovery, but status 7 errors usually occur when you dont have the required firmware build.
Also, at least for the T999, cm roms updater-scripts are outdated. So if we have the newest available, it still gives the status 7 errors because the new builds haven't been added. Just thought I'd mention this in case you're updated to the new kk firmware and are trying to flash a cm rom.
Click to expand...
Click to collapse
I was running official 4.4 unrooted. I'm trying to install Likewise S5.
Install terminal emulator from the play store and enter this:
getprop ro.bootloader
If it returns I747UCUEMJB you should be ok to flash likewise and something else is preventing it. If its anyway but that, you probably need to update your base firmware/bootloaders first.
If you're still unable to boot anything, the build should be shown on the Download Mode screen. You can probably reflash your previous rom and boot to that for right now though.
I was able to get a custom ROM installed, but now I have no reception. Im guessing the bootloader needs to be updated. So I tried updating it via odin. That failed. I also tried flashing it in recovery and still got a status 7 error. Im at my whits end here
You probably need to flash your modem. Run the Terminal Emulator command I posted before, and if it returns I747UCUEMJB, flash the MJB modem. If it returns anything else, flash the modem that matches, but let us know first just to be on the safe side.
DocHoliday77 said:
You probably need to flash your modem. Run the Terminal Emulator command I posted before, and if it returns I747UCUEMJB, flash the MJB modem. If it returns anything else, flash the modem that matches, but let us know first just to be on the safe side.
Click to expand...
Click to collapse
Terminal Emulator tells me my bootloader is 1747UCUFNE4
Syst3m Deadlock said:
Terminal Emulator tells me my bootloader is 1747UCUFNE4
Click to expand...
Click to collapse
So yeah, you need the 1747UCUFNE4 baseband. Look in Settings/About Phone to know which one you have before going and flashing it.
BWolf56 said:
So yeah, you need the 1747UCUFNE4 baseband. Look in Settings/About Phone to know which one you have before going and flashing it.
Click to expand...
Click to collapse
I cant seem to find the 1747UCUFNE4 baseband,
Syst3m Deadlock said:
I cant seem to find the 1747UCUFNE4 baseband,
Click to expand...
Click to collapse
Did you check which one you have atm?
And here, from Doc http://forum.xda-developers.com/showpost.php?p=53626873&postcount=4
BWolf56 said:
Did you check which one you have atm?
And here, from Doc http://forum.xda-developers.com/showpost.php?p=53626873&postcount=4
Click to expand...
Click to collapse
Thanks a bunch, it worked!!!
Related
Hello xda,
I tried rooting my SGH-T999 and it took a while so I unplugged the USB and restarted the phone. Phone keeps saying it has encountered a problem with the current firmware, connect to KIES and select recovery. Kies does not connect to the device. I read on xda to reflash using ODIN. I have ODIN v1.85 from trying to root, is this the right version to use because I also found the ODIN3_v3.07? As far as USB driver, is there separate drivers for ODIN or are people referring to the Samsung Kies drivers (I just installed KIES). I read to do it on this screen and I also read to try to go into the recovery mode (holding vol down, home, power) and then reflashing; which should I do?
Also, I found this link on xda for the T-mobile firmware ( http://forum.xda-developers.com/showthread.php?t=1949687 ). No idea which one to choose, why are there so many, I am currently downloading the latest one
"UVDLJA
PDA: T999UVDLJA
CSC: T999TMBDLJA
Version: 4.1.1 JB
Date: Nov. 14, 2012
Sammobile Link
Samsung-Updates Link"
If I want to use the pre rooted file do I need to fix my problem first and try flashing with stock firmware or can I try to fix the issue directly with the pre rooted firmware?
Re: [Q] SGH-T999 Rooted bad, phone stuck on start screen
Use the Odin from my signature.
You can probably just flash mrRobinson's stock rooted rom to fix it. And Kies is garbage. Uninstall it.
I would like to see the root guide you used as well.
Aerowinder said:
Use the Odin from my signature.
You can probably just flash mrRobinson's stock rooted rom to fix it. And Kies is garbage. Uninstall it.
I would like to see the root guide you used as well.
Click to expand...
Click to collapse
I used this guide to root.
http://galaxys3root.com/galaxy-s3-r...gh-t999sgh-i747sph-l710-fail-proofnoob-proof/
Before I try to flash with mrRobinson's stock rooted rom which I just finished downloading, I will uninstall Kies and install the USB drivers first?
Thanks for your response Aerowinder.
I got USB drivers earlier today that was a newer version but I will be using the files from your sig since it works :good:
Another question I had was, does the phone need to be in download mode or can I do it in the screen where it says "encountered problem with current firmware. Connect to KIES and select recovery" screen when I flash with Odin? I know normally I would have to be in the download mode but I'm wondering if it is the same when I am getting this error.
Re: [Q] SGH-T999 Rooted bad, phone stuck on start screen
Phone must be in download mode to use Odin.
The drivers in my signature are not the newest, you are correct. They are the last version I found that work without any issues. The newer ones pretty much suck. Constant disconnects mainly.
Aerowinder said:
Phone must be in download mode to use Odin.
The drivers in my signature are not the newest, you are correct. They are the last version I found that work without any issues. The newer ones pretty much suck. Constant disconnects mainly.
Click to expand...
Click to collapse
Awesome thanks!
So I am watching the root video on your sig, so in my case I would choose the rom I want for the PDA instead of the cwm-touch-6.0.2.3-d2tmo right? Should I extract the rooted firmware or just load the zipped file onto ODIN PDA?
Re: [Q] SGH-T999 Rooted bad, phone stuck on start screen
Root66 does not contain a recovery so you still need to flash one of those but don't use my link. Get ROM Manager once you're up and running.
If you don't care about the flash counter you can flash the tar in my signature.
Sorry to interject here but you can get an Odin flashable recovery from here.
You can flash one of these and then flash Root66 right after and you'll have stock Rooted ROM with stock or custom recovery (your choice).
Not to be a buzzkill or anything but you are probably the 5th or 6th person in the past 2 weeks that have encountered the "encountered problem with current firmware. Connect to KIES and select recovery" error. Only a few of them have been able to pull out of it. The ones that have, have had to flash Root66 (or their device respective FW) multiple times.
I hope that you can get out of it and please post here if you do. Aerowinder knows what he is doing. Follow his lead.
Aerowinder said:
Root66 does not contain a recovery so you still need to flash one of those but don't use my link. Get ROM Manager once you're up and running.
If you don't care about the flash counter you can flash the tar in my signature.
Click to expand...
Click to collapse
Okay I don't care about the counter, I just want my phone to work and I'll be happy.
But now I'm getting a little confused about the cwm recovery.
So just to be clear, you are saying I need to flash a recovery (cwm-touch-6.0.2.3-d2tmo in my case since I don't care about the counter), BUT do I flash the recovery before or after I flash with Root66 firmware? That part I am confused about. And do I flash one right after another or do I need to restart my phone or ODIN first?
Thank you so much for helping me out. I was freaking out this morning and I am very grateful for your help and knowledge. I hope I am not being too much of a pain or hassle with these questions. Sorry that I am quite new to this
Woody said:
Sorry to interject here but you can get an Odin flashable recovery from here.
You can flash one of these and then flash Root66 right after and you'll have stock Rooted ROM with stock or custom recovery (your choice).
Not to be a buzzkill or anything but you are probably the 5th or 6th person in the past 2 weeks that have encountered the "encountered problem with current firmware. Connect to KIES and select recovery" error. Only a few of them have been able to pull out of it. The ones that have, have had to flash Root66 (or their device respective FW) multiple times.
I hope that you can get out of it and please post here if you do. Aerowinder knows what he is doing. Follow his lead.
Click to expand...
Click to collapse
Woody, I went to the link you posted. What are the 4 files for?
Don't use those - they are older versions.
If you don't care about the counter, then flash the CWM in my signature using Odin (can provide TWRP tar link if that's your thing), then flash root66 using Odin. You can reboot in between... but no real reason to do so.
If you are still having issues after you flash these, drop into recovery (vol up + home) and reset factory defaults. If still having problems, only thing left to do is flash a full stock image, link also in my signature. The page you linked to does not contain the newest version because DocHolliday hasn't been around here much lately.
buzzking00 said:
Woody, I went to the link you posted. What are the 4 files for?
Click to expand...
Click to collapse
Top one is TWRP version 2.3.0.0
Second is 6.0.1.2 CWR touch version
Third is TWRP version 2.3.1.0
Fourth is Stock recovery.
Do not flash all of them. Are you a TWRP or CWR kind of person? Instead of re-typing it out, go here and I come in on post #20 on the 2nd page. Read that to the end and let us know if you understand it. Pretty easy to follow but I understand your Panic Mode, so take your time.
Aerowinder said:
If still having problems, only thing left to do is flash a full stock image, link also in my signature.
Click to expand...
Click to collapse
^^ This is what I see in his future.
Like I said above, I haven't seen too many people get out of that "Encountered..." error without some real technical expertise.
Aerowinder said:
Don't use those - they are older versions.
If you don't care about the counter, then flash the CWM in my signature using Odin (can provide TWRP tar link if that's your thing), then flash root66 using Odin. You can reboot in between... but no real reason to do so.
If you are still having issues after you flash these, drop into recovery (vol up + home) and reset factory defaults. If still having problems, only thing left to do is flash a full stock image, link also in my signature. The page you linked to does not contain the newest version because DocHolliday hasn't been around here much lately.
Click to expand...
Click to collapse
Awesome. Thanks Aerowinder!
I will try this when I get home (assuming I can go into download mode...) and post what happened
Woody said:
^^ This is what I see in his future.
Like I said above, I haven't seen too many people get out of that "Encountered..." error without some real technical expertise.
Click to expand...
Click to collapse
I will take a look at the link Woody.
I am really hoping this will work on the first try!
Okay so from reading your post Woody I can use EITHER the TWRP and CWR, but I want to use the one that is easiest to use. Which one do you guys think is easier to use?
Also, SU3.3 or SU1.04 which one should I use? Aerowinder, your sig shows both now but earlier I didn't notice the SU1.04. I just realized I only need the SU file IF the prerooted file doesn't work but just in case it doesn't I guess it is better to know.
Draw straws. I use CWM/Superuser. I use Superuser because CM comes with it. AOKP comes with SuperSU... both work fine. Just make sure you use the ones from my signature, as they are newer versions. You won't need su if you get a prerooted rom, only for stock.
Aerowinder said:
Draw straws. I use CWM/Superuser. I use Superuser because CM comes with it. AOKP comes with SuperSU... both work fine. Just make sure you use the ones from my signature, as they are newer versions. You won't need su if you get a prerooted rom, only for stock.
Click to expand...
Click to collapse
I am going to try it in an hour.
Wish me luck!
1. Download mode
2. Flash CWM
3. Flash Root66
4. Hopefully no problems
:good:
Aerowinder said:
Don't use those - they are older versions.
If you don't care about the counter, then flash the CWM in my signature using Odin (can provide TWRP tar link if that's your thing), then flash root66 using Odin. You can reboot in between... but no real reason to do so.
If you are still having issues after you flash these, drop into recovery (vol up + home) and reset factory defaults. If still having problems, only thing left to do is flash a full stock image, link also in my signature. The page you linked to does not contain the newest version because DocHolliday hasn't been around here much lately.
Click to expand...
Click to collapse
OMFG OMFG OMFG
OMFG OMFG OMFG
OOOOOOH MYYYYYY FOOOOOOOOKIN GOOOOOOOOOOOOSH
AEROWINDER AND WOODY
I LOVE YOU SO MUCH
IT WORKED AND NOTHING GOT ERASED. I THOUGHT PUTTING THE NEW FIRMWARE WOULD'VE ERASED EVERYTHING WITH THE NEW ROM BUT NOPE.
Uninstalled KIES and USB drivers.
Installed USB drivers from Aerowinders sig
So the Odin 3.07 didn't work either so I ended up using ODIN 1.85
Turned off auto reboot and left f reset on (no idea what f reset does lol)
Flashed CWM
Flashed root66 rom
Restarted phone and it was back to normal with all the data saved, but no SU (wasn't unlocked)
So reflashed CWM
Then restarted in clockwork recovery and ran super user and now the phone is rooted
Thanks for your helpful knowledge and now I am going to learn everything about android so I too can help another new android user in the (hopefully near) future.
:good::good::good: 3 thumbs up to the knowledge members above Aerowinder and Woody!
THANK YOU!
Panic mode TRANSFORMMMMM! *Panic mode has now transformed into excitement mode*
buzzking00 said:
Thanks for your helpful knowledge and now I am going to learn everything about android so I too can help another new android user in the (hopefully near) future.
Click to expand...
Click to collapse
So, ahh, are you excited? Haha. Great. Glad you got it up and running.
I hope that you do learn more about Android and share it with someone who needs help someday. When I first came, that is what someone did for me and I have tried to do it ever since. We are all still learning, including Aero and myself, so there will never be an end but rather more.
Good job and now you should make a Nandroid backup just in case you ever get in a bind again.
Well now I gotta learn how to make back-ups and what a Nandroid backup is lol.
Time to search the forums
buzzking00 said:
Well now I gotta learn how to make back-ups and what a Nandroid backup is lol.
Time to search the forums
Click to expand...
Click to collapse
That's the attitude, with Android you have to be a sponge and try to learn as much as you can. A single Google search will give you the answers you seek and making a backup is pretty much universal no matter what Rom, phone you have. Good luck
Sent from my SGH-T999 using xda app-developers app
Hi, let me first begin if there is any problem with my threads. And I want to thank XDA for letting me ask this question, im pretty much a noob from the start..
So, I recently got a replacement S4 (surprisingly from a faulty device on swappa that had warranty) and it was already updated with 4.3 MK2, I have used chainfire's CF-Auto Root and have gotten root and also have installed a custom recovery (CWM.) My problem lies when I want to flash a Custom 4.3 Rom. I have downloaded HyperDrive RSL12 (Mostly because of the note 3 features) and the required files for it. But when I go into recovery and try to flash the rom, the recovery would take a couple of minutes to do something and then say that I can't flash this rom (I saw something under the line of "bad" but I have tried again and again to redownload the rom, so I honestly don't think thats the issue) but this happens to all of the roms I want to install, and I'm not sure if it has something with the KNOX bootloader that came with the phone, but honestly, any help I get is much appreciated! I would gladly give more info to who will help me and I would do almost everything to either install custom rom or 4.2.2 stock!
Sounds like your not rooted
Sent from my SGH-M919 using XDA Premium 4 mobile app
Android_Monsters said:
Sounds like your not rooted
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
hmm.....i mean that is a possibility, i'll try rerooting again, but say if the problem doesn't lie in rooting, what other problem would be associated this?
I'd try a different ROM. That one was first for the international version I believe.
Also, you could try a different recovery. Twrp or Philz. Or just a different version of cwm. Which is what I use.
Sent from my SGH-M919 using XDA Premium 4 mobile app
You can't install stock 4.2.2 since you've updated to the mk2 bootloader (or any room base on 4.2.2). Did you check the md5 of the download file?
☞ Sent from here☜???
baseballfanz said:
You can't install stock 4.2.2 since you've updated to the mk2 bootloader (or any room base on 4.2.2). Did you check the md5 of the download file?
☞ Sent from here☜???
Click to expand...
Click to collapse
I'll be honest,I have no knowledge about md5 in general, but normally would the mk2 bootloader prevent me from installing a modified stock 4.3 rom or a 4.3 custom rom in general?
Android_Monsters said:
I'd try a different ROM. That one was first for the international version I believe.
Also, you could try a different recovery. Twrp or Philz. Or just a different version of cwm. Which is what I use.
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
For that rom, I was told I could use that rom for the t-mobile variant, but i had to download the compatible pack for that model, and I Have tried TWRP through Goo Manager, but still no luck...
LancerEvoDrifter said:
For that rom, I was told I could use that rom for the t-mobile variant, but i had to download the compatible pack for that model, and I Have tried TWRP through Goo Manager, but still no luck...
Click to expand...
Click to collapse
What version of TWRP are you using? It may just be me, but I spent all last night trying to flash Hyperdrive, Wicked, AND WarpDrive 4.3 and kept having all sorts of problems. Baseband being reported as unknown, no service, phone app FCing, Settings->About Phone->Status would crash settings, WiFi wouldn't connect for anything in the world. I literally spent about 5 hours wiping, flashing, and wiping again. I couldn't even restore an old backup of HyperDrive I had. I started thinking, I recently updated TWRP to 2.6.3.1 and everything was working fine before. I reverted back to 2.6.3.0 and I could restore my backup; I could now flash the 4.3 TW ROMs and get the correct Baseband to report, it all worked right.
TL;DR
Try using an older version of TWRP.
lordcheeto03 said:
What version of TWRP are you using? It may just be me, but I spent all last night trying to flash Hyperdrive, Wicked, AND WarpDrive 4.3 and kept having all sorts of problems. Baseband being reported as unknown, no service, phone app FCing, Settings->About Phone->Status would crash settings, WiFi wouldn't connect for anything in the world. I literally spent about 5 hours wiping, flashing, and wiping again. I couldn't even restore an old backup of HyperDrive I had. I started thinking, I recently updated TWRP to 2.6.3.1 and everything was working fine before. I reverted back to 2.6.3.0 and I could restore my backup; I could now flash the 4.3 TW ROMs and get the correct Baseband to report, it all worked right.
TL;DR
Try using an older version of TWRP.
Click to expand...
Click to collapse
I think I was using the newest version of TWRP. I don't think I have a previous version of TWRP, should I look it up on google for more info about older builds?
LancerEvoDrifter said:
I don't think I have a previous version of TWRP, should I look it up on google for more info about older builds?
Click to expand...
Click to collapse
You can go to http://techerrata.com/browse/twrp2/jfltetmo and download previous versions of TWRP. The .img files are flashed by using the dd command in a terminal emulator and the .tar files are flashed in Odin.
Some people aren't as lucky with TWRP as I have been; I've never had a real problem with any of the versions I've used. Some people have only really been able to use 2.5.0.2, so I would say to give that version a shot.
lordcheeto03 said:
You can go to http://techerrata.com/browse/twrp2/jfltetmo and download previous versions of TWRP. The .img files are flashed by using the dd command in a terminal emulator and the .tar files are flashed in Odin.
Some people aren't as lucky with TWRP as I have been; I've never had a real problem with any of the versions I've used. Some people have only really been able to use 2.5.0.2, so I would say to give that version a shot.
Click to expand...
Click to collapse
I have flash TWRP ver 2.5.0.2, but I been getting a error message saying this. BTW, this is what the log says when I try to flash the ROM
"Updating partition details...
Running boot script...
Finished running boot script.
E: Unable to open zip file.
Error flashing zip '/external_sd/Hyperdrive RLS12 S4 Final (1).zip'
Updating partition details..."
LancerEvoDrifter said:
I have flash TWRP ver 2.5.0.2, but I been getting a error message saying this. BTW, this is what the log says when I try to flash the ROM
"Updating partition details...
Running boot script...
Finished running boot script.
E: Unable to open zip file.
Error flashing zip '/external_sd/Hyperdrive RLS12 S4 Final (1).zip'
Updating partition details..."
Click to expand...
Click to collapse
Are you able to browse through the zip file on either your computer or a file browser on your phone? If you can't look through the directories within the zip, you have a bad download and will need to re-download it.
lordcheeto03 said:
Are you able to browse through the zip file on either your computer or a file browser on your phone? If you can't look through the directories within the zip, you have a bad download and will need to re-download it.
Click to expand...
Click to collapse
yea, usually when I have a bad download, Winrar would tell me the archive had a unexpected end, but that is not the case in this situation, the file has worked on my dad's s4, but i guess the problem lies in my own device
Tried to delete but don't know how
---------- Post added at 10:13 PM ---------- Previous post was at 10:10 PM ----------
lordcheeto03 said:
You can go to http://techerrata.com/browse/twrp2/jfltetmo and download previous versions of TWRP. The .img files are flashed by using the dd command in a terminal emulator and the .tar files are flashed in Odin.
Some people aren't as lucky with TWRP as I have been; I've never had a real problem with any of the versions I've used. Some people have only really been able to use 2.5.0.2, so I would say to give that version a shot.
Click to expand...
Click to collapse
Thanks for the info about using 2.5.0.2. I was finally to install a custom 4.2.2 ROM without a status 7 error.
David
I'm trying to help out a friend and update his Galaxy S3 SGH-I747. He originally had cyanogenmod installed but he restored his phone back to stock and flashed a stock recovery back to the phone. When he tries to do an OTA updated it downloads but fails to install? His current android version is 4.1.1 but his baseband is I747UCUFNE4 which if im not mistaken is for android 4.4.2 what would be the easiest way to get his phone updated to the stock 4.4.2 software?
Follow one of enewman17's how to update threads in General.
4.4.2 upgrade stops at 28%
DocHoliday77 said:
Follow one of enewman17's how to update threads in General.
Click to expand...
Click to collapse
Can you be a bit more specific?
Thanks
bmoliver said:
Can you be a bit more specific?
Thanks
Click to expand...
Click to collapse
The beauty of search: http://forum.xda-developers.com/search.php?searchid=292146343
Two threads from enewman17: UCUEMJB to UCUFNE4 firmware update; How to update SGH-I747 to UCUFNE4_4.4.2
DocHoliday77 said:
Follow one of enewman17's how to update threads in General.
Click to expand...
Click to collapse
BWolf56 said:
The beauty of search: http://forum.xda-developers.com/search.php?searchid=292146343
Two threads from enewman17: UCUEMJB to UCUFNE4 firmware update; How to update SGH-I747 to UCUFNE4_4.4.2
Click to expand...
Click to collapse
Thanks, I had found the last link (....2789917) by doing a Google search (i.e., searching within the forum was less successful).
Hey bmoliver and BWolf56,
I am in the same boat as your friend where my baseband (bootloader) version is I747UCUFNE4 but the software version is stuck at 4.1.1. AT&T is identifying a OTA update, downloading but the update is failing.
I tried the method described in http://forum.xda-developers.com/showthread.php?t=2789917. But when I am trying to flash MJB bootloader, it is failing. I read elsewhere in this forum that downgrading from UCU to MJB is not really advisable.
I am stuck in 4.1.1 and my phone is half functional at the moment with the camera, nfc, bluetooth not functional :crying:.
Was your friend able to get this resolved bmoliver?
I tried searching for a I747UCUFNE4 md5 file that I can flash using odin (just a hope that it might work) but could not find.
It would be great if one of you can point me to it.
PS: I am a complete newbie to this entire thing and so far from what I read, my phone is probably soft-bricked and am hoping that someone would guide and help me get out of this.
EDIT: One more thing that I observed is when I am trying flash something in the download mode, I get the error and "sw rev check fail fused 3 binary 0" and it fails
Thanks,
CJ
bmoliver said:
Thanks, I had found the last link (....2789917) by doing a Google search (i.e., searching within the forum was less successful).
Click to expand...
Click to collapse
jchennuri said:
Hey bmoliver and BWolf56,
I am in the same boat as your friend where my baseband (bootloader) version is I747UCUFNE4 but the software version is stuck at 4.1.1. AT&T is identifying a OTA update, downloading but the update is failing.
I tried the method described in http://forum.xda-developers.com/showthread.php?t=2789917. But when I am trying to flash MJB bootloader, it is failing. I read elsewhere in this forum that downgrading from UCU to MJB is not really advisable.
I am stuck in 4.1.1 and my phone is half functional at the moment with the camera, nfc, bluetooth not functional :crying:.
Was your friend able to get this resolved bmoliver?
I tried searching for a I747UCUFNE4 md5 file that I can flash using odin (just a hope that it might work) but could not find.
It would be great if one of you can point me to it.
PS: I am a complete newbie to this entire thing and so far from what I read, my phone is probably soft-bricked and am hoping that someone would guide and help me get out of this.
Thanks,
CJ
Click to expand...
Click to collapse
You don't want to downgrade bootloaders, that will brick your phone.
You'll have to flash NE4 with Odin (or a NE4 custom ROM through custom recovery) to get your baseband and software matching.
The thread you linked should work if you follow it to a T. If something doesn't work, let us know and be specific about what happened.
Thanks for the info BWolf56,
Sorry for asking a trivial question (just getting accustomed to the lingo used here) .
When you say I should follow it to a T, are you just referring to follow all the steps.
I tried two things
1. follow each step, but failed at step 3 since I was trying to downgrade my bootloader.
2. I jumped from step 2 to step 6 and tried to flash 4.4.2OTA.zip in recovery mode but that also failed. I dont remember the exact error I got, I can try it again to give you more details if you think it is safe.
Thanks
BWolf56 said:
You don't want to downgrade bootloaders, that will brick your phone.
You'll have to flash NE4 with Odin (or a NE4 custom ROM through custom recovery) to get your baseband and software matching.
The thread you linked should work if you follow it to a T. If something doesn't work, let us know and be specific about what happened.
Click to expand...
Click to collapse
jchennuri said:
Thanks for the info BWolf56,
Sorry for asking a trivial question (just getting accustomed to the lingo used here) .
When you say I should follow it to a T, are you just referring to follow all the steps.
I tried two things
1. follow each step, but failed at step 3 since I was trying to downgrade my bootloader.
2. I jumped from step 2 to step 6 and tried to flash 4.4.2OTA.zip in recovery mode but that also failed. I dont remember the exact error I got, I can try it again to give you more details if you think it is safe.
Thanks
Click to expand...
Click to collapse
If you jumped to #6, you didn't flash a custom recovery, which you need to flash the OTA.
I did install TWRP 2.6.3.1 which I am guessing is the custom recovery (as part of step 2) and then I tried to flash the OTA. Am I missing something here?
BWolf56 said:
If you jumped to #6, you didn't flash a custom recovery, which you need to flash the OTA.
Click to expand...
Click to collapse
jchennuri said:
I did install TWRP 2.6.3.1 which I am guessing is the custom recovery (as part of step 2) and then I tried to flash the OTA. Am I missing something here?
Click to expand...
Click to collapse
What error did you get when flashing it?
I just tried flashing it again and got the following error.
I loaded the zip into my internal SD and went to recovery mode (twrp gui, Power+Home+Volume Up)
and tried installing the zip
_______________
Updating partition details...
Running boot script...
Finished running boot script.
Installing '/data/media/Samsung_SGH-I747_4.4.2_OTA.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Package expects build fingerprint of samsung/d2u (the screen does not allowing me to scroll to the right to look at the complete line after 'd2u')
E: Error executing updater binary in zip '/data/media/Samsung_SGH-I747_4.4.2_OTA.zip'
Error flashing zip '/data/media/Samsung_SGH-I747_4.4.2_OTA.zip'
Updating partition details...
FAILED
_________________
This is the error I am getting.
Am I missing something? Please let me know if you need any more info
Thanks a ton!!!
BWolf56 said:
What error did you get when flashing it?
Click to expand...
Click to collapse
jchennuri said:
I just tried flashing it again and got the following error.
I loaded the zip into my internal SD and went to recovery mode (twrp gui, Power+Home+Volume Up)
and tried installing the zip
_______________
Updating partition details...
Running boot script...
Finished running boot script.
Installing '/data/media/Samsung_SGH-I747_4.4.2_OTA.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Package expects build fingerprint of samsung/d2u (the screen does not allowing me to scroll to the right to look at the complete line after 'd2u')
E: Error executing updater binary in zip '/data/media/Samsung_SGH-I747_4.4.2_OTA.zip'
Error flashing zip '/data/media/Samsung_SGH-I747_4.4.2_OTA.zip'
Updating partition details...
FAILED
_________________
This is the error I am getting.
Am I missing something? Please let me know if you need any more info
Thanks a ton!!!
Click to expand...
Click to collapse
Sounds like you'll have to use Odin to flash Stock.
Your build.prop is most likely borked (or has been changed to something it's not). d2u is not a variant of the S3, nor does it exist.
Thanks a ton for helping me identify the problem.
I just have to look if a stock file to flash using odin is out there somewhere.
I will post in http://forum.xda-developers.com/showthread.php?t=2789917 to see if enewman17 or someone from the community have a tar or md5 file that I can use.
I will try that and update on how it goes.
BWolf56 said:
Sounds like you'll have to use Odin to flash Stock.
Your build.prop is most likely borked (or has been changed to something it's not). d2u is not a variant of the S3, nor does it exist.
Click to expand...
Click to collapse
jchennuri said:
Thanks a ton for helping me identify the problem.
I just have to look if a stock file to flash using odin is out there somewhere.
I will post in http://forum.xda-developers.com/showthread.php?t=2789917 to see if enewman17 or someone from the community have a tar or md5 file that I can use.
I will try that and update on how it goes.
Click to expand...
Click to collapse
You can grab the stock ROM here: http://forum.xda-developers.com/showthread.php?p=33570269#post33570269
Just make sure you grab the right version.
Thanks for the pointing me there.
I could not find the stock firmware for NE4 though.
They only have MJ2, LK3, LG1, LEM versions, no MJB either.
BWolf56 said:
You can grab the stock ROM here: http://forum.xda-developers.com/showthread.php?p=33570269#post33570269
Just make sure you grab the right version.
Click to expand...
Click to collapse
jchennuri said:
Thanks for the pointing me there.
I could not find the stock firmware for NE4 though.
They only have MJ2, LK3, LG1, LEM versions, no MJB either.
Click to expand...
Click to collapse
There isn't a NE4 stock for Odin. I just noticed the post hasn't been updated in a while.
I though I could find it on Sammobile.com but they have LK3 as their latest too.
Since you somehow have the 4.4.2 modem, you can not flash anything older than the 4.4.2 firmware. Currently there is nothing that you can flash to fix this. Normally, I would say to flash an older modem, but if Odin is seeing it as already updated to 4.4.2 (SWREV 3), and the only thing you have that is 4.4.2 is the modem, flashing anything older will likely hard brick.
You need either the full stock firmware, which there is not one, Thanks AT&T!, or a recovery flashable firmware for 4.4.2. Enewman17 has this, but it will not work for you because of how the modem is flashed. For some reason, he has it patching the 4.3 modem rather than including the full updated one like with the other partitions. If someone makes the same thing, but with the already updated modem, you could probably flash that. No guarantees though. Running 4.1.1 firmware/bootloaders with a 4.4.2 modem is a scenario which is highly unpredictable, so anything you try to flash might cause more problems, we just don't know.
I've PM'd enewman17 to ask if there was a specific reason he updated the modem the way he did. If there is not an issue doing it like i mentioned someone can try to make a new package like that for you to try.
Thanks Doc!
Hopefully enewman17 can come up with a solution for this.
Just an information which I was not able to completely comprehend but maybe pros like you or Bwolf56 will be able to.
I opened Kies and this is what it says.
Firmware information
This is the latest firmware.
Current firmware version: PDA:LK3 / PHONE:NE4 / CSC:LK3 (ATT)
Any thoughts on how do I get the PDA and CSC updated (not even sure what exactly they are)
Thanks
DocHoliday77 said:
Since you somehow have the 4.4.2 modem, you can not flash anything older than the 4.4.2 firmware. Currently there is nothing that you can flash to fix this. Normally, I would say to flash an older modem, but if Odin is seeing it as already updated to 4.4.2 (SWREV 3), and the only thing you have that is 4.4.2 is the modem, flashing anything older will likely hard brick.
You need either the full stock firmware, which there is not one, Thanks AT&T!, or a recovery flashable firmware for 4.4.2. Enewman17 has this, but it will not work for you because of how the modem is flashed. For some reason, he has it patching the 4.3 modem rather than including the full updated one like with the other partitions. If someone makes the same thing, but with the already updated modem, you could probably flash that. No guarantees though. Running 4.1.1 firmware/bootloaders with a 4.4.2 modem is a scenario which is highly unpredictable, so anything you try to flash might cause more problems, we just don't know.
I've PM'd enewman17 to ask if there was a specific reason he updated the modem the way he did. If there is not an issue doing it like i mentioned someone can try to make a new package like that for you to try.
Click to expand...
Click to collapse
Ok, enewman17 just put this together if you want to try it. This includes the full NE4 stock firmware minus system, kernel, cache and recovery.
So flashing it will preserve your current Rom, kernel and recovery, but will otherwise fully update your base firmware/bootloaders to NE4.
This should be perfectly safe to use, but seeing as it is untested, I cannot make any guarantees that it won't make things worse. (I wouldn't post it if I thought it would, but there is always the possibility)
Flash from custom recovery such as TWRP.
http://www.androidfilehost.com/?fid=23578570567716667
Sent from my SGH-T999 using Tapatalk
---------- Post added at 08:31 PM ---------- Previous post was at 08:29 PM ----------
If you want to fully update your system (rom) to stock NE4, enewman17 has a thread in the development section with stock rooms you can flash via recovery after you update your firmware posted above.
Sent from my SGH-T999 using Tapatalk
So I've been at this for a while now. I've had no issue flashing to LiquidSmooth's Liquid-JB-v2.7-UNOFFICIAL-d710 Android 4.2.2, but I can't for the life of me get this thing to install a version of 4.3.x or 4.4.x.
Right now, I've rolled back to: Rwilco12's SPH-D710_GB27_1014481_Rooted_Nodata.exe Android 4.1.2.
I have CM 11, but when I try to install it using recovery mode, it errors out and aborts the install. All the instructions I find, keep telling me to install CM's 10.2 and then update the bootloader, but I can't find links to the old versions to any of these.
Is there anything in 4.3.x or 4.4.x that has a 1 click Odin install? Or can someone walk me through taking this thing from GB27 to something new? I believe it is rooted per Rwilco's image name.
chosos said:
So I've been at this for a while now. I've had no issue flashing to LiquidSmooth's Liquid-JB-v2.7-UNOFFICIAL-d710 Android 4.2.2, but I can't for the life of me get this thing to install a version of 4.3.x or 4.4.x.
Right now, I've rolled back to: Rwilco12's SPH-D710_GB27_1014481_Rooted_Nodata.exe Android 4.1.2.
I have CM 11, but when I try to install it using recovery mode, it errors out and aborts the install. All the instructions I find, keep telling me to install CM's 10.2 and then update the bootloader, but I can't find links to the old versions to any of these.
Is there anything in 4.3.x or 4.4.x that has a 1 click Odin install? Or can someone walk me through taking this thing from GB27 to something new? I believe it is rooted per Rwilco's image name.
Click to expand...
Click to collapse
Change the recovery that your using. What doesn't flash in ClockworkMod might flash perfectly in Philz Recovery or TWRP.
Sent from my 710C using XDA Free mobile app
I'm going to need more help with that aspect. I've tried that. I have TWRP in a zip file that I've tried to install. I downloaded TWRP Manager from the App store. I downloaded Rom manager. Nothing seems to be working. When I select reboot into recovery, it just goes to the stock android recovery and says it failed.
I am able to install E4GT-EL29-directbootCWM-v3.tar.md5
or StockCWM-EL26.tar.md5 using Odin, but no luck installing TWRP.
I'm sure I'm doing something wrong, but I have no idea what. This is likely a simple process, but I don't know which files or what order to do this in.
When I flash to E4GT-EL29-directbootCWM-v3.tar.md5 from Odin, it leaves me in recovery mode until I install LiquidSmooth 4.2.x.
chosos said:
I'm going to need more help with that aspect. I've tried that. I have TWRP in a zip file that I've tried to install. I downloaded TWRP Manager from the App store. I downloaded Rom manager. Nothing seems to be working. When I select reboot into recovery, it just goes to the stock android recovery and says it failed.
I am able to install E4GT-EL29-directbootCWM-v3.tar.md5
or StockCWM-EL26.tar.md5 using Odin, but no luck installing TWRP.
I'm sure I'm doing something wrong, but I have no idea what. This is likely a simple process, but I don't know which files or what order to do this in.
When I flash to E4GT-EL29-directbootCWM-v3.tar.md5 from Odin, it leaves me in recovery mode until I install LiquidSmooth 4.2.x.
Click to expand...
Click to collapse
There are already numerous threads here with the same question and answer [emoji6]
Surj138 said:
There are already numerous threads here with the same question and answer [emoji6]
Click to expand...
Click to collapse
Yeah? shoot me the link for one that is working. I was reading all night - most link to threads from 2013 with links that are all broken. You want to send me a working one - great
Most start from something newer, older, etc. Everything I found on GB27 didn't work. Right now, I'm on GB27, with an e3 recovery image from RWilco. I can use the guides to get me from there to Liquidsmooth 4.2.x, but any progress beyond that doesn't work, and I don't want to brick the phone.
chosos said:
Yeah? shoot me the link for one that is working. I was reading all night - most link to threads from 2013 with links that are all broken. You want to send me a working one - great
Most start from something newer, older, etc. Everything I found on GB27 didn't work. Right now, I'm on GB27, with an e3 recovery image from RWilco. I can use the guides to get me from there to Liquidsmooth 4.2.x, but any progress beyond that doesn't work, and I don't want to brick the phone.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=55623318
http://forum.xda-developers.com/showthread.php?p=50070702
http://forum.xda-developers.com/showthread.php?p=55542264
This should get you going, but let me know if you need any further assistance
Good luck! [emoji2]
Surj138 said:
http://forum.xda-developers.com/showthread.php?p=55623318
http://forum.xda-developers.com/showthread.php?p=50070702
http://forum.xda-developers.com/showthread.php?p=55542264
This should get you going, but let me know if you need any further assistance
Good luck! [emoji2]
Click to expand...
Click to collapse
Thanks, this got me through it. I ended up using philz_touch_6.15.9-d710.tar to install Cyanogen 11 and gapps for 4.4.2.
Should I be all done now, or would there be more things I'd have to install? I never did anything with the modem files. I also only plan on using this as a PDA so I'm not sure if that is needed.
chosos said:
Thanks, this got me through it. I ended up using philz_touch_6.15.9-d710.tar to install Cyanogen 11 and gapps for 4.4.2.
Should I be all done now, or would there be more things I'd have to install? I never did anything with the modem files. I also only plan on using this as a PDA so I'm not sure if that is needed.
Click to expand...
Click to collapse
If you never flashed anything modem-wise, then you're still running the GB27 (JB) modem. You'll need a Gingerbread or ICS modem only if you want working 3g data/MMS messaging.
Otherwise, JB modems shouldn't cause any problems that I know of.
I recently rooted my I9195 successfully. i then flashed a custom kernel i found here on the forum (kernel v1 or sth like that) then my phone wouldn go past the boot white logo screen. i then tried flashing other kernels but they were apparently wrong as some features of my phone didnt work. i finally found the right firmware for my phone and tried to flash it with odin but it failed and now my phone only shows this message where it says that the firmware update failed and i have to use kies in recovery mode.
so i use kies and try the install firmware thing that asks you to put in your model and serial number. i do that and it says the device doesnt support initialisation. tried on another computer and it said that serial number was invalid.. i was very careful when typing it etc.
help.. what do i do?
btw last firmware i had was 4.4.2
Silvershot said:
I recently rooted my I9195 successfully. i then flashed a custom kernel i found here on the forum (kernel v1 or sth like that) then my phone wouldn go past the boot white logo screen. i then tried flashing other kernels but they were apparently wrong as some features of my phone didnt work. i finally found the right firmware for my phone and tried to flash it with odin but it failed and now my phone only shows this message where it says that the firmware update failed and i have to use kies in recovery mode.
so i use kies and try the install firmware thing that asks you to put in your model and serial number. i do that and it says the device doesnt support initialisation. tried on another computer and it said that serial number was invalid.. i was very careful when typing it etc.
help.. what do i do?
btw last firmwar i had was 4.4.2
Click to expand...
Click to collapse
I think you should put original back and start over and read forum more howto.
You use ODIN to flash custom rom, why? ODIN is for original rom. With custom rom need use TWRP or other recovery boot.
S3miniFin said:
I think you should put original back and start over and read forum more howto.
You use ODIN to flash custom rom, why? ODIN is for original rom. With custom rom need use TWRP or other recovery boot.
Click to expand...
Click to collapse
I used ODIN for past phones to flash custom kernels and it worked fine. i said i flashed someone that isnt supposed to be supported. i have no idea. i am not an expert and i thought someone can provide with a fast fix since there will surely be someone to have experienced this issue.
anyone else?
bump! please help.. i dont have another phone and I need to get this fixed asap!
You don't need root phone before new kernel or custom rom. And i believe you use wrong files for that and now phone wont boot.
Start over with original ROM. With that you can test is your phone ok. Then use ODIN for recovery kernel and custom rom. Also check this:http://forum.xda-developers.com/showthread.php?t=2678420
S3miniFin said:
You don't need root phone before new kernel or custom rom. And i believe you use wrong files for that and now phone wont boot.
Start over with original ROM. With that you can test is your phone ok. Then use ODIN for recovery kernel and custom rom. Also check this:http://forum.xda-developers.com/showthread.php?t=2678420
Click to expand...
Click to collapse
check my attached image.. i cant flash anything with odin. it gives me error fused 2 > binary 1
Silvershot said:
check my attached image.. i cant flash anything with odin. it gives me error fused 2 > binary 1
Click to expand...
Click to collapse
How about download-mode? Never seen ODIN-mode myself, so cannot understand what is going on there....
With download- mode i do all things with ODIN if need...
S3miniFin said:
How about download-mode? Never seen ODIN-mode myself, so cannot understand what is going on there....
With download- mode i do all things with ODIN if need...
Click to expand...
Click to collapse
that works, and it says downloading like normally when you try to flash something with odin, but it fails and gives me this error again: sw rev check fail: fused 2 > binarz 1
the rom im trying to flash is the DBT one in germany.
I am choosing AP btw, and not the other flash options.
S3miniFin said:
You don't need root phone before new kernel or custom rom. And i believe you use wrong files for that and now phone wont boot.
Start over with original ROM. With that you can test is your phone ok. Then use ODIN for recovery kernel and custom rom. Also check this:http://forum.xda-developers.com/showthread.php?t=2678420
Click to expand...
Click to collapse
i flashed one of those roms and i got my phone to boot. i have no wifi. i guess it was the last rom i flashed which was the wrong one.
i now tried the one which is supposed to be the correct rom but i land on the same error again. can someone help me find the correct stock rom?
here are the current device info. it seems that there is no official 4.4.2 rom for my phone. so i ****ed up lol.
Your phone has official 4.4.2 Rom and you are currently using it. If you have Wi-Fi issues, your can try to flash custom kernel (Silviu, alexax)
Sent from my GT-I9190 using Tapatalk
Silvershot said:
that works, and it says downloading like normally when you try to flash something with odin, but it fails and gives me this error again: sw rev check fail: fused 2 > binarz 1
the rom im trying to flash is the DBT one in germany.
I am choosing AP btw, and not the other flash options.
Click to expand...
Click to collapse
But why you use F.Reset Time -option? Clear that and try again.
---------- Post added at 12:12 AM ---------- Previous post was at 12:10 AM ----------
Silvershot said:
i flashed one of those roms and i got my phone to boot. i have no wifi. i guess it was the last rom i flashed which was the wrong one.
i now tried the one which is supposed to be the correct rom but i land on the same error again. can someone help me find the correct stock rom?
here are the current device info. it seems that there is no official 4.4.2 rom for my phone. so i ****ed up lol.
Click to expand...
Click to collapse
For Wifi problem could help if boot phone again after first setup.
ok now it wont go past the flashing SAMSUNG logo. i went and bought a huawei g play mini today. no more time trying to revive the s4 mini.
if someone wants to give it a try let me know and i'll ship it to you.
I will try it!
Plz sent me a PN (i'm german)
Sent from my GT-I9195 using XDA Free mobile app
S3miniFin said:
But why you use F.Reset Time -option? Clear that and try again.
---------- Post added at 12:12 AM ---------- Previous post was at 12:10 AM ----------
For Wifi problem could help if boot phone again after first setup.
Click to expand...
Click to collapse
i tried rebooting the phone but it still is as slow as before. it peaks on 27mbit when i start the speedtest but then drops down to 19 or sth..
actually the download speed seems to be the problem. not the upload. now i forgot the network and connected again and its even slower