[Q] Problems with AT&T update from 4.1.1 - AT&T, Rogers, Bell, Telus Samsung Galaxy S III

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

Related

CivZ-FLEXNOTE-8.0_Rev1.3 crash to recovery

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:

Can't revert back to stock recovery, and other questions

Hello,
I am having some trouble reverting back from TWRP to Stock Recovery to do an OTA update to the 5/30 update. Whenever I flash the recovery in TWRP, it fails. Another problem I had was, when I was in stock recovery (before jumping to TWRP), I tried doing the OTA update, but when the phone rebooted to perform the update, it would stop half way and reboot back into the OS and no change would happen (even though it said "Updating ColorOS". Any help is appreciated. Thanks!
azeem40 said:
Hello,
I am having some trouble reverting back from TWRP to Stock Recovery to do an OTA update to the 5/30 update. Whenever I flash the recovery in TWRP, it fails. Another problem I had was, when I was in stock recovery (before jumping to TWRP), I tried doing the OTA update, but when the phone rebooted to perform the update, it would stop half way and reboot back into the OS and no change would happen (even though it said "Updating ColorOS". Any help is appreciated. Thanks!
Click to expand...
Click to collapse
If you don't want to flash recovery via fastboot, use flash tool from play. Then try updating again.
speaking of stock recovery, does anyone know where i can get the recovery.img at? i've been searching...
xBeerdroiDx said:
speaking of stock recovery, does anyone know where i can get the recovery.img at? i've been searching...
Click to expand...
Click to collapse
Here: https://www.dropbox.com/s/nsmi7q86pzymbka/recovery.zip
azeem40 said:
Hello,
I am having some trouble reverting back from TWRP to Stock Recovery to do an OTA update to the 5/30 update. Whenever I flash the recovery in TWRP, it fails. Another problem I had was, when I was in stock recovery (before jumping to TWRP), I tried doing the OTA update, but when the phone rebooted to perform the update, it would stop half way and reboot back into the OS and no change would happen (even though it said "Updating ColorOS". Any help is appreciated. Thanks!
Click to expand...
Click to collapse
You can use my recovery flasher to go back to stock recovery. Here
tantrums said:
You can use my recovery flasher to go back to stock recovery. Here
Click to expand...
Click to collapse
Thanks a lot man! I will surely give it a try tomorrow.
Man, I used your recovery flasher to install the recovery, but it still doesn't let me install the OTA. It boots into recovery and nothing happens. When I reboot the phone, it says updating, but when I check for OTAs, it still says to install the update.
azeem40 said:
Man, I used your recovery flasher to install the recovery, but it still doesn't let me install the OTA. It boots into recovery and nothing happens. When I reboot the phone, it says updating, but when I check for OTAs, it still says to install the update.
Click to expand...
Click to collapse
That's odd. You could try this recovery:
http://forum.xda-developers.com/showpost.php?p=53065486&postcount=84
It's official TWRP except it's modified to report the device as "FIND 7" (just like stock recovery) so it can flash stock ROMs/updates. I doubt the stock recovery uses open recovery script so I doubt you'll be able to initiate the flash via the settings menu. However you could try to install the OTA manually. I think the zip is placed in /sdcard/ota or something like that. I sent my Find 7a in so I can't verify the correct path.
Doc Ames said:
That's odd. You could try this recovery:
http://forum.xda-developers.com/showpost.php?p=53065486&postcount=84
It's official TWRP except it's modified to report the device as "FIND 7" (just like stock recovery) so it can flash stock ROMs/updates. I doubt the stock recovery uses open recovery script so I doubt you'll be able to initiate the flash via the settings menu. However you could try to install the OTA manually. I think the zip is placed in /sdcard/ota or something like that. I sent my Find 7a in so I can't verify the correct path.
Click to expand...
Click to collapse
Even when I use the zip, it gets like 1/4th of the way done and then says "installation failed"... Kind of frustrating.
azeem40 said:
Even when I use the zip, it gets like 1/4th of the way done and then says "installation failed"... Kind of frustrating.
Click to expand...
Click to collapse
Maybe check if the OTA is available for download here or on Oppo Forums with an MD5 so you can verify integrity. If not you could delete the .zip and redownload via software update. If all else fails you could switch to ColorOS 2.0 beta or try Gummy or Omni. I personally hated colorOS however I feel that 2.0 beta is actually more stable with less bugs.
Doc Ames said:
Maybe check if the OTA is available for download here or on Oppo Forums with an MD5 so you can verify integrity. If not you could delete the .zip and redownload via software update. If all else fails you could switch to ColorOS 2.0 beta or try Gummy or Omni. I personally hated colorOS however I feel that 2.0 beta is actually more stable with less bugs.
Click to expand...
Click to collapse
I already tried it, but even that failed.. Color os didn't install either.
So no one has an idea on why I can't install the Ota? Even tried unrooting and trying the Ota that way, but it still failed. Even if I use recovery of color os to flash the Ota without root, it still fails. I don't know what else to do... I want to get Ota in case they update to 4.4 kitkat...
I fixed it.
azeem40 said:
I fixed it.
Click to expand...
Click to collapse
How did you fix it?

Stuck in Odin Mode [from attempt to install a recovery rom]

I'd appreciate any help I can get guys.
So today, for the first time ever I rooted my android.
Found a simple video on how to and it worked. I then wanted to try a custom rom [Cyanogenmod 12?] On a video it was said to have a custom recovery rom first. Well, I tried Flashing TWRP. It asked to reboot. I pressed "yes Please". After that it restarted and was stuck at:
"Could not do normal boot" Odin mode (High speed)
I did a reset and now its just at:
"Odin mode(high speed)"
I saw someone on a random forum describing the same problem. He said he fixed it installing a recovery rom. Im guess from odin
since I cant do things on my phone. But I don't even know how to go about it. I just now I need a Tar. file
Please give me direction .__.
Try TWRP tar from Odin with phone in download mode; TWRP recovery tar linked below.
http://www.techerrata.com/file/twrp2/trltespr/openrecovery-twrp-2.8.5.0-trltespr.img.tar
If that doesn't work, you may have to Odin the stock tar.
I'm wondering if you misread the CF Auto root prompt to update the su binary? Update the su binary but don't choose the TWRP option even if you have TWRP. If you get recovery working, delete the cache and dakvik cache and reboot.
Didn't work out...at least the way I did it. I'm still new to this. Id appreciate more broken down instructions if youre willing to help
Sixgotfangs said:
Didn't work out...at least the way I did it. I'm still new to this. Id appreciate more broken down instructions if youre willing to help
Click to expand...
Click to collapse
What version of Odin do you have? Should be 3.07 with C.F. auto root. What have you flashed in Odin? Not familiar with the Odin message you gave; did anything change with the new recovery tar flash in Odin?
Won't boot or flash recovery? If so, you need to factory reset and Odin stock tar.
https://www.androidfilehost.com/?fid=95853297432265112
The instructions for stock tar are below but it's important to remember when flashing stock tars to power down first prior to going to download. You may not have any choice but power down to reach download mode; pull battery if you can't power down.
http://forum.xda-developers.com/showthread.php?p=56853325
If you can't factory reset, Odin the stock tar and see if it boots.
Yes, I have the 3.07. Only thing ive done was Root. I tried the recovery rom from a mobile download. That's as far as I got. All the recovery files I get never end up showing in the pda file search. .tar or .md5 is what it calls for. If I CAN factory reset from where im at now how do I do so. If I can start ALL over with someone who is actually up to date and knows what theyre doing id feel more comfortable. right now nothings happened and my phone is still at "odin mode (hgh speed) --downloading.
Sixgotfangs said:
Yes, I have the 3.07. Only thing ive done was Root. I tried the recovery rom from a mobile download. That's as far as I got. All the recovery files I get never end up showing in the pda file search. .tar or .md5 is what it calls for. If I CAN factory reset from where im at now how do I do so. If I can start ALL over with someone who is actually up to date and knows what theyre doing id feel more comfortable. right now nothings happened and my phone is still at "odin mode (hgh speed) --downloading.
Click to expand...
Click to collapse
ok, check my post above for updates.
Also, don't use the phone to download tar files unless you're using Flashify from Google Play. Download the tars on PC, move to folder that Odin resides in to find easily. You'll need to open the archive and drag the files there if zipped. The stock tar should be zipped but not sure about the recovery tar.
Cant believe I didn't see the last section on that post. Sorry about that. Anyway, I am downloading those files. Looks like its gonna take some time though. I'll go through each step you said and let you know.
Forgot to mention that you should close Odin after each flash attempt. You may have already noticed by now.
To get to CM after stock tar:
1) Root with CF Auto root, update su binary/reboot (you should wait no longer than 5 minutes for Knox prompt from supersu.
2) Odin TWRP recovery tar using same method as stock tar; Odin will only write over stock recovery on this step.
3) factory reset and flash CM in recovery. But also follow suggested instructions in the ROM you choose.
So far so good. The lil blue loading bar is filling.
got back to rooting. but I didn't do anything else. haven't even went to super user
Sixgotfangs said:
got back to rooting. but I didn't do anything else. haven't even went to super user
Click to expand...
Click to collapse
Booted? That's good news!
Can't remember if you have to open it or not. You should get a superuser update and possibly a su binary update but not so important going to another ROM. The su binary update is the one that I was suggesting not to use the TWRP option; I think the option is normal? Eventually, you should get the pop-up to disable Knox notifications; reboot if takes longer than 5 minutes.
Ready for TWRP? Use Odin. Flashify is something you could look into for updating TWRP, as needed. It's good for backing up recoveries and kernels, too. But watch those kernels for installed lib modules; Flashify won't restore those properly. Rely on flash zips for those; same applies for stock kernels, zip should include the stock modules.
It's late; you're probably done for the night. I'm out too.
samep said:
Booted? That's good news!
Can't remember if you have to open it or not. You should get a superuser update and possibly a su binary update but not so important going to another ROM. The su binary update is the one that I was suggesting not to use the TWRP option; I think the option is normal? Eventually, you should get the pop-up to disable Knox notifications; reboot if takes longer than 5 minutes.
Ready for TWRP? Use Odin. Flashify is something you could look into for updating TWRP, as needed. It's good for backing up recoveries and kernels, too. But watch those kernels for installed lib modules; Flashify won't restore those properly. Rely on flash zips for those; same applies for stock kernels, zip should include the stock modules.
It's late; you're probably done for the night. I'm out too.
Click to expand...
Click to collapse
Yeah, things are back to normal. Thanks again. As for the next steps, pretty lost. Im going to check the play store for an superuser update but the SU binary update....that's where I start getting lost. sorry for not being up to date with the terminology. But I am gonna check back on those links and look for the TWRP. and then use it like I did for those last files...{that's what Im getting from your messages} correct me if im straying from the path lol. catch ya later
I'm confusing you a bit with the the su binary update and SuperSU update. To keep it simpler, that can wait until after you flash CM, if that's your goal. Those are prompts so don't be too concerned. Don't think you'll see Knox in CM.
So to keep it simple, you need TWRP to flash a custom ROM. I suggest the Odin tar in the link sent earlier.
After getting your custom ROM flashed in recovery, follow the prompts but if you see the su binary update prompt, don't choose the TWRP option. I think that caused your initial recovery issue but can't say for sure.
samep said:
I'm confusing you a bit with the the su binary update and SuperSU update. To keep it simpler, that can wait until after you flash CM, if that's your goal. Those are prompts so don't be too concerned. Don't think you'll see Knox in CM.
So to keep it simple, you need TWRP to flash a custom ROM. I suggest the Odin tar in the link sent earlier.
After getting your custom ROM flashed in recovery, follow the prompts but if you see the su binary update prompt, don't choose the TWRP option. I think that caused your initial recovery issue but can't say for sure.
Click to expand...
Click to collapse
Hey there, Ok so. After messing around I ended up getting that TWRP package to work. I thought It was a SINGLE file, that's where I got stuck. but the whole ?.rar showed up in the pda selection In odin and I ran it. Worked fine. didn't see anything about updates ...still.
I restarted and went to recoverymode. Teamwin popped up like ive seen from other videos. Guessing im on the right track. So right now I don't need to be worrying about SuperSu or Rashr? or should I be dealing with those two apps? ALSO is Rom installer anything to pay attention to?
At this point, you can look into a ROM installer or Flashify but I'd recommend just following the developer OP for whatever ROM you choose.
And yes, no need to worry with SuperSU or su binary update. Just follow the prompts when they appear after flashing ROM.
samep said:
At this point, you can look into a ROM installer or Flashify but I'd recommend just following the developer OP for whatever ROM you choose.
And yes, no need to worry with SuperSU or su binary update. Just follow the prompts when they appear after flashing ROM.
Click to expand...
Click to collapse
Thanks so much! The videos ive seen have been much simple-r for installing roms SO I may survive this whole experience after all...Yesterday was kind of a bad time to almost loose my phones functionality....being on the job hunt and all. need those phone calls Lol. So thanks again. Im hoping to try out cyanogenmod 12. I'll definitely shoot off a flare gun if I fail lol.
No problem. Glad to be of some help. Godspeed on your journey and best of wishes for your career and rooted ventures!
samep said:
No problem. Glad to be of some help. Godspeed on your journey and best of wishes for your career and rooted ventures!
Click to expand...
Click to collapse
SUCCESS! Thanks again Sensei Lol
samep said:
No problem. Glad to be of some help. Godspeed on your journey and best of wishes for your career and rooted ventures!
Click to expand...
Click to collapse
eh...celebrated too early I guess. Ever run into camera connection errors?
Sixgotfangs said:
eh...celebrated too early I guess. Ever run into camera connection errors?
Click to expand...
Click to collapse
Is the error while still on stock or CM?
Now that you can wipe data, you can factory reset and either Odin the stock tar or flash CM.
If you prefer to take least intrusive approach, try going into recovery and delete cache and dalvik cache and reboot. If still not working, the factory reset. If still having camera issues, then decide if you want to go with stock tar in Odin again or CM a clean install; wipe user data first.
Personally, I'd wipe everything except my titanium backups and go back to Odin stock tar and make sure stock works fully before going to CM. In a situation like you were in, I would have powered down, flashed the stock tar in Odin and let it auto boot. Flash the custom recovery so I could wipe everything and then power down again and flash the stock tar in Odin just to get a clean start with root and custom ROM.
Edit- what is camera connection error? Oh, I see; lost camera. New thread. Maybe someone on CM can help you.

Installing TWRP Fail!! Please check this out!

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!!!

Stuck at "Patching System Image Unconditionally" when flashing CM12.1 via TWRP

Stuck at "Patching System Image Unconditionally" when flashing CM12.1 via TWRP
Just got a Note 4, proceeding with the usual root and installation CyanogenMod ASAP
Everything was going smoothly until the actual flashing of CyanogenMod, whenever I try to flash it, it just gets stuck on "patching system image unconditionally" and doesn't progress beyond that point
Steps I've taken so far:
1) unboxed phone, was running Android 6.0 (I think, maybe 6.0.1)
2) Rooted with Chainfire's Auto Root
3) Flashed TWRP 3.0.2-0 via Odin 3.09 as per TWRP's instructions
4) Ensured that I could boot both to the stock ROM and TWRP
5) Copied cm12.1 and gapps to Note 4's internal storage (sd card hasn't come in yet, normally I put it onto sd card)
6) Did default factory wipe from TWRP
7) Attempted to flash cm12.1, ran into issue
I didn't make a backup of the stock ROM so now the phone has a recovery but no actual OS, as I had to pull the battery out to get it to do anything beyond being stuck at the patching system image step
I'm redownloading cm12.1 in case maybe there was a problem with the .zip itself, I know it's bad practice but I never check md5 sums
I've found other threads that suggested flashing the stock ROM for some reason, but they were for other phones and I'm not sure if it's related to the Note 4.
I've seen some mention of the bootloader being locked, but I don't know how to tell if the bootloader is locked or not. I see the same exact boot screen that I saw with my Note 3, S4, S3, etc. Could the issue be the bootloader?
I've also found this thread, but I can't get TWRP to mount in Windows, it keeps saying the driver failed to install. MTP transfers worked fine with the stock ROM was still there, but for some reason it doesn't work with the Mount option in TWRP. I'm downloading the Android SDK so I can try using adb
If anyone else has run into this, can you advise me on what to do from here?
EDIT: Nevermind, fixed it. Changed system partition's filesystem to F2FS via TWRP, and this allowed CM and gapps to flash with no issue. Now booted into CM But hopefully this will be helpful if anyone else has this issue
EDIT2: Buuuuut now the WiFi's not working. It just gets stuck at "turn on WiFi" but nothing actually turns on, and the on/off button for WiFi in settings is grayed out. IT NEVER ENDS
CyanogenMod Thread
Reddit Thread
EDIT3:
WiFi and Settings Issue seems to be resolved
I think the problem had something to do with the baseband version
As per Trex's post (http://forum.xda-developers.com/showpost.php?p=69520362&postcount=2), I had to revert back to the OK1 baseband
Now everything seems to work fine
As for TWRP not working and just going to a black screen, I redownloaded it from the TWRP website and it worked fine
So now both TWRP and CM are installed and working, WiFi works, and Settings don't crash.
Now I've encountered an issue where the camera doesn't focus, and I'm wondering if there's still some plastic film on the camera lens, but I've been picking at it and nothing is coming off and I'm afraid of damaging the plastic if I keep trying...
AbuFiraas said:
Just got a Note 4, proceeding with the usual root and installation CyanogenMod ASAP
Everything was going smoothly until the actual flashing of CyanogenMod, whenever I try to flash it, it just gets stuck on "patching system image unconditionally" and doesn't progress beyond that point
Steps I've taken so far:
1) unboxed phone, was running Android 6.0 (I think, maybe 6.0.1)
2) Rooted with Chainfire's Auto Root
3) Flashed TWRP 3.0.2-0 via Odin 3.09 as per TWRP's instructions
4) Ensured that I could boot both to the stock ROM and TWRP
5) Copied cm12.1 and gapps to Note 4's internal storage (sd card hasn't come in yet, normally I put it onto sd card)
6) Did default factory wipe from TWRP
7) Attempted to flash cm12.1, ran into issue
I didn't make a backup of the stock ROM so now the phone has a recovery but no actual OS, as I had to pull the battery out to get it to do anything beyond being stuck at the patching system image step
I'm redownloading cm12.1 in case maybe there was a problem with the .zip itself, I know it's bad practice but I never check md5 sums
I've found other threads that suggested flashing the stock ROM for some reason, but they were for other phones and I'm not sure if it's related to the Note 4.
I've seen some mention of the bootloader being locked, but I don't know how to tell if the bootloader is locked or not. I see the same exact boot screen that I saw with my Note 3, S4, S3, etc. Could the issue be the bootloader?
I've also found this thread, but I can't get TWRP to mount in Windows, it keeps saying the driver failed to install. MTP transfers worked fine with the stock ROM was still there, but for some reason it doesn't work with the Mount option in TWRP. I'm downloading the Android SDK so I can try using adb
If anyone else has run into this, can you advise me on what to do from here?
EDIT: Nevermind, fixed it. Changed system partition's filesystem to F2FS via TWRP, and this allowed CM and gapps to flash with no issue. Now booted into CM But hopefully this will be helpful if anyone else has this issue
EDIT2: Buuuuut now the WiFi's not working. It just gets stuck at "turn on WiFi" but nothing actually turns on, and the on/off button for WiFi in settings is grayed out. IT NEVER ENDS
Click to expand...
Click to collapse
You must flash 5.1.1 ok1 bootloader to get wifi work
I suggest you first flash 5.1.1 firmware in odin
Then flash twrp. Tar file in odin.
Then make full wipe
Flash cm rom + gapps
You will get clean rom install without any errors
Hope this will help
Trex888 said:
You must flash 5.1.1 ok1 bootloader to get wifi work
I suggest you first flash 5.1.1 firmware in odin
Then flash twrp. Tar file in odin.
Then make full wipe
Flash cm rom + gapps
You will get clean rom install without any errors
Hope this will help
Click to expand...
Click to collapse
Okay I'll give that a shot. Are "5.11 ok1 bootloader" and "5.1.1 firmware" the same thing? And do you know where I can find it/them?
Just flashed OK1 via Odin via this thread, but it's just boot looping over and over
EDIT: Did a simple factory wipe and it's working fine now. Currently running unrooted Stock 5.1.1, Baseband N910PVPS4COK1. So I'm basically starting from the beginning, whereas before it was on 6.0 but now it's 5.1.1
Am now rooted but I can't get TWRP installed, I flash it and try to boot to recovery but it just boots to a black screen
Issue seems to be resolved, edited original post
AbuFiraas said:
Okay I'll give that a shot. Are "5.11 ok1 bootloader" and "5.1.1 firmware" the same thing? And do you know where I can find it/them?
Click to expand...
Click to collapse
Go to download mode and check exact model number
Tell me model number and i give you links for bootloader and firmware
Trex888 said:
Go to download mode and check exact model number
Tell me model number and i give you links for bootloader and firmware
Click to expand...
Click to collapse
It's working now, I found another post that had all the various stock firmwares on there. Now the issue I'm having is that my camera doesn't focus at all, but I don't know if it's a hardware or software issue. I never checked the camera before rooting the first time. Gonna try going back to unrooted stock again but if that doesn't change anything, I might have to take it to a Sprint store and get a replacement. Hopefully they don't notice the KNOX trip... lol

Categories

Resources