Develop Bugs

Need help with flashing custom recovery (Solved)

Hi I was rooted using cmenards int rom and I decided top use odin to go back to stock so I could do the update so I can get the new modem. It is how I have always done things when an update comes out even though I know I am going to root and use a custom I like to have a currrent stock backup and the latest modem. I am not new to this.so I dont know what is up.
I am using pc odin 3.07 i put the file in PDA and I tried to install the twrp with odin and it says that it worked but when I boot into recovery it is still stock. So I tried the CWM for the 7100 with the same results. (both of them I have used before with no problem) So I tried to redownload everything still the same resutls then I tried resetting everything and no luck. I gotta say I am stumped. The only thing I can think of is I was going to use kies to do the update but it was on my pc before but It hads to do an update so maybe the updated version of kies is doing something annd as it turned out I didnt need to use kies I just used the ota. So I am uninstalling it now as I type but I dont think it will do anything.
Can anyone help me please?

mojorisin7178 said:
Hi I was rooted using cmenards int rom and I decided top use odin to go back to stock so I could do the update so I can get the new modem. It is how I have always done things when an update comes out even though I know I am going to root and use a custom I like to have a currrent stock backup and the latest modem. I am not new to this.so I dont know what is up.
I am using pc odin 3.07 i put the file in PDA and I tried to install the twrp with odin and it says that it worked but when I boot into recovery it is still stock. So I tried the CWM for the 7100 with the same results. (both of them I have used before with no problem) So I tried to redownload everything still the same resutls then I tried resetting everything and no luck. I gotta say I am stumped. The only thing I can think of is I was going to use kies to do the update but it was on my pc before but It hads to do an update so maybe the updated version of kies is doing something annd as it turned out I didnt need to use kies I just used the ota. So I am uninstalling it now as I type but I dont think it will do anything.
Can anyone help me please?
Click to expand...
Click to collapse
It's a known issue on newer android devices, it will automatically reflash the stock recovery. Try using goomanager or exynos abuse, I'm positive one will ask you if you want to disable it (I remeber it popping up)

Oooh I read about that so thats what it is. Goo manager does not work I tried but what is ths other thing. I guess I have to get it here? I will google it I see it is not in market thank you. So if that does not work how do I get around this?

Okay I figured it out. And I actually didnt even haver to hook up to my pc. I was ****ting (which is where I come up with all my good ideas.) And I remember reading about the security hole in the exynos processor and the app chainfire came up with. Which turns out to be the exynos abuse app that killahurtz was talking about. So I remembered that with the app you can use the exploit to root so I downloaded the .apk and installed and rooted and then used goo.im app to install the latest twrp. So thanks to killahurtz for recomending it and chainfire for the app and exploit and samsung for being a little bit dopey One thing I am still wondering is how would you solve this problem if the security hole did not exist? I know I saw something in the toolkit about it So if this didnt work would In have been able to hookup tob the pc and use the toolkit without having root access?

In ExynosAbuse, it gives you the option to plug the hole after you have rooted, only thing is you may break your camera in the process. I would just stay away from pirated and sketchy apps for now.

[Q] PDAnet Broke with 4.2.2

I have been using PDAnet for a couple of years now and never had a problem with the USB tether until I got an update a week or so ago and now it just gets stuck on "connecting to your phone....". I have been emailing the website for PDAnet and they seem to think the update screwed up a driver or something so I reinstalled everything on the phone and PC including the phone drivers. I preferr stock since I am too lazy and too old to keep up with the speed at which changes come so has anyone else had this problem? If so is there a fix? If theres no fix how hard is it to roll back this last update?
Tethering is important to me so all options are on the table even if I have to get back into rooting (though I preferr not to since you guys would get sick of my dumb questions).

Now this has me bothered. Ive never posted a question in here that didn't get some kind of assistance. That would ordinarily make me think my problem was unique except for I have found others with the same issue posting in the PDAnet and PDAnet plus feedback on the Play store.
I'll take any attempt at something I haven't tried from one of you smarter folks. I did a factory reset and it did nothing to help the problem.

Then complain to PDAnet as they probably need to update their app to work with 4.2.2

I have and they are being quite useless. I've just always had good luck here on XDA. Oh well maybe it isnt meant to be.
On another note does anyone have any suggestions on another app to try for tethering without root?

It's not hard to roll back, except that you'll have to unlock the device's bootloader, which wipes its data. Also, you'll have to find a factory image of 4.2.1 for your device, unless you roll back to 4.1.2, then get an update to 4.2.1 and figure out how to disable it for the 4.2.2 update. http://forum.xda-developers.com/showthread.php?t=1626895

When new versions of Android are released its normal for apps to require an update to work properly.
Koush has that no root usb tethering app. Can't remember the name, search the play store fore more apps from the Rom Manager dev and you will see it. Never used it but that's the one I know of.
Just about any custom firmware will have any tethering block or tracker disabled so you can just tether natively with a ROM.

Solved with jTether (root needed).

Gonna lose it - 4.3 "Security Notice - unauthorized access..."

I searched all yesterday and today and cannot re-root after upgrading from 4.1.2 to 4.3. I always do a ton of searchs no matter what forum I'm on because I don't want to seem lazy like some others out there but this is beyond me. I registered so I could make a thread and this is what I have and the situation:
Samsung Galaxy S3 SCH-R530U
US Cellular
upgraded from 4.1.2 to 4.3
kernel 3.031-2025306 [email protected] #1
baseband version R30UVXUBMJA
build number JSS15J.R530UVXUBMJA
SE for Android status Enforcing SEPF_SCH-530U_4.3_0010
hardware version R530U.01
Previously rooted using Odin, SuperSU, Titanium Backup Pro, ODIN_CWM6.tar.md5
I took the phone back to stock using unroot through SuperSU and upgraded from 4.1.2 to 4.3 OTA with no problems. I've been trying to re-root using numerous combinations (ODIN3 v3.07) and no matter what I do the Samsung Security notice blocks rights to SuperSU (beta v1.76) and Titanium Backup Pro so it won't root. This is the message I get:
"Security notice - unauthorized access to a secured area has been blocked. Tap to learn more."
The most recent md5 file I've tried is CF-Auto-Root-d2usc-d2usc-schr530u.tar.md5 but nothing else has worked either. I'm at my wits end and my brain is about ready to explode. I just need to be able to access Titanium Backup Pro so I can shut off a few programs and processes. Any help is VERY VERY much appreciated. Thanks!!!!!

TTT for some help please.

jguenther said:
I searched all yesterday and today and cannot re-root after upgrading from 4.1.2 to 4.3. I always do a ton of searchs no matter what forum I'm on because I don't want to seem lazy like some others out there but this is beyond me. I registered so I could make a thread and this is what I have and the situation:
Samsung Galaxy S3 SCH-R530U
US Cellular
upgraded from 4.1.2 to 4.3
kernel 3.031-2025306 [email protected] #1
baseband version R30UVXUBMJA
build number JSS15J.R530UVXUBMJA
SE for Android status Enforcing SEPF_SCH-530U_4.3_0010
hardware version R530U.01
Previously rooted using Odin, SuperSU, Titanium Backup Pro, ODIN_CWM6.tar.md5
I took the phone back to stock using unroot through SuperSU and upgraded from 4.1.2 to 4.3 OTA with no problems. I've been trying to re-root using numerous combinations (ODIN3 v3.07) and no matter what I do the Samsung Security notice blocks rights to SuperSU (beta v1.76) and Titanium Backup Pro so it won't root. This is the message I get:
"Security notice - unauthorized access to a secured area has been blocked. Tap to learn more."
The most recent md5 file I've tried is CF-Auto-Root-d2usc-d2usc-schr530u.tar.md5 but nothing else has worked either. I'm at my wits end and my brain is about ready to explode. I just need to be able to access Titanium Backup Pro so I can shut off a few programs and processes. Any help is VERY VERY much appreciated. Thanks!!!!!
Click to expand...
Click to collapse
I have same phone. Recently went to Slimbean (4.3.1). I have Triangle Away and it couldn't access root. I also used CF-Auto-Root. Used a root check app, it says I am rooted. Odin also said device passed. Super User says I am missing a binary and I need to root manually. Trying to find that info

If you find anything out please let me know. A root checker says I'm rooted but I can't access SuperSU or Titanium backup as the S3 is blocking it.

Did you get the Slimbean 4.3.1 for USCC and if so where?

There was just a new SuperSU update and it granted me access to everything. I asked if I wanted it to disable KNOX and I said yes. Titanium Backup works and so does Triangle Away. I think I'm good to go.

How did you update?
jguenther said:
There was just a new SuperSU update and it granted me access to everything. I asked if I wanted it to disable KNOX and I said yes. Titanium Backup works and so does Triangle Away. I think I'm good to go.
Click to expand...
Click to collapse
How did you update to 4.3? Did you use the simple update you can download to computer, or did you use Kies? I'm not having any luck with either. I chatted twice with a Samsung Tech person, but neither one had any help for me. Just thought I'd check to see if you could help me. It's not easy finding someone else on here with US Cellular. Any help would be appreciated. Thank you.

smithar said:
How did you update to 4.3? Did you use the simple update you can download to computer, or did you use Kies? I'm not having any luck with either. I chatted twice with a Samsung Tech person, but neither one had any help for me. Just thought I'd check to see if you could help me. It's not easy finding someone else on here with US Cellular. Any help would be appreciated. Thank you.
Click to expand...
Click to collapse
I tried to download the simple update but my phone wouldn't update to the 4.3 so I did it over the air. You probably know but the OTA software update is in "about device." We have four S3s in our home and only one of them hasn't been able to get the download OTA yet. The only bug that I've found is when you start the phone it will show numerous downloads in the notifications and they will come back even if you clear them. The way to get rid of them is to go to the download icon (green arrow) and clear all the downloads and restart. Hope this helps.

jguenther said:
I tried to download the simple update but my phone wouldn't update to the 4.3 so I did it over the air. You probably know but the OTA software update is in "about device." We have four S3s in our home and only one of them hasn't been able to get the download OTA yet. The only bug that I've found is when you start the phone it will show numerous downloads in the notifications and they will come back even if you clear them. The way to get rid of them is to go to the download icon (green arrow) and clear all the downloads and restart. Hope this helps.
Click to expand...
Click to collapse
I have downloaded the simple update, but get an error msg while trying to install to computer. (1152: error extracting) whatever that means. I uninstalled all Samsung anything from my computer, restarted, shut off firewall & Norton, downloaded again, but same thing while trying to install to computer. I updated to 4.1.2 this way, but keep getting an error on 4.3 update.
I tried to go through Kies. It updated Kies to 2.6, it said Kies3 was for 4.3. When I tried to hook into Kies, it refuses to accept my IMEI #. Says its incorrect. wth. The Samsung Chat Tech told me USCellular 4.3 update wasn't available yet through Kies OTA.
When I tried to get the 4.1.2 update through the phone, it would never give it to me. Even though I unrooted and used Triangle Away, it still knew my sg3 was modified. Maybe I'm doing something wrong. Do you have any suggestions ? I'm not very tech savvy when it comes to these phones.
I'm sorry to bother you with this, but it's rare to find someone with USCellular on here. Thank you so much for your time.

I got the error message too so something is wrong with the download from Samsung/USCC. Just keep trying to do the OTA update and maybe it will go through. My GUESS is that Samsung and USCC stopped doing the update because of a couple bugs or issues. The reason I say that is I updated mine one day (worked), my wife's the next (worked), my son's the next days later (worked) and tried my other son's a couple days later and no update for him. I unrooted mine before the update without doing triangle away so I don't know if that really has anything to do with it at all. However, it does have to be unrooted if you do the OTA. Good luck!

I used Triangle Away, then unrooted. My phone still says 'modified' even though counter no longer says 2. When I try OTA through the phone, it constantly sticks on 'checking for updates'. I'm sure it's because it still says modified. I tried using Kies, my phone will not connect. Keeps saying my s/n is incorrect. I understand my IMEI has been corrupted.
I have started a thread on here for some help in how to get the 4.3 update.
Thank you so much for trying to help me. I will be eligible for an upgrade soon. I just may have to wait to have anything more than 4.1.2.
Again, thank you.

Samsung
jguenther said:
I searched all yesterday and today and cannot re-root after upgrading from 4.1.2 to 4.3. I always do a ton of searchs no matter what forum I'm on because I don't want to seem lazy like some others out there but this is beyond me. I registered so I could make a thread and this is what I have and the situation:
Samsung Galaxy S3 SCH-R530U
US Cellular
upgraded from 4.1.2 to 4.3
kernel 3.031-2025306 [email protected] #1
baseband version R30UVXUBMJA
build number JSS15J.R530UVXUBMJA
SE for Android status Enforcing SEPF_SCH-530U_4.3_0010
hardware version R530U.01
Previously rooted using Odin, SuperSU, Titanium Backup Pro, ODIN_CWM6.tar.md5
I took the phone back to stock using unroot through SuperSU and upgraded from 4.1.2 to 4.3 OTA with no problems. I've been trying to re-root using numerous combinations (ODIN3 v3.07) and no matter what I do the Samsung Security notice blocks rights to SuperSU (beta v1.76) and Titanium Backup Pro so it won't root. This is the message I get:
"Security notice - unauthorized access to a secured area has been blocked. Tap to learn more."
The most recent md5 file I've tried is CF-Auto-Root-d2usc-d2usc-schr530u.tar.md5 but nothing else has worked either. I'm at my wits end and my brain is about ready to explode. I just need to be able to access Titanium Backup Pro so I can shut off a few programs and processes. Any help is VERY VERY much appreciated. Thanks!!!!!
Click to expand...
Click to collapse
it looks to me like samsung are finally making a stand against rooting although i do not agree with this as i use an app called freedom and when i open it i get a security issue from Samsung
The only reason i left iphone for samsung was because i felt like they had something other apple with hardware and i was happy to do this as i could get root access but for now i see that this might not be possible for a while.
i recommend installing a normal superuser.apk and that might work but i cannot check this right now as i am out
i hope this little bit of information did help in anyway

[Q] SM-T217s - my first ever brick.

Hi friends. Long time lurker here.
I've had many Samsung phones and many other android devices, but this is my first brick.
I had flashed the rooted SM-T217s rom, and the wifi wasn't working, so I tried to reflash it, at which point everything went wonky. I searched the forums and found some threads on bricked 217s's, but nothing specific to my situation.
The tablet went to the emergency firmware update screen, and I haven't been able to get Kies to even recognize it. I try to Odin back to the latest stock (B8) but it fails at 'Get PIT for mapping.' My google-fu tells me this is not a good thing.
Am I hosed here? What else can I try?
Thanks XDA, you're my only hope.

joshuaerda said:
Hi friends. Long time lurker here.
I've had many Samsung phones and many other android devices, but this is my first brick.
I had flashed the rooted SM-T217s rom, and the wifi wasn't working, so I tried to reflash it, at which point everything went wonky. I searched the forums and found some threads on bricked 217s's, but nothing specific to my situation.
The tablet went to the emergency firmware update screen, and I haven't been able to get Kies to even recognize it. I try to Odin back to the latest stock (B8) but it fails at 'Get PIT for mapping.' My google-fu tells me this is not a good thing.
Am I hosed here? What else can I try?
Thanks XDA, you're my only hope.
Click to expand...
Click to collapse
Good news, I guess. I was able to flash TWRP recovery and the stock rooted rom from another computer, but now Wifi is borked and there's no network connection. HALP.

joshuaerda said:
Good news, I guess. I was able to flash TWRP recovery and the stock rooted rom from another computer, but now Wifi is borked and there's no network connection. HALP.
Click to expand...
Click to collapse
Okay well I fixed it.
Turns out, the problem was that I was using Odin on a VM on my Mac. I had tried to use a PC, but I think the USB controller was too old, so that failed too. I had to use Heimdall to flash each of the partitions from the B8 zip manually. It worked, and I'm back in business, though not rooted. I suppose I'll wait until there's a better way to root before I try it again.

254336992952
​
joshuaerda said:
Okay well I fixed it.
Turns out, the problem was that I was using Odin on a VM on my Mac. I had tried to use a PC, but I think the USB controller was too old, so that failed too. I had to use Heimdall to flash each of the partitions from the B8 zip manually. It worked, and I'm back in business, though not rooted. I suppose I'll wait until there's a better way to root before I try it again.
Click to expand...
Click to collapse
You should have made a backup. I used twrp recovery flashed a rom same thing wifi wouldnt work so I restored back. If you get it working again make a backup imo. Goodluck.

IAMRUDYT said:
​
You should have made a backup. I used twrp recovery flashed a rom same thing wifi wouldnt work so I restored back. If you get it working again make a backup imo. Goodluck.
Click to expand...
Click to collapse
same here, I have the rom, but hesitated on the firmware, waiting to see if someone gets the wifi working, not to many developers here for this tablet.

sm t217s
Ok guys. Heres my deal with this TAB. Ive rooted... Unrooted. wipe wipe wipe wippty wipe . WiFi not working. Fixed it with NB8. So here now I sit with:
----NB8 Wifi works---
----TWRP-----
Yup, pathetic i know. I cant even get the supersu to flash. TWRP wont move it over to flash off external sd card. Im not hip to abd plus i heard you leave yourself wide opento visitors when using that.
Ive eye hustled a thread on here that some friends are getting back together to rock it on a custom rom so my fingers are crossed. This tab is so neglected i mayjust go get the 210r. But i really dont want to. So my question is....
Can someone please give me links to files that work with the NB8 stock firmware. Some of the links are outdated after sprint uploaded the new bootloader. We are a small community on this tab so lets stick together on this. I dont think cynogen isgoing to do anything for it. As they concentrate on thier new phone which looks pretty sweet by the way. K im done. Going to wait for help and play with this htc one s
thats been collecting dust.

Rooted
Sent from my SM-T217S using XDA Premium 4 mobile app

[Q] I have a problem

Okay, so I have a T Mobile SGH t999l, a few months back I rooted it, that went smoothly. I then kept it rooted for a couple of months. Later, I wanted to restore my device to factory settings, (and did so very smoothly) but I forgot to uninstall superuser for unrooting it. It still works fine, but when I checked it with root checker (pro), I got error messages saying my phone was not properly rooted. Ever since then, I've been afraid to root my phone again. Someone, please help me get my phone back up, working, and rooted again (and a step-by-step guide, if I have to do it some special way now (if not, please, just tell me so)).

What build are you running? If you have a custom recovery installed, just flash the latest SuperSU from chainfires thread.
Sent from my SM-N900T using Tapatalk

DocHoliday77 said:
What build are you running?
Click to expand...
Click to collapse
I'm running JSS15J.T999LUVUBMK.
PS. On second thought, could you include a detailed step-by-step guide on what to do, because I actually feel a bit uncomfortable doing this on my own.

There are several ways to gain root, all of which are well
documented. Im not going to rewrite another guide on it, just too much when its been done already.
Go to the firmware thread linked in my sig and download the root66 firmware for your device. Flash via odin and you will be rooted. You will find instructions in the same thread, or the root66 thread and many other places via search.
Just backup important data first, just in case.
And check the other sticky threads too for alternatives and more info.
If you have a specific question about any of ill be glad to answer it, theres just no sense in rewriting whats already been done. Dont take it the wrong way.
Two things, stay away from the toolkit if you find it, and most odin instructions are for Odin v3.07. If you use v3.09, the only difference is use AP instead of PDA, they are the same. Youll understand if you run into it.
Sent from my SM-N900T using Tapatalk

DocHoliday77 said:
There are several ways to gain root, all of which are well
documented. Im not going to rewrite another guide on it, just too much when its been done already.
Go to the firmware thread linked in my sig and download the root66 firmware for your device. Flash via odin and you will be rooted. You will find instructions in the same thread, or the root66 thread and many other places via search.
Just backup important data first, just in case.
And check the other sticky threads too for alternatives and more info.
If you have a specific question about any of ill be glad to answer it, theres just no sense in rewriting whats already been done. Dont take it the wrong way.
Two things, stay away from the toolkit if you find it, and most odin instructions are for Odin v3.07. If you use v3.09, the only difference is use AP instead of PDA, they are the same. Youll understand if you run into it.
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
Are you %100 sure (given my specific predicament) this will work? No offense, but it sounds kind of generic, given one specific set of circumstances.

You can never be 100% when doing anything to your device. But as a general rule, if you are having problems, odin flashing stock firmware and factory resetting is the best chance of fixing stuff. Root66 is pretty much the same thing, only pre rooted, with knox removed. Its as close as you can get to 100% stock rooted on 4.3.
The only real issue is usually if you are still running base firmware build 4.1.2. At this point there is no warranty bit and you can still flash older firmware. Once on 4.3 this changes. So if youre already on 4.3 firmware, theres nothing to really lose by reflashing it or updating to the newer 4.3.
I wouldnt call it generic, as I stated above, this is often the best chance of getting things working the way you want. Its solved countless issues.
In the end its up to you what route you want to go. If youre not comfortable with my recommendation, I suggest you read up on other alternatives and choose what you are comfortable with. Wont hurt my feelings either way. Its your device and your risk, so be comfortable with what you are about to do.
Sent from my SM-N900T using Tapatalk

Try to take risk it never harms, Those who never did a mistake they never tried anything u learn from your mistakes.
Just got the T-mo T999 was on stock 4.3 flashed the cf root with ODIN, Rotted used GO im to flash the recovery BAM DONE. Stock rooted with recovery installed.
Now searching for a ROM.

Thanks
Thankyou for the help you all gave me, it worked!!!

Please, HELP!!!
I was trying to install an Xposed module, but I don't remember which one, and I don't remember anything after that. Now my phone is not working (at least, not like you'd expect it to) anymore. Whenever I try to do much of anything, it starts displaying messages like "Unfortunately, '.............' has stopped", or "Unfortunately, the process '.............' has stopped". The most notable being, "Unfortunately, Google play Services has stopped", and "Unfortunately, the process com.google.processes.gapps has stopped". Please, HELP!!!

I have a problem
Give me a break said:
I was trying to install an Xposed module, but I don't remember which one, and I don't remember anything after that. Now my phone is not working (at least, not like you'd expect it to) anymore. Whenever I try to do much of anything, it starts displaying messages like "Unfortunately, '.............' has stopped", or "Unfortunately, the process '.............' has stopped". The most notable being, "Unfortunately, Google play Services has stopped", and "Unfortunately, the process com.google.processes.gapps has stopped". Please, HELP!!!
Click to expand...
Click to collapse
It works well enough, after I get through all the original errors I can call (and receive calls), and receive texts, but I can't use the keyboard, or any of the apps involving any form of Wireless Data (eg. Wi-Fi, Bluetooth, 3G/4G or any other cellular data) or GPS.

In your op you wanted to just be stock but rooted and stable, correct? Did you ever flash the root66 firmware I originally suggested?