Rooted/Flashed my phone a long time. Constant bugs and errors. I really don't remember what all I did but I think I almost have it completely unrooted and back to stock. However, I can't update OTA. I've reflashed using this file, http://forum.xda-developers.com/showthread.php?t=2658486. Fixed just about all my issues and I actually have a lot of space on my phone. When I try to do the OTA Update, it doesn't install the update. Once it boots into recovery mode to install the update it gives an error. Can someone help my to 100% fully get my phone back to stock and be able to install OTA updates? I'm clueless.
First, did the 4.4.2 ota fail after a certain percentage? If so you may actually be partially updated already. If so, flashing MJB firmware/bootloader will hard brick.
Install and open Terminal Emulator and enter this:
getprop ro.bootloader
If it says MJB, you are still on 4.3 and can refresh that. If it says NE4, do not flash MJB!
If you can still flash MJB, there is a thread in General (I think that's where) that has the Odin flashable firmware package. Flash that with Odin and factory reset. Then try the OTA.
Factory resetting with stock recovery installed will wipe internal sd card, so back up first!
There are also a few threads in General that can help you update if the OTA continues to fail.
I'm unrooted. At least im pretty sure of that. I cant run superu anumore and root checker says im not rooted. Can I still access the terminal without being rooted. I know I had clockeork mod recovery. I also had used cyanogen mod at one point. Now I have the stock recovery but when I boot into recovery I get an error. I will post the error and install percentage as soon as the ota update downloads.
Yes, you can still run getprop w/o root. Just install terminal emulator by jackpal from the play store.
Yeah it said I747UCUEMJB. Like I said my recovery gives me an error. When I try flashing at all with odin it fails. Trying to install the ota update now. After it fails ill give the error recovery gives me. OTA update fails at 24%
Ok, booting into Android system recovery gives me a no command error than it shows the list of options. When I go to reboot system now, it gives me a no command error as well. Download mode used to give me an error, might only show up when attempting to flash something. However, these are the details of my ODIN Mode right now.
Product Name: SGH-I747
Custom Binary Download: Yes (1 Counts)
Current Binary Custom
System Status: Custom
QUALCOMM SECUREBOOT: ENABLE
Warranty Bit: 1
BOOTLOADER RP SWREV: 2
When you try to flash the firmware with Odin, what does it say in the message box?
Have you tried flashing TWRP via Odin?
A lot of people seem to be having issues with the OTA failing at 20-something percent. No idea why though. I know some found that their firmware was partially updated afterwards though, which is why they couldn't flash with Odin. Need to know what odin says about the failure to know for sure though.
You might need to factory reset btw.
I've already did a factory reset when I flashed this latest rom from that thread I posted.
Point me in the right direction of the firmware I need. I've got AT&T btw.
Try MJB firmware again. Im assuming that's what you tried to flash with odin earlier right? When/if it fails again, copy the text from the message box and paste it here.
So you want me to try flashing using Odin with that firmware I provided in that link? Like I said, ODIN on the pc gives me an error. I'll provide the error later when I get off work. Before I just put the firmware on my sd card, went into refovery mode and installed it from there.
From what I can see that is for flashing in recovery only. Of in only flashes .tar and .tar.md5 files.
This is the stock MJB firmware you can use in Odin:
http://www.androidfilehost.com/?fid=23329332407590581
Its from enewman17 in his how to update thread here (step 4):
http://forum.xda-developers.com/showthread.php?p=53563776
If you still want to update to 4.4.2, that thread has had a pretty good success rate from what I've seen.
Let me know if you have any ither questions about this.
I'll try ut as soon as I get home from work and posy my results. Thanks for the help so far!
Wow I think one of the reasons I couldn't use ODIN after trying to unroot, is because I never had turned on USB Debugging mode. You wanted me to just go through Step 4 for right now right? Just to get back to stock 4.3 AT&T S3 like right out the box?
Thanks so much Doc. After following step 4 on that thread I was able to Ota update!
DocHoliday77 said:
From what I can see that is for flashing in recovery only. Of in only flashes .tar and .tar.md5 files.
This is the stock MJB firmware you can use in Odin:
http://www.androidfilehost.com/?fid=23329332407590581
Its from enewman17 in his how to update thread here (step 4):
http://forum.xda-developers.com/showthread.php?p=53563776
If you still want to update to 4.4.2, that thread has had a pretty good success rate from what I've seen.
Let me know if you have any ither questions about this.
Click to expand...
Click to collapse
Been using my newly updated S3 and now the Touchwiz Home stops on startup and resets my default app settings repeatedly. Not sure what's the deal, tried suggestions on diff sites and am trying a factory restore, wipe date, and wipe cache partition. Any clue how to fix this?
PS: Seen in Android System Recovery it says KOT49H.I747UFNE4. Should that be I747UCEMJB since that's what mine is and recovery still gives me no command when I start it up?
You said you had updated with the OTA so NE4 would be correct.
As for recovery, if you want to keep stock recovery, enewman17 has it available in one of his threads (in development section I think). Redland that by itself and it ought to be good to go.
Otherwise, use Odin to flash TWRP recovery.
Factory reset should take care of the launcher/home issue you mentioned. You may not be able to though since it sounds like recovery is corrupted. Fix recovery as I said above and then try the reset.
If you factory reset with stock recovery installed, it will wipe your internal sd card. With custom recovery it will not.
You could also try clearing data for Touchwiz Home in application management.
I am having issues updating OTA too. It gets to 100% and then says my phone will reboot in 5 seconds, then it reboots and some at&t logo with a % counter comes up, that gets to 100% then it reboots into Android and it still says 4.3...what am I doing wrong? Anyone have any advice? Many thanks if so.
Thats a new one for me...how exactly are you going about updating? Are you using one of the threads here? Have you recently modified anything?
DocHoliday77 said:
Thats a new one for me...how exactly are you going about updating? Are you using one of the threads here? Have you recently modified anything?
Click to expand...
Click to collapse
I am trying to update by going to settings --> more --> about device --> software update. Not using a thread, no. I was rooted and uninstalled google books and newsstand then unrooted and did a factory reset in stock recovery because I found out that if you are rooted the OTA update won't take. I am 100% bone stock now except for the 2 bloatware apps I uninstalled. I have since reinstalled them via the play store , but I hear they need to be system apps?
They do, but they also need to be the same versions that were originally included. If you get them from the store they'll be updated and will cause the ota to fail.
Related
SGH-T999, stock t999uvdlja
A month or two ago, I followed a rooting instructions thread on here. It had me use odin to flash over a clockwork recovery mod as the first step. It flashed over fine according to odin, but I was never able to enter recovery following the next steps and therefore was not able to root. I can't find the thread anymore.
I realized after the fact that my phone was already on Jellybean, so I presume, maybe wrongly, that the reason the clockwork mod wouldn't work was because it was for the older Ice cream sandwich firmware.
Anyway, now my phone says unable to update because it's modified when I go into settings:about:software updates.
I want to get this error to go away. I have kies and there is now a firmware update in there that I would like to do to see if it fixes a problem with the wifi calling app breaking caller id among other things.
I am afraid that if I try to push this update via kies, it may brick the phone or not work thanks to the clockwork mod problem.
So two questions: 1) how can I un-flash that clockwork mod out of there and make the recovery back to stock so there is no further error or possible warranty issue, and 2) is it safe to do that kies firmware update and if so would that fix the recovery on its own?
Any ideas?
Sent from my SGH-T999 using xda app-developers app
You need to find the stock recovery .tar file and use odin to flash it the same way you flashed the cwm recovery. Then you will probably need to use triangle away to reset the counter.....dont think kies would work if it sees your device is modified but not sure about that.
Use triangle away first to reset your flash counter then odin the completly stock jb from here http://www.androidfilehost.com/?fid=9390169635556426424....this is from docholidays thread for stock odin roms in the sticky section of development. ..this should give you a completely stock phone including recovery.....you will lose your data from this process but your sd card will be fine.
Edit: just realized you dont have root...you need root to use triangle away....so first odin root 66 pre root stock rom....then use triangle away....then odin stock unrooted rom that I linked above.
Sent from my SGH-T999 using xda premium
Hello,
I’m looking for some guidance on getting my phone back to completely stock.
Steps I’ve done:
I have re-flashed back to the stock image using Odin. After doing so I wipe/reset. I then had a flash count of 8.
I then used Chainfires method and flashed with Odin to root device, which only installs super SU. I ran triangle away and still had a flash count as one. So I ran triangle away again and clicked the box that disables superSU for an amount of time. The rom went back to official with no flash counts.
Here is where I ran into problems. I ran super SU after seeing I had no flash counts to unroot the device. As soon as I opened superSU I got a flash count back to 1 again and could not update device from original firmware. I tried several different times including full wipe reset after I unrooted with superSU.
So what I did was re-rooted device using odin and install triangle away. I ran the exact same things as before by disabling SuperSU in triangle away and I was back to the official rom and no flash count. I then disabled superSU in manage applications and removed any notifications (force stop).
My phone was able to download the update as it recognized the stock rom, but then when I attempted to install it my phone it did its normal reboot for install and said install failed custom binary etc. Checked and again I had a 1 flash counter.
Possibly where I messed up?
Things I can gather or maybe I’m wrong. I downloaded stock image from Samsung. It was a TAR file. It is a 4.1 file. In addition I know it was for the T889 for T-mobile. Is there a possibility that this is the wrong file? Is there something else I should be flashing to phone with the PDA in any of other slots? Recovery file? Why when I attempt to run superSU unroot does it add a flash counter?
I do not have my original stock image. Phone T889 T-Mobile.
I’m usually pretty good at this stuff, but have run into a rut. I want to return my phone to completely stock and get OTA updates.
Any help would be greatly appreciated! Thank you in advance!!
RSVRMAN1 said:
...I’m usually pretty good at this stuff, but have run into a rut. I want to return my phone to completely stock and get OTA updates.
Any help would be greatly appreciated! Thank you in advance!!
Click to expand...
Click to collapse
If the main goal is to go back to stock to get official OTAs, I'm pretty sure the binary count bit doesn't need to be a worry. What has worked for me is to
- factory reset/wipe data (can do this using custom recovery or just the official stock recovery actually)
- ODIN factory image (I tend to DL them from sammobile)
At that point I had no issue grabbing OTAs - not sure if this helps but I hope it does
dwitherell said:
If the main goal is to go back to stock to get official OTAs, I'm pretty sure the binary count bit doesn't need to be a worry. What has worked for me is to
- factory reset/wipe data (can do this using custom recovery or just the official stock recovery actually)
- ODIN factory image (I tend to DL them from sammobile)
At that point I had no issue grabbing OTAs - not sure if this helps but I hope it does
Click to expand...
Click to collapse
Any response will help thank you!
I downloaded from sammobile as well. Do you download the factory image and install on phone or do you flash the factory image from ODIN.
I should probably clarify I'm trying to update phone by clicking software update. When I click that currently it states. Your device has been modified. Software updates are not available.
This is why I've been going the triangle away superSU route trying to just install the original stock firmware, click update and receive the latest version.
Here some additional info on my kernal and build. I'm not sure if this is possibly wrong?
Currently phone says android 4.1.1 baseband T889UVALL4 Kernel version 3.031-598701 [email protected]#1 SMP PREEMPT Sat Jan 5 19:34:13 KST 2013
Build number JR003C.T889UVALL4
Thanks again!
RSVRMAN1 said:
Any response will help thank you!
I downloaded from sammobile as well. Do you download the factory image and install on phone or do you flash the factory image from ODIN.
I should probably clarify I'm trying to update phone by clicking software update. When I click that currently it states. Your device has been modified. Software updates are not available.
This is why I've been going the triangle away superSU route trying to just install the original stock firmware, click update and receive the latest version.
Here some additional info on my kernal and build. I'm not sure if this is possibly wrong?
Currently phone says android 4.1.1 baseband T889UVALL4 Kernel version 3.031-598701 [email protected]#1 SMP PREEMPT Sat Jan 5 19:34:13 KST 2013
Build number JR003C.T889UVALL4
Thanks again!
Click to expand...
Click to collapse
I used ODIN - and the info looks fine. I had no issue getting the OTA from UVALK8 to UVALL4 using this approach, though is there a particular reason you want to go the click-update path? I ask because sammobile has a factory image of the most current version (UVBMD1) as well... might be a plan B at least.
dwitherell said:
I used ODIN - and the info looks fine. I had no issue getting the OTA from UVALK8 to UVALL4 using this approach, though is there a particular reason you want to go the click-update path? I ask because sammobile has a factory image of the most current version (UVBMD1) as well... might be a plan B at least.
Click to expand...
Click to collapse
I plan on giving the phone to my better half and buy new note 3 eventually. I feel that if I can click and have the phone update I know everything works and wont have to touch it again, while if I install the latest then on the next update I'm unsure if it will update having to flash the new stock rom again.
I love custom roms, but it requires lots of work keeping them up to date and can have various issues that I dont want her to deal with.
I'm wondering if I should try to flash a different stock recovery rom?
Here are 3 separate roms I could install do you have one you would suggest?
cant post the link but its from stockroms dot net
Do I need to install stock recovery on my phone? I guess I thought I just needed to install the factory image. Can you flash stock recovery on Odin or where do you put this into equation?
install stock image/install recovery/root/wipe/triangle away/superSU-unroot/wipe/update
Thanks again for the quick response.
RSVRMAN1 said:
I plan on giving the phone to my better half and buy new note 3 eventually. I feel that if I can click and have the phone update I know everything works and wont have to touch it again, while if I install the latest then on the next update I'm unsure if it will update having to flash the new stock rom again.
I love custom roms, but it requires lots of work keeping them up to date and can have various issues that I dont want her to deal with.
I'm wondering if I should try to flash a different stock recovery rom?
Here are 3 separate roms I could install do you have one you would suggest?
cant post the link but its from stockroms dot net
Do I need to install stock recovery on my phone? I guess I thought I just needed to install the factory image. Can you flash stock recovery on Odin or where do you put this into equation?
install stock image/install recovery/root/wipe/triangle away/superSU-unroot/wipe/update
Thanks again for the quick response.
Click to expand...
Click to collapse
I should clarify the factory images are from note2root DOT com
Going to keep trying to reflash: Just did it again and still keep getting a binary account right after I complete the Full unroot.
Why does it go from official to custom after this last step?
Following Chainfire
If you want to unroot for some reason :
From stock rom and root by Chainfire method all you need to do : Triangle Away app ,SuperSU / setting/ full unroot. Reboot into Recovery / Factory reset.
From custom rom : reflash stock image via Odin .reroot by CF auto root,reset counter with Triangle Away App,SuperSU/Setting/Full unroot . Recovery / Factory reset.
Can find stock firmware from here
Stock T889UVALJ1 & T889UVALK8 (Post 51) http://forum.xda-developers.com/show....php?t=1969551 ( Thank , TeshXX)
Stock + root http://forum.xda-developers.com/show....php?t=1975560 ( Thank , Mr.Robinson )
Tried a different stock firmware 4.1.2 T889 and now wont recognize T-mobile. Anyone have a link to the exact T889 stock firmware that I can just odin-install
Then triangle away/supersu reset and get OTA?
Really would like to get this working. Any help is greatly appreciated.
Try Mr Robinson,
http://forum.xda-developers.com/showthread.php?t=1975560
Sent from my SGH-T889 using xda app-developers app
I was on stock, un-rooted firmware version MD5. Went ahead with the official 4.3 upgrade through KIES. Don't like it, want to go back to stock MD5. Trying to ODIN back with official FW file (not the first time I've used this) and when I start, it fails and what is weird is that it appears the bootloader is changed as well from the 4.3 update. It has 2 new lines in the upper left corner (Warranty Bit: 0 and BOOTLOADER RP SWREV: 1) Now, once the ODIN failed, another line, in all red letters on the download screen underneath those previous mentioned lines, states
SW REV CHECK FAIL : Fused 1 > Binary 0. Any ideas? Phone works 100% on this new 4.3 from TMO, just cant seem to ODIN back to 4.1.2. Any help would be super. Thanks!
phoenix98 said:
I was on stock, un-rooted firmware version MD5. Went ahead with the official 4.3 upgrade through KIES. Don't like it, want to go back to stock MD5. Trying to ODIN back with official FW file (not the first time I've used this) and when I start, it fails and what is weird is that it appears the bootloader is changed as well from the 4.3 update. It has 2 new lines in the upper left corner (Warranty Bit: 0 and BOOTLOADER RP SWREV: 1) Now, once the ODIN failed, another line, in all red letters on the download screen underneath those previous mentioned lines, states
SW REV CHECK FAIL : Fused 1 > Binary 0. Any ideas? Phone works 100% on this new 4.3 from TMO, just cant seem to ODIN back to 4.1.2. Any help would be super. Thanks!
Click to expand...
Click to collapse
Is not possible for right now, until devs will create a new root app or something like superSU or I don't know ! :crying: Same to me ...
Your Boot loader is probably secured.
Try Root66 image and get back to UVDMD5 Rooted. From there, use Doc Holiday's thread to get 4.3 upgrade.
As it stands, right now if you flashed the official firmware or OTA, you will not be able to Odin flash any previous firmware. Maybe if you were never rooted....
For now though, you shoukd still be able to flash cwm/twrp and flash another rom. you will be limited to the 4.3 modem, but otherwise should be ok to run a 4.1.2 rom.
We are working on it.
Sent from my T-Mobile MyTouch 3G Slide(HTC Espresso) using Tapatalk 2
I had the same problem
I just had this same problem and was lucky enough to fix it!!!!
vTizzle said:
I just had this same problem and was lucky enough to fix it!!!!
Click to expand...
Click to collapse
How/ What did you do you fix it? I'm stuck in a rut :l
I was trying to few things. But essentially I was trying to get back to a custom recovery so that I can flash a compatible rom. try flashing a recovery in Odin, stay away from the CWM. Flash to TW RP or something like that. I will try to help out more as soon as I get to my laptop
Sent from behind you
vTizzle said:
I was trying to few things. But essentially I was trying to get back to a custom recovery so that I can flash a compatible rom. try flashing a recovery in Odin, stay away from the CWM. Flash to TW RP or something like that. I will try to help out more as soon as I get to my laptop
Sent from behind you
Click to expand...
Click to collapse
Hm... Interestingly enough it worked! I flashed CWM 6.3.0 though, sent me straight into stock hehe :good::good: Though I'm still curious how long until I can root it
Have you tried the auto root course??
Sent from behind you
Boot recovery, then reboot system. It should ssk if you want to root.
Better yet, flash one of our roms. Or, download the supersu zip file from chainfires thread. (Or in my sig, but its not up to date)
---------- Post added at 09:12 PM ---------- Previous post was at 09:11 PM ----------
There are several ways to root. But if you don't get rid of knox iits almost pointless.
Co-author root didn't work, and nor did Root66
I'm on the same boat
Same here,
Mine was rooted, then
I Updated to Factory 4.3
Same red letters and can't get it back,
I want to 'cause it's unstable and
it has weird partition, "emulated/0"
Any Help Please !!
This is why everyone should try to search for information on anything and everything before flashing it to your device. Even if its an official update.
As stated many, many times, once you flash the 4.3 update, you cannot flash older firmware again. Roms are ok, older firmware can brick you. Your weird folder is androids implementation of user profiles if I understand it right. May as well get used to it now, I don't think its going away.
And for those interested, the root66 firmware works fine now as far as I can tell.
If you experience instability, you need to factory reset.
DocHoliday77 said:
This is why everyone should try to search for information on anything and everything before flashing it to your device. Even if its an official update.
As stated many, many times, once you flash the 4.3 update, you cannot flash older firmware again. Roms are ok, older firmware can brick you. Your weird folder is androids implementation of user profiles if I understand it right. May as well get used to it now, I don't think its going away.
And for those interested, the root66 firmware works fine now as far as I can tell.
If you experience instability, you need to factory reset.
Click to expand...
Click to collapse
If I did softbrick it, is there anyway to restore it?
You can try first wiping just dalvik and cache, then try factory reset.
Other ROMs
DocHoliday77 said:
This is why everyone should try to search for information on anything and everything before flashing it to your device. Even if its an official update.
As stated many, many times, once you flash the 4.3 update, you cannot flash older firmware again. Roms are ok, older firmware can brick you. Your weird folder is androids implementation of user profiles if I understand it right. May as well get used to it now, I don't think its going away.
And for those interested, the root66 firmware works fine now as far as I can tell.
If you experience instability, you need to factory reset.
Click to expand...
Click to collapse
Thank you Doc , It has been said ..Over and over and over.. OTA 4.3 update means you cannot flash older firmware again! I was one of the lucky that waited and installed you ROM and it has been stable . I placed a few Mods like Apps For 4.3 TW
For those just refused to READ and have NOT done a OTA update to 4.3 Like DocHoliday77 and and many have said .. here goes one more time..
WARNING!!!
If you have NOT updated via the official firmware or OTA update, it is highly recommended that you do NOT do so at this time!
You can still run these roms and gain every advantage, with none of the problems!
There so many other 4.3 ROMs to play with DocHolidays, Sarahai, mrRobinson and now aamir123. . YOu just to READ before run in head first into the OTA.
I have been trying to keep up with all the 4.3 update stuff but its just so hard with 15 different threads and it being updated everyday. I stupidly updated OTA 4.3 before coming on here and reading and it blows! Samsung is stupid for releasing such a unpolished update. But besides the point, I have been having a problem with out going calls, and battery life. When I will press to call someone the call ends instantly and I have to restart phone for it to allow me to call out. Has anyone else had this problem?
Also, are we any closer to getting 4.3 rooted? I know developers are having problems with Knox etc? If not is there anything I can do to make this update better or do I just have to suck it up? Thanks for the help guys.
I alrdy talked to people at samsung and complained beyond belief, but I dont think the out sourced help desk person understood me.
I made it !!
How ?
1. Uninstall KNOX with Titanium.
2. Flash CWM twice (first one failed), Now I have CWM.
3. Download T999UVDMD5 (Deodexed)
4. Flash it via CWM.
5. Voilà !!
Now It has the partition as it comes from Factory !.
It's there a version similar to this one, running on Android 4.3 (Stock Deodexed, Without KNOX) ?
DocHoliday77 said:
You can try first wiping just dalvik and cache, then try factory reset.
Click to expand...
Click to collapse
So I have a question Doc, I know I posted about this in the CM11 unofficial thread as well, but I am running your Non-Knox, CiQ free version and I have CWM installed, and I'm perfectly rooted after I updated SuperSU from the Play Store, but when I try to CWM Flash a rom it throws an error about the ro.bootloader and it lists out all the older bootloaders. So what I guess I'm getting to is what would it take to use the new bootloaders with any of the ROMs?
bentheexo said:
So I have a question Doc, I know I posted about this in the CM11 unofficial thread as well, but I am running your Non-Knox, CiQ free version and I have CWM installed, and I'm perfectly rooted after I updated SuperSU from the Play Store, but when I try to CWM Flash a rom it throws an error about the ro.bootloader and it lists out all the older bootloaders. So what I guess I'm getting to is what would it take to use the new bootloaders with any of the ROMs?
Click to expand...
Click to collapse
If you have updated to official 4.3 by any means then don't try to downgrade your boot loader and rom as it may brick device
If you have not taken official update then it depends what is your current boot loader and what rom you are trying to flash
So if you are sure that you haven't gone for official update then you flash dmd5 firmware then try to flash rom
Be sure before doing anything
Sent from my SGH-T999 using Tapatalk
I am on a rooted stock ROM 4.1.2 (LDMF1) on an i747m.
Can someone point me to an upgrade procedure to KK?
desirus said:
I am on a rooted stock ROM 4.1.2 (LDMF1) on an i747m.
Can someone point me to an upgrade procedure to KK?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1725839 is full of ressources.
What exactly are you trying to do? Get the official update or flash a custom rom?
If you want the official, remove root and install the OTA (you can use towelroot afterward to root).
If you want a custom rom, follow the FULL instructions in the rom's OP that you choose.
BWolf56 said:
http://forum.xda-developers.com/showthread.php?t=1725839 is full of ressources.
What exactly are you trying to do? Get the official update or flash a custom rom?
If you want the official, remove root and install the OTA (you can use towelroot afterward to root).
If you want a custom rom, follow the FULL instructions in the rom's OP that you choose.
Click to expand...
Click to collapse
Thank you
I want to the official ROM for KK, which I can find.
OK so from what you said the first thin I do is unroot? I will research that.
I was wondering if I can go direct from 4.1.2 to 4.4.2?
I would use ODIN on my PC?
Do I have to do any sort of backing up ( I have Titanium pro) before hand, restore procedures?
desirus said:
Thank you
I want to the official ROM for KK, which I can find.
OK so from what you said the first thin I do is unroot? I will research that.
I was wondering if I can go direct from 4.1.2 to 4.4.2?
I would use ODIN on my PC?
Do I have to do any sort of backing up ( I have Titanium pro) before hand, restore procedures?
Click to expand...
Click to collapse
Tibu is my fav backup app, just make sure you don't restore system app/data. Just make a batch backup and restore once you've flashed KK.
Unroot can be done directly in SuperSU (app).
Yes you can go directly to KK (or any other version), just don't downgrade once you'll have the 4.3+ bootloader or you'll brick your device.
And yes, use Odin on your PC, mobile Odin doesn't flash bootloaders.
The entire process is fairly simple. Just gotta be patient
galaxy S3 AT&T: from stock 4.1.2 to 4.4.2
I am new to these forms, please help me with my questions.
I have a smartphone SGS III AT&T. It is unlocked and working perfect with:
ROM: 4.1.2 Stock
Baseband: DMG2
Kernel: 3.0.31-1300972
Build Number: JZO54K.I747UCDMG2
I am not in USA, so my Smartphone is unlocked.
Initially I used the *#197328640# commands to unlock it
I want to apply enewman17 thread http://forum.xda-developers.com/showthread.php?t=2789917 to upgrade to 4.4.2
My questions are:
1. When the procedure is finished, the smartphone still unlocked?
2. If it became locked, is there a free procedure to release it again?
regards
franzrocamolina said:
I am new to these forms, please help me with my questions.
I have a smartphone SGS III AT&T. It is unlocked and working perfect with:
ROM: 4.1.2 Stock
Baseband: DMG2
Kernel: 3.0.31-1300972
Build Number: JZO54K.I747UCDMG2
I am not in USA, so my Smartphone is unlocked.
Initially I used the *#197328640# commands to unlock it
I want to apply enewman17 thread http://forum.xda-developers.com/showthread.php?t=2789917 to upgrade to 4.4.2
My questions are:
1. When the procedure is finished, the smartphone still unlocked?
2. If it became locked, is there a free procedure to release it again?
regards
Click to expand...
Click to collapse
Unlock is "permanent". You shouldn't lose root but everything you do is at your own risk.
AT&T I747 from 4.1.2 to 4.4.2 Perfect procedure
BWolf56 said:
Unlock is "permanent". You shouldn't lose root but everything you do is at your own risk.
Click to expand...
Click to collapse
BWolf56...you are right!!!
Ran all procedure http://forum.xda-developers.com/show....php?t=2789917.
My I747 AT&T is now in 4.4.2. No problems at all. Still Unlocked.
One point more:
When I was in 4.1.2 Stock, I was not able to use "USB Theter" because I am not with AT&T SIM Card. With this version I can USB Theter without restriction.
unrooted 4.1.1 won't update dead android
My AT&T SG3 was rooted until yesterday with stock 4.1.1. I unrooted, re flashed stock image and stock recovery. The phone status says "Normal" now so I think I successfully unrooted. When I try to do the OTA after downloading, it goes to a screen which says installing then updating with an incremental percent counter. When it reaches about 29%, it just reboots and comes back with "Install Interrupted The software update could not be installed". When I do "adb reboot recovery" from a command window, I see a dead android with a red triangle and I assume that has something to do with it or is some kind of symptom. Is there anything I can do to get the latest stock image installed? Did I miss something in the unroot process?
SGH-I747 4.1.1 1747UCDLK3
hannahse said:
My AT&T SG3 was rooted until yesterday with stock 4.1.1. I unrooted, re flashed stock image and stock recovery. The phone status says "Normal" now so I think I successfully unrooted. When I try to do the OTA after downloading, it goes to a screen which says installing then updating with an incremental percent counter. When it reaches about 29%, it just reboots and comes back with "Install Interrupted The software update could not be installed". When I do "adb reboot recovery" from a command window, I see a dead android with a red triangle and I assume that has something to do with it or is some kind of symptom. Is there anything I can do to get the latest stock image installed? Did I miss something in the unroot process?
SGH-I747 4.1.1 1747UCDLK3
Click to expand...
Click to collapse
I'm in the exact same boat. I was rooted with stock rom and recovery previously. No matter what I've done, it always fails.
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
Yellow triangle did not solve problem
hannahse said:
My AT&T SG3 was rooted until yesterday with stock 4.1.1. I unrooted, re flashed stock image and stock recovery. The phone status says "Normal" now so I think I successfully unrooted. When I try to do the OTA after downloading, it goes to a screen which says installing then updating with an incremental percent counter. When it reaches about 29%, it just reboots and comes back with "Install Interrupted The software update could not be installed". When I do "adb reboot recovery" from a command window, I see a dead android with a red triangle and I assume that has something to do with it or is some kind of symptom. Is there anything I can do to get the latest stock image installed? Did I miss something in the unroot process?
SGH-I747 4.1.1 1747UCDLK3
Click to expand...
Click to collapse
I spent several hours on this again today. I thought I had discerned the fix when I found a post showing the custom download count on the download screen and references to the yellow triangle program to reset it. I rerooted the phone, put stock recovery back, zeroed out the counter with yellow triangle, put the stock image back with ODIN, factory reset, and ended up with an unrooted phone with zero count. The download screen now says:
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
QUALCOMM SECUREBOOT: ENABLE (in light Grey)
I thought that would do it but the OTA still fails and I still see the red triangle on the stock recovery page. The only thing I can think of now is that SuperSU is still on the phone. It is disabled but still has 12KB of data that I don't know how to clear. I used the stock image from the skipsoft Android Toolkit.
Any ideas would be really appreciated.
I would steer clear of the toolkit. Follow enewman17's how to update thread in the General section. Seems to have a pretty good success rate.
get KK 4.4.2 in your AT&T SG3 without OTA
BWolf56 said:
Unlock is "permanent". You shouldn't lose root but everything you do is at your own risk.
Click to expand...
Click to collapse
hannahse said:
My AT&T SG3 was rooted until yesterday with stock 4.1.1. I unrooted, re flashed stock image and stock recovery. The phone status says "Normal" now so I think I successfully unrooted. When I try to do the OTA after downloading, it goes to a screen which says installing then updating with an incremental percent counter. When it reaches about 29%, it just reboots and comes back with "Install Interrupted The software update could not be installed". When I do "adb reboot recovery" from a command window, I see a dead android with a red triangle and I assume that has something to do with it or is some kind of symptom. Is there anything I can do to get the latest stock image installed? Did I miss something in the unroot process?
SGH-I747 4.1.1 1747UCDLK3
Click to expand...
Click to collapse
I did the same than you and also what n01un0 says but couldn't get OTA update to 4.3 or 4.4.2.
If you want the 4.4.2 in your S3, follow enewman17's http://forum.xda-developers.com/showthread.php?t=2789917 Thread.
It worked perfect for me from 4.1.2 stock to 4.4.2. The final result is the same that you get by OTA (if OTA works)
unrooted 4.1.1 won't update dead android - solved
hannahse said:
My AT&T SG3 was rooted until yesterday with stock 4.1.1. I unrooted, re flashed stock image and stock recovery. The phone status says "Normal" now so I think I successfully unrooted. When I try to do the OTA after downloading, it goes to a screen which says installing then updating with an incremental percent counter. When it reaches about 29%, it just reboots and comes back with "Install Interrupted The software update could not be installed". When I do "adb reboot recovery" from a command window, I see a dead android with a red triangle and I assume that has something to do with it or is some kind of symptom. Is there anything I can do to get the latest stock image installed? Did I miss something in the unroot process?
SGH-I747 4.1.1 1747UCDLK3
Click to expand...
Click to collapse
I solved my problem by a convoluted process that I could not recommend but will lay out as best I can in case anyone is that desperate. I had re-rooted and un-rooted a couple times since my last post and finally decided to try a different stock image. I found a link to one in an article
how-to-unroot-att-galaxy-s3-sgh-i747 (sorry - not allowed to post URL)
The link is to stockroms.net. Really slow download - it took a couple hours. After the download (and unzip),
I attached my unrooted phone via USB cable to my computer.
Installed it with ODIN and watched the phone reboot
It seem to get stuck on the Samsung splash screen.
I went into recovery mode and noticed that - at last - I did not have the red triangle and no dead android. I tried wiping the cache a couple times from the recovery screen but it still seemed to get stuck at the splash screen (not sure if I waited long enough).
I finally did the factory reset from the recovery and it finally came back to life and went through the whole initialization thing. I confirmed a couple times that the red triangle was gone and noted that I had gone from Android version 4.1.1 to 4.04. Maybe that was the key or maybe I had a bad stock version of 4.1.1. IDK. But I started going through a series of updates. I am currently at version 4.3 and downloading what I hope will be the last update.
Started with 4.1.1 and used outdated stock image to go back to
4.04 - small update but version still
4.04 - cleared data from AT&T Update App to get around the wait 24 hours - got the update installed to version
4.1.2 - checked for update and got upgraded to
4.3 - check for update wanted me to wait 24 hours and I could not see how to clear the data - so changed the phone's date to next day. Automatically started downloading a new update - I'm hoping its the last
The development for the AT&T I747 has been discontinued by the developer. Thank you for your support.
WARNING: YOU COULD BRICK YOUR PHONE
UCUFNJ1 4.4.2 incremental update contains firmware.... bootloaders and modem baseband.
MUST BE ON UCUFNE4 FIRMWARE TO CONTINUE!!! Guide can be found here. http://forum.xda-developers.com/gal...are-update-t2808654/post53984772#post53984772
This is the perfect time to use this update to return your S3 to stock for resale or whatever. Download and save these files for when you are ready to return your phone to stock.
*This is a rooted NE4 system.img, stock recovery.img and boot.img. The install script will format system and factory data reset. /media is safe.*
1. Flash restore zip in a custom recovery. CWM, TWRP, Philz. https://www.androidfilehost.com/?fid=95784891001611561
2. Boot your phone and go through setup.
3. Use triangle away and clear your counter. http://forum.xda-developers.com/galaxy-s2/orig-development/2014-01-15-triangleaway-v3-26-t1494114
4. *Optional* If you want a clean un-rooted phone for the update do this now! , Go into SuperSu >settings>full unroot.
5. Reboot your phone.
6. Search for the OTA in the about settings, download and let the phone update.
Or download this and place in the root of your phones internal storage. Reboot into recovery and select the update from update.zip https://www.androidfilehost.com/?fid=95784891001611091
Advanced users.
The original OTA cfg file. https://www.androidfilehost.com/?fid=95784891001611092
.cfg file goes in root/cache/fota
Rename the .cfg extension to .zip and you can rename it update.zip yourself or you can actually flash it in a custom recovery once renamed. if you choose not to use the stock recovery to update.
*You will loose root during the update* But the bootloader is not locked so you can still Odin your favorite recovery and flash SuperSU.
TWRP 2.8.1.0 Odin tar. http://techerrata.com/file/twrp2/d2att/openrecovery-twrp-2.8.1.0-d2att.tar
SuperSU http://download.chainfire.eu/589/SuperSU/UPDATE-SuperSU-v2.16.zip?retrieve_file=1
Once you flash your favorite recovery via Odin, you need to be ready to hold the Volume Up, Power and Home button combo when Odin reboots your phone. If you don't catch it, once the OS boots it will replace recovery with the stock version. Once SuperSU is installed your recovery will stick.
Flashable Rooted NJ1 system.img and boot.img
MD5: 6df80e42df56ddf90512f4162e645cb3
Download: https://www.androidfilehost.com/?fid=95784891001613266
Flashable NJ1 Bootloaders and modem. *Must be on NE4 bootloaders prior to flashing.*
Download: https://www.androidfilehost.com/?fid=95832962473396872
Thanks enewman for writing this up.
Doing Vice Versa Method?
Just to be clear, what if my galaxy s3 is on UCUFNJ1 and I want to go back to UCUFNE4, I can still ODIN the custom recovery and flash SuperSU?
Galaxy S3 I747
Baseband: I747UCUFNJ1
For the advanced users, should we be able to install the update without any issues? I saw in another thread that someone had installed but now their phone will not boot past the Samsung logo to anything other than a black screen.
Also, do we know what this update contains yet? Other than new bootloaders, removal of root, etc.
mattsternc said:
For the advanced users, should we be able to install the update without any issues? I saw in another thread that someone had installed but now their phone will not boot past the Samsung logo to anything other than a black screen.
Also, do we know what this update contains yet? Other than new bootloaders, removal of root, etc.
Click to expand...
Click to collapse
You know if your not wanting to return your phone to stock I really wouldn't mess with this update. Far as the user who couldn't boot... Idk I wasn't there to watch them update. This whole mess with the S3 is exhausting. We haven't got a real Odin release so I'm woking with what I can extract from my phone after updating. The system.img in ne4 zip is 100% stock except for root. So I know the update worked because I did it. Also not sure what was updated either... The kernel yes... Firmware yes, all the system apps get patched so without decompiling ne4 and nj1 apps and comparing them afraid I have no idea what the update fixes or improves.
Thanks for all you do for us S3 owners, enewman17.
If we upgrade to the new NJ1 firmware, and then flash your latest SRX Rom, I assume we cannot then use your "restore.zip" to once again go back to NE4 stock since we would be on NJ1 bootloader? If so, is there a way to go back to NJ1 stock if we later want to sell our phone?
OKAstro said:
Thanks for all you do for us S3 owners, enewman17.
If we upgrade to the new NJ1 firmware, and then flash your latest SRX Rom, I assume we cannot then use your "restore.zip" to once again go back to NE4 stock since we would be on NJ1 bootloader? If so, is there a way to go back to NJ1 stock if we later want to sell our phone?
Click to expand...
Click to collapse
I have the nj1 system dump, I'll get it uploaded so anyone who updates can restore back to stock.
enewman17 said:
I have the nj1 system dump, I'll get it uploaded so anyone who updates can restore back to stock.
Click to expand...
Click to collapse
Thanks again my man.
Towelroot no longer works after the NJ1 update. Can the CF-AutoRoot still be used? The only version at http://autoroot.chainfire.eu/ says it's for 4.0.4.
Ark42 said:
Towelroot no longer works after the NJ1 update. Can the CF-AutoRoot still be used? The only version at http://autoroot.chainfire.eu/ says it's for 4.0.4.
Click to expand...
Click to collapse
Not sure if it still works but read the op you can Odin a custom recovery then flash super su.
enewman17 said:
Not sure if it still works but read the op you can Odin a custom recovery then flash super su.
Click to expand...
Click to collapse
Yeah, I saw that, but I never had a custom recovery before, that I know of at least, and I suspect a lot of other people finding this thread in the coming days are going to be in the same boat as me. They just want SuperSU so their favorite 1 or 2 apps that require SU can continue to work.
Has anybody tried CF-AutoRoot yet on the NJ1 4.4.2?
Ark42 said:
Yeah, I saw that, but I never had a custom recovery before, that I know of at least, and I suspect a lot of other people finding this thread in the coming days are going to be in the same boat as me. They just want SuperSU so their favorite 1 or 2 apps that require SU can continue to work.
Has anybody tried CF-AutoRoot yet on the NJ1 4.4.2?
Click to expand...
Click to collapse
Agreed! I'm the same boat as you.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Ark42 said:
Yeah, I saw that, but I never had a custom recovery before, that I know of at least, and I suspect a lot of other people finding this thread in the coming days are going to be in the same boat as me. They just want SuperSU so their favorite 1 or 2 apps that require SU can continue to work.
Has anybody tried CF-AutoRoot yet on the NJ1 4.4.2?
Click to expand...
Click to collapse
Tell you what, when I get home from work I will try cfauto root and see if it works.
enewman17 said:
Not sure if it still works but read the op you can Odin a custom recovery then flash super su.
Click to expand...
Click to collapse
I can confirm this as a root method for NJ1. You were exactly right regarding immediately booting into recovery after installing TWRP thru Odin. The files provided in your links (TWRP 2.8.1.0 Odin tar. http://techerrata.com/file/twrp2/d2a....1.0-d2att.tar and
SuperSU http://download.chainfire.eu/589/Sup...etrieve_file=1)
worked exactly as stated.
A BIG thanks to you. I can't live without AdAway, TiBackup and Xposed anymore! The few days without root left me a little grumpy.
And regarding the NJ1 update as a whole...I THINK the baseband upgrade IS an actual upgrade. Since NE4, I always thought Wifi operated was somewhat choppy/throttled. THIS looks to have been improved back to ICS "standards". Re: voice, I've had a handful of dropped calls, broken up calls, and choppy data in low signal areas over the past few months on with NE4. Initial observations (albeit a tad premature) lead me to believe that this has improved as well based on a weeks worth of data use and a few calls in a "controlled" environment (the area and physical structure of my work office complex is not cellular signal friendly to begin with) I have also noticed that boot-up time has improved a bit as well. Thanks again for your efforts with the ATT GS3!
I flashed CF-Auto ROOT via Odin without success, unable to gain root access. Followed your instructions via TWRP and flashed SuperSu 2.16, my SGS3-i747 is properly rooted and functioning perfectly on UCUFNJ1. As always, thank you very kindly for all your valuable time, effort, hard work and guidance. Be well, sir!
mwrobe1 said:
I can confirm this as a root method for NJ1. You were exactly right regarding immediately booting into recovery after installing TWRP thru Odin. The files provided in your links (TWRP 2.8.1.0 Odin tar. http://techerrata.com/file/twrp2/d2a....1.0-d2att.tar and
SuperSU http://download.chainfire.eu/589/Sup...etrieve_file=1)
worked exactly as stated.
Click to expand...
Click to collapse
What version of Odin do we need to flash that TWRP, or do you have a link handy?
I've seen quite a lot of different Odins out there and don't want to brick my phone by using the wrong one.
Any pitfalls to watch out for if using TWRP for the first time? I'm sure there is going to be a bunch of people having to do this now that both CF-AutoRoot and TowelRoot doesn't work anymore.
For me, personally, I just use root for AdFree and to edit the font fallback order to properly support Japanese instead of Chinese glyphs on shared Han-unified Unicode codepoints.
Ark42 said:
What version of Odin do we need to flash that TWRP, or do you have a link handy?
I've seen quite a lot of different Odins out there and don't want to brick my phone by using the wrong one.
Any pitfalls to watch out for if using TWRP for the first time? I'm sure there is going to be a bunch of people having to do this now that both CF-AutoRoot and TowelRoot doesn't work anymore.
For me, personally, I just use root for AdFree and to edit the font fallback order to properly support Japanese instead of Chinese glyphs on shared Han-unified Unicode codepoints.
Click to expand...
Click to collapse
Use Odin 3.0.7
Not really any pitfalls to TWRP. It has an easy clean user interface and it works.
Once you have flash Super Su, in my how to ne4 update there is a flashable stock recovery. You just flash it with TWRP and once you reboot, stock recovery will be back on you phone.
Hi enewman17,
Thanks for your posts and work. I'm hoping you can help me get the new NJ1 update installed and rooted.
Here's where I'm at: AT&T SGS3 on rooted stock NE4, installed using your guides from back in June this year.
The OTA NJ1 update downloaded but failed to install (as did the NE4 OTA back then, I assume because I was rooted).
My phone still has the TWRP recovery from the previous update, so I was hoping I could install using the original OTA cfg file download from the "advanced" section in your OP so as to avoid factory reset, etc.
I downloaded the file, renamed to update.zip, and copied to my SD card. However, when I boot into TWRP and try to install it, I get an error after the system check, something like "assert failed ro.secure==1". I guess I'm doing something wrong, maybe I'm mistaken about how the original OTA is supposed to work?
Again, I'm trying to end up with a stock, but rooted, NJ1 firmware but hopefully without having to reset/lose data and settings on the phone. I don't really care right now about resale or making it look like I haven't messed with it.
Thanks for any help you can provide! Let me know if I can provide any additional details.
I am actually looking to do the exact same thing. Currently rooted, with a lot of the AT&T apps frozen via Titanium Backup.
Hope there is some way to accomplish this without returning to stock!
Thanks in advance!
Bob2014 said:
Hi enewman17,
Thanks for your posts and work. I'm hoping you can help me get the new NJ1 update installed and rooted.
Here's where I'm at: AT&T SGS3 on rooted stock NE4, installed using your guides from back in June this year.
The OTA NJ1 update downloaded but failed to install (as did the NE4 OTA back then, I assume because I was rooted).
My phone still has the TWRP recovery from the previous update, so I was hoping I could install using the original OTA cfg file download from the "advanced" section in your OP so as to avoid factory reset, etc.
I downloaded the file, renamed to update.zip, and copied to my SD card. However, when I boot into TWRP and try to install it, I get an error after the system check, something like "assert failed ro.secure==1". I guess I'm doing something wrong, maybe I'm mistaken about how the original OTA is supposed to work?
Again, I'm trying to end up with a stock, but rooted, NJ1 firmware but hopefully without having to reset/lose data and settings on the phone. I don't really care right now about resale or making it look like I haven't messed with it.
Thanks for any help you can provide! Let me know if I can provide any additional details.
Click to expand...
Click to collapse
Bob2014 said:
Hi enewman17,
Thanks for your posts and work. I'm hoping you can help me get the new NJ1 update installed and rooted.
Here's where I'm at: AT&T SGS3 on rooted stock NE4, installed using your guides from back in June this year.
The OTA NJ1 update downloaded but failed to install (as did the NE4 OTA back then, I assume because I was rooted).
My phone still has the TWRP recovery from the previous update, so I was hoping I could install using the original OTA cfg file download from the "advanced" section in your OP so as to avoid factory reset, etc.
I downloaded the file, renamed to update.zip, and copied to my SD card. However, when I boot into TWRP and try to install it, I get an error after the system check, something like "assert failed ro.secure==1". I guess I'm doing something wrong, maybe I'm mistaken about how the original OTA is supposed to work?
Again, I'm trying to end up with a stock, but rooted, NJ1 firmware but hopefully without having to reset/lose data and settings on the phone. I don't really care right now about resale or making it look like I haven't messed with it.
Thanks for any help you can provide! Let me know if I can provide any additional details.
Click to expand...
Click to collapse
I'll get my stock rooted system dump up later so you can flash in TWRP or CWM.
Do you guys want it packaged with the stock recovery?
mattsternc said:
I am actually looking to do the exact same thing. Currently rooted, with a lot of the AT&T apps frozen via Titanium Backup.
Hope there is some way to accomplish this without returning to stock!
Thanks in advance!
Click to expand...
Click to collapse