Develop Bugs

Lost recovery when trying to flash 4.3 ROM

Ok so I am not the greatest when it comes to flashing ROMs but so far I have managed to get by.
I went from MMuzzyROM 4.2.2 to [ROM] [4.3] [JSS15J]. I wiped my data/dalvick/cache, flashed the new ROM and Gaaps and installed SuperuserSU. As of right now SuperuserSU will not install and I get an installation error. And when using Rom Manager I can not reboot into recovery. And there is a bit more, when I try and boot into recovery from the holding the volume and power button down, after choosing recovery the android with the error shows up. From what I understand is that the 4.3 rom I flashed removed the stock recovery, but I am just confused how to get back recovery.
My main question is did I loose root and how can I get the recovery option back.
Thanks, Noel

knoll126 said:
Ok so I am not the greatest when it comes to flashing ROMs but so far I have managed to get by.
I went from MMuzzyROM 4.2.2 to [ROM] [4.3] [JSS15J]. I wiped my data/dalvick/cache, flashed the new ROM and Gaaps and installed SuperuserSU. As of right now SuperuserSU will not install and I get an installation error. And when using Rom Manager I can not reboot into recovery. And there is a bit more, when I try and boot into recovery from the holding the volume and power button down, after choosing recovery the android with the error shows up. From what I understand is that the 4.3 rom I flashed removed the stock recovery, but I am just confused how to get back recovery.
My main question is did I loose root and how can I get the recovery option back.
Thanks, Noel
Click to expand...
Click to collapse
4.3 is buggy with root right now. You can use rom manager to reflash cwmrecovery or you can use goomanager to install twrp

dnewha sees
NyPlaya513 said:
4.3 is buggy with root right now. You can use rom manager to reflash cwmrecovery or you can use goomanager to install twrp
Click to expand...
Click to collapse
I try to reflash but doesn't seem to work.

knoll126 said:
I try to reflash but doesn't seem to work.
Click to expand...
Click to collapse
USE TWRP!

When trying to flash CWR I get an error message. I am pretty sure I am unrooted without an option for recovery and stuck on 4.3?

beekay201 said:
USE TWRP!
Click to expand...
Click to collapse
Ok I guess I am just too confused. Downloading TWRP gives me an image file which I don't understand how to install, because I thought I need recovery to do it? When in fastboot I can select recovery but I get the error android.

knoll126 said:
When trying to flash CWR I get an error message. I am pretty sure I am unrooted without an option for recovery and stuck on 4.3?
Click to expand...
Click to collapse
what error message?
what's the fastboot command you're using to flash recovery.
about loosing your recovery after flashing/boot/reboot OS for the first time, it's probably the same that 4.2 had
/system/recovery-from-boot.p
/system/install-recovery.sh

beekay201 said:
what error message?
what's the fastboot command you're using to flash recovery.
about loosing your recovery after flashing/boot/reboot OS for the first time, it's probably the same that 4.2 had
/system/recovery-from-boot.p
/system/install-recovery.sh
Click to expand...
Click to collapse
The error message is when using the clockwork mod app to install the recovery, once downloaded it states an error has occurred. Then when trying TWRP I am following these steps I get "fastboot is not a recognizable command..." I am pretty lost as you can tell and am thankful for the help.

knoll126 said:
The error message is when using the clockwork mod app to install the recovery, once downloaded it states an error has occurred. Then when trying TWRP I am following these steps I get "fastboot is not a recognizable command..." I am pretty lost as you can tell and am thankful for the help.
Click to expand...
Click to collapse
*facepalm*
WHY you people don't read the frakkin stickies?!?!?
http://forum.xda-developers.com/showthread.php?t=1812959

beekay201 said:
*facepalm*
WHY you people don't read the frakkin stickies?!?!?
http://forum.xda-developers.com/showthread.php?t=1812959
Click to expand...
Click to collapse
Mainly because I thought if I had rooted my device and done all this once, I should remember how to do it again. But through ignorance I thought I could and be able to remember the steps and what not. I'll read through it and figure it out, it was just a moment of panic of losing the option of recovery that I have had for a long time and not being able to use it means (or I think it means) I am just stuck of 4.3 for a bit and hopefully the ROM isn't too bad.

How to update to 4.4 with TWRP?

I rooted my tablet and installed TWRP end of august.
Two days ago I installed 4.4 with an OTA update which broke the phone, it always booted into recovery. I learned that TWRP was incompatible with 4.4 older versions of TWRP might cause problems with 4.4 and flashed the 4.3 factory image using adb. The tablet is now working again.
I'm just not sure how to proceed now. It seems the TWRP recovery is gone, because from Fastboot when I select recovery I get the dead android with the red triangle. Can I just update by following this post?

bur2000 said:
I rooted my tablet and installed TWRP end of august.
Two days ago I installed 4.4 with an OTA update which broke the phone, it always booted into recovery. I learned that TWRP was incompatible with 4.4 and flashed the 4.3 factory image using adb. The tablet is now working again.
I'm just not sure how to proceed now. It seems the TWRP recovery is gone, because from Fastboot when I select recovery I get the dead android with the red triangle. Can I just update by following this post?
Click to expand...
Click to collapse
Where have you read twrp is not compatible with 4.4? Many people are using twrp with 4.4. You should use the latest version which supports SELinux security contexts.
It is probably easiest if you just flash the KRT16S factory image from that thread.

sfhub said:
Where have you read twrp is not compatible with 4.4? Many people are using twrp with 4.4. You should use the latest version which supports SELinux security contexts.
Click to expand...
Click to collapse
It doesn't seem to happen for everybody, maybe it's older versions of TWRP. Mine was from August. I rephrased my original post to make that clear. There are some threads here about the problem and if you google for it you'll find some more warnings. It's always the same thing, the tablet will only boot into recovery after an OTA with TWRP:
http://forum.xda-developers.com/showthread.php?p=47709956
http://forum.xda-developers.com/showthread.php?p=47713265
http://forum.xda-developers.com/showthread.php?t=2537669
http://www.droid-life.com/2013/11/1...krt16o-official-update-for-nexus-7-2012-wifi/ (in the comments)
http://forum.xda-developers.com/showthread.php?t=2510810
Thanks for your reply though, so I'll try flashing the factory image. Should I use adb for that or newest TWRP? Also the red triangle means my custom recovery is gone, correct?

bur2000 said:
It doesn't seem to happen for everybody, maybe it's older versions of TWRP. Mine was from August. I rephrased my original post to make that clear. There are some threads here about the problem and if you google for it you'll find some more warnings. It's always the same thing, the tablet will only boot into recovery after an OTA with TWRP:
http://forum.xda-developers.com/showthread.php?p=47709956
http://forum.xda-developers.com/showthread.php?p=47713265
http://forum.xda-developers.com/showthread.php?t=2537669
http://www.droid-life.com/2013/11/1...krt16o-official-update-for-nexus-7-2012-wifi/ (in the comments)
http://forum.xda-developers.com/showthread.php?t=2510810
Thanks for your reply though, so I'll try flashing the factory image. Should I use adb for that or newest TWRP? Also the red triangle means my custom recovery is gone, correct?
Click to expand...
Click to collapse
Personally I think it is easiest to flash the factory image but you probably need around the same number of steps either way.
The factory image is meant to flash in boot loader using fastboot, not using adb.
The fallen android means you are using stock recovery. It is an image that hides the recovery menu. press/hold power, press/release VolUp, release Power to see the actual recovery menu and any errors which might have occured

sfhub said:
Personally I think it is easiest to flash the factory image but you probably need around the same number of steps either way.
Click to expand...
Click to collapse
Thanks again, all worked well going along with your guide. Only thing to do now is getting TWRP and SU flashed.
It seems like I'm not really up-to-date anymore when it comes to flashing, I only knew of using recovery and never heard of sideload or using fastboot to flash any images.

[Q] Problems with AT&T update from 4.1.1

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

Can't back up Nandroid and can I just flash a custom rom?

My phone current status
Unlocked
S-on (I looked for this and couldn't find solution to s-off)
Latest twrp flashed
I try to flash the supersu, it flashed, but supersu app doesn't detect the root binary. :l
Within twrp, I try to do a back up of nandroid, but i get error that the backup file is 0 bytes and back up failed.
Everytime I reboot system from twrp, it says there's no OS, but I boot into the stock OS fine.
-
From this what else do I need to do or fix?
can I just flash a custom rom? I don't ever do backup on any of my android. if something goes wrong, I just flash a new rom :l
I came from a nexus 6 so this is a bit confusing.

Use the older version of twrp. I think 5.0. I had the same issue until I did that.

I used twrp 2.6.8.3 after that no probs all good, before on 2.8.6.0 no os and no back up

dustin4vn said:
My phone current status
Unlocked
S-on (I looked for this and couldn't find solution to s-off)
Latest twrp flashed
I try to flash the supersu, it flashed, but supersu app doesn't detect the root binary. :l
Within twrp, I try to do a back up of nandroid, but i get error that the backup file is 0 bytes and back up failed.
Everytime I reboot system from twrp, it says there's no OS, but I boot into the stock OS fine.
-
From this what else do I need to do or fix?
can I just flash a custom rom? I don't ever do backup on any of my android. if something goes wrong, I just flash a new rom :l
I came from a nexus 6 so this is a bit confusing.
Click to expand...
Click to collapse
I found I had to flash the Beta version of recovery, and an additional step. Definitely backup stock as there are few RUUs right now. Check out details HERE

angasreid said:
I found I had to flash the Beta version of recovery, and an additional step. Definitely backup stock as there are few RUUs right now. Check out details HERE
Click to expand...
Click to collapse
Thanks. I noticed that. I keep flashing with the stable version and nothing works lol. I don't ever back up my roms lmao. Had like 50 android phones, I hate stock with all my might. No reason to ever go back to stock for me lol.

[Guidance] SGH-T989 UPDATING ISSUE!

Good evening everyone!
I've recently wanted to update my Hercules from 4.1 (I know it's reeealy outdated) to version 6.0 Marshmallow.
So I did a few steps and now I cant' seem to go any further, and I need your help.
So far, I've done the following:
-Installed TWRP 2.8.7.0
-Used Odin to flash the TWRP mentioned above
Now, I know there are a few problems regarding this version of the TWRP on the Hercules, so I tried fixing it by using Odin again and flashing the updated 2.8.7.1 and even the 3.0 version that I found on some threads, but with no sucess.
I haven't even had the chance to install Marshmallow on my phone in the first chance, because I couldn't find any .ZIP folders on the TWRP instalation menu.
I really appreciate your help guys, I'm a noob at this and I'm just starting to figure what is what, I just need my phone updated. It's running so far atleast, so it's not hard bricked I guess.

Did you follow the instructions to flash TWRP using Odin?

olafo73 said:
Did you follow the instructions to flash TWRP using Odin?
Click to expand...
Click to collapse
I'm pretty sure I did everything I was intended to do. I installed Samsung Kies so I could install the drivers on my mobile, and then TWRP through Odin properly with the blue light showing up. After flashing it, it turned green and said PASS or PASSED. So I think I did everything right on that end, I can even access TWRP with no real problems.
I even tried to do a ROOT on my system, but again, I couldn't use ZIP or any other files on the TWRP installation option because they simply do not appear

bump

Watching this thread as I have the same problem.
I can boot to TWRP 2.8.7, but if I try to install, there's no file to install from.
I can go back to TWRP 2.6.0, and then mount the card and see the ROM, but every ROM I try fails. Something about non-virtual partitions if I try 4.4 or better, and error executing updater binary if i try 4.1

aguycalled80 said:
Watching this thread as I have the same problem.
I can boot to TWRP 2.8.7, but if I try to install, there's no file to install from.
I can go back to TWRP 2.6.0, and then mount the card and see the ROM, but every ROM I try fails. Something about non-virtual partitions if I try 4.4 or better, and error executing updater binary if i try 4.1
Click to expand...
Click to collapse
How did you go back to TWRP 2.6.0?

N1ZUW said:
How did you go back to TWRP 2.6.0?
Click to expand...
Click to collapse
With Odin.
I can boot in download mode no problem.

N1ZUW said:
Good evening everyone!
I've recently wanted to update my Hercules from 4.1 (I know it's reeealy outdated) to version 6.0 Marshmallow.
So I did a few steps and now I cant' seem to go any further, and I need your help.
So far, I've done the following:
-Installed TWRP 2.8.7.0
-Used Odin to flash the TWRP mentioned above
Now, I know there are a few problems regarding this version of the TWRP on the Hercules, so I tried fixing it by using Odin again and flashing the updated 2.8.7.1 and even the 3.0 version that I found on some threads, but with no sucess.
I haven't even had the chance to install Marshmallow on my phone in the first chance, because I couldn't find any .ZIP folders on the TWRP instalation menu.
I really appreciate your help guys, I'm a noob at this and I'm just starting to figure what is what, I just need my phone updated. It's running so far atleast, so it's not hard bricked I guess.
Click to expand...
Click to collapse
I don't know of any problems with any of the recoveries. However there are different recoveries for different roms which need to be used in a specific order and in a specific way, the first time that you virtually repartition your phone.
Have you gone through the process of applying the "virtual partition" and installing the modified "virtual partition" recovery? This is required for most of the MM roms on this phone (Hercules). The process is very well documented here http://forum.xda-developers.com/galaxy-s2-tmobile/help/guidance-sgh-t989-updating-issue-t3414641 in the #2nd post.

markusrow said:
I don't know of any problems with any of the recoveries. However there are different recoveries for different roms which need to be used in a specific order and in a specific way, the first time that you virtually repartition your phone.
Have you gone through the process of applying the "virtual partition" and installing the modified "virtual partition" recovery? This is required for most of the MM roms on this phone (Hercules). The process is very well documented here http://forum.xda-developers.com/galaxy-s2-tmobile/help/guidance-sgh-t989-updating-issue-t3414641 in the #2nd post.
Click to expand...
Click to collapse
Hi, thanks for replying
No, I dont' take I have taken that step actually. I'm pretty new to this and I tried following every step correctly, but I know that I failed or skipped something at some extent and I've been trying to figure out what exactly, so I can fix it. I guess I need to Virtual Partition my phone then, could you post me the link do to so? Because I think you posted one that would take back to this post

aguycalled80 said:
With Odin.
I can boot in download mode no problem.
Click to expand...
Click to collapse
How do you go in download mode if you have TWRP installed? Does TWRP work as download mode aswell? Thanks for your help man, hope you can fix your phone too!

N1ZUW said:
How do you go in download mode if you have TWRP installed? Does TWRP work as download mode aswell? Thanks for your help man, hope you can fix your phone too!
Click to expand...
Click to collapse
I shut it down in TWRP then hold volume down and power to go into download mode.
My phone has gone backwards now though - it doesn't matter what I load in Odin now, it won't boot up. The SAMSUNG screen is on, with a progress bar, but it never gets to the end. It stops right near the end and it sits there until I reboot it again.