Develop Bugs

I'm stuck. I can't get root back after update to 4.3 - Tried everything

Right guys, usually I'm quite good a figuring these things out myself but this one has me stuck. I've tried loads of suggestions and I'm sure I'm doing something wrong somewhere.
Basically I've just flashed SlimBean, the Android 4.3 version. When I opened SU it says that there is no SU binary installed and that it can't install them. I researched that error message and I have tried the following.
Re-Root using Odin and CF Autroot. The process worked but I still don't have root access. (I checked that I have root enabled in the developer options)
I read that I need to flash SU v1.51 but I now don't have a custom recovery so can't flash the ZIP. I tried using ROM manager which won't work because I don't have Root access.
I decided that I need to flash a custom recovery so I downloaded one from TeamWin (the TAR/MD5 version for Odin) and tried to flash it with Odin. Unfortunately Odin detects my phone, starts file analysis, then crashes. I decided to try flashing it using Goo Manager. This said that it had worked but when I rebooted I still get the stock Android recovery
I tried to flash a CWM recovery using Odin but again it crashes. I was using Odin v3.07 but I downloaded v3.09 and it still doesn't work.
So I HAVE done some searching and tried to resolve myself but I'm stuck now. I could be missing something simple. Any ideas people?

Settings > Developer Options > Root Access then select Apps and ADB. If you can't see developer options go to about phone and tap 6x version number.
Enviado de meu GT-N7100 usando Tapatalk 4

Yes mate. That's what I meant in my original post when I said that I'd enabled root.
Thanks for trying to help though, I appreciate it.
Sent from my GT-N7100 using XDA Premium 4 mobile app

chasabi said:
Yes mate. That's what I meant in my original post when I said that I'd enabled root.
Thanks for trying to help though, I appreciate it.
Sent from my GT-N7100 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Have you tried framaroot? Not sure if it supports Note 2 but it doesn't require custom recovery afaik

xcly said:
Have you tried framaroot? Not sure if it supports Note 2 but it doesn't require custom recovery afaik
Click to expand...
Click to collapse
Never heard of that to be honest. I'll have a bit of a search and see if it will work for the Note 2.
Thanks.

xcly said:
Have you tried framaroot? Not sure if it supports Note 2 but it doesn't require custom recovery afaik
Click to expand...
Click to collapse
Problem solved. I didn't directly use Framaroot but when searching for it I stumbled across Philz Touch Recovery which actually did flash with Odin (strange why CWM or TWRP wouldn't work with Odin) so you did help indirectly
From there I flashed DrKetan_MultiTool-AromaVxx.zip and got my Root back.
Thanks

chasabi said:
Problem solved. I didn't directly use Framaroot but when searching for it I stumbled across Philz Touch Recovery which actually did flash with Odin (strange why CWM or TWRP wouldn't work with Odin) so you did help indirectly
From there I flashed DrKetan_MultiTool-AromaVxx.zip and got my Root back.
Thanks
Click to expand...
Click to collapse
I use Philz too but didn't tell you as I though there was a whole problem with custom recoveries in general :$
Glad you sorted it out though

chasabi said:
Problem solved. I didn't directly use Framaroot but when searching for it I stumbled across Philz Touch Recovery which actually did flash with Odin (strange why CWM or TWRP wouldn't work with Odin) so you did help indirectly
From there I flashed DrKetan_MultiTool-AromaVxx.zip and got my Root back.
Thanks
Click to expand...
Click to collapse
Can you tell me how you did it? I'm fairly new and don't want to brick my phone....again.
I keep having the same trouble with root access as you described and want to give Philz a try.
Thank you bunches!
Irene

One thing I have noticed myself, that unless you are Running Probam which has Super SU as it's native Root, then you will encounter this problem. Installing SuperSu on many 4.3 Roms will break root, from what I have read and tested. Use the built in superuser instead. But it is good to know that Philz works.
So until SuperSu is updated, don't use it.
---------- Post added at 06:48 PM ---------- Previous post was at 06:38 PM ----------
PrimoWorks said:
Can you tell me how you did it? I'm fairly new and don't want to brick my phone....again.
I keep having the same trouble with root access as you described and want to give Philz a try.
Thank you bunches!
Irene
Click to expand...
Click to collapse
Download Philz touch Recovery and the SuperSu and Busybox flash file. Place the SuperSu/Busybox flash file onto your phone internal or external memory card. Then open up Odin and select Philz file in the PDA section. Put your phone into download mode by holding Power, Volume Down, Home, you will see the menu asking you to go into download mode. Choose yes. Connect your phone and a yellow or blue box will show up in Odin to let you know it's connected.
Leave the boxes with tickmarks and what not. Then click Start and it will flash. It should reboot your phone.
When rebooted turn off phone. Then Hold Power, Volume up and Home button to boot into Philz recovery choose install zip file and navigate to the SuperSu/Busybox file and choose it to flash. Flash file. Optional but always a good idea, wipe cache/dalvik cache after then reboot phone.
Full instructions and files needed can be found here 2nd post:
http://forum.xda-developers.com/showthread.php?t=2032849

Hard brick resolved

I finally have everything working again. I had the phone booting via the "unbrick" SD card last night but every attempt with 2 different MJB zip files failed. I eventually just found this one http://www.androidfilehost.com/?fid=23212708291681451by @loserskater and tried it and it worked. I can boot without the SD again. I did donate to him as a thanks.
First I followed this thread (and read through Mr x's thread as well) - http://forum.xda-developers.com/showthread.php?t=2549068
I was then able to boot the phone via the special SD card.
I then kept fighting with trying to get it to boot without the SD card. Since I could get to download mode I again ran CF-autoroot and I flashed TWRP 2.6.3.0 via ODIN. I kept booting to recovery and could not get either MJB bootloader that I found to work. I did get a status 6 when I tried CWM which indicated a syntax error or formatting error. I eventually found the zip file below and that worked via TWRP and then I was set.
I hope I remember everything - I was up until 4am and then didn't get a lot of sleep so I'm a little "fuzzy" now...
I will try to clean this up later for other's reference.
Edit 4: I can now get to TWRP by booting via an SD card with the unbrick file. I can also get into download mode. I tried flashing the MJB bootloader zip file via TWRP but it keeps failing. What is the next step to correct the bootloader problem if I had MJB and flashed the MJ2 bootloader (yes that was dumb...). How can I get the MJB bootloader files onto the EMMC again?
Help! I have flashed custom ROMs hundreds of times on my Captivate, Note, and Note2. My wife's S3 has been stock and had the OTA 4.3 update. After a few attempts, I did get root and TWRP 2.6.3.0 installed. I installed this ROM http://forum.xda-developers.com/showthread.php?t=2075639- was able to update SU and restored user some apps via TB. The "about device" still showed "enforcing and she had the MJB bootloader. I rebooted to recovery and again ran the "Knox removal script" which I had run a few times already. This time I ran it and then flashed the MJ2 bootloader from the OP. I can't get it to turn on now. I pulled the battery - no luck. I plug it into my laptop and I hear the sound of windows recognizing the device but it doesn't show up. If I leave the battery out and plug into the PC, then the red LED flashes. If it was my device I would be bummed but being my wife's phone, I really am hoping someone can help...
Edit: I have been trying the 3 button recovery and download options with no luck.
During my captivate days, I used a "JIG" for getting into download mode but am concerned even that won't help if there is a bootloader mismatch or something like that.
Edit2: Even though I have a black screen, I tried using ODIN and connected the phone and it says "added"! I will now look for a full bootloader flash via ODIN
Edit3: It seems like if I have the battery removed, hold the vol. down and home and then plug in the cable, ODIN recognizes it so I have a ray of hope but am still a bit "panicked". I am looking for a full MJB firmware flash via ODIN

Did you try and reboot into recovery (not download) and flash the MJB bootloader??? that is what worked for me.
Sent from my SAMSUNG-SGH-I747 using Tapatalk

lfaulkner29 said:
Did you try and reboot into recovery (not download) and flash the MJB bootloader??? that is what worked for me.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
That is what I have tried multiple times but it keeps saying failed. Can you send me a link to the exact zip file you used? Did you do anything such as flashing anything right before (supersu update), etc? I am very hopeful now knowing that you were able to get it to work.
Edit: I have a couple of .zip files that are supposed to apply the MJB bootloader files. One of them @loserskater posted comes up with a status 6 which I am researching now.
What recovery did you use TWRP or CWM? I've been trying both.

RichMD said:
That is what I have tried multiple times but it keeps saying failed. Can you send me a link to the exact zip file you used? Did you do anything such as flashing anything right before (supersu update), etc? I am very hopeful now knowing that you were able to get it to work.
Edit: I have a couple of .zip files that are supposed to apply the MJB bootloader files. One of them @loserskater posted comes up with a status 6 which I am researching now.
What recovery did you use TWRP or CWM? I've been trying both.
Click to expand...
Click to collapse
Updated the OP - resolved with the file I used.

RichMD said:
Updated the OP - resolved with the file I used.
Click to expand...
Click to collapse
what did you use to flash it?

Michael503 said:
what did you use to flash it?
Click to expand...
Click to collapse
I updated the OP with a link to the file.
Sent from my SAMSUNG-SGH-I317 using Tapatalk

RichMD said:
I updated the OP with a link to the file.
Sent from my SAMSUNG-SGH-I317 using Tapatalk
Click to expand...
Click to collapse
no, I mean what procedure.. did you finally get the file to go with TWRP?
I assume thats what you did, but I wanted to be sure. The procedure aught to be a sticky.

Michael503 said:
no, I mean what procedure.. did you finally get the file to go with TWRP?
I assume thats what you did, but I wanted to be sure. The procedure aught to be a sticky.
Click to expand...
Click to collapse
I just updated the OP with a bit more info. Let me know if that is the info you were looking for. As I mentioned, I am over-tired right now...

RichMD said:
As I mentioned, I am over-tired right now...
Click to expand...
Click to collapse
yeah, I'll bet.. stress is a *****... glad you got it licked though
Thx.

Need help unbricking T-mobile N900TUVUBMI7

Hello everyone,
For the longest time I had just had my note 3 rooted with chainfire. Being familiar with modding androids I decided to give it a go on my note 3. As you can see from the title, I failed lol.
I've tried to use any tar.md5 I can find of the T-mobile US version; but most come up with md5 check failed. The only one i've gotten to work on the many odin versions i've tried is N900TUVUDNF4_N900TTMBDNF4_N900TUVUDNF4_HOME.tar.md5.
The phones state is it currently freezes loading on the samsung logo screen. I was able to install twrp custom recovery version 2.6.3.2. Before I installed the rom I was trying "X-note", I did a backup of the system. Though when I use the restore, it only does the boot and system files. The data fails everytime I try.
Before all this I was in 4.3.
If you guys could help me out, and point me in the right direction to at least get my phone working I'd appreciate it.

re: md5 error
Silvist said:
Hello everyone,
For the longest time I had just had my note 3 rooted with chainfire. Being familiar with modding androids I decided to give it a go on my note 3. As you can see from the title, I failed lol.
I've tried to use any tar.md5 I can find of the T-mobile US version; but most come up with md5 check failed. The only one i've gotten to work on the many odin versions i've tried is N900TUVUDNF4_N900TTMBDNF4_N900TUVUDNF4_HOME.tar.md5.
The phones state is it currently freezes loading on the samsung logo screen. I was able to install twrp custom recovery version 2.6.3.2. Before I installed the rom I was trying "X-note", I did a backup of the system. Though when I use the restore, it only does the boot and system files. The data fails everytime I try.
Before all this I was in 4.3.
If you guys could help me out, and point me in the right direction to at least get my phone working I'd appreciate it.
Click to expand...
Click to collapse
Before doing anything else you need to re-download the TAR.MD5 firmware.
If you get MD5 errors it simply means that for some reason the download
had an error in it (checksum error).
You need to have a error free download of the TAR.MD5 firmware in order
to solve the issues you are having. Your phone is NOT bricked at all and all
it needs is a error free TAR.MD5 file to flash with odin and your phone will
work perfectly. You should never flash a TAR.MD5 file which has errors.
Your problem has nothing to do with the versions of the firmwares like 4.4.2
and or 4.3 you are trying to flash, it all has to do with errors during the actual
download process of the TAR.MD5 file.
Good luck!

Thank you for replying!
So what should I look for in terms of flashing then? Just full stock of the t-mobile US version?
Reason I asked is because I'd downloaded about 15 different ones from all different sources, and only that one didn't have the issue. Should I try to flash through twrp over Odin?
Edit:
Like for instance I tried the one from here:
http://forum.xda-developers.com/not...900tuvudnf4-extracted-stock-firmware-t2834398
This was the only one that worked actually. Though after I flash it with odin it just shows the samsung logo with "recovery booting" in the top left corner.
Wow..holy crap after like attempt number 40 with the same flashing in odin it actually booted up. That's just crazy lol.

Call me to un brick your phone
HEY CALL ME TO UNBRICK YOUR PHONE AM A REPAIR SHOP IF YOU MAIL ME THE PHONE I COULD FIX IT FOR A SMALL FEE [email protected] HAVE A GOOS DAY :fingers-crossed:
Silvist said:
Hello everyone,
For the longest time I had just had my note 3 rooted with chainfire. Being familiar with modding androids I decided to give it a go on my note 3. As you can see from the title, I failed lol.
I've tried to use any tar.md5 I can find of the T-mobile US version; but most come up with md5 check failed. The only one i've gotten to work on the many odin versions i've tried is N900TUVUDNF4_N900TTMBDNF4_N900TUVUDNF4_HOME.tar.md5.
The phones state is it currently freezes loading on the samsung logo screen. I was able to install twrp custom recovery version 2.6.3.2. Before I installed the rom I was trying "X-note", I did a backup of the system. Though when I use the restore, it only does the boot and system files. The data fails everytime I try.
Before all this I was in 4.3.
If you guys could help me out, and point me in the right direction to at least get my phone working I'd appreciate it.
Click to expand...
Click to collapse

For anyone else with this problem: I had this problem I flashed the firmware a few times talked about earlier. Then I performed a factory reset through recovery and boom it works again. Maybe that's all I needed to do in the first place maybe odin wasn't even necessary... This may also work with other cf auto-root bricks across many phones.
---------- Post added at 06:18 PM ---------- Previous post was at 06:10 PM ----------
blu422 said:
For anyone else with this problem: I had this problem I flashed the firmware a few times talked about earlier. Then I performed a factory reset through recovery and boom it works again. Maybe that's all I needed to do in the first place maybe odin wasn't even necessary... This may also work with other cf auto-root bricks across many phones.
Click to expand...
Click to collapse
Scratch that. This is what I believe happened. The way CF Auto-root works is it roots through a temporary custom recovery I believe. What happened is during the process something went wrong and the phone ended up with both a corrupted system and a corrupted recovery. You need to flash the stock tar to fix both then factory reset to make it boot the rest of the way. Again this is just for future reference with more people running into this problem... I do realize OP already got helped.

blu422 said:
For anyone else with this problem: I had this problem I flashed the firmware a few times talked about earlier. Then I performed a factory reset through recovery and boom it works again. Maybe that's all I needed to do in the first place maybe odin wasn't even necessary... This may also work with other cf auto-root bricks across many phones.
---------- Post added at 06:18 PM ---------- Previous post was at 06:10 PM ----------
Scratch that. This is what I believe happened. The way CF Auto-root works is it roots through a temporary custom recovery I believe. What happened is during the process something went wrong and the phone ended up with both a corrupted system and a corrupted recovery. You need to flash the stock tar to fix both then factory reset to make it boot the rest of the way. Again this is just for future reference with more people running into this problem... I do realize OP already got helped.
Click to expand...
Click to collapse
I always ODIN flash the newest firmware, let the phone boot up, then I just ODIN flash TWRP... and then in recovery I flash my personnel rom and flash SU from chainfire...
then I just install busybox which I have a copy of all the on my sdcard, a folder I call apk files.... then I install titanium backup and restore my apps.. all done in less then 10 minutes...
when ever u think u have a problem, flash the firmware your on, or the newest, that should always fix any issues.. I have all of the versions on my site, and stock odex roms...

Silvist said:
Thank you for replying!
So what should I look for in terms of flashing then? Just full stock of the t-mobile US version?
Reason I asked is because I'd downloaded about 15 different ones from all different sources, and only that one didn't have the issue. Should I try to flash through twrp over Odin?
Edit:
Like for instance I tried the one from here:
http://forum.xda-developers.com/not...900tuvudnf4-extracted-stock-firmware-t2834398
This was the only one that worked actually. Though after I flash it with odin it just shows the samsung logo with "recovery booting" in the top left corner.
Wow..holy crap after like attempt number 40 with the same flashing in odin it actually booted up. That's just crazy lol.
Click to expand...
Click to collapse
I'm actually having this exact issue how exactly did you fix it? mine just says booting recovery and then it loops and I've downloaded at least 4 different versions of the nf9 odin

xxjahasotoxx said:
I'm actually having this exact issue how exactly did you fix it? mine just says booting recovery and then it loops and I've downloaded at least 4 different versions of the nf9 odin
Click to expand...
Click to collapse
I just kept trying to flash to the stock image that's in the link in my post. It kept giving me md5 errors, so I re downloaded the file until it passed. I also ran odin as administrator, which helps. I used an older version of odin, 3.5 I believe.
Everything else I tried failed, like hemdall. I did attempt it, but it failed when I tried to flash through it. I'm not really familiar with it, just followed the guide on these forums. It can supposedly do more than even odin can do, that's if you can get it to work lol.

Screwed up trying to root, stuck in bootloop

So, I've got a 64gb black sprint Galaxy S6, non-edge. This morning, it had stock 5.11 on it, but I decided I wanted to root it, and ... I screwed up. I got Odin 3.10.6 and installed CF-Auto-Root-zerofltespr-zerofltespr-smg920p.tar.md5 which I now know does not work with 5.11. Since then, bootloop. Reboots every minute or so. I've tried everything I can find, wiping everything, flashing what purport to be stock ROMs, putting TWRP on there, and still within a minute of booting it reboots. I tried installing Smart Switch, but it can't get a connection because the phone just won't stay booted.
Rooting would be nice, but I just want my phone to work again. What can I do here? I don't have insurance and KNOX is flipped.

if you're sure you are on 5.1.1, flash any kernel (unikernel v8, etc.) that would fix your issue.

I should mention this is a SM-G920P, if that's significant.
I flashed the stock package through Odin, then TWRP, then installed Hacker Kernel through that. It's still rebooting repeatedly while i try to go through the initial setup process, and dumping me at the language select each time.
I tried unikernel too, didn't work either.

Okay, here's my current process, which is not working.
Boot to ODIN/Download mode, by holding power+volume down+home.
Open Odin 3.10.6, as administrator. Auto-Reboot is unchecked.
Flash what's supposed to be the latest stock rom, obtained here.
Wait until it says PASS, then reboot into ODIN mode again.
Flash the TWRP 2.8.7.0 tar, obtained here.
Wait until it says PASS, then reboot into recovery, by holding power+volume down+home until it reboots and then power+volume up+home to enter recovery.
Wipe Data/Cache/Darvik.
Transfer Hacker Kernel and SuperSU .zips, obtained here, to storage on phone.
Use TWRP to install Hacker Kernel, as instructed on that page.
Reboot into recovery.
Use TWRP to install Super SU. Note: In the section of the log reading Boot Image Patcher, I get Extracting ramdisk, Decompressing ramdisk, Failure, aborting. Important?
Reboot.
Now it's sitting on the Samsung Galaxy S6 screen, and not going any farther than that.

I tried flashing nothing but the stock 5.1.1 package, but that's not working either. It still keeps rebooting, and it won't ever get past the screen that says "Preparing your device for first-time use... This may take 3 or 4 minutes." Is there anything I can do? I can't afford to not have a phone and I can't afford to replace this one. Please, help me.

I've redownloaded everything, checking md5 sums, and those are all correct. Flashing the BOL1 stock gets me rebooting, flashing it and then Unikernel v8 gets me rebooting, flashing it and then Unikernel v9 gets me rebooting, flashing it and then Unikernel v9 and then TWRP has me rebooting.
It boots up and stays up for a minute or two, enough to get a little ways into the setup. The first boot, it stays on the Sprint screen for a while, then reboots after about a second on the language select screen. When it gets back there, I can select language, connect to wifi, accept the EULA, and then wait on the "Preparing your device for first-time use" screen for a little while before it reboots. Sometimes it'll get as far as asking me if I want to let Google collect diagnostic data.

Hardware issue...i had the same issue with similar process. I had to get a replacement phone

Is it possible that trying to install the Chainfire root package on a 5.11 phone just broke something permanently? Could it be something partition-related, maybe? I'm at a total loss here.

This should help
kafziel83 said:
Is it possible that trying to install the Chainfire root package on a 5.11 phone just broke something permanently? Could it be something partition-related, maybe? I'm at a total loss here.
Click to expand...
Click to collapse
I had the same issue also with the SM-G920P.
Problems:
*unikernal > v6 (v7 and above == bootloop)
*hackerkernal on non-teamsprint rom == bootloop
*cf auto root was not required for root
What fixed it for me:
1. Odin back to stock 5.1.1
2. Flash TWRP
3. Boot into recovery
4. Reboot (it should tell you that root is not installed or something like that, so if it asks to install root let it)
5. Once booted into os SuperSU will tell you to update the su binary, update then reboot
6. Congratulations you have root.

lodbldbol said:
I had the same issue also with the SM-G920P.
Problems:
*unikernal > v6 (v7 and above == bootloop)
*hackerkernal on non-teamsprint rom == bootloop
*cf auto root was not required for root
What fixed it for me:
1. Odin back to stock 5.1.1
2. Flash TWRP
3. Boot into recovery
4. Reboot (it should tell you that root is not installed or something like that, so if it asks to install root let it)
5. Once booted into os SuperSU will tell you to update the su binary, update then reboot
6. Congratulations you have root.
Click to expand...
Click to collapse
Did 1, did 2, did 3, did 4 but it didn't give any message like that, and now it's just repeating the "Samsung Galaxy S6 Powered By Android" screen over and over.
Unless when you say "Odin back to stock 5.1.1" you mean flashing 5.1.1 and then going through the setup to a functioning OS, because I have never been able to do that since I started.

kafziel83 said:
Did 1, did 2, did 3, did 4 but it didn't give any message like that, and now it's just repeating the "Samsung Galaxy S6 Powered By Android" screen over and over.
Unless when you say "Odin back to stock 5.1.1" you mean flashing 5.1.1 and then going through the setup to a functioning OS, because I have never been able to do that since I started.
Click to expand...
Click to collapse
To Odin back to stock 5.1.1 properly follow the steps on this page exactly with the files it tells you to use http://www.androidrootz.com/2015/05/how-to-unroot-galaxy-s6-and-s6-edge.html
Then you'll need a ROM, i recommend this http://forum.xda-developers.com/spr...ment/ram9200-ofe-rom-thread-v3-5-1-1-t3173417
Once in recovery flash it (skip to step 7 in the link) then boot up, if that doesn't work I don't know what will.

Tried that, now it boots as far as the Sprint screen but hangs there and then reboots.

kafziel83 said:
Tried that, now it boots as far as the Sprint screen but hangs there and then reboots.
Click to expand...
Click to collapse
Hardware issue

Any advice on getting a replacement? I still have about $500 left on the monthly installments for this phone, and I don't have insurance. The Sprint stores I went to said to go to Samsung for a replacement for a malfunctioning phone, since I've had it for less than a year, since KNOX is flipped I'm guessing Samsung won't give me a thing.

I uploaded a file to Mediafire called 2016-03-20--04-15-35_G920P_Renegade_OJ7_v1.zip
This is a TWRP backup of my phone's system/radio/boot/efs, it should replace anything that doesn't work. I don't know if it'll work but it's worth a try.
Copy the zipped folder to TWRP/BACKUPS and restore your phone

Okay. Can you link to the mediafire page to download it?

kafziel83 said:
Okay. Can you link to the mediafire page to download it?
Click to expand...
Click to collapse
No, XDA won't let me put links to outside websites until I have 10 posts.

Same Problem
kafziel83 said:
Okay. Can you link to the mediafire page to download it?
Click to expand...
Click to collapse
Hi,
Same problem here,
Did you find a solution for your problem?

lodbldbol said:
I uploaded a file to Mediafire called 2016-03-20--04-15-35_G920P_Renegade_OJ7_v1.zip
This is a TWRP backup of my phone's system/radio/boot/efs, it should replace anything that doesn't work. I don't know if it'll work but it's worth a try.
Copy the zipped folder to TWRP/BACKUPS and restore your phone
Click to expand...
Click to collapse
If ever the EFS is cleared, deleted whatever. It re-builds from block 12, so there's no need to worry too much.
Sent from my SM-G925P using XDA Labs
---------- Post added at 10:12 AM ---------- Previous post was at 10:09 AM ----------
kbashiri said:
Hi,
Same problem here,
Did you find a solution for your problem?
Click to expand...
Click to collapse
I would do a quick repartition, nand erase all, flash stock ROM boot it, and flash from there. Hope it goes well.
Sent from my SM-G925P using XDA Labs

Please Help
ChubbbySquish said:
If ever the EFS is cleared, deleted whatever. It re-builds from block 12, so there's no need to worry too much.
Sent from my SM-G925P using XDA Labs
---------- Post added at 10:12 AM ---------- Previous post was at 10:09 AM ----------
I would do a quick repartition, nand erase all, flash stock ROM boot it, and flash from there. Hope it goes well.
Sent from my SM-G925P using XDA Labs
Click to expand...
Click to collapse
Should I do re-partition then nand erase all and then flash rom or should I do them altogether?

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