So I've been lurking these forums for quite a while over the years. Anyway I used the root method here http://forum.xda-developers.com/showthread.php?t=2039421which worked flawlessly, I must add.
Today I received notification that a new version of android was ready to be installed and now upon reboot I'm stuck in a loop. CWM recovery boots but cannot install the update.zip. i get the following error messages:
installing /sdcard/update.zip
finding update package
E: cant mount /sdcard/update.zip
Installation aborted.
Manually trying to browse for the zip file does nothing. Ive tried clearing davik/fixing permissions. Is there any way of updating besides flashing the stock recovery?
sbslammer said:
So I've been lurking these forums for quite a while over the years. Anyway would try wipingy I used the root method here http://forum.xda-developers.com/showthread.php?t=2039421which worked flawlessly, I must add.
Today I received notification that a new version of android was ready to be installed and now upon reboot I'm stuck in a loop. CWM recovery boots but cannot install the update.zip. i get the following error messages:
installing /sdcard/update.zip
finding update package
E: cant mount /sdcard/update.zip
Installation aborted.
Manually trying to browse for the zip file does nothing. Ive tried clearing davik/fixing permissions. Is there any way of updating besides flashing the stock recovery?
Click to expand...
Click to collapse
You are currently unlocked and thus cannot update via ota. Also, the current update is still ics. You probably need to come to irc for help.
KUmike said:
You are currently unlocked and thus cannot update via ota. Also, the current update is still ics. You probably need to come to irc for help.
Click to expand...
Click to collapse
Thanks to all the guys on irc and especially shelnutt2! you guys are awesome
I have the same problem, please help!
I have the same problem with my optimus g. Can someone please help! What is irc?
The IRC is a web chat room where the devs work on the device and help people with soft bricked phones and many other issues.
Can find it at WWW. http://webchat.freenode.net and the room is lg-optimus-g if I remember correctly I at work and don't have my comp with me.
Sent From My LG Optimus
Thank you. I am looking now.
Jelly bean update?
Sent from my LG-LS970 using xda premium
This is caused by your bootloader being unlocked. Restore your boot.img and associated files that you backed up during the FreeGee process and you will be good to go.
Sent from my Optimus G using xda app-developers app
vpetkar said:
This is caused by your bootloader being unlocked. Restore your boot.img and associated files that you backed up during the FreeGee process and you will be good to go.
Sent from my Optimus G using xda app-developers app
Click to expand...
Click to collapse
I think trying to install an ota without the stock recovery screws up the misc partition. I would recommend:
1. Don't upgrade with ota's (duh)
2.If you do, get help in irc before you do something the helpful folks there don't know how to fix.
Phone: Samsung SGH-I317
Android Version: 4.1.2
I got my new note 2 last week and made it about 2 days before i had to root it and install CWM as i had on my Galaxy SII (which was on US Cellular). I rooted it without difficulty, installed rom manager and installed the newest version of CWM for the Note 2 v6.0.2.5. Here is where my first and only problem has come up.
I tried doing a small 8.45mb OTA AT&T update on the phone ( i did the 4.1.2 OTA update before i rooted it). It downloaded no problem then brought the prompt up that the phone must restart to install. It goes to CWM recovery no problem to install then i get this.
Install Untrusted Package?
THIS CAN NOT BE UNDONE
-NO
-NO
-NO
-YES – Install untrusted zip
-NO
-NO
+++Go Back+++
“
Clockworkmod Recovery v6.0.2.5
E: invalid command argument
Finding update package…
Opening update package…
Verifying update package…
E: failed to verify whole-file signature
E: signature verification failed
“
So i know at this point something went wrong as it is bringing up failed outputs. So i go ahead and click - Yes install untrusted zip. Just to see what happens. Then i get the following:
Installing update…
verifying current system
assert failed: apply_patch_check(“/system/app/ALLShareCastWidget.odex”, “05c4c0b26bb484a43fd6268d76d220d4b633f193”, “b750b9d56b7c31ceaac48bd0daaf3779e5f55da0”)
E: Error in /cache/fota/2400258.cfg
(status 7)
Installation aborted
I have searched XDA, google, ect trying to find an answer but am at a loss to why i cant install the OTA updates. Any input would be greatly appreciated. Thanks XDA for the help.
Generally if you have a custom recovery installed you can not install OTA`s
Same happened to with the S3. Any fix?
No fix...
Unless the device uses the stock 3e recovery. ..
The device can be returned to stock...then the OTA taken. ..then root and flash the custom recovery again. ..
Then back up the newer build for later use. ..g
Sent from my SAMSUNG-SGH-I317 using XDA Premium HD app
tryed a few times
gregsarg said:
No fix...
Unless the device uses the stock 3e recovery. ..
The device can be returned to stock...then the OTA taken. ..then root and flash the custom recovery again. ..
Then back up the newer build for later use. ..g
Sent from my SAMSUNG-SGH-I317 using XDA Premium HD app
Click to expand...
Click to collapse
every time i go back to my first back up it ask me to updated my rom and every time it trys it screws every thing up. anything stock well carrier stock sucks any way. just flash a custom rom most allready have the lateest up date any way. i just stay clear of ota becaues they are so far behind its ridiculous. the guys on xda get the latest update on release day and hand deliver them to us. (good job guys)
jaston28009 said:
every time i go back to my first back up it ask me to updated my rom and every time it trys it screws every thing up. anything stock well carrier stock sucks any way. just flash a custom rom most allready have the lateest up date any way. i just stay clear of ota becaues they are so far behind its ridiculous. the guys on xda get the latest update on release day and hand deliver them to us. (good job guys)
Click to expand...
Click to collapse
Simple fix...
Use TIBU and freeze the updater....g
Sent from my SAMSUNG-SGH-I317 using XDA Premium HD app
Just to provide all the information I have on hand, I have the
T-Mobile SGH-M919
android version 4.3
baseband version M919UVUEMK2
Current Recovery: ClockworkMod 6.0.4.7
My issue is that regardless of what rom I attempt to download i get the error below. Specifically, I've tried to download virginROM 2.3, which seems to be compatible with my device. From what I understand status 7 is in place to keep you from flashing an incompatible rom and so I'm not too sure how to proceed from here. Any and all help would be appreciated.
flash flash flashin things
format() expects 5 args, got 4
E: Error in /data/media/0/virginROM_v2.4.1.zip
(status 7)
Installation aborted.
/tmp/recovery.log was copied to /sdcard/clockworkmod/recovery.log.
Please open ROM manager to report the issue.
Try using TWRP
My S4 Is Insane
Deviant Team Member
could be the signature veridicatrion, try disabling in recovery
aisarang said:
Just to provide all the information I have on hand, I have the
T-Mobile SGH-M919
android version 4.3
baseband version M919UVUEMK2
Current Recovery: ClockworkMod 6.0.4.7
My issue is that regardless of what rom I attempt to download i get the error below. Specifically, I've tried to download virginROM 2.3, which seems to be compatible with my device. From what I understand status 7 is in place to keep you from flashing an incompatible rom and so I'm not too sure how to proceed from here. Any and all help would be appreciated.
flash flash flashin things
format() expects 5 args, got 4
E: Error in /data/media/0/virginROM_v2.4.1.zip
(status 7)
Installation aborted.
/tmp/recovery.log was copied to /sdcard/clockworkmod/recovery.log.
Please open ROM manager to report the issue.
Click to expand...
Click to collapse
I just ran into this a few minutes ago using Philz Touch. The solution I found was under the install zip menu, you should see "Don't Allow Old update-binary. It should have a check-mark; simply untick that option and try again.
lordcheeto03 said:
I just ran into this a few minutes ago using Philz Touch. The solution I found was under the install zip menu, you should see "Don't Allow Old update-binary. It should have a check-mark; simply untick that option and try again.
Click to expand...
Click to collapse
I'm using CWM and I don't see the option to check "donm't allow old update-binary." When I turn toggle signature verification off I get
E:footer is wrong
E: signature verification failed
Installation aborted.
and then get prompted to ask if i want to install an untrusted package. I attempted to download and apply the new 4.4.2 Google Edition by Davnh, haven't tried TWCP yet but i feel like it should still be doable via CWM.
I had no problems rooting my s3 and putting custom recovery but when I attempt to flash either cyanogenmod or resurrection remix I get the status error 7. Then if I delete the Assert portion I either get status 6 error or it goes into a boot loop and I have to reinstall stock again with odin. I have also downloaded notepad++ as recommended to no avail.
You need to be on at least MD5 bootloader/firmware.
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
You need to be on at least MD5 bootloader/firmware.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
I just looked on the firmware I flashed on my phone whenever it wouldn't boot and it is md5.
So are you saying you tried to flash MD5 and it would not boot? What were you running before flashing? Did you factory reset?
DocHoliday77 said:
So are you saying you tried to flash MD5 and it would not boot? What were you running before flashing? Did you factory reset?
Click to expand...
Click to collapse
I have tried multiple roms and sometimes got error 7 sometimes error 6 and sometimes unable to boot, at which point I would then flash the stock firmware with odin on it and then it would work again, but I want to be able to put a firmware with kitkat on it.
Youd probably be best off updating to 4.3 firmware if you haven't already. If you're out of warranty there is little reason not to update imo.
Then use twrp 2.7.0.0 for your recovery. Some have had recent problems flashing with cwm.
If you still have issues, let us know exactly what steps you followed and exactly what you were trying to flash.
Sent from my SGH-T999 using Tapatalk
It came with 4.3, that's not the issue, I have tried both twrp and cwm to flash a cyanogenmod kitkat rom and I get the status error 7 at first, if I do what is said to get rid of that and delete the lines at the start then it gets a status error 6. At which point it no longer boots then I need to flash it back to the stock firmware.
Did you try the latest version of either Recoveries ? If its not the latest version you'd get error.
With the 4.3 firmware, you do not have to remove any Assert Lines from the updater Script. Just in case go back to the last stable release of CM 11.
27a
Just updated to a newer cwm to no avail, still getting status 7 error.
What CWM Version is that ?
6.0.4.5
Please post the Recovery Log. Its present in /cache/recovery
62453634 08
I don't see a cache folder
deadly8123 said:
I don't see a cache folder
Click to expand...
Click to collapse
You need a Root Explorer with Root access. Remount System as R/W in your Root Explorer.
Finally was able to do it I flashed a d2lte rom instead of a d2tmo rom.
I'm sure I'm not the only one that has had this problem. I've never been able to do the update to 4.2 from 4.1.1. After the download and reboot, the phone gives me an error message. AT&T was no help. I rooted my phone last year but I can't remember how I rooted it. Anyway, I want to update to a new stable ROM. My questions are, do I need to update from 4.1 to 4.2, then 4.3 and then 4.4? Or can I go from 4.1 to 4.4? And if someone could direct me to an easy problem-free stable ROM, I would be most grateful!
Jennifer
southernblonde said:
I'm sure I'm not the only one that has had this problem. I've never been able to do the update to 4.2 from 4.1.1. After the download and reboot, the phone gives me an error message. AT&T was no help. I rooted my phone last year but I can't remember how I rooted it. Anyway, I want to update to a new stable ROM. My questions are, do I need to update from 4.1 to 4.2, then 4.3 and then 4.4? Or can I go from 4.1 to 4.4? And if someone could direct me to an easy problem-free stable ROM, I would be most grateful!
Jennifer
Click to expand...
Click to collapse
If your phone is rooted, you could have difficulties getting an OTA update. You could either unroot your phone from the SuperSU app or you could manually do a 2-step update to 4.1.2 and then 4.3. Unrooting should allow your phone take an OTA update if you are currently on a stock ROM. For manual update process, please follow the instructions below ....
1) Go to the first page in the thread below ...
http://forum.xda-developers.com/show....php?t=2387423
2) Download the 2 zip files under update412.zip and update43.zip respectively to your computer
3) Copy the zip files to a good quality (micro) SD card
4) Place the card in your phone and boot to recovery mode by simultaneously holding down the Volume Up, Home and Power buttons
5) Hold the buttons until you see a blue message flash across the screen. Then release the Power button but continue to hold the Volume Up and Home button until you see the Android image appear. Then release the buttons
6) Use the volume up/down key to scroll to <mount from external storage> and the power button to select
7) Navigate to the first zip file (update412.zip) and install. Wait for installation to finish and your phone to reboot.
8) Complete set up. Check your phone settings. Then power off and reboot to recovery again.
9) Repeat the process for the second update file.
The latest (official) Android version available for the i747 is 4.3 Jelly Bean. Android 4.4 (Kit-Kat) has not been rolled out yet for this phone so if you want the latest stock (official) system, that would be 4.3. If you are looking at a custom ROM, there are quite a few Kit-Kat based ROMs out there.
Larry2999 said:
If your phone is rooted, you could have difficulties getting an OTA update. You could either unroot your phone from the SuperSU app or you could manually do a 2-step update to 4.1.2 and then 4.3. Unrooting should allow your phone take an OTA update if you are currently on a stock ROM. For manual update process, please follow the instructions below ....
1) Go to the first page in the thread below ...
http://forum.xda-developers.com/show....php?t=2387423
2) Download the 2 zip files under update412.zip and update43.zip respectively to your computer
3) Copy the zip files to a good quality (micro) SD card
4) Place the card in your phone and boot to recovery mode by simultaneously holding down the Volume Up, Home and Power buttons
5) Hold the buttons until you see a blue message flash across the screen. Then release the Power button but continue to hold the Volume Up and Home button until you see the Android image appear. Then release the buttons
6) Use the volume up/down key to scroll to <mount from external storage> and the power button to select
7) Navigate to the first zip file (update412.zip) and install. Wait for installation to finish and your phone to reboot.
8) Complete set up. Check your phone settings. Then power off and reboot to recovery again.
9) Repeat the process for the second update file.
The latest (official) Android version available for the i747 is 4.3 Jelly Bean. Android 4.4 (Kit-Kat) has not been rolled out yet for this phone so if you want the latest stock (official) system, that would be 4.3. If you are looking at a custom ROM, there are quite a few Kit-Kat based ROMs out there.
Click to expand...
Click to collapse
Thanks for replying so quickly. When installing 412.zip, I get the following error message after Verifying Current System:
E:Error in tmp/sideload/package.zip (Status 7)
southernblonde said:
Thanks for replying so quickly. When installing 412.zip, I get the following error message after Verifying Current System:
E:Error in tmp/sideload/package.zip (Status 7)
Click to expand...
Click to collapse
Usually, you get a status 7 error message when your recovery mode is out of date. Are you using stock recovery or custom recovery? If custom, would you know what version it is?
Larry2999 said:
Usually, you get a status 7 error message when your recovery mode is out of date. Are you using stock recovery or custom recovery? If custom, would you know what version it is?
Click to expand...
Click to collapse
It looked to be stock recovery. It said Android System Recovery
southernblonde said:
It looked to be stock recovery. It said Android System Recovery
Click to expand...
Click to collapse
You shouldn't have any difficulties flashing the zip if you are on stock recovery. Did you verify the MD5 of the zip you downloaded to be sure it downloaded correctly?
Larry2999 said:
You shouldn't have any difficulties flashing the zip if you are on stock recovery. Did you verify the MD5 of the zip you downloaded to be sure it downloaded correctly?
Click to expand...
Click to collapse
What does MD5 stand for?
Earlier today I tried unrooting and downloading OTA but same problem as before....it cuts out early during installation, reboots and I'm left with 4.1.1
southernblonde said:
What does MD5 stand for?
Earlier today I tried unrooting and downloading OTA but same problem as before....it cuts out early during installation, reboots and I'm left with 4.1.1
Click to expand...
Click to collapse
The MD5 (or checksum verifier) is an algorithm used to verify the authenticity and integrity of digital files. It is statistically improbable for 2 separately created files to have the same MD5 so verifying the MD5 ascertains that the file downloaded correctly and/or has not altered in any way from the original prior to your download. The download source for the files shows the MD5 of the original files so you can use the MD5 checker tool to verify the ones you downloaded. If the MD5 matches, then the file is OK. Otherwise, it didn't download correctly or may have been altered in some way.
http://winmd5.com/
However, the fact that you are unable to get the OTA update after unrooting suggests there may be a different problem with your device. Possible some security encryptions are preventing updates to the system. I'll suggest you back up your files and try doing a factory reset to return the phone to original settings then try the upgrade process again. Prior to upgrading your firmware, however, I would suggest you take the opportunity to free unlock your phone (if not already done). This can only be done on 4.1.1
Larry2999 said:
The MD5 (or checksum verifier) is an algorithm used to verify the authenticity and integrity of digital files. It is statistically improbable for 2 separately created files to have the same MD5 so verifying the MD5 ascertains that the file downloaded correctly and/or has not altered in any way from the original prior to your download. The download source for the files shows the MD5 of the original files so you can use the MD5 checker tool to verify the ones you downloaded. If the MD5 matches, then the file is OK. Otherwise, it didn't download correctly or may have been altered in some way.
http://winmd5.com/
However, the fact that you are unable to get the OTA update after unrooting suggests there may be a different problem with your device. Possible some security encryptions are preventing updates to the system. I'll suggest you back up your files and try doing a factory reset to return the phone to original settings then try the upgrade process again. Prior to upgrading your firmware, however, I would suggest you take the opportunity to free unlock your phone (if not already done). This can only be done on 4.1.1
Click to expand...
Click to collapse
Thanks for all your help, I really appreciate it. I've been working on this phone all day. I'm still having issues with the phone after doing a factory reset and a hard reset. I unlocked it also. The MD5s matched. It downloads the update, then when it goes to install, it gets to 25% then bypasses the rest. The phone still says its 4.1.1. After I did the factory reset only, when I went to update, it was saying there were no updates available...thats what led me to do the hard reset. I'm ready to throw this thing in the ocean. I thought the hard reset would put it back to just out of the box fresh but I still see old apps in there like SuperSU and Mobile Odin Pro. Perhaps those apps are messing it up? This really has me stumped. When I USB it to my laptop and boot up Kies, it says there are no updates available.
I just wiped the cache partition and did a hard reset again. This time I downloaded the update412.zip from the sdcard and I got the same original error: E:Error in tmp/sideload/package.zip (Status 7)
southernblonde said:
Thanks for all your help, I really appreciate it. I've been working on this phone all day. I'm still having issues with the phone after doing a factory reset and a hard reset. I unlocked it also. The MD5s matched. It downloads the update, then when it goes to install, it gets to 25% then bypasses the rest. The phone still says its 4.1.1. After I did the factory reset only, when I went to update, it was saying there were no updates available...thats what led me to do the hard reset. I'm ready to throw this thing in the ocean. I thought the hard reset would put it back to just out of the box fresh but I still see old apps in there like SuperSU and Mobile Odin Pro. Perhaps those apps are messing it up? This really has me stumped. When I USB it to my laptop and boot up Kies, it says there are no updates available.
I just wiped the cache partition and did a hard reset again. This time I downloaded the update412.zip from the sdcard and I got the same original error: E:Error in tmp/sideload/package.zip (Status 7)
Click to expand...
Click to collapse
Please don't give up on your phone yet. It isn't that bad yet. The dreaded error message you are getting means that your recovery system is compromised. Also, once rooted, your phone stays that until specifically unrooted. Even a factory reset will not remove SuperSU and Mobile Odin and the definitive solution to un-rooting is to flash a complete stock image. However, you may be able to fix the recovery issue and get updates in a number of ways. First, you could reflash a complete stock 4.1.1 image via Odin. This will update all system partitions including recovery and should deliver a new and working recovery partition. It will also remove root and make it possible to get an OTA update to 4.3JB. You can download the Odin flashable file from Sammobile.com or from the following link ... http://www.4shared.com/get/zAmWJ54J/I747UCDLK3_I747ATTDLK3_ATT.html
Unzip and extract the *.tar file and flash via Odin.
The second solution would be to use Mobile Odin or Desktop Odin v3.09 to flash a new recovery partition. You'll need the same *.tar file for UCDLK3 but you'd only need to load the recovery partition. If this is successful, you can try the manual update process again.
The final solution would be to flash custom recovery via Odin and then flash the 4.3JB stock restore image via (custom) recovery. You could do the same 2-step manual update via custom recovery. However, a complete stock restore image is available for 4.3 which can be flashed via custom recovery. Please see the first page of the thread below ...
http://forum.xda-developers.com/showthread.php?t=2658486
You can find the TWRP custom recovery Odin flashable file for your device via the link below ...
http://techerrata.com/file/twrp2/d2att/openrecovery-twrp-2.6.3.1-d2att.tar
Hope this finally solves it.
Larry2999 said:
Please don't give up on your phone yet. It isn't that bad yet. The dreaded error message you are getting means that your recovery system is compromised. Also, once rooted, your phone stays that until specifically unrooted. Even a factory reset will not remove SuperSU and Mobile Odin and the definitive solution to un-rooting is to flash a complete stock image. However, you may be able to fix the recovery issue and get updates in a number of ways. First, you could reflash a complete stock 4.1.1 image via Odin. This will update all system partitions including recovery and should deliver a new and working recovery partition. It will also remove root and make it possible to get an OTA update to 4.3JB. You can download the Odin flashable file from Sammobile.com or from the following link ... http://www.4shared.com/get/zAmWJ54J/I747UCDLK3_I747ATTDLK3_ATT.html
Unzip and extract the *.tar file and flash via Odin.
The second solution would be to use Mobile Odin or Desktop Odin v3.09 to flash a new recovery partition. You'll need the same *.tar file for UCDLK3 but you'd only need to load the recovery partition. If this is successful, you can try the manual update process again.
The final solution would be to flash custom recovery via Odin and then flash the 4.3JB stock restore image via (custom) recovery. You could do the same 2-step manual update via custom recovery. However, a complete stock restore image is available for 4.3 which can be flashed via custom recovery. Please see the first page of the thread below ...
http://forum.xda-developers.com/showthread.php?t=2658486
You can find the TWRP custom recovery Odin flashable file for your device via the link below ...
http://techerrata.com/file/twrp2/d2att/openrecovery-twrp-2.6.3.1-d2att.tar
Hope this finally solves it.
Click to expand...
Click to collapse
I finally did get it fixed last night, actually by one of your solutions there. I had googled the error message (status 7) and I found a thread here on XDA where someone said that because I had used Titanium to delete bloatware when I got the phone, I wouldn't be able to update until it looked right out of the box so I downloaded Odin and flashed 4.1.1. again. Thank God I didn't brick the phone with everything I did to it yesterday. LOL It was finally able to flash 4.1.2 then 4.3. Its disturbing all the threads I see going back to 4.1.1 from 4.3. Is there a huge issue? I'm going to try to find a stable KitKat to flash to. Thanks again for your help!
southernblonde said:
I finally did get it fixed last night, actually by one of your solutions there. I had googled the error message (status 7) and I found a thread here on XDA where someone said that because I had used Titanium to delete bloatware when I got the phone, I wouldn't be able to update until it looked right out of the box so I downloaded Odin and flashed 4.1.1. again. Thank God I didn't brick the phone with everything I did to it yesterday. LOL It was finally able to flash 4.1.2 then 4.3. Its disturbing all the threads I see going back to 4.1.1 from 4.3. Is there a huge issue? I'm going to try to find a stable KitKat to flash to. Thanks again for your help!
Click to expand...
Click to collapse
Glad to know it's now working. I think there's more fuss than fact to the 4.3 question. As far as performance and functionality goes, Touchwiz 4.3 is a major improvement on the older Jelly Bean versions. The main problem, of course, is that the bootloader can not be safely downgraded once you are on 4.3. This is only a problem if you need to free unlock your phone which is only possible on 4.1.1. Otherwise, you can safely flash a KitKat based custom ROM. I would only advise you stick with a stable like you've said and be sure it's one that won't try to mess with your bootloader. Most custom ROMs don't but it wouldn't hurt to make sure.
Larry2999 said:
Glad to know it's now working. I think there's more fuss than fact to the 4.3 question. As far as performance and functionality goes, Touchwiz 4.3 is a major improvement on the older Jelly Bean versions. The main problem, of course, is that the bootloader can not be safely downgraded once you are on 4.3. This is only a problem if you need to free unlock your phone which is only possible on 4.1.1. Otherwise, you can safely flash a KitKat based custom ROM. I would only advise you stick with a stable like you've said and be sure it's one that won't try to mess with your bootloader. Most custom ROMs don't but it wouldn't hurt to make sure.
Click to expand...
Click to collapse
Do you have a recommendation for a stable Kit Kat rom?
I am trying to upgrade to 4.3 on an unlocked, rooted SGH-I747 that I am using internationally (in New Zealand now); however, when I tried to flash a clean 4.1.1 so I could update to 4.3, doing a factory reset and cache wipe, I successfully load the firmware with Odin but then it won't boot past the blue pulsing samsung logo I think I need to flash a new recovery partition, as you suggest below, but I don't know how to do that.
Can anyone help?
Larry2999 said:
Please don't give up on your phone yet. It isn't that bad yet. The dreaded error message you are getting means that your recovery system is compromised. Also, once rooted, your phone stays that until specifically unrooted. Even a factory reset will not remove SuperSU and Mobile Odin and the definitive solution to un-rooting is to flash a complete stock image. However, you may be able to fix the recovery issue and get updates in a number of ways. First, you could reflash a complete stock 4.1.1 image via Odin. This will update all system partitions including recovery and should deliver a new and working recovery partition. It will also remove root and make it possible to get an OTA update to 4.3JB. You can download the Odin flashable file from Sammobile.com or from the following link ... http://www.4shared.com/get/zAmWJ54J/I747UCDLK3_I747ATTDLK3_ATT.html
Unzip and extract the *.tar file and flash via Odin.
The second solution would be to use Mobile Odin or Desktop Odin v3.09 to flash a new recovery partition. You'll need the same *.tar file for UCDLK3 but you'd only need to load the recovery partition. If this is successful, you can try the manual update process again.
The final solution would be to flash custom recovery via Odin and then flash the 4.3JB stock restore image via (custom) recovery. You could do the same 2-step manual update via custom recovery. However, a complete stock restore image is available for 4.3 which can be flashed via custom recovery. Please see the first page of the thread below ...
http://forum.xda-developers.com/showthread.php?t=2658486
You can find the TWRP custom recovery Odin flashable file for your device via the link below ...
http://techerrata.com/file/twrp2/d2att/openrecovery-twrp-2.6.3.1-d2att.tar
Hope this finally solves it.
Click to expand...
Click to collapse
southernblonde said:
Do you have a recommendation for a stable Kit Kat rom?
Click to expand...
Click to collapse
I'm not too much into customs. You could, however, take a loot at the new AOSP ROMS or CM 10x...
---------- Post added at 10:34 AM ---------- Previous post was at 10:30 AM ----------
Pfhyde said:
I am trying to upgrade to 4.3 on an unlocked, rooted SGH-I747 that I am using internationally (in New Zealand now); however, when I tried to flash a clean 4.1.1 so I could update to 4.3, doing a factory reset and cache wipe, I successfully load the firmware with Odin but then it won't boot past the blue pulsing samsung logo I think I need to flash a new recovery partition, as you suggest below, but I don't know how to do that.
Can anyone help?
Click to expand...
Click to collapse
You could have installed directly from recovery without first trying to flash a fresh 4.1.1. This would have only been necessary if your 4.1.1 wasn't working right in some way. Try booting into recovery and then doing a wipe/reset. If your phone boots successfully after this, then try the 2-step update -first to 4.1.2 and then to 4.3 via the instructions posted earlier in this thread. Please let me know if this works.
Larry2999 said:
I'm not too much into customs. You could, however, take a loot at the new AOSP ROMS or CM 10x...
---------- Post added at 10:34 AM ---------- Previous post was at 10:30 AM ----------
You could have installed directly from recovery without first trying to flash a fresh 4.1.1. This would have only been necessary if your 4.1.1 wasn't working right in some way. Try booting into recovery and then doing a wipe/reset. If your phone boots successfully after this, then try the 2-step update -first to 4.1.2 and then to 4.3 via the instructions posted earlier in this thread. Please let me know if this works.
Click to expand...
Click to collapse
Thanks for the suggestion. I've tried wiping again from recovery but I get errors (see this thread I started for the details).
-pf
Pfhyde said:
Thanks for the suggestion. I've tried wiping again from recovery but I get errors (see this thread I started for the details).
-pf
Click to expand...
Click to collapse
Since you are apparently successful with Odin, can you try flashing an original stock image rather than the modified (pre-rooted) version you are using. You may download the original version from sammobile.com or do an internet search for it. The zip should be close to 1Gb in size but please make sure to verify the MD5 prior to flashing.
Larry2999 said:
I'm not too much into customs. You could, however, take a loot at the new AOSP ROMS or CM 10x...
---------- Post added at 10:34 AM ---------- Previous post was at 10:30 AM ----------
You could have installed directly from recovery without first trying to flash a fresh 4.1.1. This would have only been necessary if your 4.1.1 wasn't working right in some way. Try booting into recovery and then doing a wipe/reset. If your phone boots successfully after this, then try the 2-step update -first to 4.1.2 and then to 4.3 via the instructions posted earlier in this thread. Please let me know if this works.
Click to expand...
Click to collapse
Larry2999 said:
Since you are apparently successful with Odin, can you try flashing an original stock image rather than the modified (pre-rooted) version you are using. You may download the original version from sammobile.com or do an internet search for it. The zip should be close to 1Gb in size but please make sure to verify the MD5 prior to flashing.
Click to expand...
Click to collapse
I did try an original stock, originally. I only tried the rooted stock after the original didn't work (got stuck with pulsing blue samsung logo). I'll try the one from sammobile.com (but I think that's where I got it the first time) and report back after I get off work late tonight.
-p