Develop Bugs

[SOLVED]Koodo Stock Recovery found!

GO TO THE POST BELOW FOR THE RECOVERY AND INFO. PLEASE THANK HIM
CLICK ME FOR POST.
This is his topic full of stock recoveries and what-not
--------------------
Bear in mind that I do not have the time to restore to stock, and then check it for myself if you can extract the stock recovery without root, but you probably can. Please refer to the quote I will post below as I have little time to clean this post up.
Please thank user Davy Jones for actually finding the solution!
Davy Jones said:
Okay, I don't know any coding so I apologize if this is a dumb suggestion, but is it possible to follow the article's directions to pull recovery? So from shell:
dd if=/dev/block/mmcblk0p22 of=/sdcard/recovery.img bs=4096
I'm already on cwm so I have no way of testing this. Also, please don't try this unless you know what you are doing. I tried this on cwm and it created a file that was 10MB instead of the .img I originally flashed, which was 5.98MB.
Click to expand...
Click to collapse
My post starts here
-------------------------------------------
Alrighty that's wonderful. I am trying a guide right now and I will see if I am successful at extracting a recovery and I will report back.
EDIT
I've made wonderful process, and I've extracted a 10mb file which what the recovery.img supposed to be resized to.
So i've basically typed in
After this, I got a huge list of the partitions, and using this I've confirmed that mmcblk0p22 is the block that contains the recovery (I also made sure that I didn't extract something else, etc by checking what the userdata and sdcard size is supposed to be?
Then I typed in
and got
So I ended up with a 10MB file sitting in the root of my internal memory (known as sdcard)
Now I will try to confirm if it is the same file as my recovery.
EDIT
Well after more digging around.. I found this and where it says "Download - Recovery Image Method (using dd):" It shows that the block which the recovery is in in actually the same as the one above, so there was an easier way. Oh well! At least we confirmed that we have the correct file, the question is, can we flash it, guess I'll try after I get home.
If you want to try this out on a NON-Rooted one, you'll have to go to Settings>Developer Options>Root access and allow ADB.
-----------------------------------------------
Quote ends here.
Hopefully you're a Koodo owner reading this and have noticed the title.
Many of us Koodo owners, have rooted, installed a custom recovery, and have started the flashing frenzy, but we have forgot one thing.
No its not making a NAND of the stock ROM, its the fact the we forgot to backup our stock recoveries! I know it might not be a difference compared to the Telus recovery, but we still need to be sure, that when we want to update, or if we want to return the phone, what we are fully stock.
So what I'm asking you, is to make a backup of your Koodo stock recovery, and share it with us
Unfortunately I do not know how to extract a recovery.img. So hopefully an XDA member will post a guide in this to help us extract the .img
or as always, Google is your best friend
Cheers, and thanks
EDIT
Koragg618 said:
I have found a link on how to get it
http://www.addictivetips.com/mobile...es-boot-recovery-and-system-partition-images/
Download link for RomDump is at the end of the article
Click to expand...
Click to collapse
Those are the instructions.
Thanks everyone for contributing!

I have a stock phone still but need a guide on pulling my recovery. Would I just use ADB or?...

chevymeister said:
I have a stock phone still but need a guide on pulling my recovery. Would I just use ADB or?...
Click to expand...
Click to collapse
Im not a koodo member but is it not the same way for tmobile users? With stock ODIN flash? when I ODIN flash my t989 to stock it also flash the stock recovery

I have found a link on how to get it
http://www.addictivetips.com/mobile...es-boot-recovery-and-system-partition-images/
Download link for RomDump is at the end of the article

Bump, since no one is really noticing the pinned topic

Koragg618 said:
Bump, since no one is really noticing the pinned topic
Click to expand...
Click to collapse
I could help, Ive got a Koodo S2 X. However, its not rooted, would i still be able to make a backup of my stock recovery.

Yes I believe it is still possible, just make sure Debugging mode is on and you are using the ADB method, and not the one that has the Android Terminal one. Thanks

My friend and my girlfriend both have Stock Koodo Phone... so i'm gonne try to bring the original Koodo Recovery.img. I read the articles from addictive tips... but i think i missed something, They said we need to root the phone but the first step in the method to root the phone is to install CWM recovery IMG via Odin... So it will overwrite Koodo original Recovery.img.... before i extract it...
Any clue or hint ???
Maybe another way to root via ADB ???

I have a Koodo T989D still on stock everything. I want to root my phone and do all this fancy stuff on it but I'm not in a hurry. I can make a copy of my stock recovery if I get the proper instructions.
edit: isn't this what you're looking for anyway?? http://forum.xda-developers.com/showthread.php?t=1849748

tazmania12345 said:
I have a Koodo T989D still on stock everything. I want to root my phone and do all this fancy stuff on it but I'm not in a hurry. I can make a copy of my stock recovery if I get the proper instructions.
edit: isn't this what you're looking for anyway?? http://forum.xda-developers.com/showthread.php?t=1849748
Click to expand...
Click to collapse
No. What you're pointing to us is a custom Rom... Based on the Stock Koodo Rom. What we are looking for is the Stock Recovery... Just to put back the entire phone in original condition if you have to bring it back to manufacturer for repair...

Tornade69 said:
No. What you're pointing to us is a custom Rom... Based on the Stock Koodo Rom. What we are looking for is the Stock Recovery... Just to put back the entire phone in original condition if you have to bring it back to manufacturer for repair...
Click to expand...
Click to collapse
Oh i see... I'm still on stock 4.0.4 so i'll definitely try to provide the backup. Like i said, i'd need the proper instructions because i'm new to all of this.

Someone previously posted the stock recovery which I have attached. Use at your own risk since I have not tested it!

Amazing, where did you find this!

Koragg618 said:
Amazing, where did you find this!
Click to expand...
Click to collapse
Someone previously posted it few weeks ago on the XDA forums in the device dev section and I had downloaded and kept a copy in case I needed it.

jumran said:
Someone previously posted it few weeks ago on the XDA forums in the device dev section and I had downloaded and kept a copy in case I needed it.
Click to expand...
Click to collapse
Thanks! This will come in handy.

Sorry to be the bad news but I believe this recovery is the one that I've packaged before I though I've found the TLLG2 stock recovery from this site page 68( post by netusername and uploading it without testing it 1st.... then later installed/tested it and it was a CWM touch recovery and not the TLLG2 stock recovery, Sorry again.
Source:
User:netusername
KOODO STOCK IMAGE/RESTORE
Directions: Download these three in the same folder - Part 1, Part 2, Part 3
Use Winrar/7zip to only extract Part 1 after you have all three parts in the same folder. You should get a folder called clockworkmod. There should be another folder called "backup" inside.
Put the "clockwordmod" folder in your sd card.
Use clockwordmod to restore after factory reset, wipe system, wipe dalvik cache.... It is recommended that you use Clockwordmod 6 - it can be found here - http://forum.xda-developers.com/show....php?t=1823117
Enjoy!
Click to expand...
Click to collapse
Sent from my ♛ SGH-T989 ♛ using XDA app.

Oh well thats confusing Thanks for the info man!

Sorry I'm not following.
Do you mean the post by jumran (http://forum.xda-developers.com/showpost.php?p=32299219&postcount=12) is not the stock recovery and is actually a CWM recovery that you're mentioning?
KRZ-2pa said:
Sorry to be the bad news but I believe this recovery is the one that I've packaged before I though I've found the TLLG2 stock recovery from this site page 68( post by netusername and uploading it without testing it 1st.... then later installed/tested it and it was a CWM touch recovery and not the TLLG2 stock recovery, Sorry again.
Source:
Sent from my ♛ SGH-T989 ♛ using XDA app.
Click to expand...
Click to collapse

Yes it is a CMW Touch recovery and no problem

[curious] What are you guys doing? [/curious]
You realize backing up any part of your original stock ROM is pointless? All you have to do pick up the original stock tarball from Samsung's website, fire up ODIN, flash, and then not even Samsung can tell you ever did something to your phone. It will be stock everything: radio, recovery, ROM...
---------- Post added at 08:41 PM ---------- Previous post was at 08:31 PM ----------
Here, follow the instructions: http://fus.nanzen.se/
There are no presets for Koodo, but all the information you need is readily available on the original box your phones came in.
And if you really need the Koodo recovery for whatever reason, it is an IMG file inside the TARball. You can just DD it in place.

[Q] Problem With latest Firmware update oct 12

I am new here and would like to ask this question and I sure hope you can help.
So here is the story I work in IT I am very saving but never got the chance to root my phone because I didn't want to brick it. But now I am tired of waiting for jelly bean update for my T-mobile Samsung GS3. I watch all the videos on how to go into download mode and use Odin v1.85 to install a rom(I think that's what it does sorry if it's not correct I am a noob when it comes to this) Any way when I tried to install it everything passed and everything seemed ok. But when it rebooted it wasn't rooted and I didn't understand why so when I went back into download mode to see if I did something wrong. When I went back into it I found out something that I am pissed about. With the latest firmware update(please excuse if this is wrong but i think I am right) It says Qualcomm secureboot: Enable Does this mean they have locked the boot loader so I cannot root or put a custom rom on my GS3?
If you could please tell me what that means it would be great. I have uploaded a screen shot if anybody wants to see it. Is there a way around this?

You most likey flashed a non rooted firmware usually odin firmware isnt rooted unless someone linked u to a firmware with root injected right into it..are u on fw lj4 or lh2?? Either way there are very easy and safe ways to root..let me know if u want me to link u anything.
Also the bootloader is not locked there is no need to worry.. just odin flash clockwork.tar and then from there u can flash root and bingo!
Sent from my SGH-T999 using xda app-developers app

Five10legacy said:
I am new here and would like to ask this question and I sure hope you can help.
So here is the story I work in IT I am very saving but never got the chance to root my phone because I didn't want to brick it. But now I am tired of waiting for jelly bean update for my T-mobile Samsung GS3. I watch all the videos on how to go into download mode and use Odin v1.85 to install a rom(I think that's what it does sorry if it's not correct I am a noob when it comes to this) Any way when I tried to install it everything passed and everything seemed ok. But when it rebooted it wasn't rooted and I didn't understand why so when I went back into download mode to see if I did something wrong. When I went back into it I found out something that I am pissed about. With the latest firmware update(please excuse if this is wrong but i think I am right) It says Qualcomm secureboot: Enable Does this mean they have locked the boot loader so I cannot root or put a custom rom on my GS3?
If you could please tell me what that means it would be great. I have uploaded a screen shot if anybody wants to see it. Is there a way around this?
Click to expand...
Click to collapse
I 100% understand where you are coming from I'm in IT also:
Lets get to it then, shall we?
So first make sure the drivers are installed for your T-Mobile S3 (drivers link): http://www.samsung.com/us/support/owners/product/SGH-T999MBATMB
Next, download Odin v3.40: http://forum.xda-developers.com/showthread.php?t=1670973
Then, get all the files at this link, they contain the Odin version if you dont want to install it using the link above^, clockworkmod.tar & a SuperSU program to flash to get super user permissions & be officially rooted.
When you run ODIN, right click it & select Run from Administrator. Now click the PDA button & browse for the clockworkmod.tar & click start, it'll flash the recovery & auto reboot
Then to flash the SuperSU, reboot into recovery (i believe u hold down the volume down button, home button & power at the same time, if not then its the volume up button instead of the down button)
U should be in Clockworkmod now, click install zip from file, then choose zip from file, then navigate to the SuperSU program that you put on your INTERNAL memory (not external, which is your SD card), flash it & reboot.
Your officially rooted
by the way, let me know what rom you choose! Im between 2 right now, Frosty 4.1.1 v6 & XquizIT v33 (LIH/LI8)

Thanks both of you. I will try the links you sent me @svibrant67. I was just worried that they locked the boot loader and now I know its not so I am relived. When I follow these steps will it install Rom manager so I can make a nandroid backup? I just want to make sure I can get it back to stock just in case I have to get a warranty repair on it.

Five10legacy said:
Thanks both of you. I will try the links you sent me @svibrant67. I was just worried that they locked the boot loader and now I know its not so I am relived. When I follow these steps will it install Rom manager so I can make a nandroid backup? I just want to make sure I can get it back to stock just in case I have to get a warranty repair on it.
Click to expand...
Click to collapse
Once you flash clockworkmod.tar & your phone reboots, put it into clockworkmod recovery & from their before you flash anything else, nivigate to backup/restore, then backup & it'll make a nandroid .

Thanks for the Information I am currently running FrostyJB_4.1.1-v6 with kernel KT747 and modem UVLI7. This thing flies now. The only problem I am having is sometimes wifi calling stops but I bet it is mostly because the Offical JB rom isn't out yet. Also everytime I restart my phone it switches back to default keyboard and doesn't keep my Swiftkey as default. But besides that I am very happy. Thanks again for replying so fast.

[Solved] [Q] SGH-T999 Rooted bad, phone stuck on start screen

Hello xda,
I tried rooting my SGH-T999 and it took a while so I unplugged the USB and restarted the phone. Phone keeps saying it has encountered a problem with the current firmware, connect to KIES and select recovery. Kies does not connect to the device. I read on xda to reflash using ODIN. I have ODIN v1.85 from trying to root, is this the right version to use because I also found the ODIN3_v3.07? As far as USB driver, is there separate drivers for ODIN or are people referring to the Samsung Kies drivers (I just installed KIES). I read to do it on this screen and I also read to try to go into the recovery mode (holding vol down, home, power) and then reflashing; which should I do?
Also, I found this link on xda for the T-mobile firmware ( http://forum.xda-developers.com/showthread.php?t=1949687 ). No idea which one to choose, why are there so many, I am currently downloading the latest one
"UVDLJA
PDA: T999UVDLJA
CSC: T999TMBDLJA
Version: 4.1.1 JB
Date: Nov. 14, 2012
Sammobile Link
Samsung-Updates Link"
If I want to use the pre rooted file do I need to fix my problem first and try flashing with stock firmware or can I try to fix the issue directly with the pre rooted firmware?

Re: [Q] SGH-T999 Rooted bad, phone stuck on start screen
Use the Odin from my signature.
You can probably just flash mrRobinson's stock rooted rom to fix it. And Kies is garbage. Uninstall it.
I would like to see the root guide you used as well.

Aerowinder said:
Use the Odin from my signature.
You can probably just flash mrRobinson's stock rooted rom to fix it. And Kies is garbage. Uninstall it.
I would like to see the root guide you used as well.
Click to expand...
Click to collapse
I used this guide to root.
http://galaxys3root.com/galaxy-s3-r...gh-t999sgh-i747sph-l710-fail-proofnoob-proof/
Before I try to flash with mrRobinson's stock rooted rom which I just finished downloading, I will uninstall Kies and install the USB drivers first?
Thanks for your response Aerowinder.
I got USB drivers earlier today that was a newer version but I will be using the files from your sig since it works :good:
Another question I had was, does the phone need to be in download mode or can I do it in the screen where it says "encountered problem with current firmware. Connect to KIES and select recovery" screen when I flash with Odin? I know normally I would have to be in the download mode but I'm wondering if it is the same when I am getting this error.

Re: [Q] SGH-T999 Rooted bad, phone stuck on start screen
Phone must be in download mode to use Odin.
The drivers in my signature are not the newest, you are correct. They are the last version I found that work without any issues. The newer ones pretty much suck. Constant disconnects mainly.

Aerowinder said:
Phone must be in download mode to use Odin.
The drivers in my signature are not the newest, you are correct. They are the last version I found that work without any issues. The newer ones pretty much suck. Constant disconnects mainly.
Click to expand...
Click to collapse
Awesome thanks!
So I am watching the root video on your sig, so in my case I would choose the rom I want for the PDA instead of the cwm-touch-6.0.2.3-d2tmo right? Should I extract the rooted firmware or just load the zipped file onto ODIN PDA?

Re: [Q] SGH-T999 Rooted bad, phone stuck on start screen
Root66 does not contain a recovery so you still need to flash one of those but don't use my link. Get ROM Manager once you're up and running.
If you don't care about the flash counter you can flash the tar in my signature.

Sorry to interject here but you can get an Odin flashable recovery from here.
You can flash one of these and then flash Root66 right after and you'll have stock Rooted ROM with stock or custom recovery (your choice).
Not to be a buzzkill or anything but you are probably the 5th or 6th person in the past 2 weeks that have encountered the "encountered problem with current firmware. Connect to KIES and select recovery" error. Only a few of them have been able to pull out of it. The ones that have, have had to flash Root66 (or their device respective FW) multiple times.
I hope that you can get out of it and please post here if you do. Aerowinder knows what he is doing. Follow his lead.

Aerowinder said:
Root66 does not contain a recovery so you still need to flash one of those but don't use my link. Get ROM Manager once you're up and running.
If you don't care about the flash counter you can flash the tar in my signature.
Click to expand...
Click to collapse
Okay I don't care about the counter, I just want my phone to work and I'll be happy.
But now I'm getting a little confused about the cwm recovery.
So just to be clear, you are saying I need to flash a recovery (cwm-touch-6.0.2.3-d2tmo in my case since I don't care about the counter), BUT do I flash the recovery before or after I flash with Root66 firmware? That part I am confused about. And do I flash one right after another or do I need to restart my phone or ODIN first?
Thank you so much for helping me out. I was freaking out this morning and I am very grateful for your help and knowledge. I hope I am not being too much of a pain or hassle with these questions. Sorry that I am quite new to this

Woody said:
Sorry to interject here but you can get an Odin flashable recovery from here.
You can flash one of these and then flash Root66 right after and you'll have stock Rooted ROM with stock or custom recovery (your choice).
Not to be a buzzkill or anything but you are probably the 5th or 6th person in the past 2 weeks that have encountered the "encountered problem with current firmware. Connect to KIES and select recovery" error. Only a few of them have been able to pull out of it. The ones that have, have had to flash Root66 (or their device respective FW) multiple times.
I hope that you can get out of it and please post here if you do. Aerowinder knows what he is doing. Follow his lead.
Click to expand...
Click to collapse
Woody, I went to the link you posted. What are the 4 files for?

Don't use those - they are older versions.
If you don't care about the counter, then flash the CWM in my signature using Odin (can provide TWRP tar link if that's your thing), then flash root66 using Odin. You can reboot in between... but no real reason to do so.
If you are still having issues after you flash these, drop into recovery (vol up + home) and reset factory defaults. If still having problems, only thing left to do is flash a full stock image, link also in my signature. The page you linked to does not contain the newest version because DocHolliday hasn't been around here much lately.

buzzking00 said:
Woody, I went to the link you posted. What are the 4 files for?
Click to expand...
Click to collapse
Top one is TWRP version 2.3.0.0
Second is 6.0.1.2 CWR touch version
Third is TWRP version 2.3.1.0
Fourth is Stock recovery.
Do not flash all of them. Are you a TWRP or CWR kind of person? Instead of re-typing it out, go here and I come in on post #20 on the 2nd page. Read that to the end and let us know if you understand it. Pretty easy to follow but I understand your Panic Mode, so take your time.
Aerowinder said:
If still having problems, only thing left to do is flash a full stock image, link also in my signature.
Click to expand...
Click to collapse
^^ This is what I see in his future.
Like I said above, I haven't seen too many people get out of that "Encountered..." error without some real technical expertise.

Aerowinder said:
Don't use those - they are older versions.
If you don't care about the counter, then flash the CWM in my signature using Odin (can provide TWRP tar link if that's your thing), then flash root66 using Odin. You can reboot in between... but no real reason to do so.
If you are still having issues after you flash these, drop into recovery (vol up + home) and reset factory defaults. If still having problems, only thing left to do is flash a full stock image, link also in my signature. The page you linked to does not contain the newest version because DocHolliday hasn't been around here much lately.
Click to expand...
Click to collapse
Awesome. Thanks Aerowinder!
I will try this when I get home (assuming I can go into download mode...) and post what happened

Woody said:
^^ This is what I see in his future.
Like I said above, I haven't seen too many people get out of that "Encountered..." error without some real technical expertise.
Click to expand...
Click to collapse
I will take a look at the link Woody.
I am really hoping this will work on the first try!
Okay so from reading your post Woody I can use EITHER the TWRP and CWR, but I want to use the one that is easiest to use. Which one do you guys think is easier to use?
Also, SU3.3 or SU1.04 which one should I use? Aerowinder, your sig shows both now but earlier I didn't notice the SU1.04. I just realized I only need the SU file IF the prerooted file doesn't work but just in case it doesn't I guess it is better to know.

Draw straws. I use CWM/Superuser. I use Superuser because CM comes with it. AOKP comes with SuperSU... both work fine. Just make sure you use the ones from my signature, as they are newer versions. You won't need su if you get a prerooted rom, only for stock.

Aerowinder said:
Draw straws. I use CWM/Superuser. I use Superuser because CM comes with it. AOKP comes with SuperSU... both work fine. Just make sure you use the ones from my signature, as they are newer versions. You won't need su if you get a prerooted rom, only for stock.
Click to expand...
Click to collapse
I am going to try it in an hour.
Wish me luck!
1. Download mode
2. Flash CWM
3. Flash Root66
4. Hopefully no problems

:good:

Aerowinder said:
Don't use those - they are older versions.
If you don't care about the counter, then flash the CWM in my signature using Odin (can provide TWRP tar link if that's your thing), then flash root66 using Odin. You can reboot in between... but no real reason to do so.
If you are still having issues after you flash these, drop into recovery (vol up + home) and reset factory defaults. If still having problems, only thing left to do is flash a full stock image, link also in my signature. The page you linked to does not contain the newest version because DocHolliday hasn't been around here much lately.
Click to expand...
Click to collapse
OMFG OMFG OMFG
OMFG OMFG OMFG
OOOOOOH MYYYYYY FOOOOOOOOKIN GOOOOOOOOOOOOSH
AEROWINDER AND WOODY
I LOVE YOU SO MUCH
IT WORKED AND NOTHING GOT ERASED. I THOUGHT PUTTING THE NEW FIRMWARE WOULD'VE ERASED EVERYTHING WITH THE NEW ROM BUT NOPE.
Uninstalled KIES and USB drivers.
Installed USB drivers from Aerowinders sig
So the Odin 3.07 didn't work either so I ended up using ODIN 1.85
Turned off auto reboot and left f reset on (no idea what f reset does lol)
Flashed CWM
Flashed root66 rom
Restarted phone and it was back to normal with all the data saved, but no SU (wasn't unlocked)
So reflashed CWM
Then restarted in clockwork recovery and ran super user and now the phone is rooted
Thanks for your helpful knowledge and now I am going to learn everything about android so I too can help another new android user in the (hopefully near) future.
:good::good::good: 3 thumbs up to the knowledge members above Aerowinder and Woody!
THANK YOU!
Panic mode TRANSFORMMMMM! *Panic mode has now transformed into excitement mode*

buzzking00 said:
Thanks for your helpful knowledge and now I am going to learn everything about android so I too can help another new android user in the (hopefully near) future.
Click to expand...
Click to collapse
So, ahh, are you excited? Haha. Great. Glad you got it up and running.
I hope that you do learn more about Android and share it with someone who needs help someday. When I first came, that is what someone did for me and I have tried to do it ever since. We are all still learning, including Aero and myself, so there will never be an end but rather more.
Good job and now you should make a Nandroid backup just in case you ever get in a bind again.

Well now I gotta learn how to make back-ups and what a Nandroid backup is lol.
Time to search the forums

buzzking00 said:
Well now I gotta learn how to make back-ups and what a Nandroid backup is lol.
Time to search the forums
Click to expand...
Click to collapse
That's the attitude, with Android you have to be a sponge and try to learn as much as you can. A single Google search will give you the answers you seek and making a backup is pretty much universal no matter what Rom, phone you have. Good luck
Sent from my SGH-T999 using xda app-developers app

[Q] HELP I seem to be stuck.....

Good Evening all,
I have a T-mobile Galaxy S3 that was rooted. That I took back to stock and unrooted using Odin and T999UVALEM_T999TMBALEM_T999UVALEM_HOME.tar......I let the phone sit for about 25-30 min and it never really made it past the pulsing SAMSUNG screen. Now I rebooted into Flashing Mode (Odin) and Flashed CF-Auto-Root-d2tmo-d2tmo-sght999.tar, thinking that would help.......however.....I still seem to be stuck.....How do I get myself unstuck? Thanks so much for any help .....
Mic

Have you tried using stock recovery and perform a factory reset? I also took mine back to stock via Odin, performed the factory reset and worked fine
Sent from my SGH-T999 using Tapatalk

Hellfireworks said:
Have you tried using stock recovery and perform a factory reset? I also took mine back to stock via Odin, performed the factory reset and worked fine
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
I did do that.....and was able to update to 4.3 through t-mobile, however, now I have a black block which appears over all screens giving or listing what seems to be the information about my phone, and a warning that the phone is in "Factory Mode" and I need to reset it back to user.....or something like that...it comes and goes kinda fast....I wanted to flash a different ROM but I went back to stock to kinda clean up my internal SD....it was getting kinda bulked down with all the roms I was trying.........but now I am stuck with this......any ideas??

jinx0117 said:
I did do that.....and was able to update to 4.3 through t-mobile, however, now I have a black block which appears over all screens giving or listing what seems to be the information about my phone, and a warning that the phone is in "Factory Mode" and I need to reset it back to user.....or something like that...it comes and goes kinda fast....I wanted to flash a different ROM but I went back to stock to kinda clean up my internal SD....it was getting kinda bulked down with all the roms I was trying.........but now I am stuck with this......any ideas??
Click to expand...
Click to collapse
Did you update to 4.3 while you were in stock? If you did that, maybe Knox is causing you these issues, if you havent been in 4.3 in stock, you shouldn't have that issue.
I would suggest flashing 4.1.2 version via odin, after that enter recovery and do a factory reset, after that reboot and it should start properly
Sent from my SGH-T999 using Tapatalk

Hellfireworks said:
Did you update to 4.3 while you were in stock? If you did that, maybe Knox is causing you these issues, if you havent been in 4.3 in stock, you shouldn't have that issue.
I would suggest flashing 4.1.2 version via odin, after that enter recovery and do a factory reset, after that reboot and it should start properly
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
I originally went to Stock 4.1.2....then got tried to root the phone thinking that flashing different Rom would fix the issue.....no dice...So I flashed back to the 4.1.2 Stock. Made my way around the block that pops up telling me I need to set it back to user mode and did the OTA update. After the update it was still saying that I was in Factory Mode....and needed to reset it to User Mode.....In did a hard reset and wipe....and it is still there.....I may be able to change it through root explorer but I need to root my phone again.....and I have no idea where a safe place to start would be for that....

@jinx0117
Sounds like your EFS folder might have been erased. You can root the phone and check with a file explore. If you don't have a backup of it, there is no way to recover it.
If you have updated to official 4.3 don't try to downgrade with odin or you will end up with a full brick.

sswb27 said:
@jinx0117
Sounds like your EFS folder might have been erased. You can root the phone and check with a file explore. If you don't have a backup of it, there is no way to recover it.
If you have updated to official 4.3 don't try to downgrade with odin or you will end up with a full brick.
Click to expand...
Click to collapse
Thank you so much for telling me that.....I was able to root and reset my phones Factory Mode by use of a Emulator. Now I did follow some steps I found here on XDA to get around the Knox Security that T mobile put on the 4.3 update......I am able to flash Roms now with no issues.....thanks so much everyone for all your help!!!!
I will assume that if I want to take it back to stock again I would need to flash a 4.3 stock with Odin???? That way I don't brick my phone? Is that correct?:good:

jinx0117 said:
Thank you so much for telling me that.....I was able to root and reset my phones Factory Mode by use of a Emulator. Now I did follow some steps I found here on XDA to get around the Knox Security that T mobile put on the 4.3 update......I am able to flash Roms now with no issues.....thanks so much everyone for all your help!!!!
I will assume that if I want to take it back to stock again I would need to flash a 4.3 stock with Odin???? That way I don't brick my phone? Is that correct?:good:
Click to expand...
Click to collapse
Yea, Stick with 4.3 odin for now on. The 4.3 Bootloader wont let you downgrade.

sswb27 said:
Yea, Stick with 4.3 odin for now on. The 4.3 Bootloader wont let you downgrade.
Click to expand...
Click to collapse
Thank you so much for that....I have tried to flash a few custom roms but I see there are some issues with certain parts of the phone if they are not 4.3 and above. Do you know of a good ROM that would work on my phone that has alot of customizing.....I'm a chick....so....In like to theme.....lol
I can't use anything from Team Dirt.....my phone won't load it....I have Dandroid on there now....but that is pretty much stock.....Tried StockRom custom.....but it never loaded the Aroma installer......it just sat there saying it was loading it...... Thanks again for all the help. :laugh:

jinx0117 said:
Thank you so much for that....I have tried to flash a few custom roms but I see there are some issues with certain parts of the phone if they are not 4.3 and above. Do you know of a good ROM that would work on my phone that has alot of customizing.....I'm a chick....so....In like to theme.....lol
I can't use anything from Team Dirt.....my phone won't load it....I have Dandroid on there now....but that is pretty much stock.....Tried StockRom custom.....but it never loaded the Aroma installer......it just sat there saying it was loading it...... Thanks again for all the help. :laugh:
Click to expand...
Click to collapse
Aroma is buggy, you just have to keep rebooting into recovery and keep trying, it will go. Some say it seems to work better without the usb plugged in.
As for team dirt I believe it is a aosp rom. If it is you will have to edit the updater script in the zip file so it know's your new 4.3 bootloader. META-INF>com>google>android>updater-script. If your on windows I suggest downloading notepad++ to edit the file. Just delete every thing down to where it
say's mount then save the file.
Update: I edited the updater for you https://www.dropbox.com/s/xucl47rh1wxg9rt/updater-script
Just put it in the zip file where I told you above, save and copy it to the zip and flash away.

sswb27 said:
Aroma is buggy, you just have to keep rebooting into recovery and keep trying, it will go. Some say it seems to work better without the usb plugged in.
As for team dirt I believe it is a aosp rom. If it is you will have to edit the updater script in the zip file so it know's your new 4.3 bootloader. META-INF>com>google>android>updater-script. If your on windows I suggest downloading notepad++ to edit the file. Just delete every thing down to where it
say's mount then save the file.
Update: I edited the updater for you https://www.dropbox.com/s/xucl47rh1wxg9rt/updater-script
Just put it in the zip file where I told you above, save and copy it to the zip and flash away.
Click to expand...
Click to collapse
Wow!!!! Thank you sooooo much....I admit I don't know it all just enough to be dangerous....but I am always willing to learn.....thank you so much for doing that for me....that was really awesome of you......

jinx0117 said:
Wow!!!! Thank you sooooo much....I admit I don't know it all just enough to be dangerous....but I am always willing to learn.....thank you so much for doing that for me....that was really awesome of you......
Click to expand...
Click to collapse
Well, this is the place to learn. We are all here to help each other, that's why i love android.:highfive:
Just use that thanks button to people that help you is all we ask in return.

[GUIDE] Links for Files - Update, Root and Restore (UPDATED TO QK1)

QK1 TAR File: https://www.androidfilehost.com/?fid=673791459329068925
Prior version if needed:
QJ1 TAR File: https://www.androidfilehost.com/?fid=889964283620769224
HOW TO ROOT USING MAGISK:
Flash stock with Odin. The latest build is posted above. Reboot and complete setting up the phone.
Download Magisk Zip and Magisk Manager APK (these are two different things, you need both) and place them on your phone. Download from https://magiskmanager.com/
Do the usual to enable Developer Options (tap on build number until you see it enabled) and set OEM Unlock ot on (this is a setting under developer options.) Make sure you do these steps.
Go into Download mode. Turn phone off. Hold Volume Down, Home and Power buttons. We'll do something similar in a minute.
Flash TWRP via Odin, but DO NOT REBOOT. TWRP is here, use the TAR file. https://dl.twrp.me/zerofltespr/
Manually Power phone down by holding the Power button a really long time.
Manually boot into Recovery. Hold Volume Up, Home and Power. You should now be in TWRP.
Use TWRP to flash the Magisk zip file. When you reboot, you should be rooted.
Reboot and install the Magisk APK. Allow "Unknown sources."
You can still root your phone using SuperSU, but I am not supporting that.

thank you for your link.
- have you got the latest PD2 rom file yet?
- does the TWRP work on PD2 build?
thanks again

Thank you so much for the help and the resources, i definetly would need to make nandroid backup so i won't go through that pain again lol c:

FYI, the new PD2 build is already updated...
http://samsung-updates.com/device/?id=SM-G920P

yaibakt said:
FYI, the new PD2 build is already updated...
http://samsung-updates.com/device/?id=SM-G920P
Click to expand...
Click to collapse
Thanks and I am grabbing that now, will post an Android File Host link. However, I am going to include a cautionary note until we clarify the situation with TWRP.
But I am glad that you pointed that out.

koop1955 said:
Thanks and I am grabbing that now, will post an Android File Host link. However, I am going to include a cautionary note until we clarify the situation with TWRP.
But I am glad that you pointed that out.
Click to expand...
Click to collapse
thank you for your download and upload work. it spends your time and stuffs.
also for the TWRP. I am waiting for the new TWRP version now.
cant live without being rooted nor xposed...

Amazing! If you want any help organizing or anything like that, feel free to let me know :good:

JoeFCaputo113 said:
Amazing! If you want any help organizing or anything like that, feel free to let me know :good:
Click to expand...
Click to collapse
Thanks, Joe. I think that the next step (and it won't be me!) is to do a video tutorial. A "How To Use" this stuff like Tim (QBKing) used to do.

did anyone have TWRP on the lastest PD2 yet?
im about to re-flash the rom this weekend and want to try the PD2.
if not, i guess i must stay at PB6

yaibakt said:
did anyone have TWRP on the lastest PD2 yet?
im about to re-flash the rom this weekend and want to try the PD2.
if not, i guess i must stay at PB6
Click to expand...
Click to collapse
yes,i have PD2 and TWRP 3.0.0.1.
everythings is ok.
note:dont root your phone with flashing supersu.zip (this method dont work good and have some issues)
use g920F (not g920P) cf auto root image (work great)

yaibakt said:
did anyone have TWRP on the lastest PD2 yet?
im about to re-flash the rom this weekend and want to try the PD2.
if not, i guess i must stay at PB6
Click to expand...
Click to collapse
I have twrp working on cpd2 ill see if i can find the link to the whole package
You gotta flash it via odin and it says for pb6 but during flash , it updates the firmware
Sent from my SM-G920P using Tapatalk

I didn't see this question is the pd2 link an update or a full wipe?

cyberone3 said:
I didn't see this question is the pd2 link an update or a full wipe?
Click to expand...
Click to collapse
Complete TAR file.

i confirm that the TWRP in #1 works with latest PD2.

yaibakt said:
i confirm that the TWRP in #1 works with latest PD2.
Click to expand...
Click to collapse
Thanks for this, have not gotten around to testing myself.
Could you post any feedback that you might have on PD2 itself? Worth bothering with, or just a minor security thing?

Im about to go get my new replacement S6 and have a feeling its going to be on the latest firmware so good to hear it works on Pd2. Well TWRP works on PD2what about flashing supersu 2.71 in twrp does that brick it? Or did u use cfautoroot?

Jimmy1life said:
Im about to go get my new replacement S6 and have a feeling its going to be on the latest firmware so good to hear it works on Pd2. Well TWRP works on PD2what about flashing supersu 2.71 in twrp does that brick it? Or did u use cfautoroot?
Click to expand...
Click to collapse
You'd be surprised actually, when I got my replacement, it came with the like second updat, lol

Jimmy1life said:
Im about to go get my new replacement S6 and have a feeling its going to be on the latest firmware so good to hear it works on Pd2. Well TWRP works on PD2what about flashing supersu 2.71 in twrp does that brick it? Or did u use cfautoroot?
Click to expand...
Click to collapse
Twrp and supersu 2.71 work for me.
Nothing noticeable between pd2 and pb6 actually so if you are still good on pb6, let it stay there.
BTW i get good battery life on pd2 as you can see my attached SS. Will pass 5 hrs sot easily, even more.
Sent from my SM-G920P using Tapatalk

@yaibakt, any chance you could edit your post to reduce the image size or just eliminate it, now that it has been seen?
Trying to keep the thread clean.
Thanks.

Ok, i will delete the image.
I upload directly from tapatalk app so i cant resize it.
Sent from my SM-G920P using Tapatalk