Develop Bugs

[B]PLEASE HELP[/B] I'm stuck in a Custom Recovery Reboot Loop!

Not sure what happened, but this is what's going' on. I'm working with SM-T210R / updated to the 4.4.2 - Did not like the issues with Custom Recoveries, so I got into TWRP - Restored my stock rom backup and everything restored fine and as expected. I went to Root the device, using RootJunky's TWRP recovery and root on YouTube (which I've done many times and never had an issue - I'm not a noob, but, still have a lot to learn) Anyways - when you go swipe to reboot the system, TWRP asks you about installing Supersu for Root access, and of course, you go with it. Well, since that swipe - it keeps rebooting into TWRP - I cant get to the system. I used Odin to install Philz and same thing, kept rebooting into Philz. I've tried re-restoring my back up and now it wont .... it acts like it is, but then it keeps throwing me back into the custom recovery being used ... any ideas or help is greatly appreciated!
PS - Thank you to gr8nole and RootJunky - I'm always using your guys' methods and suggestions.

jonstowe78 said:
Not sure what happened, but this is what's going' on. I'm working with SM-T210R / updated to the 4.4.2 - Did not like the issues with Custom Recoveries, so I got into TWRP - Restored my stock rom backup and everything restored fine and as expected. I went to Root the device, using RootJunky's TWRP recovery and root on YouTube (which I've done many times and never had an issue - I'm not a noob, but, still have a lot to learn) Anyways - when you go swipe to reboot the system, TWRP asks you about installing Supersu for Root access, and of course, you go with it. Well, since that swipe - it keeps rebooting into TWRP - I cant get to the system. I used Odin to install Philz and same thing, kept rebooting into Philz. I've tried re-restoring my back up and now it wont .... it acts like it is, but then it keeps throwing me back into the custom recovery being used ... any ideas or help is greatly appreciated!
PS - Thank you to gr8nole and RootJunky - I'm always using your guys' methods and suggestions.
Click to expand...
Click to collapse
Read the First part of this post. http://forum.xda-developers.com/showpost.php?p=55490325&postcount=1014
There is a stock recovery zip in my rom addons.

gr8nole said:
Read the First part of this post. http://forum.xda-developers.com/showpost.php?p=55490325&postcount=1014
There is a stock recovery zip in my rom addons.
Click to expand...
Click to collapse
Thanks for responding and offering your help ... and a BIG thanks to all that you do with giving us all that you do.
In response to your suggestion: That's IF you are using the Stock 4.4.2 ... I restored my Stock 4.1.2 before all this started happening ... Regardless, its all good now. After work I came home and decided to give it one more try, using Odin to put Philz on and go from there, and this time it took. Once I got Philz on, I was able to (again) restore my 4.1.2 stock backup (fix the flickering screen of course) and the get back to Nolekat v1.9 - thank GOD! Do you have any idea what would cause the Custom Recovery to keep rebooting to itself?

jonstowe78 said:
Thanks for responding and offering your help ... and a BIG thanks to all that you do with giving us all that you do.
In response to your suggestion: That's IF you are using the Stock 4.4.2 ... I restored my Stock 4.1.2 before all this started happening ... Regardless, its all good now. After work I came home and decided to give it one more try, using Odin to put Philz on and go from there, and this time it took. Once I got Philz on, I was able to (again) restore my 4.1.2 stock backup (fix the flickering screen of course) and the get back to Nolekat v1.9 - thank GOD! Do you have any idea what would cause the Custom Recovery to keep rebooting to itself?
Click to expand...
Click to collapse
The bootloop in recovery is caused by the bottloader. Some people appear to have this bootloader version even if they didn't flash the 4.4.2 firmware. I suspect that Samsung started including the new bottloader on devices before the KK firmware was released.

[Q&A] [RECOVERY] Ouya CWM Recovery

Q&A for [RECOVERY] Ouya CWM Recovery
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [RECOVERY] Ouya CWM Recovery. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

Can't boot into CWM Recovery
Hi,
I was thinking about installing CM11 and saw that I would need to install an updated CWM Recovery so I downloaded to the internal SD card and tried to boot CWM to flash the new version. When I tried to boot I just keep booting into normal android recovery which is badly over scanned on my TV. Having tried repeatedly to boot and pressing ALT + Print + I it never gets to CWM Recovery. So I tried rebooting into recovery from the ROM Manager app (which recognises I have CWM installed) but still standard recovery.
So I tried to flash again using one click recovery script and no ADB as I had previously switched on Wireless ADB arghhhh! Anyway I found an app to turn it off and it switches off wireless for that session only and I ran one click again. It went through the whole script and booted into standard over scanned Android recovery!
I am stuck now what to do next, any ideas? I would be happy to start from scratch but would doing a factory reset blow away CWM recovery or leave it still there?
The ouya is fully rooted with SU / Busybox / xposed and runs play store fine.
Any advice appreciated.
Paul.

Here is an image of the script I see when trying to re-run one click recovery. I assume it is not normal to see the unknown ID references?
I'm stuck unable to load CM11 without updating CWM Recovery so any help would be appreciated.

Fixed
Ah well after much searching I found people with similar issues as me and basically whilst I cannot pinpoint the exact issue I believe I had a permissions issue that was stopping CMW being written. I am not a programmer just a user and if I understood it correctly a previous update seems to have stopped me going into CWM Recovery. I had tried reloading etc but the errors I saw seem to be permission issues. After a lot of reading and seeing people overcoming this by running SU as a script and then issuing manual commands I decided to reload SU and this time when I ran the install CWM Recovery from Mod Collection for Ouya I noticed that straight away I got the message that it had been granted SU access and on reboot I am back in CWM Recovery. Have since upgraded to 6.0.4.8 which I need to go to CM11.
Paul.

thankks!

[Q&A] [Recovery][FOTA]CWM and TWRP recoveries for custom ROMs

Q&A for [Recovery][FOTA]CWM and TWRP recoveries for custom ROMs
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [Recovery][FOTA]CWM and TWRP recoveries for custom ROMs. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

cucumber09 said:
Tired waiting for someone to repack kernel with your favorite version of recovery? Or tired to run recovery script every time you update your ROM or kernel? Now you don't need any repacked kernels or recovery-scripts. Use your FOTAKernel as recovery partition!
It works on any kernel with extract_elf_ramdisk utility (it's built in mostly all kernels for custom ROMs, but I am not sure) by @Dees_Troy. And don't forget, that you are doing on your own risk, I am not responsible for bricked devices, acid rains or thermonuclear war.
Installation:
Download zip and flash it via your current recovery. If your current recovery is unusable, you can flash it via terminal emulator:
- Extract FOTAKernel.img and place it to the root of your external SD-card
- Type su and grant root access
- Type
Code:
dd if=/ext_card/FOTAKernel.img of=/dev/block/mmcblk0p23
- Reboot to recovery to test if it works (if not, try again and check if you are doing it correctly).
Download:
TWRP 2.8.4.0 (thanks to @Rohan purohit for compiling it for Xperia L, I just ported and modded it)
TWRP 2.8.0.0/CWM (or scroll down, it's right below this post)
You can restore original FOTAKernel image by following instructions in this post (or just scroll down, it is 3rd post, lol).
Some info:
Sony Xperia devices don't have recovery partition. Instead of this in custom kernels is used recovery-in-boot conception with two-stage boot (ramdisk-recovery is packed inside main ramdisk). And there is partition called FOTAKernel that is used for installing official FOTA (firmware-over-the-air) updates. After unlocking your bootloader it partition becomes redundant, because you cannot use OTA function anymore. So it may be used for storing recovery ramdisk. And this very useful future was implemented by recognized developer @Dees_Troy (lead TWRP developer), he developed utility extract_elf_ramdisk (it is merged to almost all kernels for Sony devices), it extracts recovery ramdisk from FOTA partition instead of using regular one from boot image. So even after updating or changing your kernel or ROM you don't lose your current recovery! Here is some info from Dees_Troy.
BTW, I don't own any of this work, I just adapted recovery images for using them from FOTA partition. And recoveries are not compiled by me.
Click to expand...
Click to collapse
Hey, i use your recovery but when i write reboot recovery in terminal, my phone boots normally. But i can acess it by volume up button. How can i fix it?

Vp10 said:
Hey, i use your recovery but when i write reboot recovery in terminal, my phone boots normally. But i can acess it by volume up button. How can i fix it?
Click to expand...
Click to collapse
It is CM bug, it will be fixed in next nightlies.

Hi bro, i see new twrp update in xperia l thread ..
I hope you to update them ..
Thangs

cucumber09 said:
It is CM bug, it will be fixed in next nightlies.
Click to expand...
Click to collapse
And how we can flash new nightlies without recovery?

Hi, can I install twrp 2.8.4.0 from my FOTA recovery 2.4.0.0?

digt said:
Hi, can I install twrp 2.8.4.0 from my FOTA recovery 2.4.0.0?
Click to expand...
Click to collapse
[emoji782]

AggelosGR said:
And how we can flash new nightlies without recovery?
Click to expand...
Click to collapse
Recovery is accessible, just press many times vol rocker 'till you will enter the recovery.
---------- Post added at 20:59 ---------- Previous post was at 20:55 ----------
2ALL
I'm reading Q&A section not often, better write to main thread or tag me (if you are not quoting me), so I will see the notification.

How to solve image unstability in FOTA TWRP?
Hello @cucumber09. I've been trying your FOTA recovery, which I consider a great solution for our device, but I'm facing image unstability while in recovery: the screen flips and flicks horizontally making it very hard to tap correctly any option, and could lead to fatal errors. Could you please tell me a solution? I've tried flashing several kernels/traditional recoveries, but when I make it work satable in recovery, then the OS does'nt boot (bootloop). I'm using stock 4.3 15.4.A.1.9 ROM, unlocked bootloader, rooted, with Xposed Framework and Gravitybox module.
Also I've tried many KK and LP ROMs but I always return to stock 'cause I can't stand glitches and gaps while listening to my favourite tunes.
Thanks in advance,
e-bert.

e-bert said:
Hello @cucumber09. I've been trying your FOTA recovery, which I consider a great solution for our device, but I'm facing image unstability while in recovery: the screen flips and flicks horizontally making it very hard to tap correctly any option, and could lead to fatal errors. Could you please tell me a solution? I've tried flashing several kernels/traditional recoveries, but when I make it work satable in recovery, then the OS does'nt boot (bootloop). I'm using stock 4.3 15.4.A.1.9 ROM, unlocked bootloader, rooted, with Xposed Framework and Gravitybox module.
Also I've tried many KK and LP ROMs but I always return to stock 'cause I can't stand glitches and gaps while listening to my favourite tunes.
Thanks in advance,
e-bert.
Click to expand...
Click to collapse
Your problem is using the stock sony rom, it doesn't support FOTA recoveries properly, as soon as you switch to any other rom the FOTA recovery will work.

Thanks & new question.
Remorcer said:
Your problem is using the stock sony rom, it doesn't support FOTA recoveries properly, as soon as you switch to any other rom the FOTA recovery will work.
Click to expand...
Click to collapse
OK. Thank you for your quick response. Now, could you suggest to me any custom ROM that has no glitches or gaps in music playing? In yor opinion, which is the best ROM you've tried for our device (Xperia M SS c1904)?
Thanks again.

e-bert said:
OK. Thank you for your quick response. Now, could you suggest to me any custom ROM that has no glitches or gaps in music playing? In yor opinion, which is the best ROM you've tried for our device (Xperia M SS c1904).
Thanks again.
Click to expand...
Click to collapse
Everyone has its own taste in roms, I like stable and clean roms and would suggest cm11 or PA, try some of the roms and I'm sure you'll find your favourite.

Bliss pop is good.try it ,the battery is good.smooth performance and id say not much sound glitch .
Sent from my nicki using XDA Premium 4 mobile app

All hail to all cucumber..
its so frustrated to install kernel only for recovery..
and its more frustrating when your phone not responsive because incompatible kernel.
i recommended to install this trough recovery..
more reliable and low risk..
if you cant install from recovery (signature verification failed), first install another kernel to get unsigned recovery (niu kernel example)..
its a long way, but i'm prefer this than risking my phone because wrong command..
tested in resurrection remix rom 5.1..

Installed fota twrp with terminal, it freezes
So I did just as it was written. Installed it with command thru terminal on a CM 12 rom on Xperia z2.
It did work, for approx 10 seconds. I reboot in recovery, got first the screen for
CM recovery, before it changed to twrp. When I got there, I couldn't press anything
And suddenly it reboot into normal again. Dunno what it can be?!

Stuck on cyanogenmod boot
Flashed it and now i'm stuck on the cyanogenmod boot screen

is TWRP better or CWM...?

i flashed the twrp version 2.8.3.0 stuck on boot animation and when flashed 2.8.5.0 loop of recovery...m on xenon hd 5.1.1 rom...can anyone help???/ i want to flash twrp recovery

Neemac said:
So I did just as it was written. Installed it with command thru terminal on a CM 12 rom on Xperia z2.
It did work, for approx 10 seconds. I reboot in recovery, got first the screen for
CM recovery, before it changed to twrp. When I got there, I couldn't press anything
And suddenly it reboot into normal again. Dunno what it can be?!
Click to expand...
Click to collapse
It is for Xperia M, not Z2. So it won't work on it.

@Neemac i think z2 have official fota twrp, so why you not use them?
Sent from my C1905 using Tapatalk

[Q&A] [RECOVERY][nozomi] TWRP 2.8.5.0 touch recovery [2015-02-12]

Q&A for [RECOVERY][nozomi] TWRP 2.8.5.0 touch recovery [2015-02-12]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [RECOVERY][nozomi] TWRP 2.8.5.0 touch recovery [2015-02-12]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

locked bootloader
m1st3r1 said:
for cwm, there is cwm (and twrp also) for locked bootloader, but it cant flash any kernel (due to locked bootloader). in summary you stuck with stock kernel (that can only be flashed with flashtool or similar tools (if any ) with locked bootloader.
Click to expand...
Click to collapse
Sorry, I'm a bit beginner...
Does this mean that
1. if I use the procedure on page http://teamw.in/project/twrp2/144 in section Download - Stock Kernel:
2. then I can install any ROMs? For example this one? http://forum.xda-developers.com/xperia-s/s-development/rom-naosprom-xperia-s-t2958516
?

Mickey8881 said:
Sorry, I'm a bit beginner...
Does this mean that
1. if I use the procedure on page http://teamw.in/project/twrp2/144 in section Download - Stock Kernel:
2. then I can install any ROMs? For example this one? http://forum.xda-developers.com/xperia-s/s-development/rom-naosprom-xperia-s-t2958516
?
Click to expand...
Click to collapse
Flashing TWRP would require unlocked bootloader. First unlock Your bootloader, then follow the procedure from here.
From Your other post, it turns out You cannot unlock bootloader, so You can flash only sock based ROM's which work on Stock kernel.

Why is there no version 2.8.6.0 for Xperia S?

Hello guys,
I'm just download and install TWRP manager from google play and i'm trying to install the recovery. I'm choosing device name as LT26i but no recovery file is detected.
If i choose device name as "nozomi" i can find everything but my original device name is LT26i.
What to do? Are you suggest to try with nozomi and install the recovery?

Captainlag said:
Hello guys,
I'm just download and install TWRP manager from google play and i'm trying to install the recovery. I'm choosing device name as LT26i but no recovery file is detected.
If i choose device name as "nozomi" i can find everything but my original device name is LT26i.
What to do? Are you suggest to try with nozomi and install the recovery?
Click to expand...
Click to collapse
Nozomi is the code name for LT26i/LT26ii, so You can use it with no problems.

Unable to recovery
I can't flash any recovery file !!!
While I'm trying to install it returns this:
Something is wrong
------------------------
Flashing recovery was
unsuccessful.Either you already
have this recovery installed or
another error has occured.Would
you like to attempt rebooting to
recovery now?
NO YES

Captainlag said:
I can't flash any recovery file !!!
While I'm trying to install it returns this:
Something is wrong
------------------------
Flashing recovery was
unsuccessful.Either you already
have this recovery installed or
another error has occured.Would
you like to attempt rebooting to
recovery now?
NO YES
Click to expand...
Click to collapse
Which method are You following? Try the method from here.

Thank you for your help Mirhawk, but it doesn't work

Captainlag said:
Thank you for your help Mirhawk, but it doesn't work
Click to expand...
Click to collapse
What error are You getting?

Mirhawk said:
What error are You getting?
Click to expand...
Click to collapse
There is no error but I'm trying to reboot in recovery mode and it's immpossible

Captainlag said:
There is no error but I'm trying to reboot in recovery mode and it's immpossible
Click to expand...
Click to collapse
Hope You are pressing volume up button 2-3 times when Sony appears while booting the phone. Also, what ROM are You on?

Mirhawk said:
Hope You are pressing volume up button 2-3 times when Sony appears while booting the phone. Also, what ROM are You on?
Click to expand...
Click to collapse
Of course I'm pressing volume up button 2-3 times ....
My phone is on 6.2.B.1.96 stock with unlocked bootloader

Captainlag said:
Of course I'm pressing volume up button 2-3 times ....
My phone is on 6.2.B.1.96 stock with unlocked bootloader
Click to expand...
Click to collapse
I just wanted to clarify the first point since I have come across some people who didn't follow correct procedure. Glad You are doing it properly.
Ah yes, that is the problem. This method doesn't work on stock firmwares. Use the method from here to get recovery.

Mirhawk said:
I just wanted to clarify the first point since I have come across some people who didn't follow correct procedure. Glad You are doing it properly.
Ah yes, that is the problem. This method doesn't work on stock firmwares. Use the method from here to get recovery.
Click to expand...
Click to collapse
I suppose that i have to follow "method 2", right?
And what to do with the .zip file?

Captainlag said:
I suppose that i have to follow "method 2", right?
And what to do with the .zip file?
Click to expand...
Click to collapse
Method 1. You need recovery for method 2. If You have unlocked bootloader, You can simply flash the DoomKernel too. You can find it here. Use the blue "Download Now" button, and the file has .elf extension. You can flash it via flashtool, it consists of CWM and TWRP and works with stock ROM.

@Mirhawk: Many many thanks !!! :victory:
Finally , I have recovery with Doomkernel.
Thanks a lot and keep moding

I think I messed up my S
Hi
Trying to root my S and install nAOSProm I followed the instructions in the main thread. I successfully unlocked the bootloader and got the device rooted (SuperSU installed and updated in play store), but when attempting to use the TWRP manager to install TWRP I just got an error message that it wasn't successful. I then did this as I read earlier in this thread: fastboot flash boot 2.8.4.1.img. When I started the phone, it immediately boots into the TWRP but I can't get anywhere from there. Impossible to continue to the OS. When I connect it to the computer I just get an exclamation point in the device manager and I can't seem to find the correct drivers (I've installed the FlashTool Xperia Driver Pack). The phone worked perfectly in windows in both normal mode and fastboot previously. Since the phone doesn't have an external memory card, and since I can't transfer any files to it from Windows, I'm stuck in TWRP.
Is it bricked or can I get out of here?

nielsen81 said:
Hi
Trying to root my S and install nAOSProm I followed the instructions in the main thread. I successfully unlocked the bootloader and got the device rooted (SuperSU installed and updated in play store), but when attempting to use the TWRP manager to install TWRP I just got an error message that it wasn't successful. I then did this as I read earlier in this thread: fastboot flash boot 2.8.4.1.img. When I started the phone, it immediately boots into the TWRP but I can't get anywhere from there. Impossible to continue to the OS. When I connect it to the computer I just get an exclamation point in the device manager and I can't seem to find the correct drivers (I've installed the FlashTool Xperia Driver Pack). The phone worked perfectly in windows in both normal mode and fastboot previously. Since the phone doesn't have an external memory card, and since I can't transfer any files to it from Windows, I'm stuck in TWRP.
Is it bricked or can I get out of here?
Click to expand...
Click to collapse
Flash stock firmware ftf using flash mode in flashtool and then follow the instructions from here.
Or else:
Boot Your phone into recovery. Connect it to PC. Right click on the device in Device Manager, select update drivers, "browse my computer", then "let me pick from list" then select the driver similar to "Sony a0109 ADB drivers" (number may vary). Then You will be able connect to phone via adb. Then use following command to push the ROM and gapps to the phone internal memory:
Code:
adb push ROM.zip /sdcard/
adb push gapps.zip /sdcard/
This will copy the the ROM and gapps to phone which You can flash via recovery easily then.

worked perfectly! thanks for your time and help, much appreciated!

[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.