Related
GO TO THE POST BELOW FOR THE RECOVERY AND INFO. PLEASE THANK HIM
CLICK ME FOR POST.
This is his topic full of stock recoveries and what-not
--------------------
Bear in mind that I do not have the time to restore to stock, and then check it for myself if you can extract the stock recovery without root, but you probably can. Please refer to the quote I will post below as I have little time to clean this post up.
Please thank user Davy Jones for actually finding the solution!
Davy Jones said:
Okay, I don't know any coding so I apologize if this is a dumb suggestion, but is it possible to follow the article's directions to pull recovery? So from shell:
dd if=/dev/block/mmcblk0p22 of=/sdcard/recovery.img bs=4096
I'm already on cwm so I have no way of testing this. Also, please don't try this unless you know what you are doing. I tried this on cwm and it created a file that was 10MB instead of the .img I originally flashed, which was 5.98MB.
Click to expand...
Click to collapse
My post starts here
-------------------------------------------
Alrighty that's wonderful. I am trying a guide right now and I will see if I am successful at extracting a recovery and I will report back.
EDIT
I've made wonderful process, and I've extracted a 10mb file which what the recovery.img supposed to be resized to.
So i've basically typed in
After this, I got a huge list of the partitions, and using this I've confirmed that mmcblk0p22 is the block that contains the recovery (I also made sure that I didn't extract something else, etc by checking what the userdata and sdcard size is supposed to be?
Then I typed in
and got
So I ended up with a 10MB file sitting in the root of my internal memory (known as sdcard)
Now I will try to confirm if it is the same file as my recovery.
EDIT
Well after more digging around.. I found this and where it says "Download - Recovery Image Method (using dd):" It shows that the block which the recovery is in in actually the same as the one above, so there was an easier way. Oh well! At least we confirmed that we have the correct file, the question is, can we flash it, guess I'll try after I get home.
If you want to try this out on a NON-Rooted one, you'll have to go to Settings>Developer Options>Root access and allow ADB.
-----------------------------------------------
Quote ends here.
Hopefully you're a Koodo owner reading this and have noticed the title.
Many of us Koodo owners, have rooted, installed a custom recovery, and have started the flashing frenzy, but we have forgot one thing.
No its not making a NAND of the stock ROM, its the fact the we forgot to backup our stock recoveries! I know it might not be a difference compared to the Telus recovery, but we still need to be sure, that when we want to update, or if we want to return the phone, what we are fully stock.
So what I'm asking you, is to make a backup of your Koodo stock recovery, and share it with us
Unfortunately I do not know how to extract a recovery.img. So hopefully an XDA member will post a guide in this to help us extract the .img
or as always, Google is your best friend
Cheers, and thanks
EDIT
Koragg618 said:
I have found a link on how to get it
http://www.addictivetips.com/mobile...es-boot-recovery-and-system-partition-images/
Download link for RomDump is at the end of the article
Click to expand...
Click to collapse
Those are the instructions.
Thanks everyone for contributing!
I have a stock phone still but need a guide on pulling my recovery. Would I just use ADB or?...
chevymeister said:
I have a stock phone still but need a guide on pulling my recovery. Would I just use ADB or?...
Click to expand...
Click to collapse
Im not a koodo member but is it not the same way for tmobile users? With stock ODIN flash? when I ODIN flash my t989 to stock it also flash the stock recovery
I have found a link on how to get it
http://www.addictivetips.com/mobile...es-boot-recovery-and-system-partition-images/
Download link for RomDump is at the end of the article
Bump, since no one is really noticing the pinned topic
Koragg618 said:
Bump, since no one is really noticing the pinned topic
Click to expand...
Click to collapse
I could help, Ive got a Koodo S2 X. However, its not rooted, would i still be able to make a backup of my stock recovery.
Yes I believe it is still possible, just make sure Debugging mode is on and you are using the ADB method, and not the one that has the Android Terminal one. Thanks
My friend and my girlfriend both have Stock Koodo Phone... so i'm gonne try to bring the original Koodo Recovery.img. I read the articles from addictive tips... but i think i missed something, They said we need to root the phone but the first step in the method to root the phone is to install CWM recovery IMG via Odin... So it will overwrite Koodo original Recovery.img.... before i extract it...
Any clue or hint ???
Maybe another way to root via ADB ???
I have a Koodo T989D still on stock everything. I want to root my phone and do all this fancy stuff on it but I'm not in a hurry. I can make a copy of my stock recovery if I get the proper instructions.
edit: isn't this what you're looking for anyway?? http://forum.xda-developers.com/showthread.php?t=1849748
tazmania12345 said:
I have a Koodo T989D still on stock everything. I want to root my phone and do all this fancy stuff on it but I'm not in a hurry. I can make a copy of my stock recovery if I get the proper instructions.
edit: isn't this what you're looking for anyway?? http://forum.xda-developers.com/showthread.php?t=1849748
Click to expand...
Click to collapse
No. What you're pointing to us is a custom Rom... Based on the Stock Koodo Rom. What we are looking for is the Stock Recovery... Just to put back the entire phone in original condition if you have to bring it back to manufacturer for repair...
Tornade69 said:
No. What you're pointing to us is a custom Rom... Based on the Stock Koodo Rom. What we are looking for is the Stock Recovery... Just to put back the entire phone in original condition if you have to bring it back to manufacturer for repair...
Click to expand...
Click to collapse
Oh i see... I'm still on stock 4.0.4 so i'll definitely try to provide the backup. Like i said, i'd need the proper instructions because i'm new to all of this.
Someone previously posted the stock recovery which I have attached. Use at your own risk since I have not tested it!
Amazing, where did you find this!
Koragg618 said:
Amazing, where did you find this!
Click to expand...
Click to collapse
Someone previously posted it few weeks ago on the XDA forums in the device dev section and I had downloaded and kept a copy in case I needed it.
jumran said:
Someone previously posted it few weeks ago on the XDA forums in the device dev section and I had downloaded and kept a copy in case I needed it.
Click to expand...
Click to collapse
Thanks! This will come in handy.
Sorry to be the bad news but I believe this recovery is the one that I've packaged before I though I've found the TLLG2 stock recovery from this site page 68( post by netusername and uploading it without testing it 1st.... then later installed/tested it and it was a CWM touch recovery and not the TLLG2 stock recovery, Sorry again.
Source:
User:netusername
KOODO STOCK IMAGE/RESTORE
Directions: Download these three in the same folder - Part 1, Part 2, Part 3
Use Winrar/7zip to only extract Part 1 after you have all three parts in the same folder. You should get a folder called clockworkmod. There should be another folder called "backup" inside.
Put the "clockwordmod" folder in your sd card.
Use clockwordmod to restore after factory reset, wipe system, wipe dalvik cache.... It is recommended that you use Clockwordmod 6 - it can be found here - http://forum.xda-developers.com/show....php?t=1823117
Enjoy!
Click to expand...
Click to collapse
Sent from my ♛ SGH-T989 ♛ using XDA app.
Oh well thats confusing Thanks for the info man!
Sorry I'm not following.
Do you mean the post by jumran (http://forum.xda-developers.com/showpost.php?p=32299219&postcount=12) is not the stock recovery and is actually a CWM recovery that you're mentioning?
KRZ-2pa said:
Sorry to be the bad news but I believe this recovery is the one that I've packaged before I though I've found the TLLG2 stock recovery from this site page 68( post by netusername and uploading it without testing it 1st.... then later installed/tested it and it was a CWM touch recovery and not the TLLG2 stock recovery, Sorry again.
Source:
Sent from my ♛ SGH-T989 ♛ using XDA app.
Click to expand...
Click to collapse
Yes it is a CMW Touch recovery and no problem
[curious] What are you guys doing? [/curious]
You realize backing up any part of your original stock ROM is pointless? All you have to do pick up the original stock tarball from Samsung's website, fire up ODIN, flash, and then not even Samsung can tell you ever did something to your phone. It will be stock everything: radio, recovery, ROM...
---------- Post added at 08:41 PM ---------- Previous post was at 08:31 PM ----------
Here, follow the instructions: http://fus.nanzen.se/
There are no presets for Koodo, but all the information you need is readily available on the original box your phones came in.
And if you really need the Koodo recovery for whatever reason, it is an IMG file inside the TARball. You can just DD it in place.
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,
I had stock 4.3 firmware on my att i747 galaxy s3, then I decided to flash cyanogenmod. everything went well but i dont really like it.
Now I want to go back to stock. I tried flashing the stock rom with odin but it fails and it says this on the phone:
ODIN MODE
PRODUCT NAME: SGH-I747
CUSTOM BINARY DOWNLOAD: Yes (2 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Official
QUALCOMM SECUREBOOT: ENABLE
Warranty Bit: 1
BOOTLOADER RP SWREV: 2
SW REV CHECK FAIL : Fused 2 > Binary 0
The android version it shows is 4.3.1 and im able to use it normally with the cyanogenmod.
What can I do to flash a stock rom back?
EDIT: used triangle away and the custom binary download says "no" now and the current binary says "samsung official" but still get the same problem.
Thank You
bryangd07 said:
Hi,
I had stock 4.3 firmware on my att i747 galaxy s3, then I decided to flash cyanogenmod. everything went well but i dont really like it.
Now I want to go back to stock. I tried flashing the stock rom with odin but it fails and it says this on the phone:
Thank You
Click to expand...
Click to collapse
You need to flash a stock ROM that has no boot loader attached to it. I just reverted my S3 back to stock from CM11 so that I could sell it. Flash a Rom.zip through recovery and it should work fine. I see you are ATT so I suggest this one: http://forum.xda-developers.com/showthread.php?t=2540998. You have the choice of Stock Rooted without bootloader which is what you will be looking for. This thread also has everything you may need. Do not attempt to use Odin to flash roms with older bootloaders or you will find major issues.
You will almost definitely need to wipe everything so back everything up and be sure to take a Nandroid.
BCSC said:
You need to flash a stock ROM that has no boot loader attached to it. I just reverted my S3 back to stock from CM11 so that I could sell it. Flash a Rom.zip through recovery and it should work fine. I see you are ATT so I suggest this one: http://forum.xda-developers.com/showthread.php?t=2540998. You have the choice of Stock Rooted without bootloader which is what you will be looking for. This thread also has everything you may need. Do not attempt to use Odin to flash roms with older bootloaders or you will find major issues.
You will almost definitely need to wipe everything so back everything up and be sure to take a Nandroid.
Click to expand...
Click to collapse
thanks for answering, sorry i dont know much about this, can you tell me which one has no bootloader on it?
bryangd07 said:
thanks for answering, sorry i dont know much about this, can you tell me which one has no bootloader on it?
Click to expand...
Click to collapse
In that thread you have 2 good options that I can see. Scroll down and you will find one ROM by upndwn4par/full and another debloated directly under it. Which you chose depends on if you want Samsung/ Google software on it. The upndwn4par file will have you closer to stock than the other. Please be sure to read a couple pages, even if you don't get any immediate knowledge from it you will become way more familiar with these processes. It's worth the time, and safer for your phone.
BCSC said:
In that thread you have 2 good options that I can see. Scroll down and you will find one ROM by upndwn4par/full and another debloated directly under it. Which you chose depends on if you want Samsung/ Google software on it. The upndwn4par file will have you closer to stock than the other. Please be sure to read a couple pages, even if you don't get any immediate knowledge from it you will become way more familiar with these processes. It's worth the time, and safer for your phone.
Click to expand...
Click to collapse
Thanks once again, i will download the debloated one. But I have a question, that won't be a stock rom right? If the bootloader is the problem is there a stock d2att 4.3 rom i can flash?
That is a stock ROM. It is just pre rooted with knox removed. It is a modified version of the Stock OTA with the problematic parts removed..
BCSC said:
That is a stock ROM. It is just pre rooted with knox removed. It is a modified version of the Stock OTA with the problematic parts removed..
Click to expand...
Click to collapse
how do i flash this rom? using the phone recovery(VU+home+power) ?
EDIT: i tried that and it failed the verification
What recovery are you using? Latest CWM?
BCSC said:
What recovery are you using? Latest CWM?
Click to expand...
Click to collapse
i don't know, the original i guess
bryangd07 said:
i don't know, the original i guess
Click to expand...
Click to collapse
You need a custom recovery to flash this. CWM or TWRP. I'm not too sure how you got to CM without one but be sure you have one and then flash the Rom from above. You can install CWM with the app 'Rom Manager'.
See here http://forum.xda-developers.com/showthread.php?t=2538991
BCSC said:
You need a custom recovery to flash this. CWM or TWRP. I'm not too sure how you got to CM without one but be sure you have one and then flash the Rom from above. You can install CWM with the app 'Rom Manager'.
See here http://forum.xda-developers.com/showthread.php?t=2538991
Click to expand...
Click to collapse
I installed CWM but now that i used cyanogen for a while im starting to like it. The only thing that I dont like is the music player. I downloaded google play but it is even worst, my playlists are not even in order. Is there any way of flashing the stock samsung music player on cyanogenmod or is it integrated with the touchwiz?
Thanks for all the help you gave me so far.
EDIT: I found this thread about ported s4 apps: http://forum.xda-developers.com/showthread.php?t=2267029, can i just flash it with CWM using cyanogenmod?
You can not flash that S4 port. It says it is specifically for the Galaxy advance. Also you are correct that the Samsung player requires Touchwiz. Try Power Amp, it has pretty good reviews and features. A 3rd party player is probably your best bet. You can cherry pick for features
BCSC said:
You can not flash that S4 port. It says it is specifically for the Galaxy advance. Also you are correct that the Samsung player requires Touchwiz. Try Power Amp, it has pretty good reviews and features. A 3rd party player is probably your best bet. You can cherry pick for features
Click to expand...
Click to collapse
I tried a lot of players and didn't like any. Flashed the ROM you indicated using CWM and it worked. Did it all for the player Everything is working fine now and I really like how it doesn't have all the bloatware from att.
Thank you very much for the help.
bryangd07 said:
I tried a lot of players and didn't like any. Flashed the ROM you indicated using CWM and it worked. Did it all for the player Everything is working fine now and I really like how it doesn't have all the bloatware from att.
Thank you very much for the help.
Click to expand...
Click to collapse
No problem dude. I always found myself going back to Touchwiz as well. Let me know if you need more help.
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
It's been a long bloody time since I fiddled around with stuff on this phone. So I'm still on a rooted 4.1.2.
My questions are is it worth the upgrade to KitKat? And if so, what's the easiest way for me to do so? Hopefully retaining root, but not too necessary.
Help would be appreciated. For dummies.
Hey there.
I've gone through the process myself recently. Here is what you should do :
1. Download a custom rom from the Android Development forum. For example I downloaded the DN3 v5.2, but whatever catches your eye is fine.
2. Just follow the instructions the rom' s topic states.
3. If you have trouble getting to the recovery mode, you should flash with Odin some custom recovery. I like the cwm recovery.
4. Most guides provide info how to root your phone but if not then there is a topic in the Android Development forum about it.
I suggest backing up everything you can before- copy the phone contents to your pc, run the efs professional program to backup your efs.
Cheers
Rizaria said:
It's been a long bloody time since I fiddled around with stuff on this phone. So I'm still on a rooted 4.1.2.
My questions are is it worth the upgrade to KitKat? And if so, what's the easiest way for me to do so? Hopefully retaining root, but not too necessary.
Help would be appreciated. For dummies.
Click to expand...
Click to collapse
Hi there. I'm using n7100. N7105 is not far different to n7100. I've recently upgraded my phone from 4.3 to 4.4. I can't see a big difference from the 2 version except 4.4 consumes more battery than 4.3. I think you should consider 4.3 first before going straight to 4.4.
Just to inform you. What I know is...4.3 and 4.4 Official Rom already have Knox. So maybe you should read about them first. And Flashing Custom Recovery like PhilzTouchRecovery may trigger your Knox and increase your Binary Counter. And you may loose your warranty.
Flashing and rooting stock ROM is easy. But you have to do it right. What I did:
1. Download Odin
2. Download Samsung USB Drivers
3 Download 4.4 Firmware for my phone at sammobile.com
4. Install Samsung USB Driver
5. Run Odin
6. Put phone in Download Mode. Check if Odin successfully detected my phone
7. Once success, load the firmware to PDA Tab/Button. Don't touch anything
8. Press start. Wait till done. Wait till your phone reboot on it's own.
9. Once rebooted, check "About Device".
10. Done!
11. Download PhilzTouchRecovery 6.26
12. Put device into Download Mode again.
13. Run Odin again
14. Connect device again
15. Load PhilzTouchRecovery.tar.md5 to PDA Tab/Button
16. Uncheck Auto Reboot from Odin
17. Click start. Once Pass! Disconnect device.
18. Hold Power Button, DON'T RELEASE till you boot into your new recovery.
19. Once booted to PhilzRecovery, select reboot system now, but make sure not to overwrite with stock recovery or else you're PhilzRecovery will be reverted back to your stock recovery and you have to flash again your PhilzRecovery.
20. Once successfully flashed PhilzRecovery. Make all necessary backups (Full backup) you can't make EFS/MODEM backup yet because your not yet Rooted. You just installed Custom Recovery.
21. Once fully backed up. Copy backup files to your PC.
22. If you want to root again. Use CF-ROOT on 4.4.2 or use Dr.Ketan's Multi-Tool-Advance-V6 in 4.3. And follow their instructions.
Good Luck. HTH.
PoOoZaQ said:
Hey there.
I've gone through the process myself recently. Here is what you should do :
1. Download a custom rom from the Android Development forum. For example I downloaded the DN3 v5.2, but whatever catches your eye is fine.
2. Just follow the instructions the rom' s topic states.
3. If you have trouble getting to the recovery mode, you should flash with Odin some custom recovery. I like the cwm recovery.
4. Most guides provide info how to root your phone but if not then there is a topic in the Android Development forum about it.
I suggest backing up everything you can before- copy the phone contents to your pc, run the efs professional program to backup your efs.
Cheers
Click to expand...
Click to collapse
Thanks for that. Still wondering which one I should try all this Knox stuff is puzzling. Seems a lot of things have happened since I last had a fiddle.
asin_punk said:
Hi there. I'm using n7100. N7105 is not far different to n7100. I've recently upgraded my phone from 4.3 to 4.4. I can't see a big difference from the 2 version except 4.4 consumes more battery than 4.3. I think you should consider 4.3 first before going straight to 4.4.
Just to inform you. What I know is...4.3 and 4.4 Official Rom already have Knox. So maybe you should read about them first. And Flashing Custom Recovery like PhilzTouchRecovery may trigger your Knox and increase your Binary Counter. And you may loose your warranty.
Flashing and rooting stock ROM is easy. But you have to do it right. What I did:
1. Download Odin
2. Download Samsung USB Drivers
3 Download 4.4 Firmware for my phone at sammobile.com
4. Install Samsung USB Driver
5. Run Odin
6. Put phone in Download Mode. Check if Odin successfully detected my phone
7. Once success, load the firmware to PDA Tab/Button. Don't touch anything
8. Press start. Wait till done. Wait till your phone reboot on it's own.
9. Once rebooted, check "About Device".
10. Done!
11. Download PhilzTouchRecovery 6.26
12. Put device into Download Mode again.
13. Run Odin again
14. Connect device again
15. Load PhilzTouchRecovery.tar.md5 to PDA Tab/Button
16. Uncheck Auto Reboot from Odin
17. Click start. Once Pass! Disconnect device.
18. Hold Power Button, DON'T RELEASE till you boot into your new recovery.
19. Once booted to PhilzRecovery, select reboot system now, but make sure not to overwrite with stock recovery or else you're PhilzRecovery will be reverted back to your stock recovery and you have to flash again your PhilzRecovery.
20. Once successfully flashed PhilzRecovery. Make all necessary backups (Full backup) you can't make EFS/MODEM backup yet because your not yet Rooted. You just installed Custom Recovery.
21. Once fully backed up. Copy backup files to your PC.
22. If you want to root again. Use CF-ROOT on 4.4.2 or use Dr.Ketan's Multi-Tool-Advance-V6 in 4.3. And follow their instructions.
Good Luck. HTH.
Click to expand...
Click to collapse
Very concise steps, cheers for that. Might give all that a try. Just need a safe rom. Not sure what. Is there anything else that needs flashing, like modem files or anything?
Thanks for both your comments.
Only the rom is necessary. Shouldn't flash modem and kernel etc unless something doesn't work.
All the roms published in xda are fine and safe. I just went for the topic with the most views.
If you want you can also download stock 4.3 from www.sammobile.com
Just choose your device and you get a file flashable with odin. About 1.9 giga download.
Rizaria said:
Thanks for that. Still wondering which one I should try all this Knox stuff is puzzling. Seems a lot of things have happened since I last had a fiddle.
Very concise steps, cheers for that. Might give all that a try. Just need a safe rom. Not sure what. Is there anything else that needs flashing, like modem files or anything?
Thanks for both your comments.
Click to expand...
Click to collapse
Your current Bootloader doesn't have Knox. So you better search for a 4.3 or 4.4 rom that doesn't flash new bootloader. I think i saw it somewhere in the development.If I were not mistaken, it should be flashed thru custom recovery. Coz it's a zip file.
All I know is all rom files from sammobile.com includes new kernel, bootloader and modem. So if you flash this roms from sammobile, you will have a new kernel, bootloader and modem. It's all up to you. If I were you, I'll stay away from Knox. So find a rom that supports your current bootloader. Maybe a custom one.
Maybe this will help...
http://forum.xda-developers.com/showthread.php?t=2747963
asin_punk said:
Your current Bootloader doesn't have Knox. So you better search for a 4.3 or 4.4 rom that doesn't flash new bootloader. I think i saw it somewhere in the development.If I were not mistaken, it should be flashed thru custom recovery. Coz it's a zip file.
All I know is all rom files from sammobile.com includes new kernel, bootloader and modem. So if you flash this roms from sammobile, you will have a new kernel, bootloader and modem. It's all up to you. If I were you, I'll stay away from Knox. So find a rom that supports your current bootloader. Maybe a custom one.
Maybe this will help...
http://forum.xda-developers.com/showthread.php?t=2747963
Click to expand...
Click to collapse
Fair enough, thanks.
If I try the one below, think that'd work out alright? And which to use, deoxed or not?
http://forum.xda-developers.com/showthread.php?t=2588787
Sent from my GT-N7105 using XDA Free mobile app
Rizaria said:
Fair enough, thanks.
If I try the one below, think that'd work out alright? And which to use, deoxed or not?
http://forum.xda-developers.com/showthread.php?t=2588787
Sent from my GT-N7105 using XDA Free mobile app
Click to expand...
Click to collapse
Yeah nice find... It should work fine... you're on the 3rd status "For those are on the 4.1.2 bootloader the rom could work normally with AGNi Kernel include in rom". I think you should go for DEODEXED for more customization and etc. Read here: http://codeversed.com/deodexed-vs-odexed-rom/.
Make sure to follow instruction precisely and strictly. And make sure to copy your Backup to your PC right after you created it. Coz if you do a Full Wipe, Reset and Clean Install, it will also delete the backup that you made. Read the instructions multiple times carefully to avoid mislead. Once you done it successfully, you will be on Custom Rom and Custom Kernel. Sounds very techie. Hahaha. Good Luck!
asin_punk said:
Yeah nice find... It should work fine... you're on the 3rd status "For those are on the 4.1.2 bootloader the rom could work normally with AGNi Kernel include in rom". I think you should go for DEODEXED for more customization and etc. Read here: http://codeversed.com/deodexed-vs-odexed-rom/.
Make sure to follow instruction precisely and strictly. And make sure to copy your Backup to your PC right after you created it. Coz if you do a Full Wipe, Reset and Clean Install, it will also delete the backup that you made. Read the instructions multiple times carefully to avoid mislead. Once you done it successfully, you will be on Custom Rom and Custom Kernel. Sounds very techie. Hahaha. Good Luck!
Click to expand...
Click to collapse
Thanks for the advice.
Really, I wanted to upgrade to Android L but then I saw it wasn't out yet so I was like...huh, KitKat time?
I'm not even sure if it'll be any better than what I have! Mostly just want something with better battery life. Even though I just bought a new battery that lets me use my phone for 3 days and a half hour. I have noticed that Screen/Android seem to be bleeding power a lot more these days, so figured it might be worth a wipe and an upgrade.
In any case, whenever I do, I have some handy guides now. Cheers~