I decided to try cyanogenmod on my SGH-I747 but have had so many issues I would be happy at this point if I could just get a working phone again.
I started with a 4.3 OTA-updated phone. I rooted the phone, then tried to install the latest 10.2 ROM. I also tried 10.1. I used CWM: I would have preferred the latest version but the best I could find that was not an .img file (I used Odin) was in the 5.x range. In both cases I hit what I believe is a bootloader error ("assert failed: ... Status 7"). At this point the phone is wiped with no recourse. I attempted to install the stock boot image for the I747, but after doing so the phone will no longer boot.
EDIT: I am able to get to downloading mode. I am afraid to use it to install stock firmware b/c of a post I found here claiming that downgrading from 4.3 OTA (e.g., to 4.1) will brick the phone.
tn6 said:
I decided to try cyanogenmod on my SGH-I747 but have had so many issues I would be happy at this point if I could just get a working phone again.
I started with a 4.3 OTA-updated phone. I rooted the phone, then tried to install the latest 10.2 ROM. I also tried 10.1. I used CWM: I would have preferred the latest version but the best I could find that was not an .img file (I used Odin) was in the 5.x range. In both cases I hit what I believe is a bootloader error ("assert failed: ... Status 7"). At this point the phone is wiped with no recourse. I attempted to install the stock boot image for the I747, but after doing so the phone will no longer boot.
EDIT: I am able to get to downloading mode. I am afraid to use it to install stock firmware b/c of a post I found here claiming that downgrading from 4.3 OTA (e.g., to 4.1) will brick the phone.
Click to expand...
Click to collapse
i actually had the same problem earlier today. what i did was use odin to install clockworkmod recovery. after it reboots, hold VOLUME UP and HOME at the same time. if you have a micro sd handy, download any of the two updates here http://forum.xda-developers.com/showthread.php?t=2498233 place them on you sd card and in recovery format cache and factory reset/data. then highlight "install zip from sd card" or something that sounds relevant. select the zip you placed on your sd card earlier and there.
Worked, I think
MrHaPpY66 said:
i actually had the same problem earlier today. what i did was use odin to install clockworkmod recovery. after it reboots, hold VOLUME UP and HOME at the same time. if you have a micro sd handy, download any of the two updates here http://forum.xda-developers.com/showthread.php?t=2498233 place them on you sd card and in recovery format cache and factory reset/data. then highlight "install zip from sd card" or something that sounds relevant. select the zip you placed on your sd card earlier and there.
Click to expand...
Click to collapse
Thank you. The phone now boots to a white screen with an AT&T symbol. How can I install either a stock or custom ROM without ruining everything again?
tn6 said:
Thank you. The phone now boots to a white screen with an AT&T symbol. How can I install either a stock or custom ROM without ruining everything again?
Click to expand...
Click to collapse
i think this should be a help http://forum.xda-developers.com/showthread.php?t=2539313
No luck
MrHaPpY66 said:
i think this should be a help http://forum.xda-developers.com/showthread.php?t=2539313
Click to expand...
Click to collapse
That appears to be the standard tutorial for rooting/flashing. I did it anyway, even though didn't the file you had me install before already root the phone? In any event, I ran CF-root and then I attempted to install CM 10.2 and it failed: "failed to verify whole-file signature." I believe that was the first error I hit in the beginning of this exercise. Additionally, now I get an error on the welcome screen that says "Unfortunately, SuperSU has stopped."
tn6 said:
That appears to be the standard tutorial for rooting/flashing. I did it anyway, even though didn't the file you had me install before already root the phone? In any event, I ran CF-root and then I attempted to install CM 10.2 and it failed: "failed to verify whole-file signature." I believe that was the first error I hit in the beginning of this exercise. Additionally, now I get an error on the welcome screen that says "Unfortunately, SuperSU has stopped."
Click to expand...
Click to collapse
for the supersu, you probably need to go update it on the market or disable KNOX
assert failed... getprop("ro.bootloader")
MrHaPpY66 said:
for the supersu, you probably need to go update it on the market or disable KNOX
Click to expand...
Click to collapse
Thanks for the suggestion. I went back to the no-KNOX file you pointed out earlier. I assume that is the same type of file as the CF-Root so I assume I don't need to install CF-root anymore after installing the no-KNOX file. So now I follow the tutorial from your second response minus the root step. I no longer get the SuperSU error. However, I still can't load a ROM. I get the same "assert failed... getprop("ro.bootloader... Status 7" that I mentioned in my first post. When I googled this in the first round, I saw several posts saying it means I had a bad bootloader. That is when I tried to flash the stock bootloader, which nearly hardbricked the phone. Do the two files you initially posted include a bootloader file?
tn6 said:
Thanks for the suggestion. I went back to the no-KNOX file you pointed out earlier. I assume that is the same type of file as the CF-Root so I assume I don't need to install CF-root anymore after installing the no-KNOX file. So now I follow the tutorial from your second response minus the root step. I no longer get the SuperSU error. However, I still can't load a ROM. I get the same "assert failed... getprop("ro.bootloader... Status 7" that I mentioned in my first post. When I googled this in the first round, I saw several posts saying it means I had a bad bootloader. That is when I tried to flash the stock bootloader, which nearly hardbricked the phone. Do the two files you initially posted include a bootloader file?
Click to expand...
Click to collapse
i think they contained the mj2 bootloader and modem. hmm i've been doing a little snooping around and i found this. http://forum.xda-developers.com/showthread.php?t=2540998 the thing is i still don't understand how to go from leaked (mj2) to the official release (mjb) maybe updating to this will help
MrHaPpY66 said:
i think they contained the mj2 bootloader and modem. hmm i've been doing a little snooping around and i found this. http://forum.xda-developers.com/showthread.php?t=2540998 the thing is i still don't understand how to go from leaked (mj2) to the official release (mjb) maybe updating to this will help
Click to expand...
Click to collapse
I'm worried about switching bootloaders. This post seems to indicate that doing so after I installed 4.3 OTA will brick the phone. Does anyone know if that is true?
http://forum.xda-developers.com/showthread.php?t=2321310
tn6 said:
I'm worried about switching bootloaders. This post seems to indicate that doing so after I installed 4.3 OTA will brick the phone. Does anyone know if that is true?
http://forum.xda-developers.com/showthread.php?t=2321310
Click to expand...
Click to collapse
ohh ho ho it's true alright. the new 4.3 bootloader, i'm guessing it is mjb, doesn't allow any downgrades. Downgrades of any kind will absolutely give you a nice, good brick. anyways do you understand how to go from 4.3 leaked to 4.3 official?
MrHaPpY66 said:
ohh ho ho it's true alright. the new 4.3 bootloader, i'm guessing it is mjb, doesn't allow any downgrades. Downgrades of any kind will absolutely give you a nice, good brick. anyways do you understand how to go from 4.3 leaked to 4.3 official?
Click to expand...
Click to collapse
No idea. I went ahead and tried to install the I747UCDLK3_aio.tar.md5, which I hoped was a 4.3 bootloader (don't know how you are supposed to tell). The error I got was this was another failure--this time saying the package was for d2att and this is a d2spr. My phone is definitely not a sprint phone. Some posts say I have to update the build.prop file, but I don't know how I can do that before a ROM is even installed.
resolved
tn6 said:
No idea. I went ahead and tried to install the I747UCDLK3_aio.tar.md5, which I hoped was a 4.3 bootloader (don't know how you are supposed to tell). The error I got was this was another failure--this time saying the package was for d2att and this is a d2spr. My phone is definitely not a sprint phone. Some posts say I have to update the build.prop file, but I don't know how I can do that before a ROM is even installed.
Click to expand...
Click to collapse
I realized that many of the errors I was getting seemed to be tied to cyanogenmod or stock. So I downloaded Hyperdrive and it installed with zero hiccups or errors. I have a working phone again.
Thank you for your helpful insights.
tn6 said:
I realized that many of the errors I was getting seemed to be tied to cyanogenmod or stock. So I downloaded Hyperdrive and it installed with zero hiccups or errors. I have a working phone again.
Thank you for your helpful insights.
Click to expand...
Click to collapse
you're welcome and i glad i was a help to you. anyways where'd you get hyperdrive? i've been trying to get my phone back to official stock and off the leaked one.
MrHaPpY66 said:
you're welcome and i glad i was a help to you. anyways where'd you get hyperdrive? i've been trying to get my phone back to official stock and off the leaked one.
Click to expand...
Click to collapse
I downloaded hyperdrive from the official spot: http://forum.xda-developers.com/showthread.php?t=2106830. I wouldn't have minded going back to stock, but clearly that was not going to happen any time soon.
tn6 said:
I downloaded hyperdrive from the official spot: http://forum.xda-developers.com/showthread.php?t=2106830. I wouldn't have minded going back to stock, but clearly that was not going to happen any time soon.
Click to expand...
Click to collapse
so how's the rom so far? probably going to get it myself.
MrHaPpY66 said:
so how's the rom so far? probably going to get it myself.
Click to expand...
Click to collapse
Zero issues. Worked great all day with no problems. Plus I am now able to tether and use the mobile hotspot, features that I couldn't get to work on the stock rom even with foxfi or similar apps.
tn6 said:
Zero issues. Worked great all day with no problems. Plus I am now able to tether and use the mobile hotspot, features that I couldn't get to work on the stock rom even with foxfi or similar apps.
Click to expand...
Click to collapse
so i see it's a lot better than stock. i'll install it as soon as i can and thanks for the link to the rom
Related
Does anyone have the stock ATT ROM for this device?
I've had some random issues with it that I'd like to go back to factory stock and see if they're hardware related or not. I've done hours of searching and can't find any information on it anywhere.
Help please?
here you can find stock rooted roms: http://forum.xda-developers.com/showthread.php?t=1584427
Roeni said:
here you can find stock rooted roms: http://forum.xda-developers.com/showthread.php?t=1584427
Click to expand...
Click to collapse
Thanks, but that's the opposite of what I need. I'm currently rooted and want a stock rom back on my phone. It's the non-rooted ROM that I can't find.
I think you can't get that off of samfirware.com I think that's the site
-sent from my insanely awesome captivate glide-
how do you back up your original rom? I could make one for you if you tell me how? I would like to have a backup before I flash anything as well.
dudejb said:
how do you back up your original rom? I could make one for you if you tell me how? I would like to have a backup before I flash anything as well.
Click to expand...
Click to collapse
Follow the rooting guide in the Android developement forum, then instead of flashing the rom first and then the Recovery, flash the recovery first.
Boot into it(volume down + power button) and choose the nandroid backup.
jayjayjoker2 said:
I think you can't get that off of samfirware.com I think that's the site
-sent from my insanely awesome captivate glide-
Click to expand...
Click to collapse
I downloaded the appropriate firmware from that site, but when I apply the update in recovery mode it does the following (the green text should be yellow, but I figured you'd like to be able to read it):
Code:
[COLOR="Green"]-- Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...[/COLOR]
[COLOR="Red"]E:signature verification failed[/COLOR]
[COLOR="Green"]install_package = (2)
Installation aborted.[/COLOR]
This is the firmware I downloaded: http://www.sammobile.com/firmware/?page=3&t=1&o=1&m=SGH-I927&r=5#regiona
you need CWMR (clockwork mod recovery) I don't know how to do that with this phone
-sent from my insanely awesome captivate glide-
jayjayjoker2 said:
you need CWMR (clockwork mod recovery) I don't know how to do that with this phone
-sent from my insanely awesome captivate glide-
Click to expand...
Click to collapse
Or maybe you need to use Samsung kies you should be able to get it from the same site
-sent from my insanely awesome captivate glide-
jayjayjoker2 said:
Or maybe you need to use Samsung kies you should be able to get it from the same site
-sent from my insanely awesome captivate glide-
Click to expand...
Click to collapse
Tried Kies a few times. Not once has it been able to flash the device. It will download the required files, and typically it'll just stop at that point and error out. Once I saw it try to update the device, then go back to the downloading files and then just never go anywhere...
Of course, looking now in Kies, It doesn't even pull a current firmware version, it's just blank space where it should be..
If I remember correctly, FW from samfirmware are Odin flashable....
gabby131 said:
If I remember correctly, FW from samfirmware are Odin flashable....
Click to expand...
Click to collapse
I didn't even think to check that. I'll extract it now and attempt and post back with my findings.
So, flashing the stock rom from SamFirmwares worked great with Odin, no issues. I still have SuperUser installed on the device, but Titanium backup says that it can't get root privileges. My screenshot app works just fine still though, and my AT&T update failed. The download went fine, after it rebooted, the update went to "Preparing" and then "Update is failed" and it rebooted saying the update couldn't be installed at this time...
What on earth am I doing wrong?
Gizmokid2005 said:
So, flashing the stock rom from SamFirmwares worked great with Odin, no issues. I still have SuperUser installed on the device, but Titanium backup says that it can't get root privileges. My screenshot app works just fine still though, and my AT&T update failed. The download went fine, after it rebooted, the update went to "Preparing" and then "Update is failed" and it rebooted saying the update couldn't be installed at this time...
What on earth am I doing wrong?
Click to expand...
Click to collapse
I'm sorry, you mean the flash did not wipe your data? If yes you might need to restore factory settings (wipe data)...then update..
gabby131 said:
I'm sorry, you mean the flash did not wipe your data? If yes you might need to restore factory settings (wipe data)...then update..
Click to expand...
Click to collapse
Nah, I'm not worried about my data. I just want to remove root so I can update to 2.3.6, plus I don't really have much of a reason to be rooted at this point, especially with a confirmed ICS coming "soon"...
Gizmokid2005 said:
Nah, I'm not worried about my data. I just want to remove root so I can update to 2.3.6, plus I don't really have much of a reason to be rooted at this point, especially with a confirmed ICS coming "soon"...
Click to expand...
Click to collapse
i also flashed the stock firmware from samfirmware, and yes it does not wipe data, but does remove root completely....
gabby131 said:
i also flashed the stock firmware from samfirmware, and yes it does not wipe data, but does remove root completely....
Click to expand...
Click to collapse
That's what I was expecting...but Superuser is still installed, though TitaniumBackup complains about not having root privileges, my screenshot app still works, and my OTA update fails.
Gizmokid2005 said:
That's what I was expecting...but Superuser is still installed, though TitaniumBackup complains about not having root privileges, my screenshot app still works, and my OTA update fails.
Click to expand...
Click to collapse
yeah...the SU app is still there but it's functionality is obliterated. So if you are rooted and your device is needed to be serviced, just flash the non-rooted stock ROM (recommended samfirmware) and, you may need to factory reset to perform updates....hopefully this would do the trick
gabby131 said:
yeah...the SU app is still there but it's functionality is obliterated. So if you are rooted and your device is needed to be serviced, just flash the non-rooted stock ROM (recommended samfirmware) and, you may need to factory reset to perform updates....hopefully this would do the trick
Click to expand...
Click to collapse
Well, that's what I did last night, flashed the stock non-rooted ROM from samfirmware last night, I just didn't reset the device settings/data afterwards. I can try resetting the data tonight and see if I can get the OTA update though.
Do you have clock work mod installed? Can that be effecting you from getting your updates if you do?
I think someone already answered this bit can I flash a 4.4 rom if I'm on stock 4.3??
Jairsantana said:
I think someone already answered this bit can I flash a 4.4 rom if I'm on stock 4.3??
Click to expand...
Click to collapse
Yes, but you will have to either modify the assert lines to reflect your new bootloader or delete the assert lines completely. Just be sure you have downloaded a d2spr ROM. And by stock 4.3, did you take the official Knox update or flash a modified Knox-free version?
Mr. Struck said:
Yes, but you will have to either modify the assert lines to reflect your new bootloader or delete the assert lines completely. Just be sure you have downloaded a d2spr ROM. And by stock 4.3, did you take the official Knox update or flash a modified Knox-free version?
Click to expand...
Click to collapse
i took the stock 4.3 with the knox ... im wondering the same thing
xmacx97 said:
i took the stock 4.3 with the knox ... im wondering the same thing
Click to expand...
Click to collapse
My understanding is that you can still root and flash custom ROM's as long as you don't care about permanently tripping the Knox flag. What you definitely do not want to do is try to use Odin to push a stock .tar with a bootloader that is an earlier (pre-Knox) version because Knox will interfere and hard brick your phone.
Mr. Struck said:
Yes, but you will have to either modify the assert lines to reflect your new bootloader or delete the assert lines completely. Just be sure you have downloaded a d2spr ROM. And by stock 4.3, did you take the official Knox update or flash a modified Knox-free version?
Click to expand...
Click to collapse
It is a stock rooted rom without the knox apps!!
Jairsantana said:
It is a stock rooted rom without the knox apps!!
Click to expand...
Click to collapse
That's good, should save you the headache of re-rooting and disabling Knox apps. If you don't know how to modify/delete the assert lines let me know.
Mr. Struck said:
That's good, should save you the headache of re-rooting and disabling Knox apps. If you don't know how to modify/delete the assert lines let me know.
Click to expand...
Click to collapse
Hey can I flash any 4.3 rom without any problems Like cm10??
Jairsantana said:
Hey can I flash any 4.3 rom without any problems Like cm10??
Click to expand...
Click to collapse
That should be a yes. I need to clarify as well, I think I got a little mixed up about who had what with your question and the other question from the user who took the OTA. You will need to know which bootloader you have, if it is the newest MK3 version, then the updater-script will not have your bootloader listed in the assert lines and you will then be required to modify the asserts to reflect your specific bootloader or delete the assert lines altogether. The user who took the OTA should definitely have this version installed. If you are on a previous bootloader like MD4, no modifying or deleting will be necessary with the asserts.
Mr. Struck said:
That should be a yes. I need to clarify as well, I think I got a little mixed up about who had what with your question and the other question from the user who took the OTA. You will need to know which bootloader you have, if it is the newest MK3 version, then the updater-script will not have your bootloader listed in the assert lines and you will then be required to modify the asserts to reflect your specific bootloader or delete the assert lines altogether. The user who took the OTA should definitely have this version installed. If you are on a previous bootloader like MD4, no modifying or deleting will be necessary with the asserts.
Click to expand...
Click to collapse
Ok long story short I did flash the ota zip then root my phone but now I'm runing staticpower rom!!!
Jairsantana said:
Ok long story short I did flash the ota zip then root my phone but now I'm runing staticpower rom!!!
Click to expand...
Click to collapse
OK, so your boot loader should be MK3 then, it is listed under Settings/About Phone if you need to find out for sure, In that case the original info about the assert lines will hold true if you want to flash 4.4; the exception will be the latest builds by Cjen1987, he has already modified the updater-script to remove the asserts and allow TWRP or CWM to flash.
Mr. Struck said:
OK, so your boot loader should be MK3 then, it is listed under Settings/About Phone if you need to find out for sure, In that case the original info about the assert lines will hold true if you want to flash 4.4; the exception will be the latest builds by Cjen1987, he has already modified the updater-script to remove the asserts and allow TWRP or CWM to flash.
Click to expand...
Click to collapse
Ok so that means that I can flash any 4.3 or 4.4???
Jairsantana said:
Ok so that means that I can flash any 4.3 or 4.4???
Click to expand...
Click to collapse
Yes, but again remember that the updater-script contained in most of them will not recognize your boot loader, you will need to modify the updater-script if you flash and get an "Error7" message. The thing everyone with the Knox boot loader needs to keep in mind is that trying to push a .tar file via Odin in order to restore a previous stock build with an older version of the boot loader (I.e. MD4) will hard brick your phone beyond even the help of Chuck Norris because Knox will step in and give you an expensive paperweight!!
Mr. Struck said:
Yes, but again remember that the updater-script contained in most of them will not recognize your boot loader, you will need to modify the updater-script if you flash and get an "Error7" message. The thing everyone with the Knox boot loader needs to keep in mind is that trying to push a .tar file via Odin in order to restore a previous stock build with an older version of the boot loader (I.e. MD4) will hard brick your phone beyond even the help of Chuck Norris because Knox will step in and give you an expensive paperweight!!
Click to expand...
Click to collapse
I need to know how to change the updater-script and will i be able to have the apps2sd opyion like on stock MK3???
Jairsantana said:
I need to know how to change the updater-script and will i be able to have the apps2sd opyion like on stock MK3???
Click to expand...
Click to collapse
I have a tutorial posted on Android Forums for my fellow VM SGS3 users. I will link you to that so that I don't have to type out a long explanation here; doesn't matter what carrier you are on to use this method, it is universal, but it is a must for anyone on VM or Boost to be able to use Sprint ROM's. It has only become an issue lately for Sprint users due to the newest bootloader.
http://androidforums.com/virgin-mobile-galaxy-s3-all-things-root/791952-all-in-one-guide-modifying-custom-sprint-roms-virgin-mobile-use.html
Mr. Struck said:
I have a tutorial posted on Android Forums for my fellow VM SGS3 users. I will link you to that so there hat I don't have to type out a long explanation here; doesn't matter what carrier you are on to use this method, it is universal, but it is a must for anyone on VM or Boost to be able to use Sprint ROM's. It has only become an issue lately for Sprint users due to the newest bootloader.
http://androidforums.com/virgin-mobile-galaxy-s3-all-things-root/791952-all-in-one-guide-modifying-custom-sprint-roms-virgin-mobile-use.html
Click to expand...
Click to collapse
Hey so I was able to flash the official CM11,everything fine the only problem is that I couln't move the apps to my sdcard like on the mk3 rom is there anything I can do or I just have to deal with it???
Jairsantana said:
Hey so I was able to flash the official CM11,everything fine the only problem is that I couln't move the apps to my sdcard like on the mk3 rom is there anything I can do or I just have to deal with it???
Click to expand...
Click to collapse
I think apps to SD card is an issue specific to 4.4 currently, I have seen other people with this issue as well. Just opened Titanium Backup on my phone to see, option used to be available but is currently not there. Maybe will be addressed further down the line, don't really have an answer though.
Mr. Struck said:
I think apps to SD card is an issue specific to 4.4 curreI was tly, I have seen other people se ingth this issue as well. Just opened Titaium Backup on my phone to see, option used to be available but is currently not there. Maybe will be addressed further down the line, don't really have an answer though.
Click to expand...
Click to collapse
Ok let me re ask the question because you may or may not answer my question the way i referring about....when you go in the mk3 to settings/applications manager/ we have some options like....downloaded/sd card/running/all..... but in CM11 i don't see the sdcard option!!!
Jairsantana said:
Ok let me re ask the question because you may or may not answer my question the way i referring about....when you go in the mk3 to settings/applications manager/ we have some options like....downloaded/sd card/running/all..... but in CM11 i don't see the sdcard option!!!
Click to expand...
Click to collapse
I think we are on the same page or real close communication wise. I don't think apps can go to SD card on 4.4, which is why I checked Titanium to see if it still supplied that option. Just make sure to free up as much internal space as possible by putting any file that you can on SD card instead of internal storage.
Mr. Struck said:
I think we are on the same page or real close communication wise. I don't think apps can go to SD card on 4.4, which is why I checked Titanium to see if it still supplied that option. Just make sure to free up as much internal space as possible by putting any file that you can on SD card instead of internal storage.
Click to expand...
Click to collapse
Alright yeah that was my question and how about cm10.2???
Jairsantana said:
Alright yeah that was my question and how about cm10.2???
Click to expand...
Click to collapse
MK3 is the only rom, including both AOSP and TW, that lets you move apps to sdcard
Sorry if i don't understand whats going on this is the first time rooting for me.
I have a SGH-I747
4.3
I am trying to root my phone to be able to run 4.4 on it and have followed the steps here http://forum.xda-developers.com/showthread.php?t=1963790 but once i get back to my home page and try to use superSU I get an error message stating "Unfortunately, SuperSU has stopped." along with "Security information" "An application attempted to access system on your device without authorization. This attempt has been blocked".
Sorry if this is an easy fix or i left out important information but i would just like some help getting off the gound
woerner said:
Sorry if i don't understand whats going on this is the first time rooting for me.
I have a SGH-I747
4.3
I am trying to root my phone to be able to run 4.4 on it and have followed the steps here http://forum.xda-developers.com/showthread.php?t=1963790 but once i get back to my home page and try to use superSU I get an error message stating "Unfortunately, SuperSU has stopped." along with "Security information" "An application attempted to access system on your device without authorization. This attempt has been blocked".
Sorry if this is an easy fix or i left out important information but i would just like some help getting off the gound
Click to expand...
Click to collapse
Rooting the SG3 running stock 4.3 is notoriously difficult. CF AutoRoot may not always work. The instructions below (thanks to XDA Developer upndwn4par), however, works pretty well. The usual disclaimers ... you are trying this at your own risk etc. apply here...
(http://forum.xda-developers.com/showthread.php?t=2538991)
Before rooting your phone, however, please check to see if rooting is really necessary. You may not need root access to install a custom or stock ROM. Custom recovery (e.g. CWM or TWRP) alone may be sufficient.
---------- Post added at 09:43 PM ---------- Previous post was at 09:27 PM ----------
Larry2999 said:
Rooting the SG3 running stock 4.3 is notoriously difficult. CF AutoRoot may not always work. The instructions below (thanks to XDA Developer upndwn4par), however, works pretty well. The usual disclaimers ... you are trying this at your own risk etc. apply here...
(http://forum.xda-developers.com/showthread.php?t=2538991)
Before rooting your phone, however, please check to see if rooting is really necessary. You may not need root access to install a custom or stock ROM. Custom recovery (e.g. CWM or TWRP) alone may be sufficient.
Click to expand...
Click to collapse
I presume also you are trying to install a 4.4 based custom ROM since KitKat is not officially available for the i747?
Larry2999 said:
Rooting the SG3 running stock 4.3 is notoriously difficult. CF AutoRoot may not always work. The instructions below (thanks to XDA Developer upndwn4par), however, works pretty well. The usual disclaimers ... you are trying this at your own risk etc. apply here...
(http://forum.xda-developers.com/showthread.php?t=2538991)
Before rooting your phone, however, please check to see if rooting is really necessary. You may not need root access to install a custom or stock ROM. Custom recovery (e.g. CWM or TWRP) alone may be sufficient.
---------- Post added at 09:43 PM ---------- Previous post was at 09:27 PM ----------
I presume also you are trying to install a 4.4 based custom ROM since KitKat is not officially available for the i747?
Click to expand...
Click to collapse
Yes right now the end result is to try and install KitKat i was looking into http://forum.xda-developers.com/showthread.php?t=2556839 but am having troubles with the rooting part let alone trying to flash a ROM for the first time
Thanks for anything!
woerner said:
Yes right now the end result is to try and install KitKat i was looking into http://forum.xda-developers.com/showthread.php?t=2556839 but am having troubles with the rooting part let alone trying to flash a ROM for the first time
Thanks for anything!
Click to expand...
Click to collapse
so i think that my phone is rooted and i am trying to flash the ROM but the Error i am getting is...
set_metadata_recusive: some changes failed
E: Error executing updater binary in zip '.extern
Error flashing zip '/external_sd/Gummy-M. 1-02-27
woerner said:
so i think that my phone is rooted and i am trying to flash the ROM but the Error i am getting is...
set_metadata_recusive: some changes failed
E: Error executing updater binary in zip '.extern
Error flashing zip '/external_sd/Gummy-M. 1-02-27
Click to expand...
Click to collapse
Well i think i "Soft Bricked" my phone. currently stuck in a reboot loop but can still boot into recovery and download but nothing seams to be able to get me out of this loop
woerner said:
Well i think i "Soft Bricked" my phone. currently stuck in a reboot loop but can still boot into recovery and download but nothing seams to be able to get me out of this loop
Click to expand...
Click to collapse
Since you can get to download mode the best thing may be to restore stock 4.3. Check out this thread
AT&T I747 UCUEMJB Stock Restore
dawgdoc said:
Since you can get to download mode the best thing may be to restore stock 4.3. Check out this thread
AT&T I747 UCUEMJB Stock Restore
Click to expand...
Click to collapse
Thanks for all this help any being patient with me ill try and restore back to stock and read up somemore
dawgdoc said:
Since you can get to download mode the best thing may be to restore stock 4.3. Check out this thread
AT&T I747 UCUEMJB Stock Restore
Click to expand...
Click to collapse
Tried to use this and when i swipe to confirm flash, it will freeze for 3 sec. and then show the blue teamwin page and then go right back to the twrp home page
will try more in after work tomorrow...
This is exactly whats happening to me! gah!
Exact same errors, my question is, i can get a custom recovery, i can root, but i cant for the life of me, flash any roms.
woerner said:
Tried to use this and when i swipe to confirm flash, it will freeze for 3 sec. and then show the blue teamwin page and then go right back to the twrp home page
will try more in after work tomorrow...
Click to expand...
Click to collapse
Jewyou said:
This is exactly whats happening to me! gah!
Exact same errors, my question is, i can get a custom recovery, i can root, but i cant for the life of me, flash any roms.
Click to expand...
Click to collapse
Have you removed Knox before attempting to flash the custom ROM?
Other than that I don't have a suggestion, mostly because I have never used TWRP.
dawgdoc said:
Have you removed Knox before attempting to flash the custom ROM?
Other than that I don't have a suggestion, mostly because I have never used TWRP.
Click to expand...
Click to collapse
I personally have tried both http://forum.xda-developers.com/showthread.php?t=1963790 And http://forum.xda-developers.com/showthread.php?t=2538991
Both have gotten me to Root, but still unavailable to install roms
yes i have removed Knox several times with still failing.
Jewyou said:
This is exactly whats happening to me! gah!
Exact same errors, my question is, i can get a custom recovery, i can root, but i cant for the life of me, flash any roms.
Click to expand...
Click to collapse
I was able to get it to work by using philztouch instead of TWRP try using that hope this helps!
Here is the ota file I just pulled from my s3. It's a cfg file though, and the recommended way to install is via adb sideload.
Stock users please test it. People who are rooted, use xposed, TiBu to freeze bloat, tell me how to update without a factory reset. I have already tried unrooting and using stock recovery, I am now unfreezing all bloat and uninstall xposed to see if it works.
https://mega.co.nz/#!W0JHQKAK!pA52fCAkUxTMia9A21KL1TrR8bmJT10jhNlBvn5j-Mk
Devs, is there a way to modify the update script so it doesn't check for modified system status? I'm worried I can't update because of tripped knox and if so I'm screwed
bkong said:
Here is the ota file I just pulled from my s3. It's a cfg file though, and the recommended way to install is via adb sideload.
Stock users please test it. People who are rooted, use xposed, TiBu to freeze bloat, tell me how to update without a factory reset. I have already tried unrooting and using stock recovery, I am now unfreezing all bloat and uninstall xposed to see if it works.
https://mega.co.nz/#!PJ40jDCY!I2A0Di...381MaXx3_0dl8I
Click to expand...
Click to collapse
Can you please PM @DocHoliday77 to help him build the Stock ROM for us? He does not have the AT&T Device, but can surely help us in building the ROM. Greatness of him!!
He may ask for some other files for building AT&T ROM for us. If he can build the ROM for us, then we dont have to take the pains of testing the CFG file!!
Thanks man!!
Thank you for sharing this. We'll be hard at work on this now
Sent from my SGH-I747 using XDA Premium 4 mobile app
bkong said:
Here is the ota file I just pulled from my s3. It's a cfg file though, and the recommended way to install is via adb sideload.
Stock users please test it. People who are rooted, use xposed, TiBu to freeze bloat, tell me how to update without a factory reset. I have already tried unrooting and using stock recovery, I am now unfreezing all bloat and uninstall xposed to see if it works.
https://mega.co.nz/#!PJ40jDCY!I2A0Di...381MaXx3_0dl8I
Devs, is there a way to modify the update script so it doesn't check for modified system status? I'm worried I can't update because of tripped knox and if so I'm screwed
Click to expand...
Click to collapse
Anybody have this hosted on a different mirror? The link asks me for a decryption key.
stoobie-doo said:
Anybody have this hosted on a different mirror? The link asks me for a decryption key.
Click to expand...
Click to collapse
Wait until later tonight or tomorrow when enewman17 or docholiday release a flashable
Sent from my SGH-I747 using XDA Premium 4 mobile app
@bkong
Link is bad, clicking it links to a url with "..." in the middle
CNexus said:
@bkong
Link is bad, clicking it links to a url with "..." in the middle
Click to expand...
Click to collapse
reuploaded it with new link, does it work now?
I'm also waiting for a flashable zip because I can't get adb working and ota fails every damn time.
bkong said:
reuploaded it with new link, does it work now?
I'm also waiting for a flashable zip because I can't get adb working and ota fails every damn time.
Click to expand...
Click to collapse
you can't just flash an update.zip through stock recovery?
Appears to be working! I've got someone who is going to try to get me everything I need to build a rom from the AT&T release, so if all goes well I should have it up this afternoon! :fingers-crossed:
Success!
used the odin flashable 4.3 file from http://forum.xda-developers.com/showthread.php?t=2722660 , went back to stock 4.3 and then used the OTA provided by the OP to get to 4.4.2
edit: please wait for the devs to work their magic to get fully working and easily flashable roms
Jakeuten said:
you can't just flash an update.zip through stock recovery?
Click to expand...
Click to collapse
I believe that wipes all your data so I wanted to avoid that, and it might not work according to some peoples experience,
DocHoliday77 said:
Appears to be working! I've got someone who is going to try to get me everything I need to build a rom from the AT&T release, so if all goes well I should have it up this afternoon! :fingers-crossed:
Click to expand...
Click to collapse
Awesome, will this be an odin flashable tar that will keep your data? I have been struggling for the past few hours trying to update without losing all my data. I flashed this rom [http://forum.xda-developers.com/showthread.php?t=2498233] that is stock and includes knox but Adb doesn't work for me and the at&t software update says its up to date, which its not, so I think the rom might have a problem, and I'm trying to figure out how to reinstall twrp so I can restore my backup but knox is blocking me. Hopefully I can just odin your rom and towelroot and be done with it.
DocHoliday77 said:
Appears to be working! I've got someone who is going to try to get me everything I need to build a rom from the AT&T release, so if all goes well I should have it up this afternoon! :fingers-crossed:
Click to expand...
Click to collapse
could you make an update.zip for users with stock recovery as well?
bkong said:
I believe that wipes all your data so I wanted to avoid that, and it might not work according to some peoples experience,
Click to expand...
Click to collapse
OTA shouldn't wipe any of your data. The way it works is it patches the existing files on your device with any changes to bring it up to date. Shouldn't touch any user data at all.
Awesome, will this be an odin flashable tar that will keep your data? I have been struggling for the past few hours trying to update without losing all my data. I flashed this rom [http://forum.xda-developers.com/showthread.php?t=2498233] that is stock and includes knox but Adb doesn't work for me and the at&t software update says its up to date, which its not, so I think the rom might have a problem, and I'm trying to figure out how to reinstall twrp so I can restore my backup but knox is blocking me. Hopefully I can just odin your rom and towelroot and be done with it.
Click to expand...
Click to collapse
It'll be recovery flashable. Im not sure yet if Ill be trying to create an Odin flashable one. Will need to have someone pull the system.img slightly differently if I do. (Would need to Odin flash 4.3, flash TWRP, boot straight to recovery and flash the OTA, then while still in recovery dump the partition.) Even then, no guarantee it would work quite right. These things can be a little finicky.
How is Knox blocking TWRP though? You should be able to flash that via Odin. Since you updated using the OTA though, every time you reboot, it will rewrite the stock recovery. So when you flash TWRP via Odin, uncheck the Auto Reboot box, then after the flash is successful, pull the battery. Then put it back in and boot straight to recovery and flash your rom.
Jakeuten said:
could you make an update.zip for users with stock recovery as well?
Click to expand...
Click to collapse
I will try. No guarantees though. Its been a long time since I've messed with OTA's, so I'm not completely sure I will remember exactly what to do with it. I should be able to do it though. Just not making promises!
bkong said:
I believe that wipes all your data so I wanted to avoid that, and it might not work according to some peoples experience,
Awesome, will this be an odin flashable tar that will keep your data? I have been struggling for the past few hours trying to update without losing all my data. I flashed this rom [http://forum.xda-developers.com/showthread.php?t=2498233] that is stock and includes knox but Adb doesn't work for me and the at&t software update says its up to date, which its not, so I think the rom might have a problem, and I'm trying to figure out how to reinstall twrp so I can restore my backup but knox is blocking me. Hopefully I can just odin your rom and towelroot and be done with it.
Click to expand...
Click to collapse
Not sure whether you can use Mobile Odin Pro to do that. Extracting the file from the OTA.zip and renaming it from 2400258.cfg to 2400258.zip makes it recognized in MOP, and the options are there to avoid the wipe, but I know earlier OTAs like that did wipe.
Note - I have only gone so far as loading it into MOP; waiting to see if someone more foolhardy than me is willing to actually do it.
stoobie-doo said:
Not sure whether you can use Mobile Odin Pro to do that. Extracting the file from the OTA.zip and renaming it from 2400258.cfg to 2400258.zip makes it recognized in MOP, and the options are there to avoid the wipe, but I know earlier OTAs like that did wipe.
Note - I have only gone so far as loading it into MOP; waiting to see if someone more foolhardy than me is willing to actually do it.
Click to expand...
Click to collapse
Tempted to try it (flash through stock recovery) but not my phone lol
Unless MO is written to specifically handle it, it will probably fail. (Im not sure if it is or isn't)
Sorry if I was misinformed about it wiping data. On TMobile neither OTA's or flashing in Odin ever wipes data. Afaik, Odin will only wipe data if there is a data.img included in the .tar file. Our OTA's have never touched anything but dalvik on the data partition either from what I remember.
DocHoliday77 said:
Unless MO is written to specifically handle it, it will probably fail. (Im not sure if it is or isn't)
Sorry if I was misinformed about it wiping data. On TMobile neither OTA's or flashing in Odin ever wipes data. Afaik, Odin will only wipe data if there is a data.img included in the .tar file. Our OTA's have never touched anything but dalvik on the data partition either from what I remember.
Click to expand...
Click to collapse
Let me be more precise; the technique I was talking about is found at http://forum.xda-developers.com/showthread.php?t=1767827 and applies the OTA in a way that wipes. Not sure whether MO would do the same or not; I haven't played with it since the upgrade to 4.3 last year and my memory is hazy.
Just tried and ADB sideload of this file to my S3. After renaming the .cfg file to .zip.
I get an "assert failed" on "getprop("ro.product.device") == "d2att""
Any suggestions? I'm wondering if the phone is reporting something other than d2att?
So no one tested this via stock recovery? Need to know if the update can be done through stock recovery.
stoobie-doo said:
Let me be more precise; the technique I was talking about is found at http://forum.xda-developers.com/showthread.php?t=1767827 and applies the OTA in a way that wipes. Not sure whether MO would do the same or not; I haven't played with it since the upgrade to 4.3 last year and my memory is hazy.
Click to expand...
Click to collapse
Just tried this method.
I got the assert failure again, and it happily wiped my internal SD but didn't install the OTA.
Good thing I'm not using this device for anything critical, I'd be rather pissed off.
So I've stayed at 2.19.40.20 because I wanted to wait to see if a better way to unlock the bootloader would be found, but I've given up and unlocked my bootloader (the unoffical way).
I want to get up to speed and update to the latest OTA.
Can I just flash the latest one or do I need to download every one til the newest update and sideload them individually?
If I have to do each one can I just load them one after the other, or do I need to reboot the phone and let it fully load to the OS for every update?
I did side load the latest one when I was coming from the 18 something that came with my phone. Loading the full 1.1gig firmware did the trick.
So just for clarification, to take me from 2.19.40.20 to 2.20.40.139 I should just flash the latest Stock ROM from the ASUS site?
DiGecko said:
I did side load the latest one when I was coming from the 18 something that came with my phone. Loading the full 1.1gig firmware did the trick.
Click to expand...
Click to collapse
Azdinflash said:
So just for clarification, to take me from 2.19.40.20 to 2.20.40.139 I should just flash the latest Stock ROM from the ASUS site?
Click to expand...
Click to collapse
Yes that should do it.
I was seriously dreading having to update, but this shows that my worries were unfounded, thanks!
I don't need to unroot as I'm flashing the whole rom, right?
The_wolf88 said:
Yes that should do it.
Click to expand...
Click to collapse
Azdinflash said:
I was seriously dreading having to update, but this shows that my worries were unfounded, thanks!
I don't need to unroot as I'm flashing the whole rom, right?
Click to expand...
Click to collapse
You need to unroot and make sure you are sideloading the whole 1.1 gig one.
DiGecko said:
You need to unroot and make sure you are sideloading the whole 1.1 gig one.
Click to expand...
Click to collapse
Does unrooting include removing Xposed?
Yes, and don't try to install it after you get to 139 firmware, as far as I know it still causes bootloop.
Wait, if I flash the 1.1 gig stock ROM, do I lose everything in the internal memory?
DiGecko said:
Yes, and don't try to install it after you get to 139 firmware, as far as I know it still causes bootloop.
Click to expand...
Click to collapse
I did a little digging, and it seems that the bootloop was fixed a few days ago:
http://forum.xda-developers.com/zenfone2/general/guide-to-install-xposed-installer-t3116476/page26
J M L said:
There's a new Xposed out, v78, which claims to fix a bootloop on 5.0 roms due to a security fix. I haven't tried it yet because I'm running a backup. Here is the thread and changelog.
We want the sdk21-x86 version.
Installed with no problem in TWRP with the flash able zip. Took a few minutes to boot, but seems to be working.
Click to expand...
Click to collapse
Good to know. No, you would not loose anything, at least I did not. Everything migrated over without any issues.
So I've gotten through sideloading the current version with no hiccups. Booted into system fine, it's the right version in the About section, and my internal memory came through intact.
I've flashed TWRP, and booted into it to install SuperSU when I got this message: "TWRP may have detected an unmodified system partition"
It explains that I can keep it as read only and make it easier to take official updates, but then TWRP will not be able to stop the stock ROM from replacing it and will not offer to root my device.
Should I keep it "Read Only" or should I allow the modification?