Develop Bugs

Recovery won't stick with new OTA update.

The CWM or Team Win recoveries will not stick after rebooting the phone with w OTA update. There is a way of making recovery stick on the rooted OTA update. Does anyone know the correct files to freeze or erase for the new recoveries to stick?????
Is there another way of these recoveries to stick besides flashing a custom Rom??
Vinny

vinnyjr said:
The CWM or Team Win recoveries will not stick after rebooting the phone with w OTA update. There is a way of making recovery stick on the rooted OTA update. Does anyone know the correct files to freeze or erase for the new recoveries to stick?????
Is there another way of these recoveries to stick besides flashing a custom Rom??
Vinny
Click to expand...
Click to collapse
I definitely didn't have that problem. If you have root use google manager to install twrp
Sent from my SGH-T999 using Tapatalk 2

mikeyinid said:
I definitely didn't have that problem. If you have root use google manager to install twrp
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
I have root, I have Goo Manager, I'm on a completely stock rooted rom and every time you reboot the new OTA software over writes the custom recovery to the stock Android recovery. If you have a custom rom this will not happen, only on a stock, rooted OTA latest update rom. Others are having the same issue.
Vinny

What methods did you use to install the ota and root?
Have you tried flashing the stock rooted version wildchld released?
Sent from my SGH-T999 using xda app-developers app

I waited for the OTA update then used Odin to flash root, did not reboot after flashing with Odin, pulled battery, then went right to recovery and flashed super user.zip file. I rooted my phone the right way. This is my 2nd SGS3 and didn't have this problem with the 1st one because it had the older build. This is not a problem if you are on a custom build. Only stock, rooted with latest OTA build.
Vinny
Sent from my SGH-T999 using Tapatalk 2

I honestly don't know if it would work but maybe try flashing the insecure stock kernel?
Sent from my SGH-T999 using xda app-developers app

Thanks for the input. (DocHoliday) is my favorite western character. Big western nut.
Vinny
Sent from my SGH-T999 using Tapatalk 2

vinnyjr said:
I have root, I have Goo Manager, I'm on a completely stock rooted rom and every time you reboot the new OTA software over writes the custom recovery to the stock Android recovery. If you have a custom rom this will not happen, only on a stock, rooted OTA latest update rom. Others are having the same issue.
Vinny
Click to expand...
Click to collapse
im stock, rooted on the latest ota and i dont have this issue. never had it on the other build either

vinnyjr said:
Thanks for the input. (DocHoliday) is my favorite western character. Big western nut.
Vinny
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
I'm your huckleberry!
Sent from my SGH-T999 using xda app-developers app

mrmako777 said:
im stock, rooted on the latest ota and i dont have this issue. never had it on the other build either
Click to expand...
Click to collapse
yes you do, you just don't know it yet.
Reboot your phone, then boot into recovery.
Sent from the current Heavy Weight Champ GALAXY SIII

Please try this, http://forum.xda-developers.com/showthread.php?t=1821681
Hopefully it works. Mine is fine after update

vinnyjr said:
I have root, I have Goo Manager, I'm on a completely stock rooted rom and every time you reboot the new OTA software over writes the custom recovery to the stock Android recovery. If you have a custom rom this will not happen, only on a stock, rooted OTA latest update rom. Others are having the same issue.
Vinny
Click to expand...
Click to collapse
I'm on the stock rooted rom and this hasn't been a problem for me. I've installed recovery once since I got the phone. And flashed every stock and custom Rom.
Sent from my SGH-T999 using Tapatalk 2

ingenious247 said:
yes you do, you just don't know it yet.
Reboot your phone, then boot into recovery.
Sent from the current Heavy Weight Champ GALAXY SIII
Click to expand...
Click to collapse
Lolol uh, I've done it a hundred times guy, no issues
Sent from my SGH-T999

You're right. You're the only guy in the world who's official stock update doesn't overwrite the recovery upon reboot. They special coded yours to preserve custom recovery.
Please...
I swear sometimes..
Sent from the current Heavy Weight Champ GALAXY SIII

Guys, I have seen this on my GF's GSII (Sprint) as well as on my nexus 7. They are placing a file called recovery-from-boot.p in the /system/ directory that overwrites recovery on every boot. I put a guide a few post up that outlines the issue when I saw it on my GF's phone.
Personally my T-Mobile has been fine, but this scenario I have dealt with before. So don't flame that bad.

The bottom line is that without some custom modding, if you're running the official stock OTA update, stock kernel, etc, standard CWM recovery is not going to stick.
Plain and simple.
---------- Post added at 11:07 AM ---------- Previous post was at 11:06 AM ----------
cybrnook said:
Guys, I have seen this on my GF's GSII (Sprint) as well as on my nexus 7. They are placing a file called recovery-from-boot.p in the /system/ directory that overwrites recovery on every boot. I put a guide a few post up that outlines the issue when I saw it on my GF's phone.
Personally my T-Mobile has been fine, but this scenario I have dealt with before. So don't flame that bad.
Click to expand...
Click to collapse
Yeah, I'm going to try using that guide and report back. thanks
---------- Post added at 11:12 AM ---------- Previous post was at 11:07 AM ----------
Ok, both files were present as described in your guide.
Renamed both to:
recovery-from-boot.bak
install recovery.sh.bak
Reflashed CWM through ROM Manager. Rebooting now, then will try power off & booting into recovery. Hang tight
*Edit: Worked like a charm. Gentlemen, we have the solution. Thanks due (and given) to cybrnook both here and in the guide
sweet.

ingenious247 said:
The bottom line is that without some custom modding, if you're running the official stock OTA update, stock kernel, etc, standard CWM recovery is not going to stick.
Plain and simple.
---------- Post added at 11:07 AM ---------- Previous post was at 11:06 AM ----------
Yeah, I'm going to try using that guide and report back. thanks
Click to expand...
Click to collapse
I would argue, I have a stock rooted rom, stock kernel and I update to the new OTA update via Kies and TWRP has stuck every boot since then. I even tested it again when I saw this thread as it made me unsure.

cybrnook said:
I would argue, I have a stock rooted rom, stock kernel and I update to the new OTA update via Kies and TWRP has stuck every boot since then. I even tested it again when I saw this thread as it made me unsure.
Click to expand...
Click to collapse
Maybe the Kies version is different than the OTA.
Maybe TWRP overwrites or renames/deletes the files causing it.
But you can't argue with my posts, because I said official OTA update, and CWM.

ingenious247 said:
Maybe the Kies version is different than the OTA.
Maybe TWRP overwrites or renames/deletes the files causing it.
But you can't argue with my posts, because I said official OTA update, and CWM.
Click to expand...
Click to collapse
No worries, but for clarification to all the read this thread. The update from Kies is the exact same Official update as the OTA, so if you have not been prompted for the update yet from T-Mo, just install Kies on your PC and plus your phone in, it will prompt you for the update.
I have another guide I made for that:
http://forum.xda-developers.com/showthread.php?t=1842142
For the recovery, installing twrp or CWM wont remove the two files I listed. This is done manually. I know on the sprint side, they made a root Super User package that swiped those off specific to the sprint phone. But I opted away from that for my GF as I Prefer SuperSU and am anal retentive about installing something I don't want and uninstalling it.
---------- Post added at 08:26 PM ---------- Previous post was at 08:24 PM ----------
ingenious247 said:
yes you do, you just don't know it yet.
Reboot your phone, then boot into recovery.
Sent from the current Heavy Weight Champ GALAXY SIII
Click to expand...
Click to collapse
ingenious, it's not present on all phones. Like mine for example, I have been fine since day 1 of owning the phone. But my GF's sprint phone had the persistent install present.
It's strange, some phones don't have it at all, some only have the .p file, and some have both. I have not found the common denominator yet.

ingenious247 said:
You're right. You're the only guy in the world who's official stock update doesn't overwrite the recovery upon reboot. They special coded yours to preserve custom recovery.
Please...
I swear sometimes..
Sent from the current Heavy Weight Champ GALAXY SIII
Click to expand...
Click to collapse
My bad man, I didn't get the memo that you knew everything I guess all the other guys that haven't had this same issue are nuts too...
Sent from my SGH-T999

[Q] URGENT Need Advice

I've searched and searched and haven't came up with anything so i'm resorting to asking. Was Running 4.0.1 AOKP and have been for a while with no problems. Just decided to flash ParanoidDroid so i ODIN EL26 it passed no problems, after phone rebooted it showed normal samsung boot and yellow triangle then screen goes black and it stops right there. When plugged into my computer my device manager recognizes it. If i try to boot into recovery it wont go but it will boot back into download mode. was it a bad kernal i flashed? Please tell me this isn't some sort of brick. I'll continue troubleshoting but any advice is appreciated.

Why not give a one click a go and see from there since you can get to download mode?
Or use pc odin and see if its just a bad kernel flash?
No blue light so id say your hunch is right.
Sent from my SPH-D710 using Xparent SkyBlue Tapatalk 2

MoHoGalore said:
Why not give a one click a go and see from there since you can get to download mode?
Or use pc odin and see if its just a bad kernel flash?
No blue light so id say your hunch is right.
Sent from my SPH-D710 using Xparent SkyBlue Tapatalk 2
Click to expand...
Click to collapse
Ok i'll give one click a try. and sorry i didnt give enough detail but i did uses pc odin. and what does the blue light mean?

ghostin0hs said:
Ok i'll give one click a try. and sorry i didnt give enough detail but i did uses pc odin. and what does the blue light mean?
Click to expand...
Click to collapse
Solid blue, hard brick. Seen some users talk about a blinking blue and were able to come back. Since you didn't talk about that, I'd assume you may be ok but try the one click.
Also, if you find that there are issues, crawrj has written a back to life thread. But it doesn't sound like you're there just yet.
Let us know after a one click try.. Someone may have additional suggestions.
Sent from my SPH-D710 using Xparent SkyBlue Tapatalk 2

MoHoGalore said:
Solid blue, hard brick. Seen some users talk about a blinking blue and were able to come back. Since you didn't talk about that, I'd assume you may be ok but try the one click.
Also, if you find that there are issues, crawrj has written a back to life thread. But it doesn't sound like you're there just yet.
Let us know after a one click try.. Someone may have additional suggestions.
Sent from my SPH-D710 using Xparent SkyBlue Tapatalk 2
Click to expand...
Click to collapse
One click says it was successful. Now it gets stuck at the samsung and yellow triangle screen, HOWEVER i can now boot into CWM. So what is the best/safest option at this point? Install a rom the CWM or maybe re-ODIN? I tried wiping everything from CWM but it didnt do anything. Thanks so much for the help

ghostin0hs said:
One click says it was successful. Now it gets stuck at the samsung and yellow triangle screen, HOWEVER i can now boot into CWM. So what is the best/safest option at this point? Install a rom the CWM or maybe re-ODIN? I tried wiping everything from CWM but it didnt do anything. Thanks so much for the help
Click to expand...
Click to collapse
How long did you let it sit at the boot screen? Have seen it take 10-15 minutes before.
And if it was me, at this point id stay w a one click and not from recovery just yet.
Which one click did you use?
Sent from my SPH-D710 using Xparent SkyBlue Tapatalk 2

MoHoGalore said:
How long did you let it sit at the boot screen? Have seen it take 10-15 minutes before.
And if it was me, at this point id stay w a one click and not from recovery just yet.
Which one click did you use?
Sent from my SPH-D710 using Xparent SkyBlue Tapatalk 2
Click to expand...
Click to collapse
Have been letting it sit about 10 minutes or so now. and i used:
http://forum.xda-developers.com/showthread.php?t=1342728
and just chose option C then OPTION F for EL26

Would it be an issue that i was running ICS and now Flashing back to GB? I have just read that when flashing a new rom always ODIN back to EL26 before wiping and installing new rom

ghostin0hs said:
Have been letting it sit about 10 minutes or so now. and i used:
http://forum.xda-developers.com/showthread.php?t=1342728
and just chose option C then OPTION F for EL26
Click to expand...
Click to collapse
I apologize. I was meaning a complete one click earlier.
But it does seem that you've got the kernel issue resolved.
So either you had a bad download of the rom you were trying from the start or a bad flash. I'd download the rom again, if you can transfer to sdcard via computer (if it has a sd adapter) and reflash.
Otherwise, id use this to get the phone in a working state. Then start again.
http://forum.xda-developers.com/showthread.php?p=31304851
Sent from my SPH-D710 using Xparent SkyBlue Tapatalk 2

use this link
http://forum.xda-developers.com/showthread.php?t=1416477

ghostin0hs said:
Would it be an issue that i was running ICS and now Flashing back to GB? I have just read that when flashing a new rom always ODIN back to EL26 before wiping and installing new rom
Click to expand...
Click to collapse
It can be confusing but when you flashed the rom from el26, you should have been left with the included kernel but it sounds like you had a bad flash.
Sent from my SPH-D710 using Xparent SkyBlue Tapatalk 2

Got it. i just installed my rom through CWM and everything working. idk if that was my stupid mistake or just my phone bein weird but thanks for the help anyway guys

Edit: wrong thread, I'll be back to answer your question shortly. Tapatalk flaked out on me :banghead:
Edit3: OK you may want to search for sfhubs factory reset from Odin thread and do a wipe through Odin and then use a one-click to restore a rom. Otherwise you can Odin el26+cwm direct boot, do a full wipe or run a format all script and then flash a twiz based rom through recovery, if you want an aosp based rom you'll need to flash a twiz based rom first, then boot up the phone and then Odin el26 again flash the aosp based rom, then factory reset and perform the wipes/format all script, flash the rom again and then gapps, wipe cache and dalvik and boot the phone, since your rom currently isn't full functional you'll need the twiz based rom to restore the system partitiom to be able tto flash a aosp based rom without receiving an error.
We are legion, for we are many.
Sent from the DarkSide of the GalaXy with a MEK device

[Q] galaxy s3 no lte t999 stuck on "samsung" logo

ok im going to cut this short i need help im stuck on this "samsung" logo lemme tell you the back story i root it put a rom on it (beanstalk btw) then i decided to go back to stock (dont ask me y i just want to) i used odin and the samsung website to find which version i want i then extract it and everything i used odin 3.07 to work its magic. now im in this samsung screen im waiting 20 minutes for it to pass the "samsung" boot logo yet it doesnt can anyone help me

Try downloading again or using Odin to push custom recovery and flashing a stock based ROM.
Make sure you didn't leave anything checked in Odin you weren't explicitly told to leave checked (I can't remember the exact box I'm thinking of but it has to do with partitions) I lost an admire to a hard brick like that once.
Sent from my SGH-T999 using Tapatalk

tokenpoke said:
Try downloading again or using Odin to push custom recovery and flashing a stock based ROM.
Make sure you didn't leave anything checked in Odin you weren't explicitly told to leave checked (I can't remember the exact box I'm thinking of but it has to do with partitions) I lost an admire to a hard brick like that once.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
i did try downloading it again and used odin numerous times what do you mean by push custom recovery? but i did flash a stock rom also its the re-partition that you ment to say, i definently left that one closed i didnt leave it checked i cleared my cache and data thinking that the samsung boot wouldve worked but it still didnt

I mean use Odin to put a custom recovery like twrp or cwm on the phone and try flashing a ROM like you did with beanstalk.
Sent from my SGH-T999 using Tapatalk

tokenpoke said:
I mean use Odin to put a custom recovery like twrp or cwm on the phone and try flashing a ROM like you did with beanstalk.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
but i want to go back to stock idk how doing that will help but ok

It will confirm that the phone isn't hard bricked and allow you to use the phone at least.
From there you can try Mobil Odin on the off chance that its a PC issue.
Sent from my SGH-T999 using Tapatalk

tokenpoke said:
It will confirm that the phone isn't hard bricked and allow you to use the phone at least.
From there you can try Mobil Odin on the off chance that its a PC issue.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
why is twrp asking me for a password when their is none and when i press cancel and view my file it say my sdcard and ext has 0bytes

Well, that's not good.
Um... I've never had that happen.
But SD and ext showing 0 tells me those partitions were wiped and possibly resized.
I don't know how to rebuild partitions though.
Maybe ask in the twrp thread about the password issue. I've never seen that in 5 years of modding my phones.
The fact that recovery boots at all is promising but I'm not sure if its gonna fix your problem to be honest.
Sent from my SGH-T999 using Tapatalk
---------- Post added at 06:56 PM ---------- Previous post was at 06:55 PM ----------
If you can get past the password and get ADB running you may be able to rebuild the partition tables using ADB commands.
Sent from my SGH-T999 using Tapatalk

tokenpoke said:
Well, that's not good.
Um... I've never had that happen.
But SD and ext showing 0 tells me those partitions were wiped and possibly resized.
I don't know how to rebuild partitions though.
Maybe ask in the twrp thread about the password issue. I've never seen that in 5 years of modding my phones.
The fact that recovery boots at all is promising but I'm not sure if its gonna fix your problem to be honest.
Sent from my SGH-T999 using Tapatalk
---------- Post added at 06:56 PM ---------- Previous post was at 06:55 PM ----------
If you can get past the password and get ADB running you may be able to rebuild the partition tables using ADB commands.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
but when i go to backup it gives me the mb and everything it doesnt show 0mb

Wait... So you CAN get in to flash a ROM but the recovery isn't seeing the partitions unless you're tying to backup the current ROM?
Do you have a backup already made that you can try restoring?
Also, did you ask about the password issue in the twrp thread?
Sent from my SGH-T999 using Tapatalk

tokenpoke said:
Wait... So you CAN get in to flash a ROM but the recovery isn't seeing the partitions unless you're tying to backup the current ROM?
Do you have a backup already made that you can try restoring?
Also, did you ask about the password issue in the twrp thread?
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Hmmm.. Im going to do that u mm where is the twrp thread located?

Um... I don't know for the non LTE s3. The forum has an awesome search function though that should find it for you quickly. I'm on mobile though so its a pain to find and link.
Sent from my SGH-T999 using Tapatalk

tokenpoke said:
Um... I don't know for the non LTE s3. The forum has an awesome search function though that should find it for you quickly. I'm on mobile though so its a pain to find and link.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
I got it working! ! It's weird I flashed the stock rom with Odin 4 times but when I re flashed it this time it worked. .. weird but it works thanks for your help tho

Sounds like a PC hiccup.
You may want to invest in a new USB cable just incase. I've had issues from my original USB cable where it wouldn't transfer files without corrupting. Drove me crazy until I used my girlfriends without issue.
Sent from my SGH-T999 using Tapatalk

When ever gojng between tw and cm/aosp roms it will hang at boot unless you factory reset. Glad you got it working!
Sent from my SGH-T999 using Tapatalk

[Q] Sprint Note 2 softbrick help?

Hello,
I've spent this weekend pouring over google, bing, and all sorts of different forums, and nothing I've tried has fixed the issue.
I've got a Note 2 on Sprint that I've managed to soft-brick. I can boot into download mode, but I can't boot into recovery. When I try to, it stays on the Note 2 splash screen.
I can get Odin to communicate with the phone, and it always fails at the same step: sboot.bin. I've tried several of the custom recoveries, as well as several of the different self-extracting one-click back to stock. Nothing I've tried has worked.
What is the next step that I can try? What other information do you need from me to help troubleshoot this thing?
Thanks!

Have you tried Kies?
Sent from my SPH-L900 using XDA Premium HD app
---------- Post added at 02:14 PM ---------- Previous post was at 02:06 PM ----------
I've managed to soft-brick, firm-brick and semi-hard brick my phone and always managed to find a way to resolve it. If Kies can't communicate with the phone to do the firmware recovery then you might need to reinstall the samsung usb drivers. Also does the computer recognize that you connected the isb cable? If so you're still able to recover the phone!
Sent from my SPH-L900 using XDA Premium HD app
---------- Post added at 02:21 PM ---------- Previous post was at 02:14 PM ----------
Also try using an older version of Odin to see if it helps along with an older cwm and check to see if it helps as well. If you still cant recover then you might have hard bricked the phone
Sent from my SPH-L900 using XDA Premium HD app

I had this same issue a few nights ago. I had to try multiple ROMs all downloaded from different places and flash then in Odin until one worked. If you'd like I can post the one that worked for me. The only problem with it is that it messes up your notification toggles, there is only airplane mode and blocking mode. Also every time you rotate the screen (ex. Watching a YouTube video) it force closes the system ui

RealColdHoney said:
I had this same issue a few nights ago. I had to try multiple ROMs all downloaded from different places and flash then in Odin until one worked. If you'd like I can post the one that worked for me. The only problem with it is that it messes up your notification toggles, there is only airplane mode and blocking mode. Also every time you rotate the screen (ex. Watching a YouTube video) it force closes the system ui
Click to expand...
Click to collapse
That would be great if you could. Once I get to a rom I can use, I should be able to get into recovery and flash back to stock.

You said you tried different roms, but have you tried to flash a different custom recovery first. You may want to try philz?
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2

g_money said:
You said you tried different roms, but have you tried to flash a different custom recovery first. You may want to try philz?
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2
Click to expand...
Click to collapse
I've tried multiple recoveries. I can flash them, and odin says success, but the phone never boots into recovery. Always the Note 2 splash screen.

mickeydjw said:
I've tried multiple recoveries. I can flash them, and odin says success, but the phone never boots into recovery. Always the Note 2 splash screen.
Click to expand...
Click to collapse
Yeah this was my exact issue. The download that worked for me was the most recent one over at SamMobile. Since i am a new user XDA is not letting me post links yet so i am going to put it here in pieces and you can put them together in your address bar.
http: //ww w.samm obile.com /firmw ares/3 /?downloa d=22322

You may want to give this a try:
http://www.androidayos.com/2014/06/...e-4-4-2-kitkat-for-sprint-galaxy-note-2-l900/
Keep in mind i have not used the above link, so use at your own risk...
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2

Custom Recovery after 4.4.2?

Hello XDA community,
So I've owned the Note II since it came out basically. I used to ODIN custom recoveries and flash ROMs to it all the time. After the last update (4.4.2), I ODIN my phone back to stock to get the update; which of course included the dreaded KNOX. Afterwards, I just left it be due to the KNOX security and fear of messing up the phone. Long story short, I've been out of the loop for a couple of years and recently I've had the urge to try some of the newer ROMs and what not. More than likely this urge has spawned from the fact that I'll be doing away with my Note II soon, as it's very old and dated. So the fear of messing it up, has some what diminished.
So my question is... Is there anything special that I have to do before attempting to load a custom recovery after the 4.4.2 firmware update? Do I have to downgrade my current stock firmware first? Or is it still the same as it was before 4.4.2, just using ODIN to push the recovery and reboot? Any help is greatly appreciated! :victory:

Even with knox there is a chainfire setup. Trips knox but your out of warranty anyway. Just follow threads for your note 2. Mine is att.
Sent from my SAMSUNG-SGH-I317 using Tapatalk

abonides said:
Even with knox there is a chainfire setup. Trips knox but your out of warranty anyway. Just follow threads for your note 2. Mine is att.
Sent from my SAMSUNG-SGH-I317 using Tapatalk
Click to expand...
Click to collapse
Wow, Thanks for the quick response! Would you mind looking through these instructions right quick, and see if I'm safe to go with this method?
ROOT AT&T GALAXY NOTE 2 AND INSTALL TWRP RECOVERY
1.) Download and extract CF-Auto-Root-t0lteatt-t0lteatt-samsungsghi317.zip to your PC. You’ll get an Odin flash-able file in the .tar.md5 format.
2.) Flash the CF-Auto-Root-t0lteatt-t0lteatt-samsungsghi317.tar.md5 using Odin. You can follow our exclusive guide on flashing firmware using Odin
3.) During the CF Auto-root process, if the device is stuck at bootlogo, remove the battery and boot into recovery mode manually to start the rooting process.
4.) Once the flashing process is finished, reboot the device and open the SuperSU app. If you encounter any KNOX warnings, then follow the instructions given in our KNOX disabling guide
5.) If everything is fine on the rooting end, download the latest Odin flash-able TWRP recovery from the Official TWRP page
6.) The recovery is in the form of .tar package, flash it using the Odin guide
7.) Reboot the device into recovery mode and check if the recovery is installed properly.

That looks like the right one. Been awhile my note is still going. Getting oppo r7s soon. But yes looks correct. Good flashing.
Sent from my SAMSUNG-SGH-I317 using Tapatalk

abonides said:
That looks like the right one. Been awhile my note is still going. Getting oppo r7s soon. But yes looks correct. Good flashing.
Sent from my SAMSUNG-SGH-I317 using Tapatalk
Click to expand...
Click to collapse
Oh Nice! A guy I work with was just telling me about the oppo. He's also talking about getting it. It looks like a beast, from what I've seen on it.

Looks nice...metal body. 1/2 price of new note . lol and a flip phone beats an I device. Ha ha haaa
Sent from my SAMSUNG-SGH-I317 using Tapatalk

abonides said:
That looks like the right one. Been awhile my note is still going. Getting oppo r7s soon. But yes looks correct. Good flashing.
Sent from my SAMSUNG-SGH-I317 using Tapatalk
Click to expand...
Click to collapse
Not sure where I went wrong. I factory reset my phone before I even started. Pushed the ROOT using ODIN 3.10. Everything went fine, the phone rebooted and came back with "SuperSU stopped working" ,"Youtube stopped working", "Maps stopped working." Unable to open any of those apps. I factory reset again, and cleared the cache, but still no luck. Any suggestions for me?

Only thing I can think is su needs to be re flashed
Sent from my SAMSUNG-SGH-I317 using Tapatalk
---------- Post added at 03:41 PM ---------- Previous post was at 03:40 PM ----------
I had once during root nothing opened. I flashed stock again then re flash SU then all good
Sent from my SAMSUNG-SGH-I317 using Tapatalk

abonides said:
Only thing I can think is su needs to be re flashed
I had once during root nothing opened. I flashed stock again then re flash SU then all good
Sent from my SAMSUNG-SGH-I317 using Tapatalk
Click to expand...
Click to collapse
Tried to re-flash SuperSU, but still no luck. However, after all the other apps finished updating - I can use youtube and maps again. yay! lol.
By re-flashing stock, do you mean using ODIN to push a stock firmware back over to the phone? Did the stock 4.4.2 firmware ever leak out after release?
By the way, I really appreciate your advice on all this.

I did a 4.3 stock. Then I flashed DN3. But yeah gapps can be a pain too. Slipped my mind lol.
Yw for the tips but you're doing it . lol Have fun.
Sent from my SAMSUNG-SGH-I317 using Tapatalk

abonides said:
I did a 4.3 stock. Then I flashed DN3. But yeah gapps can be a pain too. Slipped my mind lol.
Yw for the tips but you're doing it . lol Have fun.
Sent from my SAMSUNG-SGH-I317 using Tapatalk
Click to expand...
Click to collapse
I ended up going about it a different way, but I don't think I would of tried it without you talking me through some of it. Although it's not a lot, I donated to you so you could at least have a beer on me. Thanks brother. KCCO.

Greatly appreciated & good luck with everything. We are all here to help each other.
Sent from my SAMSUNG-SGH-I317 using Tapatalk