Related
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
so, i flashed the kitkat bootloader from odin, then flashed the zip from philz touch recovery. the kernel splash screen stayed on for a long time, then the screen went out, and it loaded to the kernel splash, then to recovery. then i realized i hadnt wiped, so i flashed the kitkat stock rom through odin, installed philz touch recovery, did a full wipe, then installed the zip, and the same thing happened. being a new member with less than 10 posts i cant post on the official thread, so... whats the deal? what could the problem be?
EDIT: my bad everyone. i found a misleading link to philz, the newest version in that thread was not the newest version.
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/n5110/philz_touch_6.41.6-n5110.tar.md5 use this. if you have the same problem
tooandrew said:
so, i flashed the kitkat bootloader from odin, then flashed the zip from philz touch recovery. the kernel splash screen stayed on for a long time, then the screen went out, and it loaded to the kernel splash, then to recovery. then i realized i hadnt wiped, so i flashed the kitkat stock rom through odin, installed philz touch recovery, did a full wipe, then installed the zip, and the same thing happened. being a new member with less than 10 posts i cant post on the official thread, so... whats the deal? what could the problem be?
Click to expand...
Click to collapse
in aroma choose the stock kernel option. I had the same bootloop problem ....it kept going into recovery.
After choosing the stock kernel everything was smooth.
off course pls confirm that you are using the correct ROM version
for 5100 version is 1.2
1.3 is only for 5110
I didn't see any kernel options let me make a nandroid and run it again. and yeah I have the 5110. Thanks
hey, i reinstalled it, there were no kernel options, but i left the bootanimation option on stock samsung, and i had been using the XAR region, so i tried btu this time, because thats what the stock rom i have installed is. still crashes to recovery
EDIT: and after restoring my nandroid, i get to the rom splash screen, and it just loops there.
I have the same problem...Where is the Stock KK that u can flash thru Odin ???
ronny71 said:
I have the same problem...Where is the Stock KK that u can flash thru Odin ???
Click to expand...
Click to collapse
Here is the link to Stock KK:
http://www.sammobile.com/firmwares/3/?download=29611
Also download Odin v3.09 from the same link.
Then follow these instructions:
1) Unzip the Download zip file, you will get N5110XXDNE1_N5110OXADNE1_HOME.tar.md5
2) Put the tablet in Download mode
3) Install N5110XXDNE1_N5110OXADNE1_HOME.tar.md5 using "PA" option of ODIN.
4) It will take a while, let it finish.
5) If that works, reboot back to download mode
6) Install latest Philz recovery, using ODIN's PA option.
7) Reboot into recovery, and install any custom ROMS.
Note: This will trip your KNOX counter
pvsgh said:
Here is the link to Stock KK:
http://www.sammobile.com/firmwares/3/?download=29611
Also download Odin v3.09 from the same link.
Then follow these instructions:
1) Unzip the Download zip file, you will get N5110XXDNE1_N5110OXADNE1_HOME.tar.md5
2) Put the tablet in Download mode
3) Install N5110XXDNE1_N5110OXADNE1_HOME.tar.md5 using "PA" option of ODIN.
4) It will take a while, let it finish.
5) If that works, reboot back to download mode
6) Install latest Philz recovery, using ODIN's PA option.
7) Reboot into recovery, and install any custom ROMS.
Note: This will trip your KNOX counter
Click to expand...
Click to collapse
thats the thing.... i flashed it, i have stock rooted kitkat running fine, i have philz recovery running fine, but when i try to flash the custom kitkat rom, i wipe, flash the zip, the aroma installer boots i choose a few options, the aroma installer completes, then i reboot and it just crashes to recovery, no matter how many times i try, how many factory resets i do, anything. knox is tripped, but i can't run the rom. i had the 4.2.2 custom touchwiz from the same developer running fine, but then i decided i had to have kitkat, and.... nothing. it simply won't run.
if it matters, i am already running the same stock rom you linked to, 4.4.2 btu
EDIT: just for the record, i am not new to this in general, only this particular device - my sprint galaxy s3 is running carbon rom, my galaxy gear is running null rom, i flashed N3BULA on my dad's verizon galaxy note two, and ive already decided on a rom for the note 3 i am getting at the end of july.
this is just my first time encountering this problem, all assistance with this matter is greatly appreciated.
tooandrew said:
thats the thing.... i flashed it, i have stock rooted kitkat running fine, i have philz recovery running fine, but when i try to flash the custom kitkat rom, i wipe, flash the zip, the aroma installer boots i choose a few options, the aroma installer completes, then i reboot and it just crashes to recovery, no matter how many times i try, how many factory resets i do, anything. knox is tripped, but i can't run the rom. i had the 4.2.2 custom touchwiz from the same developer running fine, but then i decided i had to have kitkat, and.... nothing. it simply won't run.
if it matters, i am already running the same stock rom you linked to, 4.4.2 btu
EDIT: just for the record, i am not new to this in general, only this particular device - my sprint galaxy s3 is running carbon rom, my galaxy gear is running null rom, i flashed N3BULA on my dad's verizon galaxy note two, and ive already decided on a rom for the note 3 i am getting at the end of july.
this is just my first time encountering this problem, all assistance with this matter is greatly appreciated.
Click to expand...
Click to collapse
Ok, so first try to validate the MD5 of the file that you are installing.
if you are installing "CivZ-FlexNote8.0_KK-Rev1.3-N5110_signed.zip" then the MD5 should match as below:
b8abeb1ec9535ef526d02ef402788359
Validate the MD5 in PC as well as Tablet. Sometime you get a good download on PC, but when you copy it to Phone/tablet file might not get copied properly.
Second option you can try to install another 4.4.2 based ROM:
http://forum.xda-developers.com/showthread.php?t=2763274
Again validate the MD5 before installing.
pvsgh said:
Ok, so first try to validate the MD5 of the file that you are installing.
if you are installing "CivZ-FlexNote8.0_KK-Rev1.3-N5110_signed.zip" then the MD5 should match as below:
b8abeb1ec9535ef526d02ef402788359
Validate the MD5 in PC as well as Tablet. Sometime you get a good download on PC, but when you copy it to Phone/tablet file might not get copied properly.
Second option you can try to install another 4.4.2 based ROM:
http://forum.xda-developers.com/showthread.php?t=2763274
Again validate the MD5 before installing.
Click to expand...
Click to collapse
Md5 matches. I'm going to download am earlier update and dirty flash, see if that helps
Hey, those who were having problems, you probably got the wrong recovery. i had two versions of philz on my computer, and i flashed philz 5 instead of philz 6.
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/n5110/philz_touch_6.41.6-n5110.tar.md5
the other guy who was boot looping, that is the link to the recovery you should use. everything will be fine with that one
tooandrew said:
Hey, those who were having problems, you probably got the wrong recovery. i had two versions of philz on my computer, and i flashed philz 5 instead of philz 6.
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/n5110/philz_touch_6.41.6-n5110.tar.md5
the other guy who was boot looping, that is the link to the recovery you should use. everything will be fine with that one
Click to expand...
Click to collapse
Thanx my man...u hit it right on the head...Wrong Recovery...I hope everyone who has this problem reads ur post...Thanx again Buddy...:good::good:
[Q] Need help in solving "Unfortunately, settings have stopped working" error
Problem: My unrooted SGH-I747 model AT&T GS3 recently gave me this error whenever trying to access the settings. The error shows up even after a full factory reset and I can no longer access my phone. Stuck a little after the language selection in the beginning stages of the setup.
Attempted fixes: Obviously, the initial factory reset. Then clearing the cache + factory reset.
After those failed to work, I tried to flash to a AT&T stock rom from this forum (http://forum.xda-developers.com/showthread.php?p=33570269#post33570269) using Odin. I tried to use the first row of downloads but the first row but it did not have a MD5 file, so I used the second row of downloads instead but this rom failed to install. My guess is that it may be too old of a version.
I would appreciate any help.
[SOLVED]
The problem may have arose from a critical error in the phone's software that had affected the OS system of the phone. I resolved the issue by flashing a new custom OS (cyanogenmod) to my phone. These are the steps that I took:
1. Installing Odin (http://forum.xda-developers.com/showthread.php?t=1722686)
2. Rooting my cellphone with CFAutoRoot using Odin (http://forum.xda-developers.com/showthread.php?t=1725839)
3. Installing a custom recovery TWRP -- highly recommended very user friendly (http://forum.xda-developers.com/showthread.php?t=1793224)
4. Installing a new custom rom through TWRP-- used Cyanogen (http://forum.xda-developers.com/showthread.php?t=1778270)
5. Installing gapps (http://opengapps.org/?api=5.1&variant=nano)
6. Identifying the correct bootloader by downloading and installing Samsung Phone Info by vndnguyen through the Play Store.
7. Installing the correct bootloader and modem (http://forum.xda-developers.com/galaxy-s3-att/general/rooted-ucufnj1-stock-rom-t2985006)
Please refer to respective installation guides for more instructions regarding installation of any new software.
I hope this helps anyone who may have run into the same problem.
Before attempting to flash anything, confirm the bootloader on your phone. An easy way to determine if the bootloader is 4.3 or newer, boot into download mode. If you see anything about warranty bit, your phone has at least a 4.3 bootloader and no attempts should be made to flash anything from sammobile.com.
If you have a 4.3 or newer bootloader, I recommend flashing a custom recovery such as TWRP, and then flashing a stock ROM from recovery.
First off, thank you for the reply audit!
Now I have officially rooted my phone using CF-Autoroot and have installed TWRP. I have also confirmed that the bootloader is at least 4.3 because it does show the warranty bit.
Which of the stock roms are compatible with this bootloader?
Do you want to stay on a stock ROM? If not, you could flash a custom ROM such as cm12.1 using TWRP. Once you have flashed a custom ROM, you can look under settings to determine the baseband on the phone which is another clue as to which bootloader is on your phone.
audit13 said:
Do you want to stay on a stock ROM? If not, you could flash a custom ROM such as cm12.1 using TWRP. Once you have flashed a custom ROM, you can look under settings to determine the baseband on the phone which is another clue as to which bootloader is on your phone.
Click to expand...
Click to collapse
Just to be clear, cm12.1 is the cyanogenMod nightly?
Yup. If you flash it, your baseband may be unknown which tells me you are probably not running a 4.4.2 bootloader and modem.
audit13 said:
Yup. If you flash it, your baseband may be unknown which tells me you are probably not running a 4.4.2 bootloader and modem.
Click to expand...
Click to collapse
I'll try it out and see if I can get past the language screen this time.
Got the latest Cyanogenmod Zip file onto my phone. Tried flashing it through TWRP with the install option but it failed.
Log reads that no MDS file was found, detected filesystem ext4 for /dev/block/platform msm_sdcc.1/byname system. Can't install this package on top of incompatible data.
CM12.1 won't have an md5 file. You're trying to install cm12.1 for the d2att or d2lte? You're running the latest TWRP which I believe is 2.8.7.0? or 2.8.7.1?
5K posts.
"all i can really do , is stay out of my own way and let the will of heaven be done"
I'm pretty sure that CM de-unified the variants for CM 12.
From: https://wiki.cyanogenmod.org/w/D2lte_Info
Note: Unified device
Between the release of CM 11 M3 and CM11 M12, all Qualcomm-based variants of this device were merged into a single build: d2lte. The device information pages for the individual variants should be used to reference any device-specific unlock instructions, download recoveries, to build CM 10.2, or to install CM 12.1: d2att, d2cri, d2mtr, d2spr, d2tmo, d2usc, d2vzw.
Click to expand...
Click to collapse
I think this was just to make searching a bit harder/ more complicated.
audit13 said:
CM12.1 won't have an md5 file. You're trying to install cm12.1 for the d2att or d2lte? You're running the latest TWRP which I believe is 2.8.7.0? or 2.8.7.1?
Click to expand...
Click to collapse
For d2att and running 2.8.7.0 for TWRP.
You should be good then.
The file should be left unzipped/unrared when using it right? I'm using it as such but it keeps returning the same error message saying that it won't install it.
Yes, leave it zipped. What is the TWRP error message?
The error log:
detected filesystem ext4 for /dev/block/platform msm_sdcc.1/byname system.
Can't install this package on top of incompatible data.
Please try another package or run a factory reset
E: Error executing updater binary in zip '/sdcard/Download/cm-12.12015913-NIGHTLY-dtatt.zip
Error flashing zip '/sdcard/Download/cm-12.120150913-NIGHTLY-D2att.zip
Weird, did you do a full wipe before trying to install?
Can't believe it was that simple. I thought I had already made the wipe when I did it with the original recovery but making a second wipe through TWRP actually helped make it happen. I finally got through and have full access to my phone.
Unfortunately, the cell service doesn't seem to work but I'm guessing that I need to do more for the set up?
Edit: Not recognizing the sim card for some reason
Sounds like you need to update the bootloader and modem to the older KK version which I think is ne4.
Sorry for the late reply I've been busy the past week. I'm guessing the modem won't work without the proper bootloader? I've tried flashing the latest and original modem from the Modem list (http://forum.xda-developers.com/showthread.php?t=1831898). While they installed successfully I still don't get a signal.
I was worried which bootloader to take because it may lead to bricking. Which one are you referring to and are they in the Bootloader updates topic here? (http://forum.xda-developers.com/showthread.php?t=2321310)
Ok guys Ive tried every post I can find on getting TWRP on my phone. I have the latest Odin3 v3.10.6.exe, the latest TWRP, twrp-2.8.7.0-trltespr.img.tar and tried, openrecovery-twrp-2.8.5.0-trltespr.img.tar, I have followed the posts and pulled the usb, then the battery for 30 seconds. I have unchecked the auto reboot, left it checked, tried it in the AP and BL slots and I cant get a custom recovery to stick. Here is the stats on my phone, Im at my wits end with this any help or suggestions would be much grateful. Ive already bricked it with cf autoroot and reinstalled the stock rom. Im wondering if I shouldn't of let it auto activate? Does sprint have a kill mode now for TWRP?
Software Version, N910PVPU4COG5
HARDWARE VERSION N90P.O5
ANDROID VERSION 5.1.1
BASEBAND VERSION SAME AS SOFTWARE VERSION
KERNEL VERSION
3.10.40-530320
DPI!SWHE8820 #1
BUILD NUBMER
LMY47X.N910PVPU4COG5
SECURITY SOFTWARE VERSION
MDF V2.0 RELEASE 1
VPN V1.4 RELEASE 5.2
KNOX VERSION
KNOX 2.4.1
Johniex said:
...Im wondering if I shouldn't of let it auto activate?...
Click to expand...
Click to collapse
Yes, you should. Although I can't recall it specifically said, that's what I do. I use the OB7 bootloader still and the OB7 to OG5 tar flash, reboots without warning on initial boot. Using OG5 modem on OB7, the phone would ask for permission to reboot. Once that reboot is out of the way, proceed.
@tx_dbs_tx implied (not to put words in his mouth but IMO he implies as you theorize here) the same recently when he added to get a GPS lock prior to proceeding.
The other steps you mentioned should get it done. Latest Odin, default settings, wipe everything but extSdCard (backup keep sakes) and power down prior to Odin download are recommended as well. Also, remember to uncheck auto reboot for TWRP flash in Odin, pull USB and battery. Most importantly, boot into recovery to help it stick.
Sent from my SM-N910P using Tapatalk
TWRP Fails While Trying To Write
Hello to all. I am trying to install TWRP on My Sprint note 4 . I am on software version N910PVPS4DPE2 and the Baseband is the same. Android VErsion 6.0.1
I was trying to install TWRP 3.0.2-0. Odin sees the phone and tries to install, but I notice that upon the writing process it fails. I even tried to install TWRP 2.8.5.0. I think I read something that this version must be installed first before any newer versions. Now mind you I am not rooted as of yet. I want to get a backup of the original setup before I flash a new ROM.
Any and all suggestions are welcomed to help me.
Blessings and Thank You In Advance.
ulremember said:
.. I notice that upon the writing process it fails. I even tried to install TWRP 2.8.5.0. I think I read something that this version must be installed first before any newer versions. Now mind you I am not rooted as of yet. I want to get a backup of the original setup before I flash a new ROM.
Any and all suggestions are welcomed to help me.
Blessings and Thank You In Advance.
Click to expand...
Click to collapse
Don't think you have to install an older version of TWRP first but there are 2 common overlooked steps when installing TWRP:
1) Goto Settings/Security when booted and make sure Reactivation lock is unchecked. (If it's set, you can't write in Odin and your phone displays something like blocked by R/L.)
2) You've dug up an old thread, this post may conflict with the older posts above but for clarity, it's best to open Odin options tab, uncheck only the auto reboot box and flash the img.tar, loading in AP slot. After flash is verified as successful, 0 failed (wait for it), pull USB cable and battery, wait at least 30 seconds. It's important that your first boot is directly to recovery to make TWRP stick as your default recovery. Else, you revert back to stock recovery if booting into system.
Note: There is a TWRP thread in original development forum which answers this question and others. Before rooting, you may consider OTA update to the update that matches your ROM if interest. The OTA updates are incremental so it may make more sense to Odin the stock reflecting the update of interest.
When Odin flashing stock tars, use the latest Odin, verify the md5 of downloaded zip then extract the tar.md5 to Odin folder to find easily when flashing. But on your phone, backup what you like before considering wiping; don't expect the flash to wipe for you but you may lose internal memory storage. Expect that but don't wipe your extSdCard; you can move what you want to keep there along with anything you intend to flash later. After backup and wipe, power phone down and pull battery prior to flashing stock tar. That seems to help ensure your csc gets setup properly. There is a stock tar thread in general forum with the stock tar updates, tools and instructions.
Make sure you install the right recovery or your touch screen will be out of calibration. Any trouble, refer to the TWRP thread but I think I've addressed the current issues.
Thank you soooo much!!!! That worked.
God bless you!!!!
Have a great weekend!!!
Hallo everybody, greetings from germany.
I would need some support from you guys on a bootloop case for the sm-t700. I searched my ass off in google and xda but could not find a solution.
So now after hours of trying it myself I like to ask for help.
In the following I will describe what I have done to come to this point including everything I installed etc.
The stock rom was lollipop 5.0.2 and already installed.
- usb debug mode on
- flashed via odin v.3.10.7 supersu "cf-autoroot-twrp-t700.tar"
- forgot to install busybox and rootchecker for verifying root.
- backup of IMEI/EMFS (data is now on pc)
- in recovery backup of Boot.img
- wipe data/cache/dalwik/system in one go
- flashed "Euphoria-OS-1.1-klimtwifi-UNOFFICIAL-20150812.zip"
"open_gapps-arm-5.1-pico-20151013.zip"
"SkyHigh_SM-T700_kernel_TW-LL_v2.0.zip"
- rebooted and waited up to 15 - 20 min. Stopped waiting after that.
the regular samsung logo while booting shows up in intervalls from 5 to 10 minutes.
Next I wanted to do it better by installing busybox and cheking for root, because
I thought first that this could be the main cause for the bootloop.
- downloadmode
- flashed succesfully "T700XXU1BOE5_T700DBT1BOD1_HOME.tar.md5" via odin v.3.10.7 to get to stockrom again
- usb debug mode on
- downloadmode
- flashed via odin v.3.10.7 supersu "cf-autoroot-twrp-t700.tar"
- verifyied it with rootvalidator
- installed busybox
- deleted all knox stuff
- installed twrp app to get to v.2.8.7.0
- recoverymode
- backup of everything
- wipe data/cache/dalwik/system
- flashed "Euphoria-OS-1.1-klimtwifi-UNOFFICIAL-20150812.zip"
"open_gapps-arm-5.1-pico-20151013.zip"
"SkyHigh_SM-T700_kernel_TW-LL_v2.0.zip"
- rebooted and waited up to 15 - 20 min. Stopped waiting after that.
the regular samsung logo while booting shows up in intervalls again from 5 to 10 minutes.
Next I went into recovery and restored everything as before the flash of the customrom.
This happens in the same way with blisspop and liquidsmooth roms.
Hope anyone knows something.
Youve flashed an aosp rom , but attempting to boot with a stock based kernel.
Its never advisable to multi flash. Flash after each successful boot.
You need to flash the kernel provided in that thread or flash the whole rom again.
Also make sure your bootloader is up to date.
Tbh I'd wipe and start again.
ashyx said:
Youve flashed an aosp rom , but attempting to boot with a stock based kernel.
Its never advisable to multi flash. Flash after each successful boot.
Click to expand...
Click to collapse
By "multi flash" do you mean the install procedure in twrp that automates the installation procedure? (add zip)
And how am I able to flash after each successful boot if there is nothing to boot left after wipe?
ashyx said:
You need to flash the kernel provided in that thread or flash the whole rom again.
Click to expand...
Click to collapse
I thought this Kernel would be great. So you do not recommend me to use it?
I will look up the roms now and the kernel they use.
ashyx said:
Also make sure your bootloader is up to date.
Tbh I'd wipe and start again.
Click to expand...
Click to collapse
How do I do this or if already up to date where do I can look it up?
According to your post you flashed rom, gapps and kernel in one go.
Any one of those could have caused a bootloop or hang.
As for SkyHigh kernel, it is a great kernel but probably not suitable for an aosp rom as it's built from stock sources intended for stock roms.
Use the kernel provided.
To update the bootloader flash the latest firmware or pull it out and flash it separately.
Okay I will do the following now.
First find the appropiate Kernel if Skyhigh is a nogo. sadly.
Then flash in recovery at first the kernel of the rom. boot. recovery, flash the customrom + gapps. Right?
And before all that flash a new bootloader.
Further, is there a Kernel beside the one of the roms that you would recommend me?
Just wipe data and cache in recovery then flash just the rom. It probably already has the kernel.
Don't flash gapps just reboot after flashing the rom.
ashyx said:
Just wipe data and cache in recovery then flash just the rom. It probably already has the kernel.
Don't flash gapps just reboot after flashing the rom.
Click to expand...
Click to collapse
Okay worked well.
Left out the kernel because I could not find any custom ones.
Now I have euphoria on it and want to change between blisspop and liquidsmooth until I have the one I like most.
It is kinda hard to get the difference. I just know that euphoria and liquid are faster, smoother?
Thanks a lot without your input I would still be searching for an answer.
Happy day to you.
skyhigh and iron kernel are mean for touchwiz. Its not mean for cyanogen/aosp/aokp.
currently there is no one cook a custom kernel for cyanogen/aosp/aokp rom. so we stuck with the kernel that come with the rom.
Kernels :
https://www.androidfilehost.com/?w=files&flid=37193
Okay, did not know about this kernel.could you give me some info about the "deathly signed"?
My browser here is not loading the xda thread where I found people talking about it.