I know this has been asked hundreds of times, and i searched the forums for days for a way to fix it, but with no use.
I have a rooted AT&T Galaxy SIII with JB 4.1.1. I am trying to install the CM 10.1(4.2.2) Nightly version, but i always get the infamous "Status 7 Installation Aborted" error.
Yes i am sure im downloading the correct ROM zip file for my phone and carrier.
I have CWM 6.0.2.1, and i followed the steps correctly. (Clear data -> Clear Cache Partition -> Clear Dalvik Cache -> install ROM)
I have tried so many times, i also re-rooted my phone, reinstalled CWM, and redownloaded different nightly versions of the ROM, as well as other ROMS like JellyBam.
I also tried to delete the assert lines in the update-script file, but that also wouldnt work.
Thank you. :good:
And please dont hate on me, im new to rooting and flashing. :crying:
Improper recovery.
samelaryan said:
I know this has been asked hundreds of times, and i searched the forums for days for a way to fix it, but with no use.
I have a rooted AT&T Galaxy SIII with JB 4.1.1. I am trying to install the CM 10.1(4.2.2) Nightly version, but i always get the infamous "Status 7 Installation Aborted" error.
Yes i am sure im downloading the correct ROM zip file for my phone and carrier.
I have CWM 6.0.2.1, and i followed the steps correctly. (Clear data -> Clear Cache Partition -> Clear Dalvik Cache -> install ROM)
I have tried so many times, i also re-rooted my phone, reinstalled CWM, and redownloaded different nightly versions of the ROM, as well as other ROMS like JellyBam.
I also tried to delete the assert lines in the update-script file, but that also wouldnt work.
Thank you. :good:
And please dont hate on me, im new to rooting and flashing. :crying:
Click to expand...
Click to collapse
BAM1789 said:
Improper recovery.
Click to expand...
Click to collapse
if you can boot into the phone, download ROM manager and update your cwm recovery. latest version is 6.0.2.8.
CM10 and 10.1 are picky about you having the most recent version. cheers
xBeerdroiDx said:
if you can boot into the phone, download ROM manager and update your cwm recovery. latest version is 6.0.2.8.
CM10 and 10.1 are picky about you having the most recent version. cheers
Click to expand...
Click to collapse
I did that and it worked thank you :good:
samelaryan said:
I did that and it worked thank you :good:
Click to expand...
Click to collapse
thats what we're all here for, buddy
Status 7: installation aborted.
xBeerdroiDx said:
thats what we're all here for, buddy
Click to expand...
Click to collapse
Hi guys, I'm having same issue but on N7000 international version. I'm able to go in the recovery mode and download mode but phone won't boot normally. It's stuck on Samsung logo so can you please advise something? How can I update CWM if that's the issue. I was on ICS 4.0.4 XXLRK before trying to install CM10.1 on Note.
Thanks in advance for your help.
perceptorz said:
Hi guys, I'm having same issue but on N7000 international version. I'm able to go in the recovery mode and download mode but phone won't boot normally. It's stuck on Samsung logo so can you please advise something? How can I update CWM if that's the issue. I was on ICS 4.0.4 XXLRK before trying to install CM10.1 on Note.
Thanks in advance for your help.
Click to expand...
Click to collapse
I would be doing my research in an N7000 forum, friend.
Also, your post seems confusing as you seem to be saying you also got a status 7 error but then you appear to have installed abroad and are stuck at the boot logo. If you successfully flashed the correct rom for your device without any errors, pull battery, replace and wipe data in recovery. Reboot
xBeerdroiDx said:
I would be doing my research in an N7000 forum, friend.
Also, your post seems confusing as you seem to be saying you also got a status 7 error but then you appear to have installed abroad and are stuck at the boot logo. If you successfully flashed the correct rom for your device without any errors, pull battery, replace and wipe data in recovery. Reboot
Click to expand...
Click to collapse
Apologies for both confusion and using the S3 that to find some help. I just found the situation quite familiar so I couldn't help myself from asking the question
On the situation, I was able to install CWM and am able to go to recovery or download mode but the error displays when I try to update the zip of any rom.
perceptorz said:
Apologies for both confusion and using the S3 that to find some help. I just found the situation quite familiar so I couldn't help myself from asking the question
On the situation, I was able to install CWM and am able to go to recovery or download mode but the error displays when I try to update the zip of any rom.
Click to expand...
Click to collapse
If the phone itself is functioning fine but you simply cannot flash a new rom or rom update, you need to update your recovery. Go to clockworkmods website and download version 6.0.1.2.
xBeerdroiDx said:
If the phone itself is functioning fine but you simply cannot flash a new rom or rom update, you need to update your recovery. Go to clockworkmods website and download version 6.0.1.2.
Click to expand...
Click to collapse
Right now, phone doesn't get pass Samsung boot logo so will I be able to update new CWM using Odin? (Sorry, if the question appears to be basic or stupid)
perceptorz said:
Right now, phone doesn't get pass Samsung boot logo so will I be able to update new CWM using Odin? (Sorry, if the question appears to be basic or stupid)
Click to expand...
Click to collapse
I would take up this situation in the correct forum. The more we discuss your device issues the more likey you are to download the wrong file or use a procedure not designed for your device software.
If you came from stock, flashed a rom and are stuck at the samsung logo, boot into recovery, wipe data and cache. Reboot to see if that helped. If not, seek advice in the N7000 forum. Cheers
Thanks for the guidance.
Related
hello all,
I'm having trouble understanding something with my SIII. I have a Canadian Rogers SIII currently running DJJOHNNYBLAZE's rom.
great rom, no problems at all!
But when I try to, I haven't been able to install any CM, AOKP or AOSP rom on my phone through TWRP or CWM recovery... only the stock based roms work when I install them..
is there something I'm missing? or doing rom? I'm quite familiar with the flashing process, I've done it a million times on my SIII and my previous Sony Xperia..
Any help, tips or direction to an answer is much appreciated
RoshanDoon said:
But when I try to, I haven't been able to install any CM, AOKP or AOSP rom on my phone through TWRP or CWM recovery... only the stock based roms work when I install them..
Click to expand...
Click to collapse
First question: what fails about the install process?
Second question: how did you install the recovery images?
Most of the time when I hear something like this on a Canadian S3, it's because of the different device code (d2can vs. d2att) of the Canadian model; the images you get through goomanager or ROM Manager or similar will see that you're trying to install a d2att ROM on a device it sees as a d2can, fails to get that the two are software-compatible, and aborts with a "status 7" error.
If that's the case, you can manually flash, say, the d2att TWRP image (look here for the image and instructions), which will happily flash d2att ROMs onto your device.
smelenchuk said:
First question: what fails about the install process?
Second question: how did you install the recovery images?
Most of the time when I hear something like this on a Canadian S3, it's because of the different device code (d2can vs. d2att) of the Canadian model; the images you get through goomanager or ROM Manager or similar will see that you're trying to install a d2att ROM on a device it sees as a d2can, fails to get that the two are software-compatible, and aborts with a "status 7" error.
If that's the case, you can manually flash, say, the d2att TWRP image (look here for the image and instructions), which will happily flash d2att ROMs onto your device.
Click to expand...
Click to collapse
thanks for the quick reply
to answer your first question: when i flash any of them, in recovery it just says "Failed" in red letters.. the funny part is I've installed a couple open source roms before and they worked (ie Liquid, Ktoonez AOKP rom), now i can't :S the ones i flashed were d2att, possibly my problem now, however, why did they work before?
to answer the second: i do a factory reset, wipe cache, flash rom, install gapps, wipe dalvik (as stated in most forums)
also, i've installed TWRP by installing GooManager on my phone and installing it from there, is that wrong? is it different than manually doing it with the command?
thanks again
RoshanDoon said:
i've installed TWRP by installing GooManager on my phone and installing it from there, is that wrong? is it different than manually doing it with the command?
Click to expand...
Click to collapse
Yes - that means you have the d2can TWRP image and not the d2att recovery image, which causes the problem I described. You will probably want to manually install the d2att image in its place.
smelenchuk said:
Yes - that means you have the d2can TWRP image and not the d2att recovery image, which causes the problem I described. You will probably want to manually install the d2att image in its place.
Click to expand...
Click to collapse
ahhhh... gracias!
will do that now then, thanks
I'm having a similar problem.
I've rooted my s3 i747m (virgin), and I have backed up using TWRP.
Attempting to install Cyanogen mod from a .zip on internal sdcard. In recovery mode I've gone in and tried to install from the zip, but I'm getting status 7. Any ideas?
ultrashaun said:
I've rooted my s3 i747m (virgin), and I have backed up using TWRP.
Attempting to install Cyanogen mod from a .zip on internal sdcard. In recovery mode I've gone in and tried to install from the zip, but I'm getting status 7. Any ideas?
Click to expand...
Click to collapse
Exactly the same problem, exactly the same cause; read the earlier posts in this thread for an idea of what to do.
smelenchuk said:
Exactly the same problem, exactly the same cause; read the earlier posts in this thread for an idea of what to do.
Click to expand...
Click to collapse
Again! You've done it sir. This worked exactly right. Thank you so much.
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.
Hi all ... I am working with a Samsung Galaxy Tab 3 7.0 (SM-T210R) and was interested in speeding the device up.
I flashed TWRP 2.6.3 and rooted and then tried to flash the SEAL ROM after watching the video.
During the install. I got a bunch of errors ... I don't have a screenshot, but it said the following:
ASSERT FAILED package_extract_file ("boot.img") ...
E: Error Executing updater binary in zip '/external_sd/ROM/SEAL V2 Official.zip' ....
Error Flashing Zip 'external_sd/ROMS/SEAL V2 ...
Luckily, the backup is working fine and I was able to restore.
I finally was able to flash a debloat script that I saw on XDA to speed it up a bit, but I really wanted to try this rom.
Any ideas are appreciated. Thanks very much.
savidon said:
Hi all ... I am working with a Samsung Galaxy Tab 3 7.0 (SM-T210R) and was interested in speeding the device up.
I flashed TWRP 2.6.3 and rooted and then tried to flash the SEAL ROM after watching the video.
During the install. I got a bunch of errors ... I don't have a screenshot, but it said the following:
ASSERT FAILED package_extract_file ("boot.img") ...
E: Error Executing updater binary in zip '/external_sd/ROM/SEAL V2 Official.zip' ....
Error Flashing Zip 'external_sd/ROMS/SEAL V2 ...
Luckily, the backup is working fine and I was able to restore.
I finally was able to flash a debloat script that I saw on XDA to speed it up a bit, but I really wanted to try this rom.
Any ideas are appreciated. Thanks very much.
Click to expand...
Click to collapse
Try removing any spaces in the zip name.
gr8nole said:
Try removing any spaces in the zip name.
Click to expand...
Click to collapse
Thanks for the suggestion .. I just tried that and got the same errors.
Strange.
FWIW .. I also had issues trying to install the RocketTab ROM as well. Different problem, but still never worked. As I said, I was able to flash a debloat script that seems to have helped with the performance somewhat but still not great.
Thanks again.
savidon said:
Hi all ... I am working with a Samsung Galaxy Tab 3 7.0 (SM-T210R) and was interested in speeding the device up.
I flashed TWRP 2.6.3 and rooted and then tried to flash the SEAL ROM after watching the video.
During the install. I got a bunch of errors ... I don't have a screenshot, but it said the following:
ASSERT FAILED package_extract_file ("boot.img") ...
E: Error Executing updater binary in zip '/external_sd/ROM/SEAL V2 Official.zip' ....
Error Flashing Zip 'external_sd/ROMS/SEAL V2 ...
Luckily, the backup is working fine and I was able to restore.
I finally was able to flash a debloat script that I saw on XDA to speed it up a bit, but I really wanted to try this rom.
Any ideas are appreciated. Thanks very much.
Click to expand...
Click to collapse
I followed these directions (minus the rooting, as the ROM is already Rooted) yesterday and installed RocketTab 3.1 without a hitch:
http://forum.xda-developers.com/showthread.php?t=2660588
tsg2513 said:
I followed these directions (minus the rooting, as the ROM is already Rooted) yesterday and installed RocketTab 3.1 without a hitch:
http://forum.xda-developers.com/showthread.php?t=2660588
Click to expand...
Click to collapse
I've tried RocketTab multiple times ... and after flashing I get a message that the device appears to not be rooted, and offers to install SuperSU ... whether I say install or not, after I reboot ... the tablet freezes on the Samsung opening screen. I have no idea what else to try.
Thanks.
savidon said:
I've tried RocketTab multiple times ... and after flashing I get a message that the device appears to not be rooted, and offers to install SuperSU ... whether I say install or not, after I reboot ... the tablet freezes on the Samsung opening screen. I have no idea what else to try.
Thanks.
Click to expand...
Click to collapse
Did you check the MD5 of the zip, it could be a bad download.
Sent from my SCH-I605
gr8nole said:
Did you check the MD5 of the zip, it could be a bad download.
Sent from my SCH-I605
Click to expand...
Click to collapse
I did .. it matched. I think I'll try downloading again just in case though. Not sure what else to try at this point.
Thanks.
So I re-downloaded the SEAL ROM files and this time it installed without any errors, but I still got the not rooted message when I tried to reboot the device in TWRP. Again, whether or not I choose to install SuperSU, it hangs on the Samsung Galaxy Tab screen and I need to boot back into recovery and restore from backup to get working again.
For some reason, the root in the ROMs is not taking or something? Is that what is causing the problem? Does that make any sense?
Any other ideas? Thanks again!
savidon said:
So I re-downloaded the SEAL ROM files and this time it installed without any errors, but I still got the not rooted message when I tried to reboot the device in TWRP. Again, whether or not I choose to install SuperSU, it hangs on the Samsung Galaxy Tab screen and I need to boot back into recovery and restore from backup to get working again.
For some reason, the root in the ROMs is not taking or something? Is that what is causing the problem? Does that make any sense?
Any other ideas? Thanks again!
Click to expand...
Click to collapse
Sound like the system is not flashing correctly. Maybe try a different recovery.
Sent from my SCH-I605
Try the normal CWM coz touch-based are allergic to my device too....no worries you can still still scroll down the menu list of options using your finger tips
Sent from my SM-T211 using XDA Premium 4 mobile app
So here is the latest update in my custom rom saga ...
I downgraded TWRP to 2.6.1 .. and attempted to re-flash both SEAL and RocketTab. Both installs seemed to complete without any errors this time, but after rebooting, my device froze on the Samsung Galaxy Tab logo screen .. before the boot animation. This happened for both the SEAL and RocketTab roms. I also no longer got the not rooted error message, so it looked like it was fine.
Any thoughts on why these custom roms are not booting? I appreciate the help.
I restored back to my de-bloated stock backup, and it works fine. A little faster definitely, but not speedy by any means.
Thanks again.
Try philz touch recovery. I also had problems with cwm and twrp. But philz touch does the charm for me.
Sent from my SM-T210R using xda app-developers app
Hi, I have rooted my device and installed a custom recovery. But that's it, haven't installed any new ROM, and still have the stock one witch it came with.
Today I received an update message, so I downloaded the new update, and as it should be, it requested a reset.
After the reset, the device boot himself into the recovery, ans apparently refuses to boot into the new rom, or anywhere but the recovery.
I performed a full wipe, and did a system restore. And still it always boot into the recovery.
Its a "Team Win" recovery v2.6.3.2
Help please.
Vad88 said:
Hi, I have rooted my device and installed a custom recovery. But that's it, haven't installed any new ROM, and still have the stock one witch it came with.
Today I received an update message, so I downloaded the new update, and as it should be, it requested a reset.
After the reset, the device boot himself into the recovery, ans apparently refuses to boot into the new rom, or anywhere but the recovery.
I performed a full wipe, and did a system restore. And still it always boot into the recovery.
Its a "Team Win" recovery v2.6.3.2
Help please.
Click to expand...
Click to collapse
what is the version number of you pad?? like 12a, 12b, 18a, 20a, 20b...........etc
Which one of those???
Jhon998 said:
what is the version number of you pad?? like 12a, 12b, 18a, 20a, 20b...........etc
Which one of those???
Click to expand...
Click to collapse
I dont remember man...
I last time I rooted a device it was a Galaxy S2, and I cracked opened the **** out of him, and something like this never happened to me..
As I told, I did a system restore, why it still doesnt boot anywhere beyond the recovery?
One more thing,
After I manage to turn it off, it starts immediately as I plug in the power, but stops on the "Logo" and with this title in the up right corner: "Secure boot error! Cause: Device Unlock, so Boot Success"
Thats it... got this message and doesnt boot... After I unplug the power, it boots into recovery, and only then (whie unplug) I can order it to power off.
Iam desperate..
Ok, now I think I am truly Fckd up...
I accidentally deleted the only restore file I had... witch didn't quit helped me the one time I launched it.. but anyways, now even this one is gone.
So now I stuck with god know what system.. (I did launched the restore, bit it didnt helped).
I do have a working recovery, and thats it. Please help me restore the device to fully stoke.
Vad88 said:
Ok, now I think I am truly Fckd up...
I accidentally deleted the only restore file I had... witch didn't quit helped me the one time I launched it.. but anyways, now even this one is gone.
So now I stuck with god know what system.. (I did launched the restore, bit it didnt helped).
I do have a working recovery, and thats it. Please help me restore the device to fully stoke.
Click to expand...
Click to collapse
Download a ROM onto sdcard through computer, transfer sdcard to tablet, install through recovery.
sleekmason said:
Download a ROM onto sdcard through computer, transfer sdcard to tablet, install through recovery.
Click to expand...
Click to collapse
Thanks, Iam downloading the one from this thread: (ROM) OFFICIAL 4.4.2 V500 Update & Go back to 4.2.2!
Is it possible to install it into the tablet in mine condition?
Vad88 said:
Thanks, Iam downloading the one from this thread: (ROM) OFFICIAL 4.4.2 V500 Update & Go back to 4.2.2!
Is it possible to install it into the tablet in mine condition?
Click to expand...
Click to collapse
Not sure. I was thinking Mahdi or Cyanogenmod. A complete ROM. If the 4.4.2 is a complete ROM, then yes. The update you are trying won't affect the recovery, correct?
sleekmason said:
Not sure. I was thinking Mahdi or Cyanogenmod. A complete ROM. If the 4.4.2 is a complete ROM, then yes. The update you are trying won't affect the recovery, correct?
Click to expand...
Click to collapse
Yes.. the update didnt effected the recovery, and from my experience it shouldnt... (the update is for the ROM, witch was stock)
Thats why I didnt install a custom ROM from the beginning, I wanted a rooted device, but for now I wanted to stay with stock ROM. After receiving an update message, I didnt think for a second that the root and the custom recovery will effect the update...
Maybe this update had something to do with the recovery... and because mine is custom, I have this issue...
Iam not an expert in the LG field, so Iam not familiar with those effects, the update caused...
Can you please look at the installation guide in the link I gave, and check if it is doable on my device.
Thank you for the help! :good:
I would like to update that I followed the instructions from this link: (ROM) OFFICIAL 4.4.2 V500 Update & Go back to 4.2.2!, and now the tablet is back alive!
Thanks for all the help!
Vad88 said:
I would like to update that I followed the instructions from this link: (ROM) OFFICIAL 4.4.2 V500 Update & Go back to 4.2.2!, and now the tablet is back alive!
Thanks for all the help!
Click to expand...
Click to collapse
Good!
Please update the post title and add "Solved".
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.